• • Home
  • Forum
  • Download
  • Affiliate
  • Product Directory
  • Knowledge Base
  • News

“Error: Message does not exist. Object…”

Solution ID = KB-72

Goal : View all application-specific messages.

Version = Syteline7.03.05

Module : SLMFG

Symptom 1 : Get error message: "Error: Message does not exist."

Symptom 2 : Messages are missing or not available.

Database : SQL 2000

Cause

In rare cases, one or more of the error message tables in the SL 7 SQL database is not populated properly:

• ObjectMainMessages
• ObjectBuildMessages
• ApplicationMessages

The cause of this error is more likely a violation of a Primary Key, Index or Check constraint due to a few records of bad data in the system, or an application bug. You can confirm this by changing the range of data you are processing, or by limiting it to one record to process if possible, to see if the error occurs for all records or only a select few.

Fix

If the Error ends in TYPE :17 and contains an object that starts with PK_ , IX_, or CK_ then it is VERY LIKELY that this is NOT a problem with the ObjectBuildMessages table. It is an application issue that is resulting in a Primary Key , Index or Check Constraint being violated. In this case you should ignore the fix information below, and not do anything to any of the message tables.

FIX STEP 1 - Populate the Message Tables

Here are the instructions on how to get all the SyteLine 7 message tables loaded properly ...

1. Copy the zip patch file from to your SQL Server machine. For example to the D:\Temp folder.

2. Unzip the zip patch file. You should now have the following 4 files in D:\Temp:

• BaseMessages.sql
• ErrorMessages.sql
• ObjectBuildMessages.d
• ObjectMainMessages.d

3. Start up a SQL Query Analyzer session for your application database.

4. Run the "ErrorMessages.sql" SQL script file against the application database.

5. Start up a Command Prompt window (DOS Window), and then run the following commands. Please review the notes that precede the commands:

• The default folder D:\Temp is used as an example in the commands.
• The commands contain angle brackets to indicate where you need to substitute values that reflect your SQL environment.
• Make adjustments as needed in the commands that follow.

BCP .dbo.ObjectBuildMessages in "D:\Temp\ObjectBuildMessages.d"

-c -o"D:\Temp\Result.txt" -U"" -P"" -S"" -t"\t"

BCP .dbo.ObjectMainMessages in "D:\Temp\ObjectMainMessages.d"
-c -o"D:\Temp\Result.txt" -U"" -P"" -S"" -t"\t"

6. Run the "BaseMessages.sql" SQL script file against the application database.

You can ignore the "primary key constraint error" messages that arise while running this script.

Note

This may be followed by other messages. For example: "CK_jobmatl_matl_cost, Type: 17"