.Net runtime exception on a scheduled .net batch job

Status
Not open for further replies.

Radiant_rash

Beta member
Messages
1
A scheduled application which was running fine for years on production environment(production server) has started to fail on every schedule.The log on the event viewer is very generic which says something like "Common Language Runtime Debugging Services: Application has generated an exception that could not be handle"and"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."Using AUXSOURCE flag was of no help as it dint work in windows 2003 server.No patches or updates have been installed on this server recently and also other .net batch jobs are running fine.Can't find the reason that's preventing only this job from runningAny help in detecting the possible causes for this would be appreciated.The application runs on windows server 2003,stadand edition,service pack 2.net framework 1.1,vs-2003Thanks in advance!
 
copy the command from the scheduled job into a terminal / command prompt window (or screen).

run the command manually and wait for error output.
 
Status
Not open for further replies.
Back
Top Bottom