Driver Fails to process changes - An unexpected error occurred in the publisher channel

  • Document ID:7023822
  • Creation Date:15-Apr-2019
  • Modified Date:16-Apr-2019
    • Micro Focus Products:
      Identity Manager

Environment

Identity Manager 4.7
Identity Manager Driver - Salesforce

Situation

Salesforce driver starts, but gets a "An unexpected error occurred in the publisher channel" error, and does not process events in the publisher channel.

[04/12/19 12:46:59.856]:Salesforce PT:Receiving DOM document from application.
[04/12/19 12:46:59.857]:Salesforce PT:
<nds dtdversion="2.0">
  <source>
    <product build="20180222_0611" instance="Salesforce" version="4.1.0.0">NetIQ Identity Manager Driver for Salesforce.com</product>
    <contact>NetIQ Corporation</contact>
  </source>
  <input>
    <status level="fatal" type="heartbeat">An unexpected error occurred in the publisher channel: </status>
  </input>
</nds>

Resolution

Delete the driver cache files resolved the issue.

You will need to know the object ID of the driver to verify the cache files are cleared.  One way to do this is to look at the cache files, then disable the driver and see what file disappears.   Then make sure any other files with that name (.p, .t) files if there are any are removed.   Additionally, see if there are any files with the driver name itself in the directory and delete them, then start the driver and see if the issue still occurs.

Here are some instructions.

1.  Get a directory listing of the .TAO files in the /var/opt/novell/eDirectory/data/dib directory
ll  /var/opt/novell/eDirectory/data/dib/*.TAO

2.  Stop and disable the salesforce.com driver.

3.  Get another directory listing and see what .TAO file was removed.   For example 12345.TAO is no longer there.

4.  Delete any files in the  /var/opt/novell/eDirectory/data/dib directory with driver object ID.  12345.*

5.   Additionally, see if there are any files in the  /var/opt/novell/eDirectory/data/dib directory with the drivername and remove them as well.   (copy them to the tmp directory)
ll <drivername>*

6.   Then see if the driver will start, and see if it gets the same error.

WARNING!   Be very careful not to delete other files in the dib directory.   Deleting other files in the dib directory can cause corruption in eDirectory.

Cause

There was a corrupted query cache file.