Highlighted

NSS throwing SQL errors in the SQL log after upgrading from NSS 8.1.1 to NSS 8.1.2

Product seems working fine, but this error appears up to 12 times per second in the SQL ERROR log:

Error Message

The activated proc '[dbo].[SqlQueryNotificationStoredProcedure-xxxxxx-xxxxx-xxxxx-xxxxxxxxxxxx]' running on queue 'NSSBE_01.dbo.SqlQueryNotificationService-xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' output the following: 'Could not find stored procedure 'dbo.SqlQueryNotificationStoredProcedure-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'.'

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Re: NSS throwing SQL errors in the SQL log after upgrading from NSS 8.1.1 to NSS 8.1.2

This has been logged as a bug but in the meantime, you can do the following to mitigate:

 Run the following query against the NSS Portal database to get a list of service queues:

select * from sys.service_queues​

Then compare those results to the available stored procedures listed in Management Studio here (also in the portal DB):

Programmability > Stored Procedures > SqlQueryNotificationStoredProcedure-[alphanumeric sequence]

If you cannot find a particular listed stored procedure within the results of your query, it can be deleted manually from the stored procedure list within Management Studio.  Check every listed stored procedure and delete where necessary.

View solution in original post

1 Reply
Highlighted
Accepted Solution!

Re: NSS throwing SQL errors in the SQL log after upgrading from NSS 8.1.1 to NSS 8.1.2

This has been logged as a bug but in the meantime, you can do the following to mitigate:

 Run the following query against the NSS Portal database to get a list of service queues:

select * from sys.service_queues​

Then compare those results to the available stored procedures listed in Management Studio here (also in the portal DB):

Programmability > Stored Procedures > SqlQueryNotificationStoredProcedure-[alphanumeric sequence]

If you cannot find a particular listed stored procedure within the results of your query, it can be deleted manually from the stored procedure list within Management Studio.  Check every listed stored procedure and delete where necessary.

View solution in original post