DTS 2000 Package Error(s)

From MS SQL Server Management Studio 2005, I register and connect to MS SQL 2000 (SP4) running on another server. I can see the list of 2000 DTS packages on the other server, but when I try to open them I first get:

Error Source : Microsoft Data Transfformation Services (DTS) Package

Error Description : The DTS host failed to load or save the package properly.

I click the OK button and get:

The selected package cannot be opened. The DTS Desiger has been closed.

I click this OK button and get to now famous:

SQL Server 2000 DTS Designer components are required to edit DTS packages. Install the special Web download, "SQL Server 2000 DTS Designer Components" to use this feature. (Microsoft.SqlServer.DtsObjectExplorerUI)

I have already been to the Feature Pack for Microsoft SQL Server 2005 - November 2005 page and installed the Microsoft SQL Server 2005 Backward Compatibility Components and the Microsoft SQL Server 2000 DTS Designer Components.

Now, the DTS Designer does not close. It stays open. I can see inside the package, but all I see are the transformation lines and the precedence lines. The icons are invisable. If I click on the invisable icons, at the end of the lines, an icon appears. This is not a normal icon. It looks like little windows with a blue border and title bar. Nothing I've seen before. Oh it gets better. If I now double-click the icons, the properties window appear as normal. Looks good... I don't need to change anything. I then press the OK button and get the Task references, like I modified the connection. I do not clear the trasformation. I just click the OK and like magic the connection icon looks at it should. This works on everthing I've tried, except for Execute SQL Task icons. I can save it, but not as the save name. I can open the new saved package. It look and works fine.

So whats up?

I am having the same issues (same errors, etc). DTS Designer 2000 will open a 2000 package that has been saved to a SQL 2005 Server SP1 (9.00.2153.00) in the sysdtspackges table, but will not work with a SQL 2000 Server SP4 (8.00.2185). We are running with all the latest service packs and hotfixes for both environments. As far as I can tell, DTS Designer 2000 is not backward compatible, which is an issue for the 450+ DTS 2000 Packages that cannot be converted to SSIS easily. It appears to me that our DBA team will need to keep both the 2000 and 2005 clients installed to support Legacy systems because of this.|||

Scott5 wrote:

From MS SQL Server Management Studio 2005, I register and connect to MS SQL 2000 (SP4) running on another server. I can see the list of 2000 DTS packages on the other server, but when I try to open them I first get:

Error Source : Microsoft Data Transfformation Services (DTS) Package

Error Description : The DTS host failed to load or save the package properly.

I click the OK button and get:

The selected package cannot be opened. The DTS Desiger has been closed.

I click this OK button and get to now famous:

SQL Server 2000 DTS Designer components are required to edit DTS packages. Install the special Web download, "SQL Server 2000 DTS Designer Components" to use this feature. (Microsoft.SqlServer.DtsObjectExplorerUI)

I have already been to the Feature Pack for Microsoft SQL Server 2005 - November 2005 page and installed the Microsoft SQL Server 2005 Backward Compatibility Components and the Microsoft SQL Server 2000 DTS Designer Components.

Now, the DTS Designer does not close. It stays open. I can see inside the package, but all I see are the transformation lines and the precedence lines. The icons are invisable. If I click on the invisable icons, at the end of the lines, an icon appears. This is not a normal icon. It looks like little windows with a blue border and title bar. Nothing I've seen before. Oh it gets better. If I now double-click the icons, the properties window appear as normal. Looks good... I don't need to change anything. I then press the OK button and get the Task references, like I modified the connection. I do not clear the trasformation. I just click the OK and like magic the connection icon looks at it should. This works on everthing I've tried, except for Execute SQL Task icons. I can save it, but not as the save name. I can open the new saved package. It look and works fine.

So whats up?

Hi, i was getting the same problem until i read http://support.microsoft.com/?kbid=917406

Method 1

Warning The following information contains steps to modify a file. Make sure that you back up the file before you modify it.

1.

Open the SQLInstall:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE folder.
Note SQLInstall is a placeholder for the drive where SQL Server 2005 is installed.

2.

Open the Sqlwb.exe.manifest file in Notepad or in another text editor.

3.

Remove the following lines of code from the Sqlwb.exe.manifest file.

<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity>
</dependentAssembly>
</dependency>

4.

Save the changes, and then exit Notepad or the text editor.

5.

Try to modify the SQL Server 2000 DTS package in SQL Server 2005.

It works for SQL Server Management Studio 2005, but in VS 2005 it doesn't work, you must change also:

devenv.exe.manifest

dexplore.exe.manifest

vsaenv.exe.manifest

VSLauncher.exe.manifest

to make VS 2005 able to open all DTS 2000 packages.

If you still get

SQL Server 2000 DTS Designer components are required to edit DTS packages. Install the special Web download, "SQL Server 2000 DTS Designer Components" to use this feature. (Microsoft.SqlServer.DtsObjectExplorerUI)

try:

1.- Uninstall Microsoft SQL Server 2005 Backward Compatibility Components

2.- Uninstall SQL Server 2000 DTS Designer components

1.- Install Microsoft SQL Server 2005 Backward Compatibility Components

2.- Install SQL Server 2000 DTS Designer components

|||I just finished fixing this issue on my computer.
I am running WinXP with SQL Server 2005 Client tools.
I am connecting to a Win2k server with SQL Server 2000.
I had to do the uninstall first, then reinstall, then file edit.
1. Uninstall Microsoft SQL Server 2005 Backward Compatibility Components
2. Uninstall SQL Server 2000 DTS Designer Components
3. Install Microsoft SQL Server 2005 Backward Compatibility Components
4. Install SQL Server 2000 DTS Designer Components
5. Open the sqlwb.exe.manifest file under [drive]:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE
6. Remove <dependency><dependentAssembly><assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity></dependentAssembly></dependency>

What a pain in the neck!
|||

Scratch that.

Almost immediately after I got it fixed, it stopped working again.
I checked the file to see if it had been rewritten, but it hadn't.
I closed SQL Management Studio and reopened.
It worked! ?
Now, it just seems to randomly work and not work.
What the heck is going on?

|||

Kerry Wano wrote:

Scratch that.

Almost immediately after I got it fixed, it stopped working again.
I checked the file to see if it had been rewritten, but it hadn't.
I closed SQL Management Studio and reopened.
It worked! ?
Now, it just seems to randomly work and not work.
What the heck is going on?

You might want to take this to the DTS forum as this forum focuses on SSIS.
http://groups.google.com/group/microsoft.public.sqlserver.dts/topics?lnk=srg

DTS 2000 Package Error(s)

From MS SQL Server Management Studio 2005, I register and connect to MS SQL 2000 (SP4) running on another server. I can see the list of 2000 DTS packages on the other server, but when I try to open them I first get:

Error Source : Microsoft Data Transfformation Services (DTS) Package

Error Description : The DTS host failed to load or save the package properly.

I click the OK button and get:

The selected package cannot be opened. The DTS Desiger has been closed.

I click this OK button and get to now famous:

SQL Server 2000 DTS Designer components are required to edit DTS packages. Install the special Web download, "SQL Server 2000 DTS Designer Components" to use this feature. (Microsoft.SqlServer.DtsObjectExplorerUI)

I have already been to the Feature Pack for Microsoft SQL Server 2005 - November 2005 page and installed the Microsoft SQL Server 2005 Backward Compatibility Components and the Microsoft SQL Server 2000 DTS Designer Components.

Now, the DTS Designer does not close. It stays open. I can see inside the package, but all I see are the transformation lines and the precedence lines. The icons are invisable. If I click on the invisable icons, at the end of the lines, an icon appears. This is not a normal icon. It looks like little windows with a blue border and title bar. Nothing I've seen before. Oh it gets better. If I now double-click the icons, the properties window appear as normal. Looks good... I don't need to change anything. I then press the OK button and get the Task references, like I modified the connection. I do not clear the trasformation. I just click the OK and like magic the connection icon looks at it should. This works on everthing I've tried, except for Execute SQL Task icons. I can save it, but not as the save name. I can open the new saved package. It look and works fine.

So whats up?

I am having the same issues (same errors, etc). DTS Designer 2000 will open a 2000 package that has been saved to a SQL 2005 Server SP1 (9.00.2153.00) in the sysdtspackges table, but will not work with a SQL 2000 Server SP4 (8.00.2185). We are running with all the latest service packs and hotfixes for both environments. As far as I can tell, DTS Designer 2000 is not backward compatible, which is an issue for the 450+ DTS 2000 Packages that cannot be converted to SSIS easily. It appears to me that our DBA team will need to keep both the 2000 and 2005 clients installed to support Legacy systems because of this.|||

Scott5 wrote:

From MS SQL Server Management Studio 2005, I register and connect to MS SQL 2000 (SP4) running on another server. I can see the list of 2000 DTS packages on the other server, but when I try to open them I first get:

Error Source : Microsoft Data Transfformation Services (DTS) Package

Error Description : The DTS host failed to load or save the package properly.

I click the OK button and get:

The selected package cannot be opened. The DTS Desiger has been closed.

I click this OK button and get to now famous:

SQL Server 2000 DTS Designer components are required to edit DTS packages. Install the special Web download, "SQL Server 2000 DTS Designer Components" to use this feature. (Microsoft.SqlServer.DtsObjectExplorerUI)

I have already been to the Feature Pack for Microsoft SQL Server 2005 - November 2005 page and installed the Microsoft SQL Server 2005 Backward Compatibility Components and the Microsoft SQL Server 2000 DTS Designer Components.

Now, the DTS Designer does not close. It stays open. I can see inside the package, but all I see are the transformation lines and the precedence lines. The icons are invisable. If I click on the invisable icons, at the end of the lines, an icon appears. This is not a normal icon. It looks like little windows with a blue border and title bar. Nothing I've seen before. Oh it gets better. If I now double-click the icons, the properties window appear as normal. Looks good... I don't need to change anything. I then press the OK button and get the Task references, like I modified the connection. I do not clear the trasformation. I just click the OK and like magic the connection icon looks at it should. This works on everthing I've tried, except for Execute SQL Task icons. I can save it, but not as the save name. I can open the new saved package. It look and works fine.

So whats up?

Hi, i was getting the same problem until i read http://support.microsoft.com/?kbid=917406

Method 1

Warning The following information contains steps to modify a file. Make sure that you back up the file before you modify it.

1.

Open the SQLInstall:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE folder.
Note SQLInstall is a placeholder for the drive where SQL Server 2005 is installed.

2.

Open the Sqlwb.exe.manifest file in Notepad or in another text editor.

3.

Remove the following lines of code from the Sqlwb.exe.manifest file.

<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity>
</dependentAssembly>
</dependency>

4.

Save the changes, and then exit Notepad or the text editor.

5.

Try to modify the SQL Server 2000 DTS package in SQL Server 2005.

It works for SQL Server Management Studio 2005, but in VS 2005 it doesn't work, you must change also:

devenv.exe.manifest

dexplore.exe.manifest

vsaenv.exe.manifest

VSLauncher.exe.manifest

to make VS 2005 able to open all DTS 2000 packages.

If you still get

SQL Server 2000 DTS Designer components are required to edit DTS packages. Install the special Web download, "SQL Server 2000 DTS Designer Components" to use this feature. (Microsoft.SqlServer.DtsObjectExplorerUI)

try:

1.- Uninstall Microsoft SQL Server 2005 Backward Compatibility Components

2.- Uninstall SQL Server 2000 DTS Designer components

1.- Install Microsoft SQL Server 2005 Backward Compatibility Components

2.- Install SQL Server 2000 DTS Designer components

|||I just finished fixing this issue on my computer.
I am running WinXP with SQL Server 2005 Client tools.
I am connecting to a Win2k server with SQL Server 2000.
I had to do the uninstall first, then reinstall, then file edit.
1. Uninstall Microsoft SQL Server 2005 Backward Compatibility Components
2. Uninstall SQL Server 2000 DTS Designer Components
3. Install Microsoft SQL Server 2005 Backward Compatibility Components
4. Install SQL Server 2000 DTS Designer Components
5. Open the sqlwb.exe.manifest file under [drive]:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE
6. Remove <dependency><dependentAssembly><assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity></dependentAssembly></dependency>

What a pain in the neck!
|||

Scratch that.

Almost immediately after I got it fixed, it stopped working again.
I checked the file to see if it had been rewritten, but it hadn't.
I closed SQL Management Studio and reopened.
It worked! ?
Now, it just seems to randomly work and not work.
What the heck is going on?

|||

Kerry Wano wrote:

Scratch that.

Almost immediately after I got it fixed, it stopped working again.
I checked the file to see if it had been rewritten, but it hadn't.
I closed SQL Management Studio and reopened.
It worked! ?
Now, it just seems to randomly work and not work.
What the heck is going on?

You might want to take this to the DTS forum as this forum focuses on SSIS.
http://groups.google.com/group/microsoft.public.sqlserver.dts/topics?lnk=srg

DTS 2000 Package Error(s)

From MS SQL Server Management Studio 2005, I register and connect to MS SQL 2000 (SP4) running on another server. I can see the list of 2000 DTS packages on the other server, but when I try to open them I first get:

Error Source : Microsoft Data Transfformation Services (DTS) Package

Error Description : The DTS host failed to load or save the package properly.

I click the OK button and get:

The selected package cannot be opened. The DTS Desiger has been closed.

I click this OK button and get to now famous:

SQL Server 2000 DTS Designer components are required to edit DTS packages. Install the special Web download, "SQL Server 2000 DTS Designer Components" to use this feature. (Microsoft.SqlServer.DtsObjectExplorerUI)

I have already been to the Feature Pack for Microsoft SQL Server 2005 - November 2005 page and installed the Microsoft SQL Server 2005 Backward Compatibility Components and the Microsoft SQL Server 2000 DTS Designer Components.

Now, the DTS Designer does not close. It stays open. I can see inside the package, but all I see are the transformation lines and the precedence lines. The icons are invisable. If I click on the invisable icons, at the end of the lines, an icon appears. This is not a normal icon. It looks like little windows with a blue border and title bar. Nothing I've seen before. Oh it gets better. If I now double-click the icons, the properties window appear as normal. Looks good... I don't need to change anything. I then press the OK button and get the Task references, like I modified the connection. I do not clear the trasformation. I just click the OK and like magic the connection icon looks at it should. This works on everthing I've tried, except for Execute SQL Task icons. I can save it, but not as the save name. I can open the new saved package. It look and works fine.

So whats up?

I am having the same issues (same errors, etc). DTS Designer 2000 will open a 2000 package that has been saved to a SQL 2005 Server SP1 (9.00.2153.00) in the sysdtspackges table, but will not work with a SQL 2000 Server SP4 (8.00.2185). We are running with all the latest service packs and hotfixes for both environments. As far as I can tell, DTS Designer 2000 is not backward compatible, which is an issue for the 450+ DTS 2000 Packages that cannot be converted to SSIS easily. It appears to me that our DBA team will need to keep both the 2000 and 2005 clients installed to support Legacy systems because of this.|||

Scott5 wrote:

From MS SQL Server Management Studio 2005, I register and connect to MS SQL 2000 (SP4) running on another server. I can see the list of 2000 DTS packages on the other server, but when I try to open them I first get:

Error Source : Microsoft Data Transfformation Services (DTS) Package

Error Description : The DTS host failed to load or save the package properly.

I click the OK button and get:

The selected package cannot be opened. The DTS Desiger has been closed.

I click this OK button and get to now famous:

SQL Server 2000 DTS Designer components are required to edit DTS packages. Install the special Web download, "SQL Server 2000 DTS Designer Components" to use this feature. (Microsoft.SqlServer.DtsObjectExplorerUI)

I have already been to the Feature Pack for Microsoft SQL Server 2005 - November 2005 page and installed the Microsoft SQL Server 2005 Backward Compatibility Components and the Microsoft SQL Server 2000 DTS Designer Components.

Now, the DTS Designer does not close. It stays open. I can see inside the package, but all I see are the transformation lines and the precedence lines. The icons are invisable. If I click on the invisable icons, at the end of the lines, an icon appears. This is not a normal icon. It looks like little windows with a blue border and title bar. Nothing I've seen before. Oh it gets better. If I now double-click the icons, the properties window appear as normal. Looks good... I don't need to change anything. I then press the OK button and get the Task references, like I modified the connection. I do not clear the trasformation. I just click the OK and like magic the connection icon looks at it should. This works on everthing I've tried, except for Execute SQL Task icons. I can save it, but not as the save name. I can open the new saved package. It look and works fine.

So whats up?

Hi, i was getting the same problem until i read http://support.microsoft.com/?kbid=917406

Method 1

Warning The following information contains steps to modify a file. Make sure that you back up the file before you modify it.

1. Open the SQLInstall:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE folder.
Note SQLInstall is a placeholder for the drive where SQL Server 2005 is installed. 2. Open the Sqlwb.exe.manifest file in Notepad or in another text editor. 3. Remove the following lines of code from the Sqlwb.exe.manifest file.

<dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity> </dependentAssembly> </dependency>

4. Save the changes, and then exit Notepad or the text editor. 5. Try to modify the SQL Server 2000 DTS package in SQL Server 2005.

It works for SQL Server Management Studio 2005, but in VS 2005 it doesn't work, you must change also:

devenv.exe.manifest

dexplore.exe.manifest

vsaenv.exe.manifest

VSLauncher.exe.manifest

to make VS 2005 able to open all DTS 2000 packages.

If you still get

SQL Server 2000 DTS Designer components are required to edit DTS packages. Install the special Web download, "SQL Server 2000 DTS Designer Components" to use this feature. (Microsoft.SqlServer.DtsObjectExplorerUI)

try:

1.- Uninstall Microsoft SQL Server 2005 Backward Compatibility Components

2.- Uninstall SQL Server 2000 DTS Designer components

1.- Install Microsoft SQL Server 2005 Backward Compatibility Components

2.- Install SQL Server 2000 DTS Designer components

|||I just finished fixing this issue on my computer.
I am running WinXP with SQL Server 2005 Client tools.
I am connecting to a Win2k server with SQL Server 2000.
I had to do the uninstall first, then reinstall, then file edit.
1. Uninstall Microsoft SQL Server 2005 Backward Compatibility Components
2. Uninstall SQL Server 2000 DTS Designer Components
3. Install Microsoft SQL Server 2005 Backward Compatibility Components
4. Install SQL Server 2000 DTS Designer Components
5. Open the sqlwb.exe.manifest file under [drive]:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE
6. Remove <dependency><dependentAssembly><assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity></dependentAssembly></dependency>

What a pain in the neck!
|||

Scratch that.

Almost immediately after I got it fixed, it stopped working again.
I checked the file to see if it had been rewritten, but it hadn't.
I closed SQL Management Studio and reopened.
It worked! ?
Now, it just seems to randomly work and not work.
What the heck is going on?

|||

Kerry Wano wrote:

Scratch that.

Almost immediately after I got it fixed, it stopped working again.
I checked the file to see if it had been rewritten, but it hadn't.
I closed SQL Management Studio and reopened.
It worked! ?
Now, it just seems to randomly work and not work.
What the heck is going on?

You might want to take this to the DTS forum as this forum focuses on SSIS.
http://groups.google.com/group/microsoft.public.sqlserver.dts/topics?lnk=srg

DTS 2000 Migration Issue

Hi ,
I am trying to Migrate DTS 2000 package to SQL 2005.

I am opening the wizard form SQL Server Management Studio>Object Explorer>Management->Legacy->DTS ->Migration Wizard .

when i run the wizard with source location than folder destination .

In the third step of the wizard i am getting an error saying :

This wizard will close because it encountered the following error:

ADDITIONAL INFORMATION:

Index was out of range. Must be non-negative and less than the size of the collection.

Parameter name: index (mscorlib)

Please advice me how to proceed ?

Thank you

Syeda

This is a known issue. See:

http://support.microsoft.com/kb/917420/en-us

DTS & SQL Server Management Studio Express

Can you use the DTS download package to run the DTS Designer from within SQL Server Management Studio Express? I don't seem to be able to get it to show up in SQL Server Management Studio Express after I dnld it.

I do not believe this is possible no.|||

Please post back if you find a way. I was looking for the same thing. This would give us a roundabout deployment option for dtsx packages on sql express, which would would be unbelievably great.

Any ideas why we can't currently redistribute dtsx packages and the new dts runtime? Being able to leverage the wonderful new SSIS package designer to create standalone data transformations would be truly outstanding!

BTW, the inclusion of reporting services and the report builder tool in sql express is just great. Thanks for providing this!

Regards,

Lacan.

DTS

Could you help me with this problem: I have a DTS
executing .bat file and when try to run it in enterprise
management error occurs "The device is not
ready." Other DTSs with SQL queries work fine.I'd guess that DTS is trying to access a physical drive letter that
doesn't exist or isn't mapped. Use UNC paths instead of drive letters
and see if the problem goes away.
--
David Portas
SQL Server MVP
--|||I am using the UNC path
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1121875027.700950.158000@.g43g2000cwa.googlegroups.com...
> I'd guess that DTS is trying to access a physical drive letter that
> doesn't exist or isn't mapped. Use UNC paths instead of drive letters
> and see if the problem goes away.
> --
> David Portas
> SQL Server MVP
> --
>|||docsql wrote:
> I am using the UNC path
> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in
> message news:1121875027.700950.158000@.g43g2000cwa.googlegroups.com...
>> I'd guess that DTS is trying to access a physical drive letter that
>> doesn't exist or isn't mapped. Use UNC paths instead of drive letters
>> and see if the problem goes away.
>> --
>> David Portas
>> SQL Server MVP
>> --
Are you sure the account running the DTS script has access to the UNC
you provide?
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||yes
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:%23At6ZwUjFHA.3540@.TK2MSFTNGP14.phx.gbl...
> docsql wrote:
>> I am using the UNC path
>> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in
>> message news:1121875027.700950.158000@.g43g2000cwa.googlegroups.com...
>> I'd guess that DTS is trying to access a physical drive letter that
>> doesn't exist or isn't mapped. Use UNC paths instead of drive letters
>> and see if the problem goes away.
>> --
>> David Portas
>> SQL Server MVP
>> --
> Are you sure the account running the DTS script has access to the UNC you
> provide?
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com|||Hello,
Similar issue will occur when using the DTS import/Export wizard, select
the option "Copy Objects and data between SQL server databases" and the
script file directory pointing to a wrong drive.
If this is the case, to narrow down the issue, copy the script file to the
local hard drive and recreate a new DTS package to test.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

dtexec Return Success BUT Not Run!

I've created a Maintenance Plan in Microsoft SQL Server Management Studio (Sql Server 2005 SP2 + Windows Updates) and currently trying to execute it via the dtexec command line program.

The problem is that it reports that it executed the Maintenance Plan but it never actually executes the Plan. The data isn't updated and the CPU and hard drive I/O reports nothing happening.

I've checked the argument lists but I don't think I've missed anything...?

On the Sql Machine itself, I run the command line as follows:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\V2Admin>cd \
C:\>dtexec /SQL "\Maintenance Plans\GPI Update" /Server V2SQL\VC2 /User sa /Pass
word XxXxXxX
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.3042.00 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

Started: 11:29:43 AM
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 11:29:43 AM
Finished: 11:29:44 AM
Elapsed: 0.375 seconds

C:\>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>I don't understand why you are running using DTEXEC, have you tried to schedule the package that is created using SSIS?|||We are running DTExec as we want chain together and run other processes outside as Sql Server as well, but want to use the History tracker of Sql Server's Maintenance Plans.

The Sql Server Maintenance Plan tasks are kept with Sql Server and the external processes are kept with their relevant tools.

We need to run both together which is why we need to call DtExec.

At the worst case scenario, we can simply run SqlCmd and execute the desired functionality, but that is asking for problems as there would then be two locations to maintain the Maintenance Tasks Sub-Plans.

Not a smart move in any operations manual!
|||

Schedule a maintenance plan and look at the arguments to dtexec in the agent job step. You will find that the subplan that contains your job steps is enabled from that command line. If you just run a maintenance plan without so enabling the subplans, all are disabled, and nothing runs, as you have confirmed in your scenario.

jkh