Event log errors RTM Workgroup edition

Question

I have just installed the workgroup edition on a fresh installation of Windows Server 2003 R2.

I'm getting the following errors in the application event log on boot:

1) MS SQL Server - Failure Audit - Event ID 18456
   "Login failed for user 'domain\tfsservice'.
   User: TFSSERVICE

Followed by

2) Windows SharePoint Services 2.0 - Error - Event ID 1000

#50070: Unable to connect to the database STS_Config_TFS on THUNDER. Check the database connection information and make sure that the database server is running.

 

Any ideas?

Regards

Phil Lee

Answer 1

How are you running the database?  Is it running as LocalService?  If not, you should run that way before you install any of the other software.

 

As for the SharePoint error, I'm thinking that this is probably related to the SQL permissions.  Depending on when this occurred WSS is trying to connect to its configuration database and getting a refusal.

Let me know more details,

marc

Answer 2

Marc,

yes the SharePoint error follows directly the SQL error.  The sequence happens twice  on boot up.  I haven't started using TFS yet until I'm happy it's installed correctly.

I installed SQL 2005 standard edition using the provided answer file.  If I look in SQL configuration manager all services are running as LocalSystem except for Integration Services which is running as NT AUTHORITY\NetworkService.

One other point is that although Windows Firewall was running and had exceptions enabled the SQL installation didn't add any exceptions.  I had to add them manually.

 

Answer 3

I have same problem with RC

Answer 4

I have just uninstalled and reinstalled TFS (I didn't uninstall IIS).

I still get exactly the same errors in the event log.  Is this a problem or not?  If it is how do I diagnose the cause and/or fix it?

Answer 5

Okay... so you are installing Workgroup edition.  This is a single server deployment only install.  This also means that there will not be any Firewall exceptions because Sql will reside on the same box as the AT.

Can we get the following confirmed?

1. Are we installing Single Server?
2. Are we using machine accounts?  (workgroup edition right?)

 

Answer 6

Yes it's single server only. 

No I'm using domain accounts the same as in the betas. 

 

Answer 7

Okay.  From the event log, it says 'domain\tfsservice'.  I expect that "domain" would be computer name.  If it isn't, then it is using the wrong account.

Now, what we need to do is determine the 'domain\tfsservice' and ensure that it has the correct permissions on the sql server. 

Once we have confirmed that, we will need to make sure STS_Config_TFS is in the database and that the service has rights to that particular database.

Technically, this would all be set up correctly by the setup.  What version (Beta3, RC, RTM) are we using?  If it isn't RTM, can we do a clean re-install with RTM?

Answer 8

Bruce,

I will restate more clearly what my installation is:

1) Windows Server 2003 R2 fresh installation, part of a domain

2) TFS workgroup edition (RTM) downloaded from MSDN (en_vs_2005_wgp.iso).

Single server installation using domain accounts - it's the workgroup edition, not installed in workgroup mode.

3) TFS accounts setup in the domain, and tfssetup account added to local administrators group of the TFS server.

4) Sorry for the confusion saying 'domain\tfsservice'.  Yes domain is my domain name name (not the computer name).

5) I have already done an uninstall/reinstall, but I'm willing to try again.

As you say it's probably a simple permissions problem.  Here's a list of all the event log errors I'm seeing:

These appear when the server is restarted:

Application Event Log

1) Source: Tfs, Type: Error, ID 3059

TF53010: 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): 24/03/2006 08:50:30

Machine: THUNDER

Application Domain: TFSServerScheduler.exe

Assembly: Microsoft.TeamFoundation.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727

Process Details:

Process Name: TFSServerScheduler

Process Id: 1320

Thread Id: 1832

Account name: PJLCONSULTANTS\tfsservice

Detailed Message: TF50801: The TFSServerScheduler service did not initialize. The Team Foundation Registration Service returned the following error: Unable to connect to the remote server

For more information, see Help and Support Center at

2) Source: MSSQLSERVER: Failure Audit, ID=18456

Login failed for user 'PJLCONSULTANTS\tfsservice'. [CLIENT: 192.168.1.32]

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

3) Source: Windows Sharepoint Services: ID=1000

#50070: Unable to connect to the database STS_Config_TFS on THUNDER. Check the database connection information and make sure that the database server is running.

Errors 2) and 3) are repeated.

Interestingly the Event Log errors are interspersed with various Information event log items from SQL regarding startup.  I notice that the STS_Config_TFS database isn't started until after the second set of errors 2) and 3).  Shouldn't Windows Sharepoint have a dependency on SQL?

Security Event Log: No problems

System Event Log: No problems during startup.  However I do get this error occasionally - not sure what triggers it

Source: DCOM, Event ID 10016, User: NT AUTHORITY\NETWORK SERVICE

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{BA126AD1-2166-11D1-B1D0-00805FC1270E}

to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.

Answer 9

To all that are seeing this error, is this only on a restart and not a repeated event?  I have seen these types of errors when Sql has not fully started yet (hence the logon failure).  Can you browse to the Sharepoint Admin site or http://localhost with error? 

Thanks,

Brad

Answer 10

Brad,

yes I can browse the admin site ok.

Regards

Phil

Answer 11

Did you get this problem resolved? I'm running into a very similar issue.

Answer 12

No, I haven't resolved it but it doesn't seem to be a problem.

Answer 13

Hi all,

When starting the machine, SQL always goes into recovery mode and checks all "pieces" of itself including all databases.  If Sharepoint or any other service tries to contact SQL before it is finished with this process, you will see these errors in the eventlog at startup.

These errors are only an issue if your server does not work once the server is up and running.  Does anybody have that problem?

Brad

Answer 14

Hi,

experienced the same problem with TFS RTM WGP in a single server deployment using domain accounts for the service accounts.

However, at least at this time, TFS seems to work correctly when up and running.

Harald.

PS: I would be happy if there were any solution to solve this, even if it currently does not impact TFS functionality. Otherwise I would have to instruct all server operators to ignore this combination of event log entires during startup.

Answer 15

Hello All,

I'm having the same problem with the trial version on a fresh install of 2003 R2, SQL Server 2005 Trial on a single server installation.  A quick look at the security in the STS_Config_TFS and STS_Content_TFS databases shows that the TFSSERVICE user is not defined.   In fact, no users other than the dbo, guest, INFORMATION_SCHEMA and sys are defined.

Seems like the installer missed a step.   However, it's not clear how the TFSSERVICE should be defined.

Will

Answer 16

As mentioned in a previous post, this seems like a race condition between SQL Server and Sharepoint.   In my situation, I see this sequence of events:

Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 18456
Date:  4/26/2006
Time:  10:20:51 AM
User:  HA01TFS\TFSSERVICE
Computer: HA01TFS
Description:
Login failed for user 'HA01TFS\TFSSERVICE'. [CLIENT: 192.168.1.69]

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

Followed by:

Event Type: Error
Event Source: Windows SharePoint Services 2.0
Event Category: None
Event ID: 1000
Date:  4/26/2006
Time:  10:20:51 AM
User:  N/A
Computer: HA01TFS
Description:
#50070: Unable to connect to the database STS_Config_TFS on HA01TFS.  Check the database connection information and make sure that the database server is running.

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

Followed by:

Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17137
Date:  4/26/2006
Time:  10:20:54 AM
User:  N/A
Computer: HA01TFS
Description:
Starting up database 'STS_Config_TFS'.

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

Answer 17

phillee wrote:

Interestingly the Event Log errors are interspersed with various Information event log items from SQL regarding startup.  I notice that the STS_Config_TFS database isn't started until after the second set of errors 2) and 3).  Shouldn't Windows Sharepoint have a dependency on SQL? Security Event Log: No problems System Event Log: No problems during startup.  However I do get this error occasionally - not sure what triggers it Source: DCOM, Event ID 10016, User: NT AUTHORITY\NETWORK SERVICE The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {BA126AD1-2166-11D1-B1D0-00805FC1270E} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.

Check out this blog post.  It refers to B3R but it may still apply to RTM. 

Sounds like a permission isn't getting set correctly. 

I had this same error on a two server upgrade to RTM but it may have been an existing condition on B3R & RC that came along with the upgrade.

Answer 18

Hi I think this is a bug :-)

This because there are no explicit dependencies between SQL Server services and TFS Services. Therefore there is no guarantee that SQL Server is started before TFS Services.

In your case and In my case, I can see in the event log that TFS is started before SQL Server.

Is there a web page where I should log this issue so that it can be addressed?

Thanks in advance,

Steeve.

 

Answer 19

I also have the same problem,  with Windows 2003 R2, TFS with SQL 2005 SP1