Share via

Adding file to filegroup containing filestreams does not work in SQL Server 2022 RC1 Express Edition

David Wimmer 1 Reputation point
2022-10-19T12:14:15.607+00:00

Hi,

just tested SQL Server 2022 RC1 Express Edition and I am getting an undocumented error when I am adding a file to a filegroup containing filestreams.
This only fails in the Express Edition adding the file/filegroup to an existing database.
Does not fail in Evaluation Edition or Developer Edition.
Does not fail when creating the file/filegroup with CREATE DATABASE.

Steps to reproduce:

  1. Install SQL Server 2022 RC 1 Express Edition with Filestream Feature
  2. Run the following script in SQL Server Management Studio
  3. CREATE DATABASE [FS_Test]
    ON PRIMARY
    (NAME = N'FS_Test', FILENAME = N'C:\databases\FS_Test.mdf')
    LOG ON
    (NAME = N'FS_Test_log', FILENAME = N'C:\databases\FS_Test_log.ldf')
    GO ALTER DATABASE FS_Test ADD FILEGROUP fsGroup CONTAINS FILESTREAM
    GO ALTER DATABASE FS_Test ADD FILE (NAME = 'FS_Test_fs', FILENAME = 'C:\databases\FS_Test_fs') TO FILEGROUP fsGroup;
    GO
  4. After ALTER DATABASE ... ADD FILE the following undocumented error occurs.

Msg 35221, Level 16, State 1, Line 13
Could not process the operation. Always On Availability Groups replica manager is disabled on this instance of SQL Server. Enable Always On Availability Groups, by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online.

The error is not listed database-engine-events-and-errors documentation.

The SQL Server installation ConfigurationFile.ini

----------

System Info:
Microsoft SQL Server 2022 (RC1) - 16.0.950.9 (X64) Sep 13 2022 13:09:32 Copyright (C) 2022 Microsoft Corporation Express Edition (64-bit) on Windows Server 2022 Standard 10.0 <X64> (Build 20348: ) (Hypervisor)

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,364 questions

7 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. David Wimmer 1 Reputation point
    2022-11-30T07:09:11.32+00:00

    I am currently in contact with a support engineer from Microsoft Technical Support regarding this issue.
    Will post an update as soon as I got one.

  2. David Wimmer 1 Reputation point
    2022-12-01T08:31:01.223+00:00

    Got an update from technical support.

    There is a workaround for this issue with enabling the trace flag 12324. 

    DBCC TRACEON(12324, -1)

    A server restart will reset the trace flags activated with DBCC TRACEON, so you have to add a startup parameter for permanent activation.

    266091-sql-server-startup-parameter.png

    The support engineer can not guarantee this will be fixed with a cumulative update, hopefully the will fix it.