SQL Connection Error after changing SQL instance name

[Paul-K]

@nickbro

 

Hi Nick,

 

I have installed dirsync for Office 365 today which wanted to install a fresh version of SQL so I took a backup of the HAP database and restored it once dirsync install had complete, the original SQL instance was called SQLEXPRESS, the new one was named automatically by the install as MSONLINE. The restore of the database to MSONLINE has gone fine and all the tables are there but HAP+ won't login, it's showing the below SQL connection error.

 

 

I have added the IIS AppPool to SQL, I have enabled named pipes and tcp/ip for the SQL server and when I type SQLCMD - L in command prompt, the server is in the list, I have also changed the SQL connection in IIS, is there anything I need to change in the HAP files because it already registered itself to another database name or something like that?

 

Your help is appreciated

[fairm010]

Open your web.config file, your SQLConnectionString line should look like this. Did you change the instance name in the web.config?

 

[Paul-K]

@fairm010

 

I didnt change that as I had it set to localhost but I've just changed it now to servername\SQL instance and that's sorted it. Don't suppose you know why I can't use localhost now thought? Does it need to have an alias set for the SQL instance to be set as localhost?

[fairm010]

To be honest I have no idea. I tried using local host but used server \instance as that worked too