Advertisement

04.11.2008 at 10:42AM PDT, ID: 23315919
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.8

Using EMC Retrospect backing up SQL 2005 Database

Asked by skidogg24 in SQL Server 2005, Retrospect Backup Utility

Tags: , ,

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 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 theres 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

Start Free Trial
[+][-]05.01.2008 at 09:54AM PDT, ID: 21480369

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: SQL Server 2005, Retrospect Backup Utility
Tags: Microsoft, Windows 2003 Server, 2003 Enterprise R2 with SP2
Sign Up Now!
Solution Provided By: Kevin3NF
Participating Experts: 1
Solution Grade: A
 
 
[+][-]09.16.2008 at 11:05AM PDT, ID: 22491316

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 7-day free trial to view this Administrative Comment or ask the Experts your question.

 
[+][-]09.20.2008 at 04:09PM PDT, ID: 22532088

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 7-day free trial to view this Administrative Comment or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628