Re: MOSS2007/WSS 3.0 Installation/Configuration Problems



OK - sorry for the wrap, but here is my IIS log. I cleared it before
making one request for the admin console. It prompted 3 times, and
then 401.1'd out:


#Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2006-07-15 03:37:11
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query
s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus
sc-win32-status
2006-07-15 03:37:11 W3SVC48396102 10.240.3.151 GET / - 38298 -
10.240.3.151
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
401 2 2148074254
2006-07-15 03:37:11 W3SVC48396102 10.240.3.151 GET / - 38298 -
10.240.3.151
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
401 1 0
2006-07-15 03:37:24 W3SVC48396102 10.240.3.151 GET / - 38298
mydomain\myid 10.240.3.151
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
200 0 0
2006-07-15 03:37:47 W3SVC48396102 10.240.3.151 GET /default.aspx -
38298 - 10.240.3.151
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
401 2 2148074254
2006-07-15 03:37:47 W3SVC48396102 10.240.3.151 GET /default.aspx -
38298 - 10.240.3.151
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
401 1 0
2006-07-15 03:37:47 W3SVC48396102 10.240.3.151 GET /default.aspx -
38298 - 10.240.3.151
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
401 1 2148074248


Any thoughts?

Thanks!
Chris


matt wrote:
Hi,

Not sure if this helps but I had a few headaches when setting up WSS 3.0
to start with. I will describe my situation and if it helps great!

So what I did exactly

1) Installed standalone WSS v3 in a VMWare Windows 2003 Server (Standard)
a) Win2k3 was joined to a workgroup and NOT a domain
2) At work the WSS v3 worked without issue.
3) At home IE sat around for ages then prompted for password. Sometimes
I could login sometimes not.
Sometimes I was logged in and then at some point I couldnt access WSS v3
again.

Root cause was that IE has a nice setting in advanced configuration to handle
integrated authentication
IE Options->Advanced Tab->Scroll down to Security->Enable Integrated Windows
Authentication (requires restart)

When I disabled this then all was well. I could log in without problem at
home and at work.

Another thing to double check would be the accounts that are used by the
application pools. Are they "Network Service"?

--Matt





OK - So now I tried refreshing my VM and installing MOSS from a clean
image. Same exact problem. I still get the 401.1 error, with no
messages in the Event Log.

AARGH!

Is there some way to figure out if the ASP.NET membership is the cause
of this, or some other permissions error for the ASP.NET Application
Pool user account? Didn't there used to be a tool to check
permissions on a web site?

Chris Koenig wrote:

That's the really weird part - when I've done trying to access the
site, there are *no* messages in the application or system logs, and
only success messages in the security log. That's why I think it
might have something to do with the ASP.NET
membership/personalization stuff...

I've had my VM rebuilt by our infrastructure team, and I'm going to
try a clean install this afternoon. I'd still like to know, though,
if anyone else has seen this problem as I fear I might be seeing it
again real soon...

Thanks!
Chris
Todd Klindt wrote:

Have you looked in the Security logs to see if there are any access
problems? After that I'd probably check the Application and System
logs to see if there are any clues there. I know the three or four
times that I've installed v3 it has went fairly smoothly. Once I
got all the freakin' requirements installed, that is. :)

tk
"Chris Koenig" <chris@xxxxxxxxxxxxx> wrote in message
news:1152683416.540388.110450@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Now that I have WSS 3.0 installed on my W2K3 server, I am unable to
get the administration panel to launch - I keep getting a 401.1
error after getting prompted 3 times for my ID and Password. From
the security logs, it looks like the authentication is working OK,
but it seems that something in the ASP.NET 2.0 membership system
isn't working quite right.

Anyone else run into this, or know what the real problem might be?

Thanks!
Chris

.



Relevant Pages

  • Re: MOSS2007/WSS 3.0 Installation/Configuration Problems
    ... Not sure if this helps but I had a few headaches when setting up WSS 3.0 to start with. ... Root cause was that IE has a nice setting in advanced configuration to handle integrated authentication ... Is there some way to figure out if the ASP.NET membership is the cause ... try a clean install this afternoon. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Use login control to limit access to certain pages
    ... Membership Database to store your users and want unauthenticated users to ... The resources are scattered as you said, ... I want to confirm which authentication type you are using? ... without validation when request path is in this XML file. ...
    (microsoft.public.dotnet.general)
  • Re: WSS 3.0 question
    ... I'll take a stab at WSS 3 again. ... Even if you decide to install SQL Server, the MSDE instance that is used by Monitoring and Reporting has to remain installed. ... SharePoint Products and Technologies Configuration ...
    (microsoft.public.windows.server.sbs)
  • RE: Forms Authentication vs MembershipProvider
    ... First, I'm glad that you've got custom membership provider working, great ... For Forms authentication and membershp service, ... authenticaiton) which is used to provide security authorization (protect ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: WSS 3.0 - WSUS and default web site issue in R2
    ... I'll post also on WSUS. ... How do you explain the fact that WSS 3.0 setup stop IIS Default web that run ... update clients after install WSS 3.0. ... This newsgroup is primarily for issues involving deployment, configuration, ...
    (microsoft.public.windows.server.sbs)