Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Tuesday, November 26, 2024 
 
slxdeveloper.com Community Forums  
   
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
 Administration Forums - Database Administration
Forum to discuss SQL Server or Oracle database administration related to SalesLogix databases. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to Database Administration | New ThreadView:  Search:  
 Author  Thread: ParamSQLUpd error on remotes
Christine Akdeniz
Posts: 1
 
ParamSQLUpd error on remotesYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 09 May 07 2:00 PM
fiogf49gjkf0d
SLX 6.2.6 - remotes have the following error in their syncerrors.txt file. Error occurs for a handful of tickets.

ParamSQLUpd - Error applying ParamSQL transaction A0436KJ : The query processor could not produce a query plan from the optimizer because a query cannot update a text, ntext, or image column and a clustering key at the same time. SQL: UPDATE TICKETPROBLEM SET MODIFYDATE=?,MODIFYUSER=?,NOTES=?,TICKETID=? WHERE TICKETID LIKE 't6UJ9A000IOI%
[Reply][Quote]
Jeremy Brayton
Posts: 491
Top 10 forum poster: 491 posts
 
Re: ParamSQLUpd error on remotesYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 09 May 07 2:34 PM
fiogf49gjkf0d
The error is actually very descriptive. "You can't update a text (in this case NOTES) and a clustering key (probably TICKETID) at the same time". I don't know of any stock code that updates both the memo and ticketid but that may take place in the Insert New Ticket screen during the SaveProblemInfo or whatever function that creates the ticketproblem record.

The problem is going to be tracking this down. If I had to guess, I would say some custom code somewhere is doing things slightly wrong but this could be happening in stock code as well. If it were to be a stock code problem, it'd be likely due to a improper clustered key set but that's usually something that doesn't just change on it's own.
[Reply][Quote]
 Page 1 of 1 
  You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

   Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 11/26/2024 5:31:43 AM