Delivery Error - PGS-220000 PostgreSQL : permission denied for relation nmssuppressionaddress

[#1]

Hi,

I try to create a delivery and I get this error:

"PGS-220000 PostgreSQL error: ERROR: permission denied for relation nmssuppressionaddress"
I try searching the forums but no clue. Please help.

Thank you,

Rumm

[#2 · Accepted solution]

Hi Rumm,

Are you on- premise setup or it is hosted by Adobe.

As per the error in screenshot, it seems that the delivery is failing due to the missing Md5Digest   installed on your Postgres database.

Usually occurs when extension "pgcrypto" not installed. This Extension have to be created once per database. And the pgcrypto extension is special as it can only be created by the database superuser (normally postgres).

If you are on on premise setup , I would suggest you to please ask DBA at your end to further look into this concern/Error.

You also might find below links helpful :

https://www.postgresql.org/docs/9.1/static/sql-createextension.html

https://www.postgresql.org/docs/9.4/static/pgcrypto.html

If environment is hosted by Adobe , You can raise a support ticket with Adobe Campaign Support.

Hope this helps in resolving the issue

[#3]

They have provided the permission so now it works. Thank you everyone.

Rumm

[#4]

Hi shrawans3150030,

Thank you for your suggestion. This is hosted by Adobe so I have requested for a support ticket. Will update the result soon.

[#5]

Thank you kapilsharma0101. I tried deactivating the rule but the error is still the same...

[#6]

In that case please try removing the "Exlude Domains" rule from the Typology selected in the Delivery and try to send the delivery again.This may work as you are facing issue with this schema only.

[#7]

Hi kapilsharma0101,

The user is the administration user. And the schema definition is like this (see picture below). The delivery used to working fine. I did not change or create any extension from this schema.

[#8]

Hi Rumn,

Please check the Validations in the Schema Definition of nmssuppressionaddress schema.

I am not sure but it may be the reason that the User by which you have logged in AC, and trying to send the delivery, doesn't have rights to access to the given schema.