Active TopicsActive Topics  Display List of Forum MembersMemberlist  HelpHelp   RegisterRegister  LoginLogin
ISAPI_Rewrite 3.0 support forum
 Helicon Tech : ISAPI_Rewrite 3.0 support forum
Subject Topic: Crashing IIS6 -- uninstall seems to fail Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
michaelz
Newbie
Newbie


Joined: 04 September 2008
Online Status: Offline
Posts: 2
Posted: 04 September 2008 at 10:47am | IP Logged Quote michaelz
Hello,

Isapirewrite 3 seems to be crashing iis6.  We've upgraded to the latest version and the problems continue -- additionally it keeps making the site go unresponsive.

We have then tried to uninstall isapirewrite 3  and while it removed everything from program files, it left the remnants in the iis configuration, so the sites would not come back up.  We then had to reinstall it to get the sites back up.

Is there a command line method of uninstalling it?
Is there anything relevant in the attached crash report that lets you know of the issues?  (it shows it's isapirewrite crashing it out)

How can we get the site performing fast again and use isapirewrite?  Or how can we get isapirewrite uninstalled?

Here is an excerpt from the crash report:
WARNING - DebugDiag was unable to locate debug symbols for ISAPI_Rewrite.dll, so the information below may be incomplete.

Detected possible blocking or leaked critical section at ISAPI_Rewrite!TerminateFilter+86058 owned by thread 69 in Hang_Rule_Targets__Date__09_02_2008__Time_11_23_09AM__w3wp.exe__**name removed****__PID__12208__890__Manual Dump.dmp

Impact of this lock

1.92% of threads blocked

(Threads 91 93)

The following functions are trying to enter this critical section
ISAPI_Rewrite+1c05

The following module(s) are involved with this critical section
C:\Program Files\Helicon\ISAPI_Rewrite3\ISAPI_Rewrite.dll from Helicon Tech


AND ANOTHER ONE
WARNING - DebugDiag was unable to locate debug symbols for ISAPI_Rewrite.dll, so the information below may be incomplete.

Detected possible blocking or leaked critical section at ISAPI_Rewrite!TerminateFilter+86058 owned by thread 93 in Hang_Rule_Targets__Date__09_02_2008__Time_11_23_24AM__w3wp.exe__***nameremoved***_PID__9648__734__Manual Dump.dmp

Impact of this lock

44.23% of threads blocked

(Threads 4 5 6 7 10 14 15 18 34 37 39 44 45 47 48 50 51 52 53 54 56 57 58 59 60 64 66 67 76 77 78 79 80 85 86 87 88 89 90 91 92 94 95 100 101 103)

The following functions are trying to enter this critical section
ISAPI_Rewrite+1c05
ISAPI_Rewrite+1395
ISAPI_Rewrite+62de
ISAPI_Rewrite+1044

The following module(s) are involved with this critical section
C:\Program Files\Helicon\ISAPI_Rewrite3\ISAPI_Rewrite.dll from Helicon Tech



Also this

Locked critical section report

Critical Section    ISAPI_Rewrite!TerminateFilter+86058
Lock State   Locked
Lock Count   2
Recursion Count   1
Entry Count   0
Contention Count   26884
Spin Count   4000
Owner Thread   69
Owner Thread System ID   408




Edited by michaelz - 04 September 2008 at 11:01am
Back to Top View michaelz's Profile Search for other posts by michaelz
 
michaelz
Newbie
Newbie


Joined: 04 September 2008
Online Status: Offline
Posts: 2
Posted: 04 September 2008 at 12:09pm | IP Logged Quote michaelz
We are on build 3.1.0.56
Back to Top View michaelz's Profile Search for other posts by michaelz
 
Yaroslav
Moderator Group
Moderator Group


Joined: 15 August 2002
Online Status: Offline
Posts: 6470
Posted: 04 September 2008 at 5:51pm | IP Logged Quote Yaroslav
1. ISAPI_Rewrite when uninstalled should also delete everything it added to IIS configuration.
2. The only things it adds to configuration is global ISAPI filter (called ISAPI_Rewrite3) registration, which can be easily removed manually, and .rwhlp ISAPI extension, which if not called directly, should not even affect IIS operation.
3. Warning from DebugDiag program you have provided is normal - the logger thread is waiting for data to write. This will never affect IIS operation.
4. The only problem that comes into my mind is when IIS is unable to load ISAPI_Rewrite.dll ISAPI filter when configured to load it (due to insufficient NTFS permissions or unaccessible disk) and thus fails to startup. Are there any error messages in Application or System log?

__________________
Yaroslav Govorunov,
Helicon Tech
Back to Top View Yaroslav's Profile Search for other posts by Yaroslav Visit Yaroslav's Homepage
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You can vote in polls in this forum