Error when backup database SQL to sofs shared folder

Huynh Minh Ngon 0 Reputation points
2024-12-17T11:38:30.9433333+00:00

BACKUP DATABASE testbackup TO DISK = N'\sofs01\SQL\1.bak'
when i run this sql command, i have error:
Location: mediaWrite.cpp:601

Expression: (m_pWriteBuffer->GetCurrentSize ()% GetBlockSize ()) == 0

SPID: 56

Process ID: 9276

Thread ID: 10672

Msg 3013, Level 16, State 1, Line 1

BACKUP DATABASE is terminating abnormally.

Msg 3624, Level 20, State 1, Line 1

A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support.

Completion time: 2024-12-17T18:29:23.5033805+07:00

I another sql server. I can run sql command to backup successfully.

this is my sql version
Microsoft SQL Server 2022 (RTM-CU16) (KB5048033) - 16.0.4165.4 (X64) Nov 6 2024 19:24:49 Copyright (C) 2022 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2022 Standard 10.0 <X64> (Build 20348: ) (Hypervisor)

How to fix this bug?

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
14,262 questions
{count} votes

4 answers

Sort by: Most helpful
  1. Erland Sommarskog 114.9K Reputation points MVP
    2024-12-17T22:03:39.9033333+00:00

    The error message as such is a bug in SQL Server. An assertion error is due to that in the program code there is an assertion check saying that "at this point, this condition is assumed to be true, and if it is not, we no longer know what we are doing, and we should get out of hear real quick, before we cause any more damage" and then they terminate your process.

    Since you have the most recent CU of SQL Server 2022, the correct action would be to open a support case. This assume that you have some form of support contract.

    I should make it clear that this is necessarily a bug in the meaning "this should work". The essence of the bug might just be that they should produce a normal error message without terminating the process.

    If I am to make any guess, I would run this command:

    fsutil fsinfo sectorinfo <volume pathname>
    

    On the machine hosting the share, replacing the angle bracketed part with the drive for the share. If any number is > 4096, this may be the problem.

    And, oh, if this is a share, shouldn't there be two backslashes in the beginning of the path?


  2. ZoeHui-MSFT 39,346 Reputation points
    2024-12-18T01:58:55.8433333+00:00

    Hi @Huynh Minh Ngon,

    Noticed that you have get the dump file and you are using Standard version.

    You may send the dump file to Microsoft to get directly help.

    Open a ticket to Microsoft support:

    Services Hub (microsoft.com)

    Regards,

    Zoe Hui


    If the answer is helpful, please click "Accept Answer" and upvote it.


  3. Zhou, Yun (CMOC) 0 Reputation points
    2024-12-18T07:18:53.91+00:00

    Have you tried accessing your local disk?Current bak command is stored in a shared folder.

    Bert


  4. John Marlow 0 Reputation points
    2024-12-19T13:17:56.07+00:00

    This bug involves all SQL used by Microsoft as of the Dec. 5th update. It affects MS Access, PowerShell, Visual Studio, etc.

    Please report this bug as I have to help Microsoft narrow down the cause.

    Thank you!


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.