Probably a silly question but I am testing a component on MTS with a client app running on Windows 2000 Professional. I keep getting error 48, Cannot Load DLL. I have run the client executable (produced when I created an export package on the NT4 Server running MTS) on the client machine I am testing with which has Windows 2000 Professional installed. Could anyone tell me if there are any issues with doing this? Sorry if this is a basic question - new to forum.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MTS with Windows 2000 clients - does it work?
- Thread starter Mark33
- Start date
- Thread starter
- #3
Hi Chiph,
Yes the component was built with VB and the server that is running MTS has visual studio on it as well so all the runtime files are there. I know that component services on 2000 server produces .mis files to configure client apps to use remote components so wondered if 2000 client machines would still work with the .exe files produced by MTS? I have searched everywhere but there is no clear statement from Microsoft and I was trying to avoid wasting days trying to fix it if it is not possible - still searching!
Yes the component was built with VB and the server that is running MTS has visual studio on it as well so all the runtime files are there. I know that component services on 2000 server produces .mis files to configure client apps to use remote components so wondered if 2000 client machines would still work with the .exe files produced by MTS? I have searched everywhere but there is no clear statement from Microsoft and I was trying to avoid wasting days trying to fix it if it is not possible - still searching!
- Thread starter
- #4
Have spoken to Microsoft and for anyone who is interested (not many judging by the replies!) there are no issues with this or trying to do it the other way round - ie. using com+ NT4 clients. my probelm is down to something else - which I haven't completely sussed yet.
Guest_imported
New member
- Jan 1, 1970
- 0
u can do it we use components built in vc++ an d we run it successfully
hello (soory for my poor english, i'm frenchy 
),
i experienced this error last year. So I can say in my own case, it was a problem on dll file access right.
the user who owned the process executing the component (identity or interactive) must have Read & Right access (NTFS) to the dll.
so, even if you're not in a such situation, i tested several situations responsible of error (to be not surprised when it will happen), and the 48 case happened in only the above case.
hopping it will help you
have a good day
),i experienced this error last year. So I can say in my own case, it was a problem on dll file access right.
the user who owned the process executing the component (identity or interactive) must have Read & Right access (NTFS) to the dll.
so, even if you're not in a such situation, i tested several situations responsible of error (to be not surprised when it will happen
), and the 48 case happened in only the above case.hopping it will help you
have a good day
- Status
Similar threads
- Locked
- Question
- Locked
- Question