Worked with the sysadmin and we came up with a workaround. Rather than using a mapped network drive, ie
L:\ImageArchive \ArchiveForms\

we are using the network IP address to access the folders, ie:
\\192.168.1.22\ e\ImageArchive\ ArchiveForms\

I am surprised that there isn't a security issue with this, but it works without any problems.

The thing to remember in running a program from the...

Thanks for the suggestions. I put in a subroutine that writes to a text file and used that at various points in the logic to pin down the problem.

The scheduled task cannot access the mapped network drive that has the image folders, but the program has permissions to do that when the user is logged on. I am working with SysAdmin to set the permissions to allow this to process.

Line 131 referenced in the message is...

Plater:
The program runs standalone with the user credentials in a command window and from the scheduled tasks as long as the user is logged on. But it will not run from the scheduled tasks if the user is logged off, even though the run-as user is the same..

Logging on seems to change the permissions available to the scheduled task, which I do not understand.

My problem is how to find out what specific object...

I have a VB.NET app that crashes when run from the Windows scheduled tasks, but runs fine when the run-as user is logged on. The app also runs fine from the scheduled jobs if the run as user is disconnected. The O/S is Windows Server 2003, the app is created with VB.NET 2003. The .NET framework is up todate with Windows releases. The APP opens connections to an SQL Server 2003 database and an ODBC sql connection to an iSeries database.
...