"Object was open" OLEDB error for parallel calls to Look Up transformation Options

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello everyone
I have an SQL Server 2005 SSIS Package which users can initiate using
when the use my IIS website.
I kick the package off from code in a separate thread.

It is used to import data and it makes repeated calls to the Look Up
transformation to validate.


If two or more instances of the package run I get the following msg:


Message: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has
occurred. Error code: x80040E05.
An OLE DB record is available. Source: "Microsoft SQL Native Client"
Hresult: 0x80040E05 Description: "Object was open.".


I'm a bit stuck. I know some versions of OLE support a flag to switch
on MARS (Multiple Active Record Sets). Could this be the problem -
how
would I switch it on?


Any information very gladly received ...

.

Relevant Pages

  • RE: Run a ssis package on SQL Server 2005 Error
    ... Failure saving package. ... This is most likely a known issue in SQL Server 2005, ... Set the SSIS Package ProtectionLevel property to ServerStorage ...
    (microsoft.public.sqlserver.dts)
  • RE: Move SSIS packages to a new SQL 2005 server
    ... domain user account for SQL Server Agent services. ... I recommend that you create a domain user account for your SQL Server Agent ... I think that a better way is to set your package ... You can create a SSIS package configuration file and deploy it together ...
    (microsoft.public.sqlserver.dts)
  • Re: Stored Procedure Error
    ... create a job for the DTS package and run it with sp_start_job? ... > I am having a problem invoking a DTS packade on my SQL Server. ... > using the stored procedures that use the OLE object to invoke the DTS ...
    (microsoft.public.sqlserver.dts)
  • Re: SSIS - can SSIS pkg recognize a drive letter within SMS job?
    ... The one alternative I've been wondering about is setting the default package ... set a starting path from within an SSIS package script. ... What is the result if you modify the FullPath value? ... indicates that your SQL Server 2005 has no service packs installed. ...
    (microsoft.public.sqlserver.dts)
  • Re: Running an SSIS package remotely from code
    ... You do not need SQL Server ... I can load and execute and SSIS package using the ... but the package runs locally. ... the local system. ...
    (microsoft.public.sqlserver.dts)