Finance | Project Operations, Human Resources, ...

Debug UAT Test Sandbox environment from cloud hosted Dev environment

(4) Share

Report

Posted on by FO user

199

Hello,

I need to debug the UAT Test Sandbox environment from the cloud hosted Dev environment. I followed the steps in the Learn article below and requested JIT database access in LCS for UAT. I added the Dev VM IP address to the UAT Sandbox environment whitelist in LCS. I then stopped all services on the Dev VM, modified the web.config and set the values exactly as mentioned in the Learn article.

After restarting the F&O services, I get a error 503 Services Unavailable and the error in the event viewer: The system cannot open the device or the file specified. I closed Notepad, Visual Studio etc so the web.config file cannot be locked. I restarted the Dev VM. I did IIS reset from CMD as admin and IIS reset from Visual Studio. Error remains. This is driving me mental.

Anybody have a clue why this is happening?

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

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (9)

Answers (0)

Martin Dráb 237,807 Most Valuable Professional on at

Like (0)

Report

Is there anything interseting on the Details tab?

Was this reply helpful? Yes No
Anton Venter 20,345 Super User 2025 Season 2 on at

Like (0)

Report

.

Was this reply helpful? Yes No
Suggested answer

Waed Ayyad 9,039 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

You can check my article connect-d365-test-db-to-the-development-environment, follow the steps and tell me if you want more help.

Thanks,

Waed Ayyad

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Suggested answer

Bharani Preetham Pe... 3,634 Moderator on at

Like (0)

Report

When you are editing the config file, did you modify the values for axadmin as well?

Also is this first time you are facing this challenge in your vm?

Also did you cross check all the values if you modified correctly without any mismatch and some tag removal?

I guess there is something when modified. So I would suggest you to re modify the original and try again.

Was this reply helpful? Yes No
Martin Dráb 237,807 Most Valuable Professional on at

Like (0)

Report

I see that one response disappeared, which stated that looking at the Details tab indeed helped; it revealed that a wrong user name was used.

You need to request just-in-time access on LCS, which generates a temporary user name and password, which is what you'll use to access the database.

Was this reply helpful? Yes No
FO user 199 on at

Like (0)

Report

I followed the Lean article but this resulted in the error message (which is the user does not have permission). I see that the Waed's blog adds a new user for debugging. This is the difference between the Learn article, it assumes the axdbadmin has permission on the Sandbox environment database while it clearly does not.

I modified the web.config file correctly as per Learn article and blog. This still resulted in the user access error. When I added a new user to the Sandbox database, I got a bit further but now have another issue. My user account is refused when I open F&O from the Dev environment and connected the Sandbox UAT environment. When I open the Sandbox UAT environment directly, my account works. I am using an account in another domain than the client's domain. And in my Dev VM, I am linked to the Admin account with my SID.

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,807 Most Valuable Professional on at

Like (0)

Report

You still have the same problem there. You shouldn't be using axdbadmin account; adding an F&O user is also irrelevant, because it doesn't grant access to the database. You need to go to LCS, open details of your UAT environment and request access to database:

This will generate a user name and a password that you need to access the database.

It's covered on the documentation page; you seemed to miss the Enable database access section, which refers to Enable just-in-time database access. When you read it, notice that there is one more step to enable remote connections to the database.

When requesting user credentials, use Performance tuning for AX (write to AX), not AX troubleshooting (read-only to AX). You need write access if you want to use the DB in an F&O environment.

Was this reply helpful? Yes No
Waed Ayyad 9,039 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

Is your issue resolved? If yes, mark the answers that helped you as verified.

Thanks,

Waed Ayyad

Was this reply helpful? Yes No
FO user 199 on at

Like (0)

Report

Thank you all for responding. Technically it's working now but I am still not able to log in the from Dev environment and debug. When I open the Sandbox UAT environment directly, my account works fine, but not from the Dev environment. I am using an account in another domain than the client's domain. And in my Dev VM, I am linked to the Admin account with my SID.

I have figured out what the issue was with the code, so debugging is not needed anymore.

Was this reply helpful? Yes No