Hi,
I’m attempting to add an application server to an exisiting farm. However when I run the configuration wizard to connect to the exisiting farm an error is thrown “The database name is not a valid configuration database”…but it is because thats tha database the main WFE connects to!
The ULS logs point to an ‘Unknown SQL error 53…named pipes etc etc’.
- I’m using a SQL alias with a non standard port…the same SQL alias as my SP servers
- Named pipes are enabled on the SQL server
- I’m running the wizard using my SP_Admin, the same account as I’ve always done
- I’ve checked the SP_Admin permissions on SQL…they are correct
- I’ve updated and checked that my SP servers are all running the same version of SP
- I’ve disabled the SQL firewall just in case…no luck.
I’ve spent a silly amount of time trying to figure this one out! If anybody could point me the in the right direction it would hugely appreciated.
Many thanks
Marc
Hi Marc,
Are you able to connect to the Config Db using the UDL? Can you see the Config DB when you use your sql alias?
Have you done the SQL alias both on 32 and 64 bit using the SQL Configuration manager?Can you check if the spelling is correct for your config DB name.
Do you have a different logical name for your Config DB?
Can you share the Log files so we can give you some advice.
have you check the Firewall ports on the New server and compared it with old server?
have you compared the sql alias settings using the SQL Configuration Manager on new server with Old sever?
From my experience it seems you need to add the 32 and 64 bit sql alias. i have this issue before and the sql alias was only applied to the 32 bit and it worked with UDL but the Config wizard was fail. So this thing to work you need to configure alias on both 32 and 64 bit.
http://mmman.itgroove.net/2013/11/03/setting-up-a-sql-server-alias-with-sharepoint-server-2013/
Cheers Qamar,
There was a service stopped but it didn’t make any difference unfortunatley.
I’ve re-entered the credentails of all AppPools but it didn’t make any difference.
The UDL file was something I’d tried already and that connected perfectly ok via the alias thats why this is so baffling.
…I’m stumped with this one!
Hi Marc,
Another few thing you can try is…
Check an AppPool is not stopped. Try providing credentials again inside the apppool.
Ensure the database is accessible by trying to access it from the failing server – try it with a UDL file.
