Hello,

I recently migrated my AD connector. I moved the driver itself from an
IDM 4.0.2.7 engine server to IDM 4.6.3, and the RL from 4.0.2.7 on
Windows Server 2012 to 4.6.3 on Server 2016. Everything seems to work
fine, except that on two occasions, the driver just... stopped. Once it
happened exactly at midnight, the other time at 00:10.

Here's the trace (only level 1, unfortunately):


[04/02/19 00:10:00.115]:AD-OSUMC ST:Injecting User Agent XDS command
document into Subscriber channel.
[04/02/19 00:10:00.116]:AD-OSUMC ST:Applying command transformation
policies.
[04/02/19 00:10:00.116]:AD-OSUMC ST:Applying policy: %+C%14CCommand
Transform%-C.
[04/02/19 00:10:00.116]:AD-OSUMC ST:Applying policy:
%+C%14COSUMC-sub-ctp-ManagePasswordGroup%-C.
[04/02/19 00:10:00.116]:AD-OSUMC ST:Applying policy:
%+C%14CPassword(Sub)-Transform Distribution Password%-C.
[04/02/19 00:10:00.117]:AD-OSUMC ST:Applying policy:
%+C%14CPassword(Sub)-Default Password Policy%-C.
[04/02/19 00:10:00.117]:AD-OSUMC ST:Applying policy:
%+C%14CPassword(Sub)-Check Password GCV%-C.
[04/02/19 00:10:00.117]:AD-OSUMC ST:Applying policy:
%+C%14CPassword(Sub)-Add Password Payload%-C.
[04/02/19 00:10:00.117]:AD-OSUMC ST:Applying policy: %+C%14CPassword
Notify Ver1%-C.
[04/02/19 00:10:00.117]:AD-OSUMC ST:Filtering out notification-only
attributes.
[04/02/19 00:10:00.118]:AD-OSUMC ST:Fixing up association references.
[04/02/19 00:10:00.118]:AD-OSUMC ST:Applying schema mapping policies to
output.
[04/02/19 00:10:00.118]:AD-OSUMC ST:Applying policy:
%+C%14CSchemaMapping%-C.
[04/02/19 00:10:00.118]:AD-OSUMC ST:Applying output transformation policies.
[04/02/19 00:10:00.118]:AD-OSUMC ST:Applying policy: %+C%14COutput
Transform%-C.
[04/02/19 00:10:00.119]:AD-OSUMC ST:Applying policy:
%+C%14CPassword(Sub)-Pub Email Notifications%-C.
[04/02/19 00:10:00.119]:AD-OSUMC ST:Applying policy:
%+C%14COSUMC-otp-AttributeTranslations%-C.
[04/02/19 00:10:00.119]:AD-OSUMC ST:Remote Interface Driver: Sending...
[04/02/19 00:10:00.119]:AD-OSUMC ST:Remote Interface Driver: Document sent.
[04/02/19 00:10:00.121]:AD-OSUMC :Remote Interface Driver: Received.
[04/02/19 00:10:00.121]:AD-OSUMC :Remote Interface Driver: Received
document for subscriber channel
[04/02/19 00:10:00.121]:AD-OSUMC :Remote Interface Driver: Waiting for
receive...
[04/02/19 00:10:00.121]:AD-OSUMC ST:Applying input transformation policies.
[04/02/19 00:10:00.121]:AD-OSUMC ST:Applying policy: %+C%14CInput
Transform%-C.
[04/02/19 00:10:00.121]:AD-OSUMC ST:Applying XSLT policy:
%+C%14CInput+Transform+SS%-C.
[04/02/19 00:10:00.122]:AD-OSUMC ST:Applying policy:
%+C%14CPassword(Pub)-Sub Email Notifications%-C.
[04/02/19 00:10:00.122]:AD-OSUMC ST:Applying policy: %+C%14CVeto Delete
User%-C.
[04/02/19 00:10:00.122]:AD-OSUMC ST:Applying policy:
%+C%14COSUMC-itp-AttributeTranslations%-C.
[04/02/19 00:10:00.122]:AD-OSUMC ST:Applying schema mapping policies to
input.
[04/02/19 00:10:00.123]:AD-OSUMC ST:Applying policy:
%+C%14CSchemaMapping%-C.
[04/02/19 00:10:00.123]:AD-OSUMC ST:Resolving association references.
[04/02/19 00:10:00.223]:AD-OSUMC ST:Received state change event.
[04/02/19 00:10:00.224]:AD-OSUMC ST:Transitioned from state
'%+C%14CRunning%-C' to state '%+C%14CShutdown Pending%-C'.
[04/02/19 00:10:00.224]:AD-OSUMC ST:Successfully processed state change
event.
[04/02/19 00:10:00.224]:AD-OSUMC ST:Leaving event loop.
[04/02/19 00:10:00.224]:AD-OSUMC ST:Shutting down DirXML driver
\ID1\OSUMC\Drivers\edirIDv1\AD-OSUMC.
[04/02/19 00:10:00.225]:AD-OSUMC ST:No shutdown policies.
[04/02/19 00:10:00.225]:AD-OSUMC ST:Remote Interface Driver: Sending...
[04/02/19 00:10:00.225]:AD-OSUMC ST:Remote Interface Driver: Document sent.
[04/02/19 00:10:00.248]:AD-OSUMC :Remote Interface Driver: Received.
[04/02/19 00:10:00.248]:AD-OSUMC :Remote Interface Driver: Received
document for subscriber channel
[04/02/19 00:10:00.248]:AD-OSUMC :Remote Interface Driver: Waiting for
receive...
[04/02/19 00:10:00.248]:AD-OSUMC ST:Remote Interface Publisher: Received
shutdown.
[04/02/19 00:10:00.249]:AD-OSUMC ST:Remote Interface Driver: Closing
connection...
[04/02/19 00:10:00.250]:AD-OSUMC :Remote Interface Driver: Closing
connection...
[04/02/19 00:10:00.250]:AD-OSUMC :Remote Interface Driver: Connection closed
[04/02/19 00:10:00.250]:AD-OSUMC PT:Remote Interface Driver: Closing
connection...
[04/02/19 00:10:00.250]:AD-OSUMC ST:Remote Interface Driver: Connection
closed
[04/02/19 00:10:00.250]:AD-OSUMC PT:Remote Interface Driver: Connection
closed
[04/02/19 00:10:00.250]:AD-OSUMC ST:Remote Interface Subscriber:
Received shutdown.
[04/02/19 00:10:00.251]:AD-OSUMC PT:Applying input transformation policies.
[04/02/19 00:10:00.251]:AD-OSUMC ST:Reading XML attribute
vnd.nds.stream://ID1/OSUMC/Drivers/edirIDv1/AD-OSUMC#DirXML-DriverStorage.
[04/02/19 00:10:00.251]:AD-OSUMC PT:Applying policy: %+C%14CInput
Transform%-C.
[04/02/19 00:10:00.252]:AD-OSUMC ST:Writing driver state.
[04/02/19 00:10:00.252]:AD-OSUMC PT:Applying XSLT policy:
%+C%14CInput+Transform+SS%-C.
[04/02/19 00:10:00.252]:AD-OSUMC ST:Writing XML attribute
vnd.nds.stream://ID1/OSUMC/Drivers/edirIDv1/AD-OSUMC#DirXML-DriverStorage.
[04/02/19 00:10:00.252]:AD-OSUMC PT:Applying policy:
%+C%14CPassword(Pub)-Sub Email Notifications%-C.
[04/02/19 00:10:00.253]:AD-OSUMC PT:Applying policy: %+C%14CVeto Delete
User%-C.
[04/02/19 00:10:00.253]:AD-OSUMC PT:Applying policy:
%+C%14COSUMC-itp-AttributeTranslations%-C.
[04/02/19 00:10:00.253]:AD-OSUMC PT:Applying schema mapping policies to
input.
[04/02/19 00:10:00.253]:AD-OSUMC PT:Applying policy:
%+C%14CSchemaMapping%-C.
[04/02/19 00:10:00.254]:AD-OSUMC PT:Resolving association references.
[04/02/19 00:10:00.254]:AD-OSUMC PT:Ending publisher thread.
[04/02/19 00:10:00.264]:AD-OSUMC ST:Waiting for Publisher thread to
terminate. Maximum wait time is 60 seconds.
[04/02/19 00:10:00.264]:AD-OSUMC ST:Publisher thread terminated.
[04/02/19 00:10:00.265]:AD-OSUMC STriver terminated.
[04/02/19 00:10:00.265]:AD-OSUMC ST:Writing XML attribute
vnd.nds.stream://ID1/OSUMC/Drivers/edirIDv1/AD-OSUMC#DirXML-PersistentData.

Short of cranking up the trace level to 3 and waiting for it to happen
again, is there any way to find out why the driver stopped unexpectedly?
Could it have anything to do with that "User agent XDS command document"
statement?

Thanks