KB3132058 - FIX: Error occurs when you try to drop or delete filegroups or partition schemes and functions in SQL Server

Applies To
SQL Server 2012 Developer SQL Server 2012 Enterprise SQL Server 2012 Express SQL Server 2012 Standard SQL Server 2012 Web SQL Server 2014 Standard - duplicate (do not use) SQL Server 2014 Express - duplicate (do not use) SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Web - duplicate (do not use) SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use)

Symptoms

You create a full-text index that uses a full-text catalog in Microsoft SQL Server. If the catalog is very large, SQL Server might create some partition schemes and functions. These are saved in the filegroups. This behavior is expected. However, after you drop the full-text index and the catalog, those partition schemes and functions are not removed from the filegroups. Additionally, when you try to delete the filegroups that contain the partition schemes and functions, you receive an error message that resembles the following:

Note

Msg 5042, Level 16, State 12

The filegroup 'filegroup_name' cannot be removed because it is not empty.

        
If you try to drop the partition schemes and functions, you receive error messages that resemble the following:

Note

Msg 15151, Level 16, State 1

Cannot drop the partition scheme 'scheme_name', because it does not exist or you do not have permission.

Msg 15151, Level 16, State 1

Cannot drop the partition function 'function_name', because it does not exist or you do not have permission.

      

Resolution

This issue was first fixed in the following cumulative update for SQL Server:

      

Recommendation: Install the latest cumulative update for SQL Server

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included in the previous cumulative update. Check out the latest cumulative updates for SQL Server:

      

Note You can find information about the latest SQL Server builds from Where to find information about the latest SQL Server builds .

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology that Microsoft uses to describe software updates.