Unrecognized database format. (1 Viewer)

Extra_Cover

Registered User.
Local time
Today, 06:46
Joined
Oct 21, 2008
Messages
71
Has anyone else encountered this error after upgrading to Windows 10?


The workaround does work, I didn't need to stop and re-start the NET SEVER either. I connect to my clients via Remote Desktop and was afraid if I stopped the NET Server my connection would drop.

Rather frustrated that Microsoft didn't advertise the fix better.
 

theDBguy

I’m here to help
Staff member
Local time
Yesterday, 22:46
Joined
Oct 29, 2018
Messages
21,455
Sure, this is an old issue without a permanent fix yet. Glad to hear you found the workaround and it worked for you (I've heard it didn't work for some people). Cheers!
 

HiTechCoach

Well-known member
Local time
Today, 00:46
Joined
Mar 6, 2006
Messages
4,357
I have run in within a Remote Desktop session and it worked fine and solved the issue.

I use a .cmd file to run the commands.Including the NET stop and start
 

The_Doc_Man

Immoderate Moderator
Staff member
Local time
Today, 00:46
Joined
Feb 28, 2001
Messages
27,148
In the final analysis, any network interruption has a chance (but not a certainty) of making a database unrecoverable. All that is needed is for the network to break halfway through a remote-disk write-back operation involving more than one disk buffer.
 

Users who are viewing this thread

Top Bottom