AnsweredAssumed Answered

direct connect to ArcSDE using postgresql doesn't work

Question asked by beerockxs on Apr 27, 2011
Latest reply on Jul 21, 2015 by ktuszynska-esristaff

Like • Show 0 Likes0
Comment • 8

Hi,

I'm having a problem with the direct connection using the "sde:postgresql:servername" entry as the service in ArcCatalog.
As far as I can tell, the entered info is all correct, and connection via the sde service works with the same usernames and passwords, but I get the "Bad login user" error message when trying the direct connection. pg_hba.conf is also set up correctly, I can for example directly connect to the database across the network using pgAdmin.
Does anyone have an idea what might cause this?

ktuszynska-esristaff

May 3, 2011 8:14 AM

Correct Answer

Sebastian,
The "bad login user" error is an hba issue.
If you think that the entries in your hba are correct than it might be a refresh issue, was the pg service restarted after the hba change? Was the client app restarted after the change?

- check what the pg error log says, often it gives very good indication of the problem
- possible problems:
      - your network has both ipv4 and ipv6 addresses and you need a entry for both
      - your authentication method is not appropriate
      - some silly spelling mistake

Sincerely,
Kasia

See the reply in context

No one else had this question

Outcomes

dlaw-esristaff

Apr 28, 2011 12:15 AM

Hi Sebastian,

Q) What OS are you using for your ArcSDE geodatabase on PostgreSQL?

If it's Red Hat Linux (RHEL) 5 or SUSE 10, please review this KnowledgeBase Article:

KB #38606 - HowTo: Make a Direct Connection from ArcGIS Server or ArcGIS Engine Runtime on SUSE to ArcSDE for PostgreSQL

Hope this helps,

Actions

beerockxs Apr 28, 2011 12:19 AM

Hi Sebastian,

Q) What OS are you using for your ArcSDE geodatabase on PostgreSQL?

If it's Red Hat Linux (RHEL) 5 or SUSE 10, please review this KnowledgeBase Article:
Hope this helps,

It's Windows Server 2008, so that doesn't help, I'm afraid.

Actions

dlaw-esristaff

Apr 28, 2011 1:33 PM

Hi Sebastian,

It's Windows Server 2008, so that doesn't help, I'm afraid.

Please review this KnowledgeBase Article:

KB #29585 - Error: Bad Login User

Hope this helps,

Actions

beerockxs May 2, 2011 4:11 AM

Hi Sebastian,

Please review this KnowledgeBase Article:

KB #29585 - Error: Bad Login User

Hope this helps,

I have reviewed it, and it doesn't help.
Does direct connect only work with operation system authentification?

Actions

ktuszynska-esristaff

May 3, 2011 8:14 AM

2 people found this helpful

Actions

beerockxs May 5, 2011 6:22 AM

- your network has both ipv4 and ipv6 addresses and you need a entry for both

Thank you, this was the problem.

Actions

maphew @ beerockxs on Jul 21, 2015 1:56 PM

I fought with this for hours. In the end the only thing that worked for me was to comment out both ipv4 and v6 and just open the gate completely:

host all all all md5

I note there is a discrepancy in syntax between Postgres and Esri docs for ipv6 that may come in to play. Compare the suffixes, "%10/n" vs "/n":

[Esri] To allow any machines with an address beginning with fe60 to connect, you would add this line to the pg_hba.conf file:

     host all all fe60::0000:0000:0000:0000%10/8 md5

[Postgres] An IPv6 address range might look like ::1/128 for a single host (in this case the IPv6 loopback address) or fe80::7a31:c1ff:0000:0000/96 for a small network.

Actions

ktuszynska-esristaff

@ maphew on Jul 21, 2015 2:46 PM

Matt,

not sure what you mean by comment out the entries for ipv4 and ipv6 completely?Do the settings below work?

- first row for ipv4

- second for ipv6

this is opening ipv4 and ipv6 wide open....

host

all

0.0.0.0/0

md5

host

all

::/0

md5

Kasia

Actions

8 Replies

dlaw-esristaff Apr 28, 2011 12:15 AM
Mark Correct
Correct Answer
Hi Sebastian,

Q) What OS are you using for your ArcSDE geodatabase on PostgreSQL?

If it's Red Hat Linux (RHEL) 5 or SUSE 10, please review this KnowledgeBase Article:

KB #38606 - HowTo: Make a Direct Connection from ArcGIS Server or ArcGIS Engine Runtime on SUSE to ArcSDE for PostgreSQL

Hope this helps,
Like • Show 0 Likes0
Actions
beerockxs Apr 28, 2011 12:19 AM
Mark Correct
Correct Answer
Hi Sebastian,

Q) What OS are you using for your ArcSDE geodatabase on PostgreSQL?

If it's Red Hat Linux (RHEL) 5 or SUSE 10, please review this KnowledgeBase Article:
Hope this helps,

It's Windows Server 2008, so that doesn't help, I'm afraid.
Like • Show 0 Likes0
Actions
dlaw-esristaff Apr 28, 2011 1:33 PM
Mark Correct
Correct Answer
Hi Sebastian,

It's Windows Server 2008, so that doesn't help, I'm afraid.

Please review this KnowledgeBase Article:

KB #29585 - Error: Bad Login User

Hope this helps,
Like • Show 0 Likes0
Actions
beerockxs May 2, 2011 4:11 AM
Mark Correct
Correct Answer
Hi Sebastian,

Please review this KnowledgeBase Article:

KB #29585 - Error: Bad Login User

Hope this helps,

I have reviewed it, and it doesn't help.
Does direct connect only work with operation system authentification?
Like • Show 0 Likes0
Actions
ktuszynska-esristaff May 3, 2011 8:14 AM
Unmark Correct
Correct Answer
Sebastian,
The "bad login user" error is an hba issue.
If you think that the entries in your hba are correct than it might be a refresh issue, was the pg service restarted after the hba change? Was the client app restarted after the change?

- check what the pg error log says, often it gives very good indication of the problem
- possible problems:
      - your network has both ipv4 and ipv6 addresses and you need a entry for both
      - your authentication method is not appropriate
      - some silly spelling mistake

Sincerely,
Kasia
2 people found this helpful
Like • Show 0 Likes0
Actions
beerockxs May 5, 2011 6:22 AM
Mark Correct
Correct Answer

- your network has both ipv4 and ipv6 addresses and you need a entry for both

Thank you, this was the problem.
Like • Show 0 Likes0
Actions
- maphew @ beerockxs on Jul 21, 2015 1:56 PM
  Mark Correct
  Correct Answer
  I fought with this for hours. In the end the only thing that worked for me was to comment out both ipv4 and v6 and just open the gate completely:
  
  host all all all md5
  
  I note there is a discrepancy in syntax between Postgres and Esri docs for ipv6 that may come in to play. Compare the suffixes, "%10/n" vs "/n":
  
  [Esri] To allow any machines with an address beginning with fe60 to connect, you would add this line to the pg_hba.conf file:
  host all all fe60::0000:0000:0000:0000%10/8 md5
  [Postgres] An IPv6 address range might look like ::1/128 for a single host (in this case the IPv6 loopback address) or fe80::7a31:c1ff:0000:0000/96 for a small network.
  Like • Show 0 Likes0
  Actions
  - ktuszynska-esristaff @ maphew on Jul 21, 2015 2:46 PM
    Mark Correct
    Correct Answer
    Matt,
    not sure what you mean by comment out the entries for ipv4 and ipv6 completely?Do the settings below work?
    - first row for ipv4
    - second for ipv6
    this is opening ipv4 and ipv6 wide open....
    host all all 0.0.0.0/0
    md5
    
    host all all ::/0 md5
    Kasia
    Like • Show 0 Likes0
    Actions

GeoNet

The Esri Community

direct connect to ArcSDE using postgresql doesn't work

Outcomes

Related Content

Recommended Content