error during check-in

[dgowans]

I have an assembly which I would like to check in to the PDMWorks vault. I am receiving the following error during the check-in process:

Unable to write custom properties to the file "XXXXXX.SLDPRT". Please make sure that the file is not being used by another program.

The part in question does not currently exist in the vault, and I am able to modify the part properties within Solidworks. What is this error attempting to tell me?

Thanks,
Dave Gowans

 

[SBaugh]

Check the version of the vault and the version of your client... they should match.

Regards,

Scott Baugh, CSWP
3DVision Technologies

http://www.3dvisiontech.com

http://www.scottjbaugh.com

faq731-376

 

[dgowans]

Yep - both versions are 2005, SP0.0.

Correct me if I'm wrong, but wouldn't I be unable to log in to the vault at all if the versions were inconsistent? In the past, I think I remember being notified upon login that the vault was newer than the client and being able to update the client automatically.

Dave Gowans

 

[engAlright]

Is the data located on the same computer that is running the vault service? Make sure that the user running the service (you can change this in the properties of the service) has write access to the complete PDMworks directory.

Some other brainstorms:
-make sure there is only one Solidworks & PDMWorks process running
-make sure the document you are checking in is write-enabled (PDMWorks "Read-only for referenced docs" option forces you to have ownership of the file to be able to edit it)

 

[PDMAdmin]

It might be a good idea to verify that you have adequate permissions, both in PDMW and in Windows (or Unix, as the case may be) for the actual vault folder structure.

 

[automationbabe]

Make sure that the file you are trying to check-in is not marked read-only. PDMWorks writes properties to the file and needs write access. I see this most when checking in files from disk.

 

[PeterJelliffe]

I'm getting the same problem. I didnt have it with 2004, but 2005 is the buggiest release I've seen of anything in a while. I can check in components by themselves just fine, but checking them in from teh assembly gives that error.

 

[PeterJelliffe]

The problem is solved if you uncheck "Tools>Options>System Options>External References>Search file locations for external references"

 

[Standing]

Look at Tools, Options, System Options, External References, then uncheck “Search file locations for external references”.

Bradley