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 - Synchronization
Forum to discuss SalesLogix synchronization and remote database management. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to Synchronization | New ThreadView:  Search:  
 Author  Thread: Error Cutting user remote datbase
Patricia Capuz
Posts: 49
 
Error Cutting user remote datbaseYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 09 11:59 AM
Hi Everybody.

I Have a problem. I 'am re-cuting a user remote database and the following error occur:


.
.
.
[02/16/2009 12:45:02 PM]Starting step: stpExecSQL_PopulateTempTable
[02/16/2009 12:45:03 PM]Error in step: stpExecSQL_PopulateTempTable Microsoft OLE DB Provider for SQL Server The statement has been terminated.
[02/16/2009 12:45:03 PM]Finished step: stpExecSQL_PopulateTempTable
[02/16/2009 12:45:03 PM]

Step: stpExecSQL_PopulateTempTable returned error: The statement has been terminated. (Microsoft OLE DB Provider for SQL Server (80040e2f): Violation of PRIMARY KEY constraint 'PK__tbl_U6UJ9A000019__39788055'. Cannot insert duplicate key in object 'tbl_U6UJ9A000019'.)

Step: stpExecSQL_PLUGIN did not execute. See previous error.
.
.
.



Has anybody any idea about it???

What can I do??

I was trying to found the specified DB object "tbl_U6UJ9A000019" but It is not in main DB.


Thanks in advance

Paty
[Reply][Quote]
Mike Spragg
Posts: 1226
Top 10 forum poster: 1226 posts
 
Re: Error Cutting user remote datbaseYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 17 Feb 09 2:36 AM
If you open up the .DTS file that was created during the remote client build you should find this table (it's a temp table - you won't find it in the ordinary schema) and then look for the SQL that's populating it - from here, back-trace and find the duplicate key that's causing the issue. Check your main tables such as T/A/C/O and ensure the Unique/Not Null constraints are set on the primary ID - as this can cause it.
[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 1:08:18 PM