Report Services - Duplicate Systems

Hello I am using the following query, listed below;    it seems to be duplicating some of my systems, not all but some...
The only thing I notice is, the duplicate systems have different IP addresses.
Thank you for your help...
SELECT DISTINCT
 v_GS_COMPUTER_SYSTEM.Name0,'Chassis'=CASE 
 WHEN v_GS_SYSTEM_ENCLOSURE.ChassisTypes0 in ('3','4','6','7','15') THEN 'Desktop'
 WHEN v_GS_SYSTEM_ENCLOSURE.ChassisTypes0 in ('8','9','10','21') THEN 'Laptop'
 END,
      v_GS_PC_BIOS.SerialNumber0, v_GS_COMPUTER_SYSTEM.Manufacturer0, v_GS_COMPUTER_SYSTEM.Model0,
                      v_GS_OPERATING_SYSTEM.Caption0, v_GS_OPERATING_SYSTEM.CSDVersion0, v_GS_SYSTEM_CONSOLE_USAGE_MAXGROUP.TopConsoleUser0,
                      v_R_System.User_Name0 AS [Last Logged], v_GS_PC_BIOS.ReleaseDate0, v_GS_NETWORK_ADAPTER_CONFIGUR.IPAddress0,
                      v_GS_NETWORK_ADAPTER_CONFIGUR.DefaultIPGateway0
FROM         v_GS_PC_BIOS INNER JOIN
                      v_GS_COMPUTER_SYSTEM ON v_GS_PC_BIOS.ResourceID = v_GS_COMPUTER_SYSTEM.ResourceID INNER JOIN
                      v_GS_NETWORK_ADAPTER_CONFIGUR ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_NETWORK_ADAPTER_CONFIGUR.ResourceID INNER JOIN
                      v_GS_OPERATING_SYSTEM ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_OPERATING_SYSTEM.ResourceID INNER JOIN
                      v_R_System ON v_GS_COMPUTER_SYSTEM.ResourceID = v_R_System.ResourceID LEFT OUTER JOIN
                      v_GS_SYSTEM_CONSOLE_USAGE_MAXGROUP ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_SYSTEM_CONSOLE_USAGE_MAXGROUP.ResourceID INNER JOIN
                      v_GS_SYSTEM_ENCLOSURE on v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_SYSTEM_ENCLOSURE.ResourceID
WHERE     (v_GS_NETWORK_ADAPTER_CONFIGUR.IPEnabled0 = 1) AND (NOT (v_GS_NETWORK_ADAPTER_CONFIGUR.DefaultIPGateway0 IS NULL)) AND
                      (v_R_System.Operating_System_Name_and0 LIKE '%Workstation%')
ORDER BY v_GS_COMPUTER_SYSTEM.Name0

Hi,
In addition, the blog below could be helpful.
SCCM Guru Webcast Q&A #2-Multiple Rows in Reports
(Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change
without notice. Microsoft does not guarantee the accuracy of this third-party contact information.)
Best Regards,
Joyce Li
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.

Similar Messages

  • SharePoint Reporting Services Integration - System Settings Page Issue

    Hi All,
    A client of mine has setup Reporting Services (SQL Server 2012 SP1) integration on a SharePoint 2010 environment and this has been working fine for a while now. This includes viewing SSRS reports and also creating PowerView reports from the SharePoint interface.
    The only issue that we have is when we browse to the SQL Reporting Services service application via SharePoint Central Administration and select 'System Settings' we receive an error and can't configure any of the settings located on this page.
    Looking at the ULS logs I can see the following error is raised:
    System.NullReferenceException: Object reference not set to an instance of an object.    at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.InitStrings()     at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.OnInit(EventArgs
    e)     at System.Web.UI.Control.InitRecursive(Control namingContainer)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    43aaadcd-fc67-420e-a30f-2e174f151084
    I removed the existing service application and uninstalled the SharePoint Services (using Install-SPRSService). I then reconfigured the RS services and created a new service application but the error is still raised. All other pages under the service application
    can be loaded. We also tried setting the reporting services diagnostic logs to verbose but couldn't see any further information.
    Has anybody seen this before? I'm thinking that perhaps some of the configuration settings for this page actually carry a null value when it should be configured with something. Does anybody know where these settings are saved?
    Cheers,
    Tom

    Just thought I'd provide an update, we ended up resolving this, problem was related to an incorrect ID one one of the fields in ReportingServicesSystemSettings.aspx.
    Updating this to the correct ID resolved the issue. Weird thing was that the file was incorrect on more than one server, only had to obviously update it on the CA server though. After this the System Settings page opened without any problems.

  • Service Manager data warehouse SQL Reporting Services server is currently unavailable

    I keep getting this error when I launch my SCSM Console. Take a look at the event log > operation manager and saw this error message below. 
    Tried to google around but unable to find any solution to it. Anybody can enlighten me on this issue that I am encountering? Thanks
    Cannot connect to SQL Reporting Services Server. Message= An unexpected error occured while connecting to SQL Reporting Services server: System.Net.WebException: The request failed with HTTP status 404: Not Found.
    at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
    at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
    at Microsoft.EnterpriseManagement.Reporting.ReportingService.ReportingService2005.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, SearchCondition[] Conditions)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItems(String searchPath, IList`1 criteria, Boolean And)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItems(String itemPath)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItem(String itemPath, ItemTypeEnum[] desiredTypes)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.GetFolder(String path)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReportingGroup.Initialize()
    at Microsoft.EnterpriseManagement.Reporting.ServiceManagerReportingGroup..ctor(DataWarehouseManagementGroup managementGroup, String reportingServerURL, String reportsFolderPath, NetworkCredential credentials)
    at Microsoft.EnterpriseManagement.Reporting.ServiceManagerReportingGroup..ctor(DataWarehouseManagementGroup managementGroup, String reportingServerURL, String reportsFolderPath)
    at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ManagementGroupServerSession.TryConnectToReportingManagementGroup() Remediation = Please contact your Administrator.
    Jeron

    Hi,
    This may occur when there is a mismatch between the Report Server URL entered on the SSRS Server Location window for the Report Deployment Wizard and the SSRS Web Service Virtual Directory for the Reporting
    Services Configuration Manager.
    Use the following steps to resolve the issue:
    Launch the Reporting Services Configuration Manager on the server hosting SSRS
    Select Web Service URL
    Copy the value entered in the Virtual Directory textbox
    Paste it after the last forward slash in the Report Server URL textbox in the Report Deployment Wizard
    Continue on with the deployment
    In addition, we may need to check you default web server IP is 'all unassigned', and ping the machine and see what default ip it has assigned.
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Service manager console can't connect to Service manager data warehouse SQL reporting services

    When I start Service manager console, it gives this kind of error:
    The Service Manager data warehouse SQL Reporting Services server is currently unavailable. You will be unable to execute reports until this server is available. Please contact your system administrator. After the server becomes available please close your
    console and re-open to view reports.
    Also in EventViewer says:
    cannot connect to SQL Reporting Services Server. Message= An unexpected error occured while connecting to SQL Reporting Services server: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
    at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
    at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
    at Microsoft.EnterpriseManagement.Reporting.ReportingService.ReportingService2005.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, SearchCondition[] Conditions)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItems(String searchPath, IList`1 criteria, Boolean And)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItems(String itemPath)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItem(String itemPath, ItemTypeEnum[] desiredTypes)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.GetFolder(String path)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReportingGroup.Initialize()
    at Microsoft.EnterpriseManagement.Reporting.ServiceManagerReportingGroup..ctor(DataWarehouseManagementGroup managementGroup, String reportingServerURL, String reportsFolderPath, NetworkCredential credentials)
    at Microsoft.EnterpriseManagement.Reporting.ServiceManagerReportingGroup..ctor(DataWarehouseManagementGroup managementGroup, String reportingServerURL, String reportsFolderPath)
    at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ManagementGroupServerSession.TryConnectToReportingManagementGroup() Remediation = Please contact your Administrator.
    We have a four server set-up where SCSM, SCDW, and sqls for both are on different servers. Also I have red that this could be a SPN problem, but this has  been worked on last week without the SPNs.

    On the computer you get the "SQL Reporting Services server is currently unavailable" message please open the Internet Explorer and try to connect to the URL <a href="http:///reports">http://<NameOfReportingServer>/reports
    This should open the reporting website in IE. If this isn't working you should check the proxy settings in IE. If the URL doesn't work in IE it won't work in the SCSM console as well (and vice versa).
    Andreas Baumgarten | H&D International Group
    Actually I can't access to the reporting website. It asks me credentials 3 times and then return a blank page. Also error message comes to the EventViewer System log with id 4 and source Security-Kerberos.
    The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server "accountname".
    The target name used was HTTP/"reporting services fqn". This indicates that the target server failed to decrypt the ticket provided by the client.
    This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using.
    Ensure that the target SPN is only registered on the account used by the server.
    This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service.
    Ensure that the service on the server and the KDC are both configured to use the same password.
    If the server name is not fully qualified, and the target domain (domain.com) is different from the client domain (domain.com), check if there are identically named server accounts in these two domains,
    or use the fully-qualified name to identify the server.
    I can access the website directly from the server which hosts Reporting Services.
    Also I query "setspn -Q HTTP/"reporting services fqn" whit result NO SUCH SPN FOUND.

  • Urgent: System.OutOfMemoryException in SQL Reporting Services 2005 Web Service

    Hi All,
    On a production server box with 8GB of RAM, we are running a windows service which retrieves image format bytes of a particular report which results in pages ranging from 10 to 300 using Reporting Services 2005 Web Service.
    Problem is when image bytes are being retrieved by using Render method for a report with more than around 30-40 pages,
    Report Web Service throws an exception of type System.OutOfMemoryException. This does not happen with reports with smaller pages. Please note that we are retrieving high DPI image and we have no option but to do so.
    Since the production server has 8 GB of RAM and we have even enabled the 3GB switch in boot.ini of Windows Server 2003, This problem still exists.
    I have already read the contents of the article http://support.microsoft.com/kb/909678 but as i mentioned even the large physical memory does not seem to help and shortening the report is not an option.
    Also note that large number of records is also not a problem as our application works fine when we generate excel files instead of images.
    Follwing is the detailed exception that we receive.
    System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
       at System.String.GetStringForStringBuilder(String value, Int32 startIndex, Int32 length, Int32 capacity)
       at System.Text.StringBuilder.set_Capacity(Int32 value)
       at System.Xml.BufferBuilder.ToString()
       at System.Xml.XmlTextReaderImpl.ParseText()
       at System.Xml.XmlTextReaderImpl.ParseElementContent()
       at System.Xml.XmlTextReaderImpl.Read()
       at System.Xml.XmlTextReader.Read()
       at System.Xml.XmlTextReaderImpl.InitReadElementContentAsBinary()
       at System.Xml.XmlTextReaderImpl.ReadElementContentAsBase64(Byte[] buffer, Int32 index, Int32 count)
       at System.Xml.XmlTextReader.ReadElementContentAsBase64(Byte[] buffer, Int32 index, Int32 count)
       at System.Xml.Serialization.XmlSerializationReader.ReadByteArray(Boolean isBase64)
       at System.Xml.Serialization.XmlSerializationReader.ToByteArrayBase64(Boolean isNull)
       at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderReportExecutionService.Read34_RenderResponse()
       at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer25.Deserialize(XmlSerializationReader reader)
       at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
       at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at ReportExecution2005.ReportExecutionService.Render(String Format, String DeviceInfo, String& Extension, String& MimeType, String& Encoding, Warning[]& Warnings, String[]& StreamIds)

    Hi Hameer,
    This error might be caused by the memory limit.  There are two settings that will affect the memory configuration.
    When you render a report through the Reporting Services Web service, the Reporting Services Web service obtains the "MemoryLimit" setting from the Machine.config file. 
    A scheduled report is rendered by the Report Server Windows service. The Report Server Windows service obtains the "MemoryLimit" setting from the RSReportServer.config file.
    These values represent a percentage of physical memory. You can adjust them to change the memory limit.
    If there are any more questions, please let me know.
    Thanks.

  • [Forum FAQ] Reporting Service Point cannot be installed on a Site System Server running SQL Server 2012 SP1

    Symptom: When you install Reporting Service Point role on a Site System Server running SQL Server
    2012 SP1, you may encounter an issue that the Reporting Service Point role cannot be installed. The error log “srsrpMSI.log” and “srsrpsetup.log” may throw the error as shown in Figure 1 and Figure 2.
    03:32:03:764]:
    MainEngineThread is returning 1618
    Figure 1: Error -1
    <03/03/14 03:32:03>
    srsrp.msi exited with return code: 1618
    Figure 2: Error -2
    Reason: All the two logs indicate an error return code 1618. From the KB below you may know what
    the return code means.
    ERROR_INSTALL_ALREADY RUNNING 
    1618
    Another installation is already in progress. Complete that installation before proceeding with this install.
    KB link:
    http://support.microsoft.com/kb/290158 “it is related to an Office Suite KB, anyway, the MSI return code is the same meaning”
    You can look into Resource Manager and Event Viewer to find the other currently running MSI installation. You may get a warning in Event Log that means the MSI wants to install a SQL Server
    related Component (Figure 3). The Resource Manager confirms this (Figure 4).
    Event Log:
    Event ID: 1004
    Source: Msinstaller
    Level: Warning
    Detection of product '{A7037EB2-F953-4B12-B843-195F4D988DA1}',
    feature 'SQL_Tools_ANS', component '{0CECE655-2A0F-4593-AF4B-EFC31D622982}' failed.  The resource '' does not exist.
    Figure 3: Event Log
    Figure 4: Resource Manager
    Resolution: the error is exactly what the following KB describes.
    KB Link:
    http://support.microsoft.com/kb/2793634
    After we resolve the SQL Server 2012 issue, the Reporting Service Role is installed successfully.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    This implies that ODP.NET does NOT need to be installed on a client. However, I cannot find OraOPs9.dll on a machine with Client Release 9.2 installed. Should OraOps?.dll automatically come with a Client installation of 9.2 or higher?
    ODP.NET needs to be installed on the client. OraOps9.dll is part of ODP.NET, not the Oracle Client.
    Also, if an application is built with the 10g ODP.NET, can it be run from a machine with OraOps9.dll?
    If an application is built with 10g ODP.NET, it can be run with 9.2 ODP.NET as long as you do not use any 10g APIs. The new features in 10g ODP.NET are included in the doc and the ODP.NET FAQ for your reference.

  • Reporting Services not automatically starting. System event log 7009, Application event: 18456

    For the past month (since Oct 11,2012)  reporting services (SSRS 2008R2) is not starting after the server is rebooted. The service is set to automatically start and starts manually without a problem.  The system event log contains the following error:
    Event ID 7009: A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect.
    SQL logs :
    The SQL logs has many "Event 18456 Login Failed, State 38" errors when the database engine starts. I assume clients conections are failing because the databases  aren't online yet. None of these 18456 errors coorespond to the account reporting services
    runs under.
    The SQL logs indication Event 7009 occures before the "ReportingServer" database is online so im assuming there is a dependancy but I don't know how to avoid this.
    This problem is occuring on a number of our servers running SSRS (if not all)
    Any ideas?
    Paul

    Hi A141695,
    For Event ID 7009, you can try to do the steps below to resolve it.
        1. Click Start, click Run, type regedit, and then click OK.
        2. Locate and then click the following registry subkey:
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
        3. Right-click Control, point to New, and then click DWORD Value.
        4. In the New Value #1 box, type ServicesPipeTimeout, and then press ENTER.
        5. Right-click ServicesPipeTimeout, and then click Modify.
        6. Click Decimal, type the number of milliseconds that you want to wait until the service times out, and then click OK.
    For example, to wait 60 seconds before the service times out, type 60000.
    Quit Registry Editor, and then restart the computer. For more information about it, please see:
    http://www.sqlservercentral.com/Forums/Topic850540-1550-1.aspx#bm851211
    http://myitforum.com/myitforumwp/2012/08/22/configmgr-2012-sms_srs_reporting_point-component-failure/
    If you have any questions, please feel free to ask.
    Regards,
    Charlie Liao
    TechNet Subscriber Support
    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback
    here.

  • Central Administration Manage Reporting Services Application - SSRS Service Application PSQA System Settings

    When I try to get into System Settings I get the following error:
    Does anyone know how to fix this?
    lcerni

    Hi lcerni,
    According to your description, my understanding is that you could not access the system settings inside SQL Reporting service application.
    There is a blog, the issue 3 is similar with your issue, please take a look at:
    http://thebaretta.blogspot.com/2013/04/sharepoint-2010-sql-server-2012.html
    In addition, please check the log file to find more information about this issue based on the correlation ID. The path of the log file is: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS.
    Best Regards,
    Wendy
    Wendy Li
    TechNet Community Support

  • System Center Operations Manager 2012 R2 and SQL Server 2014 Reporting Services

    I was able to connect SCOM12 to SQL14, however when I attempted to install Reporting Service in SCOM12 the pull down box was blank.
    I installed reporting services on the same instance of SystemCenter, when that didn't work I tried creating a new instance that only included SSRS; remote registry is also running. The drop-down box within the SCOM installer is blank.
    Is this an issue with reporting between SC12 and SQL14, yes I understand documentation says only sql server 2012 is supported, however I've seen many threads with SCOM12 and SQL12 that are having the same issues.
    Is there something I may be missing, or do I have to install SQL12 and go through the process again?

    Hi,
    As far as I know, the SCOM reporting server role should be installed on the same server where SQL reporting service installed.
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Installing Report service role

    Hi All
    Recently i installed SCCM 2012 R2 - the DB located on remote server
    the SQL server also using now as a report server for SCOM 2012
    when i tried to install repoert server role on sccm site server ( primary server ) i cannot find reporting server instance at the drop menu
    if i install the role on the sql server it's installed but when going to component status i fount it with critical stauts
    advise please

    Severity,Type,Site code,Date / Time,System,Component,Message ID,Description
    Error,Milestone,PR1,4/30/2014 4:16:42 PM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 3:16:42 PM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 2:16:41 PM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 1:16:40 PM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 12:15:43 PM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 11:15:41 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 10:15:32 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 9:15:32 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 8:14:35 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 7:13:46 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 6:12:30 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 5:11:32 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Information,Milestone,PR1,4/30/2014 4:11:10 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,4609,Component Status Summarizer set the status of component "SMS_SRS_REPORTING_POINT", running on computer "sqlserver.domain.com", to Critical.   
    Possible cause: The component is experiencing a problem.  Solution: Diagnose and fix the problem by:  1. Examining the status messages that the component reports.  2. Correcting the problem.  3. Instructing Component Status Summarizer to
    reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the Configuration Manager Console. When the counts are reset,
    Component Status Summarizer will change the status of the component to OK. This might take some time if site "PR1" is a child site.  4. Delete any unwanted status messages from the site database, if necessary.  5. Monitor the component
    occasionally to verify that the problem does not reoccur.    Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component.  Solution: Increase the Component
    Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the Configuration Manager Console.    Possible cause: The component is flooding the status system by rapidly reporting the
    same message repeatedly.  Solution: Diagnose and control the flood of status messages by:  1. Verifying that the component is actually flooding the status system. View the status messages reported by the component and verify that the same message
    is continually reported every several minutes or seconds.  2. Noting the Message ID of the flooded status message.  3. Creating a Status Filter Rule for site "PR1" that instructs Status Manager to discard the flooded status message when
    component "SMS_SRS_REPORTING_POINT" on computer "sqlserver.domain.com" reports it.   4. Verifying that your sites' databases were not filled up by the flooded status message.  Delete any duplicate
    Information,Milestone,PR1,4/30/2014 4:11:10 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,4605,Component Status Summarizer detected that component "SMS_SRS_REPORTING_POINT", running on computer "sqlserver.domain.com", has reported 5 or
    more Error status messages during the Component Status Threshold Period.    Possible cause: The count equals or exceeds the Component Status Critical Threshold (5 status messages) for Error status messages for the component.  Solution:
    Component Status Summarizer will set the component's status to Critical in the Component Status summary in the Configuration Manager Console.
    Error,Milestone,PR1,4/30/2014 4:10:35 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 3:10:09 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 2:10:09 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Error,Milestone,PR1,4/30/2014 1:10:08 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,7403,The report server service is not running on Reporting Service Point server "sqlserver.domain.com"; start the service to enable reporting.
    Information,Milestone,PR1,4/30/2014 12:10:42 AM,sqlserver.domain.com,SMS_SRS_REPORTING_POINT,4610,Component Status Summarizer set the status of component "SMS_SRS_REPORTING_POINT" running on computer "sqlserver.domain.com" to Warning. 

  • "Reporting services" service does not start automatically

    I have installed reporting services from SQL Express SP1 package. OS is Windows 2000 SP4. Just after installation "Reporting services" service has StartMode=Automatic and LogOnAS=LocalSystem as shown in SQL Server Configuration Manager. When system is rebooted reporting services state is Stopped and there is 2 errors in System log:
    1. Timeout (30000 milliseconds) waiting for the SQL Server Reporting Services (REPS) service to connect.
    2. The SQL Server Reporting Services (REPS) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
    If i select "start" from service's context menu then it starting normally and it's state becomes Running.
    What can i do to make reporting services starting automatically on system load?

    i  have the same problem here in one of our servers ,, it was working and suddenly it stopped i don't know why 
    when i reviewed the Event Viewer :
    Event Type: Error
    Event Source: SQL Server Report Service
    Event Category: None
    Event ID: 0
    Date: 8/22/2010
    Time: 12:05:26 PM
    User: N/A
    Computer: SERVICE-CENTER
    Description:
    Service cannot be started. Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information. ---> System.UnauthorizedAccessException:
    Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config' is denied.
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
       at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
       at Microsoft.ReportingServices.Diagnostics.Globals.SafeOpenXmlDocumentFile(XmlDocument doc, String pathToXmlFile)
       at Microsoft.ReportingServices.Diagnostics.RSConfiguration.LoadDocument()
       at Microsoft.ReportingServices.Diagnostics.R...
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Any body can help with this ,, because i didn't find anything helpful till now !!!
    dear all 
    i installed SQL Server 2005 SP2 and it solved my problem 
    wish you all luck 

  • Reporting Services Point, remote SQL issue

    I'm trying to install Reporting Services Point on a remote SQL 2008 R2 SP2 server. I select the SQL server under Servers and Site System Roles and it lists the site database server name, database name (should this name be the same as the DB found in Reporting
    Services Configuration Manager?), folder name and reporting services server instance. I enter a new account that is a sysadmin on the SQL click verify and get:
    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
    (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).
    Ping works both ways, remote connection on this SQL instance are enabled, static ports configured, a rule to allowany is set in the firewall. Should I perhaps be entering the port (this instance uses a non-standard one) in the Add Site System Roles
    Wizard?
    If I open up Reporting Services Configuration Manager, the service is started, mode is native, a domain user account is used for the service account, web service URL opens, I even created a new DB. Report Manager URL opens.
    SCCM itself uses the same remote SQL instance, so it appears connectivity works fine.
    Any assistance is appreciated.

     Thank you very much - CypherMike. 
    You helped me so much!!!
    I installed the DB on another Instance so i had to change the port # and just here i found this info that i need to use comma to define the port.
    Tnx

  • 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

  • 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 - All Datasets Broken

    Hello there.
    We’re having some problems with Reporting Services on a prod site and I was hoping someone might be able to offer a suggestion.
    Here are the facts :
    We have a SP Server 2010 (not foundation) farm which uses Reporting Services. There is 1 web / application server and 1 SQL server. Reporting Services 2008 R2 is installed on the SQL box.
    Sometime in the last 2 weeks the reports all stopped working (last known report run 2 weeks ago). This was picked up yesterday. I'm not aware of anything being manually changed in the farm to cause this.
    The reports report directly on SP lists using datasets with SharePoint data connections. There is one dataset per list.
    The SQL / Reporting Services box has previously had SP installed on it (Ouch! Inherited system – not sure why SP was installed on SQL box).
    A few weeks ago we stopped all SP services on the SQL box but did not uninstall SP from it. This did not affect reporting at the time.
    When a report fails, we see this message in the UI :
    Looking in the reporting services log messages are like the following, one per dataset :
    Query execution failed for dataset 'DataSet1'. ---> System.ArgumentException: Feature '22d91f57-00d1-4e0b-9c04-863a82deaa07' for list template '10001' is not installed in this farm. 
    The operation could not be completed.
    This happens for all datasets for all reports. All datasets are complaining that the feature for the list the data set uses is missing. These are features with list definitions / instances for the lists used in the reports.
    The initial thought was that someone had renamed a field or similar, but this would only impact that one dataset. What we are seeing is that
    all datasets simultaneously broke.
    The features Reporting Services are complaining about are indeed activated in SP in the relevant webs.
    On the SQL box the folders for the features Reporting Services are complaining about are not present in the 14 hive at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES, but then as far as I know they never were. On
    our dev environment we deleted these feature folders but this didn't reproduce the same error.
    We modified an unrelated SP list view yesterday via the SP UI. It’s unlikely but I wonder if there is some kind of list definition XML / voodoo behind the scenes that was interrupted by this.
    If you open the broken report in Report Builder directly from SP (via the list context menu), you can run the datasets OK, and do a test connection for the data source - but if you run the report itself you get the usual error. If I use Report Builder on
    my local machine to try to save to the web where the reports are stored, I get one of the “feature…is not installed in this farm” errors. I can’t even browse to that web in Report Builder without getting the error.
    Things I've tried so far (my infrastructure experience amounts to restart things until they work):
    App pool recycle web server.
    IISReset web server.
    Restart reporting service on SQL box.
    Delete the view I thought might have been somehow related.
    In summary I have no idea what the root cause is here or what has changed recently. I’m a 
    programmer and someone else who is no longer available set up this environment so I’m a bit stuck!
    Thanks for reading.
    Lee

    We've resolved this.
    It turns out the features it was complaining about really were missing on the Reporting Services box and needed to be present. I wrongly concluded this wasn't the problem initially when we deleted these features on a dev box, restarted a few things and reports
    didn't break. I guess something was still being cached somewhere.
    Best  guess as to why the features went away is that when we disabled all of the SP services on the reporting services box via Central Admin, one of these (probably SharePoint Foundation Web Application), all custom features / solutions were removed
    from the box.
    Moral of the story I think is make sure your reporting services box is a valid part of the SP farm and has all required features present.
    Cheers
    Lee

Maybe you are looking for

  • What is the prioritization of data when syncing to different computers?

    All of the bookmarks, passwords, etc. that I want to keep are on my '''laptop'''. If I've set up my Firefox Sync account on my ''desktop'', and I add my '''laptop '''to that account, will the "syncable" data from my ''desktop ''overwrite all the "syn

  • I opened my Macbook pro and now it won't start

    So I started to have issues with my MacBook Pro not recognizing the hard drive. I opened it up and started to see how dirty the inside was so I took the logic board and battery and cleaned them up. When I put eveything back together, now the machine

  • Please help with update for ios 8.1.3

    Some one PLEASE HELP ME!!!  I just updated my I phone 4s to ios 8.1.3 it was taking a long time then they finally updated and had the Hello screen after that I saw my photos then they would just delete it right in front of me I also lost some of my c

  • What most affects Flash performance?

    What components, hardware and software, affect Flash performance the most? I believe that video cards have no bearing, but have recently come into a debate over the RAM vs processor. Also, on Windows XP, any tricks to bring up performance speed? Than

  • Site automatically scale to fit the browser window

    hello all! i'm working on a site that i'd like to automatically scale to fit the browser window, without any scrolling and while preserving its aspect ratio. my client is very particular about the design & does not want the width & height of the imag