AD frozen jobs version 8.1

Hi,

Can you confirm if the object actually DOES exist on the server?

B.

Yes Barry, object exists on the server.

OK ..... then the thing to do now is to run the object update in trace mode so that you can see ALL the messages that are generated ..... my guess is that there is a different message from AD before the no such object message. You are only seeing the last message in the stack.

Trace Debug Connector/Sync Issues

Add these lines to globallog.config or stdioprocessor.exe.config:

Find StdioProcessor.exe.config in your job server installation dir.

Add the below lines:

       <rules>

              <!-- Debug logger definitions for trace log -->

              <logger name="SystemConnector" minlevel="Trace" writeTo="debug"/>

              <logger name="*" minlevel="Trace" writeTo="debug"/>

       </rules>

---------------------------------------------------------------------------

  <nlog autoReload="true" xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="">www.w3.org/.../XMLSchema-instance">

    <variable name="appName" value="StdioProcessor"/>

    <include file="${basedir}/globallog.config" ignoreErrors="true"/>

================== just here in the file ======================

  </nlog>

Then save it and run again ……. Whichever user the js runs as go to c:\users\<jsuser>\appdata\local ……….. and keep going to one identity manager …. Then stdioprocessor …. Then debug.

You should get a trace log/debug file in there.

Trace Debug Connector/Sync Issues

Add these lines to globallog.config or stdioprocessor.exe.config:

Find StdioProcessor.exe.config in your job server installation dir.

Add the below lines:

       <rules>

              <!-- Debug logger definitions for trace log -->

              <logger name="SystemConnector" minlevel="Trace" writeTo="debug"/>

              <logger name="*" minlevel="Trace" writeTo="debug"/>

       </rules>

---------------------------------------------------------------------------

  <nlog autoReload="true" xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="">www.w3.org/.../XMLSchema-instance">

    <variable name="appName" value="StdioProcessor"/>

    <include file="${basedir}/globallog.config" ignoreErrors="true"/>

================== just here in the file ======================

  </nlog>

Then save it and run again ……. Whichever user the js runs as go to c:\users\<jsuser>\appdata\local ……….. and keep going to one identity manager …. Then stdioprocessor …. Then debug.

You should get a trace log/debug file in there.

Thanks Barry I found the reason

May i know the reason for the issue, we are facing the same issue