Cart Search
New Topic
Forum Home | Login
esteser
esteser
Join Date 10/2001
0

Winlogon DLL Failed

Multiplicity not working

January 7, 2008 6:16:14 PM from Stardock ForumsStardock Forums
I am changing which machine I want as the primary machine and now I can't connect to the secondary machine. When I T/S it states that Winlogon dll has FAILED. I have not seen any other posts that really explain what the issue is. I created a ticket, but was hoping for a response on this board. I am running v1.1 pro.

If I go back to the original configuraiton - it works. For some reason the second machine does not like it.
multiplicity
Locked Post
Search this post
Advanced Search
Subscription Options
Reason for Karma (Optional)
Successfully updated karma reason!
esteser
Neil Banfield
Join Date 04/2001
+1109 sdemployee
Reply #1 January 8, 2008 4:30:55 AM
from WinCustomize ForumsWinCustomize Forums
What OS does your secondary run?
Reason for Karma (Optional)
Successfully updated karma reason!
esteser
esteser
Join Date 10/2001
0
Reply #2 January 8, 2008 9:54:34 AM
from Stardock ForumsStardock Forums
Both machines are running XP Pro SP2
Reason for Karma (Optional)
Successfully updated karma reason!
esteser
d5150
Join Date 02/2007
0
Reply #3 January 21, 2008 3:06:28 PM
from Stardock ForumsStardock Forums
I am having the same exact problem. Here is the email I sent to stardock support describing my issue:

Hello, my name is Dominic. I own Multiplicity Pro 1.2.1 and am registered under ***@****.com. I have been using MP for years and just recently ran into issues. For some reason MP keeps getting error bubble from system tray saying that connection to my laptop has been lost due to a protocol error. I upgraded from 1.2 pro to 1.2.1 pro paying $49.99 in hopes of resolving my issue but it did not. Below is what I have done to troubleshoot the issue:

My computers: Primary - PC - Windows XP Pro SP2 / Secondary - Laptop - Windows Vista Ultimate 32 bit (Both computers are running through a standard hub being the only two machines on my network right next to each other)

1. Uninstalled / resinstalled software several times
2. Tested xfering files back and forth through network shares
3. Tested Windows Remote Desktop & VNC enterprise applications to ensure that I can remote from laptop to desktop & vice versa
4. Ensure that firewalls on both machines are allowed to C:\Program Files\Stardock\ThinkDesk\Multiplicity\Multipl.exe (which have always been this way)
5. Manually added ports 30564 for both UDP and TCP in exception rules (which have always been this way)
6. Ping IP address and computer name from each machine
7. Ran "reinstall_mpp_service.bat" on Vista machine as outlined by Stardock rep in forum: https://forums.stardock.com/?forumid=267&aid=160323
8. Reset hub, ran widnows updates, rebooted computers several times
9. Disabled IPv6 on Vista laptop
10. Removed and let MP redetect my machine successfully several times
11. Ran troubleshooter on both machines, primary says "Multiplicity was able to connect to this machine without any problems. If you are having problems please run troubleshooter on other machine"
12. Ran troubleshooter on other machine and get "Multiplicity winlogon dll is NOT running" error

The DLL error seems to be a new issue since the upgrade to 1.2.1 as before everything tested ok and yes I was still unable to connect. Any assistance you can provide would be greatly appreciated, thank you.
Reason for Karma (Optional)
Successfully updated karma reason!
esteser
Vintage939
Join Date 04/2005
+4
Reply #4 February 21, 2009 10:13:16 AM
from WinCustomize ForumsWinCustomize Forums

Hi did you get this issue resolved?  if so how.  I'm having the same issues here.

thanks

Mark

Reason for Karma (Optional)
Successfully updated karma reason!
esteser
DanRanda
Join Date 10/2001
0
Reply #5 March 23, 2009 2:07:52 PM
from Stardock ForumsStardock Forums

I'm running Vista Ultimate on my Primary and Vista Business on my Secondary machine. I am having the same exact problem. I was using the trial version on both machines for a few weeks and then I decided to buy it. I bought and installed it and since then it hasn't worked. When I move the mouse to the edge of the screen to switch computers, my primary screen will dim and then start flashing about every second. the secondary does nothing.

Some help would be nice, especially since I PAID FOR IT FAIR AND SQUARE and now it doesn't work.

Reason for Karma (Optional)
Successfully updated karma reason!
esteser
sfsdfd
Join Date 03/2005
0
Reply #6 June 18, 2009 3:41:56 PM
from Stardock ForumsStardock Forums

Same problem here. I've been running the most recent version of Multiplicity just fine on a WinXP SP2 box and a Vista x64 Ultimate box. However, I just installed Windows 7 x64 RC1 and Multiplicity, and it is reporting a "Multiplicity WinLogon.dll not loaded" error in the troubleshooter.

I also tried running the "reinstall_mpp_service.bat" file that was recommended in another post, only to have it report errors about not finding the right registry key. The batch file also instructed me to RegEdit a particular key (something like "HKLM\Software\Stardock\ThinkDesk\Multiplicity\Path"), but only the registry key in this general area that was created by the Multiplicity installer was something like "HKLM\Software\Stardock\Multiplicity\Security" - something like that. The paths were so different that trying to guess the right key name and path was probably pointless.

- David Stein

 

Reason for Karma (Optional)
Successfully updated karma reason!
esteser
Fubeca
Join Date 04/2003
0
Reply #7 July 4, 2009 4:09:23 PM
from Stardock ForumsStardock Forums

I recently had some issues getting a Vista x64 secondary working (while my other Vista x64 secondary worked fine).  I tried everything mentioned in this and many other threads, but nothing worked. I reinstalled Multiplicity and rebooted both my primary and secondary machines so many times that I lost track.

Finally, I went into my DHCP reserve list on my router (I'm in a peer-to-peer network, not a domain) and added a reserve for the IP of my non-working secondary.  The reason behind this is that sometimes Vista has a hard time finding peer systems on a peer-to-peer network, even when there are only two machines on.  I was going to add an entry to my hosts file on my primary with the IP of the secondary, but after making the reserve in the DHCP table, I decided to give it a shot without touching the hosts file (I hate making "permanent" changes to my hosts file).  I unloaded Multiplicity on my Primary, and then restarted it.  It immediately found the secondary - and there was much rejoicing.

Reason for Karma (Optional)
Successfully updated karma reason!
esteser
Fubeca
Join Date 04/2003
0
Reply #8 July 4, 2009 4:10:35 PM
from Stardock ForumsStardock Forums

Oh, just thought I'd mention, both my working Secondaries still say "Winlogon dll not loaded", and yet, they work fine.

Reason for Karma (Optional)
Successfully updated karma reason!
esteser
cgroth
Join Date 07/2009
0
Reply #9 September 7, 2009 9:58:31 AM
from Stardock ForumsStardock Forums

I have the same issue. Has it been resolved or have you given up?

Reason for Karma (Optional)
Successfully updated karma reason!
esteser
emcee2
Join Date 07/2009
0
Reply #10 November 18, 2009 9:44:04 AM
from Stardock ForumsStardock Forums

I am using across 3 PCs (6 monitors) running Windows 7.  From time to time, for some reason, I find myself disconnected from one of the secondaries and get the same diagnostic message.  The ONLY thing I have found that works reliably is to COMPLETELY uninstall Multiplicity from the affected secondary computer ... and then 'hack the registry' ... and then reinstall the Mulltiplcity application on that secondary

Start by uninstalling the Multiplicity application on the affected secondary.  Then ... back-up your registry and then run RegEdit from the Run command.  Under the 'Edit' tab, use the 'Find' command to find all references to "Multiplicity" and delete each folder/key.  Reboot.  Reinstall Multiplicity on the Secondary.  Reboot.

On the 'primary' right-click the Multiplicity icon running on your taskbar.  Select "configure" ... select the secondary and re-configure it.  I have also changed the setting for the secondary computer address so that primary "looks up" the address each time the system reboots and attempts to re-connect.

All I can say is that it worked for me ... and like 3000 other things I tried before that did not work.

Reason for Karma (Optional)
Successfully updated karma reason!
esteser
TeMerc
Join Date 05/2010
0
Reply #11 October 5, 2010 3:25:23 AM
from Stardock ForumsStardock Forums

I'm having the same issue, winlogon.dll failed.

I've tried the fixes above, nothing works thus far.

Primary is W7-64bit home desktop, Vista Ultimate and SP systems as secondary, the system I'm having issues with is a wi-fi connected W7 laptop, 64bit Home.

Primary wil see the laptop but not connect, I suspect due to the winlogon.dll issue.

Any help would be appreciated

Reason for Karma (Optional)
Successfully updated karma reason!
esteser
TeMerc
Join Date 05/2010
0
Reply #12 October 9, 2010 3:33:27 AM
from Stardock ForumsStardock Forums

Any help on this? Or should I send an email to support?

Reason for Karma (Optional)
Successfully updated karma reason!
Stardock Forums v        Server Load Time:   Page Render Time: