Multiplicity 4 beta 2 keeps going back to Welcome to Multiplicity when I open configuration

Hello,
Sorry to hear you are having issues. Please try this uninstall multiplicity 3 from all 4 system, reboot, install Multiplicity 4 on all system. Reboot again, retest it and report back.

Thank you.
Basj,
Stardock Community Assistant.

Successfully updated karma reason!

Did a clean install and still having issues with the same computers. When it a clean install it will always ask for activation or purchase or try and no encryption key will get saved.

Successfully updated karma reason!

Found a workaround for now. Here is what I did.

1. Uninstall Multiplicity from the computers with the issue

2. Reinstall Version 3.6 and configure the encryption key and password.

3. Install Version 4 Beta 2

4. On the working secondary computer configure the keys, password and seamless display settings and backup the configuration.

5. Restore the backup on to the problematic computers.

Only one computer still prompts select primary or secondary but all configuration are still intact. Hope there will be fix in the next builds

Successfully updated karma reason!

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+674

Quoting DARKONE33,

reply 3

Found a workaround for now. Here is what I did.

1. Uninstall Multiplicity from the computers with the issue

2. Reinstall Version 3.6 and configure the encryption key and password.

3. Install Version 4 Beta 2

4. On the working secondary computer configure the keys, password and seamless display settings and backup the configuration.

5. Restore the backup on to the problematic computers.

Only one computer still prompts select primary or secondary but all configuration are still intact. Hope there will be fix in the next builds

We have what we believe is a fix for older CPU installs and the settings issue. If you can recreate the conditions for it to fail for you, I would like to PM you a link to that build for testing.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Quoting sdrohan,

reply 5

Quoting DARKONE33,

reply 3

Found a workaround for now. Here is what I did.

1. Uninstall Multiplicity from the computers with the issue

2. Reinstall Version 3.6 and configure the encryption key and password.

3. Install Version 4 Beta 2

4. On the working secondary computer configure the keys, password and seamless display settings and backup the configuration.

5. Restore the backup on to the problematic computers.

Only one computer still prompts select primary or secondary but all configuration are still intact. Hope there will be fix in the next builds

We have what we believe is a fix for older CPU installs and the settings issue. If you can recreate the conditions for it to fail for you, I would like to PM you a link to that build for testing.

Sean Drohan
Stardock Product Lifecycle Manager

Please PM the link and I can run the test

Successfully updated karma reason!

Quoting sdrohan,

reply 5

We have what we believe is a fix for older CPU installs and the settings issue. If you can recreate the conditions for it to fail for you, I would like to PM you a link to that build for testing.

Sean Drohan
Stardock Product Lifecycle Manager

I have tested the fix buy recreating the conditions and was able to setup/configure as normal. No more prompt to activate and all settings are getting saved.

Regarding issue from

https://forums.stardock.com/531853/get;3949242/Multiplicity-4-beta-2-KVM-slow

The fix resolved most of the issue like random disconnection and lockups. The speed did get better but compared to version 3 response rate is very slow, around 5 to 10 seconds and multiple flickers and pixilation.

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+674

Quoting DARKONE33,

reply 7

response rate

I suspect you mean 'refresh rate', or how KVM is redrawing the remote. I would encourage you to experiment with the KVM setting for such things

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Quoting sdrohan,

reply 8

Quoting DARKONE33,

reply 7

response rate

I suspect you mean 'refresh rate', or how KVM is redrawing the remote. I would encourage you to experiment with the KVM setting for such things

Sean Drohan
Stardock Product Lifecycle Manager

It started to work for few minutes in High completion > Lossy compression in the meddle > update thumbnails often. Then it flickered and now its back to sluggish refresh rate. I tired Restarted multiplicity, rebooted computer but cant getting it to work again.

Also will get random lock of mouse and keyboard for few seconds.

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+674

Quoting DARKONE33,

reply 9

It started to work for few minutes in High completion > Lossy compression in the meddle > update thumbnails often. Then it flickered and now its back to sluggish refresh rate. I tired Restarted multiplicity, rebooted computer but cant getting it to work again.

Also will get random lock of mouse and keyboard for few seconds.

If either PC is on a wireless connection, please try wired if possible.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Its is wired, there is no network issue. I can remote in through other mean and it works fine without any lags.

Successfully updated karma reason!

I suspect given the symptoms that the Multiplv* process is crashing out on the secondary computer. If you look in Windows event log do you see lots of errors?

Successfully updated karma reason!

Quoting Neil Banfield,

reply 12

I suspect given the symptoms that the Multiplv* process is crashing out on the secondary computer. If you look in Windows event log do you see lots of errors?

I don’t see any errors pertaining to Multiplicity on the secondary but see couple in the primary.

Application error Event ID 1000 & 1002

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+674

This is always a tough ask (as its a bit of work) but to the get the most detailed data for any crash, we would very much like dumps from your PC when it happens.

This is what you would do to get them for the crash on the Primary:

https://support.stardock.com/space/SHC/1347321935/Manually+Collecting+Start+Crash+Dumps (that is in the Start11 section but the process is the same)

Again, if you don't have the time or patience for it, we understand put any help there would be most appreciated.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

I might be able to work on it this weekend

Quoting sdrohan,

reply 14

This is always a tough ask (as its a bit of work) but to the get the most detailed data for any crash, we would very much like dumps from your PC when it happens.

This is what you would do to get them for the crash on the Primary:

https://support.stardock.com/space/SHC/1347321935/Manually+Collecting+Start+Crash+Dumps (that is in the Start11 section but the process is the same)

Again, if you don't have the time or patience for it, we understand put any help there would be most appreciated.

Sean Drohan
Stardock Product Lifecycle Manager

I might be able to work on it this weekend.

Thanks

Successfully updated karma reason!

Here is an update on KVM lag and lockups.

I was able to get is work with default setting, after rebooting the primary & the secondary. Doing more testing I was able to Triger the issue on command.

1. Opening and configuring Multiplicity on the primary computer causes the KVM to lag, lock up, or crash. This happens less frequently when configuring occasionally, but continuous configuration and setting changes, as I was doing seams to trigger the lag, lock up, and crash. Once the issue occurs, I have to reboot both the primary and secondary computers to restore normal functionality.

2. Using the side bar seams to trigger the issue every time Once you close the side bar it goes back to normal.

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+674

Quoting DARKONE33,

reply 16

Here is an update on KVM lag and lockups.

I was able to get is work with default setting, after rebooting the primary & the secondary. Doing more testing I was able to Triger the issue on command.

1. Opening and configuring Multiplicity on the primary computer causes the KVM to lag, lock up, or crash. This happens less frequently when configuring occasionally, but continuous configuration and setting changes, as I was doing seams to trigger the lag, lock up, and crash. Once the issue occurs, I have to reboot both the primary and secondary computers to restore normal functionality.

So this only happens when you have an active KVM connection and you are making 'continuous configuration and setting changes'. I can imagine a case where having an active KVM connection could very much cause issues if you are changing the characteristics of how the connections should function.

I suspect you cannot reproduce this (#1) without an active KVM connection, correct?

Did you attempt to use WinDBG to create a dump for the crash?

Neil: If this proves true, perhaps a queue for 'pending changes' for active KVM connections?

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Quoting sdrohan,

reply 17

I suspect you cannot reproduce this (#1) without an active KVM connection, correct?

Did you attempt to use WinDBG to create a dump for the crash?

Neil: If this proves true, perhaps a queue for 'pending changes' for active KVM connections?

Sean Drohan
Stardock Product Lifecycle Manager

Doing more deep diving over the weekend, It seams all ties in with the sidebar. So #1 it can be disregarded and change to if any time a sidebar was used and continuous configuration and setting changes are done it will crash Multiplicity.

I do have dump from WinDBG. I can PM the link to download it.

Thanks,

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+674

Quoting DARKONE33,

reply 18

Doing more deep diving over the weekend, It seams all ties in with the sidebar. So #1 it can be disregarded and change to if any time a sidebar was used and continuous configuration and setting changes are done it will crash Multiplicity.

I do have dump from WinDBG. I can PM the link to download it.

You are confusing us here a bit, Dark...

Define for us: 'continuous configuration and setting changes'. What are you doing and where?
Have an active KVM connection open: Yes \ No?
Have the KVM sidebar open: Yes \ No?
Have the KVM sidebar open, an active KVM connection running, and make 'continuous configuration and setting changes': Yes \ No?

Yes, you can PM me any link to any dumps you have collected.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Quoting sdrohan,

reply 19

You are confusing us here a bit, Dark...

Define for us: 'continuous configuration and setting changes'. What are you doing and where?
Have an active KVM connection open: Yes \ No?
Have the KVM sidebar open: Yes \ No?
Have the KVM sidebar open, an active KVM connection running, and make 'continuous configuration and setting changes': Yes \ No?

This issue stemmed after upgrading from V3 to V4 bata2 and then to beta 3, I thought it fixed the lag issue.

1. Assumed trying to change the KVM setting Compression, Lossy compression and Global KVM display scaling and never used sidebar.

Currently as long as I don't change it to low compression I have no issue. even if changing it to Low compression It will just pixelate and lag and resetting back to default it will go away. Regardless having KVM open or not.

2. Using the sidebar

Soon I use the sidebar I will get the lag and once i close it it will go back to normal.
While the sidebar is closed and then change any of the KVM setting and then open sidebar to see if fix the issue. At first it does not make any difference any combination of the KVM setting. Repeating this step eventually it will make the Multiplicity crash and once that happens, I have to reboot both primary and secondary. (This will still have the same results having the sidebar open wile changing the KVM settings)

For now, I'm not using the sidebar, and it’s been working.

Successfully updated karma reason!

Quoting DARKONE33,

reply 20

Quoting sdrohan,

reply 19

You are confusing us here a bit, Dark...

Define for us: 'continuous configuration and setting changes'. What are you doing and where?
Have an active KVM connection open: Yes \ No?
Have the KVM sidebar open: Yes \ No?
Have the KVM sidebar open, an active KVM connection running, and make 'continuous configuration and setting changes': Yes \ No?

This issue stemmed after upgrading from V3 to V4 bata2 and then to beta 3, I thought it fixed the lag issue.

1. Assumed trying to change the KVM setting Compression, Lossy compression and Global KVM display scaling and never used sidebar.

Currently as long as I don't change it to low compression I have no issue. even if changing it to Low compression It will just pixelate and lag and resetting back to default it will go away. Regardless having KVM open or not.

2. Using the sidebar

Soon I use the sidebar I will get the lag and once i close it it will go back to normal.

While the sidebar is closed and then change any of the KVM setting and then open sidebar to see if fix the issue. At first it does not make any difference any combination of the KVM setting. Repeating this step eventually it will make the Multiplicity crash and once that happens, I have to reboot both primary and secondary. (This will still have the same results having the sidebar open wile changing the KVM settings)

For now, I'm not using the sidebar, and it’s been working.

How fast is your network as low compression needs a very very fast network?

Successfully updated karma reason!

Quoting Neil Banfield,

reply 21

How fast is your network as low compression needs a very very fast network?

Not using Low compression - for now its stable at defaults just as long I do not use the sidebar.

Current setting

Using sidebar no matter what configuration standard or high doesn't matter, always going to lag and eventually crash if to many attempts on trying to change the compression (excluding low completion my network is not fast enough) going back and forth between standard and high. Also charging Lossy compression slider bars to worst to better or update thumbnails to often to rarely.

Successfully updated karma reason!