Skip to main content

Hello, 

I am trying to configure the Offfice365 Exchange connector. When I've gone though the steps of the manual (https://docs.thinkwisesoftware.com/docs/kb/exchange.html), and I run the SP: exh_sync_users, error 522 shows up. The error message is:

“Er kon geen verbinding worden opgezet met de Exchange koppeling:  System.Net.Sockets.SocketException (0x80004005): 
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.0.0.30:9988     
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)     at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)     at System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP)     
at UserDefinedProcedures.SendEventdT](String exchangeServerIP, Int32 exchangeServerPort, DbToExhEventMessageBuilder message, T& result, String& errorMessage)”

When I try to ping the given ip (10.0.0.30) it is not reachable. However when I check the config file, this ip is never mentioned.

Where is this IP used for and how can I fix the given error so I can use the Exchange Connector?

 

Also the Link to https://docs.thinkwisesoftware.com/docs/kb/resync-users-1 is broke. (header re-register users)

 

Hello Peter,

Thank you for contacting us. If the service is not running correct then there is no reason to try and call the exh_sync_users procedure. This procedure is only useful when the exh_get_users would yield new results from when you started the service. When the service is started the exh_get_users procedure is called and all the yielded email addresses will be autodiscovered. The first email address is used as the impersonation user that can impersonate all other email addresses. This user can also be configured in the config file.

When the first user’s autodiscover succeeds the service will update the exh_set_up table where the ip of the exchange server is kept, in your case it looks like this is 10.0.0.30. If this is not the case it could be that the service is further in the process and it tries to connect to your database on server 10.0.0.30. In the troubleshooting you can find problems that can occur when connecting to the database when using the Console Application: https://docs.thinkwisesoftware.com/docs/kb/exchange.html#console-application

 

If the IP address to the Exchange server is present you can also configure this in the config by setting the static EWS url:
https://docs.thinkwisesoftware.com/docs/kb/exchange.html#autodiscover-does-not-work


It can also be that your firewall is blocking requests for autodiscover or connecting to the database. If it is possible to turn off the firewall and give this a try then please do so.

If you have more detail on when the error occurs I am happy to help you regarding your problems.

Kind Regards,
Roel

P.s.Where did you find the broken link? I don't see it on the https://docs.thinkwisesoftware.com/docs/kb/exchange.html page

Hello Roel,

I will try it today. I will let you know.

Kind regards,

Peter

The broken link is here:

 

Hello Roel,

I have done a request to the IT of the customer as I am not sure if the Exchange has been configured for this. After I have answer, I will go on and try. 

If it won't work, can I send you a message?

Kind regards,

Peter

Sure Peter! Let me know :)

Hi Roel,

I found out the customer didn't use Office365 yet, however they use the on premise version. Do I need to install the 'normal’ exchange connector V2.10, or can I still use the latest version of the project?

Kind regards,

Peter

Hello Peter,

 

You can still use the 3.00 version, in the config file you can specify the specific office version that is being used.

 

Kind Regards,

Roel

Terms & ConditionsCookie settings