We are sorry to hear that you have such issue. We need the additional details about this issue:
1. What project type are you using, WebForms or MVC? If WebForms, do you have all HTTP-handlers properly configured in the web.config file? If MVC, do you have “Groupdocs.Web.UI.Viewer.InitRoutes();” in the Gllobal.asax?
2. From the browser debug window, request/response scanner, you can find out more details about these errors. Switch to the “Network” tab, select one of the failed requests, open it, and tell us what info is present in the “Preview” or “Response” tab.
3. Which application pool mode are you using in the IIS? Classic or Integrated? Are you using Virtual Directory system for hosting your web-site?
Thanks and waiting additional details from you.
Thank you for very detailed screencast with voice. Up to you no one has ever done that.
There might be several reasons.
1. I’ve checked your partial web.config. Need to be very careful there. For example, I see that HTTP-handler “GetFontHandler” is commented for classic mode while uncommented for integrated. There might be a situation when in MS Visual Studio you are using local IIS Express (I see from the screencast that you are using MS VS 2012) which uses system.webServer -> handlers (because it works in Integrated pipeline mode by default) and all is good. And when using Classic pipeline mode in IIS then errors are raising.
2. Maybe the publishing process corrupts the web-site somehow. You need to check this out using the description below.
2.1. Make sure that web-site with Annotation is compiled and working well in MS Visual Studio, you can add the annotations to the document and then see them, e.g. all is good.
2.2. Copy the full project folder (not overall solution folder, but only a project folder “Groupdocs.Demo.Annotation.Webforms”) to the place where you stores web-sites for IIS. Just pure copy/paste like Ctrl+C/Ctrl+V.
2.3. Create a new website in the IIS and point out this folder as its root location.
2.4. Add “Full permission” access to whole folder, not only for the “App_Data”.
2.5. Specify application pool “classic mode” for this web-site.
2.6. Run a web-site and see what is happening.
2.7. If you see the same situation as before, then please change the application pool to the “Integrated mode” or specify another application pool which works in “Integrated mode”.
2.8. This actions allow us to narrow the list of probable reasons why GroupDocs.Annotation is not working in the IIS.
3. About “validate” attribute. You are absolutely right, the “validate” attribute is not allowed in the “system.webServer / handlers”, it should be present only in the “system.web / httpHandlers”: Adding Handlers . This is a little drawback in our demo project.
Hope that this will help. Please come back to us in any case, with any results. Thanks and sorry for such long reply.
Thank you for response. Unfortunately I don’t understand, your web-site and Annotation in particular started to work properly right after switching application pool to Integrated mode? That is very strange, because GroupDocs.Annotation for .NET supports the Classic mode too.
Can you please try to remove/comment all that you have inside “httpHandlers” section, and paste the code from the article “How to use GroupDocs Annotation for .NET in an ASP.NET Project”, item 8? Using Classic mode, of course.