Greetings all,
I am running SMS 2003 no service pack and I am experiencing error 5436 on my MP once every hour. I have tried all of the suggested solutions and the error continues to return. I also have made IWAM_COMPUTERNAME a member of the local admin and nothing has worked. I was hoping this was a common problem and there was an alternative fix provided somewhere. Anyone seen this before?
The complete error is this:
MP Control Manager detected MP is not responding to HTTP requests. The http error is Access Forbidden.
Possible cause: MP service is not started or not responding.
Solution: Manually restart the SMS Agent Host service on the MP.
Possible cause: IIS service is not responding.
Solution: Manually restart the W3SVC service on the MP.
Possible cause: MP encountered an error when connecting to SQL Server.
Solution: Verify MP can connect to the SQL server and has sufficient access rights to the SQL server site system.
Possible cause: The Default Web Site is disabled in IIS.
Solution: Verify that the Default Web Site is enabled, and functioning properly.
I am running SMS 2003 no service pack and I am experiencing error 5436 on my MP once every hour. I have tried all of the suggested solutions and the error continues to return. I also have made IWAM_COMPUTERNAME a member of the local admin and nothing has worked. I was hoping this was a common problem and there was an alternative fix provided somewhere. Anyone seen this before?
The complete error is this:
MP Control Manager detected MP is not responding to HTTP requests. The http error is Access Forbidden.
Possible cause: MP service is not started or not responding.
Solution: Manually restart the SMS Agent Host service on the MP.
Possible cause: IIS service is not responding.
Solution: Manually restart the W3SVC service on the MP.
Possible cause: MP encountered an error when connecting to SQL Server.
Solution: Verify MP can connect to the SQL server and has sufficient access rights to the SQL server site system.
Possible cause: The Default Web Site is disabled in IIS.
Solution: Verify that the Default Web Site is enabled, and functioning properly.