Visual LANSA Forum

Posted: **Wed Sep 06, 2017 6:50 pm**

We are experiencing some errors in an existing solution, and I have been looking through the IIS log to spot the errors. Unfortunately the errors are not logged there.

If I provoke an error, this is returned to the browser (I am including the complete headers but has removed most of the HTML as I cannot submit that here):

Code: Select all

HTTP/1.1 500 Internal Server Error
Pragma: no-cache
Content-Type: text/html
Expires: Wed, 06 Sep 2017 06:45:31 GMT
Server: Microsoft-IIS/8.5
X-Powered-By: ASP.NET
Date: Wed, 06 Sep 2017 06:45:31 GMT
Connection: close
Content-Length: 1208

Server Error
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.

but this is logged in the IIS log:

Code: Select all

#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
2017-09-06 05:56:02 10.255.10.12 GET /lansaweb/lansaweb.dll lansaweb?webapp=WAMLOGINX+webrtn=Startpage+ml=LANSA:PPC_XHTML+partition=BUT+language=NAT 80 - 192.168.1.124 Mozilla/5.0+(Windows+NT+10.0;+WOW64;+rv:55.0)+Gecko/20100101+Firefox/55.0 - 200 0 0 187

I cannot find any log describing the error and I wonder where to look. Anyone who knows where?

Posted: **Thu Sep 07, 2017 9:19 am**

There is a file called X_Err.log that is produced when a dll on the server crashes, for an IIS web job.

It can be very useful.

On my PC I would look in:

C:\Windows\Temp.

Posted: **Thu Sep 07, 2017 5:41 pm**

Thank you. I did actually look there but apparently I got confused by the dates. The file had data from 2015 onwards but I have now created a clean version.

I'd add that lansaweb.dll still logs the error as status 200, which seems odd.

Can anyone help with this error description from X_ERR.LOG?

Code: Select all

Release 12.0.0 Build 4042 Windows 2000/XP
Message : (0586) - Component Manager request of type 3 (decimal value) failed with return code -1 (decimal value).
Routine : X_Execute_WAM
Job Number: 027460 OS User : LansaWeb

The page only fails rarely so the bug is triggered by some condition, and I am trying to figure out which.

Posted: **Fri Sep 08, 2017 8:35 am**

Anything in the event logs on the Windows server?

Posted: **Fri Sep 08, 2017 1:37 pm**

ITs possible that IIS is replacing the lansaweb error with its own error handling. So, I'd worry less about that at the moment and focus on whether there is a Lansa error and what it is. I'd report this to your local LANSA support group, they can give you the instructions to enable WAM logging.

Visual LANSA Forum

lansaweb.dll returning status 500 but logging status 200

lansaweb.dll returning status 500 but logging status 200

Re: lansaweb.dll returning status 500 but logging status 200

Re: lansaweb.dll returning status 500 but logging status 200

Re: lansaweb.dll returning status 500 but logging status 200

Re: lansaweb.dll returning status 500 but logging status 200