Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

xp_SMS_notification not found when Upgrade from SMS 2003 to SCCM 2007

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
Article ID: 556084 - Last Review: May 21, 2008 - Revision: 1.0

xp_SMS_notification not found when Upgrade from SMS 2003 to SCCM 2007

Author: Santos Martinez MVP
Community Solutions ContentCommunity Solutions Content Disclaimer
View products that this article applies to.

SUMMARY

When you try to perform a Upgrade in SMS 2003 to SCCM 2007 on configmgrsetup.log you see a xp_SMS_notification not found and you receive the following error message: Cannot insert the default site control image to the database.
Back to the top

SYMPTOMS

When you try to perform a Upgrade in Microsoft Systems Management Server (SMS) 2003 to System Center Configuration Manager 2007 on configmgrsetup.log you see a xp_SMS_notification not found and you receive the following error message: Cannot insert the default site control image to the database.
Back to the top

CAUSE

Typically, this problem occurs when the xp_SMS_notification extended stored procedure is removed during the SQL Server installation process.

The xp_SMS_notification extended stored procedure is added when you install SMS 2003. If you reinstall SQL Server, the xp_SMS_notification extended stored procedure may be removed.
Back to the top

RESOLUTION

To resolve this problem, you must re-create the xp_SMS_notification extended stored procedure by using SQL Enterprise Manager. To do this, follow these steps:
Collapse this tableExpand this table
1.Click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
2.In SQL Server Management Studio, Connect to  Microsoft SQL Server ServerName, expand Databases, expand System Databases and then click master.
3.In the right pane of SQL Management Studio, Double Click on Programmability, right-click on  Extended Stored Procedure, and then click New Extended Stored Procedure.
4. 
In the Extended Stored Procedure Properties - ServerName dialog box, type xp_SMS_notification, and then click the ellipses (...) button next to DLL Path.

Important The Extended Stored Procedure name is case-sensitive and must be entered as xp_SMS_notification.
5.In the Locate Extended Stored Procedure .DLL dialog box, locate the \SMS\Bin\i386 folder, click smsxp.dl

 
6. Go to Permissions and add NY Authority\System, SMS Admin and Click OK
Back to the top

MORE INFORMATION

http://kbalertz.com/Feedback.aspx?kbNumber=889433
 
Back to the top
APPLIES TO
  • Microsoft Systems Management Server 2003
Back to the top
Keywords: 
kbpubmvp kbpubtypecca kbhowto KB556084
Back to the top
Community Solutions ContentCOMMUNITY SOLUTIONS CONTENT DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.
Back to the top
        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting