Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Services
Managed Detection & Response

Eliminate active threats with 24/7 threat detection, investigation, and response.

Co-Managed SOC (SIEM)

Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.

Advisory & Diagnostics

Advance your cybersecurity program and get expert guidance where you need it most.

Penetration Testing

Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.

Database Security

Prevent unauthorized access and exceed compliance requirements.

Email Security

Stop email threats others miss and secure your organization against the #1 ransomware attack vector.

Digital Forensics & Incident Response

Prepare for the inevitable with 24/7 global breach response in-region and available on-site.

Firewall & Technology Management

Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.

Solutions
BY TOPIC
Microsoft Security
Unlock the full power of Microsoft Security
Offensive Security
Solutions to maximize your security ROI
Rapidly Secure New Environments
Security for rapid response situations
Securing the Cloud
Safely navigate and stay protected
Securing the IoT Landscape
Test, monitor and secure network objects
Why Trustwave
About Us
Awards and Accolades
Trustwave SpiderLabs Team
Trustwave Fusion Security Operations Platform
Trustwave Security Colony
Partners
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Trustwave PartnerOne Program
Join forces with Trustwave to protect against the most advance cybersecurity threats
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 Trustwave 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
.