AnsweredAssumed Answered

Unable to Write Custom Properties during Check In

Question asked by Pat Goettig on May 10, 2013
Latest reply on Jul 21, 2014 by Andrew Van Denend

Like • Show 0 Likes0
Comment • 7

Hello,

I am having trouble with checking things into our workgroup PDM vault. Here is a summary of what is happening:

I finish creating a drawing or an assembly and I attempt to check it in to the vault. I edit the custom properties that I want to (ie. description, drafted by, approved by, date approved, etc.) for both the drawing and the associated sldprt file. I click check in and then it gives me the following error:

I don't ever run more than one instance of Solidworks and I have had this issue both when the associated part was open and when it was not open.

I tried deleting Solidworks completely and re-installing and then restoring my settings files (without and with system options).

I even completely re-installed Solidworks and didn't restore my settings files.

Every time I tried one of the above solutions, Check-in functionality would go back to normal for a couple days but then start giving me this error again.

I contacted our company's reseller and they gave me a work around that I am not happy with. Basically, they said after I check stuff out of the vault I need to move it to a different folder before checking it back into the vault and then it will work. This does work, but I don't understand why I have to do this in the first place because I shouldn't have to.

Also, this does not happen when I check-in the part first, only a drawing or assembly.

I even tried disabling the "Search file locations for external refrerences" box in the System Options->External References section.

Has anyone ever come across this before or know what is going on?

No one else has this question

Outcomes

Jerry Steiger May 25, 2013 3:32 PM

Pat,

For some reason your post just showed up for me to read, even though I have been reading the posts in this forum every day. (About a half dozen other posts in this forum also showed up today for the first time.)

I've never seen this particular problem before, but that may be because I don't make extensive use of the custom properties.

I assume that you are changing the custom properties in both the part file and the drawing file. Is that correct?

Since it seems to work OK to check in the part, then check in drawing or assembly, it seems like an easier work-around would be to check in any revised parts first, then separately check in the assembly or drawing. I don't really understand why moving the files to a different folder helps.

Jerry S.

Actions

Larry Zolla

May 31, 2013 4:38 PM

Hi Pat,

When you run into this again; stop the check-in and go to File, File References and check to see where the associated files are all coming from.

I’m wondering if you might be accessing a part for a shared or non-writable location of the network.

A similar case I’ve see was where someone else is modeling the part and then the detailing is done by another worker.

The drawing was created in the local working folder while it was using the model from a UNC share path.

The preferred process would be to have the modeler check the part into the vault and then the detailer , can check it out , create the drawing and check the pair back in.

You might also look at Knowledgebase Articles S-036268 and S-026250 for a match as well.

-Larry

Actions

Pat Goettig Jun 7, 2013 5:15 PM

Thank you for your input. Another thing I have noticed lately is that this error will not occur on assemblies that I check out of the vault, revise, and then check back in. The check-in works just fine in these instances.

Any more thoughts?

Actions

John Burrill Jun 7, 2013 6:29 PM

Hi Pat, I have this issue periodically, where despite my having write access to the files and having 'check file locations for external references' turned off I have to open the indicated parts individually and check those in beforehand. I've had this issue at home and on my work machine.

John

Actions

Andrew Van Denend Jul 21, 2014 3:00 PM

I realize that this is an "older" post but I ran into this issue today when attempting to check-in to the PDM Vault using SW2013, SP5.0. The only solution I found to this issue was to create a completely new part based on the problem part. I then replaced all instances of the old part with the new one, redirected all references to the new part, deleted the old part, and renamed the new part to the original file name.

Yes, it was inelegant and a bit of a hassle, but I couldn't come to a resolution any other way. Hope this is helpful to someone else.

Actions

Jeff Holliday @ Andrew Van Denend on Jul 21, 2014 4:51 PM

Just checking - have you taken ownership of the part you checked out of the vault? If not, it will work as though it has been checked out "read only" and not let it check back in. The solution is to navigate to the list for the file in the vault and "take ownership".

Welcome to the forum!

Actions

Andrew Van Denend @ Jeff Holliday on Jul 21, 2014 5:22 PM

Thanks for the welcome, Jeff.

I've only run into this issue when checking a new part into the vault, with the option to take ownership selected. I think the error may have been related to an external reference to a deleted configuration of the problem part, but I'm not sure of that.

Actions

7 Replies

Jerry Steiger May 25, 2013 3:32 PM
Mark Correct
Correct Answer
Pat,

For some reason your post just showed up for me to read, even though I have been reading the posts in this forum every day. (About a half dozen other posts in this forum also showed up today for the first time.)

I've never seen this particular problem before, but that may be because I don't make extensive use of the custom properties.

I assume that you are changing the custom properties in both the part file and the drawing file. Is that correct?

Since it seems to work OK to check in the part, then check in drawing or assembly, it seems like an easier work-around would be to check in any revised parts first, then separately check in the assembly or drawing. I don't really understand why moving the files to a different folder helps.

Jerry S.
Like • Show 0 Likes0
Actions
Larry Zolla May 31, 2013 4:38 PM
Mark Correct
Correct Answer
Hi Pat,
When you run into this again; stop the check-in and go to File, File References and check to see where the associated files are all coming from.
I’m wondering if you might be accessing a part for a shared or non-writable location of the network.
A similar case I’ve see was where someone else is modeling the part and then the detailing is done by another worker.
The drawing was created in the local working folder while it was using the model from a UNC share path.
The preferred process would be to have the modeler check the part into the vault and then the detailer , can check it out , create the drawing and check the pair back in.

You might also look at Knowledgebase Articles S-036268 and S-026250 for a match as well.

-Larry
Like • Show 0 Likes0
Actions
Pat Goettig Jun 7, 2013 5:15 PM
Mark Correct
Correct Answer
Thank you for your input. Another thing I have noticed lately is that this error will not occur on assemblies that I check out of the vault, revise, and then check back in. The check-in works just fine in these instances.

Any more thoughts?
Like • Show 0 Likes0
Actions
John Burrill Jun 7, 2013 6:29 PM
Mark Correct
Correct Answer
Hi Pat, I have this issue periodically, where despite my having write access to the files and having 'check file locations for external references' turned off I have to open the indicated parts individually and check those in beforehand. I've had this issue at home and on my work machine.
John
Like • Show 0 Likes0
Actions
Andrew Van Denend Jul 21, 2014 3:00 PM
Mark Correct
Correct Answer
I realize that this is an "older" post but I ran into this issue today when attempting to check-in to the PDM Vault using SW2013, SP5.0. The only solution I found to this issue was to create a completely new part based on the problem part. I then replaced all instances of the old part with the new one, redirected all references to the new part, deleted the old part, and renamed the new part to the original file name.

Yes, it was inelegant and a bit of a hassle, but I couldn't come to a resolution any other way. Hope this is helpful to someone else.
Like • Show 0 Likes0
Actions
- Jeff Holliday @ Andrew Van Denend on Jul 21, 2014 4:51 PM
  Mark Correct
  Correct Answer
  Just checking - have you taken ownership of the part you checked out of the vault? If not, it will work as though it has been checked out "read only" and not let it check back in. The solution is to navigate to the list for the file in the vault and "take ownership".
  
  Welcome to the forum!
  Like • Show 0 Likes0
  Actions
  - Andrew Van Denend @ Jeff Holliday on Jul 21, 2014 5:22 PM
    Mark Correct
    Correct Answer
    Thanks for the welcome, Jeff.
    
    I've only run into this issue when checking a new part into the vault, with the option to take ownership selected. I think the error may have been related to an external reference to a deleted configuration of the problem part, but I'm not sure of that.
    Like • Show 0 Likes0
    Actions

Unable to Write Custom Properties during Check In

Outcomes

Related Content

Recommended Content