EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB32096: "The procedure entry point ?parse@AbstractDOMParser@xerces_2_7@@QAEXQBG@Z could not be located in the dynamic link library xerces-c_2_7.dll" error occurs when creating a new metadata using MicroStrategy Configuration Wizard 9.x


Community Admin

• Strategy


This article describes potential root cause of the error message "MSTRSvr.exe - Entry Point Not Found The procedure entry point ?parse@AbstractDOMParser@xerces_2_7@@QAEXQBG@Z could not be located in the dynamic link library xerces-c_2_7.dll" using MIcroStrategy Configuration Wizard

SYMPTOM:
The following error message is received when attempting to create a new metadata using the Strategy Configuration Wizard 9.x, after the database username and password have been provided:

ka04W000000Of2hQAC_0EM440000002HU7.jpeg


MSTRSvr.exe - Entry Point Not Found
The procedure entry point ?parse@AbstractDOMParser@xerces_2_7@@QAEXQBG@Z could not be located in the dynamic link library xerces-c_2_7.dll

 

 
CAUSE:
More than one version of the DLL file stated in the error message, such as xerces-c_2_7.dll, exists in the machine where the Strategy Configuration Wizard 9.x was used:
 

ka04W000000Of2hQAC_0EM440000002HU6.jpeg

 
This dll conflict might occur if other third party software is installed on the machine.
 
ACTION:
There are three possible actions to resolve this issue:

  • Uninstall the third party software from the machine
  • Install Strategy 9.x on a different machine

While it is possible to modify the PATH environment variable to move the Strategy version of the DLL up in the path search list, this may cause problems with the 3rd party DLL; thus this method is not suggested.


Comment

0 comments

Details

Knowledge Article

Published:

June 13, 2017

Last Updated:

June 13, 2017