Multiplicity won't connect

Published on March 14, 2006 By ZubaZ In ThinkDesk

I am unable to connect two systems after the last beta so I rolled back to 1.02.

No they won't connect.

Unable to telnet over the default port.
Windows Firewall is allowing traffic over said port. Multiplicity and multipl32 are both allowed.

Service was not running on secondary (set to automatic). When I tried to start it I got an error:

Could not start the Stardock Multiplicity Service on Local Computer.
Error 193: 0xc1

Uninstalled (rebooted), reinstalled (rebooted); no love.
I deleted the service from a command prompt (sc delete Multiplicity) and cleaned the registry of lot's of MP refrences.
Rebooted, reinstalled, all is well.

FYI for anyone else having the same trouble.
The uninstall could be better from a registry point of view.

Comments

Neil Banfield

on Mar 14, 2006

I suspect if you now install 1.04 they will connect just fine.

It sounds like something got corrupted which was stopping the service from running.

Nakor

on Mar 14, 2006

If needed, run 'multisrv32.exe -uninstall' to have it delete its service prior to installing the new one as well. I've seen one instance where Windows didn't know what end was up with the service and I had to blow it away before it would take again.

ZubaZ

on Mar 14, 2006

Thanks guys.

Posted via WinCustomize Browser/Stardock Central

Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:

Richer content, access to many features that are disabled for guests like commenting on the forums.
Access to a great community, with a massive database of many, many areas of interest.
Access to contests & subscription offers like exclusive emails.
It's simple, and FREE!