IIS 4 & 5 Differences

I have an asp app written and tested and working on windows 2000 .. running on IIS 5 with an access back end... I have just transfarred this to windows NT and IIS 4..... and I am getting script and OSBC errors all over the place...
errors such as :
Microsoft OLE DB Provider for ODBC Drivers error '80040e07'

[Microsoft][ODBC Microsoft Access 97 Driver] Data type mismatch in criteria expression.

/timetable/pageprotect.asp, line 52

where I know there wasnt one on my other pc...

and this error:
Response object error 'ASP 0156 : 80004005'

Header Error

/timetable/nocache.asp, line 3

The HTTP headers are already written to the client browser. Any HTTP header modifications must be made before writing page content.


are there problems/differences between IIS 4 & 5 that I need to know about for running ASP ....??
thanks in advance

correction... thats supposed to be "ODBC" not "OSBC".. slight typo....

Just so you know, you have an Edit link button that you can click to edit your post

Now, for your error, I've notice your using *Access 97*
Perhaps you need to update the driver on that win NT box.

If not, try a simple test.

Create yourself a simple .asp page that connects to your database...see if the error is there...

You could also try an create a DSN or a DSN-Less connection, infact try the 3 methods.

Debugging will/is the only way to find out what's the true meaning of your error message!

Hope this helps!
Sincerely

Vlince

Did you edit any pages when you transferred the application? The header error can pop up when you accidently add a character before the <% code, which asp will treat as html and send to the browser writing the http headers in the process.

Even an empty line or a space at the top of a file can cause this.

As for the db, review the permissions you have given the .mdb file and make sure the IIS user account has read/write permission.

If you need updated drivers you can get them from www.microsoft.com/data and you need to download the Jet (Access) drivers separately from the rest of the MDAC.

after searching the depths of the InternetI managed to come up with this:
by inserting
response.buffer=true

at the top of every page....
that fixed all my migration issues......
as regards my ODBC errors...
I installed mdac... which i believe would have over-written my access 97 drivers.....
funny that ..
cheers for the help
regards

R

I think there is an IIS setting to enable/disable output buffering by default, perhaps the setting is different between the previous/new servers.

FYI, if you download MDAC from v2.6 on you don't get the Access drivers in the base MDAC download. There is a separate Jet download for them.

NOTE:
By default in ASP 2.0 the Buffer is set to *FALSE* that's why you explicitly need to say it when you need it.
Example: Response.Buffer = true

BUT

In ASP 3.0 the default value of the Buffer is set to *TRUE* so you don't need to set it *unless* you want it to be false then you explicitly say it:
Example: Response.Buffer = false

Hope this helps!
Sincerely

Vlince

that makes plenty of sense..
cheers for the reply!!