KB: The Server App-V sequencing process fails with "The Sequencer could not stop the MSIServer service"
Here’s a new KB we published on an issue in App-V where the sequencer errors out and package creation fails. We’ve seen this a few times and it basically comes down to not having all the latest updates applied to the sequencing computer so the fix is pretty straight forward. You can read the entire article here:
2790852 - The Server App-V sequencing process fails with "The Sequencer could not stop the MSIServer service"(https://support.microsoft.com/kb/2790852)
J.C. Hornbeck | Knowledge Engineer | Management and Security Division
Get the latest System Center news on Facebook and Twitter :
System Center All Up: https://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: https://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: https://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: https://blogs.technet.com/momteam/
System Center – Service Manager Team blog: https://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: https://blogs.technet.com/scvmm
Windows Intune: https://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: https://blogs.technet.com/sus/
The AD RMS blog: https://blogs.technet.com/b/rmssupp/
App-V Team blog: https://blogs.technet.com/appv/
MED-V Team blog: https://blogs.technet.com/medv/
Server App-V Team blog: https://blogs.technet.com/b/serverappv
The Forefront Endpoint Protection blog : https://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : https://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: https://blogs.technet.com/b/isablog/
The Forefront UAG blog: https://blogs.technet.com/b/edgeaccessblog/
Comments
Anonymous
January 01, 2003
Brilliant article, the batch file resolved this annoying issue, thank you a lot!Anonymous
January 01, 2003
Brilliant article, the batch file resolved this annoying issue, thank you a lot!