New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No message for error code 335544528 found [DNET911] #838
Comments
Commented by: Yuriy (paulesprit) Stack trace image |
Modified by: Yuriy (paulesprit)Attachment: image.png [ 13393 ] |
Modified by: Yuriy (paulesprit)Attachment: image.png [ 13394 ] description: I logged in to system using Firebird.SQL.Client and everythin was OK, but suddenly I got this exception: [FbException (0x140000d0): database [InvalidOperationException: Could not retrive storage version.] [ProviderIncompatibleException: The provider did not return a Provider ManifestToken string] [ProviderIncompatibleException: An error occured accessing the database. This usually mean that the connection to database failed. Check that the connection string is correct..] This stack trace was retyped from image so can have any errors => I logged in to system using Firebird.SQL.Client and everythin was OK, but suddenly I got this exception: [FbException (0x140000d0): database [InvalidOperationException: Could not retrive storage version.] [ProviderIncompatibleException: The provider did not return a Provider ManifestToken string] [ProviderIncompatibleException: An error occured accessing the database. This usually mean that the connection to database failed. Check that the connection string is correct..] This stack trace was retyped from image so can have any errors. Original image with stack trace attached |
Modified by: Yuriy (paulesprit)description: I logged in to system using Firebird.SQL.Client and everythin was OK, but suddenly I got this exception: [FbException (0x140000d0): database [InvalidOperationException: Could not retrive storage version.] [ProviderIncompatibleException: The provider did not return a Provider ManifestToken string] [ProviderIncompatibleException: An error occured accessing the database. This usually mean that the connection to database failed. Check that the connection string is correct..] This stack trace was retyped from image so can have any errors. Original image with stack trace attached => I logged in to system using Firebird.SQL.Client and everythin was OK, but suddenly I got this exception: [FbException (0x140000d0): database [InvalidOperationException: Could not retrive storage version.] [ProviderIncompatibleException: The provider did not return a Provider ManifestToken string] [ProviderIncompatibleException: An error occured accessing the database. This usually mean that the connection to database failed. Check that the connection string is correct..] This stack trace was retyped from image so can have any errors. Original image with stack trace attached I did not see such issues on 6.6.0.0 |
Commented by: @mrotteveel Error 335544528 is "database <name> shutdown" |
Commented by: @cincuranet As Mark said, that's message when database is shutdown. There's nothing related to this on provider side. You should bring your database online and it will be good. |
Commented by: Yuriy (paulesprit) We use Firebird.Embedded v3.0.0.32485 and database should be always online. |
Commented by: @cincuranet Apparently somebody or something did the shutdown. |
Commented by: Yuriy (paulesprit) As I understand, one of possible reasons - IIS Idle Timeout, which could shutdown IIS after 20 minutes of idle. But it have to get back running again after the first web request. Since there are no any code which manages DB shutdown, seems like embedded database still doesn't handle the stop of website by timeout. |
Commented by: @cincuranet It's not about app pool on IIS idle/shutdown. The database itself can be put into shutdown mode, i.e. using gfix https://firebirdsql.org/rlsnotesh/util-gfix.html. It can be done programmatically from FirebirdClient too. So maybe you have some piece of code that did that. |
Commented by: Yuriy (paulesprit) We don't use such low level utils for controlling FB server except packages from Nuget, but anyway such shutdowns sometime occurs. The reason is that we use Firebird emmbedded on production in serious project and don`t want our clients face such problems. |
Commented by: @cincuranet This functionality is present in the NuGet package of FirebirdClient. But. If you can create a reproducible test case, I can have a look. Without it, there's not much I can do. |
Commented by: @cincuranet Closing this for now. Could be reopened when some reproducible stuff is provided. |
Submitted by: Yuriy (paulesprit)
Attachments:
image.png
image.png
I logged in to system using Firebird.SQL.Client and everythin was OK, but suddenly I got this exception:
Stack trace:
[IscException: database
No message for error code 335544528 found]
FirebirdSql.Data.Client.Native.FesServiceManager.ProcessSatatusVector(IntPtr[] statusVector) +105
FirebirdSql.Data.Client.Native.FesServiceManager.Attach(...) +184
FirebirdSql.Data.Client.Native.FesServiceManager.Open() +253
[FbException (0x140000d0): database
No message for error code 335544528 found]
FirebirdSql.Data.Services.FbService.Open() +602
FirebirdSql.Data.Services.FbService.QueryService(..)
FirebirdSql.Data.Services.FbService.ProcessQuery(..)
FirebirdSql.Data.Services.FbService.Query(..)
FirebirdSql.Data.Services.FbServerProperties.GetInfo(..)
FirebirdSql.Data.Services.FbServerProperties.GetString(...)
EntityFramework.Firebird.FbProviderServices.GetDbProviderManifestToken()
[InvalidOperationException: Could not retrive storage version.]
EntityFramework.Firebird.FbProviderServices.GetProviderManifestToken(DbConnection connection)
System.Data.Entity.Core.Common.DbProviderServices.GetProviderManifestToken(DbConnection connection)
[ProviderIncompatibleException: The provider did not return a Provider ManifestToken string]
...
[ProviderIncompatibleException: An error occured accessing the database. This usually mean that the connection to database failed. Check that the connection string is correct..]
This stack trace was retyped from image so can have any errors. Original image with stack trace attached
I did not see such issues on 6.6.0.0
The text was updated successfully, but these errors were encountered: