-
Notifications
You must be signed in to change notification settings - Fork 373
Azure Storage Emulator attempts to create LocalDB files in c:\Users #635
Comments
Can anyone take a look, please? Our route me to the appropriate team/contact? |
Hi @abatishchev, Please follow the steps that we have outline here and let us know if you still see any issues. Thanks! |
As I said in the last paragraph, the issue is that it tries to create |
I see, the final backslash in the path is just missing. We'll take a look. @kfarmer-msft |
hi @mirobers, I talked to @kfarmer-msft and we concluded that this issues is likely related to LocalDB/SQL Server rather than to Azure Storage Emulator. Do you have by chance any point of contact there? Here's a public bug report which I'm basically facing too. |
I Have the same error, any solution? |
@ranouf see my answer on DBA.SE |
I tried to clean up localdb but didn't work, so anyone has an issue running storage emulator with local db can benefit from this command to run it on SqlExpress. Command: |
same problem again upgrading from 5.6 to 5.7... |
This solution is not recommended in generally, but you can try it. |
If you are using LocalDB for SQL Server 2017 and hit the above issue, you may want to try install CU6 for SQL Server 2017 here: https://support.microsoft.com/en-sg/help/4101464 The fixes includes the following: |
I tried the latest CU yesterday to no avail. I was able to install Emulator with "AzureStorageEmulator init /forcecreate /sqlinstance MSSQLLocalDB". I could not use (localdb)\MSSQLLocalDB for some reason, but you can still connect to .\MSSQLLocalDB in SSMS if you want to see the Emulator data sausage. It sure would be nice if Microsoft would fix this problem with SQL 2017. |
it worked for me 👍 |
When I run this command:
I'm getting this error:
In the log file I see this error:
So it attempts to create
C:\Users\alexbat.REDMONDAzureStorageEmulatorDb53.mdf
rather thanC:\Users\alexbat.REDMOND\AzureStorageEmulatorDb53.mdf
(note the slash before the file name).Do you know why? How can this be fixed? I was getting the same error with ASE 5.2.
The text was updated successfully, but these errors were encountered: