I have a file on one server(Windows 2003) and need to access from another server (IIS server - Windows 2008) , I have written the program for the same which works fine and I can access the file.
But when this comes to the DLL (which registered successfully on Windows 2008), its not able to find the file on Windows 2003.
For the moment, forget your program. From the Windows 2008 computer can you see/access the file on the Windows 2003 computer using sharing and Windows Explorer? There are various security policy settings re network that can cause this problem, so these need to be checked first.
Yes, I can access the file from Windows 2008 on the Windows 2003. I have written one small seperate program in c++ which runs on Windows 2088 and accesses files from Windows 2003.
Yes, I can access the file from Windows 2008 on the Windows 2003. I have written one small seperate program in c++ which runs on Windows 2088 and accesses files from Windows 2003.
Okay, how much you know about COM servers? Are you aware you need to register COM server in the system where you are to invoke one? So did you register it? Otherwise, which way you create the class the DLL hosts?
The DLL contains the C++ code which search for a file and try to open it.
The DLL need to be registered on Windows 2008 and the the function to search a file will be called from the ASP code.
Is the dll 32 bit or 64 bit? If 64 bit, is the 2003 system 32 or 64?
If you have access to the dll source code, I'd recommend creating a debug build and add some trace statements (or logging) to the dll to see what's going on.
It could be a permissions problem, different path, or a host of other problems. You need to trace/log to find out exactly where things are going wrong.
Do you have any idea, if it makes any difference and if yes then whats that exactlly .... Please help!
I am trying to help, did you see my previous response?
If you have access to the dll source code, I'd recommend creating a debug build and add some trace statements (or logging) to the dll to see what's going on.
It could be a permissions problem, different path, or a host of other problems. You need to trace/log to find out exactly where things are going wrong.
What I mean here is you are going to have to debug the dll. Either step through the code in a debugger, attach a remote debugger to a debug build of the dll, or add some trace statements and logging.
Bookmarks