Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 Import/Export (DTS) and Replication (2000)
 DTSRun error: Not enough storage??

Author  Topic 

timmy
Master Smack Fu Yak Hacker

1242 Posts

Posted - 2004-06-24 : 20:06:45
Hi all,

Having a frustrating problem with a DTS package I'm trying to run.

The error showing is:

Executed as user: AUSDMZ\JobLogin. DTSRun: Cannot create COM Server to load and execute DTS Package. Error -2147024882 (8007000E): Not enough storage is available to complete this operation. Process Exit Code -2147024882. The step failed.

The job in question contains a CmdExec task that calls DTSRun.

I have created a new domain account (JobLogin) with access to the database and the O/S files it needs to read/write.

There is no issue with disk space on the server. The database has been set to automatically grow.

The O/S is Win2k Sp3, Database is v2000 Sp3

Anyone have any ideas?

btw - I tried a google search on the error: There were a few hits on the 'Cannot create COM server' error, but the error number is different and do not mention the storage issue.

TIA,

Tim

nr
SQLTeam MVY

12543 Posts

Posted - 2004-06-24 : 20:33:41
What happens if you use xp_cmdshell from query analyser?

It sounds like it can't load the package which has nothing to do with any database (except maybe msdb).
Try loading and running separately.
http://www.nigelrivett.net/sp_oacreateLoadDTSpackage.html
and see if it fails on the load or execute.

There was something that was fixed by putting in the full path to dtsrun.exe but I don't think it's this error.

Looks like you might have to reinstall dts or maybe mdac or maybe have a permissions problem.



==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

timmy
Master Smack Fu Yak Hacker

1242 Posts

Posted - 2004-06-24 : 21:02:55
Nigel,

Same problem from QA. The jobs run okay from the domain admin accounts, but I'm trying to eliminate this by creating a dedicated account for running these jobs.
So I don't believe it's a DTS problem - there is something screwy with the permissions on the new account that I need to sort.
I have given access to the master and msdb to my new account, but that didn't fix it. Is there any other perm's that I need to set?

btw - Had a look at the script on your site. My package doesn't use Global Variables - can I just omit these lines?


Cheers,

Tim
Go to Top of Page
   

- Advertisement -