Industry and services
The ideal digital transformation partner is not only an expert in theory and technology but also in its customer’s industry. Our consultants are familiar with the processes, priorities and challenges of these eight focus industries.
Contact us
Manufacturing companies
proMX has long been focused on supporting manufacturing companies with their digital transformation.
proMX services
proMX helps you tackle challenges by analyzing your processes and customizing your system with tailored solutions. In our discovery workshop, we'll pinpoint the right tools to boost productivity. Let’s get started!
This might be useful
Partners
Partnering with proMX Group to offer the proMX 365 Productivity Suite provides a unique opportunity to enhance your business portfolio and drive significant growth.
Become a Partner
Our mission
All companies strive to digitalize and optimize their processes, and thus become more productive.
About us
proMX is your digitalization partner. Our goal is to help you transform your processes to make your business more agile, efficient and competitive. As a Microsoft Partner we are both extremely experienced and well-connected.
More about proMX
Our mission
All companies strive to digitalize and optimize their processes, and thus become more productive.
Armin Odorfer
Nov 22, 2016 | Last updated: Dec 16, 2022
Expert articles | 2 min read

As a Microsoft Dynamics CRM partner, we sometimes have to import a customer database into our internal development environment. If the customer uses a language other than English in their Microsoft SQL server system, the following error may occur during import, shortly after the start of the Dynamics CRM Import Wizard:

Error 0x80131904 in the Import Organization Wizard
Figure 1: Error 0x80131904 in the Import Organization Wizard

Error| Import Organization (Name= , Id= ) failed with Exception:

System.Data.SqlClient.SqlException (0x80131904): The login already has an account under a different user name.

Step-by-step: how to solve error 0x80131904 in the Import Organization Wizard

To solve this problem, call up the Microsoft SQL Management Studio within the corresponding database server. There, you can expand the organization database *_MSCRM to the database user level.

Database user level in the Microsoft SQL Management Studio
Figure 2: Database user level in the Microsoft SQL Management Studio

In our example (German source system, English destination system), we have to delete the login “NT-AUTORITÄT\NETZWERKDIENST“ for Dynamics CRM to be able to import the organization. In other language versions, delete the equivalent login.

Deleting "NT-AUTORITÄT/NETZWERKDIENST" for Dynamics 365 CRM
Figure 3: Deleting “NT-AUTORITÄT/NETZWERKDIENST” for Dynamics 365 CRM

If you delete the user, you also have to delete the connected schema.

Pop-up "Do you want to delete the schema?"
Figure 4: Pop-up “Do you want to delete the schema?”

Subsequently, you can import the database into the Dynamics CRM system without problems. The deleted login will be created anew with the English name “NT AUTHORITY\NETWORK SERVICE“.


If you’re looking to fix the KB2720171 error message when you run an SSIS package in the SQL server, you’ll find help here.

Answering