SQL Server reserved words cause error on object lookup when used as extended field name in UAPM.

Document ID : KB000053436
Last Modified Date : 14/02/2018
Show Technical Document Details

Description

Receive the following error when selecting an object from a search return list when the object has an extended field with a name that is a SQL Server reserved word.

"An unexpected error has occurred. Reset entry, collapse and reexpand node, or cancel changes before retrying. If the problem persists, please contact your system administrator."

The uapm<date>.csv contains the following entry "Item cannot be found in the collection corresponding to the requested name or ordinal. "

When trying to delete the extended field the following error is returned:

"An unexpected error has occurred. Reset entry, collapse and reexpand node, or cancel changes before retrying. If the problem persists, please contact your system administrator."

The uapm<date>.csv contains the following error:

"Error executing command with SQL:

  ALTER TABLE dbo.ucapme_<objectname>DROP   COLUMN <sqlserver reserved word>"


Incorrect syntax near the keyword '<sqlserver reserved word> ADO Error #1: -2147217900 / Incorrect syntax near the keyword 'sqlserver reserved word. (Source: Microsoft OLE DB Provider for SQL Server Native error: 156 SQLState: 42000)
Incorrect syntax near the keyword 'sqlserver reserved word."

Solution

SQL Server reserved words should not be used as extended field names in UAPM. The list of SQL Server reserved words are available at the following URL.

http://msdn.microsoft.com/en-us/library/aa238507(SQL.80).aspx