Question : SQL Database Backup "not permitted because it is not online"

I am reposting a question which was closed some time ago with no resolution in the hope that someone else may be able to assist, given we still have the problem.

I'm posting the original question below, however please be aware that I've tried every reference available on the Internet (that I can find) on solving this problem since with no success. Everything seems to intimate a problem with the Full Text Index, which the database doesn't have.  

SELECT name, ftcatid FROM sysobjects WHERE ftcatid > 0
(0 row(s) affected)

---
I am trying to back up one of our SQL databases and am receiving:

System.Data.SqlClient.SqlError: The backup of the file or filegroup "CCT_MSCRM" is not permitted because it is not online. BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict the selection to include only online data. (Microsoft.SqlServer.Smo)

Pretty standard error, lots about it on the Internet.

However, I've tried EVERYTHING I can find on Google regarding it with no luck, 99% of the answers seem to relate to the Full Text Index specifically, however I've tried every suggestion for that and it also has not resolved it. (As you can see it doesn't reference sysft_XXX which is where the suggestions focus)

If i query the status of all the database they all show ONLINE fine:

SELECT type, name, state, state_desc FROM sys.database_files
0      CCT_MSCRM      0      ONLINE
1      CCT_MSCRM_log      0      ONLINE
4      sysft_CCTMSCRM_CAT      0      ONLINE

SELECT name, database_id, state, state_desc, recovery_model FROM sys.databases
CCT_MSCRM      7      0      ONLINE      1

It's a production box and in use almost constantly, another reason I know it's online, so if I detach/attach etc then I need to make the most of the limited time I'll have available to work on it.

Does anyone have any ideas as to what's causing this and how I can resolve it?

Thanks.

Answer : SQL Database Backup "not permitted because it is not online"

Man, you really have a problem :o)

For now I only have a solution for you but gonna take time and should only make after hours:
- Create new empty database. Script all objects from old database and run that script in new database. Migrate data from old to new database. Backup new database.

If this works, give access to users for new database and drop old database so you can work only with new one.