When we upgrade versions of the Storage Emulator it is most likely that the database has undergone some new enhancements, as a result we need to ensure the database gets updated regardless of it's prior existence. Here we see a more granular level of explanation, informing that the LocalDB instance is corrupt. Net framework 4.6.1 installed on my PC, when I install Azure Storage Emulator v4.2 few weeks ago and I didnt have this issue, I am using windows 7 sp.
Ĭannot access LocalDB instance folder: %%LOCALAPPDATA%%\Microsoft\Microsoft SQL Server Local DB\Instances\. I've just downloaded the latest version of. See the Windows Application event log for error details. Apologies if this is the wrong place to file this bug, I've been looking for a location for the last 30 mins and this is the 'best/nearest' I can find. Taking a look at the 'application' event log however reveals more detail. Please configure the SQL Server instance for Development Storage using the ‘DSInit’ utility in the Windows Azure SDK. Looking back at the error log may have left you confused as you may well have verified that a LocalDB instance does indeed exist. Failed to start Development Storage: the SQL Server instance XXX could not be found. However digging a little deeper into what the installer is attempting to do will help resolve the issue. The error message at first may appear confusing as you most likely do have an available SQL instance.
0 kommentar(er)
