AnsweredAssumed Answered

Issue with SAVE AS .sldasm files into the vault

Question asked by Alexandra P. Spaulding on Dec 12, 2013
Latest reply on Nov 6, 2018 by S. Casale

Like • Show 0 Likes0
Comment • 7

Hi,

We're having a randomly occuring issue with saving SW Assembly files into the vault. This is what's been happening: after creating an assmebly and going through the SAVE AS process, my engineers have noticed that randomly not all of these files are actually being saved into the vault, rather they're existing in a hidden local state (which you only discover, after flipping the SEE ALL FILES in the Admin tools). There doesn't seem to be any particular reason why some files SAVE AS just fine into the vault and some don't, however we currently only seem to be having this issue with .sldasm files. We've managed to circumnavigate this issue two ways: 1 . by saving to the desktop, and then saving from there to the vault, 2. Dumb luck. With one occurance I tried SAVE AS 7 times, on the 8th time it worked fine.

Can someone point me in the right direction?

Thank you

Alexandra

2 people also have this question

Outcomes

Charley Saint Dec 12, 2013 5:04 PM

Alexandra,

This was a problem in EPDM 2012, I thought it was resolved but the SPR (646713) says it's still open. Here's the workaround from there (it's not terribly helpful):

Workaround: Use "save" instead of "save as" when saving a new assembly or drawing. A dialog shows where you can select "do not save read-only documents" to avoid the extra warning dialogs showing up. New file will be added correctly. For files that ended up local, browse to the file in Explorer, right-click (RMB), Add to File Vault, reopen in SolidWorks and resave if needed. Note: Same proplem can happen if making assembly or drawing from files opened in older SW format.

Actions

Alexandra P. Spaulding @ Charley Saint on Dec 12, 2013 5:10 PM

Charley,

Thank you for your prompt response. Do you know if this issue has been resolved in EPDM 2013/14? We're currently using PDM 12 with SP2, and are trying to hedge our bets about UGing to PDM 13 or wait for PDM '14's SP 2 release, then UG.

Thank you,

Alexandra

Actions

Charley Saint @ Alexandra P. Spaulding on Dec 12, 2013 6:51 PM

Alexandra,

I checked the KB again but couldn't find anything that said it was fixed, but I'm fairly certain it was as I haven't heard anything about it in a while. I'd say it was probably fixed in 2013 sometime.

Actions

Barrie Turner @ Alexandra P. Spaulding on Nov 6, 2018 7:57 AM

I had this today with PDM Pro 2018. I couldn't use the 'Save' workaround Charley mentioned as the files were created outside the vault environment. I'm pretty sure Hector's notes could be rolled into a strategy to stop it happening again.

Actions

Hector Baezs Dec 19, 2013 12:36 PM

Alexandra,

I manage the PDM for our company, and I have come across this same issue or a similar one.

We do a save as and not all files are added into the vault.

I found that in one of these occurrences, the assembly that is being saved had a component open in a different window, and when SolidWorks goes to save that assembly, it tries to save the component as well. If write capabilities are not allowed on the component then the assembly fails to save into the vault, and exists as a local file only.

My solution to this issue is to close the component and attempt the re-save.

If that fails, then save out of the vault and then back in.

After this, the issue is usually solved for me.

Actions

Barrie Turner @ Hector Baezs on Nov 6, 2018 7:49 AM

Thanks for confirmation of my initial findings. Though I'm not about to test this I can confirm I saved-as and had the hidden files issue today, using PDM Pro 2018. It seems I set myself up for failure by opening all the read only parts' save dialogues then dismissing them all individually. The only way is to cancel the first save without opening the dialogues. (Yes, I'm failing to make this clear, sorry.)

(I ensure all our users have hidden files hidden after setting up new PCs, so even logging in as admin failed to find the files, for the simple reason they'd never entered the vault and thus weren't even in 'private state'.)

Actions

S. Casale @ Barrie Turner on Nov 6, 2018 10:08 AM

Something to note:

If your network fluctuates a lot due to traffic and you are saving a large amount of files, the file may be saved proper into the vault local folder, but not to the database and in the vault itself.

We have this issue regularly for just saving and checking in singular files, IT gets to it when they do.

Actions

7 Replies

Charley Saint Dec 12, 2013 5:04 PM
Mark Correct
Correct Answer
Alexandra,

This was a problem in EPDM 2012, I thought it was resolved but the SPR (646713) says it's still open. Here's the workaround from there (it's not terribly helpful):

Workaround: Use "save" instead of "save as" when saving a new assembly or drawing. A dialog shows where you can select "do not save read-only documents" to avoid the extra warning dialogs showing up. New file will be added correctly. For files that ended up local, browse to the file in Explorer, right-click (RMB), Add to File Vault, reopen in SolidWorks and resave if needed. Note: Same proplem can happen if making assembly or drawing from files opened in older SW format.
Like • Show 1 Like1
Actions
- Alexandra P. Spaulding @ Charley Saint on Dec 12, 2013 5:10 PM
  Mark Correct
  Correct Answer
  Charley,
  
  Thank you for your prompt response. Do you know if this issue has been resolved in EPDM 2013/14? We're currently using PDM 12 with SP2, and are trying to hedge our bets about UGing to PDM 13 or wait for PDM '14's SP 2 release, then UG.
  
  Thank you,
  Alexandra
  Like • Show 1 Like1
  Actions
  - Charley Saint @ Alexandra P. Spaulding on Dec 12, 2013 6:51 PM
    Mark Correct
    Correct Answer
    Alexandra,
    
    I checked the KB again but couldn't find anything that said it was fixed, but I'm fairly certain it was as I haven't heard anything about it in a while. I'd say it was probably fixed in 2013 sometime.
    Like • Show 1 Like1
    Actions
  - Barrie Turner @ Alexandra P. Spaulding on Nov 6, 2018 7:57 AM
    Mark Correct
    Correct Answer
    I had this today with PDM Pro 2018. I couldn't use the 'Save' workaround Charley mentioned as the files were created outside the vault environment. I'm pretty sure Hector's notes could be rolled into a strategy to stop it happening again.
    Like • Show 1 Like1
    Actions
Hector Baezs Dec 19, 2013 12:36 PM
Mark Correct
Correct Answer
Alexandra,

I manage the PDM for our company, and I have come across this same issue or a similar one.
We do a save as and not all files are added into the vault.

I found that in one of these occurrences, the assembly that is being saved had a component open in a different window, and when SolidWorks goes to save that assembly, it tries to save the component as well. If write capabilities are not allowed on the component then the assembly fails to save into the vault, and exists as a local file only.
My solution to this issue is to close the component and attempt the re-save.
If that fails, then save out of the vault and then back in.

After this, the issue is usually solved for me.
Like • Show 2 Likes2
Actions
- Barrie Turner @ Hector Baezs on Nov 6, 2018 7:49 AM
  Mark Correct
  Correct Answer
  Thanks for confirmation of my initial findings. Though I'm not about to test this I can confirm I saved-as and had the hidden files issue today, using PDM Pro 2018. It seems I set myself up for failure by opening all the read only parts' save dialogues then dismissing them all individually. The only way is to cancel the first save without opening the dialogues. (Yes, I'm failing to make this clear, sorry.)
  
  (I ensure all our users have hidden files hidden after setting up new PCs, so even logging in as admin failed to find the files, for the simple reason they'd never entered the vault and thus weren't even in 'private state'.)
  Like • Show 1 Like1
  Actions
  - S. Casale @ Barrie Turner on Nov 6, 2018 10:08 AM
    Mark Correct
    Correct Answer
    Something to note:
    If your network fluctuates a lot due to traffic and you are saving a large amount of files, the file may be saved proper into the vault local folder, but not to the database and in the vault itself.
    
    We have this issue regularly for just saving and checking in singular files, IT gets to it when they do.
    Like • Show 1 Like1
    Actions

Issue with SAVE AS .sldasm files into the vault

Outcomes

Related Content

Recommended Content