Jaa

TMG Reports stop working after installing TMG 2010 SP1

  • Artikkeli

This post is about an issue that might occur after you install Forefront TMG 2010 SP1 and Reports start to show blank result. When this happens, the following Alert appears on TMG console:

The daily summaries could not be summarized into a monthly summary for "07/2010". This may cause the report for this period to be inaccurate. Verify that no prior reporting configuration alerts exist, and that the reporting services on the designated Forefront TMG report server are running and accessible from all the array members. Use the source location 1001.158.7.0.8108.200 to report the failure.

Summary definition extended error information:

Name: 'Initialization'.

Method: 'Open Connection'.

SQL error description: Login failed for user 'ISA_RS_USER'

The failure is due to error: 0x80040e4d

In this scenario access to the report links URLs: http://localhost:8008/ReportServer_ISARS or http://127.0.0.:8008/Reports_ISARS will also fail. This issue might happen in some scenarios where there is a ‘database logon failure as showed in the error description (error code 0x80040e4d means DB_SEC_E_AUTH_FAILED). To address this issue run the script fixsqlserverlogin_vbs mentioned in the article: http://technet.microsoft.com/en-us/library/ff717843.aspx.

Note: this resolution is specifically for this scenario, where this alert is logged. Do not run the script for in other scenarios with same symptom (reporting showing blank result) but without this alert.

When you run the script, you have to wait for each node to sync with EMS and then run it on second node in case of TMG 2010 Enterprise Edition and on single TMG 2010 server in case of standard server. This script allows admin to change the password so that connection to the database can be established using new password and reports can be fetched from that.

Authors
Suraj Sigh
Support Engineer
Microsoft CSS Forefront Security Edge Team

Yuri Diogenes
Sr Security Support Escalation Engineer
Microsoft CSS Forefront Security Edge Team

Technical Reviewer
Bala Natarajan
Sr Security Support Escalation Engineer
Microsoft CSS Forefront Security Edge Team

Comments

  • Anonymous
    November 02, 2010
    I'm sorry but that is not true. I ran the script and nothing happens. And yes, I got THE SAME ERROR. Cheers Vuk

  • Anonymous
    October 03, 2011
    Lots of issues out there with Reports - is there a BLOG entry somewhere that provides step by step instructions on how to get this going?  

  • Anonymous
    December 09, 2011
    The comment has been removed

  • Anonymous
    June 13, 2013
    Check Firewall Logging Properties, Log storage format should be selected as SQL Server Express Database

  • Anonymous
    October 18, 2016
    Hi, iam getting following alert and event on TMG 2010 Sp2 Ru5event id : 31288SQL Server Reporting Services could not be configured for Forefront TMG. Restarting the Microsoft Forefront TMG Job Scheduler service may resolve this issue. Reporting Services error information: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.