Same here except that I am deploying on a shared hosting.

Hi, might be related, but have you checked file permissions (particularly write access to web.config) ?

Step 3 can fail with "Database connectino initialisation fails" if there are permission issues.

http://umbraco.codeplex.com/workitem/29896

HTH,

Hendy

I guess you are right Henry because I got an error saying "Access denied to the file umbraco.config" when I reverted back to the root url. Giving read/write access rights to the App_Data folder fixed it but I was still stuck with the "Database connection initialisation failed." error on the db config page.

As for the web.config file my hosting control panel at GoDaddy does not allow me to modify permissions for files located in the root folder.

So the solution I guess is to carry out the installation on my localhost before uploading it to the server.

Thanks a lot for your help.

I have the same "Database connection initialisation failed" error. I'm able to connect to my MS SQL database via management studio with same credentials.

/install/?installStep=filepermissions page says my permission settings are perfect though...

I also have the same problem. I looked at the code, and unless I am missing something I cannot understand how this scenario is supposed to work.

In p.aspx.cs.installOrUpgrade:

                m_Installer = sqlHelper.Utility.CreateInstaller();
                if (!m_Installer.CanConnect)
                    throw new Exception("The installer cannot connect to the database.");

The CanConnect property is false as long as CurrentVersion equals the 'Unavailable' version. By looking at the 'DetermineCurrentVersion' code in DefaultInstallerUtility, it looks to me that for a clean db with no umbraco tables, the currentversion will indeed be 'Unavailable', hence the problem to "connect".

        public virtual bool CanConnect
        {
            get { return CurrentVersion != DatabaseVersion.Unavailable; }
        }

Hi,

I can confirm that Umbraco needs to be able to write to the web.config file (I guess to save the connection string there) for the database initialisation to proceed.

I was installing to a MySQL database on GoDaddy and had to set permissions to read/write for it to work (in my case, I set everything to read/write, but I reckon it's only the web.config file and a few other folders that need to be done).

Sine you can't actually set permissons on files with the GoDaddy File Manager, you need to set permissions to the folder containing the web.config file. In my case I was installing to a subfolder so I could set permissions on that sub-folder. If you're installing to the main root however, I wouldn't know how to set write permissions here. Perhaps a call to GoDaddy would help :-|.

Regards,
Wole.

I corrected my installation by editing the connection string in the web.config and then uploaded it to my hosting server. Installation succeeded.

Brian

hi,

in case of Windows 7, IIS7.5 this issue will arise if you don't have the proper authentication set for the "ASP.Net impersonation". I had this set to "Disabled" by default. If you change it to "Enabled" and relaunch the process it should work. (This also applies to the file check issue)

To change this setting in Windows 7, go into IIS manager, select the website you're working on and click the "Authentication" in the "IIS" section. From the list set "ASP.Net impersonation" to "Enabled".

hope this helps,

Jacques.

Hi, I have exactly the same thing:

everything looks fine:

Hello,

I have the same problem with version 4.8 configured on Shared Hosting.

Doen anyone know what to do?

is working on a reply...