Showing posts with label notification. Show all posts
Showing posts with label notification. Show all posts

Monday, March 26, 2012

How do I know I have notification services (DST)

Hello,
How can I verify this? We have SQL 2000 (version 8) with sp4.
I am referring to the daylight saving time.
Thanks ahead.
Tony
You can take a look at the section "How to determine whether SQL Server 2000
Notification Services is installed" in the following KB article:
http://support.microsoft.com/?id=931815
It outlines 3 methods to verify if you have NS installed.
Note that even if you determine that you have NS installed you may not need
to do anything. You are affected only if you have an instance of NS
deployed. Just installing NS will not be a problem with DST (the binary
files are not affected). To verify if you have an instance you can check if
you see the NS* services running and if there are any NS* databases.
HTH,
Plamen Ratchev
http://www.SQLStudio.com

How do I know I have notification services (DST)

Hello,
How can I verify this? We have SQL 2000 (version 8) with sp4.
I am referring to the daylight saving time.
Thanks ahead.
TonyYou can take a look at the section "How to determine whether SQL Server 2000
Notification Services is installed" in the following KB article:
http://support.microsoft.com/?id=931815
It outlines 3 methods to verify if you have NS installed.
Note that even if you determine that you have NS installed you may not need
to do anything. You are affected only if you have an instance of NS
deployed. Just installing NS will not be a problem with DST (the binary
files are not affected). To verify if you have an instance you can check if
you see the NS* services running and if there are any NS* databases.
HTH,
Plamen Ratchev
http://www.SQLStudio.comsql

How do I know I have notification services (DST)

Hello,
How can I verify this? We have SQL 2000 (version 8) with sp4.
I am referring to the daylight saving time.
Thanks ahead.
TonyYou can take a look at the section "How to determine whether SQL Server 2000
Notification Services is installed" in the following KB article:
http://support.microsoft.com/?id=931815
It outlines 3 methods to verify if you have NS installed.
Note that even if you determine that you have NS installed you may not need
to do anything. You are affected only if you have an instance of NS
deployed. Just installing NS will not be a problem with DST (the binary
files are not affected). To verify if you have an instance you can check if
you see the NS* services running and if there are any NS* databases.
HTH,
Plamen Ratchev
http://www.SQLStudio.com

Friday, March 9, 2012

How do I fix an intenal NS SP error?

I am in the process of moving some Notification Services 2.0 applications to another server running SQL Server 2005 with Notification Services 2005. I have modified my old ADF files to get rid of the Notify() function as it is no longer supported in version 2005.

When I try to create a new instance using the old IDF file I get some errors, that I believe is internal Notification Services errors: The creation-script tries to create an SP named NSGet<MyAlertName>SMTPNotificationsDeveloperDefined but failed because of an undeclared scalar variable @.workItemId. This is not a variable I have created.

Looking at my old application, currently running fine on SQL Server 2000, I can not find the NSGet<MyAlertName>SMTPNotificationsDeveloperDefined SP, but one that is named NSGet<MyAlertName>SMTPNotifications instead. This SP takes the @.workItemId variable as a parameter, but the new SP (NSGet<MyAlertName>SMTPNotificationsDeveloperDefined) does not.

These stored procedures and the variable is as far as I know created by Notification Services so I don't see how I can correct the error? But as things are now, I'm not able to create the new instance because of this error. I have tried on both Management Studio and the NS command promt - but the same error occurs.

Anyone know how to fix this issue?

Please ignore or delete my post.

It seems that I have done some querying on the old SP which had @.workItemId via an <SQLExpression>.

Sorry for the inconvinience.