Incompatible Database [Mac M1]

[xSikes]

I am as far as I can connect to the tunnel and save the config file.
DR Project Server 17.3 says "incompatible" on the database.

In DRS 17.3.1 says Failed to create data base even though it's in PS.

"... database error for pizza : relation "public.Sm2SysIdEntry" does not exist
LINE 1: ...stSeen","ClientAddr","UserDefinedClientName" FROM public."Sm...
^

... database error for pizza : current transaction is aborted, commands ignored until end of transaction block"

[xSikes]

Also just to add I had to install Anaconda and spider separate to get all this to work. Not sure if that causes anything.

[DesertCookie]

Are you sure pizza doesn't already exist? I'd install something like pgAdmin and connect to the local Resolve databases using the following defaults, then removing pizza and trying to re-create it:

• IP: localhost or 127.0.0.1
• User: postgres
• Password: DaVinci

Furthermore, I've seen the error public.Sm2SysIdEntry pop up when using a custom user to access the Resolve database that is not postgres. The custom user needs to have all the same permissions as postgres and also be a super user.

Both of the above are easy fixes in pgAdmin.

[xSikes]

Are you sure pizza doesn't already exist? I'd install something like pgAdmin and connect to the local Resolve databases using the following defaults, then removing pizza and trying to re-create it:

• IP: localhost or 127.0.0.1
• User: postgres
• Password: DaVinci

Furthermore, I've seen the error public.Sm2SysIdEntry pop up when using a custom user to access the Resolve database that is not postgres. The custom user needs to have all the same permissions as postgres and also be a super user.

Both of the above are easy fixes in pgAdmin.

Pizza did not exists before. What works is creating the database in project server and signing in with the "postgres" profile and it works in mission control.

I've done the easy fixes in pgAdmin but another problem comes up like not allowing backend access and I can see the user ping the server as well but won't allow permission to connect from a remote location.

At this point nothing seems to work correctly, so many work arounds... I've only got this working once in my own network (two subnets) but doesn't work again after a restart.
Next step is trying it in a VM.