Getting error while running database backup maintenance plan

Question

I am getting error while running database backup maintenance plan, Backup is getting successful but job is failing with below error :-

Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 16.0.4135.4 for 64-bit Copyright (C) 2022 Microsoft. All rights reserved. Started: 12:18:58 Error: 2024-08-01 12:18:59.87 Code: 0xC002F210 Source: {1039D9F7-41A0-4E35-AB2D-A4B4AE5A1458} Execute SQL Task Description: Executing the query "DECLARE @Guid UNIQUEIDENTIFIER EXECUTE msdb..sp..." failed with the following error: "Culture is not supported. Parameter name: culture 3072 (0x0c00) is an invalid culture identifier.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error Error: 2024-08-01 12:19:00.59 Code: 0xC0024104 Source: Back Up Database (Full) Description: The Execute method on the task returned error code 0x80131501 (An exception occurred while executing a Transact-SQL statement or batch.). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2024-08-01 12:19:00.59 Code: 0xC0024104 Source: {B2FFA685-7EFB-4124-ACF0-F56FE644192B} Description: The Execute method on the task returned error code 0x80131501 (An exception occurred while executing a Transact-SQL statement or batch.). The Execute method must succeed, and indicate the result using an "out" parameter. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 12:18:58 Finished: 12:19:00 Elapsed: 1.906 seconds. The package execution failed. The step failed.

Answer 1

Hi @Shete Nitin ,

Thank you for your reaching out and welcome to Microsoft Q&A!

The 3072 (0x0c00) is an invalid locale ID, this looks like a corrupted Windows installation, perhaps from a flaky disk. We will get this error when it is on English (World) or English (Europe). Setting it to English (United States) solves it. I'm guessing that English (World) or English (Europe) were new formats with Windows 10, and SSMS is not prepared for it.

Please follow the steps below:

1. Go to Control Panel
2. Go to Clock and Region
3. Go to Regions and change the settings to English (United States).

Feel free to share your issues here if you have any concerns.

Best regards,

Lucy Chen

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

https://docs.microsoft.com/en-us/answers/support/email-notifications