[thelist] IIS ASP puzzler

[Ken Schaefer]

Please post the *exact* error you are getting, not some vague description of
what is approximately what you recall seeing at some stage in the past week.
You're an MCSE - didn't you learn anything?

As you can see, these vague descriptions have already prompted a flurry of
further posts asking for more information!

Lastly, if the exact same code[1] works on another website on this machine
then you'll need to start looking at NTFS related issues. Are both sites
running under the same anonymous user context? Are the NTFS permissions the
same for both users for both folders where the respective databases are
located?

However, there are a number of errors that are similar to the text you have
posted:
- Operation requires an updateable query - NTFS problem

- Current cursor does not support updating - this is an ADO recordset
problem. You may be using adLockOptimistic in your code, but is
adLockOptimistic defined? Are you using Option Explicit to catch these
things? If not, why not?

- Could not open ''. File in use, or you do not have permission to view the
data - NTFS permissions problem.

Cheers
Ken

[1] I'll take your word for it that are a cognisant of what things can make
two pieces of similar looking code not an exact match.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: "Dougal Campbell" <dougal at gunters.org>
Subject: Re: [thelist] IIS ASP puzzler


: On Tue, 25 Feb 2003, Anthony Baratta wrote:
:
: > At 02:03 PM 2/25/2003, Dougal Campbell wrote:
: >
: > >By liberal use of "On Error Goto Next" and "On Error Goto 0", I've
: > >determined that the object creation for ADODB.Recordset and
: > >CDONTS.NewMail succeed. The failure doesn't occur until we try to call
: > >'objRS.Update' or 'objMsg.Send'.
: >
: > Are you getting *any* error messages with your code? Have you done a
: > diff/compare between a working page and the non-working page to verify
the
: > code has not changed?
:
: I get an ASP error indicating that the recordset cursor could not be
: updated. The ASP code is identical between the two versions on this
: particular server. And the *exactly identical* code runs find on our
: test server. The problem is not in the ASP code, it is somewhere higher
: in the hierarchy of IIS.
:
: One (totally invented) theory that one of our developers had was that
: perhaps the IUSR_foo anonymous account somehow has read access to those
: components, but not write access. But I haven't found anything yet that
: would support that idea.
:
: We've also tried deleting the directory's application settings from the
: Transaction Server settings in the MMC, then recreating them under the
: IIS settings. But that didn't clear the problem up either.