How to solve "Unable to connect publishing custom string handler for output caching"

by

If you are getting “Unable to connect publishing custom string handler for output caching” error in your event log then it is because of a custom web service you have installed on your Sharepoint server. Reason for this error is that you have a web part on your portal page which use the custom web service. Now, since Sharepoint uses output caching for the web pages to optimize the rendering experience and fast delivery of unchanged pages therefore, publishing infrastructure of Sharepoint tries to access the web service through your web part and due to any issue in your service, it starts generating this error.

Anyway, cutting a long story short, here is the solution:

Edit the web.config of custom web service (Please do not edit your Sharepoint Web application web.config) and make sure you have following under httpModules node which is located under system.web node. 

            <remove name=“PublishingHttpModule“ />



Share

9 thoughts on “How to solve "Unable to connect publishing custom string handler for output caching"”

  2. Cheers, this was the solution that worked for me after a long long search.

    I have BizTalk and SharePoint running on the same server and they both use the default website (I know, I should change this 🙂 Anyway, BizTalk’s Orchestration Port’s can be published as Web Services and even though I had the Process Worker Identities configured correctly (at leaast, I think), I still got this annoying error. I’ve added the following code to my web.config and problem was solved.

    • Dear sir,

      I found your solution to fix Unable to connect publishing custom string handler for output caching. you said you have put a code to your web.config. I like to know what is the code? Please let me know and your help is greatly appreciated.

      Thanks

      Young Yang

  5. Thanks! One thing though: pasting the line above into the config file didn’t work for me because it didn’t like those kind of quotes. After replacing the quotes with standard ones it worked like a charm. Thanks again.

  7. Aoa Sir,

    I was looking for the resolution of this issue and finds you while browsing 🙂

    Regards,

    Waliullah
    Ex-Clarusian

Comments are closed.