Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SMS did not create Extended Procedure 'xp_SMS_notification' for SQL 1

Status
Not open for further replies.

Smudgens

MIS
Feb 3, 2000
7
GB
I am getting an error message from the SQL_Monitor saying that sp_addextendedproc is failing to use xp_SMS_notification in SQL. This is the second time I have installed the database with SMS and I have had this same error message both times. Do I need to get this extended procedure from somewhere or do I need to create it. Help please.<br>
<br>
Neil
 
I'm testing SMS now to hopefully put into production soon (see my posting dated 5/23). I also have duplicated this on both instances of testing (new PDC, new network, etc...). Sorry I don't have an answer for you but did you ever get your problem resolved?
 
No, unfortunately not.&nbsp;&nbsp;I have since removed SMS entirely from the Domain and a colleague and myself are trying to re-implement it, however first time we installed on a brand new server (and domain), I got the same message.&nbsp;&nbsp;Whatever I do it still doesn't want to create the extended procedure, and I am wondering what else hasn't been installed, can anybody help.
 
It appears to be triggered by any &quot;inventory&quot; done by the Site Server. The error message 601, using SMS terminology, is &quot;flooding&quot; the SMS_SQL_Monitor component. We've raised the threshhold numbers AND created a filter to ignore that flooded message. Funny thing is that even without making these changes to the SMS configuration, it still seems to work 'ok'...this removed the annoying screen every couple of hours. The Technet articles lead me to believe that it is an SQL problem but those log files contain too many &quot;big&quot; words to be understandable. &lt;grin&gt; As I said in the first reply, the same thing happened to us in October before I had to put it to rest to concentrate on Y2K. This setup I have now, is entirely new (hardware and software service packs) and still get the same problem. Do you know what extended procedure it is having trouble with??? <p>Deon Cranford<br><a href=mailto:deon.cranford@scotlandhealth.org>deon.cranford@scotlandhealth.org</a><br><a href= > </a><br>
 
The extended procedure is 'xp_SMS_notification'.&nbsp;&nbsp;All this appears to have in it is a reference to a DLL in WINNT\System32, we have added this procedure manually and had less problems but haven't managed to clear it up.&nbsp;&nbsp;We also tried manually registering the DLL with REGSVR32 but alas no ....&nbsp;&nbsp;We have just sent off for SP2 for SMS 2.0 and we are hoping that it will fix the problems (Ahhh Microsoft and the need for Service Packs, like Chalk and Chalk).&nbsp;&nbsp;anyway thanks for the help, if you have any flashes of inspiration let me know.<br><br>Regards<br>Smudge
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top