Devizes Room Booking System IIS7 problems
I have been using Devizes Room booking system on a Server 2003 DC for about 3 yrs now and it has been absolutely rock solid. A Big thanks to Ian for making such a simple to use booking system- our staff love it!
The problem is, Server 2003 is getting on a bit, so the time came to start upgrading all of our servers to Server 2008 R2. Now I am having a nightmare of a time trying to get a stable set-up!
The new set up is running on a Server 2008 R2 SP1 member server, and I have actually managed to get it authenticating quite nicely, by ensuring:
ASP.Net etc is installed
Creating an application using Classic Modes and the .net 2 framework
Enabling Allow Parent Paths
Enabling windows authentication.
in fact, the whole migration was surprisingly smooth. The problem is it won't stay up! It will authenticate with no problems at all for a few hours, and then all of a sudden the authentication will stop working!
Weird thing though- when it fails, I'm not getting the usual Internet explorer please authenticate pop up box, I'm getting the Devizes log on screen. It seems to me that the authentication isn't failing at the IIS/Windows level, but it is not passing the credentials through to the room booking system. Has anyone had any weird errors like this before?
The authentication failing seems to be random, i.e it's not happening a set time everyday, but seems to be crashing between 4-10 times a day! A quick reboot of the server (not the IIS service, as this makes no difference) seems to solve it temporarily. I'm at a loss!!
There doesn't appear to be anything to obvious in the eventvwr, except for these weird errors:
Event 12, IIS-Configuration
Unable to find schema for config section 'system.serviceModel/serviceHostingEnvironment'. This section will be ignored.
Event 12, IIS-Configuration
Unable to find schema for config section 'system.serviceModel/client'. This section will be ignored.
Event 12, IIS-Configuration
Unable to find schema for config section 'system.serviceModel/extensions'. This section will be ignored.
and every now and then (although not every time it stops working....)
The Security System could not establish a secured connection with the server LDAP/dc1.domain.com/domain.com@DOMAIN.COM. No authentication protocol was available.
The Security System could not establish a secured connection with the server LDAP/dc2.domain.com/domain.com@DOMAIN.COM. No authentication protocol was available.
The Security System could not establish a secured connection with the server LDAP/dc3.domain.com/domain.com@DOMAIN.COM. No authentication protocol was available.
Has anyone seen anything like this before?