No longer works

Hello,I had multiplicity working just fine prior to the 1.2 release. I have two Vista machines, one x64, primary, and one x32, secondary. No matter what I try firewall wise, recreating passwords etc, the Primary never connects to the Secondary. When you setup the Primary so it knows who the secondaries are the connect does find the secondary but alas no connection ever takes place after that. It's been like this for a while now just hadn't gotten around to asking for help! I do have a MS Intellipoint wireless mouse on the primary which is new. I did install the drivers onto the secondary thinking that might help but of course I only have one MS Wireless mouse. Not sure if this is the cause or not.Cheers, Dominic
16,313 views 33 replies
Reply #1 Top

I will try this on our test machines in the morning. Will you start a ticket with us and be sure to reference this forum post?

Reply #2 Top
Okay I submitted a ticket via the website. TBP-966119. Cheers, Dominic

Reply #3 Top
As an addendum, using the troubleshooting on the Primary succeeds without issue. On the secondary it reports Multiplicity WinLogon dll is NOT running.I scanned the other posts here but there was nothing I could find related to this specific issue and Multiplicity Pro. I have no other Stardock apps, besides Stardock Central, installed on this machine.

Reply #4 Top
I am running an XP machine and a Vista x64 machine, and am having the same problem (and errors) the errors clear if i log out and log in again. but the mouse wont work.

(I've tried both machines as Primary/secondary and the problem is the same)
Reply #5 Top
Yes I tried the logout and login trick, and this time troubleshooting on secondary has 3 green/white tick marks instead of 1 and the error about Winlogon DLL. However it makes no difference to actual connectivity with the primary.Cheers,

Reply #6 Top

If it never connects then it would suggest it is not configured to connect to it.

Firstly make sure the IP address is set right for the connection.  Then from the interface tab, press the configure button for seamless mode and make sure that connection is actually set to be used.

Reply #7 Top
A reply was sent to your ticket/email. Did you get the reply and did you send back the requested files?
Reply #8 Top
I found the message in my Junk folder . I received the initial ticket open message without a problem though. I actually managed to get it working again. The problem doesn't appear to have been with the secondary despite the troubleshooting errors being reported only on the secondary. I had reinstalled the secondary, messed around with various options on the primary, add/remove client, change location on the wrap around etc, nothing. I finally uninstalled the Primary, rebooted primary, reinstalled Primary and voila it works. I still need to actually do a Primary reboot though to see if the fix is temporary or will survive a restart. I'll post back once I've restarted the primary again. Cheers, Dominic

Reply #9 Top
Okay I rebooted and sure enough the Primary remains disconnected from the Secondary post reboot. I uninstalled, rebooted, reinstalled, Ran application when prompted, configured it using the stored settings, and bingo the connection to the secondary was established. So the problem is something breaks with a reboot on the primary. I finally found an error in the System log which I believe occurs just after the reboot,"The Stardock Multiplicity service failed to start due to the following error:
The system cannot find the file specified." Event ID 7000, Level Error,OpCode Info,- . Sadly it doesn't tell me which file it cannot find.

Reply #10 Top
I repeated my test of uninstall, reboot, install works, a couple of times as I had an OS patch to install. Works like a charm everytime although I would consider this a right royal pain just to restore connectivity to my secondary machine on a regular basis. Probably doesn't do the OS much good either having an app installed/uninstalled all the time either. The log entry might be misleading as I could only see it once despite the several installs/uninstalls performed.

Reply #11 Top
I have this same issue. Primary: WinXP, Secondary: Vista Ultimate (32 bit). Troubleshooting on the vista machine shows "Multiplicity winlogon dll is NOT running". Can't get connectivity between machines. This problem seems sporadic to me and I have yet to figure out what common activity causes the issue.

It seems like the issue is increasing in frequency, but that could be a result of my increasing frustration
Reply #12 Top
(Citizen)EnkiduAelderon
End of quote
Verify that the versions are exact.  Compare file size and dates if neccessary.
Reply #14 Top
That fixed it instantly - thank you!!!
Reply #15 Top
Good deal. Let us know at support@stardock.com if you need further help!
Reply #16 Top
I'm having the same problem . I even tried connecting the computers together directly using a patch cable to see if the router was the problem , even that didn't help .
When I run the batch file , it tells me it can't locate \MultiSrv32.exe , which it is in the right directory , I can see it there !
Very frustrating . As the other user , it worked fine before the update , now it just keeps saying that it can't connect to the client machine , even though it sees it .
I just moved , so I hadn't had time to work on the problem , but know it's just irritating . I've disabled firewall , av , windows firewall , UAC , nothing helps.
Reply #17 Top
The batch file didn't work for me. How can I revert to the version that used to work?

Reply #18 Top
The batch file didn't work for me. How can I revert to the version that used to work?
End of quote
If you used SDC to install and upgrade, there is an option to archive applications.  Do you use SDC and do you preserve archives on upgrades?

Spazotron and Gooberific, have you uninstalled, rebooted, installed on both (or all) PCs?
Can you verify that all the file dates are the same on all machines?
Reply #19 Top
Used SDC, without the archive checkbox unfortunately. The slave troubleshooting says winlogon.dll not running. portqry -local on the slave shows 30564 listening. portqry -n (IP) -e 30564 shows LISTENING. Master says "was able to connect"... and yet there's no connection. I have rebooted way too many times now.

Reply #20 Top
Oh and yes I've reinstalled 4-5 times now.
Reply #21 Top
Great. Had a friend send over a 1.10 standalone installer. Installs fine but when I go to activate it says "Invalid Product". After years of good success with Mutliplicity this is really really irritating.

Reply #22 Top
Email support@stardock.com.  They can get you a link to the last version.
Reply #23 Top
I have gone back to freeware Synergy2, which while a pain to configure definitely still works. Sorry but after being a Multiplicity user for over 2 years now I can't live without the functionality and this mess with the new version is enough to make me regret paying for it.

Reply #24 Top
Very sorry to hear that. Should you still wish to we would be happy to help. Please contact us at support@stardock.com.
Reply #25 Top
If MP 1.1 said the product was invalid it sounds like you tried to use a MP Pro key with MP non Pro or a MP non Pro key with MP Pro.