SQL Server 2000

  1. The number of current notification batches in the delivery retry queue. This counter is updated periodically when the application ...
  2. The number of event batches committed but not yet picked up by the generator. This counter is updated periodically when the ...
  3. The number of notification batches awaiting the distributor to pick up for distribution. This counter is updated periodically ...
  4. The number of notification batches currently being generated. This counter is updated periodically when the application is ...
  5. The number of notification batches that failed the delivery process since the application started. This counter is updated ...
  6. The number of notification batches with expired notifications. This counter is updated periodically when the application ...
  7. The number of notification status callbacks made is larger than the number of notifications. This is due to an error in the ...
  8. The number of notifications awaiting the distributor to pick up for distribution. This counter is updated periodically when ...
  9. The number of notifications in the expired batches. This counter is updated periodically when the application is enabled. ...
  10. The number of notifications that have failed the delivery process since the application started. This counter is updated ...
  11. The number of subscribers that are disabled in the instance. This counter is updated periodically when the application is ...
  12. The number of subscribers that are enabled in the instance. This counter is updated periodically when the application is ...
  13. The OLE DB datatype for ending the datetime column in the Daylight Savings table is not correct in an extended stored procedure. ...
  14. The OLE DB datatype for starting the datetime column in the Daylight Savings table is not correct in an extended stored procedure. ...
  15. The OLE DB datatype for the DSTOffset column in the Daylight Savings table is not correct in an extended stored procedure. ...
  16. The OLE DB datatype for the GMTTime column in the subscription schedules table is not correct in an extended stored procedure. ...
  17. The OLE DB datatype for the ScheduleData column in the subscription schedules table is not correct in an extended stored ...
  18. The OLE DB datatype for the ScheduleId column in the subscription schedules table is not correct in an extended stored procedure. ...
  19. The OLE DB datatype for the ScheduleType column in the subscription schedules table is not correct in an extended stored ...
  20. The protocol retry schedule is not valid. Each retry schedule entry must be a duration value conforming to the XML duration ...
  21. The quantum details requested are for an initialization quantum entry. These entries are made to reset the generator quantum ...
  22. The quantum end time is later than the current real clock time. Notification Services cannot process events that occur in ...
  23. The rule name is not valid. Rule names must not contain any of the following characters: open bracket ([), close bracket ...
  24. The service account does not have sufficient privileges to run some extended stored procedures. Please run the command GrantXpExec.cmd ...
  25. The service application list could not be synchronized with the instance's application list in the database. The instance ...
  26. The service is locked by the Service Control Manager and cannot be deleted or created until all applications using it have ...
  27. The set of event and subscription rules could not be obtained because the rule type, event class id, or subscription class ...
  28. The specification for the PRIMARY filegroup could not be found. If any filegroups are specified, one must be named "PRIMARY". ...
  29. The specified assembly does not implement a continuous event provider. Ensure that the assembly name specified in the application ...
  30. The specified assembly does not implement a scheduled event provider. Ensure that the assembly name specified in the application ...
  31. The specified class name is already in use. Class names must be unique across all event, subscription, and notification classes ...
  32. The specified delivery channel name is not valid. Delivery channel names cannot contain the following characters: open bracket ...
  33. The specified event provider class name could not be found in the given assembly. Ensure that the class name and assembly ...
  34. The specified event provider has not been registered. Ensure that it appears in the Providers section of the application ...
  35. The specified event provider name is not valid. Ensure that it has been specified in the application definition file (ADF). ...
  36. The specified field name is already in use by this notification class. Field names must be unique across all Fields, ComputedFields ...
  37. The specified protocol is not recognized. If you are using a custom delivery protocol, then an assembly and class name must ...
  38. The specified protocol name is not valid. Protocol names cannot contain the following characters: open bracket ([), close ...
  39. The specified provider name is not valid. Provider names cannot contain the following characters: open bracket ([), close ...
  40. The specified system name is not valid. A system name cannot be "localhost," an IP address or contain the backslash character. ...
  41. The start and end times supplied are invalid. The start time should be less than the end time. The end time should be within ...
  42. The starting datetime value is later than the ending datetime value in the schedule scanning extended stored procedure call. ...
  43. The string buffer supplied to the string formatting routine in the extended stored procedure was too small to continue processing. ...
  44. The total number of event batches submitted since the application started. This counter is updated periodically when the ...
  45. The total number of events received since the application started. This counter is updated periodically when the application ...
  46. The total number of notification batches successfully delivered since the application started. This counter is updated periodically ...
  47. The total number of notifications successfully delivered since the application started. This counter is updated periodically ...
  48. The total number of subscriptions added to the application since the application started. This counter is updated periodically ...
  49. The Windows Installer service cannot update the protected Windows file 2]. {Package version: 3], OS Protected version: 4], ...
  50. The Windows Installer service cannot update the system file 2 because the file is protected by Windows. You may need to update ...
  51. The work item could not be abandoned. The work item was assigned to a distributor but an error prevented it from being processed. ...
  52. There is no disk in drive 2]. Please insert one and click Retry, or click Cancel to go back to the previously selected volume. ...
  53. There is no disk in drive 2]. Please insert one and click Retry, or click Cancel to return to the browse dialog and select ...
  54. This edition of SQL Server is not supported. Notification Services requires SQL Server Standard, Developer or Enterprise ...
  55. This feature frees up 1 on your hard drive. It has 2 of 3 subfeatures selected. The subfeatures free up 4 on your hard drive. ...
  56. This feature frees up 1 on your hard drive. It has 2 of 3 subfeatures selected. The subfeatures require 4 on your hard drive. ...
  57. This feature requires 1 on your hard drive. It has 2 of 3 subfeatures selected. The subfeatures free up 4 on your hard drive. ...
  58. This feature requires 1 on your hard drive. It has 2 of 3 subfeatures selected. The subfeatures require 4 on your hard drive. ...
  59. Total number of format requests that succeeded since the distributor was started. This is not the number of notifications ...
  60. Total number of subscribers added since the instance started. This counter is updated periodically when the application is ...
  61. User 2 has previously initiated an installation for product 3]. That user will need to run that installation again before ...
  62. User 2 has previously initiated an installation for product 3]. That user will need to run that installation again before ...
  63. You can either keep any existing installed elements on your system to continue this installation at a later time or you can ...
  64. You do not have sufficient privileges to complete this installation for all users of the machine. Log on as an administrator ...
  65. You may either restore your computer to its previous state or continue the installation later. Would you like to restore? ...
  66. You must restart your system for the configuration changes made to 2 to take effect. Click Yes to restart now or No if you ...