Azure-Speicheremulator schlägt fehl, nachdem VS 2015 SDK hinzugefügt wurde

Question

Ich habe Azure SDK 2.5 und Tools für VS2013 installiert und funktioniert seit einiger Zeit einwandfrei. Heute habe ich das SDK und Tools für VS2015 installiert und jetzt startet mein Azure Storage Emulator nicht. Beim ersten Versuch, es zu starten bekam ich einen SqlException:

Unhandled Exception: System.Data.SqlClient.SqlException: 
An error occurred while processing the log for database If possible, 
restore from backup. If a backup is not available, it might be 
necessary to rebuild the log. 

Nach dem Neustart des Computers, ich bin eine geringere Störung zu erhalten:

C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>WAStorageEmulator start Windows Azure Storage Emulator 
3.4.0.0 command line tool Error: The storage emulator needs to be initialized. Please run the 'init' command. 

Aber läuft init nicht funktioniert:

C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>WAStorageEmulator init Windows Azure Storage Emulator 3.4.0.0 command line tool Error: Cannot create database. 

Beginnend mit -inprocess sagt mein Login fehlgeschlagen. Ich bin ein Admin auf der Maschine, also ist das merkwürdig.

C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>WAStorageEmulator start -inprocess 
Windows Azure Storage Emulator 3.4.0.0 command line tool 
Cannot open database "WAStorageEmulatorDb34" requested by the login. The login failed. 
Login failed for user 'DOMAIN\genslow'. 
3/24/2015 10:00:57 AM [Info] Starting Service: Blob 
3/24/2015 10:00:57 AM [Verbose_debug] [Nephos.Storage] { Initialize 
3/24/2015 10:00:57 AM [Info_debug] Loading config Param NephosAllowPathStyleUris (Allow path-style URIs) read: true 
3/24/2015 10:00:57 AM [Info_debug] Successfully loaded NephosAllowPathStyleUris: True 
3/24/2015 10:00:57 AM [Info_debug] Loading config Param NephosIncludeInternalDetailsInErrorResponses (Include internal details in error responses) read: false 
3/24/2015 10:00:57 AM [Info_debug] Successfully loaded NephosIncludeInternalDetailsInErrorResponses: False 
3/24/2015 10:00:57 AM [Info_debug] Loading config Param StampName (Stamp Name) read: StorageEmulator 
3/24/2015 10:00:57 AM [Info_debug] BlockBlob: Load Interval failed. IsGC: True, Exception at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt) 
    at Microsoft.WindowsAzure.DevelopmentStorage.Store.BlockBlobGarbageCollector.GetTimerIntervalOrDefault(Boolean isGC) 
3/24/2015 10:00:57 AM [Info_debug] BlockBlob: Load Interval failed. IsGC: False, Exception at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt) 
    at Microsoft.WindowsAzure.DevelopmentStorage.Store.BlockBlobGarbageCollector.GetTimerIntervalOrDefault(Boolean isGC) 
3/24/2015 10:00:57 AM [Verbose_debug] [Nephos.Storage] } Initialize 
Service Status: Blob http://127.0.0.1:10000/ True 
3/24/2015 10:00:57 AM [Info] Starting Service: Queue 
3/24/2015 10:00:57 AM [Verbose_debug] [Nephos.Queue] { Initialize 
3/24/2015 10:00:57 AM [Info_debug] Loading config Param NephosAllowPathStyleUris (Allow path-style URIs) read: true 
3/24/2015 10:00:57 AM [Info_debug] Successfully loaded NephosAllowPathStyleUris: True 
3/24/2015 10:00:57 AM [Info_debug] Loading config Param NephosIncludeInternalDetailsInErrorResponses (Include internal details in error responses) read: false 
3/24/2015 10:00:57 AM [Info_debug] Successfully loaded NephosIncludeInternalDetailsInErrorResponses: False 
3/24/2015 10:00:57 AM [Info_debug] Loading config Param StampName (Stamp Name) read: StorageEmulator 
3/24/2015 10:00:57 AM [Verbose_debug] [DevelopmentStorage.Queue] } Initialize 
Service Status: Queue http://127.0.0.1:10001/ True 
3/24/2015 10:00:57 AM [Info] Starting Service: Table 
3/24/2015 10:00:57 AM [Verbose_debug] [Nephos.Table] { Initialize 
3/24/2015 10:00:57 AM [Info_debug] Loading config Param NephosAllowPathStyleUris (Allow path-style URIs) read: true 
3/24/2015 10:00:57 AM [Info_debug] Successfully loaded NephosAllowPathStyleUris: True 
3/24/2015 10:00:57 AM [Info_debug] Loading config Param NephosIncludeInternalDetailsInErrorResponses (Include internal details in error responses) read: false 
3/24/2015 10:00:57 AM [Info_debug] Successfully loaded NephosIncludeInternalDetailsInErrorResponses: False 
3/24/2015 10:00:57 AM [Info_debug] Loading config Param StampName (Stamp Name) read: StorageEmulator 
3/24/2015 10:00:57 AM [Info] NOT using custom threadpool for blocking calls 
Service Status: Table http://127.0.0.1:10002/ True 

Ausführen von init mit -inprocess ergibt folgendes Detail:

C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>WAStorageEmulator init -inprocess 
Windows Azure Storage Emulator 3.4.0.0 command line tool 
Added reservation for http://127.0.0.1:10000/ in user account DOMAIN\genslow. 
Added reservation for http://127.0.0.1:10001/ in user account DOMAIN\genslow. 
Added reservation for http://127.0.0.1:10002/ in user account DOMAIN\genslow. 

Found SQL Instance (localdb)\MSSQLLocalDB. 

Creating database WAStorageEmulatorDb34 on SQL instance '(localdb)\MSSQLLocalDB'. 
Cannot create database 'WAStorageEmulatorDb34' : Database 'WAStorageEmulatorDb34' already exists. Choose a different database name.. 
One or more initialization actions have failed. Resolve these errors before attempting to run the storage emulator again. 
Error: Cannot create database 'WAStorageEmulatorDb34' : Database 'WAStorageEmulatorDb34' already exists. Choose a different database name.. 

So ist es trotzdem, sich davon zu erholen, oder sollte ich alles zu deinstallieren und neu beginnen?

Answer 1

Sie können den folgenden Prozess verwenden, um die meisten Init-Probleme mit der Datenbank wiederherzustellen. Beachten Sie, dass alle Daten im Emulator derzeit verloren gehen.

die SQL-Instanz löschen:

sqllocaldb stop MSSQLLocalDB 
sqllocaldb delete MSSQLLocalDB 

nun folgende Datenbankdateien löschen:

%USERPROFILE%\AzureStorageEmulatorDb*.mdf 
%USERPROFILE%\AzureStorageEmulatorDb*.ldf 

schließlich die SQL-Instanz neu:

sqllocaldb start MSSQLLocalDB 

dann den Emulator init wiederholen.