Mid Server stuck at validating

[Ian Elrick]

Hi

I am now exploring the ITOM part of service now and have successfully installed a mid server and got it running. When I try to validate it however, the "validated" column on the midservers discovery view just sits at "validating". How long should validation take? Is there anything I need to do to the server itself other than select "Validate" on the related links?

Thanks in advance.

[Ian Elrick]

Hi

I got this working. I suspect it was synch issues between client and Midserver, my second rekey worked and it reached validated =yes. 

Regards

Ian

[Srinivas Cheer1]

Hope you got the answer but thought to place my comments, so will be useful for others as well.

It worked for me when I changed the MID Server timezone to the Instance timezone.

Refer: https://hi.service-now.com/kb_view.do?sysparm_article=KB0696701

Thanks,

Srinivas

[mholmes]

Hi Srinivas,

I think I may be encountering a time zone issue with some new MID Servers. They are stuck in a "Validating" state.

I'm not clear on which time zones are relevant to the matter.

Of:

- The time zone of the actual Windows server on which the MID Server is hosted.

- The time zone of the MID Server application (I haven't found a relevant property for this, I'm not sure if such a setting even exists).

- The time zone of the JRE in which the MID Server runs.

- The time zone of the ServiceNow instance.

Which ones need to match each other? The KB article is a bit confusing.

Thanks,

mholmes

[mholmes]

In my case, changing the time zone on the MID Server hosts to match the time zone of the instance, and then invalidating/revalidating the MIDs, did the trick.