Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations IDS on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

EPDM 2010 Error msg on Check-in

Status
Not open for further replies.

APPENG

Mechanical
Jan 22, 2002
366
Strangest thing happening here... An assembly checked out with some of its associated parts by a co-worker. When asked to check-in what he has he is unable to check in the assembly. Instead he gets a msgBox that that says "Could not find item in database" He can however at least check-in the associated parts.. one by one.. but not the assembly. Worst part is that this is a critical project and only two weeks let before the deadline.. absolutely horrible timing.

Looking at his admin logs i see a recurring error that reads as follows:

<date><Time>
Module: Explorere.EXE
Function: hGetErrCode
Code: E_EDM_DATABASE_ACCESS
Code Description: Counld not access the item in the database.
Error running query in SpDbOdbc
State=23000
Msg=[Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'aaaaaRevision1_PK'. Cannot insert duplicate key in object 'dbo.revisions'.

He has access to the vault, network connection is fine, no one else is affected by this problem as I am able to check-in and out freely.

Things Tried:
reboot his computer
Log out of the vault and back in

Next thing is that I have requested our admin to restart the vault and dBase services...

Anyone have any other ideas?

Regards,
Jon
 
Replies continue below

Recommended for you

can he email you the asm file, then do a "undo checkout".
this will allow you to check out the file & then replace it with the emailed asm file & check it back in.

its a work around to the problem, but it should work in a squeeze for time.
 
The error suggests that that the vault has at least a partial entry for that assembly at that revision level. If a reboot of the vault does not solve the problem, I would try checking it in at the next revision up (if this does not create a revision control issue) or deleting the desired check in revision from the vault if it already exists. Take appropriate precautions if the delete route is chosen.

Eric
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor