Open the dm.cfg on the client and locate the variable DM_WEB_URL (create new if it is not there). Make sure this is set to the correct value (http(s)://<server>:<port>), e.g.
This error can occur if the DM_WEB_URL in the dm.cfg file is not properly configured. To set this, add or edit the following line in the dm.cfg file on Dimensions CM server : DM_WEB_URL http://<host_name of Dimensions server>:<tomcat port>
With a Dimensions server installed on a Linux machine, user has changed tomcat port from 8080 to 80 by replacing 8080 in 80 : - in DM_WEB_URL variable in dm.cfg of DImensions server
DM_ALF_EVENT_CONFIG %DM_DFS%alf_events_config.xml DM_PULSE_WEB_URL % DM_WEB_URL %/pulse Once the file was updated and the listener was restarted the Expert Chains were triggered as expected.
this is fixed by setting correctly only the DM_WEB_URL symbole in the dm.cfg as follow : DM_WEB_URL http://<servername>:<port > For instance, they would look similar to the following:
In this case, Dimensions has been configured to use https instead of http. Looking at the dm.cfg of the Dimensions server, it has been discovered that the DM_WEB_URL was set as follow : DM_WEB_URL http://Dimensions_server.mycompany.com:8090
