Last week I installed Exchange 2k3 SP1. This is running on a Windows Server 2k3 machine. It had been working fine up until that point, aside from an RUS issue (in that if we added a new user, they wouldn't get updated until the server was restarted, regardless of what we did to RUS).
This morning, as a lovely way to wake up, the Exchange 2003 Outlook Web Access stopped letting anyone in. It was showing a HTTP 500.13 error - which is saying that the server is too busy or has too many connections and therefore we can't get in.
I had some other issues I had to attend to on a remote site which was somewhat related to this (users couldn't access their webmail), and then once I came in I was seeting that Outlook was either losing connection entirely or it was prompting for users to enter their login/pass every 5 minutes.
The prompt would come up and then go away (this is on Outlook 2k3 systems, not sure what the behavior is on the Outlook 2k machines).
I looked at the Knowledge Base #829167 and while that somewhat resembles what we had - the "fix" was totally irrelevant to our situation (the settings were already there).
I went into IIS and it is set to unlimited connections, so there isn't an issue that we somehow surpassed a setting there.
I have no idea what this is and this is the first we have seen it.
This morning, as a lovely way to wake up, the Exchange 2003 Outlook Web Access stopped letting anyone in. It was showing a HTTP 500.13 error - which is saying that the server is too busy or has too many connections and therefore we can't get in.
I had some other issues I had to attend to on a remote site which was somewhat related to this (users couldn't access their webmail), and then once I came in I was seeting that Outlook was either losing connection entirely or it was prompting for users to enter their login/pass every 5 minutes.
The prompt would come up and then go away (this is on Outlook 2k3 systems, not sure what the behavior is on the Outlook 2k machines).
I looked at the Knowledge Base #829167 and while that somewhat resembles what we had - the "fix" was totally irrelevant to our situation (the settings were already there).
I went into IIS and it is set to unlimited connections, so there isn't an issue that we somehow surpassed a setting there.
I have no idea what this is and this is the first we have seen it.
