current community

your communities

more stack exchange communities

Stack Exchange
tour help
Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.
up vote 1 down vote favorite

I am having issues with adding postgis query layers in ArcMAP 10.2.2.3552, not doing anything special just adding a layer, this works in 10.2.1 so I don't know if its a bug or something

Also this error only happens when adding a query layer from a database over the network using ip address, the same database in the local install has no issues

error image

share|improve this question
    
Could you show us the structure of the table? ArcMap is very finicky about how you structure your postgis tables. For example, it doesn't like any uppercase column names for some reason... –  janechii Oct 29 '14 at 17:55
    
yeah thing is it works in a previous version, we are testing in the following days with Collate because in Postgis it is using "XXX.XXXX" and if we changed this to "English,XX" it works. So maybe dot notation is the culprit here. –  Antonio Locandro Nov 1 '14 at 3:40
    
OK managed to solve things, apparently username cant be longer than 8 characters or have ".", adding this here just in case someone else has same issues –  Antonio Locandro Nov 13 '14 at 17:58
    
wow.. that's interesting... and weird! Please place your answer in the answer area and accept it. Answered questions are marked differently and more legible for future readers! –  janechii Nov 13 '14 at 18:02

2 Answers 2

up vote 0 down vote

For future reference in case anyone else has the same misfortune, I got the same error message trying to add a SQL Spatial table and found that you need to "Check" the name (ISqlWorkspace::CheckDatasetName) before using it. https://badarcgis.wordpress.com/2012/03/30/query-class-name-is-invalid/

share|improve this answer
up vote 2 down vote accepted

Just for future reference,

Username was giving issues if it was longer that 8 characters and if it contained ".", I really don't know why but reducing username length to 8 characters has solved the query layers issues I was experiencing, probably didn't work in previous version as IT used postgres user to test

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.