PDMWorks(2003)-A document named "xx" already exists on the vault ... 3

[Baruch]

PDMWorks(2003)-A document named "xx" already exists on the vault ...
I wonder if someone had ever seen this message during file check-in:
"A document named "xx" already exists on the vault but appears to be a different document than this one."
This happens to us from time to time and each time when I try to investigate I get nothing.
The test I make is very simple: Open this specific file from the vault to empty directory (starting to work on the file from the beginning),
Then without doing absolutely anything I make check in,
And then I get this dialog: "A document named … please press OK."
then I get the PDMWorks form for check in, and there I get something also strange, that all the reference files in the: "Select reference to check in" list to this drawing (that what I had last time) are colored red, instead of black or gray for read-only files.
Just to emphasize my story a moment before I make check in while I checked the status of all those files the local directory I see the equal icon before each file.

 

[automationbabe]

We had this problem too, and there are two things that could be happening:

One (which doesn't sound like your issue): A completely new assembly/part was started from scratch that uses a part number in PDM. The reason it shows red is that it technically isn't the same file PDM gave you. That would also explain the error message. PDM wants you to verify that you are not over-riding an existing part with a completely different one.

Two (which isn't very obvious): Your global date settings on your system. Not sure why, but there is one setting PDM doesn't like. Play with those a little and see if it changes the colors.

Hope that helps. Good luck.

 

[Baruch]

Hi, and thanks for your response,
The first thing as you mention is the obvious, I would like to ask about the second reason you mention, do you mean to play with the “Regional and Language Options” in Control Panel? From your experience could it be only at very minor cases?

 

[automationbabe]

Yes...the settings for your entire computer. Don't know why.

Very few cases. Our VAR notes us as the only case so far as I know. It's a setting you can set, but if your company settings over-ride yours, you may want to explain the situation. It seems so non-related but I know it drove me nuts for months.

 

[avlis]

We also had this issue. Every part checked out and back in would give this message and refs would appear red. It would occur every time daylight savings time ended or started. The fix is to restart your vault service on the PDM Server.

 

[Baruch]

Thanks for all your responses,
I tried all you mention but nothing helped with this specific file, it seems that there are some more reasons for this behavior.
Yesterday it happened again, I opened a small project from the vault to a local directory.
My target was to make a very similar part to the opened part.
I used SW Explorer to rename the files (1 part, 1 ass, 2 drw.), cleaned all the custom properties PDMWorks added to those file, made all the mechanical changes to the part, and made check-in, now it is a new part (a new filename) and then I get again:
“A document named "xx" already exists on the vault …”. I continued with my check-in and at end of the process I tried to check-in again, and again the same message.
Now I suspect that maybe something wrong with the process of recycling parts from the vault and making rename with SW Explorer.

 

[Standing]

Baruch
Just a thought, have your PDM/Works administrator (they can see all folders) search from the top of the vault for the document. See what he or she gets. There is a possibility that the part name is already in PDM, in a hidden folder. Our administrator takes models we do not want anymore, (obsolete) and puts them in a hidden folder that only he can see.

Bradley

 

[automationbabe]

You get a star Bradley...keep fogetting about the hidden folders.
A vault rebuild may be needed as well if that hasn't been tried.
Good luck. I know how frustrating it is.