Folders still held hostage by SW after it's closed?

[brrian]

I've experienced this often, and another user has just come to me about this.

I work over a network. Typically I work inside a single folder which holds all project files (parts/assemblies/drawings). On occasion I've realized that I named the folder incorrectly, and I want to change it. If I attempt to rename with SolidWorks open, it almost never works...understandable. But I've noticed that even after SW has been closed, I still can't rename it--it says that it's still being used by 'another person or program.' I have to reboot my computer to break the link. Any ideas on why that may be--could it be my computer that's still accessing the folder?

Brian

 

[SBaugh]

1) Check your Processes to make sure SW isn't not running in the background.
2) I have seen this before and sometimes I just have to wait a little longer after I have closed SW... like maybe 5 minutes, to ensure all SW has Cached out.
3) If you close SW make sure your Memory is caching out, if not then SW is not closing, this could be either because of Windows or a repair to your SW needs to be performed.
4) If you have more then one person seeing this, if could be a network issue. Try something locally and see if you get the same result.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376

 

[brrian]

What do I look at to see if/how memory is caching out--is it the pagefile in Windows Task Manager?

 

[SBaugh]

Task Manager - Under Performance. You are "X" memory when SW is opened. and when you close it "X" memory should drop out and go way lower then what it is when SW is open.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376

 

[brrian]

Got it... thanks. It appears to be caching out just fine.

I just performed a quick test, & I didn't see the same problem locally. I'll test once more and then go after the network guru--the problem may indeed be the network.

Thanks for the quick response...

Brian

 

[phreaq]

I know this may not be the answer, but I'm amazed at how many people are in other peoples folders at my work. I am the sole designer on a certain project, but other people still have their hands in my folders, which would prevent any renaming.

 

[ElectroMatt]

I'm the sole drafter/designer at my company. I used to have the same problems with files being locked even after Solidworks was closed, amongst other problems.

I finally convinced my IT guy to let me move all my solidworks files back to my local drive and back up from there. Presto, no more locked files and my crashes have decreased VERY dramatically. I'm lucky if it goes down once a day, versus every couple hours or so. I've been pushing it pretty hard this past week with a thousand-part assembly going through a photoworks rendering process.

While this is not much consolation for those in a multi-user environment, there is hope for single-users if you can work out a backup strategy for these very-important files.

Solidworks does not seem to play well with networks.

 

[SBaugh]

Your problem was Item 4 on my list then... Networks can be hazardous when working on or over them. But it will also vary on how much power your IT invokes on the users of the network.

If you IT wants it to be on the server, then you need to look at PDMworks as a vialbe option.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376

 

[afb66t9]

Solidworks saves and stores information on the RAM which needs to be cleared before renaming any folders. This usually involves closing down all SW files and shutting down SWorks.

 

[SBaugh]

SW also writes TEMP files across the network when you are working on one. Network traffic can cause havoc on SW.

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376