Several problems encountered during team Foundation server deployment

The TFS was upgraded a few days ago. The database version is SQL Server 2008, while the colleague's database uses SQL Server 2008 R2 to back up its database to the server, upgrade sqlserver2008 to R2. The tragedy began.

1. SQL Server 2008 upgrade Error

In my previous upgrade scheme, TFS and SQL Server 2008 are installed on Windows Server 2003 server with a domain controller. SQL Server 2008 uses an administrator account, I don't know how my colleagues operate. If an error occurs during the upgrade, the reporting service upgrade fails, and a new team project cannot be created. This problem must be solved!

The following error occurs when you create a team project and start the report Service (open the report configuration program:

"Failed to load the provider"

InZhou66A similar error occurs in an article, but his environment is under sqlserver2005. the method mentioned here is as follows:

1. Find reportingserviceswmi. dll. The file is in c: \ Program Files \ Microsoft SQL
Server \ 90 \ shared.
2. Registration of reportingserviceswmi. dll failed.
3. Check whether the framedyn. dll file exists in c: \ Program Files \ Microsoft SQL Server \ 90 \ shared.
Copy c: \ windows \ system32 \ WBEM \ framedyn. dll (or search framedyn. dll and copy it)
4. Run c: \ Program Files \ Microsoft SQL Server \ 90 \ shared \ reportingserviceswmi. dll
Use c: \ windows \ system32 \ regsvr32.exe
Register the license (you will not use regsvr32.exe to register the DLL file and search for it on Google)

I am very happy to see a reply saying that the problem has been solved, but no reportingserviceswmi is found on my server. DLL file, which is not found on other colleagues' computers. Only reportingservicesproviderwmi is found. DLL file, view its properties, and see that its internal name is reportingserviceswmi. DLL. Now it is determined that it is, and then follow the above steps to operate, the problem is still.

I couldn't help it. I found an article on Microsoft's help and support website numbered 980142 to solve the following problems:

Fix: when you receive the error message "failed to load the provider" or when the wmiprvse.exe process is stopped, the SQL Server WMI provider obtains information about SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2. information

In the solution below, we can see the cumulative update package (hot fix) for SQL Server 2008 R2. It points to Article 2261464, which contains information about the three downloaded files in the accumulated package, enter your email address and it will be automatically sent to it. If you get the treasure, it's time to solve the problem. Download, install it. The first two installation packages are relatively small and the installation is smooth. When the third installation package is installed, an error occurs again.

Always prompts that an error occurred during the previous installation or upgrade:

A failure was detected for a previous installation, patch, or repair during configuration for features [feature, connectivity_full, SQL _ssms_full, sdk_full, feature, SQL _bids_full, feature, feature, SQL _writer,]. in order to apply this patch package (Kbxxxxxx), You must resolve any issues with the previous operation that failed. view the summary.txt log to determine why the previous operation failed.

Upload the summary.txt file again. Based on the clues, I found some time on the Internet and did not solve the problem. I asked my colleagues that the problem was fixed during the upgrade, but I did not record it .. It was just when the project was busy that the problem could not be solved, and a good solution was provided:Reinstall the system. Although I am still a bit unwilling (after all, the problem has not been solved), I will redo it.

2. Problems Encountered during sharepoint3.0 Installation

Who knows, the following question comes again.

The installation of the system was assigned to a testing team to help with the installation of the system, driver and IIS. The rest is my turn. I started to install sharepoint3.0. After the installation, I found that the computer name was not changed. The default setting is too complicated. Then Install SQL Server 2008 (after installation, you will find that it is not R2, and you have to upgrade it again ). The rest is to install TFs. Check SharePoint before it is installed. You can see that the SharePoint website cannot be opened! Looking for the reason, there are also many such problems on the Internet: After the computer name is changed, the SharePoint website cannot be opened. There are also many related solutions (for Sharepoint 2007 or 2010), but none of them can be solved. Because the first step in the solution is:

Go to SharePoint Management Center

Unfortunately, I cannot even open this one. Other commands, such as the "stsadm-O renameserver" command or the "stsadm-O updatefarmcredentials" command, cannot be solved. However, I saw a solution related to the Registry in an article, and changed all the places in the registry that contain the old machine name to the new machine name. When I reconfigure SharePoint again, or error, first error in step 1

Cannot connect to SQL Server. The machine name \ microsoft # Ssee is not found.

Let's get it done. Then we simply went wrong in step 1.

Failed to connect to the configuration database.
System. Security. Principal. identitynotmappedexception is thrown. Other exception information: some or all identity references cannot be converted.
System. Security. Principal. identitynotmappedexception: some or all of the Identity references cannot be converted.

I guess the above information is still a computer name problem. Forget it. Uninstall SharePoint and try again. However, the problem still exists. The configuration is still stuck in step 1. It is still not possible to delete the website related to IIS and reinstall Sharepoint; find the SQL server2005 embedded Edtion database directory created when sharepoint3.0 is installed, and delete the database starting with WSS and with admin (during error analysis, see the database about the wss_search _ machine name), and then install Sharepoint. Finally, find an article about how to completely delete Sharepoint, and provide the following methods:

1.run regedit.exe and find the HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ wi ndows \ CurrentVersion \ Uninstall branch.
2. Find each {guid} directory. You can also use the search function to find "Microsoft SQL 2005 embedded edition ..."
3. Test the uninstall command (for example, msiexec.exe/X {0f51a262-1adf-4914-b448-78ac58c00008a })
4.run cmd.exe, paste the uninstall command in it, and add "callerid = ocsetup. EXE"

In this way, not only the installed database is deleted, but also the service is deleted. Sharepoint is successfully reinstalled.

The next step is to install and configure TFS, and everything goes well.

3. Install the email server and set the email reminder function

After TFs is installed, the TFS email reminder function is configured by the way, so that there is an email prompt when the work project is allocated or changed, and when the code is checked in or the project is generated, save your time. My solution is to configure the email server on the TFS server machine, and assign an account (consistent with the TFS account) to each member of the team on this email server ), in this way, you can receive operations from other members of the team (related to yourself) at any time through outlook or other email clients. The email notification speed is slow only when you test the change work item. The email will be received within 2-5 minutes after the change.

Summary:

It has been about two and a half years since the team started using TFs. During this period, I have been maintaining TFS, and I have some experience in TFs, I gradually realized the importance of the configuration Administrator (which I previously only saw in the book ). I would like to provide you with some tips:

Like a project, a team also needs a fixed configuration administrator.

If you want to prevent other colleagues from operating the TFS server this time, or I want to upgrade the SQL Server 2008 database myself (because it was previously installed on the domain controller machine and some accounts do not have database-related operation permissions ), it may save several days for project implementation, instead of solving these problems that may never be encountered.

PS: "The path to mountains" is a good book that does not use TFs in real time. Many of these chapters are also of reference and learning value.