Your problem is in improper security settings and/or user accounts.
When you use IIS 6.0 to run your ASP.NET web applications, they run under a
different user account, namely the "Network Service" by default. When you
log in to the server, you are usually the Administrator. When you map a
network drive (for instance, use "net share"), you are doing so for the
Administrator account only. When IIS runs your ASP.NET app, it won't be able
to "see" that networked drive, because it was for the different user.
This is how it goes simplified, anyway. Now, you could try using a UNC paths
(\\servername\share\path\app.exe) instead of regular paths (K:\path\app.exe)
to see if that helps. However, this might not work, also because of the
security. In that case, you need to either change the user account that runs
your application pool in IIS or you need to give permissions to your file
share (and possibly, NTFS file system rights on the server) for the Network
All in all, you need to learn a bit more about security in IIS 6.0, and the
definite place to start is obviously the documentation:
Also, if you have the .NET 2.0 SDK documentation (that comes with Visual
Studio 2005) installed, then this link is also useful:
Finally, this link might prove useful in your situation:
Hope this helps you to solve your issue.
Mr. Jani Jvinen