When the Dispatch Console automatic updates stop working or mobile cannot connect to the cache service, it may be because of a misconfiguration in Redis cache. If you take a look at the event log and see that the error is “Fixing Cannot Write to Read-Only Slave", the following steps will resolve the issue:
- On each server, stop Internet Information Services (IIS), the Astea Cache Service, and the Astea Monitoring Service.
- On each server, backup the redis.windows.conf and redis-sentinal.conf files located in the Bin sub-directory of the Astea Alliance installation directory. (ie. C:\Program Files\Astea Alliance 14.0\Bin\redis.windows.conf)
- On each server, Using WordPad or Notepad++, open the redis.windows.conf file and redis-sentinal.conf file as administrator and remove the contents under the section # Generated by CONFIG REWRITE.
Example of line to remove:
- On each server, open the Web.config as administrator located in the ServiceBus sub-directory of the Astea Alliance installation directory in notepad.
- Ensure the redis.connectionstring property points to the IP_ADDRESS:PORT of each cache server, separated by commas. (ie. 10.10.8.36.6379,10.10.8.64:6379,abortConnect=false)
- Start Internet Information Services (IIS), the Astea Cache Service and Astea Monitoring Service on the server that you would like to designate as the master.
- Start IIS the cache services on the remaining servers.
- Open the Astea Configuration Editor and ensure that each cache server is listed in the Host section, separated by commas. The port section should also have the port specified for each host, separated by commas. Please see the example below:
- Save changes made to the configuration editor.
