Error in Log component :RedundantDIObjectRuntime2

Hi Jakob,

I have not seen this before, so I have no advice on how to proceed. Maybe others on here are familiar with this and knows where it originates.  The best I can offer at this stage is to log an issue with tech support - maybe they have encountered it before and can guide you - if not, thewy can raise an investigation with R&D to figure out what is causing it and to help you fix it - and, of course, to improve this error message so that in the future, it can help others figure out what is going on.

 - Ernst

Hi Jakob,

I have not seen this before, so I have no advice on how to proceed. Maybe others on here are familiar with this and knows where it originates.  The best I can offer at this stage is to log an issue with tech support - maybe they have encountered it before and can guide you - if not, thewy can raise an investigation with R&D to figure out what is causing it and to help you fix it - and, of course, to improve this error message so that in the future, it can help others figure out what is going on.

 - Ernst

Hi Ernst, I have my local distributor working on this, this has become a huge issue for my client and I have no idea how to fix it.  It seems totally random and been trying to steadily undeploy as much as i can from the galaxy to isolate it, it seems that it starts with different suitelink instances going on quarantine.

I am now considering completely wiping the machine and reinstall everything.  Thank you for your help. I will hopefully find a solution in the end and can share it here.

I had the appengines run overnight without any DI connection, now when i try to deploy one instance of a suitelink connection i get this message.

 Try deploy : on failure mark as deploy .. then undeploy properly then deploy properly ..

Hi Loris!  thank you for the suggestion, I actually noticed when trying to deploy a instance i got a message that it was already existing see screenshot

I also tried to undeploy everything except the platform hosting the appengines, I then had a look at the platform in the object viewer, there were deployed instances still running even though everything was shown undeployed.  see screenshot

So I will definately investigate this further 

I finally figured out what the issue was, after more then months work of rebuilding the galaxy from scratch (which didn't solve it) I noticed that when logging in and out of the nodes the errors started but in a random manner.  I then searched on the knowledge portal and found this article which finally clarified things. I therefore want to present the article to people on this forum because this was not obvious at all. The article from the knowledgebase in number 000032631, also attached in this post.  This is exactly the problem I have been fighting with.  Knowledge and Support Center.pdf