We are in the process of moving Tridion development in-house. To ensure environments are the same, we have restored a VMWare image of the dev CME server on our own network, and restored databases on our own SQL boxes.
We have applied new licences to match new CME box name, and have changed all the SQL configuration options to reference our own SQL instance.
When browsed the CME site authenticates a user successfully but when loading the left hand content menu it throws a named pipes connection error. Using Fiddler this is associated with a call to the TCM54 service.
We have verified that named pipes is enabled and that the CME IIS can communicate with SQL Server (using MS PortQryv2 and WireShark)...and we're assuming that if it couldn't communicate it wouldn't authenticate the user.
However, Wireshark does show that something is still trying to connect to the SQL Server on the other environment. We have searched config files for references to previous SQL server but drawn a blank.
So the question is where else could a database connection string be configured, and has anyone else had similar issues?