After doing a Google, Verisign, and PM search, I'm still stuck trying to resolve a (seemingly) interesting problem.

We have two version of Perl on our web server. One's 5.6 perl.exe (aka "regular"), and the other's the ISAPI dll version. I created a script that uses this new module (written by Verisign for their Ecommerce services, called Payflow Pro) along w/ Carp (so I could see errors). When run with the regular perl.exe, the system runs fine, able to load and use the module with no complaints.

When I try to run the exact same script with ISAPI, it tells me that it,

Can't load 'd:/opt/perl/site/lib/auto/PFProAPI/PFProAPI.dll' for modul
+e PFProAPI: load_file:The specified module could not be found at d:/o
+pt/perl/lib/DynaLoader.pm line 206.
 at d:\home\web\cgi-bin\ecom\test.plx line 16K
[download]

This test.plx thing is the test script, and line 16 is the use line for the PFProAPI module. I have both included and left out "use Win32::API" to see if it was an issue of getting to another Windows DLL in disguise, too.

We've checked the dll to make sure it has permissions for the Internet Guest users to access it, and the fact that it runs under perl.exe tells me this isn't a permission issue anyway.

The path its looking in for the DLL is correct, too.

Anyone have any links/newsgroup posts that might help out with this? If not, any suggestions on what to try next to get ISAPI to accept this frickin' module?

I've talked with Verisign about this, and they're a bit puzzled as to the cause. Because of the specificity of the issue with ISAPI, is there anything that could be of concern with that install? Other modules (like Digest::MD5, Blowfish, and others) appear to work well with the ISAPI version of Perl.

Many thanks to all posters and responders in advance.