Mixed ASP ASP.NET project migration - Inproc mode confusion

Feb 27 2018 11:14 PM
Hi all this is my first post here. I hope I do my best to describe my issue.
 
I'm migrating a very old mixed (ASP+ASP.NET) project from one server to another.
ASP subsite is at  http://mysite.com/aspsite
ASP.NET subsite is at http://mysite.com/aspdotnetsite 
 
 
Now, I thought I would only need to make changes in the SQLConnection string in web.config (located at root /).
 
  1. <appSettings>  
  2. <add key="ConnectionString" value="server=xx.xx.xx.xx;database=dbname;user id=dbuser;password=*********"/>  
  3. <add key="ConfirmationEmailId" value="[email protected]" /> <!-- Mail sent on comfirmation of Generate Certificate-->  
  4. <add key="fromEmail" value="[email protected]" />  
  5. <add key="huntsite" value="http://mysite.com/aspsite" />  
  6. </appSettings>  
However, apart from SQL Connection string and the later part of the web.config there is also InProc mode settings which again has a connection string
 
  1. <sessionState    
  2. mode="InProc"    
  3. stateConnectionString="tcpip=127.0.0.1:42424"    
  4. sqlConnectionString="data source=intranetserver;user id=user;password=pass"    
  5. cookieless="false"    
  6. timeout="20"    
  7. />    
Now this is in the parent folder.
 
Inside the /aspsite folder, there is another web.config which also has a session state details. 
  1. <sessionState   
  2.             mode="InProc"  
  3.             stateConnectionString="tcpip=127.0.0.1:42424"  
  4.             sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"  
  5.             cookieless="false"   
  6.             timeout="20"   
  7.     />  
 Also, I found that the Global.asax file contains the following(I dont know if this is related) 
  1. <%@ Application Codebehind="Global.asax.vb" Inherits="HWorkFlow.Global" %>  
 Correspondingly there is a HWorkFlow.dll in the /bin folder
 
 
Now the main issue is when I enter the login password on the page http://mysite.com/aspsite/login.asp it just keeps working on it indefinitely, it doesnt even timeout or display wrong login message or any other error message.