Skip to main content
Solved

MWS Deployment status unknown, Error 'getCurrentState' was ot found


Technical Toby
Superhero (Employee)
Forum|alt.badge.img+14
Error when login to the Admin Console and get to the deployments
 

Hi there!

After Installation of UPDATE 10 during the weekend, I can now see in the Admin Console, that the deployments are all on yellow, unknown state.

Checking the Deployments section, I am receiving this error message.

I can not find any other hints in other logfiles. The system is running fine, customer is working with it. What is the issue? Why can the AdminConsole not find this functionality?

Kind regards,
Tobias

Best answer by Technical Toby

After rebooting the database, everything went fine again.

 

Shut down IFS

Rebooted the DB

started IFS again and all went fine.

 

So still unknown what this error meant and how it could be identified properly.

But the solution had been the complete restart of IFS and the DB.

Kind regards,
Tobias

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

4 replies

Technical Toby
Superhero (Employee)
Forum|alt.badge.img+14
  • Author
  • Superhero (Employee)
  • 149 replies
  • May 10, 2021

I found one case, where the message had been included, too.

 

It seems, after the restart of the database it has then turned out to be fine again. I will propose this to the customer. As it is the production system, the downtime should be after working hours :)

I will keep you posted.

 


Charith Epasinghe
Superhero (Employee)
Forum|alt.badge.img+13

@Technical Toby,

If you are going to suggest a DB restart, please ask to restart the application server as well. It is always better to go for a full restart.

 1. Stop IFS Application server services
 2. Restart the DB
 3. Start the Application Server services,

This will resolve if there is a problem with the application end. Also, it will clear if there are any hanging threads.


Technical Toby
Superhero (Employee)
Forum|alt.badge.img+14
  • Author
  • Superhero (Employee)
  • 149 replies
  • May 10, 2021

Hi @Charith Epasinghe 

 

That would be of course the default. 

I would never suggest a customer to kick the database without shutting down IFS.

 

Regards,

Tobias


Technical Toby
Superhero (Employee)
Forum|alt.badge.img+14
  • Author
  • Superhero (Employee)
  • 149 replies
  • Answer
  • May 26, 2021

After rebooting the database, everything went fine again.

 

Shut down IFS

Rebooted the DB

started IFS again and all went fine.

 

So still unknown what this error meant and how it could be identified properly.

But the solution had been the complete restart of IFS and the DB.

Kind regards,
Tobias


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings