web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Import bacpac file exported from UAT to DevOps - Create User syntax error

(0) ShareShare
ReportReport
Posted on by 115

Hi all,

I try to follow this article:

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/database/dbmovement-scenario-exportuat

When import to DevOps I get this error

*** Error importing database:Could not import package.
Warning SQL0: The source contains users that rely on an external authentication provider that is not supported by the target. These users will be treated as users without logins.
Error SQL72014: Core Microsoft SqlClient Data Provider: Msg 102, Level 16, State 30, Line 1 Incorrect syntax near 'type'.
Error SQL72045: Script execution error. The executed script:
CREATE USER [d365-ops-dbms-prod]
WITH SID = 0xEB044DBB8A256343AD835337BE44B162, TYPE = E;

I usualy export UAT data to bacpac file manual but now I cannot access to UAT DB from SQL Server Management anymore so I used LCS tool, maybe there are some changes from last time I restored data from UAT to DevOps.

I have the same question (0)
  • TsutomuYanagida Profile Picture
    on at

    You may log a support ticket to MS for more assistance.

  • Verified answer
    Mea_ Profile Picture
    60,284 on at

    There is an issue in latest version of .Net Core, use .NET Core SQLPackage v18.4 that still works

  • DiepBH Profile Picture
    115 on at

    Thank You so much, It works perfectly :D

  • ShruthiKrishnaswamy Profile Picture
    20 on at

    Hi Ievgen,

    I tried using this, however I am still getting this warning while importing . Also, the import fails due to timeout. Any suggestions?

  • Mea_ Profile Picture
    60,284 on at

    Warning is just a warning and timeout can be increased, did you try to ? 

  • JoostBr Profile Picture
    on at

    For me worked

    - increase timeout on SQL server side, plus

    - increase timeout in import command, e.g.

    SqlPackage.exe /a:import /sf:J:\MSSQL_BACKUP\[yourbackup].bacpac /tsn:localhost /tdn:AxDB_[targetDB] /p:CommandTimeout=3600

  • ShruthiKrishnaswamy Profile Picture
    20 on at

    Yes Ievgen, the import completed successfully.

  • Srinivasa Raju Kosuri Profile Picture
    10 on at

    Thanks Ievgen. This worked for me.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 456 Super User 2025 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 429 Most Valuable Professional

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 239 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans