FIX: SP2 Regression: DTS Transfer Fails with Access Violation if Destination Server is Unnamed (268413)
The information in this article applies to:
- Microsoft SQL Server 7.0
- Microsoft SQL Server 7.0 Service Pack 2
This article was previously published under Q268413
BUG #: 58148 (SQLBUG_70)
SYMPTOMS
A Data Transformation Services (DTS) package that includes a "Transfer SQL Server Objects" task might fail with an access violation if the destination server is unnamed. If the package is run from the Enterprise Manager the following error message occurs:
Need to run the object to perform this operation.
(SQL-DMO) Code execution exception :
Exception_Access_violation
If you run the package by using the dtsrun utility, the following error message occurs:
DTSRun OnError: Transfer SQL Server Objects, Error = -2147221499
(80040005) "
This problem only applies to Microsoft SQL Server 7.0 Service Pack 2.
CAUSE
The destination does not have the local server name set correctly.
To verify the server name run the following query from Query Analyzer:
select @@servername
If the query returns "Null" the local server name is not set correctly.
WORKAROUND
If the server name exists, but is not identified as the local server, then you must run the following queries to resolve the issue:
sp_dropserver 'servername'
go
sp_addserver 'servername', local
If the server name does not exist you must run the following query to resolve the issue:
sp_addserver 'servername', local
For the name change to become effective, you must stop and restart the SQL Server service.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0.
For more information, click the following article number to view the article in the Microsoft Knowledge Base: 274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
Modification Type: | Major | Last Reviewed: | 3/14/2006 |
---|
Keywords: | kbBug kbfix KB268413 |
---|
|