AX dymanics application not working post domain migration!!! Help!!!

(0) Share

Report

Posted on by Chethan

135

Hi All,

I am working on migrating a axdymanic application from one domain to another, as the old domain wil be shutdown in couple of weeks.

The application is designed in such a way that we have to have 2 SQL server, 1 Application object server, 1 Enterprise portal server and last one is for hosting.

As the usage is very minimal hence we have moved them to virtual instances from Physical box, using MS hyper V. So, currently we have 5 Virtual instances with the same setup but on a different domain, which doesn't have any relationship/link with the old servers/domains. So any id in the old in old domain doesn't exist in the new domain.

All the virtuals instances are hosted on windows 2008 Std. and the AXdynamic version is 4.0. We have tried to run the application but it doesn't work and pop's up an error "You are not a recognised user to use Microsoft dynamics AX, please contact your system admin"

We are able to access the DB and the services and they seems to be working fine but its just the GUI for this application is not working.

It would be great if someone can actually help me in getting this migrated to the new domain as I am not an expert in Dynamics AX.

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (2)

Suggested answer

Tommy Skaue Moderator on at

Like (0)

Report

Make sure the columns NetworkAlias, NetworkDomain and SID is correct in the table UserInfo in the Dynamics AX database.

Was this reply helpful? Yes No
Chethan 135 on at

Like (0)

Report

Hi Tommy,

Thanks for the response!!!

Can you please let me know the userinfo table which you are referring to? I am not able to open the application in my new domain but I can access the application from my old domain (which is currently active).

Please help!!!

Was this reply helpful? Yes No
Suggested answer

Tommy Skaue Moderator on at

Like (0)

Report

Connect to the SQL Server instance and the actual database itself in your target domain.

Run the SQL Query below on the business database:

SELECT ID, NetworkAlias, NetworkDomain, SID from UserInfo

You will need to verify all these values in the target domain. I would probably use PowerShell to get the correct values out from the target Active Directory. Get some SQL guy to help you update the table.

The Update SQL would look something like:

UPDATE UserInfo SET NetworkAlias = 'username', NetworkDomain = 'mydomain.local', SID = 'D95B4B27-000E-4125-95D2-44D85BFC0632' WHERE ID = 'admin'

(only an example!!)

Good luck, and if it works, remember to mark the answer.

Was this reply helpful? Yes No
fsilva-jr 20 on at

Like (0)

Report

Hello Guys!

Skaue, your solution is right! But instead of using powershell i can tell you another way to update the userinfo table.

This way just work if you have administrative rights inside AX and of course if you have access to the AX table for the new domain.

That's what i do most often.

After to have database and aplication configured into the new domain you just have do access the database server and open the UserInfo table and locate the correct fields. Now that you have the fields you just have to open the REGEDIT and expand the folowing key:

Computer\HKEY_USERS - Here you can find your own actual SID in the first big line. With this information you just have to change the correct userinfo table fields!

After to change the fields just access Ax and import new users.

When you have all the necessary access rights i think that this way is a faster!

Was this reply helpful? Yes No
Tommy Skaue Moderator on at

Like (0)

Report

By the way,

For the sake of auditing historical data being tagged with user ids, I do not recommend deleting the existing users in that table and reimport them. I would rather recommend exchanging the columns already mentioned.

My preferred way of getting my own (or someone else SID) is using this command:

[wmi]"win32_userAccount.Domain='nwtraders',Name='testuser'"

(blogs.technet.com/.../use-wmi-and-powershell-to-get-a-user-s-sid.aspx)

Was this reply helpful? Yes No
Chethan 135 on at

Like (0)

Report

Hi All,

Thanks for the reply..

Just to let you that we are able to access the application from the physical box using a specific admin ID, but the same ID is not available in my domain (I can create a new ID with the same name) as of now I am trying to access the application using my new domain ID with no changes being made in the SID table..this new ID does not have any entry in the Physical box..Please let me know as to where I should make changes in my registry? Do I have to copy the entries from my Physical box and put the same info in my virtual instance?

Please guide me :)

Was this reply helpful? Yes No
Verified answer

Tommy Skaue Moderator on at

Like (0)

Report

Just make sure you authenticate using a Active Directory User, and make sure the already mentioned columns have valid values. If you have the correct SID, Network Domain and Network Alias available, put it into the UserInfo table at the database level (using SQL Server Management Studio). There is *no changes* required in the registry. Fransisco was merely trying to help you find your own valid SID.

Was this reply helpful? Yes No
Verified answer

Chethan 135 on at

Like (0)

Report

Hi All,

We would like to inform you that issue is resolved :) I am able to access the application in my new domain :) and this is what I tried...

I executed the below VB script on the new virtual server..

"Win32_UserAccount.Name='name',Domain='your domain'"

“strComputer = "."

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")

Set objAccount = objWMIService.Get _

("Win32_UserAccount.Name='user ID',Domain='domain name'")

Wscript.Echo objAccount.SID”

with all the above entries I saved the file as SID.vbs and executed the script to get the sid entry.

Once I got the SID entry i updated the same in the userinfo table wherein I replaced the old SID entry with the new one along with changes in the NetworkAlias, NetworkDomain field. I restarted the services for all the instances and the application worked :)

Thanks a lot for yor help :)

Cheers,

Chethan

Was this reply helpful? Yes No
Tommy Skaue Moderator on at

Like (0)

Report

Beautiful!

While you could do the same with PowerShell, VB Scripting is still around and saves the day. Good job! Make sure to mark one of the suggestions as answers, Chetnan.

:-)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Tommy,

I attempted to bring one of our standalone development environments over to the new domain. We took down AX and SQL, changed all the services to manual, changed the machine address to put it into the new domain, then brought it back up and brought SQL, IIS, and then the AOS back online. I had scripted Powershell to retrieve SIDs in the new domain and a SQL script to map them into AX, as well as modifying other tables with the new domain name. After running that and a bit of work to change over all the service accounts and services, as well as application pools, I was able to successfully bring up the AOS and thought we were making great progress. Then I got stuck on not being able to refresh WCF for a new client configuration in the new domain, and despite some real effort I could not find a way to do it. Knowing we were this close, it’s hard to believe there isn’t a documented way to migrate AX to the new domain on existing installations. Even if I had to reinstall the AOS and client, that would be a lot less work than having to duplicate and rebuild everything from provisioning new machines, installing the OS, and then reinstalling and configuring our entire AX architecture—a feat that we cannot do quickly or inexpensively, and without disrupting further development.

Would it be worth opening a ticket with Microsoft to ask some of their engineers if this is possible?

Was this reply helpful? Yes No