I had TFS 2015.3 with SQL Server 2014 Express, after upgrading the SQL Server to 2017, TFS stopped working and could not be started.
I removed SQL Server 2014 and installed SQL Server 2017 with same instance name (.\SQLEXPRESS) and attached all databases from files in the DATA folder of SQL Server 2014. Then tried to start TFS, but I did not succeed.
Then I upgraded TFS to 2018.3. After installation completed, I used upgrade wizard and now I have some collection which failed. When I click on start collection (in Team Foundation Server Admin. Console), this error happens:
TF400783: The Host 'MyCollection1' cannot be started. The host is in the
process of being serviced. The servicing may have failed and needs to be restarted and completed before the host can be started.
In the status of collection, in the "most recent servicing activity", I have this
AppltPatch, Failed, 3/8/2019
What can I do to get my collection work again?
What can I do to get my collection work again?
First of all, it's highly possible that you will need to restore the last good consistent set of tfs backups to get your TFS environment to a working state again. Or even contact MS support if no such backup is available.
But before doing that try to figure out what is an exact reason of the failure, perhaps it is fixable and the upgrade process will be eventually finished successfully:
USE Tfs_Configuration
-- get job id that was failed
SELECT TOP 10 *
FROM tbl_ServicingJobDetail
ORDER BY StartTime desc
-- query information for that job id
SELECT * FROM vw_ServicingStepDetail
WHERE jobid = 'BA3E49D5-EA30-4CB6-93DD-31D5D1C0FB93'
Also, have you already tried to open a Status tab of the collection, select that job that was failed and click on Rerun Job?
Related
I am carrying out a dry-run of an imminent TFS 2010 migration upgrade to TFS 2013.5 on a dedicated Windows Server 2012 R2 Datacenter host, following the steps in [this YouTube tutorial] (https://www.youtube.com/watch?v=nm-WOLc-GQQ) by Mohamed Radwan.
The intention is to keep the newly-implemented TFS 2013 running simultaneously with the TFS 2010 instance for a few days while we validate the migration upgrade. Once satisfied all's gone well, we'll then complete a full switch to the TFS 2013 instance and decommission the TFS 2010 instance which is implemented on a Windows Server 2008 R2 Enterprise.
The tutorial recommends using the TFSConfig Backup and Restore utilities to backup the existing TFS 2010 databases and reporting services key and then restoring them to my SQL Server 2014 instance on the TFS 2013 host.
Following the database and reporting key restore which has also completed successfully, I sought to adhere to the TFS cloning recommendation advised by various sources including Microsoft Support, by running in the following order, these TFSConfig commands:
TFSConfig PrepareClone
TFSConfig ChangeServerID
TFSConfig RemapDB
Problem is, when I attempt running the PrepareClone command, I keep getting the TF30040 error message (as per this thread's subject title). On the few times that I've proceeded regardless and run the ChangeServerID and RemapDB commands however, they complete successfully.
I desperately need some help resolving this TF30040 error, as all attempts to apply some of the resolution steps proposed in other related incidents have failed miserably. It's important I find a resolution due to the fact we're intending to run the two instances for a few days while verifying and validating the TFS 2013 upgrade.
Another key question I have is whether it is mandatory that I successfully execute the TFS PrepareClone command, despite the fact I'm successful executing the ServerID and RemapDB commands? In other words, is it safe to ignore the PrepareClone failure and proceed with the simultaneous running of both TFS 2010 and TFS 2013 instances for those 2-3 days of validation testing?
If you don't run PrepareClone command, the original resources will be used by both the original and the new servers. If both the original and the new servers are live and point to the same SharePoint or reporting resources for any amount of time, you could end up with corrupted databases.
You may keep one server live at the same time. Or try to use a new service account that has no access to production environment to run the command:
TFSConfig PrepareClone /SQLInstance:ServerName /DatabaseName:DatabaseName /notificationURL: ApplicationTierURL
I have an AWS instance, on which SQL Server 2014 has been running for more than 3 years.
But a few days ago, suddenly the SQL Server stopped running.
I checked the server and tried to start SQL Server service from services, from SQL Server Configuration Manager etc. but I'm not able to start the server and got following error:
So I checked event viewer entries and I found these two errors:
I started some research work over web to overcome on this issue and I found that I can start SQL service using below command using T902:
net start MSSQL$REVCORD /T902
And SQL Server service started successfully.
But I want to make SQL Server / services back to normal as before so I can start / stop services normally.
I found on web that this cause is due to corruption in master SQL Server database, I don't have backup of master SQL Server database so I cannot restore it back.
I checked multiple threads over web and tried multiple things to overcome this issue but no luck.
So finally I decided to reinstall/recover SQL Server 2014, but I am getting another error while reinstalling:
Based on finding over web, all threads showing that I have to uninstall and reinstall SQL Server to make it normal again.
Please help! It's a live server with multiple calls continously so I cannot uninstall/reinstall SQL Server there due to possible data loss.
The first thing:
select * from sys.sysmessages where error = 5833
The message:
The affinity mask specified is greater than the number of CPUs supported or licensed on this edition of SQL Server.
Check your edition, and fix the affinity mask so that the number of CPUs satisfy the number which is supported by your edition.
You can fix it in SSMS on the Processors tab in your server properties, or using sp_configure
After configuring database mail on one server and sending a test email, I am finding nothing in the queue or the log. The mail id, however, keeps incrementing with each retry. I have checked the following:
I am sysadmin on the box, so I do have permissions to send mail
EXEC msdb.dbo.sysmail_help_status_sp; reports STARTED
There are no records in the queue: SELECT sent_account_id, sent_date FROM msdb.dbo.sysmail_sentitems;
There are no records in the event log: SELECT * FROM msdb.dbo.sysmail_event_log;
Service broker is enabled. This returns "1": SELECT is_broker_enabled FROM sys.databases WHERE name = 'msdb';
I have configured this successfully on 4 other instances, it's just one that is giving me grief. Any other pointers would be appreciated.
Looks like this issue is with a bug in the version of sql that I am running on this instance as explained here: https://support.microsoft.com/en-us/help/3186435/fix-sql-server-2016-database-mail-does-not-work-on-a-computer-that-doe
Installing CU2 will fix it:
Note This issue also affects instances that are running SQL Server
2016 SP1 CU1. This issue occurs because of a bug in SQL Server 2016
SP1 CU1 setup. The setup for SQL Server 2016 SP1 CU1 deletes the
config file DatabaseMail.exe.config without replacing it with a new
one. This causes the Database Mail to break in the absence of .Net
framework 3.5 SP1. The fix in SQL Server 2016 SP1 CU2 is meant to
address this issue and prevent the DatabaseMail.exe.config file from
getting deleted from the machine after installing a CU. So if you
install SQL Server 2016 SP1 + CU2, the Database Mail will not be
impacted by the setup. However, if the Database Mail is broken by the
installation of SQL Server 2016 SP1 CU1, you can use any one of the
workarounds mentioned below.
I am trying to run SQL Server Data Quality Services on SQL Server 2014 with 32GB of RAM, plenty of disk space, and the latest updates (Microsoft SQL Server 2014 (SP2-CU2) (KB3188778) - 12.0.5522.0 (X64) Developer Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor))
The data resides on the same server, separate database.
Knowledge base is created and published with three domains over about a million records table. And that where it stops working: creating data quality project fails after displaying cheerful message "Analysis of data source has been completed successfully" - clicking "Next" button leads to message #1, and, after restarting the application (and the server - just in case), the message #2
SQL Server Data Quality Services server has stopped working
Refresh of client view table for user [domain\user] failed.
These are fairly consistent.
Examining both the server and the client logs reveals nothing (besides a full stack dump for the error), and the only suggestion from Microsoft forums is “to apply latest service pack”; the latest service pack has been applied but still no cigar.
Any insights/suggestions would be highly appreciated!
thank you,
-al
P.S. Excerpt from the client log:
2/13/2017 9:19:26 AM|[]|1|ERROR|CLIENT|Microsoft.Ssdqs.Studio.ViewModels.Utilities.UIHelper|An error has occurred.
Microsoft.Ssdqs.Infra.Exceptions.EntryPointException: Refresh of client view table for user [domain\user] failed.;
at Microsoft.Ssdqs.Proxy.Database.DBAccessClient.Exec();
After poking around I have found a question similar to my on MSDN blog: a user complained that his DQS installation has STOPPED working after applying CU2 to his SQL Server 2014 instance... So, I downgraded mine from [(SP2-CU2) (KB3188778)] to [(SP2) (KB3171021)], and - drums rolling - everything started working!
This is not a solution but an acceptable workaround, and I can continue analyzing my data until I upgrade to SQL Server 2016, and the fun begins anew!
I am shifting my development platform to a virtual machine (using VirtualBox), and have installed Win7, VS2010 and SQL Server Express 2008 R2. I have a project that uses FluentMigrator to look after the database.
When I (try to) run the initial migration, all console messages come back from FluentMigrator reporting success, but when I look at the database, no changes have been made. Also, if I try to refresh the schema in SQL Server Management Studio Express within a couple minutes of running the migration, I get a "Lock request timeout period exceeded" message.
Unfortunately SQL Server Express does not come with SQL Profiler. Is there a way I can look at the queries hitting the database without this?
Any other ideas on why FluentMigrator would be reporting success when there is no success to be found?