Highlighted
Super Contributor.
Super Contributor.
254 views

Error in MDAD Driver - Subscriber

Jump to solution

[03/23/20 21:21:58.516]:MDAD ST: DirXML Log Event ------------------- Driver: \********\system\IDM-DriverSet\MDAD Driver Channel: Subscriber Status: Retry Message: Code(-9006) The driver returned a "retry" status indicating that the operation should be retried later. Detail from driver: Code(-9006) The driver returned a "retry" status indicating that the operation should be retried later. Detail from driver: NA worker initializing, state: WAITING

 

Publisher is working as expected 

Subscriber is alone not working 

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Knowledge Partner
Knowledge Partner
It can be an issue with the "corrupted" TAO file.

-9006 for Notes Driver

Admin observed one of the following errors:
Message: Code(-9006) The driver returned a "retry" status indicating that the operation should be retried later. Detail from driver: Unable to locate note from UNID. Notes Exception ID = 4063. Message: Database <server name>!!names.nsf has not been opened yet
<status event-id="#20040930154447#1#8" level="retry">Unable to locate note from UNID. Notes Exception ID = 4091. Message: Invalid universal id</status>

While this happened, the server's TAO cache file grew as subscriber transactions backed-up.

or very old CS
https://www.novell.com/coolsolutions/feature/14710.html

Error 9006

This is the most common error you will see. Here are the details:

DriverName ST:
DirXML Log Event -------------------
Driver: \TreeName\acme\scs\DriverSetName\DriverName
Channel: Subscriber
Status: Retry
Message: Code(-9006) The driver returned a "retry" status indicating
that the operation should be retried later. Detail from driver: No connection
to remote loader
Likely Cause: The DirXML remote loader is not connecting. Usually you'll see this after the ADServer has rebooted to apply a Critical Update.

Solution: Check on the ADServer, via RDP or in person, at the Service called DirXML Loader. It is set to autoload, but make sure it does load. Sometimes it does not start after a server reboot.

The other common issue you will see is that the password on the 'RemoteLoaderUser' account gets changed in AD. You can reset it in AD, via the MMC, and try to restart the driver in iManager).

To control the AD Driver, use iManager on eDirServer at: https://eDirServer.acme.com/nps/iManager.html. Make sure you log in with an account that has sufficient priveleges and roles to manage the IDM Driver Sets. Then watch the trace to see what happens.

View solution in original post

0 Likes
3 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Could you provide a bigger part of the trace?

Where exactly you have this error and when?

When did the driver start? When you have an add/query/modification event?

When the driver tried to connect to the remote loader? etc

 

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner
It can be an issue with the "corrupted" TAO file.

-9006 for Notes Driver

Admin observed one of the following errors:
Message: Code(-9006) The driver returned a "retry" status indicating that the operation should be retried later. Detail from driver: Unable to locate note from UNID. Notes Exception ID = 4063. Message: Database <server name>!!names.nsf has not been opened yet
<status event-id="#20040930154447#1#8" level="retry">Unable to locate note from UNID. Notes Exception ID = 4091. Message: Invalid universal id</status>

While this happened, the server's TAO cache file grew as subscriber transactions backed-up.

or very old CS
https://www.novell.com/coolsolutions/feature/14710.html

Error 9006

This is the most common error you will see. Here are the details:

DriverName ST:
DirXML Log Event -------------------
Driver: \TreeName\acme\scs\DriverSetName\DriverName
Channel: Subscriber
Status: Retry
Message: Code(-9006) The driver returned a "retry" status indicating
that the operation should be retried later. Detail from driver: No connection
to remote loader
Likely Cause: The DirXML remote loader is not connecting. Usually you'll see this after the ADServer has rebooted to apply a Critical Update.

Solution: Check on the ADServer, via RDP or in person, at the Service called DirXML Loader. It is set to autoload, but make sure it does load. Sometimes it does not start after a server reboot.

The other common issue you will see is that the password on the 'RemoteLoaderUser' account gets changed in AD. You can reset it in AD, via the MMC, and try to restart the driver in iManager).

To control the AD Driver, use iManager on eDirServer at: https://eDirServer.acme.com/nps/iManager.html. Make sure you log in with an account that has sufficient priveleges and roles to manage the IDM Driver Sets. Then watch the trace to see what happens.

View solution in original post

0 Likes
Highlighted
Visitor.

Most probably the domain controller configured for domain "NA" is not responsive. The driver would attempt for sometime to connect to it before falling back on other back up/secondary domain controllers that one would have configured in the driver configuration. 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.