Reporting Services Cube Status

Hi all,
I am newbie to reporting service of team foundation server 2013. I just want to know what is the use of cube in reporting services in team foundation server environment. please clear my doubts.
Thanks for help.

Hi Vishwajeet,
Thanks for your post.
If you configure Reporting Service for TFS 2013 Server, TFS will create the warehouse database and Tfs_Analysis cube database, then TFS report files will get data from cube. Please refer to below documents:
http://msdn.microsoft.com/en-us/library/ms244710.aspx
http://msdn.microsoft.com/en-us/library/ms244691.aspx
http://msdn.microsoft.com/en-us/library/bb649552.aspx
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

  • Reporting Services Point status message errors.

    My Reporting Services Point seems to work OK -all reports are available and run correctly both through the console and via the website. However, I am seeing the following warning in the SMS_SRS_REPORTING_POINT status messages every hour:
    "The SQL Reporting Services datasource on Reporting point server "Databaseserver.contoso.com" is missing or has been changed outside of Configuration Manager.  It will be rebuilt based on the RSP configuration."
    Here's what I think is causing the issue, but I don't know how to solve it.
    The reports database is on the same remote SQL server as my site database. Because these site systems were installed automatically through the SCCM installation process, they show up in the Servers and Site Systems Role without an intranet FQDN. However,
    when I add the RSP to the database server, it creates a new entry because when manually adding site systems SCCM insists on automatically adding the intranet FQDN. So I now have two separate entries for the same server:
    \\DBServer01 - component server, site database server, site system
    \\DBServer01.contoso.com - component server, reporting services point, site system
    Any thoughts on how to stop these errors?

    Yes, I know this is an old post, but I’m trying to clean them up.
    In the past when I have seen this, they will automatically clean themselves up after a few days. (aka up to a week later). Have it clean itself up yet?
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • SCCM 2012 monitoring - Site Status - Reporting Services Point - Status Critical

    Hi all,
    I have noticed that the Site Status under Monitoring shows Reporting services point as in Critical state though we do not see anything wrong with SCCM as such (at least we haven't been reported any problems thus far). There is nothing in the event viewer
    on SQL Server. Just wanted to know how to resolve this issue. Could you help?
    When I try to open status messages for Reporting Services (for any days) it does not return anything as if there are no status messages for this role. Also, could you let me know the log file locations/names for Reporting services point?

    Here it is... I have replaced server names with a dummy name.
    =================
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.588-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.596-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.616-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.641-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.686-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.686-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.713-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.715-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.716-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.716-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.339-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.336-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.347-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.357-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.377-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.404-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.451-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.451-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.478-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.480-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.481-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.481-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.160-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.159-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.168-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.188-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.237-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.264-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.462-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.462-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.539-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.541-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.542-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.542-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.796-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.795-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.804-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.813-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.834-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.859-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.904-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.905-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.940-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.942-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.943-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.943-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.724-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.725-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.725-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.726-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.723-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.731-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.752-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.776-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.813-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.902-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.902-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.954-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.956-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.957-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.957-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.728-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.729-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.729-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.730-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.727-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.738-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.747-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.769-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.799-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.848-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.848-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.875-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.496-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.494-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.503-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.512-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.534-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.563-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.610-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.610-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.646-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.648-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.653-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.654-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.352-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.351-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.361-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.370-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.393-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.432-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.484-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.485-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.520-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.522-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.530-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.531-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.270-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.270-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.271-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.271-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.268-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.277-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.286-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.308-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.334-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.380-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.381-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.421-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.423-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.424-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.424-60><thread=6072 (0x17B8)>
    Confirmed the configuration of SRS role [ConfigMgr Report Users].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.088-60><thread=6072 (0x17B8)>
    Confirmed the configuration of SRS role [ConfigMgr Report Administrators].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.098-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.700-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.736-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Asset Intelligence].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.758-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Compliance and Settings Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.791-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Administrative Security].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.815-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Operating System].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.849-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - A Compliance].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.870-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - B Deployment Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.906-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - C Deployment States].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.929-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - D Scan].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.961-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - E Troubleshooting].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.998-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Driver Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.033-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.067-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployments].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.099-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Progress].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.127-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - References].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.155-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/State Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.192-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.221-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Virtual Applications].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.265-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.303-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.326-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/User - Device Affinity].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.362-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Metering].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.381-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.413-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.432-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Device Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.470-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages - Audit].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.495-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Alerts].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.529-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Client Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.551-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Client Push].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.585-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - CD-ROM].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.609-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Disk].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.642-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.666-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Memory].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.700-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Modem].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.724-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Network Adapter].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.755-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Processor].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.778-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - SCSI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.815-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Sound Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.835-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Video Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.867-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Client Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.888-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Discovery and Inventory Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.924-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.952-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Server Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.985-60><thread=6072 (0x17B8)>
    The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.007-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.042-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Power Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.073-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Wake On LAN].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.096-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.132-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Files].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.156-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Companies and Products].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.189-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Users].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.209-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Collections].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.243-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Content].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.268-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Out Of Band Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.298-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.320-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages/Status Messages - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.349-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection/Endpoint Protection - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.367-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring/Software Distribution - Application Monitoring - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.397-60><thread=6072 (0x17B8)>
    The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.418-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.458-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Replication Traffic].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.492-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Upgrade Assessment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.511-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/User Data and Profiles Health].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.542-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.571-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.599-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Asset Intelligence].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.632-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Compliance and Settings Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.656-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Administrative Security].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.689-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Operating System].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.709-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - A Compliance].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.742-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - B Deployment Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.767-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - C Deployment States].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.800-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - D Scan].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.822-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - E Troubleshooting].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.856-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Driver Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.880-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.911-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployments].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.932-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Progress].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.966-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - References].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.988-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/State Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.020-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.045-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Virtual Applications].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.078-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.113-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.137-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/User - Device Affinity].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.170-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Metering].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.193-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.227-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.247-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Device Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.280-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages - Audit].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.306-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Alerts].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.339-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Client Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.361-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Client Push].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.395-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - CD-ROM].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.415-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Disk].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.445-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.467-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Memory].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.497-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Modem].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.518-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Network Adapter].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.550-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Processor].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.570-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - SCSI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.602-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Sound Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.625-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Video Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.655-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Client Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.676-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Discovery and Inventory Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.710-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.731-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Server Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.762-60><thread=6072 (0x17B8)>
    The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.785-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.821-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Power Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.852-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Wake On LAN].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.878-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.899-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Files].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.933-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Companies and Products].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.967-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Users].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.994-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Collections].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.027-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Content].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.052-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Out Of Band Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.084-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.106-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages/Status Messages - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.135-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection/Endpoint Protection - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.153-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring/Software Distribution - Application Monitoring - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.186-60><thread=6072 (0x17B8)>
    The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.209-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.250-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Replication Traffic].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.284-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Upgrade Assessment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.304-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/User Data and Profiles Health].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.338-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>

  • Reporting Services Cube Parameters not generated automatically

    Hi, I have a few reports which display data from an Analysis Services cube.
    For example my report uses Dateset1 as the source of the report.
    When I modify Dataset1 by adding a new parameters in the Query Designer, a new (hidden) dataset is created called:  CustomerAgeCustomerAge.
    But a new parameter on the report is not automatically generated. In the Dataset1 - Dataset Properties \ Parameters there is an entry for the parameter which should be created e.g. [@CustomerAgeCustomerAge]. I can work around this but I'd like to find the
    cause. Is there a max number of parameters which are generated automatically - my report has 12.

    Hi darkdusky,
    Based on my understanding, when you add a new parameter in dataset query, the parameter doesn’t generate automatically in report parameters.
    In Reporting Service, when we define a dataset query that contains a query variable, the query command is parsed. For each query variable, a corresponding dataset parameter and report parameter are created automatically. As we tested in our environment,
    even we create thirteen parameters in data set query, corresponding parameters automatically appear both in report parameters and dataset parameters in dataset properties.
    So in your scenario, I would like to know how about your query with those parameters. If possible, please provide some screenshots of results before and after you add a new parameter in dataset query.
    If you have any question, please feel free to ask.
    Best regards,
    Qiuyun Yu

  • Configuring Reporting Service Add-in for sharepoint - HTTP status 401: Unauthorized.

    I have the following setup
    Machine 1
    WSS 3.0
    Installed Reporting Service Add-in
    Machine 2
    Reporting Service
    Sharepoint Object Model
    SQL Server
    Sharepoint and Report Server DB
    I have congigured Reporting Service for Sharepoint Integrated Mode adn Created new Reprot Server DB
    Sahre Point Integration is Green and verified link
    In Sharepoint Central Administration
    Manage Reporting Service Integratio i have selected the URL and "Trusted Account" as my web applications use "Windows Integration - NTLM".
    All services, DB access everything running under one domain user account.
    I am logged into sharepoint with same account. When clieck on set server defaults i get following error
    An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. --> Server was unable to process request. ---> The request failed with HTTP status 401: Unauthorized.
    Same error when i try to add a report to a sharepoint webapplication
    The domain account is part of "Farm Administration", "site colletion administrato" and local administrator also on both servers.
    Can someone let me know how to fix this.

    jpmartop,
    were you able to get this to work?
    We have a 4 server topolgy.
    moss
    wfe
    sql
    ssrs
    and are using Kerberos.
    I've installed the wfe on the ssrs and am using a domain user for services, web and pools.
    I get all green dots in the ssrs config.
    in Central Admin, Grant access seems to work with the domain user, but set defaults gives me:
    HTTP status 401: Unauthorized.
    What should my web security on the default web site and reports and reports server look like? Integrated Security
    Should the SSRS WFE entry in MOSS have Web application service turned on?
    I've checked that my SPNs are good.I've installed sql server sp2 and a did windows update on all servers..
    Could it be the user I log into the Central Admin with.. it's got server administrator and Farm administrator?
    Thanks for any help or information.

  • Sharepoint 2013 Reporting Services & OLAP Cubes for Data Modeling.

    I've been using PowerPivot & PowerView in Excel 2013 Pro for some time now so am now eager to get set up with Sharepoint 2013 Reporting Services.
    Before set up Reporting Services  I have just one question to resolve.
    What are the benefits/differences of using a normal flat table set up, compared to an OLAP cube?
    Should I base my Data Model on an OLAP Cube or just Connect to tables in my SQL 2012 database?
    I realize that OLAP Cubes aggregate data making it faster to return results, but am unclear if this is needed with Data Modeling for Sharepoint 2013.
    Many thanks,
    Mike

    So yes, PV is an in-memory cube. When data is loaded from the data source, it's cached in memory, and stored (compressed) in the Excel file. (also, same concept for SSAS Tabular mode... loads from source, cached in mem, but also stored (compressed) in data
    files, in the event that the server reboots, or something similar).
    As far as performance, tabular uses memory, but has a shorter load process (no ETL, no cube processing)... OLAP/MDX uses less memory, by requiring ETL and cube processing... technically tabular uses column compression, so the memory consumption will be based
    on the type of data (numeric data is GREAT, text not as much)... but the decision to use OLAP (MDX)/TAB (DAX) is just dependent on the type of load and your needs... both platforms CAN do realtime queries (ROLAP in multidimensional, or DirectQuery for tabular),
    or can use their processed/in-memory cache (MOLAP in multidimensional, xVelocity for tabular) to process queries.
    if you have a cube, there's no need to reinvent the wheel (especially since there's no way to convert/import the BIDS/SSDT project from MDX to DAX). If you have SSAS 2012 SP1 CU4 or later, you can connect PV (from Excel OR from within SP) directly to the
    MDX cube.
    Generally, the benefit of PP is for the power users who can build models quickly and easily (without needing to talk to the BI dept)... SharePoint lets those people share the reports with a team... if it's worthy of including in an enterprise warehouse,
    it gets handed off to the BI folks who vet the process and calculations... but by that time, the business has received value from the self-service (Excel) and team (SharePoint) analytics... and the BI team has less effort since the PP model includes data sources
    and calculations - aside from verifying the sources and calculations, BI can just port the effort into the existing enterprise ETL / warehouse / cubes / reports... shorter dev cycle.
    I'll be speaking on this very topic (done so several times already) this weekend in Chicago at SharePoint Saturday!
    http://www.spschicagosuburbs.com/Pages/Sessions.aspx
    Scott Brickey
    MCTS, MCPD, MCITP
    www.sbrickey.com
    Strategic Data Systems - for all your SharePoint needs

  • SQL Server Reporting Service 2008 R2 - The request failed with HTTP status 401: Unauthorized.

    I got the error "The request failed with HTTP status 401: Unauthorized." when I call the Reporting Service Web Service.
    The code is very simple:
    // Initialise the reporting service Web Service
    this.RSWebService = new ReportingService2010();
    // Pass windos authentication credentials to Web Service
    this.RSWebService.Credentials = System.Net.CredentialCache.DefaultCredentials;
    // List children
    List<CatalogItem> reports = this.RSWebService.ListChildren(folder, false).ToList();
    The SQL Server is installed on a different machine (say server A) from the Web server (say server B). We are using Windows Server 2003.
    The code work fine for all the scenario below:
    i) Run locally (XP) to call the web service on the sql server
    ii) Provide the Network Credentials with the username, password, and domain when calling the web service
    iii) If the web server and sql server is using same server (i.e. not distributed)
    I'm using windows authentication and impersonation. Any idea?

    Hi Raymond,
    If I understand correctly, the issue only happens in the environment that the web server is different with the SQL Server Reporting Services server. This means the web server is a remote server of the Report Server. Windows Integrated authentication is used
    in this case. When running the web page, the 401 error occurs.
    If so, it is actually a double hop issue. The double-hop problem will usually only be an issue to those of you who write some sort of web-based code (a web application or web service) that uses impersonation.
    To fix the issue, we can configure kerberos authentication for the web application and the SQL Server Reporting Services.
    Below is a great article that has delivered many solutions to fix the issue you met:
    http://odetocode.com/articles/216.aspx
    Additionally, you can read the following article to know more about double-hop:
    http://blogs.technet.com/b/askds/archive/2008/06/13/understanding-kerberos-double-hop.aspx
    http://blogs.msdn.com/b/knowledgecast/archive/2007/01/31/the-double-hop-problem.aspx
    If you have any more questions, please feel free to ask.
    Thanks,
    Jin Chen
    Jin Chen - MSFT
    Thanks Jin. I believe this is the cause of the problem as well.
    I tried to register the SPN but unfortunately it still doesn't work. I'm not sure whether I'm using the correct SPN name.
    I have 3 reporting server instance on the SQL box. So the Web Service URL is like
    http://Server:80/VirtualDirectoryDev,
    http://Server:80/VirtualDirectoryTest  and
    http://Server:80/VirtualDirectoryStaging .
    What's the SPN I need to register?
    I tried
    Setspn -a http/Server:80/VirtualDirectoryDev domain\account
    and
    Setspn -a http/aerver:80 domain\account.
    But both of them are not working :(

  • Pass parameter to analysis services report to cube (Not filter)

    Hi I am trying to pass a parameter from a report to a subreport. Both reports are built on Analysis Services cubes.
    I can pass the parameter value to a FILTER parameter but I cannot pass it directly to parameters used in cube. Is it only possible to use the passed parameter as a filter? 
    My subreport is a lot slower when I have to return everything then filter it in Reporting Services, rather than only returning what I need.

    Hi Darkdushy,
    As you said, there are two ways to filter data using parameters. First is add a filter to the dataset or other report items. The second one is use the parameter on the query no matter the database is a multidimensional or relational database. Here is a sample
    query for your reference.
    select
    {[Measures].[Internet Sales Amount]
    } on columns,
    {[Date].[Date].members} on rows
    from(
    select
    STRTOMEMBER("[Date].[Date].&["+@StartDate+"]"):STRTOMEMBER("[Date].[Date].&["+@EndDate+"]")
    ) on columns
    from [Adventure Works]
    Reference:Define Parameters in the MDX Query Designer for Analysis Services (Report Builder and SSRS)
    Regards,
    Charlie Liao
    TechNet Community Support

  • Reporting Services Point - possibly permissions issue

    I'm having a really hard time configuring a working reporting services point in my test SCCM 2012 R2 environment and was hoping someone might be able to help me work out what's gone wrong.
    My servers are WS2008 R2.  SQL Server 2008 R2 is installed on the primary site server and holds the site database.  I installed SSRS onto a separate site server and added it as a reporting services point.  This worked, and I see the list of
    reports in the SCCM admin console.  However, when I try to run a report - either from the console or via web browser - I get this message:
    The default value expression for the report parameter 'usertokensids' contains an error.  There are no logon servers available to service the logon request. (rsRuntimeErrorInExpression)
       at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
       at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
       at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
       at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
       at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
       at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
    SMSAdminUI.log shows this message:
    [25, PID:3096][06/12/2014 11:24:05] :[fqdnofprimaryserver] : The request failed with HTTP status 503: Server Error.
    Now, the reason I think this is a permissions issue is because srsrp.log on the Reporting Point server shows this:
    (!) Error retrieving folders - [Login failed for user 'domain\reportingservercomputername$'.].
    (I've removed the actual name here, obviously.)
    I'm really puzzled about what's going on here, what is trying to authenticate with the SSRS server's machine credentials, and what for.  Looking in SQL Server Management Studio on the primary site server which hosts the SQL database, I can see that
    the account has a login listed and it has its default schema listed as DBO.  On the SSRS server, in Reporting Services Configuration Manager, the Report Server Service Account is set to a dedicated domain user account.  The Current Report Server
    Database Credential is set to my own Windows login using Current User - Integrated Security - I can't seem to get it to accept the dedicated user account.
    Can anyone help me figure out what's gone wrong and how I fix it, please?  I'm by no means a SQL person, and I'm at my wit's end with this!
    Thanks,
    M

    The plot thickens.
    The SSRS server has these:
    "The report server has detected a possible denial of service attack. The report server is dropping requests for service from the IP address 192.168.113.163" (this is the IP address of the primary site system, which hosts the SQL database)
    and then
    "Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database"
    The primary site system, meanwhile, has got thousands of these:
    "Login failed for user 'DOMAIN\SSRSSERVERNAME$'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 192.168.113.164]" (that's the IP of the SSRS server)
    The Windows firewall is off for both systems.  They're on an isolated test network.  I still don't understand where the setting is that tells it to make SQL queries using the SSRS server's machine account, rather than the dedicated service account
    I created.
    Any more ideas?  Thanks for your help so far - I really appreciate it!

  • Reporting Services 2012 for SharePoint and SQL Server Agent "Subscriptions and Alerts"

    After installing Reporting Services for SharePoint (Denali) in my test farm, I'm trying to configure the "SQL Server Agent" access for Reporting Services.  From Central Admin I'm going to the Reporting Service applicaiton configuration screen and selecting
    "Provision Subscriptions and Alerts".  I've tried both options on this screen.  I've manually executed the "download sql script" in SQL Server, as well as entering a user with SQL sys admin rights on the SQL server into the login fields on the screen. 
    The role and permissions have been created for the application pool service account, but Reporting Services is still trying to connect with the annonymous login because I'm getting the following alert each time I open the "Provision Subscriptions and Alerts"
    screen:
    Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
    The "status" on the screen still shows "SQL Server Agent State cannot be determined".  Has anyone else seen this? 
    Thanks!!

    Thanks for your reply!
    1) Looks like the new Reporting Services does not run as a Windows Service so it's not listed in the "Configure Service Accounts" pulldown.  As a result, I don't see how to set the service account.  It's only assigned to an application pool. 
    I installed it into an existing application pool and that application pool "is" in the list and has a domain service account already assigned.
    2) Which users need to be in here in order to configure the "Provision Subscriptions and Alerts" screen?  I already have the farm admin account which is the account I use when running Central Admin.
    3) As mentioned in #1, I've installed Reporting Services into an existing application pool with other service apps.
    4) This link is for Reporting Services 2008 R2 which is very different install process.  But I did follow the SQL Server Reporting Services 2012 RC0 installation instructions and the Reporting Services is functioning correctly with no errors. 
    I'm just not able to configure the sceduling the alerting with interfaces with the SQL Server Agent.
    Thanks!

  • Service Order status  Not Changing From Resloved to Closed status

    The service order Status not automatically moving from Resolved to closed after 30days.
    Observation
    We Revived program Z program ,seems to be fine.
    I am set the program in debugging mode for testing the Service orders by  reduce the time duraion for staus resolved to closed, am getting the getting the Error Test determination procedure is not evaluated . 
    Point of dout
    1) Is there any relation between Test Determination Procedure and Z program.
    2) while am checking for Text Customing for Consistency I found an error Log.
    3) While creating Service Order Test field was Mandatory
                      for that have dout about is there any relation between for this program
    Thanks in Advance
    Regards
    Raju.........

    Solved ...
    BD75  (RBDMOIND ) is T-Code and report name ...
    need to schedule ...

  • Report Services Integrated mode : Error 503 after 100 seconds

    Hello,
    After resolving an issue with some timeouts in shared datasets (updated value not taken into account), i am now facing another timeout (?) issue with our production sharepoint server and reporting services :
    If a report takes more than 100 seconds to display, the following message is displayed on the top of the page :
    "Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server.  The status code returned from the server was: 503"
    The exception is triggered by the scriptmanager, but i don't know why : all the applications pool are running fine, and if i look in SSRS log, it shows that the task completed successfully !
    Our development server is not affected by this strange behavior.
    Is there a secret timeout switch hidden somewhere ??

    Hi Raphael,
    In Reporting Services, if the report server is under high memory pressure, the report server will refuse new requests until the current application domain is unloaded and a new one instantiated. While requests are refused, you will receive HTTP 503 errors.
    To avoid this issue, you can add more memory, move the report server installation to a computer that has more memory, or change the memory configuration settings. For the detail information about it, please see HTTP 503 Service is Unavailable section on the
    link below:
    http://technet.microsoft.com/en-us/library/ms159778(v=sql.105).aspx
    Besides, for the timeout issue, you can refer to the links below to troubleshooting it.
    http://blogs.msdn.com/b/mariae/archive/2009/09/24/troubleshooting-timeout-errors-in-reporting-services.aspx
    http://geekswithblogs.net/ssrs/archive/2009/10/30/steps-to-resolve-ssrs-timeout-issues.aspx
    If you have any questions, please feel free to ask.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Unable to login to Report Service on Windows 2008 R2 server

    I have reporting services installed on a Windows 2008 R2 server, When I make and RDP connection to the server and go to http://servername/Reports everything works fine. When I try to connect from another client to the web service, it asks for username and
    password. it fails 3 times and the shows a blank page.
    When I see the Event Viewer in the server (Windows Logs --> Security, I can see an Audit Failure:
    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          9/4/2014 11:46:25 AM
    Event ID:      4625
    Task Category: Logon
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    Computer:      MI-SWACO-DB.houston.livequest.net
    Description:
    An account failed to log on.
    Subject:
        Security ID:        NULL SID
        Account Name:        -
        Account Domain:        -
        Logon ID:        0x0
    Logon Type:            3
    Account For Which Logon Failed:
        Security ID:        NULL SID
        Account Name:        Administrator
        Account Domain:        HOUSTONLQ
    Failure Information:
        Failure Reason:        An Error occured during Logon.
        Status:            0xc000035b
        Sub Status:        0x0
    Process Information:
        Caller Process ID:    0x0
        Caller Process Name:    -
    Network Information:
        Workstation Name:    MI-SWACO3
        Source Network Address:    -
        Source Port:        -
    Detailed Authentication Information:
        Logon Process:        
        Authentication Package:    NTLM
        Transited Services:    -
        Package Name (NTLM only):    -
        Key Length:        0
    This event is generated when a logon request fails. It is generated on the computer where access was attempted.
    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
    The Process Information fields indicate which account and process on the system requested the logon.
    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
    The authentication information fields provide detailed information about this specific logon request.
        - Transited services indicate which intermediate services have participated in this logon request.
        - Package name indicates which sub-protocol was used among the NTLM protocols.
        - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
        <EventID>4625</EventID>
        <Version>0</Version>
        <Level>0</Level>
        <Task>12544</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8010000000000000</Keywords>
        <TimeCreated SystemTime="2014-09-04T16:46:25.247229500Z" />
        <EventRecordID>8917</EventRecordID>
        <Correlation />
        <Execution ProcessID="504" ThreadID="1344" />
        <Channel>Security</Channel>
        <Computer>MI-SWACO-DB.houston.livequest.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="SubjectUserSid">S-1-0-0</Data>
        <Data Name="SubjectUserName">-</Data>
        <Data Name="SubjectDomainName">-</Data>
        <Data Name="SubjectLogonId">0x0</Data>
        <Data Name="TargetUserSid">S-1-0-0</Data>
        <Data Name="TargetUserName">Administrator</Data>
        <Data Name="TargetDomainName">HOUSTONLQ</Data>
        <Data Name="Status">0xc000035b</Data>
        <Data Name="FailureReason">%%2304</Data>
        <Data Name="SubStatus">0x0</Data>
        <Data Name="LogonType">3</Data>
        <Data Name="LogonProcessName">
        </Data>
        <Data Name="AuthenticationPackageName">NTLM</Data>
        <Data Name="WorkstationName">MI-SWACO3</Data>
        <Data Name="TransmittedServices">-</Data>
        <Data Name="LmPackageName">-</Data>
        <Data Name="KeyLength">0</Data>
        <Data Name="ProcessId">0x0</Data>
        <Data Name="ProcessName">-</Data>
        <Data Name="IpAddress">-</Data>
        <Data Name="IpPort">-</Data>
      </EventData>
    </Event>
    The firewall is OFF in both client and server.
    I saw a similar question and the answer is related to firewall which is not may case.

    Hi Mario,
    According to your description, when you try to access the Report Manager in another client, a login dialog prompt. After typing a valid username and password 3 times, a blank page displays.
    Generally, the issue is always caused by the Report Server is configured to use Kerberos authentication, while the Service Principal Name(SPN) is not configured correctly. To fix this issue, please refer to the following methods:
    Register an SPN for the Report Server service under the domain user account.
    Change the service account to run under a built-in account such as Network Service.
    Remove RSWindowsNegotiate and ensure RSWindowsNTLM is specified in the rsreportserver.config file.
    Besides, the issue can also be caused by the Internet Explorer (IE) didn't pass the user's credential to the Report Server automatically or the IE is not Windows Integrated enabled. For more detail steps about how to address this issue, please refer to the
    following steps:
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/184c4f6c-b292-4f9a-beca-80b70f4392fe/report-manager-prompts-3-or-4-times-for-usernamepassword-before-letting-users-in?forum=sqlreportingservices
    Reference:
    Resolving Kerberos Authentication Errors When Connecting to a Report Server
    Solving the Reporting Services Login issue in the February CTP of SQL Server 2008
    If there are any other questions, please feel free to ask.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Unable to configure reporting services on Web(sharepoint) server where DB(SQL )server is insatlled on another machine.

    Hi Team,
    We have reporting services and sharepoint 2010 installed on one server and DB(Sql server2008 R2 )server installed on another machine. But we are unable to configure reporting(SSRS) on the web(sharepoint)server. Is there any similar configuration
    done on any of your environments and can you please suggest us the workround/resolution.
    Regards,
    Sobha Muyida

    Hi ,
    Iam unable to insert the image/error screenshot here as I have created the account yesterday which throws me email verification error. Though , I have given the error details above. Please suggest accordingly. PFB the details again :
    while building OLAP cube, we are facing below errors with build failure. And DB server is running fine.
    ===== Initiating OLAP database build process =====
    [6/10/2014 12:03 PM] Cube build request message has been added to the Project Server queue
    ===== Verifying and running pre-build server event handler =====
    [6/10/2014 12:04 PM] Verifying and running pre-build server event handler
    ===== Determining database and OLAP database structure =====
    [6/10/2014 12:04 PM] Cube build initialization started
    [6/10/2014 12:04 PM] OLAP database and cube structure was determined successfully
    ===== Building database and cubes =====
    [6/10/2014 12:04 PM] Cube build session started
    ===== Process Completed =====
    [6/10/2014 12:04 PM] Failed to build the OLAP cubes. Error: Failed to connect to the Analysis Services server ServerName. Error: A connection cannot be made. Ensure that the server is running.
    Regards,
    Sobha

  • How to create user-friendly MDX parameters for MS Reporting Services?

    In SQL Server Reporting Service, when I connect to my cube to create a dataset, in Query Designer I create my query with a filter. It creates the following MDX for me:
    SELECT NON EMPTY
    KPIValue("KPI1"), KPIGoal("KPI1"), KPIStatus("KPI1")
    ON COLUMNS, NON EMPTY
    [Create Date].[Month Num].[Month Num].ALLMEMBERS * [Create Date].[Hierarchy].[Month].ALLMEMBERS
    DIMENSION PROPERTIES MEMBER_CAPTION,
    MEMBER_UNIQUE_NAME ON ROWS FROM
    ( SELECT
    ( STRTOSET(@CreateDateYear, CONSTRAINED) )
    ON COLUMNS FROM [ERP])
    WHERE
    ( IIF( STRTOSET(@CreateDateYear, CONSTRAINED).Count = 1,
    STRTOSET(@CreateDateYear, CONSTRAINED),
    [Create Date].[Year].currentmember ) )
    CELL PROPERTIES VALUE, BACK_COLOR,
    FORE_COLOR, FORMATTED_VALUE,
    FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS
    When I add this dataset, Reporting Services creates a parameter named CreateDateYear. When I pass a value like "2014" to this parameter I get nothing and I have to pass a value like
    [Create Date].[Year].&[2014].
    How can I change my report to change this parameter for passing the value like "2014" instead of ugly and not user-friendly string
    [Create Date].[Year].&[2014]?

    Hi ,
      Follow the below steps
      1. Create a dataset with MDX as below which would return the member caption (2005,2006 etc) and member uniquename ([Date].[Calendar Year].&[2005],[Date].[Calendar
    Year].&[2006] etc)
    WITH MEMBER [Measures].[ParameterCaption] AS [Date].[Calendar Year].CURRENTMEMBER.MEMBER_CAPTION
    MEMBER [Measures].[ParameterValue] AS [Date].[Calendar Year].CURRENTMEMBER.UNIQUENAME
    SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue]} ON COLUMNS
    , [Date].[Calendar Year].ALLMEMBERS ON ROWS
    FROM [Adventure Works]
    2. In the parameter's available values choose the above data set and set the options as 
    Value Field = ParameterValue
    ValueCaption = ParameterCaption
    In this way use will see only the years and based on the selection the respective values will be passed to the dataset as parameter.
    Best Regards Sorna

Maybe you are looking for