Windows Azure Storage Emulator failed to install - azure

I almost wasted my whole day trying to install Windows Azure Storage Emulator but somehow it is not getting installed..
The log is showing me this error : Sql instance not found. I tried re-installing Sql server 2012 but it did not help. It is not able to find Sql instance at all..
Here is the detailed log : http://pastebin.com/KUW4mjuf
I tried googling around but ended up with no solution at all.
:-( I can't go ahead without Azure Storage emulator..
I hope somebody here will help.

There may be an issue with the sqllocaldb user database v11.0 during the install.
You need to recreate it (see below).
As far as I'm concerned, my first install attemp left some files in my c:\users[user] directory :
WAStorageEmulatorDb30.mdf
WAStorageEmulatorDb30_log.ldf
(Your version numbers may differ.) The sqllocaldb logs would mention these files still existed and it would not erase them.
I just deleted them manually.
Recreated the v11.0:
sqllocaldb stop v11.0
sqllocaldb delete v11.0
sqllocaldb create v11.0
And reinstalled.

For those who has new Azure Storage Emulator 4.5 and SQL Server 2016. As MWood mentioned, check c:\users[UserProfile] directory and delete any AzureStorage* databases found.
Then open command window and write same commands, but change database to V13 (the number depends on the SQL server database version installed on your machine).
sqllocaldb stop v13.0
sqllocaldb delete v13.0
sqllocaldb create v13.0
Then install Azure SDK tools again.

I had this problem too. But I solved it with it:
Programs and Features
Selected Visual Studio 2015
Selected "Change -> Modify"
Checked "Microsoft SQL Server Data Tool" and Click "Install"

This didn't work for me. I'm using Parallels on OSX and have an automatic "network profile" with a long path name for my desktop and download folders. Parallels does this automatically
Another solution that worked for me:
Manually download the MSI referenced in the error log
Create a new LOCAL username (not passport/LiveID connected)
Install the MSI from C:\ NOT downloads (where Parallels is backing it as a UNC)
I think it's hitting a 255 char limitation in Windows UNCs'

To keep my laptop responsive during startup, I have changed the sqlserver (express) service startup to manual during its installation. Emulator failed without any error that sql server is not running. On seeing this question, I realized to start the sql server service and then, the installation (emulator 3.2) wen through.

I was able to resolve this problem for myself by running:
"C:\Program Files\Microsoft SQL Server\110\Tools\Binn\SqlLocalDB.exe" create MSSQLLocalDB
Simple but effective.

Related

LocalDB does not starts correctly for IIS worker process

When I deployed MVC application on IIS then localDB databse is not starting correctly. Error message is as follows:
Windows API call WaitForMultipleObjects returned error code: 575. Windows system error message is: {Application Error}
The application was unable to start correctly (0x%lx). Click OK to close the application.
Reported at line: 3621.
But the localDB is working fine with visual studio application and with sqlserver management studio. I already have restarted it and recreated it by command prompt to make it work. But nothing is working. The problem came when i re installed IIS in my machine.
How can i fix this. Any help will be appreciated.
Simply delete all files in "C:\Users\MYUSERNAME\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0" folder. Give write permissions to v11.0 folder. If you can't create another instance give write permission to Instances folder.

Failed to initialize Windows Azure storage emulator.Unable to start the storage emulator

Whyle starting cloud application (Azure storage emulator v 2.3) I got error:
Failed to initialize Windows Azure storage emulator
I have used this to configure sql express for this purpose and I was able to create database - WAStorageEmulatorDb32. But still got above error. Any idea? Thanks.
Edit
Here is what I get when started storage emulator with -inprocess option:
I encountered similar issues when updating to v2.5. I tried everything outlined in the various blogs and technet forums with no luck but it seems like the advice given was correct, just slightly different for my case.
Uninstall all previous version of azure sdks
Optional and probably not related to fixing my issue. I uninstalled all azure sdks, authoring tools, azure tools for VS, azure libraries for .Net, storage emulators and compute emulators.
Delete WAStorageEmulatorDb files
Next up was to clean up any previous WAStorageEmulator database files. For most users these appear to be kept in c:\users\{user}\WAStorageEmulatorDb*.*.
sqllocaldb stop v11.0
sqllocaldb delete v11.0
manually delete c:\users\{user}\WAStorageEmulatorDb*.*
sqllocaldb create v11.0
At this point reinstalling Azure SDK 2.5 via Web Platform Installer failed to install with the following error.
CAQuietExec: Windows Azure Storage Emulator 3.0.0.0 command line tool
CAQuietExec: Error: Cannot create database.
CAQuietExec: Error 0xfffffff3: Command line returned an error.
CAQuietExec: Error 0xfffffff3: CAQuietExec Failed
This is where I noticed my environment was different. Running sqllocaldb info I noticed I had 4 instances, V11.0, two instances which hosted personal databases and a 4th one called MSSQLLocalDB. If you open (localdb)\MSSQLLocalDB in Visual Studio - SQL Server Object Explorer you should should see WAStorageEmulatorDb. The problem for me was that my WAStorageEmulatorDb wasn't being stored in v11.0 as it was for other people, so deleting v11.0 didn't help.
Delete WAStorageEmulatorDb files again. So now that I knew where my WAStorageEmulatorDb was, I re-ran the following
sqllocaldb stop MSSQLLocalDB
sqllocaldb delete MSSQLLocalDB
sqllocaldb create MSSQLLocalDB
Re-install Azure SDK 2.5 via Web Platform Installer completed successfully.
Lastly, running c:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\WAStorageEmulator.exe init followed by c:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\WAStorageEmulator.exe start started successfully.
To verify you should also have new c:\users\{user}\WAStorageEmulatorDb34.* files.
I hope this helps someone who comes across this in the future.
I had a similar problem.
Refer Azure storage emulator failed to initialize for the solution.
It solved my problem.
I hope this helps you.

Windows store app deployment error

I just downloaded and installed Visual studio on my computer (windows 8.1) to start building windows 8 apps. The problem is when I try to run any application this error message shows up (the application from this error message is called Parcels.comStarter):
Error 1 Error : DEP0700 : Registration of the app failed. Deployment
Register operation on Package
a783768f-d79c-495b-bf64-e59e4297fb42_1.0.0.0_neutral__1mfyfctfxa0tr
from:
(d:\Gebruikers\wardv_000\Downloads\Parcels.comStarter\Parcels.comStarter\Parcels.com\bin\Debug\AppX\AppxManifest.xml)
failed with error 0x8E5E0530. See
http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app
deployment issues. (0x80073cf9) Parcels.com
I searched the entire internet but I didn't found a solution. I also did reinstall visual studio and I still have the problem.
Thanks in advance
Open the Services management console (services.msc) and stop the Windows Installer service.
In Windows Explorer, go to C:\ProgramData\Microsoft\Windows\AppRepository\ and rename PackageRepository.edb to PackageRepository.edb.backup.
Back in the management console, restart the Windows Installer service.
Now run Visual Studio as an administrator and open your project.
I was having this exact same problem, and the solution for me was to unlink my Windows account from my Microsoft account.
There are a couple of things to try.
Run WSReset (press [Win] then type wsreset)
Delete the metastore and remotemetastore folder here: C:\Users\%userprofile%\AppData\Local\Microsoft\Windows\SettingSync where %userprofile% is your username. (I suggest just renaming them to metastore.old and remotemetastore.old)
Make sure that there are no staged packages for the app in question.
If you re-deployed an app that was already installed by some other user, then you would get a deployment error. This should wear off if you change the identity in your package.appxmanifest fie.
You should try an OS refresh. You should not lose your apps and settings.
After that re-link your windows account to microsoft account.
If that doesnt work...The problem may be that visual studio is not able to delete the application data in local folder. So when you go in the location C:\Users\UserName\AppData\Local\Packages you will find application data of app installed in your computer, now you need to find your app's application data and delete the folder. The folder name is the same as the package family name which you can see in your solution.
now again open the solution and rebuild and your app will run. (hopefully)
close visual studio and simulator before deleting the folder.
make sure that your account is set as administrator.
I had the same problem with visual studio running under Parallels VM. The solution was to copy the project from a cloud based directory to a local directory.

Azure cloud publish not uploading new files

I've recently copied my visual studio 2010 website project from my windows 7 PC to a new PC running windows 8. That all went relatively smoothly. When I now publish or package the cloud project it only packages files that were originally on the windows 7 PC. Any files that I have created on the windows 8 PC are ignored. The solution builds fine and I can run and debug the project fine. Any ideas?
Not sure why that would be, but here's something to try: In Visual Studio Solution Explorer, right-click the solution and choose Clean Solution. Then try to package/publish again.
When you say files do you mean images/JavaScript?
What is the setting of the "Copy to Output Directory" ? for the files/content that is not making it...make sure it is NOT set to "Do not copy"
Are you using the new v1.8 of the SDK? (did you upgrade your project?)...this can happen if you are using an old SDK from a previous computer and then try to build stuff using a "fresh installation".
The issue was that somewhere along the way the cloud project got disassociated with the web project so wasn't actually updating the file list for publishing - it was just using the file list that had already been generated on my old PC.
The fix was to scrap the cloud project and start over with a new one, then add a new web role to it and then convert that web role into a web application project and then move my whole existing website into that...

Windows Azure Tools: Warning: Unable to delete directory

Anyone know the solution for this? Using the latest version of Azure tools and every time I do a build I see these messages in the output window:
Windows Azure Tools: Warning: Unable to delete directory APPROOT.
Windows Azure Tools: Warning: Unable to delete directory WEBUX.
Windows Azure Tools: Warning: Unable to delete directory APPROOT.
Angela, it is very much possible that an application has open handle to these folders and build process could not delete the folder/files so it can update with new binaries. This problem is specific to your machine, not Windows Azure.
If you could not figure out which application is using, what you could do is restart your machine so you know none of any application is using and then start Visual Studio and clean/rebuild your application and see if you still see this error. If you still see the error, I can provide some other troubleshooting info to help you further.
I ran into this error too. Azure SDK 1.7 added a new way to deliver 'extra' file resources upto the roles. To fix my this error, I manually deleted the folders under the Azure project, Profile roles after exiting VS.
As Avkash mentioned, some app is using your files... a few suggestions that worked for me:
1) Prevent antiviruses from inspecting the build folders
2) Disable Windows search service
3) Disable any auto-backup or auto-sync services that look at build folders
HTH

Resources