micster> Increasing the RAM allocation did nothing for us.  We are running with VMware GSX and allocated 1024M with little success.  I have watched the perf monitor throughout the entire TFS install, and it does not appear to be memory intensive.  The install does indeed timeout, at the same two places, but not because the machine was running out of memory resources and things were being swapped -- those services are not available/locatable.  This install is anything, but trivial.  It is especially frustrating to have an install that cannot be restarted -- and that leaves the machine in an indeterminate state.  There would be no reasonable to try this so many times w/o some virtualization software.

2)     

I'm still getting error 26105 when installing TFS Beta 3. The install works flawlessly when the machine is not a member of the company domain (Win 2000 AD) and I use workgroup accounts for TFSSETUP (local admin), TFSSERVICE and TFSREPORTS.

Those accounts exist on the domain as TFSSETUP1, TFSSERVICE1, TFSREPORTS1 and I've even tried adding TFSSETUP1 to the domain admins group in case there were permission issues.

As I said, install works just fine in a workgroup. In order to reinstall each time I have been reverting back to before Windows Sharepoint Services 2.0 before starting again, otherwise I get the standard "Sharepoint Services is not correctly configured" blurb.

It looks like TFS install creates LM\W3SVC\3 key as the 3rd identifier in IIS due to the fact that the Default website is 1, and Sharepoint is number 2. During the installation the VSMsiLog error log file points to the following failure:

MSI (s) (CC:34) [07:45:02:112]: Executing op: ActionStart(Name=WriteMetabaseChanges,Description=Writing Metabase Changes,)
MSI (s) (CC:34) [07:45:02:112]: Executing op: CustomActionSchedule(Action=WriteMetabaseChanges,ActionType=25601,Source=BinaryData,Target=**********,CustomActionData=**********)
MSI (s) (CC:0C) [07:45:02:112]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI46D.tmp, Entrypoint: WriteMetabaseChanges
WriteMetabaseChanges:  Error 0x8004e00f: failed to create web application: /LM/W3SVC/3/Root
MSI (s) (CC!B4) [07:45:27:598]: Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 26105. The arguments are: -2147164145, /LM/W3SVC/3/Root,

WriteMetabaseChanges:  Error 0x8004e00f: failed to create ASP App
MSI (s) (CC:34) [07:45:27:754]: User policy value 'DisableRollback' is 0
MSI (s) (CC:34) [07:45:27:754]: Machine policy value 'DisableRollback' is 0
Action ended 07:45:27: InstallFinalize. Return value 3.

And the dd_vsinstall log file has the following:

[10/18/05,07:32:31] vs70uimgr: Entering DisplayMessage() method.
[10/18/05,07:32:31] vs70uimgr: DisplayMessage_START:The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 26105.
[10/18/05,07:33:30] vs70uimgr: DisplayMessage_END:The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 26105.
[10/18/05,07:33:30] Setup.exe: AddGlobalCustomProperty
[10/18/05,07:33:30] Microsoft Visual Studio 2005 Team Foundation Server - ENU: ***ERRORLOG EVENT*** : ERROR:The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 26105.
[10/18/05,07:33:30] Setup.exe: AddGlobalCustomProperty
[10/18/05,07:33:30] Microsoft Visual Studio 2005 Team Foundation Server - ENU: ***ERRORLOG EVENT*** : ACTION FAILURE:Action ended 07:33:30: InstallFinalize. Return value 3.See MSI log for details.
[10/18/05,07:33:30] Setup.exe: GetGlobalCustomProperty({710A502B-4669-405C-A985-BA21545509BA})
[10/18/05,07:33:49] Setup.exe: AddGlobalCustomProperty
[10/18/05,07:33:49] Microsoft Visual Studio 2005 Team Foundation Server - ENU: ***ERRORLOG EVENT*** : ACTION FAILURE:Action ended 07:33:49: INSTALL. Return value 3.See MSI log for details.
[10/18/05,07:33:49] Microsoft Visual Studio 2005 Team Foundation Server - ENU: CRootComponent::Install(): Finished MSI Installation

It seems it's constantly battling to open the LM\W3SVC\3\Root key at which point it spits out the 26105 error. Now it would be fine if I didn't mind keeping the workgroup, but unfortunately, company policy means that it has to be on the domain to be on the company network, and I'm guessing there's potential global policy causing this problem I'm getting, but I'd love to know which one.

Any ideas?

Thanks in advance
Rob

I was able to get it to work, simply by tracking down the errors:

1) if you experience Problems with Analysis-Services, just use the SQL Studio to connect to it and go into the properties of the server, security tab. Remove all SIDs there, which could not be resolved. I added builtin/administrators aswell. I guess all this talk about needing SQL-Enterprise is just "a" way to fix - but in my case (I am using the DEV edition, which basically "is" the ent.) it didn't help either.

2) if setup then fails to startup the web-services, I did the following: I looked at the logs and found that http://tfs:8080/services/ created an error, so I went into IIS, found the source-dir and changed the corresponding web.config to show errors. I then called any one of the asmx files from the browser and found that the TFSService user did not have appropriate rights on the %TEMP% folder (c:\windows\temp, in my case). After I fixed that, it worked just fine.

During the installation of RC1 I have also encountered error 26105. I am currently deploying a TFS for a multinational and the biggest problem is the strict company security policies. With this I mean that company-wide all Windows 2003 Servers have less default privileges and a lot of disabled services than an out-of-the-box Windows 2003 installation. I have encountered several errors that were security related and that had to do with services being disabled including error 26105.

Finally the problem could be isolated to the Distributed Transaction Coordinater. For some reason it was not correctly installed.

I also encountered the error 26105 during the installation of RC1. I have been through all the forum entries there seems to be so many varying suggestions I'm unsure which one to try.

It reaches the same point everytime in the logs:

MSI (s) (E4:78) [15:58:24:437]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI40.tmp, Entrypoint: WriteMetabaseChanges
WriteMetabaseChanges: failed to open root key, retrying 0 time(s)...
WriteMetabaseChanges: Error 0x80110414: failed to create web application: /LM/W3SVC/3/Root

This is what's in the event log:

Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 26105. The arguments are: -2146368492, /LM/W3SVC/3/Root,

What I want to know is there an actual definition of what the error 26105 is about or what it usually indicates, I just find from reading all the possible solutions a lot of them seem unrelated. I don't want to waste time implementing a solution when I don't have that problem.

If anyone has any suggestions they will be greatly appreciated.

Thanks

Michelle

Hi All,

Error 26105...

Firstly - thanks for all your advice above on error 26105 - it has helped me to finally install the full TFS version, on a dual server, in an AD environment, with enforced group policies.

What has worked for me in finally installing -

1. Default directory for IIS - without the c:\inetpub\wwwroot, I seemed to have a slightly incomplete SharePoint service installation. While the SharePoint install didn't seem to mind, the TFS log files seemed to indicate errors on the stsadm.exe launch.

2. Ensuring that the COM+ System Application service is running. This was not for me, and when I enabled this (I've read so many postings recently, I can't recall where I saw this one) - however, it was the final change that got me through the 26105 error.

Hope this helps someone else!

Cheers! Corey.

When I install Team foundation server 2005 after completing all the prerequisites as a single server, an error appears after one fourth of the installation is complete stating that "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 26403."

Any information on this error will be great help.