Why won’t WorldClient start, I keep getting **** ALERT **** WorldClient was expected to be
running but wasn’t; restart attempt was successful [EvProcess]?
The most common 2 causes for this error are detailed below:
1. MDaemon has been upgraded or restarted, but WorldClient wasn’t able to close correctly and as a result Windows still thinks it’s running and won’t let the new WorldClient.exe process bind to the associated port number.
To resolve this:
a. Choose Setup -> WorldClient and specify “WorldClient runs using built-in web server” if it’s showing disabled.
b. Change the “Run WorldClient Server using this TCP port” value to one number higher (for example, if it’s currently specified as port 3000, change the port to 3001).
c. When prompted choose “YES” to restart the WorldClient service.
d. Confirm that WorldClient is now able to remain active on this port.
e. Take the same steps again, but this time change the “Run WorldClient Server using this TCP port” value to the old one you changed it from in step b.
f. When prompted choose “YES” to restart the WorldClient service.
WorldClient should now be running and accessible on the original port.
2. If the Micosoft IIS (Internet Information Services) is installed on the same machine as MDaemon and WorldClient and IIS is already ‘listening’ on the port that WorldClient wants to use, then this will prevent WorldClient from being able to start.
To verify if IIS is installed, from the Windows Start Menu choose … Settings -> Control Panel -> Administrative Tools -> Services.
Under ‘Services’ you should find a service called ‘IIS Admin’.
If you aren’t using IIS on this machine and would like to stop the ‘IIS Admin’ Service take the following steps :-
a. Right Click ‘IIS Admin’ and choose Properties.
b. Choose “Disabled” from the ‘Startup Type’ drop down menu.
c. Under ‘Service Status’, click “Stop”.
d. You may be advised that services related to IIS Admin must also be stopped. Click OK to acknowledge this.
e. Move to the associated services and disable them in the same way as you did in Step 2.
By disabling the services, you ensure that they do not restart if you reboot the MDaemon machine in the future.