App-V 5.1 Sequencer: "time out has expired or operation has not been completed"

-
If you run across this error in the App-V Sequencer check the Event Log for AppV - Sequencer - Operational. You will probably find that the sequencer was not stopping a service (in my case it was the windows update service). It will show as "stopping". Set the service to disabled and then reboot. That should fix it.

Comments

Post a Comment

Popular posts from this blog

Windows 10 Upgrade - Panther Logs - Locations

-
Where the heck is the #($*@(*#$# panther logs? Logfile location Description $windows.~bt\Sources\Panther Log location before Setup can access the drive. $windows.~bt\Sources\Rollback Log location when Setup rolls back in the event of a fatal error. %WINDIR%\Panther Log location of Setup actions after disk configuration. %WINDIR%\Inf\Setupapi .log Used to log Plug and Play device installations. %WINDIR%\Memory.dmp Location of memory dump from bug checks. %WINDIR%\Minidump.dmp Location of log minidumps from bug checks. %WINDIR%\System32\Sysprep\Panther Location of Sysprep logs.
Read more

Unable to open Start or Search after Window 7 to Windows 10 1809 Upgrade

-
Image
This one was a real head scratcher. After upgrading from Windows 7 to Windows 10 1809, you could not open the Start Menu. When you would click on it, nothing would happen. You could also not perform a search. I saw in the System event log: "The server Microsoft.Windows.ShellExperienceHost _10.0.17763.1_neutral_neutral_cw5n1h2txyewy! App did not register with DCOM within the required timeout." about every 30 seconds. I noticed the same thing with Cortana. and "The server Microsoft.Windows.Cortana _1.11.6.17763_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXfbn8w4s0jbk3tjevpcn9kaxerc6rby8k.mca did not register with DCOM within the required timeout." I captured a procmon trace and found: Both ShellExperienceHost.exe and SearchUI.exe exit with an error (-1073741790 which is Access Denied) as soon as they try to load sysfer.dll (part of Symantec Endpoint Protection). See https://support.symantec.com/us/en/article.TECH252314.html Evidently, sysf...
Read more

Moving KMS to a New Server

-
In this guide, I'll take you through the process of uninstalling a Key Management Service (KMS) host key and then installing it on a new server, step-by-step. Step 1: Uninstall the KMS Host Key To remove the current KMS host key from the server, run the following command: cscript.exe C:\windows\system32\slmgr.vbs -upk This command will uninstall the KMS host key. Step 2: Install the Default KMS Key Install the default KMS key by running the following command: cscript.exe C:\windows\system32\slmgr.vbs /ipk [KMS Client Setup Key] You can find the default KMS client setup keys here. Step 3: Delete the Record from DNS Open the DNS console and expand the _tcp node under the domain.com. You'll see a record called _VLMCS. Delete this record. Now, the KMS server is uninstalled. Step 4: Install KMS on a New Server To install KMS on a new server, enter the following command: cscript.exe C:\windows\system32\slmgr.vbs /ipk Step 5: Activate the KMS Host Activate the KMS host by entering thi...
Read more