Although InRelease is great, unfortunately I have found a new issue when rebooting the server. In testing the InRelease application on my test VM, I learned that after rebooting or shutting down my host machine, I was not able to log back into the InRelease application.
The Error message from console log:
Error – The request failed with HTTP status 403: Forbidden.: \r\n\r\n at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters)
at (Object )
I was able to reproduce this issue not only on my VM but also on my co-worker’s VM. Fortunately, this is a documented bug therefore I was able to find the following on the InRelease knowledge base website.
This error message usually means that the credentials used in the InReleaseAppPool (application pool) is not registered as a Release Manager and Service User in InRelease. To resolve this issue:
1. Change the credentials of the application pool to an InRelease user that is a Release Manager and Service User (i.e. Network Service usually have those permissions).
2. Open the InRelease Client.
3. Create an InRelease user with the Windows Account you want to use in the application pool and make it a Release Manager and a Service User.
4. Close the InRelease Client.
Change the credentials of the InReleaseAppPool for the new credentials.
I was able to fix the issue by using the above-mentioned workaround.
Tip: The un-install will remove the DB, IIS, and InRelease folder. Be prepared to redo the entire configuration settings if you have to re-install.
I would love to see a Service or User account be added during the installation phase, as this would likely prevent a few of the issues I have run across.