The company heavily uses BizTalk, so they threw up a staging server with BizTalk 2009 on it and ran the Team Foundation Server Build Setup. After this, building non-BizTalk projects was working just fine, but BizTalk projects fail to build. After examining the box, they had copied various things from a BizTalk development workstation, but none of the additions had any effect. The rationale behind this was they don’t want Visual Studio on the staging server, but without it when running the BizTalk install the Developer Tools and SDK option is not selectable.

To get around this, look during the installation of BizTalk under Additional Software, and find the Project Build Component feature. While this allows for builds without Visual Studio, it should be noted that you can’t generate MSI packages, just build stuff.

Related posts

• No related posts.

In TFS 2010 when trying to make Sequential builds (i.e. for one you have several interdependent solutions in your automation strategy) in the DefaultTemplate XAML file you have to change the tag to . It should be noted that this is a lot different than TFS 2008. In TFS 2008, in the TFSBuild.proj file the solutions were just ordered correctly and made use of the BuildSolutionsInParallel property. This also required changing the setting for the MaxProcesses in the tfsbuildservice.exe.config file on the build server to a value greater 1, and also to restarting the build service on the build server. This is a lot more cumbersome than changing the type tag mentioned above.

Related posts

• No related posts.

http://msdn.microsoft.com/en-us/library/ee412237.aspx

or if you are just interested in the specific image:

http://i.msdn.microsoft.com/Ee412237.792e5c8b-f1b7-4cb4-9b87-5689c44973da(en-us,office.12).gif

was experiencing an abnormal amount of memory utilization on the WFE’s I had built for them. While they wanted a quick fix, it is important to remember that the scanning processes of FSSP will cause memory consumption depending on how you balance the engines being used. Forefront uses in-memory scanning (FSCRealtimeScanner.exe) and up to 5 scan engines can be employed so each scan process will load the engines that you have enabled under SETTINGS>Anti Virus.

For each of the scanning processes ~ 200-300MB RAM will generally be consumed depending the file being processed since the file being scanned is loaded into memory. Thus, if a scan is being executed on a file that is 200 MB and further 200MB RAM utilized. Once the scan is complete, this memory will return to the available pool.

All this being said, explicit reduction of processes spawned is controllable by modifying the RealtimeProcessCount registry value (HKLM\SOFTWARE\Wow6432Node\Microsoft\Forefront Server Security\SharePoint), which would require restarting FSSP and SharePoint services, however this should be approached with caution since having several real-time processes allow FSSP to scan more than one file, thus avoiding scan-related bottlenecks.

The only recommendation that can be made is a review of the memory consumption to establish whether the memory consumption is normal, and thus requires expanding the available RAM or whether there is a separate problem.

Related posts

• No related posts.

Generally, this will throw the error:

TFS Error: TF20015, stating that a field contains a value that is not on the supported list

This leads to the requirement where a developer, even though they have gone onto greener pastures, has an invalid account value, within a value restricted field. Bad news bear.

Fortunately, there is a supported route you can take with TFS in order to overcome this issue. Using the ALLOWEXISTINGVALUE rule allows entered value to still be valid even if that value is no longer a valid value. By customizing the process template work item types and use this definition for the field with invalid values.

Bada bing, good to go!

Related posts

• TFS Proxy Server Unexpected Shutdowns (2)
• ForeFront TMG and Active FTP Issues (1)
• High QueryBuildQueue Execution Time? No Problem! (0)
• SharePoint Claims Based Authentication Architectures Explained – Part 8 – Design Principles for Claims Based Applications (0)
• SharePoint Claims Based Authentication Architectures Explained – Part 7 – Transforming Identity In SharePoint (1)

Fortunately, to get around this limitation you can use the TfsSecurity tool, specifically the TfsSecurity /imx command, to get the direct members of the specified group.

It is important to remember that TfsSecurity.exe comes from Team Explorer, not the Visual Studio shell.

Related posts

• TFS Proxy Server Unexpected Shutdowns (2)
• SharePoint Claims Based Authentication Architectures Explained – Part 8 – Design Principles for Claims Based Applications (0)
• SharePoint Claims Based Authentication Architectures Explained – Part 1 – Intro To Claims Architectures (0)
• Free SharePoint Redirection WebPart – Programming SharePoint WebParts With LINQ to Active Directory – Part 1 (2)
• SharePoint Claims Based Authentication Architectures Explained – Part 9 – Specifying the Identity of a Given User (0)

Recently, a strange issue was occurring with my clients geo-environment where the proxy servers would start shutting down repetitively. The exact error you may run into is:

The VSTF Proxy Server stopped at [server]. The application is being shutdown for the following reason: HostingEnvironment. For more information ....."

Now this can happen for a variety of reasons, but first thing is you should enable proxy server tracing to get some more relevant error information by opening the web.config in the VersionControlProxy folder by setting the traceDirectoryName to a familiar storage location and changing traceWriter to true. For this particular error, one of the error returns can be:

Detailed Message: TF53002: Unable to obtain registration data for application VersionControl.
TF30055: Visual Studio could not find or read the Team Foundation Server server name in the configuration file. Contact your Team Foundation Server administrator. (type VstfNotConfiguredException)

If you get this error, the TfsNameUrl appsetting is not configured in the web.config file for the proxy server. Locate the:

element and change it. After, check your IIS app pool setting and check that the recycle interval or memory limit. After, you should be good to go!

Related posts

• SharePoint Claims Based Authentication Architectures Explained – Part 1 – Intro To Claims Architectures (0)
• SharePoint Claims Based Authentication Architectures Explained – Part 3 – SharePoint As A Browser Based Application (1)
• ForeFront TMG and Active FTP Issues (1)
• TMG Web publishing for SharePoint HTTPS, No Certificate Usage On TMG (1)
• Developer Turnover and Maintaining Valid TFS Historical Data – TFS Error TF20015 (0)

The QueryBuildQueue command is generated by TE and BuildNotification….when TFS queue a build, TE and BuildNotification it will query the status of the build about every 30 seconds. Naturally, this will result in a multitude of QueryBuildQueue commands being issued. When a query beings, TFS requires establishing a connection to the Build Agent, which results in a time lapse will the request is issued and the subseuquent response is listened for, during this lapse period within the request / response frame, threads are idle so the load is nothing to be concerned in terms of server load.

Rest easy, fickle TFS admins

Related posts

• Developer Turnover and Maintaining Valid TFS Historical Data – TFS Error TF20015 (0)
• Mirroring TFS – Consider Index Rebuilds When Using TLog Backups (0)
• SharePoint Federated Identity Process – Part 3 – Exploring the SharePoint Federated Identity Solution (1)
• ForeFront TMG and Active FTP Issues (1)
• TMG Web publishing for SharePoint HTTPS, No Certificate Usage On TMG (1)

At a current client of mine where I was setting up initial, trial mirroring for the TFS instance, it because evident that the TfsIntegration Maintenance Job was causing issues with a long completion time which eventually resulted in TFS to respond uncharacteristically slow. Now this job does two things, firstly it re-indexes the TFS databases (TFSIntegration, TfsWarehouse, TfsWarehouse, TfsWorkItemTracking and TfsVersionControl) by calling the Re-indexing:TfsIntegration stored procedure. This is done by calling exec TfsIntegration.dbo.Prc_OptimizeTfsDatabases. As well, it also removes deleted process templates by calling exec TfsIntegration.dbo.prc_deleteTemplates. The first of these is the culprit though for this issue, and if you run the stored procedures directly you will see a Stop Request being issued which will result in the re-index has not being executed.

9 times out of the ten, because Index rebuilds and Defragmentation generate very hefty transaction logs, it is because a transaction log backup job (TLog backup job) is running while the re-indexing is executed. While calling TLog may help in log file reduction, it can also cause these issues when executed simultaneously with the index rebuild.

Related posts

• TFS Proxy Server Unexpected Shutdowns (2)
• SharePoint Claims Based Authentication Architectures Explained – Part 5 – SharePoint Identity Across Realms (0)
• SharePoint Claims Based Authentication Architectures Explained – Part 6 – Understanding Federated Identity In SharePoint (0)
• SharePoint Claims Based Authentication Architectures Explained – Part 1 – Intro To Claims Architectures (0)
• High QueryBuildQueue Execution Time? No Problem! (0)

What if one is trying to use TMG to publish a SharePoint environment for both HTTP and HTTP access, while the certificate is appropriately setup in the SharePoint server it is not desirable to have the web publishing rule bound to the certificate, i.e. certificate stuff should be handled by the SharePoint environment. So, breaking the question down even more, they wanted to publish the HTTPS SharePoint instance WITHOUT using the certificate in the TMG instance.

This obviously is not a supported route, because logically it doesn’t make a ton of sense. One can’t use a HTTP web publishing rule without having the appropriate certificate accessibly and appropriately in place, and clearly is not a TMG limitation because it is the same requirement for ISA and Proxy Server stuff.

Related posts

• TFS Proxy Server Unexpected Shutdowns (2)
• SharePoint Claims Based Authentication Architectures Explained – Part 3 – SharePoint As A Browser Based Application (1)
• ForeFront TMG and Active FTP Issues (1)
• SharePoint Claims Based Authentication Architectures Explained – Part 9 – Specifying the Identity of a Given User (0)
• SharePoint Claims Based Authentication Architectures Explained – Part 7 – Transforming Identity In SharePoint (1)

Unfortunately, there are some limitations however which I ran into recently with a current client of mine. The long and short of it is check-in policies cannot be included in process templates. However, there are custom development avenues you can use by building some managed code against the TFS API to execute this, the objects and methods that are used are fairly self explanatory. Consider the following that shows getting a collection of the current policies, and then setting the policies.

Firstly, getting an appropriate reference to the desired project:

Off the TeamProject object instance, you can following call the GetCheckinPolicies method, which will allow you to return a Microsoft.TeamFoundation.VersionControl.Client.PolicyEnvelope array type. Essentially this is what we can refer to as the policy instance, representing the applied policy's of type IPolicyDefinition. Since you have an active array, you can do push the array into a typed collection of PolicyEnvelope objects using List.AddRange

Related posts

• No related posts.