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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / SQL server died, movin...
Microsoft Dynamics AX (Archived)

SQL server died, moving DBs?

(0) ShareShare
ReportReport
Posted on by Community Member

Hello there, we have a MS AX 2009 server that connected to a SQL2008 server for a few years. Unfortunately the 2008 SQL server died (our last physical server) before we could virtualize it. We do have DB backups and I created a new (VM) SQL server 2014 using the same name and IP as the old SQL server. I restored the DBs but can't seem to get AX to connect.

Services on AX fail to start - 'service-specific error code 100'

I have added the ports the Server Configuration uses to the SQL server TCP/IP config and restarted.

Setup an ODBC connection to the SQL server from the AX server and it tested successfully.

I'm thinking this is permission related but the users were still existing in the restored DBs

Could it be incompatibility with SQL2014?

This solution was created by consultants years ago and we have no in house expertise. Searching around I don't see too many articles about this (maybe I missed them?) but some would have me change the SID for the DB admin account and that is where I thought best to ask here first.

Thanks in advance for any assistance!

j

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Hi

    I would start by looking if any of these guides would help. The situation you're in resembles "moving to a different domain/server" quite a lot.

    dynamicsessentials.net/.../how-to-move-your-ax-2012-deployment-to-a-different-domain

    community.dynamics.com/.../106710

  • Martin Dráb Profile Picture
    Martin Dráb 237,896 Most Valuable Professional on at

    I would think about permissions in SQL Server, namely that the AOS service doesn't have access to certain resources (the DB itself, stored procedure etc.). First of all, check event logs - they're usually quite specific.

    Are you using an existing AOS? It may be easiest to install a new AOS and connect to your database during installation, as the installer sets appropriate permissions (if you identify it as a problem with permissions).

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Thanks Steffen and Martin - great information. I noticed that the AX server services used 'NT AUTHORITY\NETWORK SERVICE', when I changed to my personal account as a test, (I have full permissions to the DB) they started and I was able to launch the .axc file successfully.

    I will set up an Active Directory account for the service - but I don't understand how it used to work set up like that.

    j

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    This is the issue with database security, as the service account that AOS runs as, need to have the full access to Dynamics AX database. If you look at Event Viewer, Application log should show additional details and error message “Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.”.

    Simple solution to fix the issue is to map Network Service account to db_owner role for Dynamics AX database. In SQL Server Management studio for the used instance, go to Database > Security > Logins. Here for service account login (NT AUTHORITY\NETWORK SERVICE), select Properties, then on User Mapping find the Dynamics AX database and map the account to db_owner role membership and to dbo schema.

    You don’t need to change SID for the admin account. This is required if you are changing network domains or changing access levels for the admin account, but I presume that you kept using the same domain and just changed the database server (keeping the name and IP).

    Note that SQL Server 2014 is not officially supported by Dynamics AX 2009, the latest supported SQL version is 2012 (requires a hotfix). If you’re running just database engine without SSRS/SSAS and you’re not installing AX from scratch, then it might still work with the newer SQL Server. However, for production instance, I would highly recommend to use only officially supported versions.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans