Problem assembling parts on a network

Hello, we have a PC with a SOLIDWORKS 2017 license.

This PC is connected to an internal company network.

We carry out our assemblies on this network in order to facilitate their accessibility by other stations.

After creating my parts in a folder on this network, I created an assembly from them in the same folder.

I save my assembly... I re-open it 10 seconds later, and there, "impossible to find the file for the component to complete the operation".

The paths to all my pieces have been lost... I undo the deletion on each item, the software finds them directly in the folder in question.

I just have to click on "open" to make them re-appear in the assembly.

I save the assembly with the paths found. I close it, open it again and then... The same thing happens. All paths are lost.

We tried to open this same assembly on another PC with another SOLIDWORKS 2017 license. And there, no problem, the parts are found.  The assembly is correct

I tried to do a pack and go in another folder on the same network.

Same thing, the paths of the pieces get lost.

I rebuilt this same assembly locally on my hard drive "C".

The assembly behaves correctly, my parts are found when opening my assembly.

I tried to create other parts on the network and create the assembly on my desktop: files not found.

I tried to create the assembly on the network and create the parts on the desktop: the assembly behaves well.

PS: we replaced this PC during this malfunction, thinking it came from him but same thing. The problem persists.

We also tried to swap the SOLIDWORKS licenses between the problem PC and the no problem PC, but the fault remains on the problem PC.

I think I haven't forgotten anything in the description of my problem and my various attempts to solve it.

If anyone has ever encountered this kind of thing and knows how to solve it, I'd be happy to know the solution.

Hello

Have you looked at the rights of the problem PC on the network?

Hello

Wouldn't you have disconnections which would have the effect of making you lose the paths of the pieces.

Cdt.

Fred

Hello, I don't have a problem disconnecting.

The rights of the PC on the network, I didn't know it.

Other tests:

We put the problem PC instead of the non-problem PC in order to find out if it came from the link between my wall network socket and our server. The result is inconclusive: the problem is persistent.

After putting my PC back in its location, I opened an old assembly (dating back a few years) on the network. And there, all the pieces were displayed without any problem. I then inserted a "canister" part made in a hurry on this assembly. I saved it and re-opened it, and there BINGO all the coins are nowhere to be found.

I don't really know what to think about it....

 

Hello

Have you found the solution to date?
I have exactly the same problem

Kind regards

Hello
If the rights are defined according to the ip or the name of the pc, it will have the same problem regardless of its location on the network.
I'm leaning towards a restriction of rights or maybe at the level of the firewall of the problematic pc.

1 Like

In reality, I work locally with documents on a drive synchronized live. So no passage of the lights by Solidworks. In addition, offline I have my parts locally that I can open but the assemblies jump each time I reopen.
I'm leaning more towards a path problem but I can't find the solution.

Hello
When you say "a synchronized drive", is it a OneDrive-like mechanism?
I'm not sure SW works perfectly with this type of environment.

Yes, that's right, it's a Google drive.

I am aware that my editing is complicated and wobbly.
I'm using SW 2017 on Win 7 on Parallels Desktop 11 on a macBook Pro 2012.
With a shared drive as a server (I'm not an owner) that I duplicate on my personal drive and then synchronize on my computer.

Probably the most complex method that exists to make SW run.

But the problem I have is exactly the same as RomualdAlvarez who doesn't have the same configuration as me at all. I was hoping that this would be an easy to adjust SW or Win access setting.

Hmm Maybe the method you used to set up the drive isn't enough.
Try to take a look at this page if you learn anything there.
I would start by checking that the key is present in the register, because if you go to fetch it manually the path is valid, there is no guarantee that the loads operated by solidworks do not need a predefined path to the drive.

Well, this is only a hypothesis.

I'll take a look. Thank you for your help

Hello
My problem is indeed solved.
After changing my internal server, I didn't have any more problems.

1 Like

Is the path to the drive a classic windows path, especially with a drive letter?
If not, I'll try to create a network drive that points to the drive's directory.

1 Like

Hi all

I agree with @stefbeno on the fact of mounting a network drive that points to the drive-thru folder.

SW uses absolute paths to access files:
c:\mondosssier\myproject...

It is unable to manage the relative paths: .\myfolder\myproject...
(the 40 years and more of computer science will :joy:understand me)

This is the kind of path that we don't have access to if we use a live drive via the web for example.

When mounting this drive, Windows creates a drive: W:\myfolderdrive, then the sync software does the job... For SW it's transparent, he doesn't realize anything.

This could explain why SW no longer finds the assembly elements if it is opened from the drive and finds them when opening locally.

I hope I've been clear enough, have a good day.

5 Likes

Hello @a.eriaud

Well agree with you and it's even worse with DropBox.

By the way! Your explanation is very clear

Kind regards

PS: 50 years of computer science :joy:

Hello
We link a network disk to our PCs with offline files enabled.
This allows us to have our files locally off-network and that it synchronizes when we return.
No problem being several on it for a few years.

1 Like

Hello
We link a network disk to our PCs with offline files enabled.
This allows us to have our files locally off-network and that it synchronizes when we return.
No problem being several on it for a few years

Hello
Can we know a little more? :wink:

In fact, we add a "network location" pointing to a network folder which gives us a drive letter. Then we activate offline files for local assets in case of business travel.

3 Likes

I didn't know this function. I'm going to test that.
Thank you.
Nice day

Good to know, the network location can also point to a local folder on the machine.