There was an error displayed but the account name was identical to my login name. I was really sure I had used the correct one in the configuration file. Another red face special.
Apart from that it won't work on my Windows 7 machine as it needs .NET 1.1. You have to do this on a windows 7 machine to install .net 1.1 http://blogs.iis.net/bills/archive/2008/06/02/installing-asp-net-1-1-with-ii s7-on-vista-and-windows-2008.aspx. Frankly I don't want to stuff up my windows 7 machine just to do this. I found an old XP Pro Clunker in a cupboard and hooked that up but it wanted to be authorized before one could use it. It is a legit copy but the network connection would not work. One could do it via the telephone but the code you have to write down it huge. I tried to use a virtual copy of XP (Windows 7 virtual machine) but I could not even see shares. I did manage to see my notebooks sql server 2008 instance but it still would not work. (login timeouts and nothing in a SQL Profiler trace) The fun of it all. Regards Peter -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Arjang Assadi Sent: Tuesday, 22 March 2011 1:59 PM To: ozDotNet Subject: Re: FW: ASP.NET application in IIS7 Hi Peter, That is stange, when running it on the local machine you should have seen an error message saying the login failed for the user Blah, etc. Was there no error being displayed? Regards Arjang On 22 March 2011 16:28, Peter Maddin <[email protected]> wrote: > I found the problem (me) after I put tracing in my code. > > It was a database login that had failed. > > > > If nothing else I have refreshed my knowledge on debugging ASP.NET. > > Its been several years since I last touched this. > > > > Regards Peter > > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Peter Maddin > Sent: Tuesday, 22 March 2011 11:49 AM > To: 'ozDotNet' > Subject: ASP.NET application in IIS7 > > > > I have an old (developed using ASP.Net 1.1 and VS2003) that they wanted some > performance issues tackled. > > This was an urgent job. They did not want to redevelop it to something more > recent, that might come later. > > > > I made my modifications on an old XP box. > > > > I thought I would try it on my Windows 7 notebook. > > > > I created an application virtual directory and pointed it to where my > ASP.NET code and forms were copied. > > > > Anonymous authentication is enabled and windows authentication disabled. > > Credentials to the ASP.NET folder is set to application pool identity. > > > > Check the application pool, the one to use for authentication is the > DefaultAppPool. > > The identity for this was set to localSystem. > > > > When I try and access the web site, I get the first page displayed but when > I put in my login credentials ( I am using my own authentication within the > site using a database table), > > It says that Login failed for my Windows Login account. > > > > Also database access uses a SQL Login account not a windows account. > > > > I dont want it to use my Windows Account. I want it to be anonymous. > > > > I tried changing the DefaultAppPool to use NetworkService and for my > application folder gave permission to NETWORK to access the folder. > > This made no difference. > > > > I have had a look at the IIS log file in C:\inetpub\logs\LogFiles\W3SVC1 > > And all it says is that a get for the page I see displayed had a status of > 200. > > > > Is there anything obvious before I start putting trace information in my > application? > > > > > > Regards Peter Maddin > Applications Development Officer > PathWest Laboratory Medicine WA > Phone : +618 6396 4285 > Mobile: 0414 240 307 > E-Mail : [email protected]; [email protected] > The contents of this e-mail transmission outside of the WAGHS network are > intended solely for the named recipient's), may be confidential, and may be > privileged or otherwise protected from disclosure in the public interest. > The use, reproduction, disclosure or distribution of the contents of this > e-mail transmission by any person other than the named recipient(s) is > prohibited. If you are not a named recipient please notify the sender > immediately. > > > >
