Re: windows 2003 bug

From: Pat [MSFT] (patfilot_at_online.microsoft.com)
Date: 03/03/04


Date: Tue, 2 Mar 2004 22:23:35 -0800

1) The Jet problem has nothing to do with opportunistic locking.
2) The issue is entirely within the Jet ODBC/OLEDB drivers

If you have an IISState log, you may post it and we can confirm the issue
for you. Once confirmed, I would recommend that you open a support
incident.

Pat

"Avner Netz" <info@netzbiz.com> wrote in message
news:%23hashDLAEHA.576@TK2MSFTNGP11.phx.gbl...
>
>
> I had set a new web server with windows 2003 enterprise.
> All my sites are ASP with Access database with the new JET4 engine
> installed!
> What a big mistake!!! Since it is up the w3wp.exe stop responding at
> list once or twice a day! can not find why, can not get help from
> microsoft or anybody else so far...
> Log files don't give too much info and I had setup iisstate as well.
> Anybody have the same problem???
>
> I also found this artical about windows 2003 and database:
>
> I ran across this on a mailing list, written by an MCSE, and thought you
> all ought to be aware of this problem -- at least until it gets fixed.
>
> -------------------------
>
> 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."
>
> If that is the case, do not bother with server at all!!!
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!



Relevant Pages

  • RE: 2nd form with recordset of 1st
    ... processes using this table using optimistic locking? ... If this is a split database, is there a persistent connection to the back ... Every directory traversed requires Windows to ... > record source to be the 1st forms recordset? ...
    (microsoft.public.access.formscoding)
  • Re: help with 2000i on win2k server (sp3 on database)
    ... See Leonard's post for the config options. ... If the server is mangling itself, then ANYTHING running on the server ... that I work with will support the database AND the application. ... As for Windows vs. Linux/NetWare, I can agree, but I also see MANY ...
    (comp.databases.btrieve)
  • Re: nt4.5 to w2003
    ... keep in mind that there basically is two different things you can do to move from an NT 4 (SAM Database) domain to an Active Directory Domain. ... You can choose to upgrade the domain from NT 4 to Windows 200x Active Directory. ... The thing to keep in mind here is that you have to Upgrade an NT 4 PDC to Windows 200x. ... You could download and install Virtual Server 2005 if you needed to upgrade an NT 4 machine to Windows 200x and your real hardware either does not support NT 4, or the NT 4 hardware you have does not really support Windows 200x. ...
    (microsoft.public.windows.server.migration)
  • Re: Setting up Linked server to MsAccess
    ... At the server level I have added my windows user group ... At the database level I have added my Server login ...
    (microsoft.public.sqlserver.security)
  • Problem with Sharepoint Windows Services on Win 2003 SBS Server
    ... The other day we had a server that crashed for some unknown reason. ... "Cannot connect to the configuration database. ... I should point out at this stage that the OS is Windows 2003 Small Business ... SharePoint Services 2.0 and tried re-installing MSDE by launching ...
    (microsoft.public.windows.server.sbs)

Quantcast