KB32750: Various errors occur when trying to access MicroStrategy Office and Web Services 9.4.1 and above when Web Services is installed on Microsoft IIS 7 with Integrated Managed Pipeline mode.

• Strategy

Various errors occur when trying to access MicroStrategy Office and Web Services 9.4.1 and above when Web Services is installed on Microsoft IIS 7 with Integrated Managed Pipeline mode.

SYMPTOM
Users trying to connect to Strategy Office 9.4.1 and above when Strategy Web Services is hosted on IIS 7 get the following error message described in the image below:

Sample Code/Error


Client found response type of ‘text/html’, but expected ‘text/xml’.
The request failed with the error message:
<h2>500 – Internal server error.</h2>
<h3>There is a problem with the resource you are looking for, and it cannot be displayed.</h3>

When trying to access the Strategy Office configuration, the following error shows up:

Sample Code/Error


Properties could not be retrieved from Web Services at ‘http://<WSserver-name>/StrategyWS/MSTRWS.asmx’. Do you want to connect to a different Web Services URL?

Lastly, when trying to access the Strategy Web Services URL from a browser, the following error message is shown:

Sample Code/Error


IIS7.5 Detailed error – 500.24 – Internal Server Error
Server error in Application “DEFAULT WEB SITE/StrategyWS”
HTTP Error 500.24 – Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
Things you can try:
(You can set “Classic .NET AppPool” to the name of another application pool running in Classic managed pipeline mode)

CAUSE
As stated in the error message, the application pool was configured for Integrated managed pipeline mode, instead of Classic managed pipeline mode.

ACTION

In IIS 7, locate the Application Pools. It should be above the Default Websites folder.
Edit the Application Pools to access the following menu:

Change the Managed pipeline mode to Classic.
Restart IIS 7.

WORKAROUND
Instead of switching the managed pipeline mode, administrators should edit the web.config file located inside the installation folder for Strategy Web Services.
Add the following piece of code between </appSettings> and </configuration> tag:

Sample Code/Error


<system.webServer>
        <directoryBrowse enabled="false" />
        <validation validateIntegratedModeConfiguration="false" />
        <handlers accessPolicy="Read, Execute" />
        <defaultDocument enabled="true">
            <files>
                <add value="MSTRWS.asmx" />
            </files>
        </defaultDocument>
    </system.webServer>

Comment

0 comments

Details

Knowledge Article

Published:

May 19, 2017

Last Updated:

May 19, 2017

Client found response type of ‘text/html’, but expected ‘text/xml’. The request failed with the error message: <h2>500 – Internal server error.</h2> <h3>There is a problem with the resource you are looking for, and it cannot be displayed.</h3>

IIS7.5 Detailed error – 500.24 – Internal Server Error Server error in Application “DEFAULT WEB SITE/StrategyWS” HTTP Error 500.24 – Internal Server Error An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode. Things you can try: (You can set “Classic .NET AppPool” to the name of another application pool running in Classic managed pipeline mode)

<system.webServer> <directoryBrowse enabled="false" /> <validation validateIntegratedModeConfiguration="false" /> <handlers accessPolicy="Read, Execute" /> <defaultDocument enabled="true"> <files> <add value="MSTRWS.asmx" /> </files> </defaultDocument> </system.webServer>