Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Error message when you transfer a requisition to a purchase order in Business Portal for Microsoft Dynamics GP: "Invalid column name UPDLOCK. Invalid column name holdlock"

Error message when you transfer a requisition to a purchase order in Business Portal for Microsoft Dynamics GP: "Invalid column name UPDLOCK. Invalid column name holdlock"

Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION THAT IS CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED TO SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top

Symptoms

Note Before you follow the instructions in this article, make sure that you have a complete backup copy of the database that you can restore if a problem occurs.

When you transfer a requisition to a purchase order in Business Portal for Microsoft Dynamics GP, you receive the following error message:

Invalid column name UPDLOCK. Invalid column name holdlock. Parameters supplied for object SY01500 which is not a function. If the parameters are intended as a table hint, a with keyword is required.

↑ Back to the top

Cause

This error is caused by a damaged stored procedure in the DYNAMICS database. The name of the stored procedure is coGetNextNoteIndex.

↑ Back to the top

Resolution

To resolve this problem, re-create the coGetNextNoteIndex stored procedure. To do this, follow these steps:
  1. Start the SQL Server Management Studio. To do this, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
  2. Click to expand the following nodes:
    • Databases
    • Programmability
    • Stored Procedures
  3. Right-click the coGetNextNoteIndex stored procedure, and then click Delete.
  4. Download, and then run the following script to re-create the coGetNextNoteIndex stored procedure:
    https://mbs.microsoft.com/fileexchange/?fileID=ae8addfc-3db7-4b77-b397-929a262417dc

↑ Back to the top

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top

Keywords: kbexpertiseadvanced, kbtshoot, kbmbsquickpub, kbnomt, kbnoloc, kbexpertiseinter, kbmbsmigrate, kb, kbgreatplainsbp, kberrmsg, kbnosurvey, kbmbspartner

↑ Back to the top

Article Info
Article ID : 946302
Revision : 1
Created on : 3/25/2017
Published on : 12/29/2014
Exists online : False
Views : 70