7. GSX Lookup Troubleshooting

Most if not all of the errors relating to GSX lookups are either due to something on Apple’s end or something to do with a technician ID or the need to acquire a new security token.

In order to properly communicate with GSX or CheckIn support you will need to email your log file. Immediately after a failed GSX lookup attempt, go to the Scripts menu at the menu bar of your Mac and select “Show CheckIn Activity Log” and go to the last log listed which should have the timestamp of the lookup you just attempted. If Result show nothing then you will need to Restart the FileMaker Script Engine by doing the following:

• Go into Terminal on the server and enter following command: fmsadmin restart fmse
• Then type a: Y then Hit Return
• You can create an Apple Script to automate this to happen once a day or week if you like.

If your log file shows any type of error you will need to email GSX but this is the most common error: HTTP/1.1 403 Forbidden & X-Apple-Error-Codes: UNAUTHORIZED

Email Apple GSX Web Services team at:  [email protected] and copy your service rep on the email along with the Information listed below filled out as the header (at the top of your email) before composing the rest of the email and pasting in the log file.

GSX Sold-to account number:
GSX Ship-to account number:
Contact’s name:
Contact’s email:
Apple ID for GSX Access:
Contact’s phone number:

If apple GSX Web Services team says that a certain account “no longer has GSX access” this means there is another issue with the account and it most likely has an outdated “Person Type of Developer” issue and in order to be able to use the GSX API services, you will need to have an updated Person Type which you need to rectify by emailing:  [email protected]

You can of course email CheckIn support at [email protected] first if you like but best to save time and email Apple and copy us.