• State Not Answered
  • Replies 2 replies
  • Subscribers 95 subscribers
  • Views 455 views
  • Users 0 members are here
Options
Related

Message "500 - Internal server error" returned by Exchange 2016 target system

michel.gruau-ext
over 2 years ago

Hello,

We have created in our TEST environment a new sync project for the connection to an Exchange 2016 server and everything worked fine for one moment, I mean creation of the project + a few synchronization run but suddenly the synchronization started to failed with the message "500 - Internal server error"

We have a similar error referring to this "500 - Internal server error" in the corresponding job queue process and also in job server logs.

Each time I click in the sync editor on "Target System", I have the same error.

When I click on "Edit connection", everything works fine but in the end of the wizard I have again the same error.

My colleague managing the Exchange server made a reboot but it changed nothing.

What is especially strange is this issue happened without changing anything in the configuration.

Many thanks thanks for your help.

Best regards,

Michel

Parents
  • 0 over 2 years ago

    Hello,

    What version of 1IM are you running?

    Have you already opened a Support case for this issue?

    Trevor

  • 0 over 2 years ago in reply to Trevor Pike

    Hello Trevor,

    Thank you for your answer. 

    I tried to open a ticket but our support contract is temporarily expired due to an administrative issue on our side apparently...

    Anyway I tried in meantime to connect to Exchange using the following commands ...

    Get-ExecutionPolicy
    $LiveCred = Get-Credential
    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://<our Exchange server>/powershell/ -Credential $LiveCred

    ... and I reproduced the issue with the "500 - Internal server error" and then I guess this is simply an Exchange configuration issue or a PowerShell configuration issue.

    I just reported this finding to the Exchange administrator and I am waiting his feedback but I am interested if you see additional things to check.

    Many thanks.

    Michel

Reply
  • 0 over 2 years ago in reply to Trevor Pike

    Hello Trevor,

    Thank you for your answer. 

    I tried to open a ticket but our support contract is temporarily expired due to an administrative issue on our side apparently...

    Anyway I tried in meantime to connect to Exchange using the following commands ...

    Get-ExecutionPolicy
    $LiveCred = Get-Credential
    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://<our Exchange server>/powershell/ -Credential $LiveCred

    ... and I reproduced the issue with the "500 - Internal server error" and then I guess this is simply an Exchange configuration issue or a PowerShell configuration issue.

    I just reported this finding to the Exchange administrator and I am waiting his feedback but I am interested if you see additional things to check.

    Many thanks.

    Michel

Children
No Data