has anybody seen the problem of the system being unable to create a journal file and unable to use the backup feature on SW '08 SP 0.1 - 2.1 on Vista 32 bit?
Generally you get that message when there is already a SolidWorks session running. Next time it happens, bring up your Task Manager and see if there aren't two session running. I've had times where SolidWorks didn't fully shut down.
The engineer that keeps having this problem sees it even when he first starts up in the morning. The error message says the same thing but I can't see a way that SW would be running after a cold restart.
By default SolidWorks will write the journal file in the location specified by:
HKEY_CURRENT_USER\Software\SolidWorks\SolidWorks nnnn\ExtReferences\SolidWorks journal folders
In SolidWorks 2007 this key is:
HKEY_CURRENT_USER\Software\SolidWorks\SolidWorks 2007\ExtReferences\SolidWorks journal folders
If this is unset when SolidWorks starts then the default location will be used:
{User profile}\Application data\SolidWorks
on a standard computer this would be:
C:\Documents and settings\%User Name%\Application data\SolidWorks
If running the copy settings wizard then this key is part of the copied registry and may be set to an inappropriate location This issue has been identified and reported to the development team on SPR#364811 ("Admin Director Workflow causes the journal file to be set to the wrong directory").
Please check the settings of this key in the user's installation and verify that each user has a separate location set. Verify that the users have full control over the journal file in the specified location.
I've seen this problem when the user is new to SW and doesn't realise that it takes quite a while for SW to load after the splash screen's brief appearance; they see no "Eggtimer" and nothing seems to be happening, just the usual pointer and the desktop, so they try again and SW obligingly starts another instance.
I think that this is something that the software writers should trap and maybe ask if the user really want's to run a second instance, but most don't bother!
Trevor Clarke. (R & D) Scientific Instruments.Somerset. UK
