Beta2 woes.

Hot Topic

Serious problems with merging files
"object reference" error on project load
Web Test Transactions
Recomended installation order for VS2003 and VS2005 TS Beta2
Custom Exception causes "Not Authorized to View this page"
Project Creation Problem: Unable to connect to the Windows SharePoint Services
Version Tree Browser
Which versions are compatible with which versions??
Infopath Integration
Can't do Team Build with Tests

VS Team System

Beta 2 Team Suite - Designers
Alert receiving problem
Compare Utility should Ignore White Spaces
What are the improvements in beta3?
multi-platform project dependencies
Quick Search for Work Items
HttpSessionState Session Problem
Unit Test Sample won't download (Woodgrove Bank)
Missing database updates when running a Web Test
VSTS Ship Date?

Beta2 woes.

I managed to get Team Foundation Server and Team Suite installed, beta 2 with the April CTP.  I followed the pdf doc instructions closely and everything seemed to go fairly well, minus one issue as noted below.  I can get the suite to connect to the server, however, I get an error when creating a new project:

---begin Exception entry---
Time: 04/19/2005 12:54:38.667
Module: Initializer
Event Description: Initialization for plugin "Microsoft.Pcw.wss" failed with error: "The request failed with HTTP status 401: Unauthorized."
Exception Type: System.Net.WebException
Exception Message: The request failed with HTTP status 401: Unauthorized.
WebException: Response Status Code: Unauthorized
WebException: Response Status Message: Unauthorized
WebException: Status : ProtocolError
WebException : ToString() = System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.VisualStudio.ELead.WssProxy.UserGroup.GetUserInfo(String userLoginName)
   at Microsoft.VisualStudio.TeamSystem.ELead.ProjectCreationNew.WssSiteCreator.Initialize(ProjectCreationContext context)
   at Microsoft.VisualStudio.TeamSystem.ELead.ProjectCreationNew.PluginInitializer.InitializePlugins(MsfTemplate template, ProjectCreationContext context)
Stack Trace:
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.VisualStudio.ELead.WssProxy.UserGroup.GetUserInfo(String userLoginName)
   at Microsoft.VisualStudio.TeamSystem.ELead.ProjectCreationNew.WssSiteCreator.Initialize(ProjectCreationContext context)
   at Microsoft.VisualStudio.TeamSystem.ELead.ProjectCreationNew.PluginInitializer.InitializePlugins(MsfTemplate template, ProjectCreationContext context)
--- end Exception entry ---

This looks related to the only issue during the install and that was for installing sharepoint.  Sharepoint installed fine, however, when it brought up the browser I got and continue to get:

You are not authorized to view this page
You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept.

It appears sharepoint changed my default web site properties to not allow anonymous access, if I reenable anonymous access I do get a sharepoint page which states:

Access denied. You do not have permission to perform this action or access this resource.
Access requests are not enabled.

Project creation via the suite still fails with the 401 exception as noted above.

When I disable anonymous and turn on integrated windows authentication the sharepoint page seems fine and I'm able to create projects...

Is this the correct setup for sharepoint/team system   If so, I find it strange the install process didn't do the correct thing. Tongue Tied



Answer this question

Beta2 woes.

  • Franck EMSALLEM

    Thanks a ton buddy it solved my Project Server 2003 buddy, I was also getting
    "You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept."

    I guess Share Point Services had caused the bungle




  • MS MVP KenLin for VB.NET

    Sure, I should've included this info to begin with, but it was quite late.  Smile

    1).  Indeed Windows Server 2003 SP1, x86.
    2).  I installed Sharepoint services 2.0 via msdn (en_stsv2.exe), and then installed SP1 for it via windows update.
    3). This was a single server deployment.

    Unfortunately I wasn't able to locate the log file(s) requested.  I suspect I cleaned out the temp directory after I got it working.


  • Sung Hon Wu - MSFT

    Ok, I've just gone through an install on another machine with an identical setup.  However, this time, I installed stsv2.exe which is Sharepoint services 2.0 with SP1 bundled.  The install went fine and the permissions were set correctly.  Previously I made the assumption that en_stsv2.exe from MSDN also had SP1 bundled only to find out that I then had to get SP1 via Windows Update.  In that scenario the permissions were set correctly.  My fault for not following the directions explicitly. Sad


  • Juan Carlos Velez

    I'm trying to understand the details of what you did and what you are seeing.

    Can you let me know ...

    1. Were you using SP1 w/ W2K3
    2. Are you using WSS w/ SP1
    3. Was this 1 or 2 box TFS

    So you know, the installation of the middle-tier (or AT) does in fact set Windows Intergrated Authentication.  I'm surprised that you had to enable this.

    So, can you help me understand the order by which you installed the system

    Would be great if you could also provide me with the VSMsi*.log file found in the %temp% directory of the installing account.  It might be up a directory or two (depends on certain conditions)

  • Philippe Caron

    Hi there, I have the same problem as you did -

    I was following the single machine deployment

    I installed W2k3 Server enterprise, then setup AD, then SQL 2k5, then sharepoint (stsv2 with sp1 bundled) but when I accessed the sharepoint homepage I got the same security exception.

    I looked into this and found that SQL2k5 had configured the default website to ASP.NET v2 which broke sharepoint. VSTS didn't work of cause... and changing the ASP.NET config to v1.1 didn't work either because I assume some of the configuration would have been damaged.

    I figured I would check that sharepoint installed ok first, so I nuked my box and tried the same install but sharepoint before SQL2k5. Sharepoint now works because it's using .NET framework v1.1 and the rest of the install completed ok - but when I go to add a site in team system I get the following exception:

    .
    .
    .
    05/06/2005 10:01:09.546 | Module: Rosetta | Thread: 8 | Exiting Initialize for RosettaReportUploader
    05/06/2005 10:01:09.546 | Module: Initializer | Thread: 8 | Initialization for plugin "Microsoft.Pcw.Rosetta" succeeded
    05/06/2005 10:01:09.546 | Module: WSS | Thread: 8 | Entering Initialize in WssSiteCreator
    ---begin Exception entry---
    Time: 05/06/2005 10:01:09.656
    Module: Initializer
    Event Description: Initialization for plugin "Microsoft.Pcw.wss" failed with error: "The request failed with HTTP status 401: Unauthorized."
    Exception Type: System.Net.WebException
    .
    .
    .

    Now if I change the ASP.NET config for the default website to use v2 - sharepoint home site is broken (same as before, something to do with the webparts and v2 framework) but the Microsoft.Pcw.wss plugin initialization works and it completes this step and the site creation process starts - only problem is it breaks further on in the process:

    .
    .
    .
    05/06/2005 10:03:42.328 | Module: Engine | Task "Scc" completed with success | Completion time: 0 seconds
    05/06/2005 10:03:42.343 | Module: Engine | Thread: 9 | Running Task "WSS.WssPortal"
    05/06/2005 10:03:45.328 | Module: WssSiteCreator | Thread: 9 | Exception: System.Net.WebException: The request was aborted: The connection was closed unexpectedly.
       at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)
       at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32 size)
       at System.Xml.XmlUtf8RawTextWriter.FlushBuffer()
    .
    .
    .

    Any suggestions - I can include the full logs. If I have to do another clean install some advice upfront would really help!

    Thanks

    Justin
  • Beta2 woes.
Answer this question