ominin1 Absent Member.
Absent Member.
598 views

Driver for Office 365 does not starts

Hello

I have been working on Driver for Office 365 but the driver always starts whit error.

I did all prerequisites tasks for Office 365 driver and deploy the driver.

And when starting the driver after “Performing operation check-password for .” driver stop whit :

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: No connection to remote loader

<nds dtdversion="4.0" ndsversion="8.x">
<input>
<check-password event-id="This check-password result is expected. It is the result of the shim verifying that the driver object password is non-empty."><!-- content suppressed --></check-password>
</input>
</nds>
[05/28/19 13:14:26.849]:MSOffice365 PT:Filtering out notification-only attributes.
[05/28/19 13:14:26.849]:MSOffice365 PT:Pumping XDS to eDirectory.
[05/28/19 13:14:26.849]:MSOffice365 PT:Performing operation check-password for .
[05/28/19 13:14:26.850]:MSOffice365 PT:--JCLNT-- \IDM_TREE\system\driverset1\MSOffice365 - Publisher : Duplicating : context = 831455370, tempContext = 831455383
[05/28/19 13:14:27.787]:MSOffice365 ST: SubscriptionShim.execute() returned:
[05/28/19 13:14:27.787]:MSOffice365 ST:
<nds dtdversion="4.0" ndsversion="8.x">
<output>
<status event-id="0" level="retry" type="remoteloader">No connection to remote loader</status>
</output>
</nds>
[05/28/19 13:14:27.788]:MSOffice365 ST: Applying input transformation policies.


Full trace file https://pastebin.com/6jnk7a4L

Any help would be greatly appreciated!
Labels (1)
0 Likes
13 Replies
Knowledge Partner
Knowledge Partner

Re: Driver for Office 365 does not starts

On 5/28/2019 6:34 AM, ominin wrote:
>
> Hello
>
> I have been working on Driver for Office 365 but the driver always
> starts whit error.
>
> I did all prerequisites tasks for Office 365 driver and deploy the
> driver.
>
> And when starting the driver after �Performing operation check-password
> for .� driver stop whit :
>
> *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: No connection to remote loader*
>
>
> Code:
> --------------------
> <nds dtdversion="4.0" ndsversion="8.x">
> <input>
> <check-password event-id="This check-password result is expected. It is the result of the shim verifying that the driver object password is non-empty."><!-- content suppressed --></check-password>
> </input>
> </nds>
> [05/28/19 13:14:26.849]:MSOffice365 PT:Filtering out notification-only attributes.
> [05/28/19 13:14:26.849]:MSOffice365 PT:Pumping XDS to eDirectory.
> [05/28/19 13:14:26.849]:MSOffice365 PT:Performing operation check-password for .
> [05/28/19 13:14:26.850]:MSOffice365 PT:--JCLNT-- \IDM_TREE\system\driverset1\MSOffice365 - Publisher : Duplicating : context = 831455370, tempContext = 831455383
> [05/28/19 13:14:27.787]:MSOffice365 ST: SubscriptionShim.execute() returned:
> [05/28/19 13:14:27.787]:MSOffice365 ST:
> <nds dtdversion="4.0" ndsversion="8.x">
> <output>
> <status event-id="0" level="retry" type="remoteloader">No connection to remote loader</status>
> </output>
> </nds>
> [05/28/19 13:14:27.788]:MSOffice365 ST: Applying input transformation policies.


This is possibly one of the worst mistakes the original designers of IDM
made. A driver object requires a password, even if you are not using it.

So they check. If it comes back empty, error. If it comes back with
wrong password, then it shows this error which notes, THIS IS EXPECTED.

Not your error.

Your problem is earlier:

<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Advanced" version="4.7.2.0">DirXML</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status level="retry">Code(-9006) The driver returned a "retry"
status indicating that the operation should be retried later. Detail
from driver: No connection to remote loader</status>
</output>
</nds>
[05/28/19 13:14:27.800]:MSOffice365 ST:Stopping driver due to an error
in Startup policies.
[05/28/19 13:14:27.800]:MSOffice365 ST:
DirXML Log Event -------------------
Driver: \IDM_TREE\system\driverset1\MSOffice365
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: No connection
to remote loader
[05/28/19 13:14:27.801]:MSOffice365 ST:Requesting termination.
[05/28/19 13:14:27.808]:MSOffice365 ST:Starting event loop.
[05/28/19 13:14:27.808]:MSOffice365 ST:Leaving event loop.
[05/28/19 13:14:27.809]:MSOffice365 ST:Shutting down DirXML driver
\IDM_TREE\system\driverset1\MSOffice365.
[05/28/19 13:14:27.809]:MSOffice365 ST:No shutdown policies.
[05/28/19 13:14:27.809]:MSOffice365 ST:Remote Interface Driver:
Notifying publisher t
o shutdown.



Error is Startup policies. Reading earlier:

[05/28/19 13:14:26.485]:MSOffice365 ST:Exception occured while
restricting permission for :
/var/opt/novell/eDirectory/data/dib/dx35154. Reason : insufficient space
(-1)

This might be the actual cause...


0 Likes
ominin1 Absent Member.
Absent Member.

Re: Driver for Office 365 does not starts

Hi
Thanks for answer

geoffc;2500291 wrote:
On 5/28/2019 6:34 AM, ominin wrote:

Error is Startup policies. Reading earlier:

[05/28/19 13:14:26.485]:MSOffice365 ST:Exception occured while
restricting permission for :
/var/opt/novell/eDirectory/data/dib/dx35154. Reason : insufficient space
(-1)

This might be the actual cause...


It is strange error because there is enough free space on the server ( 60G )

Thanks
0 Likes
Knowledge Partner
Knowledge Partner

Re: Driver for Office 365 does not starts

On 5/28/2019 8:24 AM, ominin wrote:
>
> Hi
> Thanks for answer
>
> geoffc;2500291 Wrote:
>> On 5/28/2019 6:34 AM, ominin wrote:
>>
>> Error is Startup policies. Reading earlier:
>>
>> [05/28/19 13:14:26.485]:MSOffice365 ST:Exception occured while
>> restricting permission for :
>> /var/opt/novell/eDirectory/data/dib/dx35154. Reason : insufficient
>> space
>> (-1)
>>
>> This might be the actual cause...

>
> It is strange error because there is enough free space on the server (
> 60G )


Then it is possible it is a permission error? Though eDir should run as
root usually, and IDM runs inside eDir.

However this might not be the fatal. There is also the no connection to
remote loader. Diagnose that one as well.


0 Likes
Knowledge Partner
Knowledge Partner

Re: Driver for Office 365 does not starts

ominin;2500292 wrote:
Hi
Thanks for answer



It is strange error because there is enough free space on the server ( 60G )

Thanks


Maybe you have separate partition for /var/opt/ and you have no free space for this specific partition
ominin1 Absent Member.
Absent Member.

Re: Driver for Office 365 does not starts

Hi al_b
I haven't separate partition for /var/opt/


Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.8G 0 7.8G 0% /dev
tmpfs 7.8G 84K 7.8G 1% /dev/shm
tmpfs 7.8G 19M 7.8G 1% /run
tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
/dev/sda3 77G 16G 60G 22% /
/dev/sda2 494M 53M 417M 12% /boot
tmpfs 1.6G 0 1.6G 0% /run/user/482
tmpfs 1.6G 0 1.6G 0% /run/user/481
tmpfs 1.6G 0 1.6G 0% /run/user/483
tmpfs 1.6G 16K 1.6G 1% /run/user/484
tmpfs 1.6G 0 1.6G 0% /run/user/0


Thanks
0 Likes
Highlighted
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Driver for Office 365 does not starts

On 05/28/2019 04:34 AM, ominin wrote:
>
> I have been working on Driver for Office 365 but the driver always
> starts whit error.
>
> I did all prerequisites tasks for Office 365 driver and deploy the
> driver.
>
> And when starting the driver after �Performing operation check-password
> for .� driver stop whit :
>
> *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: No connection to remote loader*


It mostly seems odd to me that the driver config object would stop after
being told to retry. In my experience that just leaves the thing retrying
forever, and that's okay for a while (until it gets going fully). Hmmm.

> Code:
> --------------------
> <nds dtdversion="4.0" ndsversion="8.x">
> <input>
> <check-password event-id="This check-password result is expected. It is the result of the shim verifying that the driver object password is non-empty."><!-- content suppressed --></check-password>
> </input>
> </nds>
> [05/28/19 13:14:26.849]:MSOffice365 PT:Filtering out notification-only attributes.
> [05/28/19 13:14:26.849]:MSOffice365 PT:Pumping XDS to eDirectory.
> [05/28/19 13:14:26.849]:MSOffice365 PT:Performing operation check-password for .
> [05/28/19 13:14:26.850]:MSOffice365 PT:--JCLNT-- \IDM_TREE\system\driverset1\MSOffice365 - Publisher : Duplicating : context = 831455370, tempContext = 831455383
> [05/28/19 13:14:27.787]:MSOffice365 ST: SubscriptionShim.execute() returned:
> [05/28/19 13:14:27.787]:MSOffice365 ST:
> <nds dtdversion="4.0" ndsversion="8.x">
> <output>
> <status event-id="0" level="retry" type="remoteloader">No connection to remote loader</status>
> </output>
> </nds>
> [05/28/19 13:14:27.788]:MSOffice365 ST: Applying input transformation policies.
> --------------------


Something else interesting here is that it s almost one full second, which
is the defalut handshake timeout between engine and Remote Loader (RL),
befor ethe connection is killed. Have you tried adjusting the
handshaketimeout parameter on the RL side to see if that may be the issue?
I your RL box is too slow about setting up the TLS/SSL connection then it
will timeout here and never continue and I think the symptom matches this
one. In the RL config's text file you can add somtehing like the
following to the existing connection line:


handshaketimeout=10000


The timeout uses milliseconds for units, so that means ten (10) seconds,
much longer than the default (1) second.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
ominin1 Absent Member.
Absent Member.

Re: Driver for Office 365 does not starts

Hi ad,

Something else interesting here is that it s almost one full second, which
is the defalut handshake timeout between engine and Remote Loader (RL),
befor ethe connection is killed. Have you tried adjusting the
handshaketimeout parameter on the RL side to see if that may be the issue?
I your RL box is too slow about setting up the TLS/SSL connection then it
will timeout here and never continue and I think the symptom matches this
one. In the RL config's text file you can add somtehing like the
following to the existing connection line:


At this time, I do not use TLS/SSL connection, but I added handshaketimeout to RL config and restart RL instance

-connection	"port=8091 handshaketimeout=10000"


But unfortunately, it did not help the driver did not start


[05/28/19 16:07:11.105]:MSOffice365 PT:Policy returned:
[05/28/19 16:07:11.105]:MSOffice365 PT:
<nds dtdversion="4.0" ndsversion="8.x">
<input>
<check-password event-id="This check-password result is expected. It is the result of the shim verifying that the driver object password is non-empty."><!-- c
ontent suppressed --></check-password>
</input>
</nds>
[05/28/19 16:07:11.106]:MSOffice365 PT:Filtering out notification-only attributes.
[05/28/19 16:07:11.106]:MSOffice365 PT:Pumping XDS to eDirectory.
[05/28/19 16:07:11.106]:MSOffice365 PT:Performing operation check-password for .
[05/28/19 16:07:11.106]:MSOffice365 PT:--JCLNT-- \IDM_TREE\system\driverset1\MSOffice365 - Publisher : Duplicating : context = 831455321, tempContext = 831455378
[05/28/19 16:07:12.025]:MSOffice365 ST: SubscriptionShim.execute() returned:
[05/28/19 16:07:12.025]:MSOffice365 ST:
<nds dtdversion="4.0" ndsversion="8.x">
<output>
<status event-id="0" level="retry" type="remoteloader">No connection to remote loader</status>
</output>
</nds>
[05/28/19 16:07:12.026]:MSOffice365 ST: Applying input transformation policies.

Thanks
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Driver for Office 365 does not starts

Please post the Remote Loader (RL) trace; since things are failing thre,
it may be useful to see why.

If you have not done so already, be sure the passwords are all set
properly (driver object and RL) on both sides, and if using Designer (as
you probably are) be sure you deploy those changes (sometimes people set
the min Designer and forget to deploy, which does nothing to help the
situation).

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
Knowledge Partner
Knowledge Partner

Re: Driver for Office 365 does not starts

On 5/28/2019 9:43 AM, ab wrote:
> Please post the Remote Loader (RL) trace; since things are failing thre,
> it may be useful to see why.
>
> If you have not done so already, be sure the passwords are all set
> properly (driver object and RL) on both sides, and if using Designer (as
> you probably are) be sure you deploy those changes (sometimes people set
> the min Designer and forget to deploy, which does nothing to help the
> situation).


And a compare does not suffice to push encrypted values (Named
Passwords, Driver/Remote/Auth passwords) has to be a deploy.


ominin1 Absent Member.
Absent Member.

Re: Driver for Office 365 does not starts

Please post the Remote Loader (RL) trace; since things are failing thre,
it may be useful to see why.


Trace file https://pastebin.com/AMFqvpZK

I analyzed network using wireshark and password set properly and I tried to re-enter passwords through iManager

Thanks
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Driver for Office 365 does not starts

On 05/28/2019 08:14 AM, ominin wrote:
>
>> Please post the Remote Loader (RL) trace; since things are failing thre,
>> it may be useful to see why.

>
> Trace file https://pastebin.com/AMFqvpZK


From your network trace which side is sending the FIN or RST first?

Also should 'c:\temp' be using a backslash? I suppose it may be fine, but
so often in Java-ish things (and every other programming language usually)
you should be using a regular slash as backslashes are often used as
escape characters. Slashes even work in the windows CLI, though
convention and history often hsa people using backslashes still.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
ominin1 Absent Member.
Absent Member.

Re: Driver for Office 365 does not starts

From your network trace which side is sending the FIN or RST first?

Remote Loader send the FIN first.

Also should 'c:\temp' be using a backslash?

This field is set by default when importing Office365 driver package in Designer
I changed this field to "c:/temp" but nothing has changed.
0 Likes
ominin1 Absent Member.
Absent Member.

Re: Driver for Office 365 does not starts

Hello All,

The problem was with the entitlement policy in the latest package "Office365 Entitlement" and disabling it lets the driver to run.
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.