We run a scheduled import every hour. Occassionally (about once in 2 days) w
e
get the following error:
Error Information
An error has occurred that has interfered with the generation of this
report. Please try the operation again, and contact your system administrato
r
should this error persist.

Error ID: -2147352567
Source File:
Source Method: .Net SqlClient Data Provider
Source Line: 0
Description: Violation of PRIMARY KEY constraint
'PK__##impBlobData__23637A1C'. Cannot insert duplicate key in object
'##impBlobData'. The statement has been terminated.

Recommended Action:
----------------------------------------

We are running MCMS 2002 sp1a, Windows Server 2003.
I have found 2 KB articles with the same Error ID, but different
Descriptions: 823452 & 899962.

Anybody able to offer any help or suggestions?

[ Post a follow-up to this message ]

David,

See also KB article 811993 (although that applies to MCMS2002 before
SP1).
We've gotten the same error when we did a scheduled incremental import.
It has happened on all MCMS2002 versions, so also on SP1a.

I've noticed that this can start to occur after one of the imports went
wrong for some reason (for instance: timeout settings on the webserver
set too low or metabase file not updated. Usually happens with big
imports). Maybe the import inserted a node which wasn't rolled back
when the import failed, I'm not sure.

You need to "refresh" the contents of your database, to get any
weird/duplicate stuff out. What I do to get rid of the problem is
create a new MCMS database, but not by using backup/restore, but
through an sdo export:

- export all of the site contents to an sdo file
- delete your MCMS database in SQL server and create it again using the
same name. You could also try leaving the original databas, but
deleting all channels/galleries, although I'm not sure if that's enough
- point the DCA to it, to ensure that the SP1a update is performed on
the database
- now import your sdo again

regards
Pascal


David Adamson schreef:
> We run a scheduled import every hour. Occassionally (about once in 2 days)
 we
> get the following error:
> Error Information
> An error has occurred that has interfered with the generation of this
> report. Please try the operation again, and contact your system administra
tor
> should this error persist.
>
> Error ID: -2147352567
> Source File:
> Source Method: .Net SqlClient Data Provider
> Source Line: 0
> Description: Violation of PRIMARY KEY constraint
> 'PK__##impBlobData__23637A1C'. Cannot insert duplicate key in object
> '##impBlobData'. The statement has been terminated.
>
> Recommended Action:
> ----------------------------------------
>
> We are running MCMS 2002 sp1a, Windows Server 2003.
> I have found 2 KB articles with the same Error ID, but different
> Descriptions: 823452 & 899962.
>
> Anybody able to offer any help or suggestions?

[ Post a follow-up to this message ]

Thanks for the advice Pascal.
Due to the urgency, I logged a PSS call with Microsoft. They have seen
similar issues before and believe it may be to do with having a large amount
of items in "Deleted Items". I've taken their advice and cleared these.
Evidently there were many hundreds of items in the resource gallery deleted
items.

We have not experienced the problem since, but I will keep this post up to
date with any further news on the matter.

Dave

"Pascal" wrote:

> David,
>
> See also KB article 811993 (although that applies to MCMS2002 before
> SP1).
> We've gotten the same error when we did a scheduled incremental import.
> It has happened on all MCMS2002 versions, so also on SP1a.
>
> I've noticed that this can start to occur after one of the imports went
> wrong for some reason (for instance: timeout settings on the webserver
> set too low or metabase file not updated. Usually happens with big
> imports). Maybe the import inserted a node which wasn't rolled back
> when the import failed, I'm not sure.
>
> You need to "refresh" the contents of your database, to get any
> weird/duplicate stuff out. What I do to get rid of the problem is
> create a new MCMS database, but not by using backup/restore, but
> through an sdo export:
>
> - export all of the site contents to an sdo file
> - delete your MCMS database in SQL server and create it again using the
> same name. You could also try leaving the original databas, but
> deleting all channels/galleries, although I'm not sure if that's enough
> - point the DCA to it, to ensure that the SP1a update is performed on
> the database
> - now import your sdo again
>
> regards
> Pascal
>
>
> David Adamson schreef: 
>
>

[ Post a follow-up to this message ]