AnsweredAssumed Answered

Pdm works error

Question asked by Brian McElmury on Jun 25, 2009
Latest reply on Jul 3, 2009 by David Demaria

Like • Show 0 Likes0
Comment • 4

SW09 sp1 on vault. Two systems on SP3.0 (95% users) other systems are 5% users which are network lic. are using sp1.0. A user running 09 sp1.0 same version of the vault wants move a file from one project folder to another project folder. He has ownership of all the files. Goes thru the process and gets a message saying; error you do not have write access to this project. Please try another project or press cancel. Since than I have logged into his system as administrator and tried with same error. I have also tried on my system getting the same error. I have checked permissions and he has read write access to all the projects. I also backup the vault, and stopped and restarted the vault to validate vault at start up with the same results as before. I have been in contact with our Var and know solutions. Under globel settings the following are checked: Keep extra copy of latest files, Allow users tyo create sub projects, allow attachments to documents owned by others to use, Allow users to remane documents in the vault and bind ownership to Solidworks read-write/read only access.

Any thoughts?

No one else has this question

Outcomes

David Demaria Jun 25, 2009 12:26 PM

Running different SP versions are a perfect recipe for vault problems. Your first step I would suggest be updating everying across your site to the latest SP release (SP4.0 is days away). This must include SolidWorks AND PDMW.

The range of issues that can present themselves while running inconsistent SP's vary but are significant enough to cause such problems.

Actions

Brian McElmury @ David Demaria on Jun 25, 2009 12:49 PM

I have tried moving files being logged in with two systems that are on the same sp as the vault and get the same error. I'll have to work on getting everything to the same service pack.

Actions

Brian McElmury @ Brian McElmury on Jul 2, 2009 1:09 PM

Just a update. This issue is still unresolved, Solidworks has not seen this one before, and we are gathering the info they are looking for.

Actions

David Demaria @ Brian McElmury on Jul 3, 2009 10:59 AM

Brian, I'm trying tp think back to an issue I was faced with several months back where I was getting an error while trying to check documents in or out the server (I honestly dont remember the exacts here).

After contacting our VAR, I was still very much without a clue. Just by chance, I queried the data quota on our network drive allocations and had established, I was over my (400MB) limit. As it turned out, the new install had set my local files location as my (hopelessly undersized) corporate network residing location. I then changed the local files location to C:\local files. After tossing out everything out of the network drive location, the problem instantly went away.

Without know the status or setup of your own netwoprk, just check this out. Clear out any files that may be causing a similar error for yourselves.

Just a thought.

Actions

4 Replies

David Demaria Jun 25, 2009 12:26 PM
Mark Correct
Correct Answer
Running different SP versions are a perfect recipe for vault problems. Your first step I would suggest be updating everying across your site to the latest SP release (SP4.0 is days away). This must include SolidWorks AND PDMW.

The range of issues that can present themselves while running inconsistent SP's vary but are significant enough to cause such problems.
Like • Show 0 Likes0
Actions
- Brian McElmury @ David Demaria on Jun 25, 2009 12:49 PM
  Mark Correct
  Correct Answer
  I have tried moving files being logged in with two systems that are on the same sp as the vault and get the same error. I'll have to work on getting everything to the same service pack.
  Like • Show 0 Likes0
  Actions
  - Brian McElmury @ Brian McElmury on Jul 2, 2009 1:09 PM
    Mark Correct
    Correct Answer
    Just a update. This issue is still unresolved, Solidworks has not seen this one before, and we are gathering the info they are looking for.
    Like • Show 0 Likes0
    Actions
    - David Demaria @ Brian McElmury on Jul 3, 2009 10:59 AM
      Mark Correct
      Correct Answer
      Brian, I'm trying tp think back to an issue I was faced with several months back where I was getting an error while trying to check documents in or out the server (I honestly dont remember the exacts here).
      
      After contacting our VAR, I was still very much without a clue. Just by chance, I queried the data quota on our network drive allocations and had established, I was over my (400MB) limit. As it turned out, the new install had set my local files location as my (hopelessly undersized) corporate network residing location. I then changed the local files location to C:\local files. After tossing out everything out of the network drive location, the problem instantly went away.
      
      Without know the status or setup of your own netwoprk, just check this out. Clear out any files that may be causing a similar error for yourselves.
      
      Just a thought.
      Like • Show 0 Likes0
      Actions

Pdm works error

Outcomes

Related Content

Recommended Content