Dear All,

I have issue in front end web application 500 Internal Server error, What caused this error?

Id:45c54bef-4ddf-4514-a289-cb314418c50e
Time of Log:2019-07-17 10:03:02
eSpace:CustomerPortalFO
Tenant:Users
User: (87)
Session Id:2muxnwfhjdcgv5khv1g1r1gz
Server:HKRINPPW010
Module:REST (Consume)
Message:500 Internal Server Error
Environment InformationeSpaceVer: 0 (Id=87, PubId=0, CompiledWith=11.0.108.0)
RequestUrl: https://cignaku.cigna.co.id/CustomerPortalFO/BuatKlaim.aspx?_ts=1563332576049 (Method: POST)
AppDomain: /LM/W3SVC/1/ROOT/CustomerPortalFO-22-132060195035961086
FilePath: D:\Outsystems\Platform Server\running\CustomerPortalFO.124766253\BuatKlaim.aspx
ClientIp: 10.144.188.200
Locale: id-ID
DateFormat: yyyy-MM-dd
PID: 2556 ('w3wp', Started='15/6/2019 5:16:03 PM', Priv=812Mb, Virt=2115396Mb)
TID: 68
Thread Name:
.NET: 4.0.30319.42000
Stack:500 Internal Server Error
   at ssCigna_IS.CcPolicy.ActionPostClaimSubmissionMetadata(HeContext heContext, ICcPolicyCallbacks _callbacks, STPostClaimSubmissionMetadataRequestStructure inParamRequest, STAdditionalProfileStructure& outParamResponse)

Hi Rendi,

This could be anything, unfortunately. What does the "PostClaimSubmissionMetadata" Action do?

Kilian Hekhuis wrote:

Hi Rendi,

This could be anything, unfortunately. What does the "PostClaimSubmissionMetadata" Action do?

That`s the API forreceiving binary file from portal, file is uploaded by customer


Hi Rendi,

In that case, assuming the "portal" is called via a REST service method, it is very likely the REST service returned an error (i.e. an HTTP status code other than 200), which in turn causes the 500 error. You should check the Integration Logging in Service Center, and if that doesn't give you enough information, increase the logging level so you can see the actual message sent.

Kilian Hekhuis wrote:

Hi Rendi,

In that case, assuming the "portal" is called via a REST service method, it is very likely the REST service returned an error (i.e. an HTTP status code other than 200), which in turn causes the 500 error. You should check the Integration Logging in Service Center, and if that doesn't give you enough information, increase the logging level so you can see the actual message sent.

This is the logging :


Integration Error Detail
Back to Log
Id:0936106b-3321-4dca-856e-dea3e5873a88
Time of Log:2019-07-17 10:28:21
eSpace:CustomerPortalFO
Tenant:Users
User: (87)
Session Id:2muxnwfhjdcgv5khv1g1r1gz
Server:HKRINPPW010
Module:REST (Consume)
Action:Policy.PostClaimSubmissionMetadata
Error Message:The underlying connection was closed: An unexpected error occurred on a send.
Stack:[1] The underlying connection was closed: An unexpected error occurred on a send.
   at System.Net.HttpWebRequest.GetResponse()
   at ssCigna_IS.CcPolicy.ActionPostClaimSubmissionMetadata(HeContext heContext, ICcPolicyCallbacks _callbacks, STPostClaimSubmissionMetadataRequestStructure inParamRequest, STAdditionalProfileStructure& outParamResponse)

[2] Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
   at System.Net.Sockets.NetworkStream.MultipleWrite(BufferOffsetSize[] buffers)
   at System.Net.Security._SslStream.StartWriting(SplitWritesState splitWrite, SplitWriteAsyncProtocolRequest asyncRequest)
   at System.Net.Security._SslStream.ProcessWrite(BufferOffsetSize[] buffers, SplitWriteAsyncProtocolRequest asyncRequest)
   at System.Net.TlsStream.MultipleWrite(BufferOffsetSize[] buffers)
   at System.Net.Connection.Write(ScatterGatherBuffers writeBuffer)
   at System.Net.ConnectStream.ResubmitWrite(ConnectStream oldStream, Boolean suppressWrite)

[3] An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.MultipleSend(BufferOffsetSize[] buffers, SocketFlags socketFlags)
   at System.Net.Sockets.NetworkStream.MultipleWrite(BufferOffsetSize[] buffers)


No, this is not the (integration) logging, this is the error logging. However, it does show the problem, the host you are trying to contact is actively refusing the connection. This can have all kinds of causes, but none of them are directly related to OutSystems.