Error saving .slp file after inference

[bancroftg]

Inference ran successfully and I was able to export the analysis as CSV files. Error saving .slp file after inference:

2024-12-11T15:32:43.242ZE [4152:ShellIpcClient] shell_ipc_client.cc:141:Connect Can't connect to socket at: \.\Pipe\GoogleDriveFSPipe_eisch_shell
2024-12-11T15:32:43.243ZE [20588:ShellIpcClient] shell_ipc_client.cc:141:Connect Can't connect to socket at: \.\Pipe\GoogleDriveFSPipe_eisch_shell
2024-12-11T15:32:43.243ZE [20588:ShellIpcClient] shell_ipc_client.cc:631:operator() Failed to connect to the server: NOT_FOUND: Can't connect to socket at: \.\Pipe\GoogleDriveFSPipe_eisch_shell [type.googleapis.com/drive.ds.Status='UNAVAILABLE_RESOURCE']
=== Source Location Trace: ===
apps/drive/fs/ipc/shell_ipc_client.cc:142

I've attempted to 'save as' and change the file name, but this results in the same error.

• OS:
  • Windows 11
• Version(s):
  • SLEAP v1.3.3
• SLEAP installation method:
  • Conda from package

[eberrigan]

Hello @bancroftg,

The error message indicates that this is an issue with your computer's connection to google drive and not sleap. Please try to save the file in another location on your computer that is not on google drive.

If you do want to save your file on google drive, troubleshoot your connection to google drive and then try to save once you are able to work with your files on the drive.

Here are some suggestions from ChatGPT:

The error messages indicate that Google Drive File Stream (now known as Google Drive for desktop) is experiencing a problem connecting to its internal communication socket. Here's a breakdown of what it means and possible steps to resolve it:

---

Key Details:

1. Socket Connection Failure:

   • The error Can't connect to socket at: \\.\Pipe\GoogleDriveFSPipe_eisch_shell implies that the application is unable to establish a communication link via a named pipe, which is a mechanism for interprocess communication on Windows.

2. UNAVAILABLE_RESOURCE Error:

   • This typically indicates that a required resource (in this case, the named pipe or related service) is not available or running.

3. shell_ipc_client.cc Errors:

   • These errors originate from the code handling the Google Drive File Stream client’s internal shell IPC (inter-process communication) for file system operations.

---

Why This Happens:

• The Google Drive desktop application may not be running or functioning correctly.
• The named pipe (GoogleDriveFSPipe_eisch_shell) could be blocked or deleted due to:
  • A misconfigured or corrupted Google Drive installation.
  • A permissions issue or a conflict with other software (e.g., antivirus, firewall).
  • Windows system issues affecting named pipes.

---

What You Can Do:

1. Restart Google Drive for Desktop:

   • Close and restart the Google Drive application from the system tray.
   • If it’s not visible, ensure it is running by searching for Google Drive in the Start menu.

2. Restart Your Computer:

   • This ensures any temporary pipe connection issues or resource locks are cleared.

3. Check Permissions:

   • Make sure the current user has permission to access the Google Drive folder and its associated processes. Run the application as an administrator.

4. Reinstall Google Drive:

   • Uninstall and reinstall Google Drive for Desktop to repair any corrupted files or configuration.

5. Check Antivirus or Firewall:

   • Ensure your antivirus or firewall is not blocking the Google Drive app or its internal components.

6. Clear Google Drive Cache:

   • Go to the Google Drive cache directory:

     C:\Users\<YourUsername>\AppData\Local\Google\DriveFS
     

   • Rename or delete this folder to force a refresh.

7. Run a System File Check:

   • Open a command prompt as an administrator and run:

     sfc /scannow
     

   • This checks for and fixes any corrupted system files.

8. Check for Windows Updates:

   • Make sure your system is fully updated, as system-level bugs can occasionally cause IPC or resource issues.

---

Further Diagnosis:

If these steps do not work:

• Check Logs: Google Drive keeps logs in C:\Users\<YourUsername>\AppData\Local\Google\DriveFS. Reviewing these logs may provide additional clues.
• Contact Google Support: If the issue persists, Google Drive’s support team can provide more targeted help.

[roomrys]

Hmm... while the text provided by the user does seem to indicate a connection error, we also ran into this in:

• Error saving: Unable to create attribute (object header message is too large) #2117

and with the context provided in that discussion, it seems to be related to the size of data we attempt to save to the metadata group. We will keep this issue closed to avoid duplicates, but please follow #2117 for updates.