We have an ASP.NET Web Form Application written in .NET 3.5 framework. This application has been evolved for over 10 years now and is a mature application. It has been implemented across a number of different clients.
Recently we have had an issue with the application for one of our clients. The application has been live for over a year on the client's infrastructure before seeing this error. This error only started showing itself over the past month.
The error we are seeing is: 500 - Internal Server error. There is a problem with the resource you are looking for, and it cannot be displayed. Server Application Unavailable. The web application you are attempting to access on the web server is currently unavailable...
And from the event log: "Failed to execute request because the App-Domain could not be created. Error: 0x80004003 Invalid pointer"
Recycling the App pool fixes the issue (i.e. the application starts working without any further issues). This is an intermittent issue and the application will work fine for a about a week or so then we see the error again. Recycling the App Pool fixes is the issue again. The App Pool is set to recycle once a day rather than when it is idle, otherwise I think we would see this issue a lot more.
For this client the application is deployed in a Web Farm. We have only ever seen this error on ONE of the two servers on the Web Farm. Both should be identical to each other in terms of the Application deployed. It has happened 4 times now and all have been on the same server. Might be too early to call, but it seems to be server specific. We have never seen this error before across all our implementations to date. Also, it does not show up in Test and Dev for the client experiencing this issue.
I haven’t found much while googling this issue. This post seems similar, but no resolution included:https://m.reddit.com/r/WindowsServer/comments/4ew2p2/iis_0x80004003_error/#
I am fairly certain that the issue relates to starting up the App Pool and is likely (although I can’t be certain) to have occurred before hitting any of our start up code as none of our logging is outputted. We also have 2 other instances of our application (they have different content and databases however) on the same production servers. Both of the other 2 applications do not see this issue (they are running under different App Pools under different service accounts).
Any thoughts or feedback is welcome. The sever is Windows Server 2012 R2 running IIS 8.5.
Thanks!