To put it briefly: We have 3 solidworks workstations on our site, 2 Pro and 1 Prenium.
I did all the configuration of solidworks as well as smartproperties on my workstation with all the links to network files where the access paths are completely identical.
I saved my configs (I'm in PRO) and I sent them in the prenium.
Well it seems that you have a second solidworks open on the sly. You should look at the processes that run in your task manager (if you go from the pro version to the premium version on the same workstation, Solidworks sometimes takes a little time to close everything ... even when nothing is on the screen anymore!)
As stated in the message, there is another SolidWorks assignment that is started.
This sometimes happens, even if you close SolidWorks it remains running.
To fix it, press CTRL+SHIFT+ESC to enter the task manager and kill the SolidWorks task that is too much. Kill all the tasks to be sure and restart SolidWorks.
Then you go to: HKEY_CURRENT_USER\Software\SolidWorks\SOLIDWORKS 2015\ExtReferences
On the right, you search: SolidWorks journal Folders, you double click and you check that the path entered here is indeed a path that exists and in which you have write rights.
If not, you modify it (with SolidWorks closed)
If everything is ok but you still get this message, it's probably because a sldworks.exe process is blocked in the task manager process site
that's what "mcordero" is, the "SolidWorks journal Folders" points to rmon C:, but how can I make this location stay on the C: of each user because I don't think you can make a folder on the network and that everyone uses this file at the same time.
Each one must have a unique file for each position.
The simplest, you close Sw and delete: "solisdworks journal folder" on this computer. When sw is launched, this key will be automatically recreated with the value that is fine.
Mick
Since you have copied the settings from a "A" extension to import them to a "B" extension, there is a good chance that you have paths that still point to folders that do not exist on this extension B.
In the registry, check all the string values of the hive: "ExtReferences", and correct (or delete) as needed.
Then, remember to make a backup of the settings on this workstation B just in case;)
I had already anticipated, all the paths are on the network and are all the same for all the workstations except the one in the log that I didn't know, but I didn't think there would be this kind of "bug" because I thought that saving the settings allowed you to be reinstalled on any workstation without worrying about this kind of workstation. path.