Getting issues affixing a Database with multiple filegroups along with a full text catalog from server A to server B with either "sp_attach_db" or CREATE DATABASE in SQL Server 2005 SP3. All of the database files (primary data, secondary data, log, full-text catalog) happen to be replicated from server A to server B.

I'd an identical problem (SQL Server 2005: Attach database using sp_attach_db with full text catalog) but this situation only were built with a primary computer file, primary log file along with a full text catalog

Now i'm confronted with including more filegroups so when I attempt to operate the example command below it fails

CREATE DATABASE DBNAME ON 
    (FILENAME = 'C:\Databases\DBNAME\Data\DBNAME_data.mdf'), 
    (FILENAME = 'C:\Databases\DBNAME\Data\DBNAME_indexes.ndf'), 
    (FILENAME = 'C:\Databases\DBNAME\Data\DBNAME1_data.ndf'), 
    (FILENAME = 'C:\Databases\DBNAME\Logs\DBNAME_log.ldf'), 
    (FILENAME = 'C:\Databases\DBNAME\Data\FTData') 
FOR ATTACH;
GO

Error Message:

Msg 5120, Level 16, State 101, Line 1
Unable to open the physical file "C:\Databases\DBNAME\Data\FTData". Operating system error 5: "5(Access is denied.)".

I have tried personally this Microsoft page (http://msdn.microsoft.com/en-us/library/ms176061.aspx) as my guide however it does not come with an example such as this. I understand this needs to be possible, what shall we be held missing!?

Determined things i required to do. Whether this is actually the proper way or perhaps a work-around way I don't know. This is exactly what Used to do....very first I removed the fulltext catalog in the create database list because it was getting difficulties with it (regardless of how I'd it) and could create/attach the database (though Used to do obtain a warning)

CREATE DATABASE DBNAME ON 
    (FILENAME = 'C:\Databases\DBNAME\Data\DBNAME_data.mdf'), 
    (FILENAME = 'C:\Databases\DBNAME\Data\DBNAME_indexes.ndf'), 
    (FILENAME = 'C:\Databases\DBNAME\Data\DBNAME1_data.ndf'), 
    (FILENAME = 'C:\Databases\DBNAME\Logs\DBNAME_log.ldf')
FOR ATTACH;
GO

I Quickly got the logical title and road to the fulltext catalog out of this...

SELECT * FROM SYS.DATABASE_FILES  WHERE TYPE_DESC = 'FULLTEXT'

Then introduced the database offline, repathed the fulltext catalog after which introduced the database back online with this particular...

ALTER DATABASE DBNAME SET OFFLINE
ALTER DATABASE DBNAME MODIFY FILE ( NAME = sysft_cat_full_text , FILENAME = 'C:\Databases\DBNAME\Data\FTData\cat_full_text')
ALTER DATABASE DBNAME SET ONLINE

To date I haven't needed to rebuild the catalogs yet