I had same problem. Solution was to give Read & Execute permissions to the c:\orant directories to the network/local account that the web server uses. The perl scripts need to go outside of the perl directories to use Oracle stuff, so give the web server permission to execute the Oracle stuff.

The reason it worked from the command line was that I was using my own network account that already had permissions to the Oracle directories.

Up until recently, I did troubleshooting by logging on to the web server using the account that the web server uses. Then use Windows Explorer to verify that the web server can see the same things I can see when logged in as myself. A recent "lockdown" tool removed the ability to log on locally to the web server itself, but I can still log on to another computer and do the testing.

Hey, my first post! FirstCool