On Windows, if your project folder is on a network share (a UNC path such as \\server-name\...) and its owner doesn’t match the user you’re logged in as, you may get the following error when you open a project, publish a note, or refresh data.
Error code: 128
Error: Command failed: git log -n 1 --pretty=format:%n%H%n%s%n%cD
fatal: detected dubious ownership in repository at '//<server name>/<user name>/exploratory/projects/<project ID>'
'//<server name>/<user name>/exploratory/projects/<project ID>' may refer to a non-local directory
To add an exception for this directory, call:
git config --global --add safe.directory '%(prefix)///<server name>/<user name>/exploratory/projects/<project ID>'
Cause
This comes from a safety check added in Git 2.35.2 (the fix for CVE-2022-24765). When the owner (SID) of a folder on the network share doesn’t match the Windows user you’re logged in as, Git refuses to trust the repository in that folder, and git log fails with error code 128.
Exploratory uses Git to manage project history, so the operation stops at that point. Depending on the file server’s settings, a folder’s owner may differ from the user you’re logged in as.
Solution
Register all folders as trusted repositories (safe.directory) in your Git configuration.
- Open Git Bash. Git must be installed to use Exploratory, and installing Git on Windows normally installs Git Bash along with it.
- Run the following command.
git config --global --add safe.directory "*" - Reopen the project in Exploratory.
Specifying "*" turns off the ownership check for every folder, so use it only in a trusted environment such as your company’s file server.
If your project folder is on a local drive (for example, C:\Users\<user name>\.exploratory), and you created or imported the project yourself, the owner normally matches, so this error doesn’t occur.