locked
Error when installing Forefront Client Security

    Întrebare

  • Hi all,

    I'm installing FCS to a 1-server topology.

    This is log file:

    [19/01/2007 16.49.11] Verifications started.

    [19/01/2007 16.49.11] Verification(Verify operating system requirements)

    [19/01/2007 16.49.11] Verification(Verify hardware requirements)

    Warning: For the single-server configuration, it is recommended that you have two or more processors with a speed of 2850 MHz or greater.
    Warning: For the single-server configuration, it is recommended that you have 4096 MB or more of memory.
    Warning: For the single-server configuration, it is recommended that you have 18632 MB of disk space available.

    [19/01/2007 16.49.12] Verification(Verify software prerequisites)

    [19/01/2007 16.49.12] Verification(Verify MOM operations database)

    [19/01/2007 16.49.13] Verification(Verify access to MOM management server)

    [19/01/2007 16.49.13] Verification(Verifying collection server DAS account)

    Error: Account sqlaccount is not valid or the password is incorrect.

    [19/01/2007 16.49.13] Verification(Verify access to MOM Report server)

    [19/01/2007 16.49.14] Verification(Verify MOM reporting database configuration)

    [19/01/2007 16.49.16] Verification(Verify URLs for reports)

    Error: Could not access 'http://<myserver>/Reports'. The remote server returned an error: (500) Internal Server Error..

    [19/01/2007 16.49.17] Verification(Verify MOM Agent account)

    Error: Account momdts is not valid or the password is incorrect.

    [19/01/2007 16.49.17] Verification(Verify MOM DAS account)

    Error: Account sqlaccount is not valid or the password is incorrect.

    [19/01/2007 16.49.17] Verification(Verifying MOM DTS account)

    Error: Account sqlaccount is not valid or the password is incorrect.

    [19/01/2007 16.49.18] Verification(Verify MOM reporting database service startup)

    [19/01/2007 16.49.18] Verifications completed.

    19 ianuarie 2007 15:52

Toate mesajele

  • Thanks for your post, it looks like you have a couple of problems.  First, please make sure you are specifying domain names for  ‘sqlaccount’ and ‘momdts’ like DOMAIN\username so that they can be properly validated.

     

    Next, you have an http 500 for 'http://<myserver>/Reports'  please open that URL in your browser and see if there is additional information provided.  If not, you may want to look in your application log to see if there are IIS or SQL reporting services errors.

     

    Thanks,

    Craig

    22 ianuarie 2007 16:08
  • ok thanks you!

    first problem is ok! i have specify <servername>\<username>... and work fine! :-)

    now i have this problem:

     

    [22/01/2007 11.48.04] Verifications started.
    [22/01/2007 11.48.05] Verification(Verify operating system requirements)
    [22/01/2007 11.48.05] Verification(Verify hardware requirements)
    Warning: For the single-server configuration, it is recommended that you have two or more processors with a speed of 2850 MHz or greater.
    Warning: For the single-server configuration, it is recommended that you have 4096 MB or more of memory.
    Warning: For the single-server configuration, it is recommended that you have 17608 MB of disk space available.
    [22/01/2007 11.48.06] Verification(Verify software prerequisites)
    [22/01/2007 11.48.06] Verification(Verify MOM operations database)
    [22/01/2007 11.48.06] Verification(Verify access to MOM management server)
    [22/01/2007 11.48.07] Verification(Verifying collection server DAS account)
    [22/01/2007 11.48.07] Verification(Verify access to MOM Report server)
    [22/01/2007 11.48.08] Verification(Verify MOM reporting database configuration)
    [22/01/2007 11.48.10] Verification(Verify URLs for reports)
    Error: Could not access 'http://MYSERVER/Reports'. The remote server returned an error: (500) Internal Server Error..
    [22/01/2007 11.48.10] Verification(Verify MOM Agent account)
    [22/01/2007 11.48.11] Verification(Verify MOM DAS account)
    [22/01/2007 11.48.11] Verification(Verifying MOM DTS account)
    [22/01/2007 11.48.12] Verification(Verify MOM reporting database service startup)
    [22/01/2007 11.48.12] Verifications completed.

     

    When I browse to http://myserver/reports I get:
    The request failed with HTTP status 400: Bad Request.

    When i try to browse to http://myserver/reportserver  i get:
    myserver/ReportServer - /

    Microsoft SQL Server Reporting Services versione 9.00.2047.00


    Can you help me please??

    23 ianuarie 2007 08:19
  • can anyone help me please?

    thanks you!

    stefano

    www.sysadmin.it

     

    27 ianuarie 2007 18:49
  • Hello Stefano,

     

    Sorry we missed picking up on this one.  Are you still experiencing errors when accessing http://myserver/reports ?

     

    Please note whether they are http 500 or http 400 errors.  The log above seems to indicate both.

     

    Did you find any information in the application event log, IIS or SQL reporting services log files?

     

     

    Thanks,

    Craig

    5 februarie 2007 16:03
  • ok no problem! :-)

    I still have the problem!

    ServerSetup.log:
    [05/02/2007 17.22.18] Verification(Verify operating system requirements)
    [05/02/2007 17.22.18] Verification(Verify hardware requirements)
    Warning: For the single-server configuration, it is recommended that you have two or more processors with a speed of 2850 MHz or greater.
    Warning: For the single-server configuration, it is recommended that you have 4096 MB or more of memory.
    Warning: For the single-server configuration, it is recommended that you have 16584 MB of disk space available.
    [05/02/2007 17.22.19] Verification(Verify software prerequisites)
    [05/02/2007 17.22.19] Verification(Verify MOM operations database)
    [05/02/2007 17.22.19] Verification(Verify access to MOM management server)
    [05/02/2007 17.22.20] Verification(Verifying collection server DAS account)
    [05/02/2007 17.22.20] Verification(Verify access to MOM Report server)
    [05/02/2007 17.22.21] Verification(Verify MOM reporting database configuration)
    [05/02/2007 17.22.23] Verification(Verify URLs for reports)
    Error: Could not access 'http://MYSERVER/Reports'. Unable to connect to the remote server.
    Error: Could not access 'http://MYSERVER/ReportServer'. Unable to connect to the remote server.
    [05/02/2007 17.22.23] Verification(Verify MOM Agent account)
    [05/02/2007 17.22.24] Verification(Verify MOM DAS account)
    [05/02/2007 17.22.24] Verification(Verifying MOM DTS account)
    [05/02/2007 17.22.25] Verification(Verify MOM reporting database service startup)
    [05/02/2007 17.22.25] Verifications completed.

    IIS Log:
    iis log for http://myserver/Reports
    2007-02-05 16:25:57 W3SVC1 192.168.1.1 GET /Reports - 80 - 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
    2007-02-05 16:25:57 W3SVC1 192.168.1.1 GET /Reports - 80 - 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 1 0
    2007-02-05 16:25:57 W3SVC1 192.168.1.1 GET /Reports - 80 myserver\myuser 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 301 0 0
    2007-02-05 16:27:30 W3SVC1 192.168.1.1 GET /Reports/Home.aspx - 80 myserver\myuser 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 302 0 0
    2007-02-05 16:27:35 W3SVC1 192.168.1.1 GET /Reports/Pages/Folder.aspx - 80 myserver\myuser 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 500 0 0
    2007-02-05 16:27:35 W3SVC1 192.168.1.1 GET /Reports/js/ReportingServices.js - 80 myserver\myuser 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 200 0 0
    2007-02-05 16:27:36 W3SVC1 192.168.1.1 GET /Reports/styles/ReportingServices.css - 80 myserver\myuser 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 200 0 0
    2007-02-05 16:27:36 W3SVC1 192.168.1.1 GET /Reports/images/blank.gif - 80 - 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
    2007-02-05 16:27:36 W3SVC1 192.168.1.1 GET /Reports/images/48error.jpg - 80 - 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
    2007-02-05 16:27:36 W3SVC1 192.168.1.1 GET /Reports/images/blank.gif - 80 - 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 1 0
    2007-02-05 16:27:36 W3SVC1 192.168.1.1 GET /Reports/images/48error.jpg - 80 - 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 1 0
    2007-02-05 16:27:36 W3SVC1 192.168.1.1 GET /Reports/images/blank.gif - 80 myserver\myuser 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 200 0 0
    2007-02-05 16:27:36 W3SVC1 192.168.1.1 GET /Reports/images/48error.jpg - 80 myserver\myuser 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 200 0 0

    iis log for http://myserver/reportserver
    2007-02-05 16:31:33 W3SVC1 192.168.1.1 GET /reportserver - 80 - 192.168.116.63 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
    2007-02-05 16:31:33 W3SVC1 192.168.1.1 GET /reportserver - 80 - 192.168.116.63 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 1 0

     

    APPLICATION LOG IS EMPTY

    SYSTEM LOG: (i don't know if this error is significative!)
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {BA126AD1-2166-11D1-B1D0-00805FC1270E} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.

    SQL REPORTING SERVICES LOG FILES (ReportServerWebApp__02_05_2007_17_27_29.log)
    <Header>
      <Product>Microsoft SQL Server Reporting Services Version 9.00.2047.00</Product>
      <Locale>en-US</Locale>
      <TimeZone>W. Europe Standard Time</TimeZone>
      <Path>E:\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles\ReportServerWebApp__02_05_2007_17_27_29.log</Path>
      <SystemName>MYSERVER</SystemName>
      <OSName>Microsoft Windows NT 5.2.3790 Service Pack 1</OSName>
      <OSVersion>5.2.3790.65536</OSVersion>
    </Header>
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing ReportBuilderTrustLevel to '0'  as specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing MaxScheduleWait to default value of '1' second(s) because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing DatabaseQueryTimeout to default value of '30' second(s) because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing ProcessRecycleOptions to default value of '0'  because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing RunningRequestsScavengerCycle to default value of '30' second(s) because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing RunningRequestsDbCycle to default value of '30' second(s) because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing RunningRequestsAge to default value of '30' second(s) because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing CleanupCycleMinutes to default value of '10' minute(s) because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing WatsonFlags to default value of '1064'  because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing WatsonDumpOnExceptions to default value of 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException'  because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to default value of 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException'  because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing SecureConnectionLevel to default value of '1'  because it was not specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing DisplayErrorLink to 'True'  as specified in Configuration file.
    w3wp!library!1!05/02/2007-17:27:30:: i INFO: Initializing WebServiceUseFileShareStorage to default value of 'False'  because it was not specified in Configuration file.
    w3wp!ui!5!05/02/2007-17:27:34:: e ERROR: The request failed with HTTP status 400: Bad Request.
    w3wp!ui!5!05/02/2007-17:27:35:: e ERROR: HTTP status code --> 500
    -------Details--------
    System.Net.WebException: The request failed with HTTP status 400: Bad Request.

       at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()

       at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()

       at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)

       at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()

       at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)

       at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)

       at System.EventHandler.Invoke(Object sender, EventArgs e)

       at System.Web.UI.Control.OnInit(EventArgs e)

       at System.Web.UI.Page.OnInit(EventArgs e)

       at System.Web.UI.Control.InitRecursive(Control namingContainer)

       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    w3wp!ui!5!05/02/2007-17:27:36:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
       at System.Threading.Thread.AbortInternal()
       at System.Threading.Thread.Abort(Object stateInfo)
       at System.Web.HttpResponse.End()
       at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
       at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at    at System.Threading.Thread.AbortInternal()
       at System.Threading.Thread.Abort(Object stateInfo)
       at System.Web.HttpResponse.End()
       at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
       at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)
    w3wp!ui!5!05/02/2007-17:33:43:: e ERROR: The request failed with HTTP status 400: Bad Request.
    w3wp!ui!5!05/02/2007-17:33:43:: e ERROR: HTTP status code --> 500
    -------Details--------
    System.Net.WebException: The request failed with HTTP status 400: Bad Request.

       at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()

       at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()

       at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)

       at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()

       at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)

       at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)

       at System.EventHandler.Invoke(Object sender, EventArgs e)

       at System.Web.UI.Control.OnInit(EventArgs e)

       at System.Web.UI.Page.OnInit(EventArgs e)

       at System.Web.UI.Control.InitRecursive(Control namingContainer)

       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    w3wp!ui!5!05/02/2007-17:33:44:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
       at System.Threading.Thread.AbortInternal()
       at System.Threading.Thread.Abort(Object stateInfo)
       at System.Web.HttpResponse.End()
       at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
       at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at    at System.Threading.Thread.AbortInternal()
       at System.Threading.Thread.Abort(Object stateInfo)
       at System.Web.HttpResponse.End()
       at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
       at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)
    w3wp!ui!5!05/02/2007-17:34:38:: e ERROR: The request failed with HTTP status 400: Bad Request.
    w3wp!ui!5!05/02/2007-17:34:38:: e ERROR: HTTP status code --> 500
    -------Details--------
    System.Net.WebException: The request failed with HTTP status 400: Bad Request.

       at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()

       at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()

       at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)

       at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()

       at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)

       at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)

       at System.EventHandler.Invoke(Object sender, EventArgs e)

       at System.Web.UI.Control.OnInit(EventArgs e)

       at System.Web.UI.Page.OnInit(EventArgs e)

       at System.Web.UI.Control.InitRecursive(Control namingContainer)

       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    w3wp!ui!5!05/02/2007-17:34:39:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
       at System.Threading.Thread.AbortInternal()
       at System.Threading.Thread.Abort(Object stateInfo)
       at System.Web.HttpResponse.End()
       at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
       at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at    at System.Threading.Thread.AbortInternal()
       at System.Threading.Thread.Abort(Object stateInfo)
       at System.Web.HttpResponse.End()
       at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
       at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)

    SQL REPORTING SERVICES LOG FILES (ReportServer__02_05_2007_17_31_39.log
    <Header>
      <Product>Microsoft SQL Server Reporting Services Version 9.00.2047.00</Product>
      <Locale>en-US</Locale>
      <TimeZone>W. Europe Standard Time</TimeZone>
      <Path>E:\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles\ReportServer__02_05_2007_17_31_39.log</Path>
      <SystemName>MYSERVER</SystemName>
      <OSName>Microsoft Windows NT 5.2.3790 Service Pack 1</OSName>
      <OSVersion>5.2.3790.65536</OSVersion>
    </Header>
    w3wp!webserver!5!05/02/2007-17:31:39:: i INFO: Reporting Web Server started
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing ConnectionType to '0'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing IsSchedulingService to 'True'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing IsNotificationService to 'True'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing IsEventService to 'True'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing IsWebServiceEnabled to 'True'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing ProcessRecycleOptions to '0'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing WatsonFlags to '1064'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing SecureConnectionLevel to '0'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing DisplayErrorLink to 'True'  as specified in Configuration file.
    w3wp!library!5!05/02/2007-17:31:39:: i INFO: Initializing WebServiceUseFileShareStorage to 'False'  as specified in Configuration file.
    w3wp!resourceutilities!5!05/02/2007-17:31:39:: i INFO: Reporting Services starting SKU: Enterprise
    w3wp!resourceutilities!5!05/02/2007-17:31:39:: i INFO: Evaluation copy: 0 days left
    w3wp!runningjobs!5!05/02/2007-17:31:39:: i INFO: Database Cleanup (Web Service) timer enabled: Next Event: 600 seconds.  Cycle: 600 seconds
    w3wp!runningjobs!5!05/02/2007-17:31:39:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds.  Cycle: 60 seconds
    w3wp!runningjobs!5!05/02/2007-17:31:39:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds.  Cycle: 60 seconds
    w3wp!runningjobs!5!05/02/2007-17:31:39:: i INFO: Memory stats update timer enabled: Next Event: 60 seconds.  Cycle: 60 seconds
    w3wp!library!5!02/05/2007-17:31:39:: i INFO: Catalog SQL Server Edition = Enterprise
    w3wp!webserver!5!02/05/2007-17:31:40:: i INFO: Processed folder '/'

    Thank you very much!

    Stefano

     

    5 februarie 2007 16:42
  • A couple of thoughts and questions:

     

    1.    The SYSTEM log message with : {BA126AD1-2166-11D1-B1D0-00805FC1270E} is unrelated.  We have a KB article forthcoming on this, however since it seems to appear more often on FCS servers.

    2.    This line is a reflection of the problem:

    2007-02-05 16:27:35 W3SVC1 192.168.1.1 GET /Reports/Pages/Folder.aspx - 80 myserver\myuser 192.168.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 500 0 0

    Notice the HTTP 500 error.  The callstack in the ReportServerWebApp should be additional information on the problem.

     

    3.    Is MYSERVER in  'http://MYSERVER/Reports' really the name of your server or is it an alias?  We has seen SQL reporting services fail on GetSecureMethods() in this manner when a hostname is being used instead of the machine name.

     

     

    4.    When you setup SQL reporting services, did you require SSL?  You can review this by looking at All Programs > Microsoft SQL Server 2005 > Configuration Tools > Reporting Services Configuration.  Select “Report Server Virtual Directory”.

     

     

    Thanks,

    Craig

    6 februarie 2007 15:07
  • MYSERVER is really the name of my server!

    SQL reporting services not require SSL!

    thanks you for your support!

    6 februarie 2007 15:25
  • hi craig,

    have you good news?

    11 februarie 2007 12:24
  • hi craig,

    are you in?

    15 februarie 2007 12:28
  • Sorry for the delay.

     

    Can you create a feedback bug based upon this issue?

     

    1.    Visit our Connect portal bug submission page: http://connect.microsoft.com/site/sitehome.aspx?SiteID=27   

    2.    Follow the steps to register on the site and then click the 'Feedback' link in the left nav

    3.    Then submit the log files we have above, as well as the application and system event logs from the machine

    4.    Also, if you have WSUS on the machine, does the WSUS administration website work?

     

    Thanks,

    Craig

    22 februarie 2007 17:56
  • Did this problem ever get resolved?

    I have a very similar issue, it is the only error appearing during the setup. If I try and see the ReportServer VS in IIS, it will not display, and shows the message:

    Reporting Services Error
    --------------------------------------------------------------------------------
     
    The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) Get Online Help
    Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

    --------------------------------------------------------------------------------
    SQL Server Reporting Services

     

    ReportServer is installed on the default web site on port 80, and sharepoint is installed separately on another site on another port.

    Cannot access the Report Manager Virtual Directory in the SQL Report Server Configuration Tool (it is just greyed out.)

    the installation log shows the following:

    [2/26/2007 12:24:57 PM] Verifications started.


    [2/26/2007 12:24:58 PM] Verification(Verify operating system requirements)

    [2/26/2007 12:24:58 PM] Verification(Verify hardware requirements)

    Warning: For the collection server role, the reporting server role, it is recommended that you have two or more processors with a speed of 950 MHz or greater.
    Warning: For the collection server role, the reporting server role, you must have 512 MB or more of memory.
    Warning: For the collection server role, the reporting server role, it is recommended that you have 18432 MB of disk space available.

    [2/26/2007 12:24:58 PM] Verification(Verify software prerequisites)

    [2/26/2007 12:25:02 PM] Verification(Verify MOM operations database)

    [2/26/2007 12:25:02 PM] Verification(Verify access to MOM management server)

    [2/26/2007 12:25:03 PM] Verification(Verifying collection server DAS account)

    [2/26/2007 12:25:03 PM] Verification(Verify access to MOM Report server)

    [2/26/2007 12:25:03 PM] Verification(Verify MOM reporting database configuration)

    [2/26/2007 12:25:04 PM] Verification(Verify URLs for reports)

    Error: Could not access 'http://FOREFRONTSERVER/Reports'. The remote server returned an error: (404) Not Found..
    Error: Could not access 'http://FOREFRONTSERVER/ReportServer'. The remote server returned an error: (500) Internal Server Error..

    [2/26/2007 12:25:04 PM] Verification(Verify MOM Agent account)

    [2/26/2007 12:25:05 PM] Verification(Verify MOM DAS account)

    [2/26/2007 12:25:05 PM] Verification(Verifying MOM DTS account)

    [2/26/2007 12:25:05 PM] Verification(Verify MOM reporting database service startup)

    [2/26/2007 12:25:06 PM] Verifications completed.

     

    I have lots of lovely errors in the Event Viewer, Applications log:

    Report Server 107 Report Server (MSSQLSERVER) cannot connect to the report server database., MSSQLSERVER 18456 Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <local machine>] and Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 10.0.0.25]

     

    26 februarie 2007 19:17
  • I believe to fix your problem we need to grant permissions for the machine account on the ReportServer SQL database.

     

    On the FCS Reporting server, please do the following:

    1.    All Programs > Microsoft SQL Server > Configuration Tools > Reporting Services Configuration

    2.    Click Connect

    3.    Server Status : Make sure the service is running.  You should see a green check mark on the left.

    4.    Report Server/Report Manager Virtual directory : You should see ReportServer and Reports respectively. You should see a green check mark on the left.

    5.    Windows Service Identity:  Verify the appropriate identity is set. You should see a green check mark on the left.

    6.    Web Service Identity : likely NetworkService. Verify both VDirs above are in the same application pool.  You should see a green check mark on the left.

    7.    Database Setup: This is where I think you have the problem. Set the appropriate account in the drop down, either Windows credentials or Service credentials, then click Apply. It should grant the appropriate database permissions.  You should see a green check mark on the left. 

    8.    Initialize : You should see your machine / instance name here with a check mark. You should see a green check mark on the left.

     

    Assuming you see all green checks when you are done that should eliminate “The report server cannot open a connection to the report server database

     

    Thanks,

    Craig

    26 februarie 2007 21:00
  • Thanks Craig for your information.

    I also getting the same problem. When I check the Reporting Services Configuration console, all the items that u mentioned are alr in green mark, except "Initialize". This setting is DISABLED as I can even highlight it. May I know wat's the reason? Any solution for it?

     

    Thanks.

    Vivian

    1 martie 2007 08:32
  • Unfortunately, I have not seen this before.  You may want to go to the “Database setup” portion of the utility.  Make sure that “ReportServer” is listed in the dropdown and clicking the “Connect” button works.

     

    Thanks,

    Craig

    1 martie 2007 22:49
  • Has this ever been fixed?
    9 iunie 2010 13:49
  •  

    "Just a quick post for Reporting Services.

     

    If you are using the Standard edition of Reporting Services, the initialization pane is grayed out in Reporting Services Configuration Manager.

     

    You should still see the checkmark. This is grayed out because scale out to a web farm is not available in this edition. If the Report Server Windows service is running, it is already initialized."

     

    http://blogs.msdn.com/b/sqlblog/archive/2006/10/23/why-is-the-initialization-checkmark-sometimes-grayed-out-in-reporting-services-2005-configuration-manager.aspx

     

     
    9 iunie 2010 16:24