Using API /odata/Processes to upload a package. Get Internal Server Error

Help Orchestrator
1

Using API /odata/Processes to upload a package. Get Internal Server Error (500 error). We have two On Site Orchestrators - one that handles our Dev/Test and one that handles our Stage/Prod. Each Orchestrator serves 2 Org Units (Enviornments.)

We use SAML to log into both Orchestrator servers/sites.

The Dev/Test box works fine with using the /odata/Processes to upload packages.
The Stage/Prod does not (as well as a number of other API endpoints that also have the same error msg but work in the Dev/Test)

The reason this needs to work is that our packages are published from TFS using Power Script that uses the /odata/Processes to publish packages.
This works on the Dev/Test as outlined above.

I’ve used the SWAGGER page to test the various APIs and they fail on Stage/Prod as outlined above, but work fine on Dev/Test.
First I get logged in/authenticated by logging into the Orchestrator site using the SAML login. This ensures the proper token/access is established.

Any suggestions as to how I can find the actual error reason? User permissions? Bad Install? Other?

2

@scott.drudge

Can you check
The permissions…if the publish access
Is present or not…

Also is the authetication itslef failing from swagger?…are the orchestrator versions different?

Cheers

3

Hi Anil,
Thanks for the reply!
The Orchestrators are the same build, installed version, but the Stage/Prod server is locked down more than the Dev/Test machine.
Swagger works for many of the APIs, but not all. If permissions error, I would expect a “you are not authorized” or other response when tried and not a 500 Internal Server Error message.

We’ll check the permissions settings again. I think it’s related to how SAML2 is integrated as we do not use any normal Orchestrator logins.
This all worked fine at one time (been over a year.)

One of the Orchestrator admins can publish manually from the Upload Packages and is how we have been publishing to Prod until the API piece works again.

4

@scott.drudge

Did you make any recent changes to the iis servers?

Did you try restarting them?

Cheers

5

Hey Anil,
No server changes. Yes, they have been restarted. This has been happening for a long time.
I’m stepping through IIS server logs and reviewing the service user integration. I’m hoping it’s permissions related.
Thanks for the suggestions. Not solved yet, but I hope to resolve soon.
Cheers.

1 Like
6

@scott.drudge

Please check this.Also please check the event viewer on the server if there is something unusual

image
image828Ă—761 97.5 KB

Orchestrator - 2020.10.2(%20HTTP,expected%20behavior%20of%20the%20application.

Hope this might help(agrred that you are able to login…but still worth a check)

Cheers