.sdf corruption?
-
Wednesday, February 20, 2013 7:04 PM
We are using SQL CE as a subscriber in a merge replication topology. Occasionally, users get the following error when trying to sync with the publisher:
Cannot connect to C:\[pathRemovedByPoster]\DB.sdf.
Invalid provider type. [ Db version = 0,Requested version = 1,File name = \\?\C:\[pathRemovedByPoster]\DB.sdf ] (SQL Server Compact ADO.NET Data Provider)
I get the same error when I try to connect to the .sdf directly through SSMS. I am under the impression that this is caused by .sdf corruption. Is this true? How can I tell? I've seen the C# code that allows you to verify corruption, but does anyone know of a utility I can use so I won't have to get developers involved? Is there any other info I can provide her that will help diagnose the problem?
Thanks in advance,
Clint
Clint
All Replies
-
Wednesday, February 20, 2013 10:01 PMModeratorwhat database version does the Sql Server Compact Toolbox version detector think the file is (reads first bytes of file header)
Please mark as answer, if this was it. Visit my SQL Server Compact blog
-
Thursday, February 28, 2013 11:43 PMSorry Erik, it's taken me a while to get back to this. I won't be able to get that info until next week. What version should I expect?
Clint
-
Friday, March 01, 2013 7:39 AMModerator
Try it out, if no version can be read, it is not a SQL Server Compact file, or it cannot be saved in any way.Please mark as answer, if this was it. Visit my SQL Server Compact blog
- Marked As Answer by Maggie LuoMicrosoft Contingent Staff, Moderator Monday, March 04, 2013 9:22 AM

