azureaccelerators Issue Tracker Rss Feed

Created Issue: unable to connect to instance [1582]

jpmcfeely — Wed, 08 May 2013 19:52:19 GMT

I have created:
- Storage account
- SQL Azure DB
- Hosted Service

I then changed the ServiceConfiguration file in the accelerator and ran the .bat file

All deployed to Azure without error but I am unable to connect to the instance of umbraco in the cloud.

Commented Issue: Umbraco: Deployment Package Logging [534]

mfraiss — Sat, 16 Apr 2011 21:01:24 GMT

Issue: Deployment package .\Logs directory needs to be dynamically created.
Reported By: Warren Buckley
Comments: ** Comment from web user: mfraiss **

It is very important that you implement a dynamically creation of the .\Logs directory. Otherwise the deployment setup process will fail! A workaround is to remove the

-o "%~dp0..\Logs\%dbServerAdmin%.createdatabase.log" Parameters at the end of the three SQL Commands

and it works.

Commented Issue: Umbraco: Creation of SQL Azure Deployment Scripts (Help or Walkthrough) [536]

ryanmar — Sun, 30 Jan 2011 23:11:46 GMT

Issue:
Rapid deployment package contains scripts to dynamically create a new database, create user, set logins, and then update the deployed Umbraco site web.config with new and valid credentials when it is started in Windows Azure. How this is best customized is ambiguous and difficult to follow.
Comments: ** Comment from web user: ryanmar **

This needs to be addressed in documentation and also clarified in the actual configuration files.

For the Umbraco rapid deployment release, the ServiceConfiguration.cscfg file contains a new ConfigurationSetting named "DatabaseConnectionString". The DatabaseConnnectionString needs to include valid SQL Azure administrator credentials in order to provision the new SQL Azure database. (Or have sufficient permissions to create a database, user accounts, and set security and login rights. A valid SQL Azure connection should be similar to:

<Setting name="DatabaseConnectionString"
value="Server=tcp:???.database.windows.net;Database=umbraco;User ID=???@???;Password=???;Trusted_Connection=False;Encrypt=True;" />

SERVER: Full and complete SQL server name. When connecting to SQL Azure this field should always be prepended with tcp: and end with the database.windows.net. An example of a SQL Azure value: tcp:azureserver.database.windows.net.

DATABASE: Name of the database on the SQL server where the application schema has been deployed (or will be deployed during the initial setup). A common choice would be 'umbraco' or a 'customer-name-umbraco' when provisioning customer sites using the scripts.

USER ID, PASSWORD: User account (and password) with access to SQL. When connecting to SQL azure this field must always include @servername following the user login name. An example of a SQL Azure user id value: slalomadmin@azureserver.

ENCRYPT, TRUSTED_CONNECTION: Do not update these two settings.

NOTE 1:
SQL Azure's default firewall settings will block all external networks from access. This includes
other Windows Azure services (even in the same datacenter). Verify or grant other Windows Azure services
and any on-premise system's which require connectivity access by creating the required rules. -->

NOTE 2:
The connection string in the ServiceConfiguration.cscfg will be used to update the web.config of the site
hosted on the clouddrive (VHD) each time the role is redeployed. The database connection string can be
updated at any time.

NOTE 3:
Run the RemoveUmbraco.bat scripts if you wish to restart the deployment process. But be warned, this will
delete both the SQL schema and database as definited in the above ServiceConfiguration.cscfg file's
DatabaseConnectionString value.

Created Issue: Umbraco: Creation of SQL Azure Deployment Scripts (Help or Walkthrough) [536]

ryanmar — Sun, 30 Jan 2011 22:56:48 GMT

Created Feature: Umbraco Rapid Deployment [535]

ryanmar — Sun, 30 Jan 2011 22:50:22 GMT

Issue: Deployment scripts will not overwrite existing cloud drives, solution packages or service definition files.
Reported By: Warren Buckley

Created Issue: Umbraco: Deployment Package Logging [534]

ryanmar — Sun, 30 Jan 2011 22:42:29 GMT

Issue: Deployment package .\Logs directory needs to be dynamically created.
Reported By: Warren Buckley