SYMPTOM:
In Strategy Mobile 9.4.x and 10.x, when applying a configuration link to a mobile device, user may intermittently receive the following error:
Configuration Retrieval Error - Configuration could not be applied successfully
CAUSE:There could be different reasons why this issue occurs, one of them is that the configuration cannot be found. When that is the case, this error will be found in the device logs:
<taskResponse statusCode="500" errorMsg="Configuration not found.">
If an administrator has setup two or more Strategy Mobile Server machines behind a Load Balancer, it is important to keep in mind that the Strategy Mobile Configurations created in one Strategy Mobile server are not get automatically shared by the other Strategy Mobile server nodes. This means that the Configuration only exists in one of the nodes of the cluster, thus all other nodes are missing the configuration. When users click on the link, the load balancer might direct the user to one mobile server that contains the configuration or might direct them to another node that does not contain the configuration, then this error will occur. This explains why the problem is intermittent, as the client device could be routed to different mobile servers every time.
ACTION:To fix this issue, go to the Strategy Mobile server where the configuration was created and navigate to:
<Strategy Mobile Home>/WEB-INF/xml/mobile
Copy the following Strategy Mobile Configuration files:
- mobileConfigurationIndex.xml
- mobileConfig-xxxx-xxxx-xxxx.xml
Note: There may be more than 1 mobileConfig-xxxx-xxxx-xxxx.xml file.
Access the other Strategy Mobile server machine(s), go to the same folder location as above, and paste the xml files copied over. Restart the application server for the changes to take effect. Now, regardless of which server the load balancer points the user to, all servers will contain the same configuration files.
Note: Any changes made to the configuration files will require to repeat the same synchronization steps listed above.
