The default credentials should work. What credentials are you using?

You can also add AutoMigrateEPiServer to appSettings with value = true, so it will migrate automatically for you. Once it's done you can access the site as normal

Hi Quan,

I am using admin@example.com/store. as credentials. Those are wrong credentials, according to quicksilver.

Adding AutoMigrateEPiServer to appSettings in web.config does nothing.

I was using this guide https://world.episerver.com/documentation/developer-guides/commerce/deployment/deploying-commerce-to-azure-web-apps/

but it is not very good. Should I do the process for all projects in quicksilver? For Manager and for Shared?

There was no information that I should add two databases to azure. It is obvious after the fact, but not when doing this for the first time.

Among other things.

Is there a way to completely turn off credentials validation in quicksilver? Just to finish this process? I have changed authorisation nodes to allow users="*" but that did nothing.

Is there a way to check what exactly is goig on at this state of the site initialisation process? Should I check for some specific rows of data in the database? Should the dbo_MigrationHistory table contain someting else than InitialCreate? Where could I find logs from Update-EpiDatabase script? Are thre any?

I am really stuck here. I dont know what is going on, What went wrong and what went right.

I have managed to get it to work!

I have deleted existing databases for commerce and cms and recreated them in azure.

I have added two scripts for updating databases to publish settings.

I have added my IP to azure Firewall and have run Update-EPiDatabase

After that the site is still stuck on login page.

So I have added

<authorization>
<allow users="*"/>
</authorization>

to manager web.config and moved the same piece of code in Site web.config to the top most position. And I have changed

<authentication mode="None">

to

<authentication mode="Forms">

And that gave me a 502 error after one more publish. But after a refresh I finally have clean Quicksilver with content.

But now I cannot login to the dashboard. Any credentials I enter are incorrect.

I have added admin user:

but still, Quicksilver is adamant that this user does not exist.

Did someone managed to install this Quicksilver on azure with any success? I could really use some pointers here.

There is a script (SetupDatabases.cmd) file that should be run to populate Quicksilver database when running on eg local server. 

There are also two scripts for two databases in packages.

When installing in local environment, after running SetupDatabases.cmd everything is ok, commerce database is populated and admin@example.com.

can be used to login to the dashboard.

But when using the two scripts from packages, when installing on the azure servers, this user does not exists and logging in is not possible.

Should I run the first script on azure server? Is this even possible?

I think I have figured it out. It is really obvious now, but wasn't at the beggining, when I did not know what was really happening. Also, the decumentation should be a bit more precise. For example what resources need to be added to azure for the manager part and waht can be shared between the two.

There are three procedures in the SetupDatabases.cmd: Create cms database, create commerce database and creating users for it.

The documentation states that I should add two scripts to the deploy setup, both create databses, ommitting the step responsible for user creation. So add the aspnet_identity.sql file to the commerce database in the database updates setting and do it after the database creation script.