While working with a few different customers over the past weeks I have seen this error come up. While accessing a subscription you get the following popup error.

So you ask yourself what does that mean? That popup error itself offers little in the way of a clear answer. It does however point you in the right direction. Since we are dealing with the Notifications Library we can figure that the error is coming from something within a subscription or subscriber. After doing some digging I found that these are often caused by the deletion of a rule or monitor that has been subscribed to within one of your subscriptions. If you export the Notifications Internal Library MP and open the XML file with an editor, you can see that the subscriptions MP is just XML like all other MP’s. In the case of the error we see above there is a GUID that is referenced within the XML that no longer exists. To resolve this you will need to find the GDID that is causing the problem and remove it.

To locate and remove the faulting GUID follow the steps below.

1. Export the Notifications Internal Library, then make a copy of it for backup purposes.

2. Open the XML File in whatever editor you would like to use. Now do a find for the name of the subscription, in my example I am using “Server Down” . You are looking for an entry like you see below. You will want to copy the “Subscriptiondb8a65fa_53ea_46e1_9a65_ebd45ca1ca69” to your clipboard.

<DisplayString ElementID="Subscriptiondb8a65fa_53ea_46e1_9a65_ebd45ca1ca69">

          <Name>Server Down</Name>

3. Now do a find in the XML file for that Subscription GUID you just copied. This will take you to a chunk of text like you see below.

<Rule ID="Subscriptiondb8a65fa_53ea_46e1_9a65_ebd45ca1ca69" Enabled="true" Target="Notification!Microsoft.SystemCenter.AlertNotificationSubscriptionServer" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">

        <Category>Notification</Category>

        <DataSources>

          <DataSource ID="DS1" RunAs="SystemCenter!Microsoft.SystemCenter.DatabaseWriteActionAccount" TypeID="SystemCenter!Microsoft.SystemCenter.SubscribedAlertProvider">

            <AlertChangedSubscription Property="Any">

              <Criteria>

                <Expression>

                  <And xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="https://www.w3.org/2001/XMLSchema">

                    <Expression>

                      <Or>

                        <Expression>

                          <SimpleExpression>

                            <ValueExpression>

                              <Property>ProblemId</Property>

                            </ValueExpression>

                            <Operator>Equal</Operator>

                            <ValueExpression>

                              <Value>b59f78ce-c42a-8995-f099-e705dbb34fd4</Value>

                            </ValueExpression>

                          </SimpleExpression>

                        </Expression>

                        <Expression>

                          <SimpleExpression>

                            <ValueExpression>

                              <Property>ProblemId</Property>

                            </ValueExpression>

                            <Operator>Equal</Operator>

                            <ValueExpression>

                              <Value>b59f78ce-c42a-8995-f099-e705dbb34fd4</Value>

                            </ValueExpression>

                          </SimpleExpression>

                        </Expression>

                      </Or>

                    </Expression>

                    <Expression>

                      <Or>

                        <Expression>

                          <SimpleExpression>

                            <ValueExpression>

                              <Property>ResolutionState</Property>

                            </ValueExpression>

                            <Operator>Equal</Operator>

                            <ValueExpression>

                              <Value>0</Value>

                            </ValueExpression>

                          </SimpleExpression>

                        </Expression>

                        <Expression>

                          <SimpleExpression>

                            <ValueExpression>

                              <Property>ResolutionState</Property>

                            </ValueExpression>

                            <Operator>Equal</Operator>

                            <ValueExpression>

                              <Value>255</Value>

                            </ValueExpression>

                          </SimpleExpression>

                        </Expression>

                      </Or>

                    </Expression>

                  </And>

                </Expression>

              </Criteria>

              <ExpirationStartTime>12/09/2010 18:48:52</ExpirationStartTime>

              <PollingIntervalMinutes>1</PollingIntervalMinutes>

              <UserSid>S-1-5-21-3175464644-3620557901-2431004025-500</UserSid>

              <LanguageCode>ENU</LanguageCode>

              <ExcludeNonNullConnectorIds>false</ExcludeNonNullConnectorIds>

              <RuleId>$MPElement$</RuleId>

              <TargetBaseManagedEntityId>$Target/Id$</TargetBaseManagedEntityId>

              <TimeZone>2C01000000000000C4FFFFFF00000B0000000100020000000000000000000300000002000200000000000000|Eastern Standard Time</TimeZone>

            </AlertChangedSubscription>

          </DataSource>

        </DataSources>

        <ConditionDetection ID="CD1" TypeID="Microsoft.SystemCenter.Notification.Recipients">

          <Recipients>

            <To>

              <DirectoryReference>

                <RecipientId>6d901c6d-2254-406a-a16b-d766a997839a</RecipientId>

              </DirectoryReference>

            </To>

          </Recipients>

        </ConditionDetection>

        <WriteActions>

          <WriteAction ID="WA0" TypeID="Cmd_9f075aec_9d63_43bf_bccf_f9685bcb3dd7" />

        </WriteActions>

      </Rule>

4. Now you will have to validate what RuleID or ProblemID is the cause of the failure. You will need to run a PowerShell command to validate each RuleID and ProblemID. See below for an example. Make sure to replace the RuleID with the GUID listed in the XML block.

                        <Expression>

                          <SimpleExpression>

                            <ValueExpression>

                              <Property>ProblemId</Property>

                            </ValueExpression>

                            <Operator>Equal</Operator>

                            <ValueExpression>

                              <Value>b59f78ce-c42a-8995-f099-e705dbb34fd4</Value>

                            </ValueExpression>

                          </SimpleExpression>

                        </Expression>

a. RuleID validation - get-rule -id your-RuleID | select-object DisplayName

b. ProblemID Validation - get-monitor -id Your-ProblemID | select-object DisplayName

c. When you run this you should see an output with the display name of the Rule or Monitor if that GUID is valid. What you are looking for is a failure, this is indicated b the return similar to what I have listed below.

This is a valid rule or monitor

This is an invalid rule or monitor and the cause of the failure.  The key here is the “parameter was not found.”

5. So now that you located the cause of the failure you can simply remove the section of the XML file. This will remove the broken reference to the rule or monitor. You will need to remove everything between the <Expression> and </Expression> for the bad GUID.

                     <Expression>

                          <SimpleExpression>

                            <ValueExpression>

                              <Property>ProblemId</Property>

                            </ValueExpression>

                            <Operator>Equal</Operator>

                            <ValueExpression>

                              <Value>b59f78ce-c42a-8995-f099-e705dbb34fd3</Value>

                            </ValueExpression>

                          </SimpleExpression>

                        </Expression>

6. Before saving your edited file make sure you have a backup of the origanal file just incase there was an error in your edit. Now that you have your back you can save the edited file as “Microsoft.SystemCenter.Notifications.Internal.xml”.  Now import the modified Microsoft.SystemCenter.Notifications.Internal.xml file into your management group. You can do this like any other management pack. Allow a few moments for the MP to refresh, then access the subscription again. This will have removed the broken reference and allow you gain access to the subscription again.

Recently I was doing a clean install of the new Exchange 2010 Management Pack for System Center Operations Manger 2007 R2 and ran into the following error when running reports for the first time.

-----------

Error Details:

Microsoft.Reporting.WinForms.ReportServerException: An error has occurred during report processing. (rsProcessingAborted) ---> Microsoft.Reporting.WinForms.ReportServerException: Query execution failed for dataset 'CalculateReportParameterDates'. (rsErrorExecutingCommand) ---> Microsoft.Reporting.WinForms.ReportServerException: For more information about this error navigate to the report server on the local server machine, or enable remote errors

--- End of inner exception stack trace ---

--- End of inner exception stack trace ---

at Microsoft.Reporting.WinForms.ServerReport.GetExecutionInfo()

at Microsoft.Reporting.WinForms.ServerReport.GetParameters()

at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.ReportParameterBlock.Initialize(ServerReport serverReport)

at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.SetReportJob(Object sender, ConsoleJobEventArgs args)

Microsoft.Reporting.WinForms.ReportServerException: Query execution failed for dataset 'CalculateReportParameterDates'. (rsErrorExecutingCommand) ---> Microsoft.Reporting.WinForms.ReportServerException: For more information about this error navigate to the report server on the local server machine, or enable remote errors

--- End of inner exception stack trace ---

Microsoft.Reporting.WinForms.ReportServerException: For more information about this error navigate to the report server on the local server machine, or enable remote errors

After doing some research on this issue it turns this error is caused by the Data Warehouse reader account not having the correct permissions for some items in the data warehouse database. To resolve this you can run the the following SQL query to set the permissions needed.

Like always I suggest that you have a known good backup of the databases before making any changes to it.

Open SQL Management Studio and run the query below.

-----------

USE [OperationsManagerDW]
GO
GRANT SELECT, EXECUTE ON SCHEMA :: Exchange2010 TO “DOMAIN\DataReaderAccount”
GO
-----------

Replace the [OperationsManagerDW] with the name of your data warehouse if yours differs from the default install. Also you will need to replace DOMAIN\DataReaderAccount with the account that your SQL reporting services instance is running under. This should be the data reader account that was configured during the installation of SCOM Reporting.

So we checked the installation log found in %temp% and found no leads other then the error in the screen shot above. So we ran Process Monitor and noticed a failed call to \\SQLClusterName\PIPE\winreg which was the virtual name of the cluster we were running the installation on.  We also ran Debugview and noticed the same call "00000135    43.59947586    [14564] SetSqlProperties: RegConnectRegistry failed to connect to remote reg. Error Code: 0x80070035. \\SQLClusterName”. After doing some digging we were able to track this down to a missing registry value. The value below is used to remap named pipe calls to the current active node of the cluster. So in our case when the installer made a call the registry to check the SQL version the call failed.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters, we should normally have the key:

Name:                          NoRemapPipes

Type:                            REG_MULTI_SZ

Data:                             winreg   svcctl eventlog

So to fix this you will needed to add this registry value on each node. Keep in mind that the values are entered on separate lines. We noticed that you do not need to reboot the node for this to take effect.  Like always make sure to backup your registry before making changes to your production servers.

1. Open the Operations Manager console logged in as an administrator role user

2. Navigate to the Administration node of the console and select accounts under Run As Configuration

3. Select Data Warehouse Action Account from the list of accounts

4. Next select the Credentials tab, then enter the new password for the data writer account then click okay to close the Run As Account Properties windows.

5. Select the Data Warehouse Report Deployment Account from the list of Run As accounts.

6. Next select the Credentials tab, then enter the new password for the data reader account then click okay to close the Run As Account Properties windows.

7. If any of the Run As accounts are being used as service accounts make sure to change the password for these services and restart them after the password has been changed.

8. You will next have to reset the password for the account that the SQL Reporting Server uses to connect to the reports server database. This is often the same user as your data writer account. Open an Administrative command prompt and navigate to the path where rsconfig.exe is located. RSCONFIG.EXE is a tool that will be located under the path were the BIN folder for your installation of SQL is located.

9. You will need to run the following command replacing the server name, database, username and password with your information; RSConfig.exe -c -s SERVERNAME -d DATABASE -a Windows -u DOMAIN\USER -p PASSWORD

10. From the console switch to the Reporting node and run a report to confirm the data reader account is working correctly.

11. Review the operations manager logs to confirm there are no errors pertaining to the password change.

Note: If you used the data reader or data writer account for corresponding service accounts you will need to change the passwords for those services or IIS application pool as well. You can find more information about these steps below or at our TechNet site listed here. https://technet.microsoft.com/en-us/library/bb735419.aspx