Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: IW 14.2.6 and ISAPI



Permlink Replies: 5 - Last Post: Feb 5, 2018 5:12 PM Last Post By: Alexandre Machado
Omar Edgardo Ze...

Posts: 80
Registered: 8/7/07
IW 14.2.6 and ISAPI
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 1, 2018 7:28 AM
Hi,

I have updated to IW 14.2.6 from 14.1.8 and now a ISAPI DLL app stops
working after a few minutes(Error 500), I have tested on both Berlin
Update 2 and Tokyo 10.2.2 with same results, reverting back to 14.1.8
makes de app works ok with no problems.

Any hints or setting to set to help identify the change version issue
with my app.

Thanks in advance,

Omar Zelaya
Joel Zimmer

Posts: 68
Registered: 9/24/01
Re: IW 14.2.6 and ISAPI
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 1, 2018 12:08 PM   in response to: Omar Edgardo Ze... in response to: Omar Edgardo Ze...
I have been working through some similar issues but I am not sure if they are related to the iw version.

Alex had us put this line in the dpr to turn off some of the new things they were doing in version 14.2. (note you will also need add IWServerControllerBase in the uses section of the dpr.)

begin
TIWServerControllerBase.DisableFixupPatch := True;
IWRun;
end.

If adding that line solves your issue, then you will need to have Alex assist you to find the problem real problem
Omar Edgardo Ze...

Posts: 80
Registered: 8/7/07
Re: IW 14.2.6 and ISAPI
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 1, 2018 6:11 PM   in response to: Joel Zimmer in response to: Joel Zimmer
El 1/2/18 a las 2:08 p. m., Joel Zimmer escribió:

begin
TIWServerControllerBase.DisableFixupPatch := True;
IWRun;
end.

If adding that line solves your issue, then you will need to have Alex assist you to find the problem real problem

Hi,

Going to give it a try.

Thanks
Omar Edgardo Ze...

Posts: 80
Registered: 8/7/07
Re: IW 14.2.6 and ISAPI
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 2, 2018 9:28 AM   in response to: Omar Edgardo Ze... in response to: Omar Edgardo Ze...
El 1/2/18 a las 8:11 p. m., Omar Edgardo Zelaya Medrano escribió:
Hi,

Going to give it a try.

Thanks
Hi,

Making the changes to the dpr file has made my app estable now as it was
with previous 14.1.x version.

Now what? how can I find out what the real issue is with 14.2.x and my
ISAPI app?

Thanks in advance,

Omar Zelaya
Joel Zimmer

Posts: 68
Registered: 9/24/01
Re: IW 14.2.6 and ISAPI
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 2, 2018 9:35 AM   in response to: Omar Edgardo Ze... in response to: Omar Edgardo Ze...
You might look at this thread for some changes that we made which helped our applications: https://forums.embarcadero.com/thread.jspa?threadID=276948&tstart=0

However, it did not fix all of the issues. We are working with Alex and supplied him with a call stack using Eurekalog:

You might check out the following to see if you maybe supplying this to IW support would help.

One way is to use Eurekalog and their tool call ThreadsSnapShotGui.exe found in the C:\comps\EurekaLog 7\Bin folder

For more information look att: http://eurekalog.blogspot.com/2012/05/what-my-application-is-doing.html
Alexandre Machado

Posts: 1,754
Registered: 8/10/13
Re: IW 14.2.6 and ISAPI
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 5, 2018 5:12 PM   in response to: Omar Edgardo Ze... in response to: Omar Edgardo Ze...
Now what? how can I find out what the real issue is with 14.2.x and my
ISAPI app?

This switch will make it work as before 14.2.x (regarding some multi-thread improvements). We are still investigating it. I suspect that something else (maybe some 3rd party code), or something unusual causes it to fail. I've just sent you an e-mail so we can get more data to find out the cause.

Kind regards
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02