Ending A Windows Installer Transaction Event Id 1042



Ending

  1. Ending A Windows Installer Transaction Event Id 1042 Online
  2. Ending A Windows Installer Transaction Event Id 1042 Code

Feb 04, 2018 event id: 1042 Ending a Windows Installer transaction: D: SysMaint SysMaint Agent-SCOM agent AMD64 MOMAgent.msi. Client Process Id: 4356. Client Process Id: 4356. Event id: 10005. Windows Installer features 'self repair' for installed applications.In essence this means that it will keep checking whether the files on disk and settings in the registry match what the respective package originally installed.

Installer

Ending A Windows Installer Transaction Event Id 1042 Online

How to uninstall VIPRE by Sunbelt Software from Windows

VIPRE, the antivirus program from Sunbelt Software, is a little bit tricky to uninstall. In the Windows XP control panel, “Add/Remove Programs”, or the Windows Vista/Windows 7 control panel, “Programs and Features”, the user is presented with options to re-configure VIPRE, not to uninstall it. The way to go about uninstalling it is a little bit tricky. Let’s walk through it, shall we?

Open the “Add/Remove Programs” or “Programs and Features” control panel, depending on which version of Windows you are running. Select “VIPRE” and attempt to uninstall. The option to uninstall will not be available, but the option to re-configure will be. Select it and let it run through its process. After it is over, close any remaining “VIPRE” windows and close the “Add/Remove Programs” / “Programs and Features control panel.

Open the Event Viewer. You can either go to “Start”–>”Control Panels”–>”Administratrive Tools–> “Event Viewer”–>”Application” or “Start”–>”Control Panels”–>”Administratrive Tools–> “Computer Management”–>”Event Viewer”–>”Application”. You should have an entry for “Event ID 1040″ with the description of “Beginning a Windows Installer transaction: C:WindowsInstallerxxxxx.msi”. It should look similar to the picture below

Ending A Windows Installer Transaction Event Id 1042

The next entry will be for “Event ID 1042″ with the description of “Ending a Windows Installer transaction: C:WindowsInstallerxxxxx.msi”. It should look similar to the picture below.

The next entry will be for “Event ID 11728″ with the description of “Product: VIPRE antivirus — Configuration completed successfully.” It should look similar to the picture below.

Ending A Windows Installer Transaction Event Id 1042

The fourth entry will be for “Event ID 1035″ with the description of “Windows Installer reconfigured the product. Product Name: VIPRE Antivirus. Product Version: 4.0.3904. Product Language: 1033. Manufacturer: Sunbelt Software. Reconfiguration success or error status: 0″. It should look similar to the picture below.

Now, open Windows Explorer and go to C:WindowsInstaller. Look for the file listed in your first and second log entry. In this case, it was 42a97.msi. Double-click to run the file. You will get a dialog box with an uninstall checkbox option. Select “Uninstall” and click OK. You may have to restart after the uninstall is finished.

Ending A Windows Installer Transaction Event Id 1042 Code

As I said, the uninstallation of VIPRE is tricky. You have to go through the Event Log to find the name of the Windows Installer file that can truly uninstall VIPRE for you.

Hope this helps.

Windows

Categorised as:IT Services


Recently i faced the issue while creating a DSN to connect to SQL Server from remote machine. I am getting login failure message and below is the error logged in error log file.
Error: 18456, Severity: 14, State: 12
Login failed for user 'admin'. Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors
1. No issue with login name and password as i am able to connect to SQL Server using SSMS.
2. If we specify sysadmin to the failed login then DSN is creating without any issues.
I have executed the below commands to fix the issue in my environment,
GRANT CONNECT SQL TO 'admin'
GRANT CONNECT ON ENDPOINT::'TSQL Default TCP' TO 'admin'
As a quick resolution you can give sysadmin role to user and create dsn and remove the sysadmin role.