If the application is experiencing significant lag when logging in, check the server logs (%\inetpub\wwwroot\<your_wrm_site_>\<your_wrm_site_core>\logs\application.log file) for a Redis error similar to the following:
2017-03-23 15:14:29,908 [90] ERROR Methodware.ERA.Cache.RedisCache - StackExchange.Redis.RedisConnectionException: No connection is available to service this operation: GET un:eraadmin ---> StackExchange.Redis.RedisConnectionException: SocketFailure on localhost:6379/Subscription
If this error is appearing in the logs, complete the following steps:
- Click the Windows icon and use the search function to open Services.
- Right-click the Redis service and select Properties.
- Note the Path to executable location in the Properties window. This is the location of the Redis configuration folder.
- Navigate to Redis configuration folder.
- Open the redis.windows-service.conf file with Notepad.
- Note the port number in the General section of the file. For example:
port <portnumber>
- Navigate to %\inetpub\wwwroot\<your_wrm_site_>\<your_wrm_site_core> and open the WRM Core website's web.config file using Notepad.
- In the appsettings section, review the port number. For example:
<appSettings>
…
<add key="InstanceName" value="localhost:<port number>"/>
- If the port numbers from the redis.windows-service.conf and the web.config don't match, run the WRM installer again.
- Select your existing instance, then select the Reconfigure option.
- On the Database Server Login screen of the installer, change the port number in the Redis cache connection field to match the port in the redis.windows-service.conf file.
- Leave the remainder of the settings the same, then complete the installation.