Select the product you need help with
FIX: Error message when you run the snapshot agent on a replication of a stored procedure in SQL Server 2005 or in SQL Server 2008: "The Name property cannot have a value of @param＿name for this version of SQL Server"Article ID: 956889 - View products that this article applies to. Bug #: 50003735 (SQL Hotfix) Bug #: 50003135 (SQL Hotfix) SQL Server 2008Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.SQL Server 2005Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.On This PageSYMPTOMS In Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, you have a stored procedure that has a parameter whose name contains full-width underscore characters (＿). You create a replication on this stored procedure. However, when you run the snapshot agent, you receive the following error message: Error: 14151, Severity: 18, State: 1. Replication-Replication Snapshot Subsystem: agent <AgentName> failed. The replication agent had encountered an exception. Source: Unknown Exception Type: Microsoft.SqlServer.Management.Smo.WrongPropertyValueException Exception Message: The Name property cannot have a value of @param＿name for this version of SQL Server. CAUSEThe snapshot agent calls the Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.GenerateStoredProcedureArticleScripts method. This method eventually calls the Microsoft.SqlServer.Management.Smo.ParameterBase.CheckParamName method. The CheckParamName method raises the WrongPropertyValueException exception if full-width underscore characters (＿) are used in the name of the parameter. RESOLUTIONFor SQL Server 2008The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:958186 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/958186/
)
Cumulative update package 2 for SQL Server 2008956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was releasedFor SQL Server 2005SQL Server 2005 Service Pack 2Important You must use this fix if you are running SQL Server 2005 Service Pack 2.The fix for this issue was first released in Cumulative Update 10 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 956854 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/956854/LN/
)
Cumulative update package 10 for SQL Server 2005 Service Pack 2937137
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
SQL Server 2005 Service Pack 3Important You must use this fix if you are running SQL Server 2005 Service Pack 3.The fix for this issue was also later released in Cumulative Update 1 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 959195 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/959195/LN/
)
Cumulative update package 1 for SQL Server 2005 Service Pack 3960598 Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/960598/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was releasedSTATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor SQL Server 2008For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:958186
(http://support.microsoft.com/kb/958186/LN/
)
Cumulative update package 2 for SQL Server 2008For SQL Server 2005This hotfix enables you to use full-width underscore characters (＿).For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base: 956854
(http://support.microsoft.com/kb/956854/LN/
)
Cumulative update package 10 for SQL Server 2005 Service Pack 2REFERENCES
For more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956909
For more information about the list of builds that are available after the release of SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released
937137
For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/937137/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
913089 For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service pack for SQL Server 2005
http://go.microsoft.com/fwlink/?LinkId=71711
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
(http://go.microsoft.com/fwlink/?LinkId=71711)
935897
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 956889 - Last Review: December 20, 2008 - Revision: 4.0 APPLIES TO
|
Back to the top
