Friday, March 30, 2012

Running a vb.net exe from a dts

I'm trying to run a VB.NET exe from a dts.
This works when I run the DTS manually but just hangs when I schedule the DTS.
Has anyone seen this before ?Many times when you can run a DTS package manually, but not thru a scheduled job, it boills down to one of two things. Either you are running it from your machine instead of the server, or you have permissions that SQL Agent does not.

Physically logon to the SQL Server (not just open Enterprise Manager) and try to run your package ... if it fails, you were referencing files on your local box and not the server.

If it succeeds, then you need to look at the permissions of the service logon running SQL Agent verses your permissions.|||Thanks for the reply.
The DBA stated that the following error was found on the db server:

"Unable to Locate DLL - The Dynamic Link Library mscoree.dll could not be found in the specified path"

He is currently installing the .net framework on the sequel server.

Do you think this will do the job ?|||After installing the .net framework on the sequel server, I re run the dts and got the following message from the event viewer:

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: SQLXXXXX
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..[/B]

Anybody got any ideas ?

Thanks in advance.sql

No comments:

Post a Comment