Emulatore di archiviazione di Azure non riesce dopo l'aggiunta di VS 2015 SDK

Question

Ho installato Azure SDK 2.5 e Tools per VS2013 installato e funzionante per un bel po '. Oggi ho installato SDK e Tools per VS2015 e ora il mio Azure Storage Emulator non verrà avviato. Al primo tentativo per avviarlo ho ottenuto uno 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. 

Dopo il riavvio della macchina, sto ottenendo un errore minore:

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. 

Ma esecuzione init non funziona:

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. 

L'avvio di -inprocess indica che il mio accesso non è riuscito. Sono un amministratore sulla macchina, quindi è strano.

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 

Esecuzione di init con -inprocess ha pronunciato la seguente dettaglio:

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.. 

Quindi c'è comunque di recuperare da questo o devo disinstallare tutto e ricominciare da capo?

Answer 1

È possibile utilizzare il seguente processo per recuperare dalla maggior parte dei problemi di init che coinvolgono il database. Si noti che tutti i dati nell'emulatore al momento andranno persi.

eliminare l'istanza di SQL:

sqllocaldb stop MSSQLLocalDB 
sqllocaldb delete MSSQLLocalDB 

Ora eliminare i seguenti file di database:

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

Infine, ricreare l'istanza di SQL:

sqllocaldb start MSSQLLocalDB 

quindi ripetere l'init emulatore.