I’ll see if I can help!
Also, in general, It might also help to turn logging on ‘Trace’ in Smart Connector and make sure the ‘Ews Serve’ logging filter is set to true? We might get some additional info from Smart Connector that can help to debug this issue.
As an additional test I added another EWS service in a ASP on the site (The first EWS was in the ES) and it doesn't seem to be having any issues ATM. I'm keeping an eye on it.
Have you had a chance to look over the log yet?
Your logs look normal as far as I can see.. You mention that you tried creating the interface in an AS and it works as expected..
Did you delete and re-create the interface in the ES? Does the same thing happen? I am wondering if you can use SOAP UI (installed on the same machine as the ES), and try and send some requests to the EWS Server hosted in Smart Connector, and see what the response is.
If you need help with SOAP UI, please feel free to send me an email.
Yes everything is still working well in the ASP. We have some trends and binds setup with the points in the ES. I'll get with the guy who is setting up everything at the customer site on Wednesday when he returns and recreate the service. I'll let you know how everything goes.
I had the guy working on the site make an export of all the items in the ESWService. I then haphazard deleted about 75% items and the all the remaining hosted items started working again. After that I deleted the rest of the hosted objects and the EWSService. I created a new identical EWSService and we imported all the items into the EWSService. It started having the same error right away, so we deleted all the objects that we imported and manually reconfigured everything. Its all working fine now and I suspected something in our import was giving us grief for all of the values in the ESW.
I've attached the import just in case you wanted to look at what we had going on originally.