"Proc" <anonymous@email.com> wrote in message
news:ujjgl09s0pttaodu94e0kc671snkjrkl1l@4ax.com...
>I have a package built in VB.NET being run from an ASP.NET webpage.
> It is pulling large amounts of data from SQL Server into an Access
> database for download by the user.
>
> I have two Web servers running this package and only one of them is
> getting the following error, while the other Web server runs the
> package perfectly:
>
> System.Runtime.InteropServices.COMException (0x80040005): Code
> execution exception: EXCEPTION_ACCESS_VIOLATION
> at DTS.Connection2.get_ConnectionProperties()
> ...
>
> The problematic Web server is running SQL Client Tools SP3 and the
> database server is running SQL 2000 SP3. Both Web servers are using
> the same connection string and are using the same user account for
> access to the SQL Server.
>
> Please Note:
> I have already made sure that all steps have:
> ExecuteInMainThread = True
>
> I have some ASP sites successfully running a similar package on the
> same server experiencing these problems.
>
> Any ideas where I could be experiencing a problem?
>
> Thanks in advance.

On Mon, 27 Sep 2004 13:46:49 -0400, Proc <anonymous@email.com> wrote:

>I have a package built in VB.NET being run from an ASP.NET webpage.
>It is pulling large amounts of data from SQL Server into an Access
>database for download by the user.
>
>I have two Web servers running this package and only one of them is
>getting the following error, while the other Web server runs the
>package perfectly:
>
>System.Runtime.InteropServices.COMException (0x80040005): Code
>execution exception: EXCEPTION_ACCESS_VIOLATION
> at DTS.Connection2.get_ConnectionProperties()
> ...
>
>The problematic Web server is running SQL Client Tools SP3 and the
>database server is running SQL 2000 SP3. Both Web servers are using
>the same connection string and are using the same user account for
>access to the SQL Server.
>
>Please Note:
>I have already made sure that all steps have:
>ExecuteInMainThread = True
>
>I have some ASP sites successfully running a similar package on the
>same server experiencing these problems.
>
>Any ideas where I could be experiencing a problem?
>
>Thanks in advance.