Error message when starting Solidworks

Hello, for a few days I have had an error message when launching solidworks:

Where can the problem come from? knowing that:

This message is always displayed when launching SolidWorks even in the morning after the computer starts (so there are no other SolidWorks sessions in progress)

The servers were changed during the holidays.

 

 

Hello 

In the task manager, go see in Process if there is a Solidworks lying around. If there is one, do "Stop the process"

 

Dimitri

4 Likes

Hello

I agree with Dimitri. It is enough that Solidworks crashed a few days ago and it is not properly stopped. There may be a Solidworks phantom open.

3 Likes

Hello

If you don't have any other solidworks process running then it may come from the write rights on the folder where this log file is saved, see:

http://help.solidworks.com/2016/french/solidworks/sldworks/c_preventative_file_management.htm

Kind regards

3 Likes

Hello

If none of this works, you can try changing the SOLIDWORKS journal folders variable data from the regedit as shown in the link. Deleting the data seems to be the solution for many people.

https://forum.solidworks.com/thread/23679

2 Likes

Hello

Try to:

- Delete the log file

C:\Documents and Settings\<username>\Application Data\SolidWorks\SolidWorks <version>

- Check in the registry where it is saved (write rights)

HKEY_CURRENT_USER > Software > SolidWorks > SolidWorks <version> > ExtReferences.

http://help.solidworks.com/2011/french/SolidWorks/sldworks/LegacyHelp/Sldworks/Fundamentals/SolidWorks_Journal_File.htm

Do you work with floating licenses?

If so, I had the same problem.

If you have borrowed a license and the server has been updated in the meantime, the license manager no longer recognizes the license in use...

Unable to borrow or return a license.

In short, a ticket to the hotline and they pay it to you remotely.

Hello

Thank you for your answers, 

There was no phantom process and I have write rights to the folder where this log file is saved.

I fixed the problem by modifying the SOLIDWORKS Journal Folders variable in the registry

 

Cdt