Multisite.svc 'does not exist' error in the event log - On Premise – Configurations & Setup - On Premise – Configurations & Setup - Progress Community
 On Premise – Configurations & Setup

Multisite.svc 'does not exist' error in the event log

  • Multisite.svc 'does not exist' error in the event log
  • Sitefinity 8.2.59 on IIS 8.5.  The Multisite module is not installed.  However, something seems to be trying to use its service, because the following error is logged at various times:


    WebHost failed to process a request.
     Sender Information: System.ServiceModel.Activation.HostedHttpRequestAsyncResult/23827279
     Exception: System.Web.HttpException (0x80004005): The service '/Sitefinity/Services/Multisite/Multisite.svc' does not exist. ---> System.ServiceModel.EndpointNotFoundException: The service '/Sitefinity/Services/Multisite/Multisite.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.ServiceModel.Activation.HostedHttpRequestAsyncResult.HandleRequest()
       at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.BeginRequest()
       at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
       at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result)
     Process Name: w3wp
     Process ID: 2088


    Doesn't appear to be any pattern to the timing.  Sometimes days will pass before it happens, just once, and sometimes it'll happen in sets (3-5 times) just minutes apart.

    Any ideas about what might be triggering this?



  • I would be interested in an explanation as well.
  • Anybody have an idea?
  • Hi,

    We've been also experiencing this same issue on a Feather based website using the same SF version and no Multisite module installed.

    Any luck yet, Eric? 

  • Sitefinity came back to me with the following:

    Based on our experience the above error message is thrown when the Multisite module is activated in your project and the project runs in an environment which is not properly configured for Sitefinity projects. Is it an option for you to set the project on another environment and check if the issue will be reproduced on this environment?

    Please also double check that the environment is configured properly to host Sitefinity projects as described in this article:

    If you are not using the Multisite module, you can also try to uninstall the Multisite module from its Actions link under Administration -> Modules and Services. Please chek the below article for more details about uninstalling modules:

  • I have been unable to check the setup thoroughly due to staff being unavailable. Doubt that it is the root of the evil,  but can someone please confirm that their setup is as per documentation? Thanks
  • Nope, no luck yet.  We had to go ahead and roll out the site to production with the error continuing to occur.  We got the same feedback from Sitefinity support as reported above, which was that the Multisite module must be activated, etc., but as noted in the first line of the original post that's not the case - it's neither activated nor installed.


    Looking at the IIS logs, I've correlated the Windows Event with this (primary) request by a backend user in a Sitefinity designer:



    That request kicks off a bunch of other requests for various designer resources like these:





    There's a pause, then it looks like the user begins to edit something in the content block (or other component in a page), presumably an image or image-based link, which then kicks off these supporting designer related requests:









    Which then leads to this request, which raises the exception that appears in the Windows Event log:



    I'm pretty sure it doesn't impact the backend user in the designer or I would have heard from them by now.  This also explains why there is no pattern to the Windows Event log entries, because they're clearly tied to some arbitrary backend design activity.


    We're ignoring it for now, as is Sitefinity, apparently, because they closed our support ticket without resolving it.  If anyone learns any more about it, please come back and share it with us.



  • Support suggested us to update the latest Windows updates on the server. After updating the missing required updates (WS2012 R2) and now checking over the weekend this hasn't been happening anymore so it might have just resolved the issue.

    Props to Velizar Bishurov for providing this info.
  • What windows update solved the issue? We have all windows updates on our 2012 R2 server applied and are experiencing this issue despite the feature not being installed.
  • Wanted to close the loop for everyone on this post. It appears once we installed a 8.5 hot fix update. We recently migrated to v10 of Sitefinity. It's been two weeks and the error hasn't appeared.