Reporting Failure with RC

All Replies

• Saturday, October 24, 2009 7:08 PMgreyt

   
  

  0

  Sign In to Vote
  Just to rule this in/out. If anyone has reporting working with a non en-us OS install, can you post here to confirm.
  
  Thanks.
  • Reply
  • Quote

   
• Monday, November 09, 2009 6:52 PMFJA PT

   
  

  0

  Sign In to Vote

  verify the configuration for de TMG reports on Release Notes for Forefront Threat Management Gateway RC
  
  Logging and reporting

  • When you publish reports to a directory on the Forefront TMG server, you must add the SYSTEM account to the file sharing permissions of the directory, to ensure that Forefront TMG will be able to publish the reports to the directory.
    
  • If your Forefront TMG deployment handles high volumes of traffic, you might need to change the default time of the Forefront TMG recurring report jobs from 1:00 to a later time, such as 3:00, to allow sufficient time to generate report summary data for the reporting summary that is scheduled to begin at 00:30.
    
  • The Forefront TMG default log maintenance policy defines the total size of logs files that the system saves before deleting old logs, as 8GB. For most organizations, this value is insufficient for the following log storage formats:
    
    
    • SQL Server Express Database
      
    • File
      
    To allow sufficient storage space for these logs, do one of the following for both firewall logging and Web proxy logging:
    
    
    • Disable the option Limit total size of log files.
      
    • Disable the option Limit total size of log files, assess your storage needs over a period of one week, and then enable this option again and set storage to the required size.
      
    For details, see Configuring Forefront TMG logs (http://go.microsoft.com/fwlink/?LinkId=165832).
    
  • TCP port 8008 is used for reporting purposes; assigning this port for any other purpose will interfere with Forefront TMG reporting services.
    
  • Reply
  • Quote

   
• Monday, November 16, 2009 8:51 AMgreyt

   
  

  0

  Sign In to Vote

  Thanks for taking the time to reply.
  
  I have reviewed the config and can't see anything wrong :-
  
  I checked the SQL Express default log folder. This has a file for every day since the server was installed. Total Size around 1GB. I changed the config to only retain 3 days and watched all but 3 days worth of files be deleted
  
  I turned off disable Limit Total size of log files
  
  Running netstat I can see the process wspsrv.exe is listening on port 8008
  
  I then ran dailysum.exe. it runs for around a minute and I can see high SQL processor usage during this time.  However I still get this error :-
  
  Description: The daily summary for day "11/15/2009" was not created. 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.105.7.0.7733.100 to report the failure.
  The failure is due to error: 0x80040e57
  
  This error is also reported if I let reports generate by themselves at 12.30am

  • Reply
  • Quote

   
• Thursday, November 19, 2009 8:27 AMgreyt

   
  

  0

  Sign In to Vote

  I have upgraded to the RTM release and the problem has been resolved :-)

  • Marked As Answer bygreyt Thursday, November 19, 2009 8:40 AM
  •  
  • Reply
  • Quote