POST
|
Hi @JonathanQuinn Thanks for your response. From devtools it seems there's no errors. I can make the warnings disappear if I want by fiddling with the devtools settings. All network resource responses come back green. When I look at the response for the job submitted to the GPServer I can see the error. {"jobId":"j83f11f0370504d62a2719ece324665c1","jobStatus":"esriJobFailed","messages":[{"type":"esriJobMessageTypeInformative","description":"Submitted."},{"type":"esriJobMessageTypeInformative","description":"Executing..."},{"type":"esriJobMessageTypeError","description":"Invalid value for parameter inputLayer - Details : Accessing URL https://maps.portofnewcastle.com.au/server/rest/services/Hosted/colabtest/FeatureServer/0 failed with error ERROR: code:403, Access to this resource is not allowed, Access to this resource is forbidden, regardless of authorization.. "},{"type":"esriJobMessageTypeError","description":"Failed."}]} I can browse to that resource without logging into the rest server and there should be no restrictions. This little test layer is globally shared. Any ideas what went wrong? Thanks again. James
... View more
12-01-2020
07:11 PM
|
0
|
0
|
219
|
POST
|
Hi @Travis_Esri, Apologies for the late reply. I did check the portal and server logs before and couldn't find anything. However thanks to your post I went looking in the Windows logs. I've found the problem. Arc threw a system level error. I've used an AD user as is recommended by ESRI to run all of the arcgis processes. It appears to be a rights issue. Specifically a "Local Activation permission". I think I may have fixed the issue using the instructions from https://appuals.com/how-to-fix-the-application-specific-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application-error/ but I don't think it will apply until I reboot the server. I'll be doing that shortly to see if hopefully the arcgis user has access to that COM module. Thanks for your help. Cheers, James
... View more
11-29-2020
08:26 PM
|
0
|
3
|
231
|
POST
|
Hi All, Analysis via our 10.7.1 ArcGIS Enterprise portal has been a feature that I haven't exposed users to yet. When I went to use them recently I realised that any analysis fails with the below blank error message box. So I tried restarting the publishing and publisingex services. I also used the browsers (Chrome) devtools to catch any errors when I stepped through the process. No issues there. I swear it worked when I first spun up the portal but I'm not sure how long its been broken. I haven't powered down and restarted the vm server itself yet which was my next move. Has anyone got any ideas? Cheers, James
... View more
11-24-2020
05:39 PM
|
0
|
6
|
271
|
POST
|
If you happen to be working with the built in Windows Defender real time protection you have the ability to turn it off for nominated processes (Configure exclusions for files opened by specific processes - Windows security | Microsoft Docs). That way you can still have Defender do its thing but anything that pro opens gets excluded. I used the powershell method (must be admin): Add-MpPreference -ExclusionProcess "C:\ArcGIS\Pro\bin\ArcGISPro.exe" Obviously it won't help traffic on the network but it might help locally...
... View more
04-02-2020
06:12 PM
|
2
|
0
|
139
|
POST
|
I had the same issue. I found a resolution. I had configured my portals identity store with my own domain login for testing. Worked fine. Following ESRIs best practice advice (http://enterprise.arcgis.com/en/portal/latest/administer/windows/use-integrated-windows-authentication-with-your-portal.htm) I asked my ICT to make a basic domain account who can do lookup and whose password doesn't expire. In my case I called it GISLookUp. I kept getting the same error described even though I was sure that there was nothing wrong with the JSON. I thought that perhaps my ICT had stuffed up the account so I signed in to the domain using GISLookUp. I noticed that Windows asked me for a password change up front. Once done and signed in I was happy the account worked. Then I tried to update identity store again and it worked! The problem for me was the new domain account hadn't been registered or activated or whatever it is that Windows does until I had done that initial sign in. Try signing in with the account you are using first.
... View more
03-24-2019
04:33 PM
|
0
|
0
|
165
|
Online Status |
Offline
|
Date Last Visited |
Wednesday
|