It’s currently so hot in Vienna that the keyboard almost melts under your fingers. In this heatwave, of all times, I have a technical blog post for you on a very interesting topic.

Today, we’ll look at a problem, that was discused in a forum thread of the Automic Community. When trying to update the system, an unusual error message appears:

U00038140 Action not possible. Different Automation Engine systems were started with this database. Please check your database and try again.

After some detective work, I was able to find the bug. It was because the system had been renamed.

Why Would Someone Rename Their System?

The first thing you might ask now is, why this should be done in the first place. But recently I’ve come across this with several customers.

The reason was the same for all of them: In the course of an upgrade, they clone their system and then want to activate it (for example for upgrade tests). Then they rename the system so that there is no confusion.

What’s Behind the Error Message?

But let’s go through this process step by step. I have a system called “Automic”. You can see this name in the system settings, for example.

If I want to rename this system, I have to first log out and exit the system. After that I have to do the renaming in several places:

  • I open the Automation Engine configuration file ucsrv.ini and change the value of SYSTEM to the new name under [GLOBAL].
  • Then I change the two parameters name and system in the AWI configuration file uc4config.xml.
  • If agents are to connect to the system as well, I also have to enter the new name in the agents’ INI files.
Renaming in the AWI configuration file

The system has now been successfully renamed and when I start it everything works great.

But if I now want to upgrade the system and load the initial data of the renamed system via dbLoad, then the previously announced error message appears:

U00038140 Action not possible. Different Automation Engine systems were started with this database. Please check your database and try again.

How Can I Solve this Issue?

We can see what triggers this error message when we switch to the directory in the Process Assembly. For every process that I start, an object is created and stored in the <No Folder>. So there we find a lot of processes with the new system name, but also old processes that still have the old system name.

Server Process in the directory <No Folder>

This problem can easily be solved by deleting the objects with the old name in the process assembly.

If you do not have access to the system via AWI, you can also do this via SQL. In the HOST table we can also see the exact trigger for the error message. All objects that are displayed with the wrong name in the process assembly also have a different host version in the database. This wrong version triggers the error.

Column with different host versions of the processes. Click on the picture to enlarge it.

If these objects are deleted, the update starts without errors.

More Technical Tutorials?

Did you like this technical article? Then you should take a look at my platform membership.philippelmer.com. There I covered this topic in more detail in a webinar.

The platform also has courses, tutorials, and tools from me and other Automic experts. Members can also take part in up to 2 webinars per month and receive exclusive offers for workshops and consulting.

If you are interested, just look at it for a month free of charge and without obligation in the test version.

Philipp ElmerPhilipp

Get concentrated knowledge from 5 years of AutomicBlog

Download an archive with all old articles:

  • Features, SQL-Tricks, and handy Scripts.
  • 63 extensive articles (+ comments).
  • Used by Automic experts around the world.

Subscribe to the newsletter and immediately get all articles!

[caldera_form id="CF572741b60f87f"]