We have moved a SuperOffice-installation to a new environment, and are experiencing that the eventlog on the appserver is being spammed with the following message:
WebHost failed to process a request.
Sender Information: System.ServiceModel.Activation.HostedHttpRequestAsyncResult/3664333
Exception: System.Web.HttpException (0x80004005): The service '/service/soweb/services/TrayApp2.svc' does not exist. ---> System.ServiceModel.EndpointNotFoundException: The service '/service/soweb/services/TrayApp2.svc' does not exist.
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath, EventTraceActivity eventTraceActivity)
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result)
Process Name: w3wp
Process ID: 3384
The message itself is allright, but i dont understand why it points to the wrong URL (?).
We have set this up (when moving it to the new environment) according to 8.1, so we have 1 site with ../service/ and ../sales/ as applications under it.
The old WEB, in the old environment, was set up with 1 site, where CS was placed directly on the root. Soweb was placed as an application underneath this site. So I belive there is a pointer somewhere that tells it to look for TrayApp2.svc underneath the service-application.
To complicate things a little more we have set up a reverse proxy in DMZ that routes all the traffic.
I have created explisit rules to NOT forward URL's including 'soweb', to make sure no un-configured web tools tries to connect to the old URL/endpoint.
This had no effect on the appserver, so it should/must be something internally in the WEB-application that checks the endpoint for trayapp?
Any advice is appreciated, im scratching my head on how to get around this problem. The only way i can see is to set up soweb as an application under /service, and 'force' the URL to be valid again..