You may can make use of DATABASEPROPERTYEX

You can drop and recreate the Full Text Index in SSMS as seen in this screenshot.

Comma (,) is missing after this

name = BribsIndex01

During the backup/restore process looks like somewhere the Full Text Index got broke. Did you try dropping and recreating the FTE on the restored database?

You may find this article useful...

You can do it through the "Server Network Utility" as in this screenshot.

Most likely the script has thrown an exception and it needs action (like clicking on Ok). Try running the script in command prompt under the context of the SQL Server...

What is the exact error message you get, when SQL Server is started in the command prompt?

Please check which process is causing this one to be deadlocked. You may find this article useful.

Please check if "RETAINDAYS" option while Backing up the database meets your requirements. Read more here

Open Microsoft SQL Server Management Studio and you will find Linked Server as in this screenshot.

There is nothing much I can recollect to fix this issue. Please check if dropping and recreating the FULL TEXT Index helps.

Please check if the SQL Server FullText Search service is running.

Since you have tried the other options, I feel restarting the SQL Server should help. There is nothing much we can configure in the Default Trace.

Yes, scripting the Linked Servers through SSMS is an easy option. But the password mentioned in the Linked Servers will not be scripted out as I mentioned here[/url]. The password...

It is possible that the default trace got stopped due to an error. The SQL Server Error Logs should have that information recorded.

You can restart the SQL Server instance or...