Unable to hot-swap the revised assembly to the server

(0) Share

Report

Posted on by Piyush Adhikari

2,546

Error 1 Unable to hot-swap the revised assembly to the server. If this is a test or development installation, configure the server to enable hot-swapping. 0 0 ITStaging

i m getting this error when i am trying to deploy Class Library project on server.

How can i solve this>??

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Verified answer

Piyush Adhikari 2,546 on at

Like (0)

Report

To Enable Hot Swapping of Assemblies

Open the Microsoft Dynamics AX server configuration utility by clicking Start > Administrative Tools > Microsoft Dynamics AX 2012 Server Configuration.

To change the server configuration, you must run the utility with administrative privileges.

On the Application Object Server tab, select Allow hot swapping of assemblies when the server is running.

Click OK. You will see a prompt that asks whether you want to restart the AOS service. The change will only take effect after you restart the AOS.

Got the solution :)

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

Like (0)

Report

Just make sure you do not enable hot-swapping in Production, or essentially not for any non-development AOS. :-)

Was this reply helpful? Yes No
Piyush Adhikari 2,546 on at

Like (0)

Report

sir. thanks for you valuable response.....

but why ?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

You should not use the hot-swap feature in your production environment. The AOS might consume a lot of memory due to an accumulation of application domains. Many assemblies would be loaded multiple times, which would waste memory resources.

Was this reply helpful? Yes No
Suggested answer

guk1964 10,888 on at

Like (0)

Report

The hot swapping option enables you to deploy assemblies to the server without the inconvenience of restarting the Application Object Server (AOS). Hot swapping of assemblies useful in development scenarios.

When hot swapping is off, the AOS contains one application domain and assigns all client connections to that domain.

When hot swapping is turned on before the AOS is restarted, a new application domain is created for each client connection. Each application domain loads the latest version of the assemblies. This means two application domains might contain different versions of the same assembly.

Note even in a dev/test environment after you have completed code change and compiled the assembly DLL for the last time, its still good practise to turn off hot swapping.

Inside Microsoft Dynamics AX 2012 adds this:

“However, you should never do this in a production server because any breakpoints that are encountered will stop all of the managed code from running, essentially blocking any users who are logged on to the server and processes that are running.”

The book goes on to mention performance issues as well.

To understand better read this article http://daxmusings.codecrib.com/2011/09/ax-2012-net-assembly-deployment.html

Last time I looked the installation default is to have the checkbox set on, so be aware.

Was this reply helpful? Yes No