Symantec.Cloud SEP SBE.Cloud: Installation Fails Due to "Another Installation is Currently in Progress

Source: https://support.symantec.com/en_US/article.TECH218138.html

Problem

If it is not possible to install SEP SBE due to an error that another installation is in progress, resolution involves clearing out any other pending installations and allowing the SEP SBE installer to proceed with its installation.

Solution

When addressing this type of installation failure, always make sure that no other software is being installed or uninstalled when the SEP installer is running. If no other install service is running, try rebooting the machine and initiating the installation again. If the installation continues to fail reporting that another installer service is running the following process can be attempted, however it is important to note that this solution is unsupported as the recommended alterations do not relate to SEP but rather removing the registry flag which indicates that a microsoft installer process is running.

1. Start the registry editor by navigating to the start menu and clicking "Run", then typing "regedit" and clicking the OK button.
2. Back up the registry by choosing the "Export" option from the "File" menu, make sure to check the "All" radio button under the "Export Range" section, then select a location in which to save the backup and click "Save".
3. Once back in the registry editor, navigate to:
   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Inprogress
4. Delete the Inprogress key (make sure to delete the entire key and not only the values contained within the key).
5. Open the Task Manager.
6. Navigate to the "Process" tab.
7. Search the list for any occurrence of "msiexec.exe", highlight any entries found and click "End Process".
8. Try the installation again.

ASANYs_sem5, Cannot open transaction log file -- No such file or directory

Event Type: Error
Event Source: ASA 9.0
Event Category: None
Event ID: 1
Date:  25/04/2012
Time:  12:47:00
User:  N/A
Computer: 

Description:
The description for Event ID ( 1 ) in Source ( ASA 9.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ASANYs_sem5, Cannot open transaction log file -- No such file or directory.

Whether your SEPM started working ,Otherwise try this

Verify if there is any running instance of dbsrv9 in the Task Manager > Processes tab. If yes, then end that process

Start the Embedded database service. ( If this does not resolve the issue, then follow the steps listed below )

Go to "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\" and rename sem5.log to sem5.log.old

Click Start, click on Run and Type "CMD" then click OK

In the Command Prompt type: "CD C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\" and press Enter this will change directories to the folder containing dbsrv9.exe.

To force the recreation of sem5.log. Type: "dbsrv9 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" and press Enter

Click Start, click on Run and Type "services.msc" then click OK and start the Symantec Embedded Database Service

Start the Symantec Endpoint Protection Manager service