CRM 4 Move to new server still looks for old server

(0) Share

Report

Posted on by Robert Hanlon

135

I just moved our CRM 4 application to a new 64bit server. Moved to same domain, same db so setup was a snap; just install on new box and choose existing database. After setup completed, removed server from server list in Deployment Manager.

Several customizations are failing because it is still trying to connect to the old server. Confirmed by writing a simple C# app to connect to the CrmDiscoveryService to return both MetaDataServerURL and CrmServiceUrl; both return the old server URL.

I tried to open a ticket with MS CustomerSource but they say thay can't help with SDK issues. Great!

Anyone have a suggestion? How do I strip out the old server and make sure any references are returned to the new server?

Setup environment info:

IIS Server: Windows 2003 R2 x64, CRM 4 On-Premis w/Rollup 2 applied

DB Server; Windows 2003 R2 x64, SQL2005 x64

*This post is locked for comments

I have the same question (0)

All responses (1)

Answers (0)

Brett Davis 45 on at

Like (0)

Report
Robert,

I suspect that the issue may be with your config database. If I understand your issue correctly I would suggest you do the following:

Backup all of the %_MSCRM databases on your SQL server

Uninstall MSCRM completely, being sure to delete the orphaned folders and databases from SQL.

Reinstall CRM + Rollups as per normal and just create a temp organisation, but make sure you delete the organisation in your deployment manager afterward(or install using a setup xml file to omit the organisation creation if you know how)

Restore your organisation_MSCRM database back in to SQL (But not the MSCONFIG database)

In Deployment Manager import an organisation - it should pick up the db in SQL.

The user mapping wizard should then come up - be sure to tell it to do nothing with the users as the GUID's wont be changing.

And that as they say, should be that.

Was this reply helpful? Yes No