Problem with Areas and Iterations not being updated in work items

moke48462

After creating a new area or iteration, the new item does not appear in the area drop down used when creating a new work item in Visual Studio.

• I verified this behavior (create an area, but it is not visible at the work item level) is reproducible from Visual Studio, Excel and MS Project.
• I deleted my local cache (C:\Documents and Settings\<userid>\Local Settings\Application Data\Microsoft\Team Foundation\1.0\Cache), re-started Visual Studio, but no dice.
• When I expand the dimensions in the TFSWarehouse, the new area appears as a dimension.

After some time (3 to 4 hours), the areas and iterations become available and are visible from the work item view.

Why are areas and iterations not immediately available Some fun facts about our tfs server.

• the server is in a single server configuration (application and data tier) on the same machine
• I recently moved the tfs server from serverA to serverB. All other features seem to be working correctly.
• TFS server has SP1 applied, and my workstation has VS 2005 Team Suite with SP1 applied.

This is really annoying because I don't have a work-around other than just to wait for some time.

James Manning - MSFT

I'm assuming you had VS shut down while you killed the cache dir

moke

I just double checked by shutting down vs, deleting the cache, re-opened VS. But the area I added still does not appear.

Dan Kershaw

Sorry for the problems you are seeing with this.

Are there any event log errors or warnings on the Application Tier

Thanks,

Dan Kershaw

Your issue might be related to the following posting:

http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=1032208&SiteID=1

It has links to some scripts that you might want to try running to help diagnose the problems.

Hope this helps,

moke

There are two identical Failure Audit entries in the Security log that occur every 1/2 hour (like a scheduled job is failing). Both messages have the same contents like the one below.

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 2/28/2007
Time: 9:30:00 AM
User: NT AUTHORITY\SYSTEM
Computer: <computerName>
Description:
Logon Failure:
Reason: An error occurred during logon
User Name:
Domain:
Logon Type: 3
Logon Process: Authz
Authentication Package: Kerberos
Workstation Name: <computerName>
Status code: 0xC000040A
Substatus code: 0x0
Caller User Name: <computerName>$
Caller Domain: <domain>
Caller Logon ID: (0x0,0x3E7)
Caller Process ID: 1784
Transited Services: -
Source Network Address: -
Source Port: -

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

moke

Here are the results from one of the queries mentioned in a post you referenced. If I understand the results correctly, this confirms there is a synchronization problem. I am not sure if this matters, but the original TFS install was workgroup. Now, we are running the trial edition until we get our key from purchasing.

set nocount on

select next_id - 1 as GSSMaxIdenditySeqId from TFSIntegration..tbl_sequence_ids where name = 'identity_cache'

select max(seqid) as WITMaxIdentitySeqId from TFSWorkItemTracking..ADObjects

select next_id - 1 as GSSMaxNodeSeqId from TFSIntegration..tbl_sequence_ids where name = 'css_node'

select max(seqid) as WITMaxNodeSeqId from TFSWorkItemTracking..TreeNodes

select next_id - 1 as GSSMaxAclSeqId from TFSIntegration..tbl_sequence_ids where name = 'acl'

select max(sequence_id) as GSSMaxAclSeqId from TfsIntegration..tbl_security_acls where action_id like '%WORK_ITEM%'

select max(seqid) as WITMaxAclSeqId from TfsWorkItemTracking..Rules

----------------------------------------------------- Query results ----------------------------------------------------- -----------------------------------------------------

GSSMaxIdenditySeqId
-------------------
130

WITMaxIdentitySeqId
-------------------
130

GSSMaxNodeSeqId
---------------
194

WITMaxNodeSeqId
---------------
193

GSSMaxAclSeqId
--------------
276

GSSMaxAclSeqId
--------------
139

WITMaxAclSeqId
--------------
178

moke

I still don't have a work-around for this issue.  Anyone have an idea

Dan Kershaw

Sorry for your issues. We're a little perplexed here.

Generally syncing is either completely broken or it works just fine. You seem to have a hybrid where it will work, but takes some time to sync.

Normally any change to areas and iteration fires an event from the group security system (GSS) to the work item tracking (WIT) system, so that these system stay in sync. However if there is something wrong with the eventing sub-system these events may get lost, and changes may not update. When the system is not being used, ASP.Net shuts down the TFS app pool after 20 minutes. The TFSScheduler restarts the TFS app pool every hour, at which point WIT asks GSS for anything new, and then the areas and iterations is brought up to date. This *might* explain the delay.

Can you double check the NT event log on the Application tier machine for any suspicious TFS Service events (The security audit events look like something unrelated).

Is there anything else unusual about your server configuration

Can you run the following SQL script on the DT too:

select * from TfsIntegration.dbo.tbl_subscription where delivery_type = 2

Can you look at the address for the "SyncEventsListner". Does anything look unusual about it

Thanks,

moke

Here are the results of the query. You can copy the contents below and paste into Excel, then use "Text to Columns" feature to parse this text (there is probably a better way, but this should be sufficient).

id,event_type,expression,subscriber,schedule,delivery_type,address,
1,BuildCompletionEvent,,<sid>,0,2,http://<servername>:8080/WorkItemTracking/v1.0/Integration.asmx,
2,DataChangedEvent,,<sid>,0,2,http://<servername>:8080/WorkItemTracking/V1.0/SyncEventsListener.asmx, 3,ProjectCreatedEvent,,<sid>,0,2,http://<servername>:8080/Warehouse/v1.0/warehousecontroller.asmx, 4,DataChangedEvent,,<sid>,0,2,http://<servername>:8080/VersionControl/V1.0/Integration.asmx, 8,CheckinEvent,,<sid>,0,2,http://<servername>:8080/TeamCI/notify.asmx, 11,CheckinEvent,,<sid>,0,2,http://<servername>:80/Automaton/Service.asmx, 12,ProjectCreatedEvent,,<sid>,0,2,http://<servername>:80/Automaton/Service.asmx, 13,ProjectDeletedEvent,,<sid>,0,2,http://<servername>:80/Automaton/Service.asmx,

I did notice a difference between my old and new tfs server. (The problem described above occurs on the new tfs server).

I can remote into old tfs server using my local account (this tfs server is configured in workgroup), open a web browser, and navigatet to http://<oldservername>:8080/VersionControl/V1.0/Integration.asmx without getting prompted for credentials.

When I remote into the new tfs server using my domain acount (this tfs server is part of a domain), open a web browser, and navigate to the similar path (http://<newservername>:8080/VersionControl/V1.0/Integration.asmx), I get prompted for and have to provide my domain credentials.

This behavior may be completely unrelated but is a difference in behavior that I noticed.

Dan Kershaw

Thanks - and you see nothing unusual (TFS Services) in the NT Event log on the application tier

I'll ask folks if what you are reporting seems unusual.

moke

No, there is nothing unusual in the event logs. Here are some of the messages (related to TFS) in the event viewer in chronological order. I do not see anything "unusual".

Event Type: Information
Event Source: MSFTESQL
Event Category: MSFTESQL Service
Event ID: 4103
Date: 3/7/2007
Time: 12:20:11 PM
User: N/A
Computer: <servername>
Description:
Component: MicrosoftIndexer
A master merge has completed for catalog SQLFT0000700005.

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

Event Type: Information
Event Source: MSFTESQL
Event Category: MSFTESQL Service
Event ID: 4164
Date: 3/7/2007
Time: 12:20:11 PM
User: N/A
Computer: <servername>
Description:
Component: MicrosoftIndexer
Catalog: SQLFT0000700005. A master merge was started due to an external request.

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

Event Type: Information
Event Source: TFS Warehouse
Event Category: None
Event ID: 9001
Date: 3/7/2007
Time: 7:49:26 AM
User: N/A
Computer: <servername>
Description:
Warehouse controller application started.

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

Event Type: Information
Event Source: TFS Version Control
Event Category: None
Event ID: 9001
Date: 3/7/2007
Time: 7:37:08 AM
User: N/A
Computer: <servername>
Description:
TF10181: The Team Foundation source control server TfsVersionControl started at 3/7/2007 7:37:08 AM

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

Event Type: Information
Event Source: TFS Services
Event Category: None
Event ID: 9001
Date: 3/7/2007
Time: 7:37:05 AM
User: N/A
Computer: <servername>
Description:
Team Foundation Core Web Service Application started.

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

Event Type: Information
Event Source: TFS WorkItem Tracking
Event Category: None
Event ID: 9002
Date: 3/7/2007
Time: 7:36:37 AM
User: N/A
Computer: <servername>
Description:
Work Item Tracking Web service stopped.

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

Event Type: Information
Event Source: TFS Warehouse
Event Category: None
Event ID: 9002
Date: 3/7/2007
Time: 7:36:37 AM
User: N/A
Computer: <servername>
Description:
Warehouse controller application stopped.

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

Event Type: Information
Event Source: TFS Services
Event Category: None
Event ID: 9002
Date: 3/7/2007
Time: 7:36:37 AM
User: N/A
Computer: <servername>
Description:
Team Foundation Core Web Service Application shut down.

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

Event Type: Information
Event Source: TFS Version Control
Event Category: None
Event ID: 9002
Date: 3/7/2007
Time: 7:36:36 AM
User: N/A
Computer: <servername>
Description:
TF10182: The Team Foundation source control server TfsVersionControl stopped at 3/7/2007 7:36:36 AM

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

Matthew Mitrik MSFT

Hello,

Was this issue ever resolved Dan, were you able to find out anything more for this

-Matt

moke

Your timing could not be better. This issue has not been resolved.

Incidentally, last week, the engineers at my client site misunderstood my request and reinstalled the OS on the TFS server that was having this problem. So, I have been going through the disaster recovery exercise on this server. The good news is that I was able to completely restore the environment, but I have not tested the problem described in the thread above. Tomorrow, I was plan to see whether this problem is still reproducible, and I will post my results here.

moke

This problem IS still reproducible even though the server has been completely rebuilt and Team Foundation Server restored from SQL Server backups.

Anyone have an idea