Creo file fails to checkin

[BenLoosli]

Version: Windchill 13.0

Use Case: User cannot check in a file

Description:

Part with matching number exists but is checked out by you to other workspace.

The user has no other workspace.

[Hari_Vara]

Hi,

Check the server side workspace that exists with every context for every user.

I think this could be something to do with Numbering of the part.

Cheers

Hari

[BenLoosli]

I am logged in as that user and in his workspace is only 3 files. The part, the drawing and the drawing format. The user has no other workspaces. I even went to the server and ran my SQL query against the DB that reports all workspaces and the owner.

This is a revision to an existing part. Revision A is checked in to common space and now we are trying to get revision B checked in.

[RandyJones]

---

Description:

Part with matching number exists but is checked out by you to other workspace.

The user has no other workspace.

---

I have seen this misleading message when the user has checked out the item in Common Space.

[BenLoosli]

When I look in common space at other files, and select one, it does not allow a check out.

[RandyJones · Accepted solution]

---

@BenLoosli wrote:

When I look in common space at other files, and select one, it does not allow a check out.

---

You are correct. Check out in Common Space only applies to wtparts and not epmdocuments.

[BenLoosli]

Randy,

That was it. I went to common space and checked in the WTpart, then I was able to check in the part and drawing from the workspace.

[Ajit_Kulkarni]

Hello,

I would suggest to do following 

1. Look for a checked out table on home screen by that user. 

2. Activate each workspace by user and see if there are any new objects with same numbers. 

If checked out table or new objects are not giving any clue may be it is a bug in new version. 

Thanks

[BenLoosli]

I am pulling the files into a new local workspace from the uploaded server side workspace of that user.

He has no other workspaces, verified by looking in the DB directly with a script that matches workspaces with the username.

We are using Windchill 13.0.2.1 with Creo 9.0.9.0 and have been since early October with this being the first problem reported by a user.

It is a very minor change and if we have to remove the Rev B files and start back from the Rev A released version, we can do that, but would rather understand where this issue is coming from and see if there is a cure. I have opened a call with PTC, too.