SQLDriver not initialized with server version
And a bit of Stacktrace:
[InvalidOperationException: SQLDriver not initialized with server version.]OpenAccessRuntime.Relational.sql.SqlDriver.get_ExtensionName() +55
OpenAccessRuntime.Relational.RelationalMetaDataBuilder.findMatchingJdbcColumn(DataObjectsExtension[] nested) +56
OpenAccessRuntime.Relational.RelationalMetaDataBuilder.createColumn(DataObjectsExtension[] nested, String fieldName, Class javaType, String oType, Boolean secondaryTable) +16
OpenAccessRuntime.Relational.RelationalMetaDataBuilder.createJdbcSimpleField(FieldMetaData fmd) +173
OpenAccessRuntime.Relational.RelationalMetaDataBuilder.createJdbcField(FieldMetaData fmd, Boolean quietParam) +69
Any thoughts?
28 Answers, 1 is accepted
I would like to see a bit more of the stack trace, can you give us more information on when this happens? The exception occurs when we try to calculate a name that can be used for configuration, but it requires the server version number to be read already, which in your case seems to be missing.
Best wishes,Thomas
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>
This is the full stacktrace
[InvalidOperationException: SQLDriver not initialized with server version.] OpenAccessRuntime.Relational.sql.SqlDriver.get_ExtensionName() +55 OpenAccessRuntime.Relational.RelationalMetaDataBuilder.findMatchingJdbcColumn(DataObjectsExtension[] nested) +56 OpenAccessRuntime.Relational.RelationalMetaDataBuilder.createColumn(DataObjectsExtension[] nested, String fieldName, Class javaType, String oType, Boolean secondaryTable) +16 OpenAccessRuntime.Relational.RelationalMetaDataBuilder.createJdbcSimpleField(FieldMetaData fmd) +173 OpenAccessRuntime.Relational.RelationalMetaDataBuilder.createJdbcField(FieldMetaData fmd, Boolean quietParam) +69 [MetadataException: The metadata for field '_totalPoints' of class 'SolidGkanServices.Core.Pd.AppUser' cannot be initialized: SQLDriver not initialized with server version.] Telerik.OpenAccess.RT.ExceptionWrapper.Throw() +7 OpenAccessRuntime.storagemanager.StorageManagerFactoryBuilder.createSmfForURL() +269 OpenAccessRuntime.storagemanager.StorageManagerFactoryBuilder.createStorageManagerFactory() +276 OpenAccessRuntime.DataObjects.PersistenceManagerFactoryImp.createStorageManagerFactory() +442 OpenAccessRuntime.DataObjects.PersistenceManagerFactoryBase.init() +811 OpenAccessRuntime.DataObjects.PersistenceManagerFactoryImp.init() +41 OpenAccessRuntime.DataObjects.BootstrapPMF.getPersistenceManagerFactory(PropertySet props) +233 Telerik.OpenAccess.RT.Helper.getPersistenceManagerFactory(PropertySet props) +223 Telerik.OpenAccess.RT.DatabaseAdapter.AssertPersistenceManagerFactory(String usr, String password, Boolean open) +1274 Telerik.OpenAccess.RT.DatabaseAdapter.GetObjectScope(TransactionProvider provider) +32 Telerik.OpenAccess.Database.GetObjectScope(TransactionProvider provider) +13 Telerik.OpenAccess.OpenAccessContextBase.GetScope() +42 Telerik.OpenAccess.OpenAccessContext.GetAll() +32 SolidGkanServices.Core.Pd.UserRepository.FindByFacebookId(String facebookId) in C:\Projects\BitBucket\parking-defenders-services\SolidGkanServices.Core\Repositories\PdUserRepository.cs:0 SolidGkanServices.Web.Default.Page_Load(Object sender, EventArgs e) in C:\Projects\BitBucket\parking-defenders-services\SolidGkanServices.Web\Default.aspx.cs:25 System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14 System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35 System.Web.UI.Control.OnLoad(EventArgs e) +91 System.Web.UI.Control.LoadRecursive() +74 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207
Thanks,
John
thanks for the information. We found the issue and the next patch will contain the needed changes. The problem is bound to the increased major version number that SQL Azure reports for _some_ accounts; our test account still shows the older version number.
All the best,Thomas
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>
just my 2 cents...
Your are right and we acknowledge the issue severity. In order to fix it, a service pack will be released as soon as possible.
We apologize to the clients affected by this discrepancy and we'll certainly keep you posted for any new developments.
Greetings,
Ivailo
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>
we expect a build to be ready end of this week or next week. The reason for this issue to happen is that Microsoft changed the servers for some of their Azure customers (I think for unpaid accounts) to a new major version, which we were not handling correctly. I still see the older version!
Kind regards,Thomas
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>
The thing is application is in production (so it is paid account) and has been like that for more than a year now. Only OA has been updated in this time.
Major number change shouldn’t really be responsible for application to fail, especially here, because SQL Azure will get updated from time to time, and if so I believe quick fix should be very important, otherwise you can't claim that you support SQL Azure.
RedGate had similar problems with SQL Azure Backup, but were fixed within a day: http://www.simple-talk.com/community/blogs/richard/archive/2011/08/08/102745.aspx .
I agree however that that’s not the proper way to upgrade SQL Azure.
We are now having the same issue and we have a production app failing with no fix as well!! Microsoft is upgrading the Azure servers according to their schedule and it does not have anything to do with paid vs not. Please provide a patch for this as soon as possible.
Brent
I have a production downtime and unhappy customers. I really do not want to switch ORMs, so please help !!!
Telerik, can I share it with others?
The site is scheduled to go live tomorrow, so I got to stay up all night last night and completely rebuild it as a regular .Net project.
All that being said, I know things happen.. This is still part of what we are to deliver, so I would like to be informed immediately when a patch is released.
Any talk of an exact release date?
I owe you one !
thank you for your support!
Can you please open a support ticket? We will provide a hotfix for version 2011.2.713.3 there.
All the best,
Jan Blessenohl
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>
Mike
All our local numbers are available on this side.
Greetings,
Jan Blessenohl
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>
Jason
We will ship an internal build today. If you nevertheless need the hotfix for the 2011.2.713.3 version please open a support ticket.
Regards,
Jan Blessenohl
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>
Thanks,
Jason
The SQL Azure server now reports version 11.0, we were not prepared.
Greetings,
Jan Blessenohl
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>
1.) I got the hotfix and it worked. Thanks
2.) I appreciate your honesty, it is refreshing to hear the truth.
Also, what can be and will be done in the future so this won't happen?
Jason
We are trying to get more information from Microsoft and we will start testing beta version. Our continuous integration tests are now running against Denali.
On the other hand, you are paying for your Azure account and from my perspective you should ask MS, why they do not offer you a reliable environment. I do not think that any other hosting provider will do such changes without notice but if nobody complains, it might happen again in the future.
All the best,
Jan Blessenohl
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>
I plan on letting MS know my dissatisfaction with what happened on their end. Lucky for us we are in beta testing but we will have to explain what happened. I do really appreciate Telerik getting a hotfix out so fast.
I am just curious why djsolid saw this on 8/10 and I did not see it until 9/7. I am just trying to piece everything together so I can do my best on my side so this does not happen again.
Again thanks for getting me a fix so fast.
Jason
For us it looked like Microsoft did it in waves. We were unlucky with our test machine, it was updates as one of the last.
Greetings,
Jan Blessenohl
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>
I am getting the following error. is this the same? were can you download the patch? i am using the latest trail version and it doesn't not working.
Noam
The metadata for field '_id' of class 'Dengue.DB.Customer' cannot be initialized: SQLDriver not initialized with server version.
at Telerik.OpenAccess.RT.ExceptionWrapper.Throw() at OpenAccessRuntime.storagemanager.StorageManagerFactoryBuilder.createSmfForURL() at OpenAccessRuntime.storagemanager.StorageManagerFactoryBuilder.createStorageManagerFactory() at OpenAccessRuntime.DataObjects.PersistenceManagerFactoryImp.createStorageManagerFactory() at OpenAccessRuntime.DataObjects.PersistenceManagerFactoryBase.init() at OpenAccessRuntime.DataObjects.PersistenceManagerFactoryImp.init() at OpenAccessRuntime.DataObjects.BootstrapPMF.getPersistenceManagerFactory(PropertySet props) at Telerik.OpenAccess.RT.Helper.getPersistenceManagerFactory(PropertySet props) at Telerik.OpenAccess.RT.DatabaseAdapter.AssertPersistenceManagerFactory(String usr, String password, Boolean open) at Telerik.OpenAccess.RT.DatabaseAdapter.GetObjectScope(TransactionProvider provider) at Telerik.OpenAccess.OpenAccessContextBase.GetScope() at Telerik.OpenAccess.OpenAccessContext.GetAll[T]() at Dengue.Services.Services.CustomerService.GetCustomer(String email) in F:\Sinibex_Git\Sinibex\Server\Dengue\Dengue.Services\Services\CustomerService.cs:line 252 at Dengue.Services.Services.CustomerService.GetCustomer(IPrincipal user) in F:\Sinibex_Git\Sinibex\Server\Dengue\Dengue.Services\Services\CustomerService.cs:line 243 at Dengue.Controllers.HomeController.OnAuthorization(AuthorizationContext filterContext) in F:\Sinibex_Git\Sinibex\Server\Dengue\Dengue\Controllers\HomeController.cs:line 32 at System.Web.Mvc.ControllerActionInvoker.InvokeAuthorizationFilters(ControllerContext controllerContext, IList`1 filters, ActionDescriptor actionDescriptor) at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName) at System.Web.Mvc.Controller.ExecuteCore() at System.Web.Mvc.ControllerBase.Execute(RequestContext requestContext) at System.Web.Mvc.MvcHandler.<>c__DisplayClass6.<>c__DisplayClassb.
System.InvalidOperationException: SQLDriver not initialized with server version. at OpenAccessRuntime.Relational.RelationalMetaDataBuilder.findMatchingJdbcColumn(DataObjectsExtension[] nested) at OpenAccessRuntime.Relational.RelationalMetaDataBuilder.createJdbcSimpleField(FieldMetaData fmd) at OpenAccessRuntime.Relational.RelationalMetaDataBuilder.createJdbcField(FieldMetaData fmd, Boolean quietParam)
If you go to the telerik trial page you will find a 'Browse all product files' link. Here you can find the latest build, that fixes the problems (Telerik-OpenAccess-ORM-trial-2011.2.908.1.zip)
Best wishes,
Jan Blessenohl
the Telerik team
Check out the latest stable build of Telerik OpenAccess ORM. Download it and benefit from our new Project Templates.
My support expired in September, so I'm running 2.713 - I appreciate "end of support" means "end of upgrades" but I've also just hit this problem and really think this should not count as an upgrade but a fix (given that the problem was acknowledged by you guys before my support ran out); is there some way I can download the hotfix?
Thanks!
Edit: I figured out that the answer is yes. Excellent! :)