I was in the process of trying to restore my TFS Server to a different machine until there was time for it to be rebuilt. This turned out to be quite a headache. Once all the querks were identified it wasn’t all that bad but it took much longer than it should have. Here are the key steps:
Install Fresh Copy of Team Foundation Server
Stop all Services (IIS, REporting Services)
Restore all TFS Databases
Restore Reporting Services Databases
Restore SharePoint Content Database
Log into SharePoint Administration and remove content database and re-add WSS_CONTENT database
Ensure Reporting Services is functioning
Run TfsAdminUtil configureconnections and ensure reporting services is pointing to new machine
Modify web.config in the web services/services/ directory so the data tier matches EXACTLY what was in the previous machine
Run TFSAdminUtil renamedt ensuring data tier
Run TFSAdminUtil activateat
After those steps you should be up and running. The major issue…
I was recently working on an excel pivot table report that pulls its data from a SharePoint list. One of the business requirements was to be able to sort, filter, and/or group by a “Week Ending” date. The list has a column called Action Date which could be any day/date. The solution turned out to be quite simple.
Create a new column in the list called, for example, “Week Ending.” Make this column a calculated column with the following formula:
=TEXT([Action Date]+(7-WEEKDAY([Action Date])),”mm/dd/yyyy”)
Replace [Action Date] with the column off which you are basing the week ending date.
This particular formula assumes that Saturday (7) is the week ending date. Adjust accordingly.
A situation present itself occur where an orchestration uses a receive port that is sourced by multiple receive locations to receive a message and a specific context property must be read from the incoming message. Because the message is coming from different receive locations, an evaluation of the to location may be necessary to determine the proper context property. For example, the following receive port is set up to accept an incoming message from four different receive locations:
In this example, the file is not only coming in from four receive locations, but each location is a different type (a windows folder, a SharePoint document folder, an FTP site or email). To get a file property such as the file name, an orchestration will need to read the context property ReceivedFileName associated with the specific receive location. When multiple locations are…