DELETE statement conflicted with COLUMN REFERENCE constraint

For general questions and discussions specific to the AbleCommerce 7.0 Asp.Net product.
Post Reply
PC77375
Ensign (ENS)
Ensign (ENS)
Posts: 4
Joined: Tue Jul 20, 2010 7:33 am

DELETE statement conflicted with COLUMN REFERENCE constraint

Post by PC77375 » Tue Jul 20, 2010 7:37 am

I see the following in the error logs generating every 20-30 seconds:

Error in user maintenance
DELETE statement conflicted with COLUMN REFERENCE constraint 'ac_Addresses_ac_BasketShipments_FK1'. The conflict occurred in database 'Cart', table 'ac_BasketShipments', column 'AddressId'. The statement has been terminated.

Does anyone know how to eliminate this error?

User avatar
mazhar
Master Yoda
Master Yoda
Posts: 5084
Joined: Wed Jul 09, 2008 8:21 am
Contact:

Re: DELETE statement conflicted with COLUMN REFERENCE constraint

Post by mazhar » Tue Jul 20, 2010 9:52 am

What is your application version? You can found this information under Administration -> Help -> About AbleCommerce

PC77375
Ensign (ENS)
Ensign (ENS)
Posts: 4
Joined: Tue Jul 20, 2010 7:33 am

Re: DELETE statement conflicted with COLUMN REFERENCE constraint

Post by PC77375 » Tue Jul 27, 2010 8:18 am

AbleCommerce for ASP.NET
VERSION: 7.0.4.14026
MSSQL v2000
AC SCHEMA v2000


PC77375
Ensign (ENS)
Ensign (ENS)
Posts: 4
Joined: Tue Jul 20, 2010 7:33 am

Re: DELETE statement conflicted with COLUMN REFERENCE constraint

Post by PC77375 » Tue Jul 27, 2010 9:24 am

Already been there and tried that, I get the following when I run the script:
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near 'try'.
Server: Msg 156, Level 15, State 1, Line 29
Incorrect syntax near the keyword 'end'.
Server: Msg 195, Level 15, State 1, Line 34
'ERROR_NUMBER' is not a recognized function name.
Server: Msg 156, Level 15, State 1, Line 43
Incorrect syntax near the keyword 'end'.

PC77375
Ensign (ENS)
Ensign (ENS)
Posts: 4
Joined: Tue Jul 20, 2010 7:33 am

Re: DELETE statement conflicted with COLUMN REFERENCE constraint

Post by PC77375 » Tue Jul 27, 2010 9:29 am

I guess what we are also missing is that bug appears to have been resolved many versions ago. We are running the most current version, are we seeing a new bug?

Post Reply