"GSX Lookup was not successful."

Solved. It was as I had guessed a GSX setup fubar on our side.

Still seeing this on our prod and test JSS v8.6—both on 10.6 Server. Can you elaborate on your GSX fubar (e.g. not setup w/ "Manager" GSX role, incorrect account name/password)? Pretty sure I've checked these things several times.

Here's a system.log snippet from our prod JSS while testing client details > Purchasing > clicking blue GSX search icon, which fails with "GSX Lookup was not successful."...

Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: Mar 25, 2013 3:25:08 PM org.restlet.ext.httpclient.HttpClientHelper start
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: INFO: Starting the HTTP client
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: Mar 25, 2013 3:25:08 PM org.restlet.ext.httpclient.internal.HttpMethodCall sendRequest
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: WARNING: An error occurred during the communication with the remote HTTP server.
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:352)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:339)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:123)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:147)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:108)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.restlet.ext.httpclient.internal.HttpMethodCall.sendRequest(HttpMethodCall.java:332)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.restlet.engine.http.adapter.ClientAdapter.commit(ClientAdapter.java:117)
Mar 25 15:25:08 MyJSSHost com.jamfsoftware.tomcat[72139]: at org.restlet.engine.http.HttpClientHelper.handle(HttpClientHelper.java:110)

Still not sure logs refer to GSX or internal proxy auth error.

For anyone else who might benefit, here's a summary of resolution to my GSX lookup issue...

1. JAMF TAM identified one GSX option unchecked, "Can check Coverage/Warranty"—despite the "Manager" role and "Can access Web Services", which was already set. Seems obvious in hindsight, but there was also a proxy component, too...

2. Our standard proxy PAC .js required unchecking, then setting Web proxy and Secure Web proxy (both w/ DOMAINaccount and password auth settings).

Working like a charm now.

I'm seeing "GSX lookup was not successful." errors now, exactly as described by original poster.

GSX connection tests work fine from the JSS. Certificates are valid etc. I can also log into the GSX site manually, and my AST Diagnostic Gateway GSX account works, too.

This is a relatively new issue, as I was in GSX checking purchase info via the JSS last week. No network changes have been made. Affects all my admin JSS accounts, thus not a ACL permissions issue.

Casper 9.81

@dstranathan Me too!

GSX test are successful. In the past 7 to 10 days, looking up individual devices both old and new, are resulting in "GSX lookup was not successful."

EDIT - More information has been posted here: related JAMF Nation Discussion