1319
Views
12
Comments
Solved
publish extension. "You don't have enough permissions over the database connection"
Question

Hi,

I'm using integration studio 10.0.303.0.

I' ve created 2 external entities (Java Stack, Oracle database) based on 2 views.

When I want to publish the extension I get the following error during step 5 (Uploading Extension) of the publishing process:

"You are not allowed to publish this extension. You don't have enough permissions over the database connections that own the following external entities: TMS001_CUSTOMER_UPDATE, TMS001_CUSTOMER_SHOW."

Could anybody help me out?

Best regards,

Matthieu de Graaf


2020-10-15 10-24-31
Miguel Seabra Melo
Solution

Hi Matthieu,

I presume you need to grant the person that first publishes the extension access to that connection. In Service Center, check out Administration->Users->(select the user)->Database Connections and set that user to "Full Control" for that connection (even if temporarily).

Subsequent publishes should NOT need this access anymore.

Cheers.

UserImage.jpg
Matthieu de Graaf

Hi Miguel,

Thanks for your swift reply. However, after granting "full control" privilege, the error still occurs.


Could it be a firewall issue?

Cheers,

Matthieu

2020-10-15 10-24-31
Miguel Seabra Melo

Judging by the message text I don't think it's a connectivity problem, so I wouldn't say it's firewalls.

Have you logged off and back on with the user that is attempting the publish after changing his access? Some roles in the platform are only loaded on login.

UserImage.jpg
Matthieu de Graaf

Hi Miguel,

I couldn't find a  "Log of Button/Menu option. So I changed to another environment en switched back to the original environment.

The same error still occurs.

Regards,

Matthieu

UserImage.jpg
Matthieu de Graaf

Hi Miguel,

After all, it was a permission problem. After getting the Admin role everything worked ok.

Thanks for your answer.

Matthieu

2019-04-10 09-25-04
Aneesh

Matthieu de Graaf wrote:

Hi Miguel,

After all, it was a permission problem. After getting the Admin role everything worked ok.

Thanks for your answer.

Matthieu

Hi Matthieu,

I am also facing the same issue with few tables. I have added are round 50 tables and 3 tables are giving the same issue. What Admin role are you specifying here? (Service Center, Life Time or SQL Server)


UserImage.jpg
Rafael Vezzani

Hi Matthieu,

I am facing the same issue and I already have Full Control privilege. When you say "After getting the Admin Role", can you describe where exactly? Is it in the Service Center, Life Time, on SQL Server... ?

Thanks!
Rafael

UserImage.jpg
Matthieu de Graaf

Hi Aneesh,

To be honest I'm not sure anymore. At least it wasn't the SQL server admin role. I think it was ht LifeTime role. Our administrator had to give me full control on all applications.


Success,

Matthieu

2018-10-29 15-41-37
Kevin Swanson

We're having this same issue. I see there were two different bug fixes for this, the latest in 10.0.804.0.  We are currently on 10.0.820.0, and it's still happening. I know this has been marked as solved, but in my mind giving someone administrative access in Lifetime is not a solution.

Has anyone found another solution?


2019-04-10 09-25-04
Aneesh

Hi Kevin,

The issue with my case was, I was using the same connection string which was used by another database extn module. I wasn't having enough permission for that module, even if i am having the full control on the connection string. So whenever I am trying to refer a new table which is already being used in that other extn, I was not able to publish my extn for those specific tables.

The temporary solution was to create a new connection string and use that to add the tables. Meanwhile a case is already created to fix this bug.

Let me know if this helps you.

Thanks.

2018-07-24 01-18-37
joao.moretti

Aneesh wrote:

Hi Kevin,

The issue with my case was, I was using the same connection string which was used by another database extn module. I wasn't having enough permission for that module, even if i am having the full control on the connection string. So whenever I am trying to refer a new table which is already being used in that other extn, I was not able to publish my extn for those specific tables.

The temporary solution was to create a new connection string and use that to add the tables. Meanwhile a case is already created to fix this bug.

Let me know if this helps you.

Thanks.

Hello. This bug continuos? I have problems with
 database connection used for more than one extension and just administrator role can change and deploy this extensions. I use version 10.0.710.0 stack java.

Thanks: 

João Henrique


2018-02-22 10-33-20
Alexander Lange

Anybody an update as to whether this has been solved? We are on version 10.0.900.0 and i'm having exactly the same issues. 


We have two existing MySQL connection to two separate servers, and now i had a third one created to a third server (hence the connection string should at least contain some differences). I have full control over this specific DB connection but not admin access. Can't publish, same error.....


Hope someone knows where this stands...

Kind regards,

Alexander

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.