In an OutSystems Platform running on .NET stack, one (or more) of the following happens in a specific eSpace:
- It is not possible to access any screens in the eSpace
- It is not possible to call any web-services from the eSpace
- All BPT processes are stuck and giving errors
- All timers are stuck and giving errors.
- A publication error occurs in the final stage
When looking at the error log, the error message is generic, but the details show the below detail:
<b> Parser Error Message: </b>Could not create Windows user token from the credentials specified in the config file. Error from the operating system 'Logon failure: unknown user name or bad password.<br>'<br><br>
This problem happens because you have configured a "Run-As" user for your eSpace, but somehow the user you configured does not exist (or have the needed privileges) to run in the server.
Solving this problem involves either:
1. Removing the Run-As credentials, if they are not needed. This is the solution for all cloud customers, since Run-As is not available for cloud customers.
2. Fixing the privileges for the user.
To remove the Run-As credentials, access the details of the eSpace, and check the Operation tab. You will see the username set up. To remove these credentials, simply delete the value, click Apply Run As settings.
After this change, Service Center informs you that you need to republish the eSpace so the change gets effective.
To fix the user credentials, first identify the user that is running the eSpace. In our example, it is jpi90871
After you have found the user, log in to your server, and in Manage Users and Roles, open the IIS_IUSRS group and add the user to it:
Applies to OutSystems Platform for .NET, all versions (last reviewed under P9.1).