Note that there are some explanatory texts on larger screens.

plurals
  1. POIIS 7.5 only allows one user to view web site
    primarykey
    data
    text
    <p>I have a web site developed in VS2010 Framework 4.0 published to a Windows 2008 R2 server running IIS 7.5 (As a bit of side info - I have a copy of the same site (apart, obviously, from the Framework) developed in VS2005 Framework 2.0 published on a Windows 2003 server that works perfectly.)</p> <p>When I publish the Framework 4.0 site to the Windows 2008 server, it only works for the first person that tries to access the site. E.g. I publish it to the server, and then access the site from my PC using IE. Someone at the desk next to me tries to access the site and nothing happens - the browser progress bar just chuggs along going nowhere - no errors, no errors on the server, nothing. If I log out and the person at the desk next to me accesses the site - it works fine. If I then try to access it - the browser just hangs and goes nowhere. So, only one person is allowed to use this web site! (It's on an intranet). If, while someone is using the site, I go into IIS and browse the site - it connects perfectly.</p> <p>The site has a global.asax which calls a stored procedure to do some log ins and sets 5 session variables.</p> <p>Any ideas please. It's driving me nuts and has caused me to go back to VS2005 and Framework 2.0</p> <p>** Added code from comment below**</p> <pre><code>string CurrUser = System.Security.Principal.WindowsIdentity.GetCurrent().Name.ToString().Replace("\\"‌​, "/"); CPDataAccess.DataAccess da = new CPDataAccess.DataAccess(); System.Data.DataView dvGetUserCurrWP; dvGetUserCurrWP = da.GetUserCurrWP(CurrUser); int somerows = dvGetUserCurrWP.Count; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload