none
sharepoint foundation and server 2013 RRS feed

  • Question

  • hi all

    i have scom 2012 sp1 on windows server 2008 r2. sql reporting services (mssql 2012 sp1) installed and configured on this server.

    OM, OMDW, scom`s reportserver db - on other server 2008 r2 (mssql 2012 sp1).

    i try to install management pack sharepoint foundation and server 2013 (use http://www.enduria.eu/the-sharepoint-2013-management-pack-and-my-experience-installing-it/).

    in scom console task status - success, but server (sharepoint 2013) in unidentified machines.

    in log on sp2013 server i get error:

    Cannot identify which SharePoint farm this server is associated with. Check the management pack guide for troubleshooting information.

    in log on scom management server i get same error every 10 minutes:

    Failed to deploy reporting component to the SQL Server Reporting Services server. The operation will be retried.
    Exception 'DeploymentException': Failed to deploy reports for management pack with version dependent id 'edf9e0b9-65aa-df29-6729-d16f0005e820'. Failed to deploy linked report 'Microsoft.SharePoint.Server_Performance_Report'. Failed to convert management pack element reference '$MPElement[Name="Microsoft.SharePoint.Foundation.2013.Responsetime"]$' to guid. Check if MP element referenced exists in the MP. An object of class ManagementPackElement with ID 75668869-f88c-31f3-d081-409da1f06f0f was not found.

    One or more workflows were affected by this. 

    Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report
    Instance name: d2781f95-d488-4e35-8226-a9e1d7127149
    Instance ID: {96379E66-14B2-B413-F73F-1F39806AF714}
    Management group: scom-service_group

    what could be the problem?

    thanks



    • Edited by GogolMogol Monday, February 25, 2013 6:01 PM
    Monday, February 25, 2013 6:00 PM

All replies

  • Hi

    If it is Event ID 31567 you might want to try this http://thoughtsonopsmgr.blogspot.ch/2010/09/eventid-31567-failed-to-deploy.html ?

    Cheers,

    Stefan


    Blog: http://blog.scomfaq.ch

    Tuesday, February 26, 2013 6:41 AM
  • thanks for reply, i would try it later.

    if it will give bad result, i'll write here.

    Tuesday, February 26, 2013 2:35 PM
  • We are having the same exact problem

    SCOM 2012 SP1 on Windows Server 2012 and Sharepoint 2013.

    Monday, March 11, 2013 3:04 PM
  • We are having the same exact problem

    SCOM 2012 SP1 on Windows Server 2012 and Sharepoint 2013.

    I have exact same problem with SCOM 2012 SP1 on Server 2012 and Sharepoint 2013. Bug in MP ? Or compatibility problem with SCOM 2012 SP1 and Sharepoint 2013 MP ? 

    Unfortunately link posted by Stefan didn't help :(


    • Edited by iGz Wednesday, April 3, 2013 8:22 AM
    Wednesday, April 3, 2013 7:38 AM
  • Same issue...running SCOM 2012 RTM with UR3 on Windows 2008 R2 and SharePoint 2013.  I got the discovery to work after editing the .config file.  All appeared to be working with the exception of the Configuration Databases and Content Databases which are currently in a Not monitored state (this could be by design?).  I believe this is a bug with the SharePoint 2013 Management Pack.  I tried importing the SharePoint 2010 MP to validate my SCOM environment and Report Server and did not get any errors and the reports imported fine.  Has anyone openened a case with Microsoft or know if this is a known issue?  Thanks!

    Error:

    Data Warehouse failed to deploy reports for a management pack to SQL Reporting Services Server. Failed to deploy reporting component to the SQL Server Reporting Services server. The operation will be retried.
    Exception 'DeploymentException': Failed to deploy reports for management pack with version dependent id 'edf9e0b9-65aa-df29-6729-d16f0005e820'. Failed to deploy linked report 'Microsoft.SharePoint.Server_Performance_Report'. Failed to convert management pack element reference '$MPElement[Name="Microsoft.SharePoint.Foundation.2013.Responsetime"]$' to guid. Check if MP element referenced exists in the MP. An object of class ManagementPackElement with ID 75668869-f88c-31f3-d081-409da1f06f0f was not found.


    One or more workflows were affected by this.

    Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report

    Instance name: 9afddb34-5f35-40fa-8564-1de5d33773d3

    Instance ID: {4BF8AF22-E5E4-1FC6-3951-F731DCA65317}

    Only two SharePoint 2013 reports are showing up in SCOM:

    SharePoint Foundation Performance

    SharePoint Server Performance

    Missing the following reports (according to the product guide):

    Server Alert

    This report renders all alerts raised by specified server(s).

    Service Alert

    This report renders all alerts raised by specified service(s).

    Server Event

    This report renders all events raised on specified server(s).

    Service Event

    This report renders all events raised on specified service(s).

    Top Server Events

    This report renders top 20 events raised on specified server(s).

    Top Service Events

    This report renders top 20 events raised on specified service(s).

    Top Alerts

    This Most Common Alert Report helps to identify high volume alerts, the volume a distinct alert contributes to the total number of alerts and the resolution times. This report helps in tuning the alerts.

    Server Performance

    This report renders performance data for specified server(s).

    Entity State

    This report renders entity state for specified SharePoint object(s) over time.


    • Edited by Magnus_001 Thursday, April 18, 2013 7:51 PM append
    Thursday, April 18, 2013 7:44 PM
  • +1

    OpsMgr 2012 SP1 UR2 running on Windows Server 2012 and using SharePoint 2013 RTM.

    JJ

    Thursday, April 25, 2013 5:31 PM
  • I take it you are having the same issue as well?

    I opened a case with Microsof on this and they said it was a known bug in the SharePoint 2013 MP.  There is no work-around or ETA on a fix at this time.  Just another wonderful example of product/support from Microsoft I guess...

    Friday, April 26, 2013 3:41 PM
  • Correct, we are having the same issue here and I wanted to add that it is also a problem with our specific configuration for everyone's benefit.  We are also using SQL 2012 SP1 for the OpsMgr 2012 SP1 and SharePoint 2013 database servers. Thanks for the feedback on the support case!

    Regards,

    JJ

    Friday, April 26, 2013 3:50 PM
  • Hi, it looks like an issue indeed.

    I see the same behavior in multiple SCOM 2012 SP1 UR#2 environments, running Windows Server 2008 R2 SP1 and SQL Server 2008 R2 SP2. I have contacted Microsoft about this issue.


    Best regards, Marnix Wolf

    (Thoughts on OpsMgr)

    Friday, May 3, 2013 8:55 AM
    Moderator
  • Hi

    I just want to mention, I have seen this error also in the meantime...

    Stefan


    Blog: http://blog.scomfaq.ch

    Friday, May 3, 2013 8:59 AM
  • Ah, not the same issue.. I thought it was this:

    http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/thread/d0b862fc-cc7e-4832-9dd6-caba246203fe/

    I have seen something similar in SCOM 2007 R2 with the infamous OCS R2 MP.  As a matter of fact we are seeing this in our lab today, because I forgot the steps we took to fix it.  From what I remember, we had to add the service account used for the SDK into SCOM Admins group in the console, and maybe some other place.  Once we did this everything worked.

    Apparently when they authored the mp, they didn't follow best practices on how to deploy reports, Jonathan Almquist was our DSE at the time and he did a trace and found out what was going on.  He raised something internally, but of course nothing was done about it.  I suspect if you modify your security so that the report publisher account is a SCOM Admin, this issue may go away, I think that is all we did.


    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.


    Friday, May 3, 2013 4:07 PM
    Moderator
  • SCOM 2012 R2 RU1 on SQL 2012 SP1 and I see this error. This install is new as of Jan 2014 and in terms of management pack I'm running version 15.0.4420.1017 of Microsoft SharePoint Foundation 2013, Server 2013, & Core Library. A search for updates don't show any. Anyone know of an update floating in this blogosphere?

    tia

    Friday, March 7, 2014 1:33 AM
  • Hi

    I think it is fixed in this release 15.0.4557.1000 SP Foundation 2013 http://www.microsoft.com/en-us/download/details.aspx?id=35591 and SP 2013 MP http://www.microsoft.com/en-us/download/details.aspx?id=35590

    Cheers,

    Stefan


    Blog: http://blog.scomfaq.ch

    Friday, March 21, 2014 2:28 PM