mswinsck.ocx not found

[Former Member]

Hi MI-fans,

I copied the whole MI installation to another PC and

adjusted the JDK home and MI home in the startup.bat file

according to Jo's blog.

/people/sap.user72/blog/2005/12/21/how-to-reconfigure-mi-client-when-installation-path-is-altered

I am getting mswinsck.ocx not found error when I startup

MI. mswinsck.ocx and other dependent libraries are missing?

Should I have to run the setup.exe rather than copying?

Thanks,

Maverick

[Former Member · Accepted solution]

hello maverick,

your winsock active x component might not have been

installed or registered. MI installer might not include

the ocx component in the package... im not sure though.

before trying the solution in the link, try running your

MI installer... if it persists, try the solution below.

http://www.ascentive.com/support/new/support_dll.phtml?dllname=MSWINSCK.OCX

you tried to run the MobileEngine.exe, right?

this app uses the winsock OCX...

rgds,

jo

[Former Member · Accepted solution]

Thanks Jo,

I did not bother running the MI installer. I just followed

the solution in the link you provided and it's working now.

Thanks a lot.

Maverick

[Former Member · Accepted solution]

hello maverick,

if ever you don't have the permission to install such

components, you can still start up MI thru the startup.bat

script file directly. as i already said, this activeX

component is only used by the MobileEngine.exe in checking

for the status of the Tomcat server.

you can save a little memory by running the startup script

on the commandline.

regards

jo