SSIS Error when deploying package, the locale identifier LCID is not supported by SQL Server

Lynn Carelse 21 Reputation points
2021-05-03T11:51:51.583+00:00

Hi

I am unable to deploy my project from Visual Studio to SSISDB. I have tried to change my localename and locale as well as my region. I have also made MYSQL Server login local but the below error still persists. Can anyone provide guidance

TITLE: SQL Server Integration Services

A .NET Framework error occurred during execution of user-defined routine or aggregate "deploy_project_internal":
System.Data.SqlClient.SqlException: The locale identifier (LCID) 15369 is not supported by SQL Server.
System.Data.SqlClient.SqlException:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnectionSmi.EventSink.DispatchMessages(Boolean ignoreNonFatalMessages) at System.Data.SqlClient.SqlDataReaderSmi.InternalNextResult(Boolean ignoreNonFatalMessages) at System.Data.SqlClient.SqlDataReaderSmi.NextResult() at System.Data.SqlClient.SqlCommand.RunExecuteReaderSmi(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at Microsoft.SqlServer.IntegrationServices.Server.ServerConnectionControl.GetServerProperty(String propertyName)
at Microsoft.SqlServer.IntegrationServices.Server.ServerConnectionControl.GetSchemaVersion()
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExecArgumentBuilder.ToString()
at Microsoft.SqlServer.IntegrationServices.Server.ServerApi.DeployProjectInternal(SqlInt64 deployId, SqlInt64 versionId, SqlInt64 projectId, SqlString projectName)
. (Microsoft SQL Server, Error: 6522)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=15.00.2080&EvtSrc=MSSQLServer&EvtID=6522&LinkId=20476

BUTTONS:

OK

Azure Database for MySQL
Azure Database for MySQL
An Azure managed MySQL database service for app development and deployment.
714 questions
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,748 questions
SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,454 questions
Accepted answer
  1. EchoLiu-MSFT 14,571 Reputation points
    2021-05-04T08:40:40.4+00:00

    Hi @Lynn Carelse ,

    Please try chang the following registry:

    HKEY_USERS[SID of user running VSDT]\Control Panel\International
    "Locale" change to 00000409
    "LocaleName" change to "en-US"

    Please also refer to the following article:
    SSIS – Error while deploying package The locale identifier (LCID) is not supported by SQL Server

    If you have any question, please feel free to let me know.

    Regards
    Echo

    If the answer is helpful, please click "Accept Answer" and upvote it.
    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.

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Erland Sommarskog 101.1K Reputation points MVP
    2021-05-03T21:39:54.7+00:00

    So what are you regional settings set to? Have you checked your system locale? (This is under Control Panel->Region->Administrative.)

    I had an issue where I got this error message, because I had my settings set to English(Sweden). As soon I changed things to Svenska (Sverige), things started working. (My issue was not with SSIB, but a CLR loopback that I had, and which only caused problems with MSSQLLOCALDB.)

  2. Lynn Carelse 21 Reputation points
    2021-05-04T15:21:00.65+00:00

    Hello

    The problem was that the running account was not set to local admin. The locale and localename seemed to have worked.

    Thank you very much