I have a portal that I have successfully published, however, when I click on the URL to preview the portal I get the "The System Has Encountered an Error HTTP Code: 500" Appian pop up. Previously I was getting a "record does not exist, has been deleted, or you don't have permission to access it" error on a record backed dropdown field, so I commented out those fields and now I'm getting this error.
Looking in the Portal Server Log on the Troubleshoot tab in the Portal object, I noticed this error message "An error occurred while trying to read the security token from "/conf/appian.sec". No security token will be sent when connecting to engines". Would I be correct in thinking that this security token error is causing my issues? If so, what does this mean/how can I fix it?
I have a service account associated with this portal that has viewer access to all record types referenced in the portal, and viewer access to the process model it starts on submission. Since this seems to be a security issue, I suspect something is wrong with the way that I have configured the service account, however, this service account has been used in other portals successfully.
Any help or thoughts would be greatly appreciated. Thanks!
Discussion posts and replies are publicly visible
How long has the portal been published for now? I've seen once or twice where publishing a new portal refuses to work at first, but after a while (perhaps some lagging configurations on the server side), it starts working on its own.
If that persists more than a day or so, it might merit opening a support case.
It was last published at 4:06 PM last night, and as of 9:24 AM this morning it is still not working (so total of about 17 hours).
assuming this is in your Dev environment, try temporarily giving the service account in question Admin privs, wait a few minutes, and see if anything changes. that'll pretty much allow you to rule out whether it's some sort of configuration conflict on that side (i'm inclined to think it's not, but it'd be helpful to know for sure).
I gave the service account system admin privileges, waited a while, and tried again with the same result. I also republished the portal after that first try and tried it again, still got that error.
Then it might be time to just bite the bullet and try opening a support case, just to rule out any sort of back-end issue you'd have no control over anyway. At least, if you've already tried stripping the portal down to just a single interface of "hello world" complexity level and you still see the same results (if not, then maybe try that first just to be absolutely sure it's not something on your interface).
Reducing the interface to a few empty local variables and an empty text field produces that same result. I did notice that today the portal server log now also shows the error "Error when retrieving portal context keys from LCP Unexpected return code from LCP when fetching keys 401. Unexpected return code from LCP when fetching keys 401"
I went ahead and created a support case, and was able to fix the issue with Appian support's help. First, the "An error occurred while trying to read the security token from "/conf/appian.sec" message is not actually an error, it logs every time the portal is republished, so that was helpful to learn. Second, they had me unpublish the portal, save it, then republish the portal. That completely fixed the issue! Just the good ol' turn it off and back on again. Can't believe I didn't try that first lol, but now I know.
Jack Ferguson said:Just the good ol' turn it off and back on again
iykyk...