Siebel Remote Sync Not Working With Direct Access
(Doc ID 2295649.1)
Last updated on APRIL 04, 2025
Applies to:
Siebel CRM - Version 15.12 [IP2015] and laterInformation in this document applies to any platform.
Symptoms
On : 15.12 [IP2015] version, Remote / Replication / Anywhere
Siebel remote sync not working with direct access
Recently enabled direct access on our tablet devices. When I connect to direct access, and try to sync our local databases, we get an error
Cannot connect to server. Sync manager may be down. Session timeout.
The sync manager is up and running, and as soon as we connect to Office network using LAN or WiFi or VPN, the sync works fine, but not with microsoft direct access.
ERROR
-----------------------
The error we get there is [TCPIP-client] connect() to <serverhostname.xyz.domain.net>:40400 failed (err=10060 | Connection timed out.)
GenericLog GenericError 1 0000000559531e00:0 2017-06-28 15:36:12 (commapi.cpp (310) err=1180849 sys=10060) SBL-NET-01201: Internal: connect() failed: Connection timed out.
SBL-DCK-00175: Cannot open connection to <serverhostname.xyz.domain.net>. The Synch Manager component on the server is most likely unavailable.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Connect to local database and run Synch in Microsoft DirectAccess enabled.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, all remote users cannot perform local database synch when using MDA.
Changes
Siebel Remote synch needs support of IPv6 which helps to make use of Microsoft DirectAccess feature
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |