cal.com icon indicating copy to clipboard operation
cal.com copied to clipboard

Bug on installation

Open 89itworld opened this issue 1 year ago • 5 comments

Hello Team,

I hope you are doing great! I found a bug while I am installing version 3.1.5 of cal. I am facing prisma.schema not found error, even though the database has been migrated.

I am using self-hosting.

Error: PrismaClientInitializationError

I am also attaching the screenshot. Please find the screenshot.

Screenshot 2023-08-02 at 1 51 21 PM

Thanks Manoaj

89itworld avatar Aug 02 '23 08:08 89itworld

can you try this? https://cal.com/docs/introduction/quick-start/self-hosting/upgrading

PeerRich avatar Aug 03 '23 08:08 PeerRich

Hi @PeerRich Thanks for responding, but I have already did it multiple times, please check my error, it is schema.prisma could not be found while database has been migrated.

89itworld avatar Aug 03 '23 12:08 89itworld

I am also getting same error

Vinod-Mane3021 avatar Sep 08 '23 18:09 Vinod-Mane3021

Same when installing this project.

Yangthemob avatar Jan 31 '24 09:01 Yangthemob

I got this too.

also tried yarn clean, tried reinstalling db and configs. nothing fix it.

`yarn workspace @calcom/prisma db-migrate

Environment variables loaded from .env Prisma schema loaded from schema.prisma Datasource "db": PostgreSQL database "cal_db", schema "public" at "localhost:5432"

Already in sync, no schema change or pending migration was found.

✔ Generated Prisma Client (v5.4.2) to ./node_modules/@prisma/client in 793ms ✔ Generated Zod Schemas (0.5.4) to ./zod in 900ms ✔ Generated Kysely types (1.8.0) to ./../kysely in 1.62s ✔ Generated Prisma Enum Generator to ./enums/index.ts in 250ms`


SOLVED:

I updated prisma client in package.json to latest version, by removing this update and changing my package.json to default package.json in repo, problem solved.

Katerou22 avatar May 18 '24 09:05 Katerou22