none
Azure Storage Emulator - v4.2 Setup Wizard ended prematurely

    Question

  • From Chad

    @c_tolkien via twitter

    "Hey @azuresupport how do I debug this? Have 4.1 installed, can't install 4.2.. completely stuck pic.twitter.com/8EkR9jeul6"

    http://twitter.com/c_tolkien/status/653425049425219584

    Thanks,

    @AzureSupport


    Monday, October 12, 2015 4:28 AM

Answers

  • Our engineer is recommending the following:

    You can use the following process to recover from most init problems involving the database. Note that any data in the emulator currently will be lost.

    Delete the SQL instance:

     

        sqllocaldb stop MSSQLLocalDB

        sqllocaldb delete MSSQLLocalDB

     

    Now delete the database files:

     

        %USERPROFILE%\AzureStorageEmulatorDb*.mdf

        %USERPROFILE%\AzureStorageEmulatorDb*.ldf

     

    Finally, recreate the sql instance:

     

        sqllocaldb start MSSQLLocalDB

     

    Then retry the emulator init.

    Tuesday, October 13, 2015 5:59 PM

All replies

  • Further details via the log file:

    Action start 15:32:48: InstallFinalize.
    CAQuietExec:  Windows Azure Storage Emulator 4.2.0.0 command line tool
    CAQuietExec:  Error: Cannot create database.
    CAQuietExec:  Error 0xfffffff3: Command line returned an error.
    CAQuietExec:  Error 0xfffffff3: CAQuietExec Failed
    CustomAction RunInitialize returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    Edit: Which makes no sense, I can see that the database has been created when I jump on the localdb instance.

    • Edited by Chad__T Monday, October 12, 2015 4:44 AM
    Monday, October 12, 2015 4:35 AM
  • Our engineer is recommending the following:

    You can use the following process to recover from most init problems involving the database. Note that any data in the emulator currently will be lost.

    Delete the SQL instance:

     

        sqllocaldb stop MSSQLLocalDB

        sqllocaldb delete MSSQLLocalDB

     

    Now delete the database files:

     

        %USERPROFILE%\AzureStorageEmulatorDb*.mdf

        %USERPROFILE%\AzureStorageEmulatorDb*.ldf

     

    Finally, recreate the sql instance:

     

        sqllocaldb start MSSQLLocalDB

     

    Then retry the emulator init.

    Tuesday, October 13, 2015 5:59 PM
  • What Ananda has recommended is usually the fix for Storage Emulator installation issues. Let us know if this is not the case.
    Friday, October 16, 2015 6:45 PM
    Moderator
  • Worked like a charm for me! Thanks ;-)
    Wednesday, December 16, 2015 2:39 PM