PDMWORKS VAULT ERROR

[SCRUDRIVER]

We recently upgraded our server and now whenever I go to check something in I get VAULT ERROR 50 7 out of 10 times....very frustrating. I looked up the code for vault error 50 and it wasn't very helpful "50
PDMW_ERROR_FILESYSTEM_UNKNOWN"

Anybody else have this issue or know what is causing it?

I have stopped and restarted PDM service on the server and rebooted my local machine and still same issue.

Thanks

 

[JMirisola]

From the kb:
In this case, a vault administrator should go into the PDMWorks Vault Admin settings and enable the option "Validate Vault" if it is not already turned On. Next, stop the PDMWorks Server service and then restart the service and allow the vault to rebuild itself. After vault has finished restarting, attempt the check in of the assembly and reference files again.



Jeff Mirisola, CSWP, Certified DriveWorks AE

http://designsmarter.typepad.com/jeffs_blog

Dell M90, Core2 Duo, 4GB RAM, Nvidia 3500M

 

[SCRUDRIVER]

Talked to my VAR and they suggested the same thing...unfortunately it didn't help. They are going to try and resolve this but right now no luck.

 

[PDMAdmin]

Scrudriver,

I saw that error a number of years ago, and as I recall, the directory access permissions on our file server were all screwed up. The PDM service account didn't have write permission to the vault directory.

What does your PDM setup look like? Login server and file server are the same machine? If not, is the file server running Windows or Linux/Unix?

 

[SCRUDRIVER]

Fortunately it has not given me this error for awhile now...I restarted the server and PDM service a few times and apparently that did the trick...go figure...

Actually i would like to thank my VAR for nothing...they were supposed to get back to me but never did...good thing we pay them maintanence....

Thanks for the replies though!!!

 

[PDMAdmin]

Another user had a similar problem that was caused by the hard disk running out of space.

thread559-126684

 

[SCRUDRIVER]

We just upgraded to a 500GB hard drive and we are using about 20% of it so I don't think this was the issue. Checked everything else and it looked fine....It may have been because of moving the Vault to a new server.

 

[Standing]

A few years ago we move our data from one server to another. We did a move data to new server, then installed PDM software and pointed everyone PDM to the new server name. Nothing fancy and it worked right away.

Bradley
SolidWorks Pro 2008 x64, SP3.0
PDMWorks Workgroup, SolidWorks BOM,
Dell XPS Intel(R) Pentium(R) D CPU
3.00 GHz, 5 GB RAM, Virtual memory 12577 MB,
nVidia Quadro FX 3400
Use SolidWorks BOM
e-mail is Lotus Notes

 

[SBaugh]

We had a Customer just reinstall the vault and client and it fixed the issue.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

"If it's not broke, Don't fix it!"

faq731-376