After v11 upgrade ... "The remote server returned an error (401) Unauthorized"

Hi all !

I have a problem after the upgrade from v10 to v11. We upgraded all our infrastructure (Dev server / Lifetime server / Prod server) ... everything works. We upgraded / republished all the applications / modules.

Now, when we click on the "New application" button we have the message "The remote server returned an error (401) Unauthorized".

This happens even with the personal users accounts (developers), even with the admin account.

What are we missing ?

I recommend opening a ticket with support.

https://www.outsystems.com/SupportPortal/Support/

They will be able to better assist you with this issue since they have better visibility into the environments.

Andres Moreno

Thanks Andres, I'll do that

Luca De Mori wrote:

Hello Luca,

Did you get an answer to your problem? Please I would like to now as I am getting the same error.

Yes, I solved with the Support ... I opened a case

It was a pemission problem ... I make a copy / paste of our activity (maybe it can help you):

You can find below a summary of the troubleshooting we performed during our call:

    We started by reproducing the problem of attempting to create a new application in Service Studio and we immediately obtained the HTTP 401 Unauthorized error;
        This was tested from outside the server machine and also from inside the server connected through "localhost";
    There was no error logged in the Error logs of Service Center nor any call in the Integration Logs;
    From the error in Service Center, we could see that the error was being triggered when calling and exposed REST service from a System Component called Template Manager;
        This web service uses Basic Authentication and the authentication token is sent on the headers of the request;
    By enabling the IIS feature Failed Request Tracing, we were able to validate that the request from Service Studio did contain the Basic Authentication header, but the error was happening nonetheless;
    After analyzing the IIS Authentication on the Template Manager site, we verified that this site had the Basic Authentication enabled. After disabling it, we were able to create new applications;


It seems that the Template Manager inherited the Authentication configurations from the Default Web Site because it is a new module. Modules that already existed remained with the current configurations.

You can also revert the changes we performed during the troubleshooting:

    Change the Integration log level of the Template Manager exposed REST service TemplateServices to Default to avoid excessive logging;
    Disable the IIS Failed Request Tracing;


Since the problem is resolved, we'll be marking the ticket as solved.

Hi Luca,

Just marked your answer as solution for everyone else that get the same problem.

Regards,

Marcelo