Vaneyen Vaneyen

Cannot KVM connect to second computer.

▼

Cannot KVM connect to second computer.

Using KVM mode

https://forums.stardock.com/486104/multiplicity-support-faq#connectionissues
from Stardock Forums

I followed the Connection Issues 101 thread, all the way to running the Purge_MP-New on both machines, and reinstalling, using exactly the same download.  Installed the second machine first, as a Secondary, then the primary machine, as Primary.  Primary confirms that it can see Secondary, *but* when I try to connect, I get the "Connecting to <pc_name> . . . . . . [ Cancel connection ]" window for maybe 5 seconds, then it just goes away.

What else can I do to troubleshoot?  Are there logs made of the connection process that can provide more input?

multiplicity
73,451 views 74 replies
Reply #51 from Stardock Forums Top

I had the same problem.

Running "MPRDP.EXE" instead of "MPRDP64.EXE" did help and I am able to successfully connect when using "MPRDP.EXE" while "MPRDP64.EXE" is crashing.

What I did to avoid having to run this manually, is the following:

* Unloaded multiplicity

* Created a copy of MPRDP64.exe to keep it for backup-reasons

* Created a copy of MPRDP.EXE and renamed it to MPRDP64.EXE

Then I can use the system tray conveniently to to KVM based remote connections and it works. I suspected that this might lead to 64-bit process loading issues, but so far it didn't.

Windows build: Microsoft Windows [Version 10.0.19042.508] (20H2)

Reply #52 from Stardock Forums Top

Quoting marioszp, reply 51

I had the same problem.

Running "MPRDP.EXE" instead of "MPRDP64.EXE" did help and I am able to successfully connect when using "MPRDP.EXE" while "MPRDP64.EXE" is crashing.

What I did to avoid having to run this manually, is the following:

* Unloaded multiplicity

* Created a copy of MPRDP64.exe to keep it for backup-reasons

* Created a copy of MPRDP.EXE and renamed it to MPRDP64.EXE

Then I can use the system tray conveniently to to KVM based remote connections and it works. I suspected that this might lead to 64-bit process loading issues, but so far it didn't.

Windows build: Microsoft Windows [Version 10.0.19042.508] (20H2)
End of marioszp's quote

While this is very valuable information, what we REALLY need is a dump capture to find out why the other file is crashing.  This process will help:
https://forums.stardock.com/501231/get;3788076

Again, any time that can be spent providing the information would be very well received.

Sean Drohan
Stardock Support Manager

WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #53 from Stardock Forums Top

I can confirm removing the license did not do anything. So I went through the process of purging settings and the install of Multiplicity on all machines.

On installing again I made sure it was 3.5 on all machines and it all works no connection issues, no crashing. All machines connect as expected.

Reply #54 from Stardock Forums Top

Quoting bigwookie, reply 53

I can confirm removing the license did not do anything. So I went through the process of purging settings and the install of Multiplicity on all machines.

On installing again I made sure it was 3.5 on all machines and it all works no connection issues, no crashing. All machines connect as expected.
End of bigwookie's quote

Ok, so the purge on each box worked, no need to modify files, the KVM connections worked as expected after, yes?

Sean Drohan
Stardock Support Manager

Reply #55 from Stardock Forums Top

Yes all worked as expected. I did not try what the other user did above in moving the EXE around. Before I downgraded to 3.44 and then upgraded to 3.5 to fix. But purging and installing at 3.5 worked.

Reply #56 from Stardock Forums Top

Quoting bigwookie, reply 55

Yes all worked as expected. I did not try what the other user did above in moving the EXE around. Before I downgraded to 3.44 and then upgraded to 3.5 to fix. But purging and installing at 3.5 worked.
End of bigwookie's quote

Well, that too would be nice to hear from the others.  It would also point to a potential issue of that file not being replaced (even though we can't see that it was changed in any way).

Looking forward to hearing from the others.

Sean Drohan
Stardock Support Manager

Reply #57 from Stardock Forums Top

We have a test build for the KVM crashing.  You can install this over what you have, on each box, reboot, and let us know if you still see the issue:

https://cdn.stardock.us/downloads/public/software/multiplicity/Multiplicity_3.51-j40-Setup.exe

Thanks for the patience and feedback.

Sean Drohan
Stardock Support Manager

Reply #58 from Stardock Forums Top

If either machine has two active graphics systems, particularly the secondary machine, disable/uninstall one and see what happens.   

One of my secondary machines is an HP Zbook that has two graphics systems (the Intel one that comes with the i7) and a discrete Nvidia.   Until I disabled/uninstalled the Intel graphics, I had exactly the situation you have.  Once I did so, MP worked just fine.

Reply #60 from Stardock Forums Top

Quoting Metal0gic, reply 59

should this be posted here? i was told to post my dump here in the main topic
End of Metal0gic's quote

If you install this version, on each box, reboot, does it still happen?

https://cdn.stardock.us/downloads/public/software/multiplicity/Multiplicity_3.51-j40-Setup.exe

Sean Drohan
Stardock Support Manager

Reply #62 from Stardock Forums Top

the issue doesn't seem to be recurring now after that version install

 

edit# i may have spoken too soon, I think having the windbg debugger erroring getting access denied seem to prevent the app from stopping?

as soon as I i turned off the debugger and closed windbg multipl2.exe crashed so ill see if it happens again.

Reply #65 from Stardock Forums Top

Quoting Metal0gic, reply 63

crashing again with the new j40 build

https://1drv.ms/u/s!AjtwOUB1LvjqmmRGUoUHYdu_PalX?e=8jgU1f

 
End of Metal0gic's quote

Install this build, on each PC, and let us know, please.

https://cdn.stardock.us/downloads/public/software/multiplicity/Multiplicity_3.52-j42-Setup.exe

Thank you for your time and feedback.

Sean Drohan
Stardock Support Manager

+1 Loading…
Reply #66 from Stardock Forums Top

Just wanted to chime in that I noticed that KVM didn't work with version 3.5 installed on both computers (and KVM had been used between them previously, but while ago since I primarily use Seamless mode which has been working fine)

Found this thread and tested the 3.52 build linked on both computer and it at least fixed it on my end.
Unfortunately didn't do any kind of logging with the older version as I was more keen to just try the ready solution straight away.
Figured I'd least let you guys now it fixed it in my case

Reply #67 from Stardock Forums Top

Quoting sdRohan, reply 65


Install this build, on each PC, and let us know, please.

https://cdn.stardock.us/downloads/public/software/multiplicity/Multiplicity_3.52-j42-Setup.exe

Thank you for your time and feedback.

Sean Drohan
Stardock Support Manager
End of sdRohan's quote

 

new build, new dump, the crashing does seem less frequent however.

https://1drv.ms/u/s!AjtwOUB1Lvjqm1NI36tyzEPq8T2b?e=PRXUDi

 
Reply #68 from Stardock Forums Top

Quoting Metal0gic, reply 67


Quoting sdRohan,
reply 65


Install this build, on each PC, and let us know, please.

https://cdn.stardock.us/downloads/public/software/multiplicity/Multiplicity_3.52-j42-Setup.exe

Thank you for your time and feedback.

Sean Drohan
Stardock Support Manager



 

new build, new dump, the crashing does seem less frequent however.

https://1drv.ms/u/s!AjtwOUB1Lvjqm1NI36tyzEPq8T2b?e=PRXUDi

End of Metal0gic's quote

Could you check the file signing date on multip2.dll in the multiplicity folder please as the dump file lacks file version data and I want to be 100% sure the file was replaced correctly.  Thats right click on file, properties, digital signatures tab.

Reply #69 from Stardock Forums Top

hey, i dont have a multipl2.dll

i have am multip.dll and a multi2.dll

the multip.dll is feb 23 2020

the multi2.dll is September 4th 2020

also I found what causes the crash,

it has to do wit the clipboard, when there's like a blank or maybe just a spacebar character in my clipboard it crashes, as soon as I replace whats in my clipboard with text or something it seems to work. i have a clipboard history tool and the item that makes it crash appears to be just blank, I'm not sure what I  copied to get that, its possible I copied something else that multiplicity didn't like and so it makes the clipboard blank but it does seem to be clipboard related. cuz if I go back in my clipboard history and choose that particular item it will crash every time if I switch it to something normal the app wont crash.

 

Reply #70 from Stardock Forums Top

Quoting Metal0gic, reply 69

i have a clipboard history tool and the item that makes it crash appears to be just blank
End of Metal0gic's quote

Is that the Windows 10 native clipboard tool or something else?

If Windows, do you have 'Sync' turned on for each PC?

Sean Drohan
Stardock Support Manager

Reply #71 from Stardock Forums Top

Hi, its not the Microsoft clipboard history or sync. im using a third party tool called ditto, but it just records your clipboard and lets you search previous clipboard items. but i don't think the issue is due to the that software.

I do think the issue is related to clipboard items but i think its something else

I work in IT and am constantly remoting into other users computers through a software called screenconnect or "connectwise Control"

which also syncs clipboards from my machine to the remote machine and vice versa, it seems like something happens where the clipboard doesn't sync properly from the remote machine and makes my clipboard blank or perhaps some other sort of invalid value, and its when that happens and i try to move the other screen with multiplicity, that is causes the crash. as soon as clip something else the crashes stop.

I haven't been able to figure out exactly whats causing the clipboard items to go weird from a remote users machine. but i think if you catch or sanitize invalid clipboard values before trying to sync it to the other multiplicity machine that should help.

Reply #72 from Stardock Forums Top

my clipboard is currently crashing multiplicity.

multiple apps such as powershell show the clipboard as blank

using insideclipboard which shows your current clipboard in multiple value types

CF_TEXT appears blank

CF_UNICODETEXT is

Code: html
  1. 00000000 00 00 ..

hope this helps

Reply #73 from Stardock Forums Top

Quoting Metal0gic, reply 72

my clipboard is currently crashing multiplicity.

multiple apps such as powershell show the clipboard as blank

using insideclipboard which shows your current clipboard in multiple value types

CF_TEXT appears blank

CF_UNICODETEXT is

Code: html

  1. 00000000 00 00 ..




hope this helps

End of Metal0gic's quote

That is very strange.  I wonder why they would be putting an entirely blank text entry into the clipboard rather than just emptying it?

We will see if we can see whats going on as a 0 length entry shouldn't cause a problem.

Reply #74 from Stardock Forums Top

it seems like it happens when I disconnect from a computer, so it could be overwriting the clipboard as a security measure.