A problem with SafeCom G4 520*03 installed on Cluster causes the Clustered Printspooler resource to fail to start when brought online, or during a Cluster failover.
On the cluster administrator, the problem can be seen as the Clustered Printspooler resource ends in a failed state.

A side effect is that Printspooler crash dump logs are created in the c:\safecom_trace\ folder

The error has been located to the PULL and PUSH port monitor failing to start up correctly when first the local cluster node print spooler service and later the clustered printspooler service start up.

The problem has been identified as a missing registry information in the clustersection, and will be fixed in a coming SafeCom G4 version or updated version of the PULL and PUSH port monitor.

Until a permanent fix is available, the problem can be overcome by manually editing the registry on all clustered nodes.

  1. On the Cluster Administrator take the Clustered Print Spooler resource offline (if the Clustered Print Spooler resource is currently in a failed state, then leave it as it is)
  2. On Cluster node 1, open up registry in “Run as administrator” mode (Eventually do this by clicking, Start, All programs, Accessories, Right click “Command prompt” and choose “Run as administrator”
    Then from command prompt, write C:\regedit <Enter>
  3. In registry go to HKEY_LOCAL_MACHINE\Cluster\Resources\
  4. Within HKEY_LOCAL_MACHINE\Cluster\Resources\, you need to find a subkey that has \Parameters\Monitors\
    Withing\Parameters\Monitors\ locate SafeCom Pull Port\Ports and SafeCom Push Port\Ports
    Example (this is unique for each cluster installation):
    HKEY_LOCAL_MACHINE\Cluster\Resources\092f2994-363e-43da-8311-ebc13622c30b\Parameters\Monitors\SafeCom Pull Port\Ports
  5. Expect that you will need to search a little as, the guid part between \Resources\... and \Parameters\ is a guid that is unique to every cluster installation.

  6. After you have located the sections:
    HKEY_LOCAL_MACHINE\Cluster\Resources\special guid\Parameters\Monitors\SafeCom Pull Port\Ports
    and
    HKEY_LOCAL_MACHINE\Cluster\Resources\special guid\Parameters\Monitors\SafeCom Push Port\Ports
    Verify that the InstallDir string is filled out with the correct filepath to where the SafeCom G4 program is installed.
  7. If the InstallDir string is missing then do the following:
  8. In the right hand side of the registry window, rightclick and chose “New, String Value”
    Type in “InstallDir” as the name, and hit Enter

    Doubleclick the newly created string, and type in the filepath to the Safecom installation

  9. Do this for both sections:
    …… Monitors\SafeCom Pull Port\Ports and
    …… Monitors\SafeCom Push Port\Ports
  10. Make sure that the InstallDir exists and is filled out with the correct filepath to where the SafeCom program is installed.
  11. Repeat the steps on all other Cluster nodes.
  12. When done, take the Clustered PrintSpooler resource online.
  13. Now the Clustered Printspooler resource should after a few attempts end as online
  14. Now perform an ordinary Cluster failover, and verify that the clustered resources can be successfully moved to the other Cluster node, and back again.