- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Has anyone had an issue with the latest version of Smart connector in that the REST endpoint for SOAP EWS to SBO is stopping daily. We have set the logging to 'everything' but very little shows up. We will change to 'debug' tomorrow to see if any more information is available in the Smartconnector log but I was wondering if anyone else has had this issue? Any ideas?
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Root cause of the "stopping" was due VMWare issues in the host environment and not anything specific to SmartConnector.
Reference:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Steve,
In order to help us determine what/where the issue is please confirm the following:
- Your Logging Level is set to "Debug" (Setup-Service Settings).
- You have Logging filters for "Rest Serve", "Ews Consume", and "Service" set to "Include in Logs" (Setup-Logging Filters).
Also, if you could provide the following:
- What version of SmartConnector are you using?
- What version of SBO are you using?
- Are you communicating with an ES or AS?
- What response does the client receive from SmartConnector when the symptoms occur?
- Is the REST SmartConnector endpoint itself "stopping" e.g. no longer active?
- Provide a log file which captures the condition with the above settings confirmed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Root cause of the "stopping" was due VMWare issues in the host environment and not anything specific to SmartConnector.
Reference:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Hi Mark,
Hope all goes well.
Just curious, was the client able to resolve the issues using the linked KB articles? Just trying to figure out if SmartConnector is fully compatible with a VM. It doesn't mention anything that I can see in the Developers guide.
Starting to think we might have to move the Smart Connector to a physical machine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
The problem I linked was a VMWare issue; not a SmartConnector issue. We use VMs with SmartConnector for virtually (pun intended) all of our PoCs without any issue.
I haven't heard anything further from the originator of the reported issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Hi Petri, the issue was caused by the quiescing during snapshotting of the back up. It has to do with the way VMWare freezes the VM whenbacking up. I believe that the customer disabled quiescing to fix the issue, however I would like to see some further investigating into the reason for it causing SmartConnector to stop and if anything can be done on our end to handle this event, as I am sure I will not be the last person to experience this.

