Error 28100.Error loading Event web service.

Question

Hi,

  During installation I got "Error 28100.Error loading Event web service.". Any idea what is going wrong ? TFS is being installed on a Virtual Machine.
  Please feel free to contact me if you need any more information.

Thanks,
Bart

ps. Is it possible to upload the setup log ?

Answer 1

Are you attempting a single server or duel server TFS install? At what stage of the installation process are you getting the error? 
Easiest way is cut and paste the relevant error stack trace.

Answer 2

Hi Joe,

  Thanks for your response.
  I am installing the single server TFS and the error occurs at the end of the installation. Sharepoint and SQLServer are running as specified.The error stack trace in dd_vserror80.txt :

[09/26/05,15:01:24] Microsoft Visual Studio 2005 Team Foundation Server - ENU: [2] WARNING:Warning 32000. The Commandline '"c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" ...' returned non-zero value: -2.
[09/26/05,15:01:25] Microsoft Visual Studio 2005 Team Foundation Server - ENU: [2] WARNING:Warning 32000. The Commandline '"c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" ...' returned non-zero value: -2.
[09/26/05,15:01:27] Microsoft Visual Studio 2005 Team Foundation Server - ENU: [2] WARNING:Warning 32000. The Commandline '"c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" -o addpath -url http://localhost/ReportServer -type exclusion' returned non-zero value: -2130246318.
[09/26/05,15:01:29] Microsoft Visual Studio 2005 Team Foundation Server - ENU: [2] WARNING:Warning 32000. The Commandline '"c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" -o addpath -url http://localhost/Reports -type exclusion' returned non-zero value: -2130246318.
[09/26/05,15:07:28] Microsoft Visual Studio 2005 Team Foundation Server - ENU: [2] ERROR:Error 28100.Error loading Event web service.

Thanks,
Bart

Answer 3

1.  We haven't seen this error for a while.  What version of VSTF are you installing?
2. What version of WSS are you installing?  Did you install the stsv2.exe or did you upgrade to SP1

Answer 4

Hi Bruce,

  VSTF : beta 3
  WSS : stsv2.exe, no upgrade (i.e. I've updated with windowsupate)

  If you need more information, please feel free to contact me.

Thanks,
Bart

Answer 5

I have the same problem and mine is Beta 3 and WSS with SP1.

Answer 6

A couple of questions:
1. Was IIS installed before or after you _started_ to install SQL 2005?
2. Did you change the location of the default web site?

Thanks,
Scott

Answer 7

Hi Scott,

  1. IIS was installed before starting SQL2005
  2. The default web site was not changed

If necessary, I can redo the IIS - SQL 2005 installation.

Thanks,
Bart

Answer 8

Hi Eric,

  Did you find the cause of the error ?

Thanks,
Bart

http://www.xenopz.com/blog/bartdeboeck/

Answer 9

Hi,

  Is it advised to redo the complete installation of TFS on a clean system ? Will be at the Visual Studio 2005 Roadshow the day after tomorrow, I'd love to have a working TFS ...

Thanks,
Bart

Answer 10

I would say it's your best bet. The install guide supports "clean" installs rather than machines with previous installations.

From install guide:
This release only supports deployment of Team Foundation on "clean machines" (computers on which no other applications have been installed since installing the operating system). Upgrading from previous installations of Team Foundation Server (for example, Team Foundation Server Beta 2) is not supported.

Answer 11

my original install was on a clean machine, if the same error occurs again, I'll let you know

Thanks for the feedback,
Bart

Answer 12

No... I have tried number of different method but no luck. I previously had a VS 2005 Beta 2 bits but as Joe recommended I should start it from the scrach. I wish MS responses this issue promptly...

Eric

Answer 13

I'm having the same problem.  Completely clean machine, health checks pass fine, then partway through the install I get  "Error 28100. Error loading Event web service."

Answer 14

I went back to some lessons learned when installing tfs beta 2, one of which was to install wss before sql server (even though the install guide says to do it after).  I installed wss, stopped the default web site, set the sharepoint site to port 80, then installed sql server.  Then I manually configured reporting services to make sure the /reports and /reportserver virtual directories were under the sharepoint site, but not in the sharepoint application pool.  Tfs got further with the install this time before ending with an "error 28905.WiDbLoc: Could not list of fields to localize from the database", which I will post on a new thread.

Hope this works for someone.

Answer 15

did an install on a clean machine, same result :

[09/27/05,18:20:43] Microsoft Visual Studio 2005 Team Foundation Server - ENU: [2] WARNING:Warning 32000. The Commandline '"c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" ...' returned non-zero value: -2.
[09/27/05,18:20:45] Microsoft Visual Studio 2005 Team Foundation Server - ENU: [2] WARNING:Warning 32000. The Commandline '"c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" ...' returned non-zero value: -2.
[09/27/05,18:20:49] Microsoft Visual Studio 2005 Team Foundation Server - ENU: [2] WARNING:Warning 32000. The Commandline '"c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" -o addpath -url http://localhost/ReportServer -type exclusion' returned non-zero value: -2130246318.
[09/27/05,18:20:53] Microsoft Visual Studio 2005 Team Foundation Server - ENU: [2] WARNING:Warning 32000. The Commandline '"c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" -o addpath -url http://localhost/Reports -type exclusion' returned non-zero value: -2130246318.

Bart

Answer 16

Hi,

  I have a solution which did it on my machine :
http://www.xenopz.com/blog/bartdeboeck/PermaLink,guid,067f7541-88a2-449a-a4e2-5e1e3e706d22.aspx

  All comments are appreciated !

Bart

Answer 17

I have used the solution.
it did not solute the problem.

I use wss sp1(chinese) and English Language Pack.

Answer 18

Bart, your solution didn't help.

In my case, the "sptimer" service WAS running. I still restarted the IIS and hit Retry on TFS installation. I looked through the logfile and it had exactly the same error messages that was in your log. I also ran the stsadm with the same command line parameters and got the same error messages...

Weird. Still it doesn't work...

Answer 19

Hi Cae, Powerword,

  Are you doing the single server install on a virtual machine ?
  Sorry that I could not help you out :-(

Bart

Answer 20

Bart De Boeck wrote:

Are you doing the single server install on a virtual machine ?

I'm doing a Single server install on a normal pc with a clean installation of Windows Server 2003 SP1.

Answer 21

Bart,

My experience with this error was that it was solved when I started using the (in the installationguide) suggested 'tfs' account names.
http://bloggingabout.net/blogs/edward/archive/2005/09/27/9536.aspx

Regards,
Edward

Answer 22

I was having the same problem as well on a completely clean machine (so I thought).  I did the install twice and tried the other suggestions.  Turns out that the image my data center team puts on new servers has URLScan installed by default.  This will cause this error every time. 

Answer 23

I'm also getting this error.  Any tips from MS???
-s

Answer 24

Hi Jamie,

  Based on http://www.microsoft.com/technet/security/tools/urlscan.mspx I'd say that URLScan is a "standard tool" on IIS. How should we check the "URLScan causes error 28100" ?

Thanks,
Bart

Answer 25

I install TFS on a single normal server,but I got the error 28100.

now, I will try to install it on a virtual machine .

Answer 26

Helloooo!

You guys will love this.   Yesterday after repeated "Retry" attempts, this error persisted...  so I walk away from it.

Today, I hit the "Retry" button for the first time, and.. the install completed!

I'm not sure of the reason why, but, it seems that letting it "cool off" overnight allowed the setup to continue.

Who knows..  I'm stumped.
Of course, whether the wervices actually work properly is another story. :)

Cheers!
-Sean

Answer 27

It appears that the login account you use to install makes a big difference. I used the administrator acccount to install everything and ended up with the error.

At this point I switched to using the TFSSETUP account to do everything.

Unfortunately the rollback that the Team Foundation Server install does trashes WSS 2.0 so I had to uninstall and re-install that. After that I ran the install for TFS and it installed fine.

Hope this helps!

-Mike

Answer 28

Hi,

I tried installing TFS Beta3 on a clean installation of Windows Server 2003 R2 and I am getting the same error.

Regards,
Vikram

Answer 29

Hi Edward,

  Yep, you are right. Installing with the TFS account names did the job !

Thanks a lot !
Bart

ps. updated my blog with a reference to your entry

Answer 30

Hi Diver7,

  Indeed, the TFS accounts seems to solve the problem : http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=102333#102333

Thanks,
Bart

Answer 31

I had similar issues as well with installing TFS.  The first symptom was an unsuccessful install of Sql2005, specifically reporting services.  I was able to brute force manually install and configure SQL RS, but then was left with the 28100 error trying to install TFS.  I tried all recommendations on this forum and others, but was not successful.  I uninstalled sql 2005, sharepoint, .netfx 2.0 and then removed (uninstalled) the application role from my server -effectively uninstalling IIS.  I then followed the setup instructions to the letter and had success.  Team build install was unsuccessful on the first attempt, but the combination of a server restart and stopping the machine debug service enabled a successful install.

lesson learned - start with a clean machine. 
Here's my blog entry:  http://spaces.msn.com/members/jskelly/Blog/cns!1p3qATcT1xmNDC8ldqo1KbrA!124.entry


good luck

Jay Skelly
Microsoft Regional Director - Gulf Coast District

Answer 32

Hi all, i had this problem too, but my problem was that i had an Oracle instance installed on the same machine. The thing that blocked me from to get the installation finnished, was that Oracle had laied his big hands on address http://localhost:8080. But when i changed Oracle listening on 8080 to 8081, everything went fine.

Answer 33

Hi Bart,

I had the same problem that you had with all the exact reproduction that you have described. However I was using the accounts specified in the help. What seems to be the problem is that I left the accounts with blank passwords. It seems that IIS application pool can not handle accounts with blank passwords and the pool could not start. I set the passwords' length greater than 0 chars and it worked like a charm.

Best regards,
Martin Kulov
http://www.codeattest.com/blogs/martin

Answer 34

Just FYI ...

We didn't do any testing yet with R2 so it is hard to say if you will experience any issues
- marc
Marc Kuperstein [MSFT]

Answer 35

Martin,

Nice catch. I just asked our QA team to verify with blank passwords and when we repro we will take a bug to block on blank passwords.

- marc
Marc Kuperstein [MSFT]

Answer 36

FWIW, there is zero reason why using TFSSETUP or TFSSERVICE should work.  Internally we use a variety of accounts to test with.

Does your environment have some unique policies that are impacting you?

And I saw a post that indicates that a blank password will cause problems

Answer 37

I installed ISA 2004 on my machine. After look at the message above, I changed the portnumber of ISA Firewall service from 8080 to another,then the intallation completed.

maybe it is a solution. I hope it is helpful.

Answer 38

Hi,

Here is some nice feedback for Windows Server 2003 R2 then...

I have completed the successful installation of TFS Beta 3 on R2, the issue again was the UserAccounts with blank passwords. Editing the security policy also dint help and so I went ahead and added passwords to the three accounts and the Setup completed successfully.

This is a TFS Beta 3 install along with WSS 2.0 SP2.

Regards,
Vikram

Answer 39

Hi,

I tried installing TFS Beta3 on a clean installation of Windows Server 2003 and I am getting the same error.
I created the 3 TSaccounts with administrator permission.
Is there a solution to this issue?

Regards,
Giorgio Sardo

Answer 40

Giorgio,

Can you provide me with a little more information? Specifically, were you using a blank password or were the passwords non-blank
- marc
Marc Kuperstein [MSFT]

Answer 41

Of course I can! I used the three accounts
1)username:TSSETUP
   password: pincopallo

2)username:TSSERVICE
   password: pollopollo

3)username:TSREPORT
   password: frittofritto

Let me know if you need further informations.

Giorgio [MSA]

Answer 42

Hi,

i had the same error when installing TFS Beta 3 refresh version on a clean W2k3 SP1, SQL Server 2005 RTM and WSS SP2 machine.

I had to add the service accounts TFSService and TFSReports to the local Administrators group and the installation runs through. There should be a more detailed information, what kind of security rights each account needs and/or the setup program could set these rights himself.

Regards,
Werner

Answer 43

I received this same error message, but it was resolved differently. Looking at my event logs I noticed some errors saying it couldn't bind IIS to port 8080. Turns out that I had something on that port already. After changing the port used for that other app I was able to install just fine.

 

May I suggest that when TFS is checking if the machine is setup correctly (one of the first phases), that it check to see if something is on the ports that the system requries (there are plenty it requires).

Answer 44

I have yet one other suggestion that worked for me:

I noticed that in the vsmsilog that there was the typical asp.net error that was being scraped to the log:
"...The current custom error for this application prevent the details of app error from being viewed."

The error occured on the /Services vdir on the Team Foundation Server so I went there and set the customErrors mode to "Off" in the web.config.  After that I hit retry on the error and went back to the vsmsilog to see the real error which was:
Failed to load EventService proxy object: System.Web.Services.Protocols.SoapException:Server was unable to process request. ---> System.InvalidOperationException: Unable to generate a temporary class (result=1)
Error cs2001: Source file 'C:\windows\temp\<tempfilename>.cs' count not be found.....

This is nearly the same error that we got on xp sp2 when developing our own web services - the asp.net process identity doesn't have write access to the temp dir.
Not knowing what the identity of asp.net in 2.0, I first added the IWAM_ and TFSSERVICE account to the domain admins group, clicked retry but didn't work.  Then tried adding the IIS_WPG group directly to the \windows\temp folder with full access - clicked retry and the install seemed to continue and then finally finished successfully.

Hope that helps:
B

Answer 45

Thanks blevitt

i had the same error when installing TFS Beta 3 refresh version on a clean W2k3.

But when i adding the IIS_WPG group directly to the \windows\temp folder with full access and clicked retry - the install seemed to continue and then finally finished successfully.

Answer 46

I too am experiencing the 'Error 28100. Error loading Event web service.' problem with the Beta 3 refresh. I've tried all the suggestions in this thread and also those in the MSDN Product Feedback Centre but to no avail.

My setup scenario is this: Clean install on dual-CPU Dell server, Windows 2003 Standard edition with SP1, all other software as defined by the installation guide. I've been using SQL 2005 Enterprise edition as a post on Rob Caron's (I think) blog suggested that there is a problem running the beta 3 refresh on SQL 2005 Standard edition. The server is a member of our Windows domain and inherits many of its settings, including all firewall settings, through group policy. It also has dual NIC's, though one is currently disabled. I'm using three domain level accounts for the TFS process identities, using the account names as suggested in the installation guide and have configured group membership as required.

The installation initially failed the health check saying that Windows firewall was not installed, even though the firewall was installed and running. However all settings were configured by group policy and local exceptions were not permitted. I created a separate OU in Active Directory which does not inherit any of the domin group policies and moved the server into this OU. After updating the group policy the firewall and security policy are now under full local control and the health check passed with no problems reported. 

Somet time between 70-95% of the way through the install a message box pops up with the 28100 error; no matter how many times I click 'Retry' it never succeeds and the install eventually fails. The problem is repeatable. I performed the same install on a second, identical clean server which also did not inherit any settings from group policy, and the error appears exactly as on the first server. Thinking this may be an issue with the Beta 3 Refresh, I attempted to install Beta 3 on one of the servers (without reinstalling the OS first) and it failed in exactly the same way with the same error. I have successfully deployed beta 3 on other servers in a different Windows domain with no problems whatsoever so this leads me to suspect that it is a configuration problem with these particular servers and/or domain. I've compared the User Rights Assignments on the working Beta 3 server with the User Rights Assignments on the servers I'm trying to install Beta 3 Refresh on and they look pretty much the same to me - they certainly have the same entries under Log On Locally, Impersonate a client after authentication and Log on as a service for the TFS accounts.

If I look in the MSI log when the setup fails it records the problem as an HTTP 503 Service Unavailable error

BisSubscribe - Team Foundation Server BisSubscribe Tool
(c)Copyright, Microsoft Corporation, 2005. All rights reserved.
   
Failed to load EventService proxy object: The request failed with HTTP status 503: Service Unavailable..
11/17/05 09:41:19 DDSet_Status: Process returned 1120
11/17/05 09:41:19 DDSet_Status: Found the matching error code  for return value '1120' and it is: '28100'
11/17/05 09:41:19 DDSet_Error:  1120
MSI (s) (E0!7C) [09:41:25:457]: Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- Error 28100.Error loading Event web service.

However the curious thing is that if, whilst the error dialog is on screen and the install is still in progress, I use the Web browser on the server to browse to services/v1.0/EventService.asmx, I can happily call methods on the Web service (e.g. EventSubscriptions). When the setup fails with the HTTP 503/28100 error, nothing shows up in the IIS logs for the connection attempt; when I manually invoke the Event web service, the IIS logs shows all the events I would normally expect. A quick inspection of IIS shows that all app pools and Web sites are running correctly. It looks as if during the install they attempt to load the Event web service doesn't even get as far as the IIS server.

If anyone could shed any light on what's going on I'd be very grateful

------
David

Answer 47

I ran into the same error and discovered inadvertantly (via an event viewer error posted by sharepoint) that I had forgotten to uncheck the "User must change password at next login" box for the TFSSERVICE and TFSREPORTS user accounts that I created locally on the test server.  I had already unchecked this box for the TFSSETUP account.  FYI, I am using a single server for TFS running within Virtual Server 2005 standard edition and I am not using domain accounts at this point.  I got past this error after unchecking the box, so you should not have to add these accounts to the local admin group to get the install to work properly.  I also did not explicitly change the version of ASP.NET to 2.0 for the web sites in IIS, although ASP.NET 2.0 is installed on the machine and IIS sees it as an option.  My philosophy is to change as little as possble to get things running.

Note, I did get an additional error that popped up AFTER the "Setup completed successfully" window appeared.  It was a file-io exception.  Not sure why that popped up after I had already been informed that setup had completed successfully. 

Answer 48

A good suggestion from genuine_tuffguy, but unfortunately not the cause of my 28100 error. All three of the accounts I'm using are set to 'Password never expires' and I can happily (interactively) log on to the TFS server machine with all three accounts.

-----
David

Answer 49

I have a solution that is a combination of two described above.  My 28100 Error occured at the end of the TFS installation, and I had followed the instructions to the letter on a fresh install of W2k3 SP1.  The only deviation was using SQL 2005 Developer edition.

First, I tried Bart De Boeck's suggestion regarding starting the sptimer service.  (http://www.xenopz.com/blog/bartdeboeck/PermaLink,guid,067f7541-88a2-449a-a4e2-5e1e3e706d22.aspx)  When I ran "net start sptimer" it gave me an error about not being able to login.  Interesting.  My accounts were the suggested ones in the instructions, and did have passwords, so that wasn't an issue.  Then after reading genuine_tuffguy's suggestion, it made sense -- I forgot to uncheck "must change password on next login" and check "password never expires" for those accounts.  I tried changing just that, but by itself didn't get retry to work.  Then I did "net start sptimer" and it worked! Great!  But retry didn't work.  Looking into the service control panel, I saw there were one or two other services marked as automatic but not started -- TFSServerScheduler and Code Coverage Analysis Service.  I started those, then restarted IIS Admin Service, and viola!  Retry worked, install complete.

In short, after making sure your passwords are set up correctly, start/restart the appropriate services.

Answer 50

Hi!

Maybe it can be useful in single server setup scenarios to use the computer's hostname, instead of localhost, since if you've a configured IIS with 2 network cards and IIS is just listening on one a specific IP address, then localhost will fail and you'll receive the same error message for 28100.

Here is the snippet from the setup log:
[12/11/05,18:29:39] Microsoft Visual Studio 2005 Team Foundation Server - ENU: ***ERRORLOG EVENT*** : WARNING:Warning 32000. The Commandline '"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" ...' returned non-zero value: -2130246810.
[12/11/05,18:29:40] Setup.exe: AddGlobalCustomProperty
[12/11/05,18:29:40] Microsoft Visual Studio 2005 Team Foundation Server - ENU: ***ERRORLOG EVENT*** : WARNING:Warning 32000. The Commandline '"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" -o addpath -url http://localhost/ReportServer -type exclusion' returned non-zero value: -2130246810.
[12/11/05,18:29:41] Setup.exe: AddGlobalCustomProperty
[12/11/05,18:29:42] Microsoft Visual Studio 2005 Team Foundation Server - ENU: ***ERRORLOG EVENT*** : WARNING:Warning 32000. The Commandline '"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" -o addpath -url http://localhost/Reports -type exclusion' returned non-zero value: -2130246810.

Hope this helps and will be fixed.

Attila [MSFT]

Answer 51

I found similar with my IT group server image.  Clean Win2003 included UrlScan, followed install using domain accounts (different user names than install guide) an encountered 28100 error.  After uninstalling UrlScan 2.5, install was successful.

Answer 52

I HAVE THE SOLUTION, HAHAHA!!!

You need to follow the instructions from the Installation Guide from start to finish and you MUST do the following (if you didnt do the following, you should redo your entire setup starting with a clean box and reinstall the OS) -

Important
You must install Windows SharePoint Services using the Server Farm option. This configures Windows SharePoint Services to use a remote SQL Server. Later, Team Foundation Server Setup will configure Windows SharePoint Services to use the same SQL Server instance as the rest of Team Foundation Server.

Hope this helps all you guys out!!!

Answer 53

I went through all of the suggestions here until I remembered I had Source Offsite hanging off port 8080 - durrr!

Answer 54

Today I did my first install of TFS on a clean Windows 2003, SP1 vmware virtual machine. It's in a workgroup, with IIS installed, then Sql 2005 Enterprise, the Sharepoint Services with SP2.  Then I began the TFS, Beta 3. Everything passed clean as a whistle, and then I got the error message that is the subject of this Message. Anyone found how to get around this issue?

Bill

 

 

Answer 55

Martin -- you are a genius!. I also used blank passwords for all three accounts - this is Beta software and I'm installing it all on one machine in a workgroup for testing -- so why not! When I set each of the 3 passwords to the letter "a" the TFS install finished beautifully!

2 barks and a tail for your suggestion!

Barkingdog

Answer 56

It has taken me two days to install TFS Beta Refresh 3 and get a project created. Without going into gory detail of the problems (well documented above) that I encountered here are a couple of tips:

 

Create 3 local user accounts TFSSETUP, TFSSERVICES AND TFSREPORTS. Use TFSSETUP to set up Windows ShairPoint Services (2.0 SP2 in my case) and Team Foundation (Beta Refresh 3 in my case) with this account. You should be good to go.

 

But I ran into a nasty problem. For some reason (if WSS is reinstalled multiple times … or what ever) the TFS registers the WSS Services with the wrong port number! This will cause the project creation process to fail.

 

Solution on the machine that WSS was installed navigate to http://localhost:8080/services/v1.0/Registration.asmx

And click invoke … Search the resulting xml for the string WssAdmin … below this line you should see something like http://<YourServerName>:17012/_vti_adm/admin.asmx Now all you have to do is make sure that 17012 is the same port that is used by the WSS Administrators site. Simply go to IIS and change the port number.

 

Hope this helps

 

JR

Answer 57

finnally I resolve same problem adding IIS_WPG group to \windows\temp too.

 

thanks

Answer 58

Do you mean these...
A user account to run setup (for example, Domain\TFSSETUP).

A user account to run Team Foundation services (for example, Domain\TFSSERVICE).

A user account to access SQL Server Reporting Services data sources (for example, Domain\TFSREPORTS).

As I have tried an install on a clean machine and got the same error.
Would be nice with the beta relases to have script that the testers use, not sample names (and they dont work) but the ones they used. This of course will not expose probs back to MS.

Answer 59

Hi,
I had install successful in the first time. After i removed  and install again, it made that error, i do'nt know how to fix,

I remove all app (vs2005, sql2005, Windows SharePoint Services) and reinstall but still fail. (also add IIS_WPG roles temp folder)

(i install the latest version of  Team Foundation Server)

Answer 60

I also have this issue, and have attempted every fix/solution on the board. There is a slight variation in that when I install WSS, it tells me I need to rerun the asp_net config for 1_1_4xxx. However, the config page still appears so I move forward. The event log brings up the following 3 entries (any help would be greatly appreciated):

first :

Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- Error 28100.Error loading Event web service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Then :

An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 3/13/2006 2:19:22 PM
Machine: GHGDEV
Application Domain: /LM/W3SVC/2/Root/services-1-127867308052148773
Assembly: Microsoft.TeamFoundation.Server, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
  Process Name: w3wp
  Process Id: 1192
  Thread Id: 5376
  Account name: GHG\tfsservice

Detailed Message: TF50212: Missing setting in Web.Config: BisDomainUrl. Defaulting to:

And finally :

An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 3/13/2006 2:19:22 PM
Machine: GHGDEV
Application Domain: /LM/W3SVC/2/Root/services-1-127867308052148773
Assembly: Microsoft.TeamFoundation.Server, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
  Process Name: w3wp
  Process Id: 1192
  Thread Id: 5376
  Account name: GHG\tfsservice

Detailed Message: A crash report for this problem was recently created; a new crash report for this occurrence of the problem is not being created. This problem has occurred 18 times.
Web Request Details
    Url: http://ghgdev:8080/Services/v1.0/ServerStatus.asmx [method: POST]
    User Agent: Team Foundation (BisSubscribe.exe, 8.0.50727.43)
    Headers: Content-Length=354&Content-Type=text%2fxml%3b+charset%3dutf-8&Accept-Encoding=gzip%2cgzip%2cgzip&Accept-Language=en-US&Authorization=NTLM+TlRMTVNTUAADAAAAAAAAAEgAAAAAAAAASAAAAAAAAABIAAAAAAAAAEgAAAAAAAAASAAAAAAAAABIAAAANcKI4gUCzg4AAAAP&Expect=100-continue&Host=ghgdev%3a8080&User-Agent=Team+Foundation+(BisSubscribe.exe%2c+8.0.50727.43)&X-TFS-Version=1.0.0.0&SOAPAction=%22http%3a%2f%2fschemas.microsoft.com%2fTeamFoundation%2f2005%2f06%2fServices%2fServerStatus%2f02%2fCheckAuthentication%22
    Path: /Services/v1.0/ServerStatus.asmx
    Local Request: True
    Host Address: 172.21.140.72
    User: GHG\tfssetup [authentication type: NTLM]

Exception Message: Value cannot be null.
Parameter name: absoluteUrl (type ArgumentNullException)

Exception Stack Trace:    at Microsoft.TeamFoundation.Server.ProxyUtilities.GetServerUrl(String absoluteUrl)
   at Microsoft.TeamFoundation.Proxy.BisRegistrationService.ExpandRelativeUrls(RegistrationEntry[] entries, String tfsServerUrl)
   at Microsoft.TeamFoundation.Server.Plugin.InitializePlugins()
   at Microsoft.TeamFoundation.Server.Global.EnsureInitialized()
   at Microsoft.TeamFoundation.Server.Global.Application_BeginRequest(Object sender, EventArgs e)
   at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Answer 61

PLEASE HELP. In my case, two services, TFS Services and code coverage analysis sevices, can not be started using TFSSERVICE account.

The event log says:

事件类型: 警告
事件来源: ASP.NET 2.0.50727.0
事件种类: Web Event
事件 ID: 1310
日期:  2006-6-20
事件:  22:13:54
用户:  N/A
计算机: IDEAL170
描述:
Event code: 3006
Event message: A parser error has occurred.
Event time: 2006-6-20 22:13:54
Event time (UTC): 2006-6-20 14:13:54
Event ID: 0e74b92d76594b8e83bdf1e018bc2a8a
Event sequence: 1
Event occurrence: 1
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/3/Root/Warehouse-1-127952864337656250
    Trust level: Full
    Application Virtual Path: /Warehouse
    Application Path: C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Warehouse\
    Machine name: IDEAL170
 
Process information:
    Process ID: 5648
    Process name: w3wp.exe
    Account name: IDEAL170\TFSSERVICE
 
Exception information:
    Exception type: HttpException
    Exception message: Could not load type 'Microsoft.TeamFoundation.Warehouse.Global'.
 
Request information:
    Request URL: http://ideal170:8080/Warehouse/v1.0/WarehouseController.asmx
    Request path: /Warehouse/v1.0/WarehouseController.asmx
    User host address: 132.159.175.170
    User: 
    Is authenticated: False
    Authentication Type: 
    Thread account name: IDEAL170\TFSSERVICE
 
Thread information:
    Thread ID: 1
    Thread account name: IDEAL170\TFSSERVICE
    Is impersonating: False
    Stack trace:    at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException()
   at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)
 
 
Custom event details:

有关更多信息，请参阅在 http://go.microsoft.com/fwlink/events.asp 的帮助和支持中心。