Article ID: 308801 - Last Review: October 31, 2003 - Revision: 3.2 FIX: DTSRUN Fails with Errors If the Arguments Have Multiple Space Characters Between ThemThis article was previously published under Q308801
BUG #: 355042(SHILOH_BUGS) BIG #: 102083(SQLBUG_70) SYMPTOMS
When you execute a Data Transformation Services (DTS) package from a command line by using Dtsrun.exe, if extra blanks or spaces are present between the package name and the argument that follows, the package execution may fail. The error messages that follow occur even though the package exists at the specified location.
If you save the package you execute through DTSRUN to SQL Server, this error message occurs:
DTSRUN /S "ServerName" /N "parsetest" /E
DTSRun:Loading...
Error: -2147217900 (80040E14);Provider Error: 14262 (37B6)
Error string:The specified DTS Package ('Name = '"parsetest" ';ID.VersionID = {[not specified]}.{[not specified]}') does not exist.
Error source: Microsoft OLE DB Provider for SQL Server
Help file:
Help context: 0
DTSRUN /F "%drive%:\path\parsetest.dts" /E
DTSRun: Loading...
Error: -2147024773 (8007007B); Provider Error: 0 (0)
Error string: The filename, directory name, or volume label syntax is incorrect.
Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts80.hlp Help context: 704 CAUSE
The problem occurs due to incorrect parsing of multiple spaces between the arguments for DTSRUN.
Even though the package exists on your local SQL Server computer or in the location you specify, if there are multiple space characters between the arguments you pass to DTSRUN, the error message occurs. RESOLUTIONTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
290211
(http://support.microsoft.com/kb/290211/EN-US/
)
INF: How to Obtain the Latest SQL Server 2000 Service Pack
WORKAROUND
All the arguments (switches) for the DTSRUN command should have a single space in order to avoid the problem.
STATUSMicrosoft has confirmed that this is a problem in Microsoft SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|

Back to the top
