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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / CRM 2013 server setup ...
Microsoft Dynamics CRM (Archived)

CRM 2013 server setup failure. Organization database

(1) ShareShare
ReportReport
Posted on by Robert Cassar

We are trying to install a new instance of CRM 2013 onto new VM server. We have SQL server installed on a separate VM server. Setup is managing to create the CRM Config database but fails to create the organization database. We are getting the below error in the setup log file.

Install exception.System.Exception: Action Microsoft.Crm.Tools.Admin.CreateDatabaseAction failed. ---> System.IO.IOException: The network name cannot be found.

This is strange because the connection is not lost and the 2 servers are pinging eachother. Even the fact that the config DB is being created and Org DB is failing makes this a strange issue.

Has anyone encountered this error and can anyone suggest a possible solution?

*This post is locked for comments

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

    Try installing Reporting Extension in SQL server

  • Robert Cassar Profile Picture
    Robert Cassar on at

    The error is occuring during the setup of CRM full server installation wizard.

    So you are suggesting installing the Reporting Extensions in SQL Server before running the CRM 2013 setup?

    Wouldn't that fail since it will not find the CRM Config DB?

  • axtolf Profile Picture
    axtolf on at

    Hi, on the SQL there is only one instance of SQL ? Or you have more than one of them?

  • Robert Cassar Profile Picture
    Robert Cassar on at

    We created 2 new servers specifically to run the CRM setup. Yes the SQL server will only be used by CRM.

  • axtolf Profile Picture
    axtolf on at

    Asked because it happened to me with a server with four instance, with different versions of SQL on board (please, don't ask me why the customer decided it).

    I solved using FQDN of the SQL. It worked using an alias too.

    After it I had a problem with reporting extentions too, but it turned out to be a DLL problem

  • Robert Cassar Profile Picture
    Robert Cassar on at

    Thanks but unfortunately in our case is seems different. I am starting to think that it is something deeper than it seems.

    Any other suggestions ? We are stuck with this and cannot install the system.

  • axtolf Profile Picture
    axtolf on at

    Check if you are really able to reach SQL, telnet the server on the default SQL port.

    And check if the logs of CRM are telling something more.

  • Suggested answer
    Satish Tiwari - CRM Profile Picture
    Satish Tiwari - CRM Microsoft Employee on at

    I have also seen above behavior if anti virus in installed on CRM and /or SQL and blocking the .dll’s for SQL & CRM. Can you disable Antivirus on both CRM and SQL and then check the issue?

    If its fails then you can run Netmon and Procmon while installing CRM Server to check the calls and it will give more information about the issue.

    Download Netmon from www.microsoft.com/.../details.aspx

    How to use Netmon - support.microsoft.com/.../812953

    Procmon- technet.microsoft.com/.../bb896645.aspx

  • Verified answer
    Robert Cassar Profile Picture
    Robert Cassar on at

    We tried reinstalling the CRM and SQL from scratch on 2 new virtual machine setups and it worked without a hitch.

    Cannot explain what was wrong but it must have been something wrong with the Virtual Machines that we had created or some missing AD service roles.

     

    UPDATED: The error was with the setup of the Virtual Machines themselves. As explained in the link below

    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2058692

  • CgRuMy Profile Picture
    CgRuMy 397 on at

    we appear to have the same issue in crm 2016 - we cant seem to resolve it though...

    setup was able to create the MSCRM_Config db but we are unable to add a new or import an existing db

    System.Exception: Error.ActionFailed Microsoft.Crm.Tools.Admin.CreateDatabaseAction ---> System.IO.IOException: The network name cannot be found.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

#2
Mark Eckert Profile Picture

Mark Eckert 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans