Thanks for your quick reply!

I just don't understand what the difference is between manually running the .exe file and invoke the .exe file from SQL Serevr Agent. As I mentioned in the last post, if I run it manually, there was no problem. If I run it through Windows Scheduler, there was no problem either. Which means somehow the OS can locate the dlls under certain scenarios. But why it doesn't work for SQL Server Agent?

BTW, we are running SQL Server 2000 32-bit under Windows Server 2003 32-bit on a 64-bit IBM server, there is no problem at all. Now the what I am wondering is where the problem possibly is.