This is on Windows 2003 Server. I have an olde ASP script that runs a .NET console app (to get a price from a database) via WScript.Shell. The basic version that just returns a number works fine.
However, the console app needs to connect to a MYSQL5 database, which means it links to the MySQL.Data DLL. The DLL is in the same folder as the EXE, but whenever I try it via the web it fails to find the DLL. I get a "Starting Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'MySql.Data, Version=6.2.2.0" etc. message back on stderr.
However, if I run the same exe from a command prompt on the server it works fine. I've tried setting the PATH, and also checked that the webserver anonymous account has read access to the EXE and DLLs, so I can't understand why the version run from the command line works, and the version run via WScript.Shell fails.
Can anybody help?
(The problem here is it's a hodge podge of a system with ASP using MySQL4 and ASP .NET using MySQL5 otherwise I'd just write the ASP to talk to the database).
However, the console app needs to connect to a MYSQL5 database, which means it links to the MySQL.Data DLL. The DLL is in the same folder as the EXE, but whenever I try it via the web it fails to find the DLL. I get a "Starting Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'MySql.Data, Version=6.2.2.0" etc. message back on stderr.
However, if I run the same exe from a command prompt on the server it works fine. I've tried setting the PATH, and also checked that the webserver anonymous account has read access to the EXE and DLLs, so I can't understand why the version run from the command line works, and the version run via WScript.Shell fails.
Can anybody help?
(The problem here is it's a hodge podge of a system with ASP using MySQL4 and ASP .NET using MySQL5 otherwise I'd just write the ASP to talk to the database).
Comment