Skip to Content
Last modified by David Muszynski on 2025/05/09 15:31
From version 1.4
edited by David Muszynski
on 2025/03/21 13:40
Change comment: There is no comment for this version
To version 1.3
edited by David Muszynski
on 2025/03/21 13:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -21,6 +21,7 @@
21 21  
22 22  //Renewing GSX Access in CheckIn//
23 23  
24 +
24 24  In the event that you need to renew your GSX access in CheckIn, or if you see a “Call Not Authorized” error message when attempting to connect to GSX: In the SRO Dashboard, click "More," and from the drop-down menu, select "Get New Token." (You can also do this through any SRO, by clicking on the small ‘gear’ icon in the lower right hand corner.) In the small pop-up window, click the “Get a New Token” button. A new window will appear.
25 25  
26 26  If this is a troubleshooting step, you can click the “Test Connection” button, to establish that CheckIn has a working connection with GSX.
... ... @@ -29,38 +29,12 @@
29 29  
30 30  Click the “Authorize New Token” button. You should see a dialog box indicating success. Click the “Test Connection” button, to establish that CheckIn has a working connection with GSX.
31 31  
33 +
32 32  //If you experience connection issues with GSX, or see an error message that indicates you might need to restart the FileMaker Script Engine//
33 33  
36 +////
37 +
34 34  Have a look at the most recent Activity Log entry (assuming the attempt to connect to GSX was the most recent activity). That's in the Menu Bar: //Checkin > Functions > Show Activity Log,// or [Command-9]. Click on the small "word balloon" icon at the right of the last entry to show the details of the log. Look for the section "RESULT," and if you see no text (rather than an error message), it's possible this will be resolved by restarting the FileMaker Script Engine.
35 35  
36 -To do so, open Terminal on the FileMaker server and type the following:
37 37  
38 -{{code width="60%"}}
39 -fmsadmin restart fmse
40 -{{/code}}
41 -
42 -Then type //Y//, and [Return]
43 -
44 -This will restart the FileMaker Script Engine, but should not disrupt any other users.
45 -
46 -
47 -//GSX Connection Issues//
48 -
49 -If you encounter an error like this when checking the log files:
50 -
51 -//HTTP/1.1 403 Forbidden & X-Apple-Error-Codes: UNAUTHORIZED//
52 -
53 -If you are confident you have CheckIn configured correctly, this might be an issue that needs to be resolved by Apple. Email Apple's GSX Web Services team at //[[[email protected]>>mailto:[email protected]]]// and copy your service Rep. Ask Apple if your IP address is not currently whitelisted, and ask them to whitelist it again, if necessary.
54 -
55 -At the beginning of the email, include the following information:
56 -
57 -//GSX Sold-to account number:
58 -GSX Ship-to account number:
59 -Contact’s name: //
60 -//Contact’s email:
61 -Apple ID for GSX Access:
62 -Contact’s phone number: //
63 -
64 -//Supplier //must// be configured as Apple Service//
65 -
66 -GSX Access in CheckIn is configured to use "Apple Service" as the supplier for all service parts ordered through GSX. //It's important that you not change this,// as doing so will create issues with adding service parts with the appropriate coverage and pricing options.
41 +To do so, open Terminal on the FileMaker server and type the following: