This issue is caused by the inability to authenticate properly to the RMS SQL DB.
When you first log into the Recast Management Server (RMS), it will try to use your Windows credentials to log into the webpage. If you installed RMS with a different account than is signed into windows, this can cause it not to authenticate properly. Open a private browser and navigate to the RMS webpage. It will prompt for a username and password. Make sure to sign in with the same user account that ran the RMS installer.
After you are authenticated successfully, you should see the RMS interface. Navigate to permissions and make sure you see “Administrators” underneath the Recast Roles section.
If you are unable to use the installation username to run the browser, you can alternatively add your currently logged in username to the local group on the computer where you installed RMS called “Recast Administrators.” After you add your username to that local group and refresh your browser, the Recast Management Server should allow you to log in using that username and should show the Administrators group (and you will know you are authenticated successfully.)
If you are already logging in with that user and it still doesn’t show Administrators in the Recast Roles section, you should open the IIS manager on the Recast Management Server and recycle the app pool.
Once you have been successfully logged into RMS, you should add any users that you want to be able to log in to the server under the “Recast Users” section. Make sure they are assigned to a role that has at least some Administration privileges so they are able to use the Recast Management Server console.
When the Recast Management Server (RMS) is first installed, the account that ran the installer was added to the Recast Administrators local group. This allows for authenticating in the webpage for the first time. This group only allows the account to be an admin in the RMS web interface but does not give any other admin privileges. The user accounts will still need to be added in RMS under Administration > Permissions > Recast Users and given a Recast Role to use other Recast products like Right Click Tools and Endpoint Insights. This can be helpful in situations where the former RMS admin may have left the company and no one else can log in.
The 500.19 IIS Error can happen when WSUS is installed on the same box as Recast Management Server and is caused by WSUS installing a 64-bit version the DynamicCompressionModule but not the 32-bit version.
To fix the issue, you can either disable the XPress compression scheme for all pages and application pools, disable loading the XPress module for 32-bit application pools, or install the 32-bit version of this module.
Disable XPress compression for all pages and application pools
Run the following command to disable XPress compression globally. %windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']
Disable XPress for 32-bit application pools
Edit the C:\Windows\System32\inetsrv\config\ApplicationHost.config file and add the following line in the section.
Install the 32-bit version of suscomp.dll
Install WSUS on a 32-bit machine and copy the suscomp.dll file from that machine to %windir%\SYSWOW64\inetsrv\
Full Error message: HTTP Error 503.2 - Service Unavailable. The serverRuntime@appConcurrentRequestLimit setting is being exceeded.
- When you try to go to the Recast Management Server interface, you get a page saying there's a 503.2 Error.
- When you attempt to use the Right Click Tools, you will get an error saying that the tools were unable to connect to the Recast Management Server.
This error usually occurs when too many endpoints are trying to connect to a server. The default limit is 5,000 concurrent connections. If you have more than 5,000 Recast Agents, you might come across this error.
To increase the concurrent connection limit:
1. Open IIS Manager and on the server node, under Management, select the Configuration Editor.
2. Navigate to system.webServer and select serverRuntime.
NOTE: On older versions of IIS Manager, appConcurrentRequestLimit may be under system.web and httpRuntime.
3. Change the appConcurrentRequestLimit to a higher value. We recommend increasing the value above the current number of Agents in your environment to provide a sufficient buffer, in case you add more later.