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 :
Microsoft Dynamics AX (Archived)

How to run full cil + db sync + publish reports in single user mode

(0) ShareShare
ReportReport
Posted on by 1,871

I am wondering how do people handle this scenario (2012 R2)

Production environment 24/7 shifts (2 client aos 1 batch aos). I need to take the server down for maintenance so I put it in single user mode/reject new clients so no one logs in while I do maintenance.

When in the single user mode I can import a model & compile the application. However whenever I click on the full cil button it never executes or if I try to publish reports (SSRS) and gives me an "unable to login" error

If I take it out of single user mode then I can do these things but people can log in which is no good. What do others do to handle needing to do full cils/publish reports on production environments while keeping the normal users out.

*This post is locked for comments

I have the same question (0)
  • nunomaia Profile Picture
    25 Moderator on at

    You can disable login’s in AOS.

    Check this technet.microsoft.com/.../hh433538.aspx

  • adam260 Profile Picture
    1,871 on at

    yes this is how you put the aos into 'single client mode' which is mentioned in the original post. The problem is once the system is in this mode I can not run a full cil or deploy my reports.

  • Verified answer
    Community Member Profile Picture
    on at

    You could have a dedicated AOS server for your operations that is not in a cluster and not in your configuration files (axc). Shut it down once your maintenance is done thus it won't transgress your licensing.

  • adam260 Profile Picture
    1,871 on at

    ah so under cluster config basically create a "maintenance" group or use the default group (right now we have a nonbatch and a batch group for the 3 aos') So we really should be running 4 in order to support our prod environment. But only turn on #4 during the maintenance period

  • Community Member Profile Picture
    on at

    Yeah.

    Put the fourth AOS in its own Cluster Group.

    Configure SSRS for the fourth AOS (in AX)

    Stop the first 3 AOS services

    Start the fourth AOS service

    Do you your maintenance in the the fourth AOS service

    Stop the fourth AOS

    Start the first 3 AOS

    People could connect to the fourth AOS, but the point is that they don't know the existence of this AOS...

    This is a recommendation based on what I am reading from your request.

  • adam260 Profile Picture
    1,871 on at

    One of the other ideas that was given to us is to create a job that would disable specific users and re-enable them upon completion. What do you guys think of that idea?

  • Verified answer
    Community Member Profile Picture
    on at

    Hmmm, not bad.

    So I am assuming that your script will disable all users, then you will do your maintenance  and then you will re-enable all users ?

    You will need to find a mechanism to make sure that you are not enabling users that were initially disabled.

    but the way, are you using the user with the ID "ADMIN" to generate CIL and publish reports ?

  • adam260 Profile Picture
    1,871 on at

    Correct I would write a quick mode that if the user was enabled and belonged to a specific role I would snap off the user name in a table and disable only those. Then when I wanted to turn it back on I would use the list in table of disabled users to re-enable them and then clear the table. Thus disabling/enabling only active users.

    As far as the admin account, my windows account is an admin on the aos and a sys admin role under roles. But I am not a domain admin. Is there maybe an account/account type that is always enabled are you thinking?

  • Community Member Profile Picture
    on at

    Got it for the first point.

    Log into Dynamics AX and open the users form. Find the user with the ID "ADMIN".

    Yes, I was thinking that this user would never be "rejected" since it has special privileges in AX, but I just tried and it is not the case.

  • Community Member Profile Picture
    on at

    I used to do exactly this through a SQL script. Disable all users but my own and re-enable them when I was finished. Yeah, I did have some method by which I did not enable users who were previously disabled. I don't remember now, since I now work somewhere that I can have a true maintenance window.

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!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Andrew Jones a1x Profile Picture

Andrew Jones a1x 2

#3
GL-01081504-0 Profile Picture

GL-01081504-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans