Hello, we want to update from V6.0.322.7 to V7.0.323.2 (Opening PDFs in Sharepoint bug is finally resolved in the current version) via SCCM silent installation and got the same error. The Uninstall routine shuts down explorer.exe and because SCCM uses Local Authority rights to perform installation tasks, it cannot restart explorer.exe which is intended behavior by Microsoft. https://social.msdn.microsoft.com/Forum ... formssetup
the error ”Application SID does not match Conductor SID” will be generated whenever the user account the service is being run under does not match the user account used to launch the setup instance. The term “Conductor” refers to the MSI setup engine. It also appears that if the setup is executed with elevated permissions (Run As Administrator), then the SID check is bypassed. This behavior is by design and is intended to prevent the malicious restarting of critical system services.
I had this issue with a different product before and fixed it by disabling MSIRESTARTMANAGERCONTROL property with Orca and/or deleting the used Dialogs in the MSI file with Orca:https://msdn.microsoft.com/en-us/librar ... 77(v=vs.85
).aspx https://zoomztech.com/2014/07/22/dealin ... -silently/
This is not a good solution because I don´t want to mess with your MSI each time I want to update PDF Exchange Pro. My latest try was using WMIC (wmic product where "vendor like '%%Tracker Software%%'" call uninstall /nointeractive) to uninstall the old Application before. This prevents explorer restarts but unfortunately it restarts the PC if a PDF is open during uninstall. I´m going to try a workaround I found on Google to prevent this: wmic product where "vendor like '%%Tracker Software%%'" call uninstall /nointeractive | wmic && shutdown /a
I think the real solution would be to make it possible to enforce the setup to uninstall PDF exchange and ask for an reboot if there was a file in use instead of terminating the process.
This problem is a big one for us because if you deploy PDF Exchange Pro to >1000 PCs silently you don´t want to fix 1000 crashed explorers and nobody is able to work.
Thanks and regards,