Hello,

Hi James,

The URL you are talking about is constructed in the Report by looking at the ToolArtifactUrl table in the "TfsWarehouse" database. That table contains the URLs for the different artifacts in Team Foundation and I'm guessing that in your case the ".urc.edu" part is missing there. If you manually update this table the Warehouse adapters will update it back so manually changing this value won't be a solution.

I never saw a URL that looks like yours for a Team Foundation server so if you can explain how did you setup that maybe I can help you to figure out how to get the adapters to populate that Warehouse table with the correct URL.

For instance, if someone wants to connect to your server in Team Explorer, is <servername>.ucr.edu the name they will use for the server?

Thanks.

Federico

Hi Federico,

Yes, this is an "interesting" installation. The TFS is behind our firewall (ISA 2004 server) and the client machines are outside the firewall. The setup went well, with some tweaks here and there to config files and registry settings. We connect to the server with servername.ucr.edu. and are able to create projects, add/modify work items, view the project portal, etc. I posted on this setup in Unable to connect to the Windows SharePoint Servicesin the TFS Setup forum.

Thanks for your help,

James

One "interesting" solution that may work for you would be to edit the report to have the URL of your server. I have not tested this, and it is not a recommended solution.

Anyway, on the Work Items report (from a Report Server Project) if you view the "Action" property for the ID field you can see it is set to "=Fields!Work_Item_URL.Value". This is the [Measures].[Work Item Url] that Federico mentions. This data is pulled from the dsCurrentWorkItem data set (you can see this set from the Data tab). If you set the "Action" to something like:

="http://ServerName.ucr.edu:8080/WorkItemTracking/Workitem.aspx?artifactMoniker=" & Fields!System_Id.Value

This will create the link you are looking for. Another possible solutions is to to modify your hosts file on the clients and map ServerName to ServerName.ucr.edu.

Hi James,

The correct name of the table is "Tool Artifact Display Url". So can you please verify that in [TfsWarehouse].[dbo].[Tool Artifact Display Url] table the URLs in the [Tool Artifact Display Url] column are missing the ".ucr.edu" part.

If so then can you please in your Application Tier machine open the following config file <tfs_install_path>\Web Services\web.config and check the value of the "TFSNameUrl" key. Does that value have the ".ucr.edu" part?

Thanks.

Federico

Hi Federico,

I just responded to Nick and then saw your message. Here is the data from the Tool Artifact Display URL table

1	Build/Build	http://<servername>:8080/Build/Build.aspx?artifactMoniker=	8/8/2006 10:24:01 PM	True
2	WorkItemTracking/HyperLink	http://<servername>:8080/WorkItemTracking/HyperLink.aspx?artifactMoniker=	8/8/2006 10:24:01 PM	True
3	WorkItemTracking/Workitem	http://<servername>:8080/WorkItemTracking/Workitem.aspx?artifactMoniker=	8/8/2006 10:24:01 PM	True
4	VersionControl/Changeset	http://<servername>:8080/VersionControl/Changeset.aspx?artifactMoniker=	8/8/2006 10:24:01 PM	True
5	VersionControl/Label	http://<servername>:8080/VersionControl/Label.aspx?artifactMoniker=	8/8/2006 10:24:01 PM	True
6	VersionControl/LatestItemVersion	http://<servername>:8080/VersionControl/LatestItemVersion.aspx?artifactMoniker=	8/8/2006 10:24:01 PM	True
7	VersionControl/VersionedItem	http://<servername>:8080/VersionControl/VersionedItem.aspx?artifactMoniker=	8/8/2006 10:24:01 PM	True
8	TestTools/TestResult	http://<servername>:8080//Build/TestTools/TestResult.aspx?artifactMoniker=	8/8/2006 10:24:01 PM	True

the following is the section from \WebServices\web.config

<!-- TFS name and Url information -->

<add key="TFSNameUrl" value="http://<servername>:8080" />

<add key="TFS Name" value="<servername>"/>

<!-- TFS Url for access from internet, used for specifying links in alerts-->

<add key="TFSUrlPublic" value="http://<servername>.ucr.edu:8080"/>

I will change the TFSNameURL to http://<servername>.ucr.edu:8080 and reboot the server to see if that picks up the change in the TFSWarehouse DB.

Thanks,

James

Ok, I made that change to the web.config file and rebooted the server. When I connect to TFS from my client machine, I get the following error in the Output window:

"Team Foundation Server <servername>.ucr.edu does not exist or is not accessible at this time. Technical information (for administrator): HTTP code 503: TF30059: Fatal error while initializing web service"

One clue is that in the web.config the value for TFSNameURL is in uppercase <SERVERNAME>.ucr.edu, while the error message is in lowercase <servername>.ucr.edu.

James

Hi James,

I was sort of expecting something like that. The TFSNameURL key in that web.config is the URL used internally by the server so different components can communicate to other components inside the server. For instance the Warehouse Adapters use that URL to connect to the linking service to create the URLs that go in the [Tool Artifact Display Url] table.

What I think is happening is that the URL with the .ucr.edu is only valid to use from the client because it goes through the ISA server but is not valid inside the server. Is there a way you can have your server to also recognize the URL with the .ucr.edu as something valid?

Thanks.

Federico

Ok, making that change causes a new issue. Connecting to TFS from the client gives the following error dialog:

Team Foundation Error

TF26173: Team Foundation could not connect to the application tier. Check that you have a network connection and that the Team Foundation Server is available. If the problem persists, contact your TFS administrator.

Switching the value of TFSNameURL back to http://<servername>:8080 removes the error dialog.

I do have a mapping in my hosts file for the server and it's IP address.

James

I'm not sure if you were able to read my last post before your last post. What you saw is that if you change TFSNameURL to have the .ucr.edu part your server won't initialize and because of that your client won't be able to connect.

What I was wondering is that if it is possible to set the hosts file or something on your server so the server itself can also use the URL with the .ucr.edu part. If that is possible then you should be able to change TFSNameURL to that and the server will initialize correctly and the client will connect.

Also, it is the first time I hear about this type of configuration and maybe if I understand better the steps you followed (updated config files, etc) I could think other possible solutions. Did you follow some documentation in order to configure your server like this?

Federico

Hi Federico,

I have added a hosts file to the server and have changed the web.config back to <servername>.ucr.edu. I can now connect to the server from the client, but the link in the report is still wrong; <servername>:8080 instead of <servername>.ucr.edu:8080.

This setup is basically an extranet configuration. How I configured the server setup is in the following post:

Unable to connect to the Windows SharePoint Services

Previously you had mentioned the Warehouse adapters. Is there a way to configure them. I have used the TFSAdminUtil activateat command, but that didn't help either.

Thanks for your help,

James

One other issue has come up. When I view the project portal, the work items have not been updated. The following message is on the page:

"Report Generated: 8/10/2006 2:18:45 PM by VCSANET\JAMESJ; Last Warehouse Update: 8/8/2006 3:24:13 PM"

James

We are getting close James. It seems that now you are able to get your system going. The reason your URL in the reports is still wrong is because it seems that the Warehouse adapters didn't run in the past couple of days.

The adapters are suppose to run on a regular basis so one thing you may want to do is in the Application Tier you will see an NT service named TFSServerScheduler, make sure that service is started. Also go to <tfs_install_path>\TFSServerScheduler and open the TFSServerScheduler.exe.config and set the TfsNameUrl key to the server URL (if you are in RTM it is possible that the key doesn't exist and instead you have a key named BisNameUrl, go ahead and BisNameUrl to TfsNameUrl and set the URL). Once you do this please restart the service.

By default the adapters run every hour and the service won't kick them for one hour. You can check the run interval by going to http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx in the Application Tier:

- Click on the GetNextInterval method, type 0 in the lastInterval prompt and click Invoke. The value returned is the run interval in minutes (by default it is set to 3600 minutes)

- In order to change that value navigate back to the root of the web service page and click on the ChangeSetting method, type "RunIntervalSeconds" (without the quotes) in the setttingID and the new interval minutes in the newValue. The next time the scheduler runs it will pick this new value and start to run in that frequency.

But in order to figure out why your adapters don't seem to be running please take a look at our Troubleshoot guide that I think will help you solve the problem http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=154526&SiteID=1.

Please let me know how it goes or if after going through the guide you still experience the problem.

Hi, Federico

1. TFSServiceScheduler is set to automatic and is running
2. TFSServerScheduler.exe.config had the following entry (this is a RTM Workgroup install)

<add key="BisDomainUrl" value="http://<servername>:8080" />

I changed it to

<add key="TfsNameUrl" value="http://<servername>:8080" />

3. I set the RunIntervalSeconds to 60 to test for a while. ScheduledServices.xml has an entry of:

<tool url="http://<servername>:8080/Warehouse/v1.0/WarehouseController.asmx" lastrun="2006:8:10:23:43:36" />

the Project Portal now shows updated information. All other projects show updated information.

4. From the troubleshooting guide, I ran the SQL to check what data was moved to the warehouse (the SQL needs to be updated for the RTM as column names have changed). Here are the results:

Last Cube Processing: blank
LastVCWHWrite: 2006-08-08 22:24:03.167
LastWITWHWrite: 2006-08-10 23:18:26.040
WH Revisions: 287
WIT Revisions: 124
WH Changeset: 61
VC Changset: 61
Warehouse Identity Id: 209
Integration Identity Id: 209
Warehouse Structure Id: 173
Integration Structure Id: 173

5. Drililng down to the work items report still shows the wrong link to the Workitem.aspx page; <servername>:8080 instead of <servername>.ucr.edu:8080

since this is basically an extranet installation, do you suppose installing the Team Proxy would help to alleviate or solve this problem?

Thanks,

James

Hi James,

Installing the Proxy won't change the behavior of the warehouse do that won't help in this case. I'm going to ask you to follow these steps to really figure out of the adapters are still populating the old URL.

- First of all, can you check if the [Tool Artifact Display URL] table still contains the incorrect URL. It is possible that you are looking at cached versions of the reports, they are cached for 30 minutes by default but that the table was actually updated.

If the table still has the wrong data then I will ask you to follow these steps:

- Stop the TFSServerScheduler service.

- Using SQL tools update all the URLs in the [Tool Artifact Display URL] table to something invalid. For instance, add to all of them the character "a" before the http part.

- Make sure the Web Services\web.config has TFSNameUrl using the url with the .urc.edu. Also make sure let me know if Web Services\Warehouse\web.config has the TFSNameUrl key is doesn't need it but if it is there make sure it is also with the .urc.edu part.

- Reset IIS.

- Go to http://<servername>:8080/Warehouse/v1.0/WarehouseController.asmx and manually run the adapters by clicking in the Run method and then in the invoke button.

- In a few seconds all the URL entries in the [Tool Artifact Display URL] should be updated. Your "a" character should definitely go away. Do they now have the right URL?

Please give it a try and let me know.

Thanks.

Federico

Hi Federico,

The urls in [Tool Artifact Display URL] are still the same. There is not an entry in Web Services\Warehouse\web.config for TFSNameUrl.

I followed your instructions but ran into the following errors.

1. If I change the TFSNameUrl value to http://<servername>.ucr.edu:8080, then the WarehouseController.asmx page won't run, when accessed from the server.

You didn't mention when to restart the TFSServerScheduler in your steps, so I restarted it both after resetting IIS, and after invoking the webservices. (I did your steps several times)

The webservices won't run, unless the TFSNameUrl value is set to http://<servername>:8080 When browsing to the webservice, the following error is displayed:

The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
--------------------------------------------------------------------------------

Invalid at the top level of the document. Error processing resource 'http://<servername>:8080/Warehouse/v1.0/WarehouseControl...

TF10216: Team Foundation services are currently unavailable. Try again later. If the problem persists, contact your Team Fou...
 

thanks,

James

Hi James,

I apologize, I understood from your previous e-mails that you were able to set TFSNameUrl in Web Services\web.config to the ucr.edu one and have the system working.

The Warehouse adapter uses that URL to build the ones in [Tool Artifact Display URL] so whatever value is there is the one that will show up in the entries in that table.

I'll talk with some people here to figure out what you can do to have a working system after setting TFSNameUrl to http://<servername>.ucr.edu:8080. In the mean time can you please send me the event log error that I suppose gets created when you try to go to http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx after setting TFSNameUrl with ucr.edu.

Thanks.

Federico

HI Nick,

I think I understand what you mean. I did a search for *.rdl files on the server, and the only ones are in the MsfAgile_new.zip file. If I edit the Work Items.rdl in that archive will it carry across to all new projects?

James

James and I took this thread offline to find a solution to the problem.