
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Sap Portal Driver Remote Loader issue
Hi there.
IDM: 4.7.3
eDirectory: 9.1.4.1
Sap Portal Driver: 4.0.1.0
I have a freshly out-of-the-oven SAP Portal Driver recently deployed from scratch, when it connects to the application without a Remote Loader it works pretty neat but when i configure it to use a Remote Loader, it explodes in a nasty way.
I have to use a RL(MF's request).
I tried removing some logics and i got that without the NOVLPORTD-ots-SPMLOutputTransform it can connect succesfully with the RL, but if i use that Policy, it just explodes.
Does anybody know what could be happening here with that policy? is there any bug reported or something like that?
This is the error i see in the Trace file using trace level 3.
DirXML Log Event -------------------
Driver: \IDM_TREE\Meta\Services\DriverSet1\SAP_PO_DEV
Channel: Publisher
Status: Fatal
Message: Unable to validate that there is a non-empty driver object password (a Publisher-channel Policy may be incorrect)
[11/04/19 17:42:48.086]:SAP_PO_DEV PT:
DirXML Log Event -------------------
Driver: \IDM_TREE\Meta\Services\DriverSet1\SAP_PO_DEV
Channel: Publisher
Status: Fatal
Message: Code(-9005) The driver returned a "fatal" status indicating that the driver should be shut down. Detail from driver: Unable to validate that there is a non-empty driver object password (a Publisher-channel Policy may be incorrect)<application>DirXML</application>
PD: I checked the passwords multiple times.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Set a Driver object password. Does not need to be used, just needs to be there.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
As i pointed out earlier i did set the driver object password in both RL
and IDM