Microsoft IIS
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
 
 
User Name:
Password:
Remember me
Go Back   ASP Free ForumsSystem AdministrationMicrosoft IIS

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Rate Thread Display Modes
 
Unread ASP Free Forums Sponsor:
  #1  
Old April 23rd, 2004, 10:16 AM
steve123 steve123 is offline
Registered User
ASP Free Newbie (0 - 499 posts)
 
Join Date: Sep 2003
Location: Maryland
Posts: 13 steve123 User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 0
IIS 6.0 and disappearing HTML Elements

ASP pages that use RecordSets like this:

recordSet.Open Session("RepQryStr"), connection, 3

where 3 = adOpenStatic, work on the setup of
Windows 2000 Server/IIS 5.0, but on Windows 2003 Server/IIS 6.0 I see that HTML elements disappear after attempting the query.

The strange thing is, on other ASP pages I just changed the cursor type to 0 = adOpenForwardOnly, and it works, but on another ASP page it does not and plus makes HTML elements disappear!

Anyone experience this oddity with IIS 6.0?

Reply With Quote
  #2  
Old April 23rd, 2004, 11:32 AM
steve123 steve123 is offline
Registered User
ASP Free Newbie (0 - 499 posts)
 
Join Date: Sep 2003
Location: Maryland
Posts: 13 steve123 User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 0
Post

I have a theory on the disappearing html elements issue,
I imagine that ASP is a new version on Windows Server 2003, and there are thus new rules and behavours. I am just experiencing some of them.

I have noticed this with ASP and Windows Server 2003 and I detail it below:

When you use a particular cursor type for a RecordSet, and you attempt to call the RecordCount property, or the MoveFirst method, and that cursor is not supposed to use those properties/methods, you won't get an error, but you may get very unpredictable results.

I know this because I tried to trap errors by using
"On Error Resume Next" and calling an errorHandler subroutine,
and Err.Number was zero.

This has to be helping someone.

Reply With Quote
  #3  
Old April 23rd, 2004, 12:36 PM
Doug G Doug G is offline
Grumpier Old Moderator
ASP Free God 11th Plane (10000 - 10499 posts)
 
Join Date: Sep 2003
Posts: 10,143 Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level) 
Time spent in forums: 3 Weeks 4 Days 23 h 19 m 36 sec
Reputation Power: 181
I'd review your asp code. Everything you are discussing is ADO related, not necessarily ASP related. IIS6 doesn't have any problems with asp that I'm aware of.

You might wander around the ADO reference documentation for more description of cursor type, lock type, recordcount, etc.

http://msdn.microsoft.com/library/e...rsreference.asp
__________________
======
Doug G
======
I didn't attend the funeral, but I sent a nice letter saying I approved of it. --Mark Twain

Reply With Quote
  #4  
Old April 26th, 2004, 10:33 AM
steve123 steve123 is offline
Registered User
ASP Free Newbie (0 - 499 posts)
 
Join Date: Sep 2003
Location: Maryland
Posts: 13 steve123 User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 0
The fact that there was different behavior on the 2 setups, same web page code, indicates to me there are subtle differences between the ASP DLL with the new Windows Server 2003.

Looks like a stricter policy on what is allowed with the cursors, because I am "getting away with it" on Windows 2000 Server.

So whether I was using the cursors exactly in the correct way on Windows 2K or not, it was working, and the html elements were not disappearing.

Reply With Quote
  #5  
Old April 26th, 2004, 09:49 PM
Doug G Doug G is offline
Grumpier Old Moderator
ASP Free God 11th Plane (10000 - 10499 posts)
 
Join Date: Sep 2003
Posts: 10,143 Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level)Doug G User rank is First Lieutenant (10000 - 20000 Reputation Level) 
Time spent in forums: 3 Weeks 4 Days 23 h 19 m 36 sec
Reputation Power: 181
Recordsets, cursors and such are components of ADO, not ASP. You may have different versions of ADO on the different machines. MDAC is downloadable from http://www.microsoft.com/data if you need different versions.

Reply With Quote
Reply

Viewing: ASP Free ForumsSystem AdministrationMicrosoft IIS > IIS 6.0 and disappearing HTML Elements


Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump


Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 





© 2003-2008 by Developer Shed. All rights reserved. DS Cluster 4 hosted by Hostway
Stay green...Green IT