Re: w3wp.exe stop responding!!!
From: Pat [MSFT] (patfilot_at_online.microsoft.com)
Date: 03/03/04
- Next message: Pat [MSFT]: "Re: CreateObject of java class dosen't work with IIS6"
- Previous message: Pat [MSFT]: "Re: constant http timeouts iisstate.log below"
- In reply to: avner: "w3wp.exe stop responding!!!"
- Next in thread: Shekhar: "Re: w3wp.exe stop responding!!!"
- Reply: Shekhar: "Re: w3wp.exe stop responding!!!"
- Reply: Avner Netz: "Re: w3wp.exe stop responding!!!"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 2 Mar 2004 22:38:30 -0800
I believe that I already answered this, but the IIS6/Jet issue has nothing
to do with Opportunistic Locking. The issue is entirely within the Jet db
drivers. I would urge you to run IISState against the w3wp.exe process and
post the log so that we can confirm what you have.
So,
the next time w3wp.exe stops responding run:
iisstate -p <pid of w3wp.exe> <enter>
And post the log.
Pat
"avner" <info@netzbiz.com> wrote in message
news:5c5001c400b7$0d22b4d0$a401280a@phx.gbl...
> Hi there, I have a new server 2003 with IIS6 and since I
> had set it up, I have a major problem with the IIS. The
> w3wp.exe will stop responding to any ASP pages and all my
> sites will stop work! I found out the a static HTML pages
> still runs fine. All my site use Access database and I
> had upgrade to JET4 already. can anybody help me???
> All my sites had run fine under 2000 server IIS5 with the
> same code.
>
> I also got this email from a friend that claims Microsoft
> 2003 have a bug with any databases and they do not give a
> patch to anyone but Great Plains company! Is that is
> true????
>
> Here is the email i got:
>
> Windows 2003 Gotcha: Opportunistic File Locking
>
> "I have been running W2K3 since it was a beta and had no
> problems with
> the OS. I then decided it was becoming time to start
> offering it to my
> customers so the first step was to get my office running
> it first. I
> upgraded the servers all to Windows Server 2003 and as
> with most
> engineers I was rushed back into the wild to fix
> something and let the
> office jockeys run on it.
>
> I felt that I had a successful migration after a few
> weeks so I moved
> on
> to a contract customer of mine that I have had for six
> years. I
> upgraded
> his Dell PowerEdge 1500SC from Windows 2000 Server to
> 2003 and
> immediately the users started complaining of problem
> accessing there
> QuickBooks files, then the no access turned into file
> corruption. This
> customer also runs a older Paradox database system on the
> server and
> files started becoming corrupt with it as well.
>
> I ran through the basic troubleshooting, then the second
> phase of
> troubleshooting all with no victory. I called QuickBooks
> and they said
> must be hardware, I called Dell and the said must be
> Windows Server
> 2003, so I called MS and they said it must be hardware.
> To shorten
> this
> up some I removed Windows 2003 upgrade and reinstalled
> Windows 2000
> Server and the problems immediately went away. The only
> thing at time
> my
> searches on the internet showed had something to do with
> Opportunistic
> File locking features in Windows, but nothing conclusive
> to me.
>
> So I put it on the back burner until yesterday and
> started searching
> again, wow what a difference a month makes, now people
> all over the
> place are having the same problems with Windows Server
> 2003 and
> Database
> applications, it seems opportunistic file locking is the
> problem, I
> found one news group posting where someone stated that
> Great Plains
> was
> experiencing this problem so I took a shot and called our
> Great Plains
> contact at MS and he stated that MS had patched it for
> them but he was
> not allowed to release it to anyone not running Great
> Plains. To wrap
> this up Microsoft has let down an engineer that lives and
> breathes
> their
> product, I make my living off of this software and to be
> told first
> that
> nothing is wrong (must be hardware) and then told that
> they have a fix
> but it is only for the big clients is not pretty."
>
>
> Please contact me if you have any information about this
> so i know if i need to downgrade to 2000 and stop
> waisting my time and money on 2003.
- Next message: Pat [MSFT]: "Re: CreateObject of java class dosen't work with IIS6"
- Previous message: Pat [MSFT]: "Re: constant http timeouts iisstate.log below"
- In reply to: avner: "w3wp.exe stop responding!!!"
- Next in thread: Shekhar: "Re: w3wp.exe stop responding!!!"
- Reply: Shekhar: "Re: w3wp.exe stop responding!!!"
- Reply: Avner Netz: "Re: w3wp.exe stop responding!!!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|