main.workspaces does not exist error on Microsoft Surface 7 ARM64 Running WIndows 11 #1800

Closed
opened 2026-02-28 05:41:17 -05:00 by deekerman · 10 comments
Owner

Originally created by @myonlinematters on GitHub (Dec 8, 2024).

I am running AnythingLLM on a Microsoft Surface 7 ARM64 machine and am getting the same message: "Error: Invalid prisma.workspaces.create() invocation: The table main.workspaces does not exist in the current database." I have read the older issues - https://github.com/Mintplex-Labs/anything-llm/issues/1077 and #1170 - and they all relate to Linux. How do I fix this on Windows 11 on ARM64?

Originally created by @myonlinematters on GitHub (Dec 8, 2024). I am running AnythingLLM on a Microsoft Surface 7 ARM64 machine and am getting the same message: "Error: Invalid prisma.workspaces.create() invocation: The table main.workspaces does not exist in the current database." I have read the older issues - https://github.com/Mintplex-Labs/anything-llm/issues/1077 and #1170 - and they all relate to Linux. How do I fix this on Windows 11 on ARM64?
Author
Owner

@myonlinematters commented on GitHub (Dec 8, 2024):

I have gotten a little further on this.

  1. I checked node.js and npm. They are both on my machine with latest versions (node = v22.6.0, npm = 10.8.2) and working

  2. I added C:\Program Files (x86)\AnythingLLM\resources\backend\prisma to my path file.

  3. I then ran npx prisma init successfully with the response:
    ✔ Your Prisma schema was created at prisma/schema.prisma
    You can now open it in your favorite editor.

  4. I set the database URL in the .env file to
    DATABASE_URL="file:./anythingllm.db"

  5. I also checked in the schema.prisma file in the C:\Program Files (x86)\AnythingLLM\resources\backend\prisma directory and there is a model called workspaces, which I assume is main.workspaces. So it seems that the table is there.

Also on #3 - just in case - copied the schema.prisma file from the anythingLLM directory to c:\users\prisma directory just in case prisma was looking there. I ran 'npx prisma studio' and was able to open the schema, but it threw an error when trying to read the database tables.

Still did not work. Very frustrating.

@myonlinematters commented on GitHub (Dec 8, 2024): I have gotten a little further on this. 1. I checked node.js and npm. They are both on my machine with latest versions (node = v22.6.0, npm = 10.8.2) and working 2. I added C:\Program Files (x86)\AnythingLLM\resources\backend\prisma to my path file. 3. I then ran npx prisma init successfully with the response: _✔ Your Prisma schema was created at prisma/schema.prisma You can now open it in your favorite editor._ 4. I set the database URL in the .env file to DATABASE_URL="file:./anythingllm.db" 5. I also checked in the schema.prisma file in the C:\Program Files (x86)\AnythingLLM\resources\backend\prisma directory and there is a model called workspaces, which I assume is main.workspaces. So it seems that the table is there. Also on #3 - just in case - copied the schema.prisma file from the anythingLLM directory to c:\users<myuser>\prisma directory just in case prisma was looking there. I ran 'npx prisma studio' and was able to open the schema, but it threw an error when trying to read the database tables. Still did not work. Very frustrating.
Author
Owner

@timothycarambat commented on GitHub (Dec 11, 2024):

Answered this over email, but blowing away the desktop storage folder and opening the app again worked.

@timothycarambat commented on GitHub (Dec 11, 2024): Answered this over email, but blowing away the desktop storage folder and opening the app again worked.
Author
Owner

@myonlinematters commented on GitHub (Dec 11, 2024):

Sorry Tim for not getting to this sooner. Yes, I just deleted the storage folder in C:\Users<my_username>\AppData\Roaming\anythingllm-desktop (Windows 11) and then restarted AnythingLLM. It worked just fine.

@myonlinematters commented on GitHub (Dec 11, 2024): Sorry Tim for not getting to this sooner. Yes, I just deleted the storage folder in C:\Users\<my_username>\AppData\Roaming\anythingllm-desktop (Windows 11) and then restarted AnythingLLM. It worked just fine.
Author
Owner

@timothycarambat commented on GitHub (Dec 11, 2024):

No big deal it's not your responsibility! Just documenting it for anyone who finds this thread in the future.

@timothycarambat commented on GitHub (Dec 11, 2024): No big deal it's not your responsibility! Just documenting it for anyone who finds this thread in the future.
Author
Owner

@robbyteal commented on GitHub (Dec 23, 2024):

Hello, I am running into this error on my Thinkpad T14s Gen 6 (ARM) and getting the same error:

Error: Invalid prisma.workspaces.create() invocation: The table main.workspaces does not exist in the current database.

I also get this error on the first time setup: Failed to create workspace: undefined

I tried deleting:
C:\Users<USER>\AppData\Roaming\anythingllm-desktop
and specifically:
C:\Users<USER>\AppData\Roaming\anythingllm-desktop\storage
C:\Users<USER>\AppData\Roaming\anythingllm-desktop"Local Storage"

But after restarting the program I run into the same issue. I am using AnythingLLM as the LLM provider in case that creates a different case from the user above me.

image
image

@robbyteal commented on GitHub (Dec 23, 2024): Hello, I am running into this error on my Thinkpad T14s Gen 6 (ARM) and getting the same error: _Error: Invalid `prisma.workspaces.create()` invocation: The table `main.workspaces` does not exist in the current database._ I also get this error on the first time setup: _Failed to create workspace: undefined_ I tried deleting: C:\Users\<USER>\AppData\Roaming\anythingllm-desktop and specifically: C:\Users\<USER>\AppData\Roaming\anythingllm-desktop\storage C:\Users\<USER>\AppData\Roaming\anythingllm-desktop\"Local Storage" But after restarting the program I run into the same issue. I am using AnythingLLM as the LLM provider in case that creates a different case from the user above me. ![image](https://github.com/user-attachments/assets/59cabdbb-2477-4d99-857f-8e782a4cc5ce) ![image](https://github.com/user-attachments/assets/b1380fb8-8724-4f1d-a99f-302754ac64a6)
Author
Owner

@robbyteal commented on GitHub (Dec 23, 2024):

Solved my issue, I reinstalled the ARM copy one more time before trying x64 and this time selected my specific Windows user instead of "Install for all users" and now I no longer have the error when creating workspaces. I did not need to delete the storage either.

@robbyteal commented on GitHub (Dec 23, 2024): Solved my issue, I reinstalled the ARM copy one more time before trying x64 and this time selected my specific Windows user instead of "Install for all users" and now I no longer have the error when creating workspaces. I did not need to delete the storage either.
Author
Owner

@timothycarambat commented on GitHub (Dec 28, 2024):

Solved my issue, I reinstalled the ARM copy one more time before trying x64 and this time selected my specific Windows user instead of "Install for all users" and now I no longer have the error when creating workspaces. I did not need to delete the storage either.

This is indeed the issue! The Arm64 version right now has issues if the user installs as admin - we will probably remove that option in the ARM64 builds until it is patched. And if it happens it will basically break the whole app and make it unusable since the local DB cannot be used at all.

@timothycarambat commented on GitHub (Dec 28, 2024): > Solved my issue, I reinstalled the ARM copy one more time before trying x64 and this time selected my specific Windows user instead of "Install for all users" and now I no longer have the error when creating workspaces. I did not need to delete the storage either. This is indeed the issue! The Arm64 version right now has issues if the user installs as admin - we will probably remove that option in the ARM64 builds until it is patched. And if it happens it will basically break the whole app and make it unusable since the local DB cannot be used at all.
Author
Owner

@pyx26266 commented on GitHub (Jan 21, 2025):

Solved my issue, I reinstalled the ARM copy one more time before trying x64 and this time selected my specific Windows user instead of "Install for all users" and now I no longer have the error when creating workspaces. I did not need to delete the storage either.

@robbyteal
How did you get the option to install as user? I’m also having T14s 6th gen. When I open the installer it directly goes to install step.

@pyx26266 commented on GitHub (Jan 21, 2025): > Solved my issue, I reinstalled the ARM copy one more time before trying x64 and this time selected my specific Windows user instead of "Install for all users" and now I no longer have the error when creating workspaces. I did not need to delete the storage either. @robbyteal How did you get the option to install as user? I’m also having T14s 6th gen. When I open the installer it directly goes to install step.
Author
Owner

@robbyteal commented on GitHub (Jan 22, 2025):

I was Version 1.7.1 ARM if that helps.


From: Aman Kumar @.>
Sent: Tuesday, January 21, 2025 8:48 PM
To: Mintplex-Labs/anything-llm @.
>
Cc: Robert Hamblet @.>; Mention @.>
Subject: Re: [Mintplex-Labs/anything-llm] main.workspaces does not exist error on Microsoft Surface 7 ARM64 Running WIndows 11 (Issue #2771)

Solved my issue, I reinstalled the ARM copy one more time before trying x64 and this time selected my specific Windows user instead of "Install for all users" and now I no longer have the error when creating workspaces. I did not need to delete the storage either.

@robbytealhttps://github.com/robbyteal
How did you get the option to install as user? I’m also having T14s 6th gen. When I open the installer it directly goes to install step.


Reply to this email directly, view it on GitHubhttps://github.com/Mintplex-Labs/anything-llm/issues/2771#issuecomment-2606288216, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASU3JXMH5YSUL5ZWCRGPCDD2L4PJPAVCNFSM6AAAAABTHQTPAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBWGI4DQMRRGY.
You are receiving this because you were mentioned.Message ID: @.***>

@robbyteal commented on GitHub (Jan 22, 2025): I was Version 1.7.1 ARM if that helps. ________________________________ From: Aman Kumar ***@***.***> Sent: Tuesday, January 21, 2025 8:48 PM To: Mintplex-Labs/anything-llm ***@***.***> Cc: Robert Hamblet ***@***.***>; Mention ***@***.***> Subject: Re: [Mintplex-Labs/anything-llm] main.workspaces does not exist error on Microsoft Surface 7 ARM64 Running WIndows 11 (Issue #2771) Solved my issue, I reinstalled the ARM copy one more time before trying x64 and this time selected my specific Windows user instead of "Install for all users" and now I no longer have the error when creating workspaces. I did not need to delete the storage either. @robbyteal<https://github.com/robbyteal> How did you get the option to install as user? I’m also having T14s 6th gen. When I open the installer it directly goes to install step. — Reply to this email directly, view it on GitHub<https://github.com/Mintplex-Labs/anything-llm/issues/2771#issuecomment-2606288216>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASU3JXMH5YSUL5ZWCRGPCDD2L4PJPAVCNFSM6AAAAABTHQTPAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBWGI4DQMRRGY>. You are receiving this because you were mentioned.Message ID: ***@***.***>
Author
Owner

@timothycarambat commented on GitHub (Jan 22, 2025):

@robbyteal This was patched in v1.7.2-r2, if you install the app "for all users" instead of "only me" this issue will occur. We removed it from the installer to prevent people form doing this now.

@timothycarambat commented on GitHub (Jan 22, 2025): @robbyteal This was patched in v1.7.2-r2, if you install the app "for all users" instead of "only me" this issue will occur. We removed it from the installer to prevent people form doing this now.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/anything-llm#1800
No description provided.