I will soon be undergoing a project where I will be migrating four to five web applications, developed in classic ASP, from a single Windows Server 2000 to a web farm that will utilize two, Windows 2003 Servers.
All of the applications utilize user/session management and I know that ASP's built-in session management cannot be carried across multiple servers.
I've been researching products available for purchase out there on the web, which allows you to include new code, which overrides ASP's built-in session management, by using a database to store sessions.
They all advertise that their solutions simply require just one line of code to be added to each ASP pages that uses Sessions, without any other changes to the existing ASP code.
Can someone who has done something similar advise on their experience? Is this really as easy as they are advertising, or are there other issues to take into consideration? Code:
Is it possible to use session in web farm? Some say just use cookies because session does not work in web farm. But others say something about persist into SQL Sever, if this is true please tell me more about this approach.
It seems that I am assigning to the session rather than comparing against. I want to compare it in the first peice of code but it seems that I am assigning to it. When the user first requests the page they are not a member.Heres my code:
If(Session("IsMember") = "True") then 'Do Nothing End if
'should still not be True
If(Session("IsMember") = "True") then Response.write("IS TRUE") End If
'Response.write is working telling me that the first part of the code assigned to the session
I hav developed web application using ASP.net 2.0 there are just 2 pages only. Both are works fine in visual studio. But same when i run on IIS 5.1 ....the page without session variable works fine.
But the page with...even the Sub() with session variable won't works.....even it automatically reaches the last sub of the program.
What are the changes i hav to do in IIS / application or web.config file.
we've just set up a subdomain,'demos' for one of our projects that normally works fine. on the login page, if the user enters the correct username/pw, we write session info and then response.redirect to the home page. this works for on the normal site, but session state info is dying on the demo subdomain.
i'm sure the session info is being written since i can see it when i response.write the value. also, the response.redirect uses a relative path, so it's not that we're accidentally changing domains.
We have an ASP site that uses a MySQL db backend. Usename/Password authentication is stored in db tables. We are currently using session variables as a means for validation when the user navigates to new pages. Generally speaking, all this does and has worked fine
The issue is with abandoned sessions. For instance..
Joe user clicks the [X] in the upper right hand container, closing out IE or firefox. IIS will not terminate the session for ~ 20minutes(default), leaving these resources unavaliable.
In our situation, (and possibly a different issue) unless the user clicks the [EXIT] button we've provided, not only does the session persist for 20 minutes, the login state saved in the MySQL table stays locked. Before the User can log back in, they need to call us to reset their state.
I'm looking for some kind of solution to address a user exiting the application abnormally. I am not sure of the correct procedural methodology, but I would think that some kind of process or event trigger would run in the background looking to cleanup stale sessions. Code:
I have a problem where the session state will not be enabled on the server. We are using Framework 1.1, a non-Sql Server database, and will be moving the application to a web farm in the future. Is there any way to keep the session state on a relational database that is not Sql Server? If so, how?
I was thinking about disabling session state on some of my pages by doing this: <% @ EnableSessionState = False %>
My question is if I disable the session state will the page still reset the session timeout (eg. back to 20min. default) when that page is loaded? I need it to reset the session timeout.
I'm looking for a working example on how to share session state between ASP and ASP.NET.The solution of Y Yeung of Microsoft seemed to be a good solution but I did not get the asp part working.Anybody tips, tricks, links ?
I have been storing an object as session variable, such as
set session("oRS") = Server.CreateObject("ADODB.Recordset")
The page then redirects to another page. i need to use this object on the called page, but i encounter an error saying 'User session has expired.' On checking with the code, it was found that the sesion variable has not maintained its state for object 'oRS'. Although, session for string type variable are maintained.
i have a form having hyperlink calling the same page.on click on hyperlink i am
submitting form "Onclick=dosubmit(form1);" dosubmit{ document.form1.submit(); } but i am not able to retain session data.how can i retain session data.
We are running windows 2000 with dot.net framework 1.1 on IIS 5.1. This is an NLB architecture with the session being stored in an SQL DB. We have been coding and deploying using ASP.NET with no problems however the 'powers that be' have recently bought an online booking application which has been coded using classic asp.
We have set the session location in the machin config of the framework stating
mode="SQLServer". Will this ASP use this or continue to store the code InProc?
I am having trouble maintaining Session state between pages within my website. I had someone test the pages on their website and sessions state was maintained between pages, but for some reason, the same pages on my server do not. what might be happening?
I'm wanting to know how I can plug in a session state provider into ASP.NET. Currently you can use either the in-process, stateServer or SQL stores. Is the provider interface open and where is it documented? I've seen that Mono does provide their own state servers but I'm not sure if this is using standard provider interfaces.
Is it possible to store session state for each separate user in a separate process? We have a COM component that we want to use that is not thread safe and has to be isolated. We would like to store this in a separate process for each user.
I used KB 308150 as a guide to create a virtual directory shared by a few webstores that my company hosts. The virtual folder and websites reside on the same box. The shared directory includes code files used by all the webstores.
The problem - when a user adds items to the shopping cart, ***sometimes*** the session variables get reset and all cart information is lost. I can't consistently make the error occur - it seems to be random.
Also, if you have any different ideas on how to share code between many websites...I'm all ears.
wat i need to know urgently is whether Load Balancing will affect my session state for logging in. If it does affect, what should i do?
Currently, the Session("login") is set to false for not logged in and true for log in... pls help i need to know it urgently... in Global.asa its default is "false" Code:
At risk of being flamed for mentioning the N-word here ...
Has anybody yet cracked the knotty problem of sharing Session state between ASP and ASP.Net sites (within the same domain)?
Last time I looked, the two Session() mechanisms were totally divorced and separate, making step-by-step conversion of Session -dependent web sites from ASP to ASP.Net all but impossible.
To better manage our secure site we just separated the registration and checkout sections of our web into separate virtual directories. These new virtual directories are on the same server as the primary eCommerce website. This is an ASP site (not asp.net). When this version goes into production it will be on a 2003 server (IIS 6) with a SQL Server backend (located on a different server). Now when the main server passes control to one of the new virtual webs the session information is lost. I'm having problems finding information on the web as to how to maintain this information between the web and virtual directories. It's imperative that this information remain secure so query strings or anything that would pass visible data is not an option.
i have a problem with a web farm. an application asp net 1.1 that works in different servers.doesnt works in the web farm (4 servers balanced). The error it says is "System.Web.HttpCompileException: External component has thrown an exception" basically is a page that its requested in one server and served by other server and are different version of the application .. the technichal staff says its applied the same version in the four servers and i can believe them.
Im using classic ASP (3.0) and I have a web farm with 2 webservers (webserver A and webserver B, both windows server 2003). I do not want to store any client specific information on the webserver (therefore do not intend to use the session object- as you cannot gaurantee which server the user will go to). I want to store a small value (e.g. a Y/N value or an Id) on the client machine for the duration of their browsing session, hence I want to use a non persistent cookie (in client memory) not a persistent cookie that will be written to disk as a file.
Q. Therefore if I create a non persistent cookie (i.e. it resides in the client browsers memory) and set this when the user was on webserver A, can I read the value server side on subsequent requests even if the user is redirected back to webserver B? As the webservers are part of the same domain name Im assuming I can..?
Q. Using non persistent cookies (in client in memory) im assuming the session Id that gets created by IIS has no use, as I am using client side storage, hence it is worth disabling this on the webserver for performance reasons?
Q. Is there a way, when using non persistent cookies that the client user can see the values of this cookie client side, are their any downloadable tools for example they can run?
Im aware of the issues with size of using cookies and users can disable them, my question is more related to using them in a web farm. Im also not intended in the short term to upgrade to asp.net as Im aware there are alternatives for state storage in this. I hope someone can clarify these points for me. Note: I see many articles talking about cookies but none relating to web farms and cookies, those that do talk solely about the session object (Server side), none really go further to talk about (non persistent / persistent cookie usage with web farms client side.
I currently am using a script which submits full state names to a payment processor. However, the payment processor only accepts 2 digit state names. Does anyone have a premade code for asp that converts state names into 2 digit ones. Code:
how can i pass state for each user through pages without using session,cookies,hidden form fields,querystring or database, which knowledge base article 175167 refers? i don't want to build a form with hidden fields and get it posted on the client. it seems possible using server variables, response.addheader method, but how can i use it?
I am learning asp.net using Zak Ruvalcaba's book from Sitepoint. When trying to do the example on application state from chapter 11, i get the following error:
Object reference not set to an instance of an object.
Is there any way a Form can be made automatically not retain its field values after it has been succcessfully posted in classical ASP. Something like the way ASP.Net can perform state management in postbacks automatically.
how to find all the cities in the US and relate them to their state? I want to have a drop down that goes from state to city. i.e. I choose Illinois from a drop-down, then the next drop-down is populated with all the cities in Illinois.
I have all the states in my db, but how would I go about finding all the cities? I have been googling this for awhile, but no luck. Is it an xml feed?
I'm back to ASP for a short while and I was wondering how I could save the entire Application/Session-state to a file or database and how to read it back afterwards. I'd like to preserve the state inbetween service/server- restarts. I know how to do it in ASP.NET.
I have a form on a .asp page that when submitted via post to itself its values are grabbed by asp and put into an sql statement. From there the records are generated depending on the criteria selected in the form. What I would like some help or guidance is if no records match the criteria how can I generate a meesage that states which criteria in the request did not match.
So if the form submitted is looking for a home in Michigan, Ranch Style, with 2 car garage, 3 bedrooms, 2 baths, between 1000 to 1500 square feet and there is no record that matches that criteria a response is given that the reason for no match is because the 2 bath criteria didn't match or because the 2 bath and the square footage criteria didn't match.
I have the form working with asp already. When there is no record I have a simple statement that says "sorry, no homes matched your criteria" I would like to state why there was no match.
