Deferred Processor Stops after Password Recovery

[Chris]

Deferred Processor Stops after Password Recovery

Rev: 1.5
Date: 01/04/2010

Problem

The deferred processor stops or is no longer running after you recover a password from the password recovery website.

There are no errors or warnings recorded in the host system's application or system logs regarding why the service keeps stopping.

Cause

Cause 1
In versions 4.80 and earlier, there may be a "missing" and unnecessary registry key which causes the Windows Installer to attempt to automatically (and unnecessarily) repair the program installation to add the "missing" registry key.

The same behavior can be duplicated manually by attempting to run an upgrade/repair installation of the program. One of the upgrade/repair steps taken by the installer package is to stop the deferred processor.

Cause 2
The 4.80 version of ERPM introduced a "heartbeat monitor" that would stop jobs that appear to have stalled which was very aggressive in its interpretation of a stalled job. When the hearbeat monitor would kill the job it might kill the processor and could also leave the job in an indeterminate state requiring the job lock to be manually removed by opening the job.

More Information

More Information 1
In the host system's event logs you may see information or warning events with a source of 'MSIInstaller' happening about the same time as the deferred processor stops working.

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 4/23/2009
Time: 11:57:42 AM
User: USERNAME
Computer: COMPUTERNAME
Description:
Detection of product '{DB936339-E9F1-42C8-BA13-3F1BF16C3962}', feature 'Complete', component '{CD9E7ABD-033A-42FE-91B7-1BEAF60FEEA2}' failed. The resource 'HKEY_CURRENT_USER\Software\Lieberman\RPM\Shortcut Name' does not exist.

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 4/23/2009
Time: 11:57:42 AM
User: USERNAME
Computer: COMPUTERNAME
Description:
Detection of product '{GUID_HERE}', feature 'Complete' failed during request for component '{GUID_HERE}'

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11706
Date: 4/23/2009
Time: 11:57:48 AM
User: USERNAME
Computer: COMPUTERNAME
Description:
Product: Random Password Manager -- Error 1706. No valid source could be found for product Random Password Manager. Windows Installer cannot continue.

Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11729
Date: 4/23/2009
Time: 11:57:49 AM
User: USERNAME
Computer: COMPUTERNAME
Description:
Product: Random Password Manager -- Configuration failed.

More Information 2
The job log for the deferred processor as well as the job specific log will note the heartbeat monitor many times and no job completion will be noted at the end of the log/job run.

Resolution:

Resolution 1

1. Download http://ftp.liebsoft.com/forumkbdownl...zap/msizap.exe.
2. Close the application
3. Open a command prompt and navigate the directory where you put msizap.
4. Run the following command: msizap TW {GUID_HERE}
   The GUID required can be found in the MsiInstaller warning with an event ID of 1004 where it says "Detection of product '{GUID_HERE}'"
5. Then try your process again.

OR

This problem is fixed in versions after 4.72. Upgrade to the latest version.

Resolution 2
Determine where you store your system event sinks. This can be done by opening "Configure Event Sinks" from the SETTINGS menu of the management console. On the "Event Sink Definitions" dialog, open "Event Sinks Configuration Files Directory" from the "Event Sink Settings" menu. Note the directory.

Navigate to the directory noted above. Under this directory is a sub-directory called "SystemEventSinks". In this directory is a file called "Proc Heartbeat Failure - Named Pipe.xml". Edit this file and replace its contents with the contents below:

<?xml version="1.0" encoding="UTF-8"?>
<EventSink CompactMode="1" sName="Heartbeat Failure - Named Pipe" sDescription="" sEventOutputType="NamedPipe">
	<EventFilterSettings bMatchApplicationName="1" sApplicationName="Enterprise Random Password Manager Stand-alone Processor" bMatchBasicEventType="0" dwBasicEventType="0" bMatchEventIDRanges="1">
		<listEventIDRanges dwLowValue="16781312" dwHighValue="16781312"/>
	</EventFilterSettings>
	<EventOutput>
	</EventOutput>
</EventSink>

OR

This problem is fixed in versions after 4.80. Upgrade to the latest version.

Applies To:

Random Password Manager (RPM)
Enterprise Random Password Manager (ERPM)