I am referring to this article on TechNet, but where you’ve already renamed your server (like when you’ve cloned a VM) and you are unable to connect to SharePoint.
In this case you will be unable to follow the steps in the above article due to the fact that SharePoint cannot access the database. What I did to get around this problem was the following:
- Create a SQL Alias to the old database
- Set the protocol on my Alias to Named Pipes
- Change the order of my protocols so that Named Pipes is before TCP/IP
- Perform an IISRESET /noforce
- Follow the TechNet article and you’re in business
- Delete the Alias and change protocol order back to original configuration
- Reboot your server
No comments yet... Be the first to leave a reply!