🚀 go-pugleaf

Hi

I have an existing service that has been running fine on Windows 2000 server
for ages.  It makes use of a third party dll that is loaded shortly after
the service starts up, using LoadLibrary("c:\fullpath\thedll.dll").  I
recently had to move the service over to a Windows 2003 server and now the
LoadLibrary fails with error code 126 (module not found).  I call a
FileExist before the LoadLibrary to verify that the dll is in fact where
expected (and it is...).  Stranger still is that if I run the service in its
debug (application) form instead it loads the library fine.  I have double
(and triple and quadruple) checked the file paths etc.  I have registered
the dll correctly.

I know that Windows 2003 server has increased security features but I can't
find anything that seems related.  Is there something obvious here that I'm
missing?  Anybody else had this problem?

Thanks

Kev