Not sure if this is related to a recent upgrade of web connect or not. I upgraded a Web Server 2008 from version around 5.78 to 6.15. It ran fine for a few days and then I started getting this error:

The current request failed with an unhandled failure in the server application. Object reference not set to an instance of an object.

I reset IIS and it went away for a couple days but then came back. I just rebooted the server and is working fine.

In case it comes back, I would appreciate your thoughts Rick.

Thanks,

Eddie

ps. Love your work and customer support.

Not sure...

How does this error show up exactly? On every request? Every request to the Web Connection request? What about static pages? What about admin\admin.aspx page?

+++ Rick ---

The first time, it seemed to be on every page. The 2nd time, it seemed to be a mixed bag. Quite possibly some windows bug that a reboot fixed. If it happens again, I will investigate more.

Thanks

We have the server to release the com instances each morning at 4am. It seems to be related to this. Maybe it doesn't completely release them all and a dangling instance is the cause of the problem?

Thanks for any thoughts on this,

Eddie

It shouldn't be a problem releasing instances. Web Connection will release the COM objects and if they don't release, will issue a hard process kill to release the instances that are 'stuck'. However, if you have stuck instances they do have a tendency to eventually cause a problem as COM reference counts by the host take up memory and eventually cause a problem. Again, if you're not using the .NET Module that's the first place to consider making changes as the module is much more reliable when it comes to COM operation.

If you're doing any sort of recycling you should do an automated IIS restart via the IIS Health Management tools (in the Application Pool config). You can set the server to recycle on a regular schedule. This will ensure the entire Process is released, not just the COM servers. Further this process is staged so that the new Application Pool is launched before the other one is taken down and the old one is drained in the background. If you do any sort of 'reload' this is the way to go.

+++ Rick ---