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

KB33491: "Server Error in `/MicroStrategy` Application. Could not obtain computer name" error message appears when accessing MicroStrategy Web


Community Admin

• Strategy


"Server Error in `/MicroStrategy` Application. Could not obtain computer name" error message appears when accessing MicroStrategy Web

SYMPTOM:
When opening Strategy Web running on an IIS web server, the following error message is displayed in the browser:


Server Error in `/Strategy` Application.

________________________________________

Could not obtain computer name.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Could not obtain computer name.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a `Debug=true` directive at the top of the file that generated the error. Example:

  <%@ Page Language=`C#` Debug=`true` %>

or:

2) Add the following section to the configuration file of your application:

<configuration>

   <system.web>

       <compilation debug=`true`/>

   </system.web>

</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

 


   System.Web.HttpServerUtility.GetMachineNameInternal() +279

   System.Web.HttpServerUtility.get_MachineName() +26

   Strategy.MSTRControls.MSTRWebApplication.getServerName() +109

   Strategy.MSTRControls.MSTRWebApplication.InitializeAllControllers() +18

   Strategy.GlobalApp.Application_BeginRequest(Object sender, EventArgs e) +73

   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68

   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

________________________________________

Version Information: Microsoft .NET Framework Version:2.0.50727.3607; ASP.NET Version:2.0.50727.3082

 
CAUSE:
One possible cause of the problem is that the installation of ASP.NET 3.5 on that computer is incorrect
 
ACTION:
Reinstall ASP.NET 3.5 on the machine where the web server resides to resolve the problem.
 
Third Party Software Installation:
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.


Comment

0 comments

Details

Knowledge Article

Published:

June 14, 2017

Last Updated:

June 14, 2017