V 1.3
We are getting the following error on one of our locations:
Error -2147217873: Cannot insert duplicate key row in object 'Configuration' with unique index 'IX_Configuration_StoreID'.
Any, any thoughts?
V 1.3
We are getting the following error on one of our locations:
Error -2147217873: Cannot insert duplicate key row in object 'Configuration' with unique index 'IX_Configuration_StoreID'.
Any, any thoughts?
Kx?ÕWmsâ6þ\ÿ?ít&¹?_I ä|w`?m)!¹æSÆt±%?-?Ð_?e0¦0.×NËx2?¼zvWûhõd4£)àãC?????H?úS?A¿×÷ àIäCÓôüg?\?gq??e=X5·???SoÎÉYóì¤cig?0¡1iÀfú?k??g~?a|?8¿ÞT¯å¢Ägi@Ýcc>¡lÚi@&z?P&ü?hÚ/|LÂ{«i.??g ?$D§lB?qølIÆXþã?AH?ô ?S?""?~*`NÈÓ? }d!2 ùâä+®9º??¹? _»î~·ç?{?(ÃÌ d©?A&B?À{?,0ðRàbFX&à02O§ ÏbÜH?lMp-%$ßÌ ?³ûÀ5Ðg?ð??ö&ýÙèy%p£?qQ¸ö°·?ð0äsM??=a|8Á^7¢DD'¤XÎ@qds*f?%?UÈ2&C?ØýáÓú>C2Ëáf$?4Ièt&Y="n?¦ l?%¡1æ?Ù8y?þùÿ(4ûòE?Xà ,§>Nh:Î?r?'
Thanks Jeff, that was actually my number one try. This however is a different location issue, but I still went with the db|check|reindex.
Also, I checked that the dbs were running the same in SO Admin and HQ Client (because that would not have surprised me).
Now, I am just baffled. But, I am also now alll about the db|check|reindex! :-)
I did get support involved here, but you know, the more ideas the better. They were first thinking there was something w the store id, but actually, I heard that the id was not changed on this local, and that there were issues with it frfrom day 1, like 5 mos ago.
I'll post back here what we learn.
Have something to add? Share your thoughts — no account required.
Ask the community — no account required