locked
Error when using get-scsmSubscription - "Could not resolve NotificationSubscription with ID..." RRS feed

  • Question

  • When I run the cmdlet Get-SCSMSubscription, I get 6 errors and then it displays the remains notifications.

    My notifications appear to all be working correctly.  What I was looking to grab was the notification and the recipientusers...  Should be simple, but then I get these errors.... not sure why.

    PS C:\PS1> Get-SCSMSubscription -ComputerName scsm01 | select DisplayName
    Get-SCSMSubscription : Could not resolve NotificationSubscription with ID
    10d5bef8-70d1-36d1-58e4-27afa75584c0 to a Subscription instance. The subscription is invalid.
    Please ensure that the references in the subscription are still valid.
    At line:1 char:1
    + Get-SCSMSubscription -ComputerName scsm01 | select DisplayName
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (Microsoft.Enter...ionSubscription:NotificationSubscrip
       tion) [Get-SCSMSubscription], ArgumentException
        + FullyQualifiedErrorId : InvalidSubscription,Microsoft.EnterpriseManagement.ServiceManager.Cm
       dlets.GetSCSMSubscriptionCommand
    
    Get-SCSMSubscription : Could not resolve NotificationSubscription with ID
    be97771c-d4fd-f66b-ceb6-7499a2ac6a78 to a Subscription instance. The subscription is invalid.
    Please ensure that the references in the subscription are still valid.
    At line:1 char:1
    + Get-SCSMSubscription -ComputerName scsm01 | select DisplayName
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (Microsoft.Enter...ionSubscription:NotificationSubscrip
       tion) [Get-SCSMSubscription], ArgumentException
        + FullyQualifiedErrorId : InvalidSubscription,Microsoft.EnterpriseManagement.ServiceManager.Cm
       dlets.GetSCSMSubscriptionCommand
    
    Get-SCSMSubscription : Could not resolve NotificationSubscription with ID
    86d8f397-b673-3232-7db7-8d2c4a7e03ad to a Subscription instance. The subscription is invalid.
    Please ensure that the references in the subscription are still valid.
    At line:1 char:1
    + Get-SCSMSubscription -ComputerName scsm01 | select DisplayName
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (Microsoft.Enter...ionSubscription:NotificationSubscrip
       tion) [Get-SCSMSubscription], ArgumentException
        + FullyQualifiedErrorId : InvalidSubscription,Microsoft.EnterpriseManagement.ServiceManager.Cm
       dlets.GetSCSMSubscriptionCommand
    
    Get-SCSMSubscription : Could not resolve NotificationSubscription with ID
    5ffe64c3-56a1-444c-948b-e0ef56f7b496 to a Subscription instance. The subscription is invalid.
    Please ensure that the references in the subscription are still valid.
    At line:1 char:1
    + Get-SCSMSubscription -ComputerName scsm01 | select DisplayName
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (Microsoft.Enter...ionSubscription:NotificationSubscrip
       tion) [Get-SCSMSubscription], ArgumentException
        + FullyQualifiedErrorId : InvalidSubscription,Microsoft.EnterpriseManagement.ServiceManager.Cm
       dlets.GetSCSMSubscriptionCommand
    
    Get-SCSMSubscription : Could not resolve NotificationSubscription with ID
    38cf6cdb-96de-69e4-a080-f6cea525a026 to a Subscription instance. The subscription is invalid.
    Please ensure that the references in the subscription are still valid.
    At line:1 char:1
    + Get-SCSMSubscription -ComputerName scsm01 | select DisplayName
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (Microsoft.Enter...ionSubscription:NotificationSubscrip
       tion) [Get-SCSMSubscription], ArgumentException
        + FullyQualifiedErrorId : InvalidSubscription,Microsoft.EnterpriseManagement.ServiceManager.Cm
       dlets.GetSCSMSubscriptionCommand
    
    Get-SCSMSubscription : Could not resolve NotificationSubscription with ID
    607e6f9c-59b8-d0e9-d5a9-f894efe04b20 to a Subscription instance. The subscription is invalid.
    Please ensure that the references in the subscription are still valid.
    At line:1 char:1
    + Get-SCSMSubscription -ComputerName scsm01 | select DisplayName
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (Microsoft.Enter...ionSubscription:NotificationSubscrip
       tion) [Get-SCSMSubscription], ArgumentException
        + FullyQualifiedErrorId : InvalidSubscription,Microsoft.EnterpriseManagement.ServiceManager.Cm
       dlets.GetSCSMSubscriptionCommand
    
    
    DisplayName
    -----------
    CMN02 - onCreate - Expedited/Emergency Urgency Notification
    CMN32 - onUpdate - PIR Required
    CMN25.1 - onCreate - New Server Deployment


    Joshua Fuente



    Friday, June 7, 2013 6:47 PM

All replies

  • Hello All,

    Just wanted to give this post a bump as we're experiencing the same issue.

    Ran the following Powershell

    PS C:\Program Files\Microsoft System Center 2012\Service Manager> Get-SCSMSubscr
    iption | where {$_.Name -eq "NotificationSubscription_54a1b2de_61f9_46d4_88f0_40
    1b7beea7a3"}

    Result:

    Get-SCSMSubscription : Could not resolve NotificationSubscription with ID 04717
    bf7-78c4-9430-b724-03b65933a131 to a Subscription instance. The subscription is
     invalid. Please ensure that the references in the subscription are still valid.

    Other IDs: (Same Error)

    8befaf57-c831-a5bb-4d47-20aa0bfb444d

    5d9e0969-636e-79e6-a60c-3480b096462d

    cba36df2-37ac-0310-1114-3e9c0a042fc8

    fac3431b-bee7-86a4-8584-6d045fde215f

    f0fe6b02-971f-b6a4-3e0b-74ae3bc402ea

    77a8616f-5064-f1ce-bffb-b012a8b22c9b

    97d3241a-434e-105b-f3ef-b5dccdd0e3b5

    41eecd5e-765d-935f-8a80-cd32e47a0c92

    12c7e68-1faa-9a78-1221-d8b40f9f32c0

    064df0a6-bfeb-ebe1-6288-e0b4d5bec202

    d3b0aa29-9089-ffba-854e-e4f0fa0e8b83

    6e5ce345-45cd-0402-36d3-eacd52f27c5b

    aa021c2b-8372-c132-aecb-f305721ce532

    b7616dd9-b904-1acf-68fb-f475251bec86

    b858859c-f060-ff90-ff45-fa8b6b14ea1e

    Best regards,

    Ken Perry

    Monday, October 28, 2013 9:16 PM
  • Bump... 


    Joshua Fuente

    Friday, January 31, 2014 7:19 PM
  • Hi,

    It clearly states that 'Please ensure that the references in the subscription are still valid'. You have to make sure that all management packs mentioned in the reference section of the subscriptions' MPs are presented in Service Manager's Management Packs.


    Cheers,
    Marat
    Site: www.scutils.com  Twitter:   LinkedIn:   Facebook:   

    • Proposed as answer by Marat Kuanyshev Wednesday, February 5, 2014 2:31 AM
    Sunday, February 2, 2014 12:37 AM
  • I am having the same issue, but only with subscriptions created in the console. Subscriptions created using New-SCSMSubscription there is no error when retrieved with Get-SCSMSubscription. But I get an "Object reference not set to an instance of an object" when trying to open the PS-generated subscriptions in the console.

    There is no issue on my prod environment (not tested creating scripted subscriptions though).

    http://codebeaver.blogspot.dk/

    Monday, December 1, 2014 12:40 PM
  • I was just able to open a subscription where "When to notify" is set to created. still an issue with Get-scsmsubscription (both on created and updated).

    http://codebeaver.blogspot.dk/

    Monday, December 1, 2014 12:55 PM