Recently we implemented a new terminal server that runs Great Plains 10.0 and running SQL 2005 w/ SP2 on there as well. I want to backup our SQL Server using EMC Retrospect and I already have the agent installed on there. Originally we had an old terminal server running older versions of Great Plains and SQL 2000 so we since then upgraded and migrated on a new piece of hardware. Anyways originally during the migration, we had the old terminal server and new terminal server online at the same time:
Old Terminal Server Name = TS2003 New Terminal Server Name = TS2003-NEW
So when the guy was doing our migration, he installed SQL and Great Plains with the TS2003-NEW machine name although our plan was to change it to TS2003 after the migration was complete and the old TS2003 was decommissioned. Once the old one was put out of production, we changed the machine name of the new terminal server to TS2003. The problem occurs when I try to backup the SQL Server, I can license it through Retrospect and it sees there is a DB there although I cannot authenticate with Retrospect either by Windows Authentication or SQL Authentication. We diagnosed the problem referencing the old machine name by clearing the report log, then trying to re-authenticate to the TS2003 and within the error I saw it was trying to reference the machine name TS2003-NEW.
T-2: TWDBSqlServer::Init: Connect() failed [0x80040000]:[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). T-2: TWDBSqlServer::InitDMO: connection failed to instance: 'TS2003NEW', username: 'administrator' vlocQuitHook: DK_DRMODE is false. Exit at 4/10/2008 3:06 PM
Then I figured there's gotta be a reference to TS2003-NEW in the registry so I go into regedt32 and go to find and select everything and searched for TS2003-NEW The following keys referenced TS2003-NEW - HKLM/Software/Microsoft/Microsoft SQL Server/90/Machines o Original Machine Name = TS2003-NEW - HKLM/Software/Microsoft/Services/Report Server o Group Prefix = SQLServer2005ReportUser$TS2003-NEW$ - HKLM/Software/Microsoft/Services/SSIS o Group Prefix = SQLServer2005DTSUser$TS2003-NEW - HKLM/Software/Microsoft/MSSQL Server/Client/SNI9.0/Last Connect o TS2003-NEW = -1040187384:LPC:TS2003-NEW
Any of these keys need to be changed in the registry to fix this issue so the software see's the database under TS2003 name instead of TS2003-NEW?
After changing a machine name if you run the setup again it should detect the change and correct the entries. You may also have to change the entry in sysservers.