• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 94 subscribers
  • Views 3618 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Exchange Data Import into D1IM

sshvets
over 8 years ago

Hello Experts,


I am trying to import data from Exchange 2010 into D1IM, using initial synchronization workflow in Sync Editor (v. 7.0.1), it is a first time data import from Exchange into D1IM. And we are seeing the error message below, has anyone seen this type of error message before or knows what 'is not in transaction' means? We also received the same error if we attempt to simulate a report only.

"VI.Projector.JobComponent.ProjectorComponent - 61d441cc-8d8e-4bcd-9aab-3fd0fdf2edba: Errors occured

    [2134003] Error executing a full projection!
    [1777018] Error executing workflow (Initial Synchronization) of synchronization project (Exchange 2010 "Domain" (all recipients)).
    [1777124] Error executing projection step (MailboxDatabase) of projection configuration (Initial Synchronization (Initial Synchronization)).
    [1777219] Error executing projection step (MailboxDatabase)!
    [1777004] Method (Insert object (Insert)) could not be executed successfully.
    [System.Exception] Object ( - BCSMAIL2) is not in transaction!"

BCSMAIL2 is one of the servers

Thanks.
Parents
  • 0 over 8 years ago

    Hi,

    it would be awesome if you are able to post the complete logfile from the StdioProcessor executing the full sync where the error occurs.

    To get some debug messages, please configure the globallog.config on the Job Service, executing the full sync, to include debug messages in the NLog logging.

    To do that change the minlevel to "Debug" as shown in the snippet from the globallog.config

    ...

    <rules>
      <logger name="*" minlevel="Debug" writeTo="logfile"/>

    ...

    You will find the log file in the path

    %localappdata\Dell\One Identity Manager\StdioProcessors

    Please remember to switch logging back to the normal Info level after you have created the log file for the full sync.

     

     

Reply
  • 0 over 8 years ago

    Hi,

    it would be awesome if you are able to post the complete logfile from the StdioProcessor executing the full sync where the error occurs.

    To get some debug messages, please configure the globallog.config on the Job Service, executing the full sync, to include debug messages in the NLog logging.

    To do that change the minlevel to "Debug" as shown in the snippet from the globallog.config

    ...

    <rules>
      <logger name="*" minlevel="Debug" writeTo="logfile"/>

    ...

    You will find the log file in the path

    %localappdata\Dell\One Identity Manager\StdioProcessors

    Please remember to switch logging back to the normal Info level after you have created the log file for the full sync.

     

     

Children
No Data