.Net runtime exception on a scheduled .net batch job

Discussion in 'General Computer Support' started by radiant_rash, Dec 13, 2011.

  1. radiant_rash


    Dec 13, 2011
    Likes Received:
    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"


    "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 running

    Any 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-2003

    Thanks in advance!
    radiant_rash, Dec 13, 2011
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.