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)
 DTS OLE Automation Error

Author  Topic 

cbrochhagen
Starting Member

5 Posts

Posted - 2003-03-03 : 10:50:54
I'm attempting to run a DTS package via OLE Automation in a stored procedure on SQL Server 2000 but am receiving the following error: Not enough storage is available to process this command.

The step in which the error occurs is the following:
-- Create a Pkg Object
EXEC @hr = sp_OACreate 'DTS.Package', @oPKG OUTPUT
IF @hr <> 0
BEGIN
PRINT '*** Create Package object failed'
EXEC dbo.Pro_Display_SQL_Errors @oPKG, @hr
RETURN 1
END

The full error message that is returned is the following:

*** Create Package object failed
OLE Automation Error Information
HRESULT: 0x80070008
Source: ODSOLE Extended Procedure
Description: Not enough storage is available to process this command.

Does anyone have any insight as to what might be causing the error and how to fix it? Thanks.

Curt


janakis
Starting Member

1 Post

Posted - 2004-02-03 : 15:28:32
I am having the same problem as the previous post.

I am running SQLServer 2000 Enterprise edition with SP3 installed.

The sp_oACreate code succeeds most of the time. It fails occassionally with the "Not enough storage..." error. If the server is rebooted, then this error goes away. It manifests itself again after some time.

Leak in sp_oA methods was supposed to have been fixed in SQLServer 2000 SP1. So, I am at a loss as to what might be causing this problem.

Any suggestions or ideas about how to fix it?

Thanks,
Janaki.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-02-03 : 16:13:09
If this problem was supposed to be fixed in a previous service pack, then I would suggest contacting MS to report the bug in service pack 3. If the problem is truly a bug, then MS does not charge for the support call.

I didn't find anything SQL Server related when I search MS' knowledge base for that error.



Tara
Go to Top of Page
   

- Advertisement -