In the last blog post, we saw that SC Orchestrator R2 eval has taken steps to reduce the occurrence of HTTP 500 error by modifying the stored procedures responsible for calculating the authorization cache. In this post, we will look into the solution to the problem related to occurrence of HTTP 404 errors.
We saw that [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache table holds the records for authorizationcache and this authorization cache is cleared every 10 minutes and is also maintained (older authorization entry timestamp compared to current time is deleted) every 30 minutes. These authorization cache and their schedules are maintained within Orchestrator SQL database. The authorization cache is also created if the authorization cache is empty and a request is made to the web service.
As noted above, if we can clear the authorizationcache table and then invoke the web service, the authorization cache would be calculated from scratch and new Runbooks would find its way within the authorization cache.
Therefore steps to remove the HTTP 404 error are
1. Use the below SQL statement to empty the [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache table
Truncate table [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache table
2. Open Browser and browse the Web Service to view its metadata. This action will re-populate the authorization cache. The url is generally of the form http://localhost:81/Orchestrator2012/Orchestrator.svc which could be different in your case.
Hope this post would help solve some of your Orchestrator web service issues.