MidServer dow after auto upgrade

[Victor Sarmento]

Hi everyone, everything fine? I'm having a problem with a specific MIDServer. At first, whenever I updated it, it was back to normal, but on the last update it didn't come back and it was down. And whenever I try to force the service it keeps updating and does not return. Analyzing the Mid server problems tab, I came across this warning:

WARNING: Ignoring addition of SVP03700ITOM01\srvp003itomlan01: SVP03700ITOM01\srvp003itomlan01: No mapping between account names and security IDs was done

and also when reading the logs during the upgrade I found this:

WARNING *** WARNING *** Null topic or source value detected: topic: HeartbeatProbe, source: null, sys_id: 5229ac991b606110d3c8415fe54bcbd0

Has anyone been in a similar situation and can help me?

[Allen Andreas · Accepted solution]

Hi,

Upon searching this and reading a few other threads, this may be a security issue and not actually a ServiceNow issue. I'd recommend checking out a few other forum posts, such as this: https://www.servicenow.com/community/developer-forum/unresolved-issue-while-upgrading-mid-server/m-p... and then speak to your internal team.

It could be related with the inability to swap out files/replace them on the upgrade.

Please mark reply as Helpful/Accept Solution, if applicable. Thanks!

[Johns Marokky · Accepted solution]

Hi @Victor Sarmento ,

Hi @Victor Sarmento ,

I think this might be something related to the user id issue.

Please check the below doc and see if it helps.

https://kb.netwrix.com/1145#:~:text=Here%20are%20possible%20reasons%3A,read%20account%20properties%2...

Also are you on Tokyo Patch 3? I had seen some community articles that most users found this issue in Tokyo Patch 3.

Please subscribe to the below community post as well.

https://www.servicenow.com/community/developer-forum/unresolved-issue-while-upgrading-mid-server/m-p...

Mark helpful if it helps in solving your query.

Regards,

Johns

[Appli · Accepted solution]

Hi, I suggest to restart Windows server. Restarting just MID service may not be enough under conditions you specified.

[Appli]

Hi, please try to restart MID servers and let us know if it helped.

[Victor Sarmento]

Completely restart the server or just the service? We have already started the Mid service on Windows several times and it tries more, it cannot update the patch and it always stays as dow.   

[Appli · Accepted solution]

Hi, I suggest to restart Windows server. Restarting just MID service may not be enough under conditions you specified.

[SiD2 · Accepted solution]

Hi @Victor Sarmento 

Even I see the first warning multiple times on my mid's but it seem no impact to me at least for discovery and was working fine.

The mid being down might not be related to this WARNING, however you need to open the mid agent log from the VM and observe for errors.

The second warning you can ignore, it will go off once your issue is resolved and mid is up.

Try doing a machine restart where mid was installed and see the service is started or not and check agent logs as suggested corresponding to that time frame.

[Victor Sarmento]

Hello, thank you all for the tips. however the solution was to uninstall and reinstall the MIdServer in the source , then it returned correctly. Thanks!