Reasons and Solutions for Solidworks Journal File Could Not Be Created Warning

Solidworks Journal File Could Not Be Created
Solidworks Journal File Could Not Be Created

The actions you do while using SOLIDWORKS are documented in a text file called the journal file. This file is particularly useful for developing SOLIDWORKS Basic macros or SOLIDWORKS API programming tools.

SOLIDWORKS generates a journal file with the name swxJRNL.swj in the following place when you launch it: C:\Users\current_user\AppData\Roaming\SOLIDWORKS\SOLIDWORKS 20XX. The 20xx refers to the Solidworks version.

If a journal file already exists and isn’t being utilized in the destination folder when you create a new journal file, SOLIDWORKS copies the current file to swxJRNL.BAK. The current session is represented by swxJRNL.swj, and the previous session is represented by swxJRNL.BAK.

When attempting to utilize Solidworks, the following notice may appear:

Journal file couldn't be created message

The Reasons and Solutions for “Solidworks Journal File Could Not Be Created” Warning

Reason 1: SOLIDWORKS sessions that are running concurrently.

The most typical source of the error notice is because two SOLIDWORKS sessions are operating concurrently. The warning notice will pop up when you start the second or later session because the first SOLIDWORKS session writes to the journal file and the second SOLIDWORKS session cannot overwrite the same journal file.

To verify that there isn’t another instance of SOLIDWORKS running, locate SLDWORKS.exe in the Task Manager’s Details tab. Restart SOLIDWORKS after completing the process.

Reason 2: Invalid Location

You will probably encounter a “journal file could not be generated” issue if you were unable to locate the path provided for SolidWorks Journal Folders or if it differs from the usual — C:\Users\[current user]\AppData\Roaming\SOLIDWORKS\SOLIDWORKS 20XX.

This typically occurs when a.sldreg file from another machine, especially one with a different Operating System, is loaded in using the Copy Settings Wizard. A typical deviation from the norm is to show something other than the currently logged-in user as the “[current user]”.

If this problem is brought on by an incorrect SolidWorks Journal Folder placement, do the following actions to fix it:

  1. Close all active SOLIDWORKS sessions.
  2. Launch the Windows registry. You may access regedit by clicking the Windows button and typing regedit, then selecting regedit.exe from the search results.
  3. Navigate to ExtReferences under HKEY_CURRENT_USER\Software\SolidWorks\SOLIDWORKS 20XX\ExtReferences.
  4. Look for the SolidWorks Journal Folders key.
  5. Double-click this key to remove its contents.
  6. After selecting OK, shut off the Registry Editor.

Registry editor extreference under hkey current user

Reason 3: Restricted Access

If you don’t have the proper access rights to the place where SOLIDWORKS is configured to write the journal file, this error may also occur.

It is not possible to see or modify the journal file location in SOLIDWORKS 2007 or later editions. Open the Registry entries and navigate to the following location to see where SOLIDWORKS is keeping the journal file:


Locate the key titled “SolidWorks Journal Folders” in ExtReference. The path to the directory where SOLIDWORKS will attempt to create journal files is the value of this key.

Locate key tile solidworks journal folders

Browse to the location in Windows File Explorer and store a test file there to make sure you have the necessary rights. You may create a new.txt file by right-clicking on the folder and choosing New > Text Document.

If you are unable to perform this, you have identified the issue. Speak with your internal IT department about gaining full access to this folder or changing the value of SolidWorks Journal Folders to a new place where you do have read-write access.

NB: The Windows registry is used to address the last two causes. Your computer’s regular operation depends on the data in the Windows registry, which may be corrupted by removing or altering the incorrect entries. I firmly advise against attempting to change your registry without first consulting your internal IT Technical Support.