Skip to main content

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
PGA of America Partnership
Secure What's Next
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

PRB: Reports fail when IIS not configured on port 80

Expand / Collapse


This article applies to:

  • Marshal Reporting Console

Symptoms:

  • Emailing reports fails
  • Error message: Failed to call the Job Executor Service
  • Additional error message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
  • Similar error messages may be displayed depending on the SQL connection method configured

Causes:

  • The default website on the MRC server is configured on a port other than port 80.

Resolution:

To resolve this issue:

  1. Edit the configuration files for the Marshal Reporting Console as detailed below. The files are located within the Marshal Reporting Console installation.
    • In each case you will find lines titled add key as shown below. In each line, for the ServerName substitute ServerName:Port (where Port is the port used by the website).
    • For instance:
      <add key="WebServerUrl" value=http://VM-EXAMPLE01:81/MarshalReportingConsole />
  2. After editing the files, restart the Marshal Reporting Scheduler and Marshal Reporting Executor Services.

Notes:

  • The most likely entry to require changing is the WebServerURL in all files.
  • Before changing the ReportServer URLs, verify the correct port in the Reporting Services Configuration Manager.
  • The path part of the URLs could differ depending on the version of SQL Server and the URL you chose for Marshal Reporting Console. Do not change the existing path information.
  • Do not add lines to the config files. Locate and edit the existing lines.

 

Bin\MMReportingExecutor.exe.config

<add key="WebServerURL" value="http://{ServerName}/MarshalReportingConsole/" />

<add key="ReportServiceWebReference.ReportService" value="http://{ServerName}/ReportServer_SQLEXPRESS/ReportService.asmx" />

<add key="ReportServerUrl" value="http://{ServerName}/ReportServer_SQLEXPRESS/>

Bin\MMReportingScheduler.exe.config

<add key="WebServerURL" value="http://{ServerName}/MarshalReportingConsole/" />

<add key="ReportServiceWebReference.ReportService" value="http://{ServerName}/ReportServer_SQLEXPRESS/ReportService.asmx" />

<add key="ReportServerUrl" value=http://{ServerName}/ReportServer_SQLEXPRESS />

Web.config

<add key="WebServerURL" value="http://{ServerName}/MarshalReportingConsole/" />

<add key="ReportServerUrl" value=http://{ServerName}/ReportServer_SQLEXPRESS" />


To contact LevelBlue about this article or to request support:


Rate this Article:
     

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.