View previous topic :: View next topic |
Author |
Message |
hypehuman
Joined: 18 Sep 2013 Posts: 25
|
Posted: Fri Oct 04, 2013 2:41 pm Post subject: Connecting to Azure linked database |
|
|
I'm a dummy when it comes to web development. I'm evaluating ILS and I'm pleased with the features as I have been working with the local development authenication server. I tried to create authentication server on Windows Azure, but I can't get Install.aspx to find my db server. Here are the steps I took:
- Using Infralution License Tracker, created a product and keys
- Added code to my project so that it checks for licenses the way I want it to
- Create an ASP.NET website on Windows Azure
- Uploaded the contents of my computer's C:\Program Files (x86)\Infralution\Licensing System 5\AuthenticationServer into my website's /site/wwwroot directory
- Using Infralution License Tracker, configured the server at the new URL
The authentication server is now active and my program communicates with it, but the database is still on my computer. I want to be able to create keys from multiple computers, so I will attempt to link an Azure SQL database to my website.
- Using the Azure web interface, created a new SQL database
- Linked the database to the website
- Navigated to /Install.aspx on the website
- Chose "SQL Server" and clicked "Next>>"
- Entered parameters on the "SQL Server Database Configuration" page that appeared:
- Server: a 10-digit alphanumeric string that I got from the "SQL Databases" tab of the Azure web portal
- Database Name: the name that I gave to the database when I created it
- Integrated Security? unchecked
- User ID: the only user ID in the database
- Password: the password I created for that user
- Encrypt Connection Details in Web.Config checked
- Clicked "Next>>"
A red error message appeared at the bottom of the page: Quote: | Connection Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) |
I feel like I'm missing something obvious, but I can't find any support on setting up an ILS authentication server in Azure. Any help would be greatly appreciated. |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Mon Oct 07, 2013 5:39 am Post subject: |
|
|
It sounds like the server name is not correct. It should be a URL. Can you post what it looks like - obviously if you don't want to post the full path you can change it to protect that. _________________ Infralution Support |
|
Back to top |
|
|
hypehuman
Joined: 18 Sep 2013 Posts: 25
|
Posted: Tue Oct 08, 2013 4:47 pm Post subject: |
|
|
Thanks for the tip. I found the URL by navigating to the Azure portal's database dashboard and clicking on "Show connection strings". It was <servername>.database.windows.net.
Instead, I now get the following error: Quote: | An unexpected error occurred while installing/upgrading the database. You may need to delete the database and try again.
Error: Tables without a clustered index are not supported in this version of SQL Server. Please create a clustered index and try again. |
This seems to be because of Azure's "Clustered Index Requirement" found at http://msdn.microsoft.com/en-us/library/windowsazure/ee336245.aspx#cir.
Is there a method I can override to force ILS to use clustered indices? Is there a different solution? |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Tue Oct 08, 2013 8:56 pm Post subject: |
|
|
What version of ILS are you installing? The issue of Azure requiring clustered indexes was fixed in Version 5.10.0. If you are using 5.10.0 or 5.10.1 and are still having this problem then can you please contact support@infralution.com and provide details of your database connection so that we can try to create the database for you to see exactly what the issue is.
Note that if you were trying to install an earlier version then you will need to completely delete the database and start again with 5.10.1. _________________ Infralution Support |
|
Back to top |
|
|
hypehuman
Joined: 18 Sep 2013 Posts: 25
|
Posted: Tue Oct 08, 2013 9:42 pm Post subject: |
|
|
I managed to get it to work! I deleted the database that I had created through the Azure portal, and instead created it using the ILS installer (the exe that installs the License Tracker application). |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Wed Oct 09, 2013 8:52 am Post subject: |
|
|
I've checked the code and it looks like there is still a problem installing the standalone Authentication database on SQL Azure. Connecting the Authentication Server directly to the License Tracker database (which you configured using the License Tracker database install wizard) will work around the issue - but it does mean that you will have to use that single database model which may or may not be what you want.
We will try to get a fix for this issue in a release next week. _________________ Infralution Support |
|
Back to top |
|
|
hypehuman
Joined: 18 Sep 2013 Posts: 25
|
Posted: Wed Oct 09, 2013 3:11 pm Post subject: |
|
|
I'm glad I helped you find a bug Fortunately, I do want to use the single database model, provided that the communication between the License Tracker application and the License Tracker database is encrypted (like communications between the Authentication Server and the end user). Is that the case? |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
|
Back to top |
|
|
hypehuman
Joined: 18 Sep 2013 Posts: 25
|
|
Back to top |
|
|
hypehuman
Joined: 18 Sep 2013 Posts: 25
|
Posted: Mon Nov 04, 2013 6:11 pm Post subject: |
|
|
Note to future users: when using a cloud-based server, be sure to UNCHECK the "Encrypt Connection Details in Web.Config" option on the Install.aspx page. The encryption key is specific to the machine it was installed on, and since cloud-based servers can change machines, encrypting the connection details will cause your authentication service to become unresponsive every few days. |
|
Back to top |
|
|
|