Sign in
 
HomeProductsLibraryLearnDownloadsSupportForums
Microsoft Forefront TechCenter >
> 
> 
Forefront Reporting Server Timeout Error during Completing the Configuration Wizard

Respondido Forefront Reporting Server Timeout Error during Completing the Configuration Wizard

  • Monday, January 07, 2013 8:32 PM
     
     
    Sign In to Vote
    0

    Forefront was originally installed and conifugred before my time with the company. There have been enough complaints of people wanting to change the schedule times that my boss has finally pushed the issue through. The Forefront configurations are being pushed via a GPO, yet if I go to edit the GPO there is nothing there. Upon first researching the issue I thought that perhaps they were configured through a .adm file, however, I cannot find an adm file anywhere. I then realized that my searches were talking about a a different solution. That led me to looking in Microsoft Forefront Client Security Console, which, of course is not set up. I'm managing to get through some of the configuration of it but I'm running into an error on the Collection Server Compoenent section. The Reporting Server Timeout Adjustments is returning an error for Adjusts timeout via Web service. The log file reads:

    [1/7/2013 2:16:48 PM] Task(Reporting Server Timeout Adjustments)
    System.InvalidOperationException: Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
    The request failed with the error message:
    --
    <html>
        <head>
            <title>Runtime Error</title>
            <style>
             body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;}
             p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px}
             b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px}
             H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red }
             H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
             pre {font-family:"Lucida Console";font-size: .9em}
             .marker {font-weight: bold; color: black;text-decoration: none;}
             .version {color: gray;}
             .error {margin-bottom: 10px;}
             .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
            </style>
        </head>

        <body bgcolor="white">

                <span><H1>Server Error in '/' Application.<hr width=100% size=1 color=silver></H1>

                <h2> <i>Runtime Error</i> </h2></span>

                <font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif ">

                <b> Description: </b>An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
                <br><br>

                <b>Details:</b> To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".<br><br>

                <table width=100% bgcolor="#ffffcc">
                   <tr>
                      <td>
                          <code><pre>

    <!-- Web.Config Configuration File -->

    <configuration>
        <system.web>
            <customErrors mode="Off"/>
        </system.web>
    </configuration></pre></code>

                      </td>
                   </tr>
                </table>

                <br>

                <b>Notes:</b> The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.<br><br>

                <table width=100% bgcolor="#ffffcc">
                   <tr>
                      <td>
                          <code><pre>

    <!-- Web.Config Configuration File -->

    <configuration>
        <system.web>
            <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
        </system.web>
    </configuration></pre></code>

                      </td>
                   </tr>
                </table>

                <br>

        </body>
    </html>

    --.
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.Forefront.ClientSecurity.Configure.ReportManagerWS.ReportingService.CreateBatch()
       at Microsoft.Forefront.ClientSecurity.Configure.ReportServerTimeoutTask.ReportServerTask()
       at Microsoft.Forefront.ClientSecurity.Configure.ReportServerTimeoutTask.ThreadedWebServiceTask(Object x)Number of tasks completed: [1/7/2013 2:16:49 PM]

    Any help is much appreciated.

     

All Replies

  • Tuesday, January 08, 2013 2:44 AM
     
     Answered
    Sign In to Vote
    0

    Forefront Client Security uses a custom MMC console to create, edit and deploy policy to Active Directory as GPOs. FCS Policy can only be mananged from the FCS console that is installed with the FCS Management role. New installations of FCS will not be able to 'see' old (orphaned) policies or edit them.

    The FCS console provides the Dashboard (overview), Policy management, and the Configuration Wizard. The Configuration Wizard allows you configure any changes to the FCS roles.

    FCS supports six different topologies/configurations and is most often installed with most roles on one or two machines. You should try to identify the existing servers that have the FCS roles installed on them as opposed to installing new FCS roles in your environment.

    Management role: FCS MMC

    Collection role: MOM 2005

    Collection Database role: MOM OnePoint db

    Reporting role: SQL Reporting Svcs

    Reporting Database role: MOM SystemCenterReporting db

    Distribution role: WSUS

    Supported Topologies

    http://technet.microsoft.com/en-us/library/bb418915.aspx

    You might start with confirming which MOM 2005 server any FCS client is configured to use via these registy keys;

    HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\Configurations\ForefrontClientSecurity\Operations\Agent\Consolidators
    Consolidator 1 Host
    Consolidator 1 AD Name

    Thanks!

    ~Andrew Davis

    Andrew Davis | Sr. Technical Lead | CSS Security