Cannot KVM connect to second computer.

Additional note: I can connect using Seamless, and that works correctly, but I really need this second computer to be in KVM mode.

If I hastily click on the Gear icon at the top of the connection screen, I get the notification "Successful connection   Multiplicity has connected to <pc_name> (<pc_ip_address>) using AES-256 encryption   Stardock Multiplicity 3", but still no screen appears to control the second computer.

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

AzDude
Stardock Community Assistant

Hello,

Sorry to hear you are having trouble.

Has it ever worked to KVM connect tot he PC in question? 

If you disable the firewalls on each PC, does that have an effect?

If you redo the connection and add it by IP (type it in), does that change the result:

Do you connect to others that do work?  If you try the opposite, make the Secondary a Primary, reversion the current Primary, can you connect to it?

Is the Secondary headless (no monitor)?

Do you have 3.5 installed on each PC?

Sean Drohan
Stardock Support Manager

Thanks, Sean, I'll try to answer these in order:

1) Has it ever worked to KVM connect tot he PC in question? -- No, this is a new purchase, and this is the only time these two computers have ever communicated via Multiplicity

2) If you disable the firewalls on each PC, does that have an effect? -- Good question, I'll have to look at what firewalls each PC, but to the best of my understanding, the only firewalls are those built-ion to Windows 10.  Does it help to know that "Seamless" works fine in the current state?

3) If you redo the connection and add it by IP (type it in), does that change the result -- Per the Connection 101 instructions, I tried using the IP address after it didn't work the first few times, no better.  This was before I did the full purge and reinstall.  I haven't tried using the IP afterwards, as the instructions indicated to use all defaults.  Both computers are on the same 10.0.0 subnet.

4) Do you connect to others that do work? -- I haven't tried yet, but if you think this will result in better troubleshooting information, I can try.

5) If you try the opposite, make the Secondary a Primary, reversion the current Primary, can you connect to it? -- Also a good question.  Can I use the same license code on two computers (the one I _want_ to have as Primary, and the one I'm wanting as Secondary) without trouble?

6) Is the Secondary headless (no monitor)? -- The secondary does currently have a monitor, but only because I'm trying to get it working headless, and I'm borrowing the monitor from another workstation.  Could the fact that the Secondary currently has a monitor be fouling the KVM connection somehow?

7) Do you have 3.5 installed on each PC? -- Exactly the same version is running on both machines, as per the About, although the Secondary reports "Version 3.5 Build 00096" and the Primary reports "Version 3.5 Build 00096.kvm".  Both versions were downloaded from the same link (Download)

Follow-up:

2) If you disable the firewalls on each PC, does that have an effect? -- No change.  Turned off the Windows Defender firewall from both machines, and it still did not connect in KVM mode.

5) If you try the opposite, make the Secondary a Primary, reversion the current Primary, can you connect to it? -- No.  If I make Primary into Secondary (and remove the license), then apply the license to the secondary to make it Primary, I encounter the same issue, only in reverse.  Both machines work to have the other as Secondary via Seamless mode, but neither can use the other machine in KVM mode.

Hello,

For the time being, we want any test PCs to have monitors attached.

If it is indeed 'crashing', is anything showing in the Windows Event viewer on either the Primary or Secondary?

Does anything show for connections there if this is enabled on the Secondary:

Does the Secondary has 2 video cards - one integrated perhaps?

Is it at all possible to share a link to a video of the whole process (shared linked to Google Drive, OneDrive, DropBox, etc)?

Sean Drohan
Stardock Support Manager

Secondary has 2 video ports on the motherboard only: HDMI and DisplayPort (using HDMI).  I could try capturing video of the process.  For some reason the Secondary is currently unresponsive, I will check it out after I reboot it.

Primary is reporting two errors in the Application Event Log:

Faulting application name: MPRDP64.exe, version: 3.0.90.0, time stamp: 0x59760b1d

Faulting module name: KERNELBASE.dll, version: 10.0.18362.628, time stamp: 0xf96f12ee

Exception code: 0xc06d007e

Fault offset: 0x000000000003a839

Faulting process id: 0x1128

Faulting application start time: 0x01d674d51c936189

Faulting application path: C:\Program Files (x86)\Stardock\Multiplicity\MPRDP64.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: 86f7e310-7ca8-455c-98c1-1c88abde42b8

Faulting package full name: 

Faulting package-relative application ID: 

The second error is 2 seconds later:

Fault bucket 1255539194435416573, type 4

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: MPRDP64.exe

P2: 3.0.90.0

P3: 59760b1d

P4: KERNELBASE.dll

P5: 10.0.18362.628

P6: f96f12ee

P7: c06d007e

P8: 000000000003a839

P9: 

P10: 

Attached files:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER62B7.tmp.dmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER63B2.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6430.tmp.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER643D.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER646D.tmp.txt

These files may be available here:

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MPRDP64.exe_56b2263f5c7827f0a31e19d7c55cac29ed717cf_44d5ae03_42dd6c95-f0e5-48a1-b89e-8c4cc212d44a

Analysis symbol: 

Rechecking for solution: 0

Report Id: 86f7e310-7ca8-455c-98c1-1c88abde42b8

Report Status: 268435456

Hashed bucket: 0f9828d258ae9d97716c923ec5e731fd

Cab Guid: 0

I turned on the Logging to the Event Log on the secondary, and although I see some other Informational stuff in the Application Log, the only one I see directly relating to Multiplicity is:

The description for Event ID 257 from source Multiplicity cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

KVM connection initiated by 10.0.0.204, internal port: 18049

Video of me trying to connect from Primary to Secondary:

https://www.dropbox.com/s/n5ty6rkvrjojeim/Multiplicity-2020-08-17-15-09.wmv

Does it help to know that the Primary has 3 monitors, two DVI on an external video card, and one via a DVI-to-USB adapter?  I also have Fences 3 installed, which had crashed when I recorded the video, but the results were identical to previous runs (so, Fences in a crashed or non-crashed state wasn't a determinant.)

Thank you for the information.

What we would like to do is see that it is not a 3rd party app conflict.  While laborious, the most effective way to do this is a clean boot:

https://forums.stardock.com/486104/multiplicity-support-faq#cleanboot

Again, this would need to be done on each box.

We would also like the exact OS builds for each box (winver.exe).

Thank you for your time, effort, and patience.

Sean Drohan
Stardock Support Manager

The Primary is Version 1909 (OS Build 18363.657).  The Secondary is Version 1909 (OS Build 18363.959).

Yes, the Clean Boot is arduous, and not at all like the Shift-F8 process of yesteryear.  My Secondary is in a Clean Boot state, with a new Admin-level account, no dependencies, and no firewall (still remains that way even now, no reason to put it back yet). 

My Primary is my main development machine, and Clean Boot into a separate new Admin-level account proved troublesome, as the new account, though an "Admin account", didn't have access to many of the files and services that my main account does, and I could not get the Multiplicity service to run.  I tried running the mpRestart batch, and it just kept opening and closing new windows, each displaying "Requesting administrative privileges..."  At least when logged in as my main domain user, in a "Clean Boot" state, I could access Multiplicity.

In this state (Secondary: Clean Boot, Clean Admin-level account and Primary: Clean Boot, My Normal Domain Admin account), the symptoms were the same: Seamless mode works flawlessly, KVM mode doesn't result in any window that grants control of the Secondary, although a message does appear in the Notification tray indicating that the Primary has control of the Secondary.  On the Secondary, the only logging I can see is in the EventViewer Application logs, indicating Event 275, although I did see one actual error in Multipl2.exe logged.  In the most "clean" format, my screen recording software wouldn't run, although the results were identical to what has already been sent.

Are there any log files stored anywhere on the Primary or the Secondary that would be helpful in this case?

Can you RDP to the 2nd PC?

Sean Drohan
Stardock Support Manager

I would like to have you try another (PITA) process as we really need to see if anything new in 3.5 (just released) is the cause.  We did not change anything for KVM for 3.5 but we have to be certain.

Again, this is not a fun process, we are sorry for it, but it would be a purge on each PC, reboot, and an install of this 3.44 build:

Purge:
https://cdn.stardock.us/support/uploads/Purge_MP-New.zip

3.44 install:
https://cdn.stardock.us/support/uploads/Multiplicity_3.44_setup_sd.exe

If this too fails, we might have you attempt to attach a debugger to see what it catches.  Have you used Windbg and somewhat comfortable with it?

Again, we appreciate the time and effort.

Sean Drohan
Stardock Support Manager

Having the same problem evaluating Multiplicity V3.5, ie secondary computers apparently connecting but not opening a desktop on the primary computer. 

After uninstalling and purging V3.5 then installing V3.44 was able to connect to the secondary computer immediately without any problems.  They are both running Windows 10 home 2004 build 19041.450 with Norton Security.  They are also on the same subnet, one connecting via ethernet and one on wifi.

Judy

Are you also seeing actual MP crashes in your event viewer as reported here?

https://forums.stardock.com/501231/get;3786231

Sean Drohan
Stardock Support Manager

Very similar:

Log Name:      Application

Source:        Application Error

Date:          16/08/2020 7:18:33 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      xxxxxxx

Description:

Faulting application name: MPRDP64.exe, version: 3.0.90.0, time stamp: 0x59760b1d

Faulting module name: KERNELBASE.dll, version: 10.0.19041.423, time stamp: 0xed02c0bc

Exception code: 0xc06d007e

Fault offset: 0x0000000000023e49

Faulting process ID: 0x2140

Faulting application start time: 0x01d673ae364a24d9

Faulting application path: C:\Program Files (x86)\Stardock\Multiplicity\MPRDP64.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report ID: 21553071-d84a-47eb-b5d2-5b5b5de9bb40

Faulting package full name: 

Faulting package-relative application ID: 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>100</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2020-08-16T09:18:33.6316598Z" />

    <EventRecordID>10128</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>Application</Channel>

    <Computer>xxxxxx</Computer>

    <Security />

  </System>

  <EventData>

    <Data>MPRDP64.exe</Data>

    <Data>3.0.90.0</Data>

    <Data>59760b1d</Data>

    <Data>KERNELBASE.dll</Data>

    <Data>10.0.19041.423</Data>

    <Data>ed02c0bc</Data>

    <Data>c06d007e</Data>

    <Data>0000000000023e49</Data>

    <Data>2140</Data>

    <Data>01d673ae364a24d9</Data>

    <Data>C:\Program Files (x86)\Stardock\Multiplicity\MPRDP64.exe</Data>

    <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>

    <Data>21553071-d84a-47eb-b5d2-5b5b5de9bb40</Data>

</Event>

2 seconds later:

Fault bucket 1597307716408504578, type 4

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: MPRDP64.exe

P2: 3.0.90.0

P3: 59760b1d

P4: KERNELBASE.dll

P5: 10.0.19041.423

P6: ed02c0bc

P7: c06d007e

P8: 0000000000023e49

P9: 

P10: 

etc

Judy

Closing the following like threads and directing them here:

https://forums.stardock.com/501204

https://forums.stardock.com/501180/

For all here with the issue, how many CPU cores do your Secondaries have?

Also, on the Primary PC, if you go to:

C:\Program Files (x86)\Stardock\Multiplicity  (btw, VERY important that MP is installed in that default location).

And run: MPRDP.exe (not MPRDP64.exe) manually (double click),

Can you then connect without it crashing?

Sean Drohan
Stardock Support Manager

I have Multipplicy Pro 3.5 Build 00096.kvmpro, installed on 6 computers (5 Windows 10 Pro, 2004; 1 Server 2016).  One of the WIn 10 machines is primary; all others are secondary.   The program works perfectly on 4 of the 5 secondary machines.

The 5th machine is another story.  I can connect to it and I can send it a Ctrl+Alr+Del, to which the machine responds aw well as to any other keystrokes such as entering a password following the three-key salute.  However, there is nothing displayed on the primary computer, the screen remains blank.  

I have removed Multiplicity from the computer, removed it from the list of computers on the primary computer, and then installed the software and added it back into the list of computers on the primary machine.   All this has made no difference at all.

The computer in question is an HP Z-Book 15 G3 (a laptop), i7-6700HQ, 16 GB RAM and 369 GB of free disk space.  All drivers are up to date per HP's softpaq manager.   It has two onboard/built-in video cards, an Intel HD Graphics 530 and an Nvidia Quadro M1000M.   No external monitors now or ever.

I have found this problem goes away if I change the BIOS to use only the Nvidia "card".    This is not a fix because I lose the power savings of the machine using the Intel "card" for undemanding/light display tasks.

I had this same problem with the previous release of Multiplicity (3.44) and hoped it would be resolved with 3.5.  No such luck.

Thank you.

4 cores

The program IS installed in C:\Program Files (x86)\Stardock\Multiplicity on both computers

I do not - and never have had - any problems with the program crashing on either computer. 

This is why this thread is NOT appropriate for my issue.
Formatting removed by admin

Posting for reference from other thread - what is relevant:

Quoting sdRohan, reply 14

I want to have you try a new file.

On the Secondary, open 'Services' and shut down Multiplicity:



DL this file:
https://cdn.stardock.us/support/uploads/MultiPLV64.zip

Unzip and replace the one here - again, only on the Secondary in question:
\Program Files (x86)\Stardock\Multiplicity

Start the MP service again.

Try to connect from the Primary.

Let me know, please.

Sean Drohan
Stardock Support Manager

End of sdRohan's quote

Re: Reply #21 August 27, 2020 1:00:58 PM from Stardock Forums

So where does this leave this issue?   I have answered your questions and tried that file - which made no difference.

It means we evaluate what to do next and work with you when we have a plan, Mike.  I posted that here so the devs have a place where the information is aggregated. 

Our primary concern is the crashing, however; it is what we will address first. I am working with the devs to work on something for those that are having it to try.

Thank you for your patience.

Sean Drohan
Stardock Support Manager

I certainly understand that crashing has to be the priority but I don't have crashes, just a blank screen. 

By way of reminder, I have an HP Zbook G3 laptop.  The machine has Intel 530 graphics built-in as well as a discrete Nvidia Quadro M1000M.  In its two of the three graphics settings in the BIOS (auto and hybrid), the machine apparently uses the Intel sometimes and sometimes the Nvidia.  It does this automatically and transparently and there is no external monitor involved.   Both the Intel 530 and Nvidia M1000M show up in Device Manager.  

However, this seems to befuddle Multiplicity.  With either of these BIOS graphics settings, I can connect to the laptop from my primary computer without any problems and the laptop responds correctly to any inputs from the primary (Ctrl+Alt+Del; typing in a password; etc.).   Unfortunately, the window on the primary computer where I should see the ZBook's screen remains blank.   There are no crashes on either machine and the primary computer can connect to the other secondary machines (4 of them) with no problem.

If I set the Zbook BIOS graphics option to Discrete, everything works perfectly.  Only the Nvidia M1000M shows up in Device Manager with this BIOS setting.

I have a similar problem. Windows 10 2004 build 19041 on both machines, Primary Laptop connects to Secondary Desktop. IF the secondary has a monitor attached, it works fine. If there is no monitor on the secondary then it connects and I have a black screen on the secondary.

RDP works fine.

I was using the desktop as the primary previously and switched, it worked perfectly before (I switched because I needed to repurpose my monitor for a short time for someone else to work from home). I activated Multiplicity on the Laptop as primary, and changed the desktop to secondary. I rebooted the Desktop with the monitor disconnected to see if that would work, no luck.

Help is needed and appreciated!