What I can see, I have properly set the connectionstring, added access to the database in Azure and using correct user and password combination.
When connecting to the local database before converting to a bacpac file and uploading to Azure everything went fine.
However, when recreating the bacpac as a Azure database, I received an undefined error. When refreshing the portal the database is however created and seems to be working. I assume the umbracoUser and umbracoServer tables in the database are in conflict here.
Trying to login in to admin/backoffice from Azure DB fails
Hi!
Just created a bacpac-file extension in Azure with an empty Umbraco installation.
When connection to the database in my local project I don't seem to be able to login to the admin backoffice.
I receive the following error message in the console of the browser: http://cgv.local/umbraco/backoffice/UmbracoApi/Authentication/IsAuthenticated 500 (Internal Server Error)
What I can see, I have properly set the connectionstring, added access to the database in Azure and using correct user and password combination. When connecting to the local database before converting to a bacpac file and uploading to Azure everything went fine.
Is there something that I may be missing?
Thanks! / Eric
Not sure which way round you're doing this but to access the DB on Azure you'll need to add your IP address to it's Firewall. ??
Hi, Craig!
Yes, that I have. Which is odd that it doesn't allow me to connect...
Here's the connectionstrin (nothing fancy):
However, when recreating the bacpac as a Azure database, I received an undefined error. When refreshing the portal the database is however created and seems to be working. I assume the umbracoUser and umbracoServer tables in the database are in conflict here.
I've just done this in the last few days. I got an error creating the bacpac file too. I had to set the DB compatability mode to include 2012 I think.
I resolved the issue by creating the Azure database instance in the installation of the Umbraco site.
Directly after the installation was complete the account was able to logon, but not after timeout action occurred.
The status code now returns a 400 when trying to logon to the backoffice.
Strange...
is working on a reply...