I have two IIS 7.0 applications running on the same server. I.e. http://website/application1 and http://website/application2. They both have seperate databases are seperate applications, but are physically located in the same "website" on the server. What happens is if I login into application1 and then log into application2 it kills my application1 session. Then if I log back into application1, it kills the application2 session. These applicatons run under seperate app pools and connect to completely different databases where the asp.net security tables are located. I am unsure why we are seeing this behavior.
...
Go to the complete details ...