May 22, 2007 at 3:50 am
I'm trying to run a VB.NET from a dts.
This works when I run the DTS manually but just hangs when I schedule the DTS.
Has anyone seen this before ?
May 22, 2007 at 8:13 am
When you run a DTS package from your machine using Enterprise Mangler the DTS uses local resources to execute the tasks. Check your dependencies, connections and configuration for the Sql Server machine.
If the vb.net program is to run without any interaction (no button pressing or anything) solving the resource issue on the Server machine should sort this out.
May 22, 2007 at 8:20 am
Adrian
Thanks for the reply. Since I posted the message I've got the DBA to install the .net framework on the sequel server.
When I scheduled the dts again I got the following message:
Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 0
Date: 22/05/2007
Time: 14:54:35
User: N/A
Computer: SQLXXXXXX
Description:
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: .NET Runtime version 1.1.4322.573- FraudDailyImport.exe - Common Language Runtime Debugging Services: Application has generated an exception that could not be handled.
Process id=0x1224 (4644), Thread id=0xe64 (3684).
Click OK to terminate the application.
Click CANCEL to debug the application..
Could it be a security error ? If so do you know how to fix it ?
May 22, 2007 at 8:55 am
The error seems familiar in the fog at the back of my mind.
It could be a permissions issue. You can download a handy tool from Sysinternals (http://www.microsoft.com/technet/sysinternals/SystemInformation/Filemon.mspx) which will show whether you're getting access denied issues or not.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply