Getting an error on calling the Reload REST API

[rumen-vasilev]

Hello,

I am trying to reload an application via the REST API, but unfortunately I am getting an internal server error. Please take a look at the screenshot.

API Call via Windows Command Prompt:

Error log Butler:

I am actually running the pre-build application (ver. 8.4.0) on a Windows 2019 machine. Does somebody have the same problem?

BR,
Rumen

[mountaindude]

Exactly how do you call Butler's API? If you can share that it may be possible to test things here and possibly reproduce the issue. The starting-task-API is very flexible and powerful, but you need to pass in parameters the correct way. The helper sub included in the repo and in the demo app is prob easiest way to use that API from within a Sense script.

…

On Wed, 10 Aug 2022, 17:14 Rumen Vasilev, ***@***.***> wrote: Hello, I am trying to reload an application via the REST API, but unfortunately I am getting an internal server error. Please take a look at the screenshot. API Call via Windows Command Prompt: [image: image] <https://user-images.githubusercontent.com/83919259/183934391-13ab6946-6654-44d3-954b-65c84ccf491b.png> Error log Butler: [image: image] <https://user-images.githubusercontent.com/83919259/183939454-e744b92d-48c9-40ed-92c9-32d87003db0b.png> I am actually running the pre-build application (ver. 8.4.0) on a Windows 2019 machine. Does somebody have the same problem? BR, Rumen — Reply to this email directly, view it on GitHub <#543>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH3JDXNZDFIDIJ3OZ6CI5TVYPBMFANCNFSM56E5M4NQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mountaindude]

@rumen-vasilev
I did a quick test with 8.4.2 (stand-alone butler.exe running on WinSrv 2016) here and for me the API works:

Using cURL(on macOS) to call the API

➜  temp curl -X "PUT" "http://192.168.100.110:8081/v4/app/f42d6b16-8faf-45ca-a783-59f9da47db6d/reload" -H 'Content-Type: application/json; charset=utf-8' -d $'{}'

{"appId":"f42d6b16-8faf-45ca-a783-59f9da47db6d"}%
➜  temp

The result in the log is:

The fact that it's Enigma that complains about "Access denied" makes me wonder if your Butler for some reason cannot connect to the Sense server. Or if there are permissions issues in the file system on the Windows server.

Ideas for debugging the issue

Ensure connectivity to Sense server

You can try the Butler Ping endpoint to rule out Butler-to-Sense connectivity issues:

Using cURL (on macOS again):
curl "http://192.168.100.110:8081/v4/butlerping"

Looking good, which means Butler's communication with the Sense server is working. I.e. no certificate problems or similar.

The same can be done from PowerShell too.
Note that you should do this from a computer where the QlikClient certificate is installed, for example one of the servers in the Sense cluster:

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\goran> $url="http://192.168.100.110:8081/v4/butlerping"
PS C:\Users\goran> $cert = Get-ChildItem -Path "Cert:\CurrentUser\My" | Where-Object {$_.Subject -like '*QlikClient*'}
PS C:\Users\goran> Invoke-RestMethod -Uri $url -Method Get -Certificate $cert

response                  butlerVersion
--------                  -------------
Butler reporting for duty 8.4.2

PS C:\Users\goran>

Test for file system permissions issues

Try running Butler as local admin. If things work then you probably have a file system permissions issue.

[rumen-vasilev]

Hello Göran,

curl "http://192.168.100.110:8081/v4/butlerping" works fine.

I tried to call the api from the Butler demo app but also without success. I am getting the same error.

... and that is the debug log ...

However I will talk with our administrator tomorrow. Maybe this is a firewall security issue at our site. I give you a feedback tomorrow.

Thank you again for your support!

BR,
Rumen

[rumen-vasilev]

Hello Göran, I found the problem. It was because I tried to reload an application, which was published. That were the Sense security. :-)

[mountaindude]

Haha nice one! Good that you found the cause of the issue. All good now thus?

…

On Fri, 12 Aug 2022, 11:48 Rumen Vasilev, ***@***.***> wrote: Hello Göran, I found the problem. It was because I tried to reload an application, which was published. That were the Sense security. :-) — Reply to this email directly, view it on GitHub <#543 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH3JDXJU6V7R5CFSQDPWXLVYYMYLANCNFSM56E5M4NQ> . You are receiving this because you commented.Message ID: ***@***.***>