Web application returns an error upon changing server password.

Web application returns an error upon changing server password.

Hi guys,

A server which contains the web application we have developed using OutSystems changed its password. The problem is, upon changing the password, the application returns the "There was an error processing your request. Please try again later." message.

When the server's password was reverted back to the original password, the web application works again.

May I know what could be the factors affecting such action or what we can do to address the password change?
Hi Ju-chan,

You should check in http://<yourserver>/ServiceCenter in the Error Logs what is the error you are having.

Hi Andre,

As per checking, the error logs show entries of Scheduler Service errors. May I know what can I do?

You should check the error log right after you get the error in your application or filter the logs with the date and time when you got the error. You can also filter by your application. The Scheduler Service errors should not be the problem in your case.
What does the Scheduler Service really do? In the application we're developing, there are numerous timers being run in the system, and two of them are the contents of the error log and is repeated every minute (not the timer itself but the instant of the error log)

An error log stack is shown below and is only one of them.

Error Log Description:
Scheduler Service: Error executing request for Timer OutsideTAT. Request duration = 0 secs. [Will retry later]

Error Log Stack:

"System.InvalidOperationException: Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
        <title>Configuration Error</title>
         body {font-family:""Verdana"";font-weight:normal;font-size: .7em;color:black;}
         p {font-family:""Verdana"";font-weight:normal;color:black;margin-top: -5px}
         b {font-family:""Verdana"";font-weight:bold;color:black;margin-top: -5px}
         H1 { font-family:""Verdana"";font-weight:normal;font-size:18pt;color:red }
         H2 { font-family:""Verdana"";font-weight:normal;font-size:14pt;color:maroon }
         pre {font-family:""Lucida Console"";font-size: .9em}
         .marker {font-weight: bold; color: black;text-decoration: none;}
         .version {color: gray;}
...Exception]: An error occurred executing the configuration section handler for system.web/identity.
   at System.Web.HttpRuntime.FirstRequestInit(HttpContext context)
   at System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context)
   at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at OutSystems.HubEdition.Scheduler.TimerHandler.ExecuteTimer(String ssKey, Int32 timeout, Int32 tenantId)
   at OutSystems.HubEdition.Scheduler.TimerJob.Execute()
   at OutSystems.HubEdition.Scheduler.SchedulerProducerConsumer`1.Execute(Job job)
eSpaceVer: 0 (Id=0, PubId=0, CompiledWith=
RequestUrl:  (Method: )
AppDomain: Scheduler.exe
Path: C:\...\PS\
DateFormat: yyyy-M-d
PID: 2524 ('Scheduler', Started='7/2/2014 1:38:08 AM', Priv=72Mb, Virt=588Mb)
TID: 8
Thread Name: Timer Processor #1
.NET: 2.0.50727.5472"
The Scheduler service is the piece in the OutSystems Platform responsible for executing any asynchronous logic, like Timers, Processes and Emails.

Your error message tells me that you have a Timer named OutsideTAT on the module CCM. It looks like you have a configuration problem for that application. Is this application running ok? Is it just the timer that it is failing?
It looks like you may have changed the 'Run As' for this module in Service Center, is it correct? If you did are the credentials of that user correct?

Before the incident happened, basically, all is well. Application is OK, Timers are running ok.

The time the administrator changed the server's login credential, after a while, the application runs ok. The next day the application fails. Upon checking, the 'Run As' fields were not filled out yet.

I'll try later with the team to fill out the Operation category with the proper credentials.

It seems filling out the 'Run As' solved the issue! :) Thanks!