cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Knowledge Base

Why won't the EUM Server start up after updating the geo mapping file?

Symptoms

After making changes to geo mapping files, the EUM Server fails to start up. We see the below error in the EUM processor log:

 

1 Jan 2017 09:00:56.972 +0000 main AD.ALL ERROR 
| Error Starting EUM Processor Server
| com.google.inject.CreationException: Unable to create injector, see the following errors:
|
| 1) Error in custom provider, com.appdynamics.eum.geo.local.LocalXmlConfigException: Error parsing XML: null
| at com.appdynamics.eumcloud.OnPremModule.getGeoResolver(OnPremModule.java:261)
| at com.appdynamics.eumcloud.OnPremModule.getGeoResolver(OnPremModule.java:261)
| while locating com.appdynamics.eum.geo.api.GeoResolver
| Caused by: com.appdynamics.eum.geo.local.LocalXmlConfigException: Error parsing XML: null

 

Diagnosis

Looking at the error message, the EUM process is unable to parse the mapping.xml file. The changes made to the mapping file is not in a valid format and hence the resulting xml file is not proper. 

 

Solution

Validate the mapping.xml file and make the changes in the proper format so that it can be parsed by the EUM processor.

 

Before making any changes to the working mapping file, always keep a back-up so that you can revert back to the original file if the new edited one is malformed.

Version history
Last update:
‎12-21-2018 04:54 PM
Updated by:
Labels (1)
By replying you agree to the Terms and Conditions of the AppDynamics Community.
0 Kudos