Hello @Bhuvan
I thank you for your engagement, and I do not want to discourage you from contributing, but rather provide feedback as to why your posts in this case were not helpful.
Your first answer linked to a suggestion to RDP into the MID server, even though I had specified that I was not able to RDP into the MID server because the username and password were not accepted. Then you suggested again that I RDP into the MID server below the link, again, after I specified that I was not able to RDP into the MID server. You then proceeded to suggest that I re-provision the instance even though I specified that i asked the automation to create a new instance and that had the same issues.
Your second reply suggest that there might be a white space when copying the password, completely disregarding that I wrote that I had carefully both typed and copied the password. You then suggested that I use the IP in stead of the FQDN, but if the issue was one of not reaching the MID server then the error would not be that the username and password were not accepted, but rather that the server did not accept the connection.
The most helpful item in your post was the suggestion to create a case with ServiceNow University support team, and that would have been my next step had the issue not resolved it self by the instance hibernating and waking up.
If you wish to be more helpful, please make sure that you thoroughly read and understand the issue that people are having, and do not provide suggestions that are already addressed in the original post.
Again, thank you for volunteering your time to help others with their problems.
