Error after MID server reboot

[David131]

Hi all,

I am getting the following error on our MID server. LDAP sync seems to be working fine in ServiceNow, but our discovery schedules are having timeout issues. I am wondering if the two are related and how to fix this error. 

An unexpected error occurred: Command [enforcePerms "C:\Servicenowmid-Prod1\mid.kingston-10-17-2017__patch7-06-12-2018_06-21-2018_1724.windows.x86-64\agent" "snc_mid_Servicenowmid-Prod1" $false ""] timed out after PT2M

[Maik Skoddow]

Hi

are you really running a Kingston MID Server? Which main version is your instance? Also Kingston? I don't hope so. 

I think the error message is created at the PowerShell script /agent/bin/scripts/EnforceFilePermissions.psm1

Please open that script and read the comments at the beginning. There are some hints regarding the required permissions the MID Server user must have.

Kind regards
Maik

[David131]

Thanks for the reply. We are not running Kingston any more, that was the original install when we started up our instance. 

I looked through the powershell comments, our connected user is already added to the administrator group on the VM so it should have applied the correct permissions according to what is called out there.

[shloke04]

Hi,

For Mid Server related issue, below is the approach which I have followed in my past experiences and have always been helpful:

Please try this and let me know if this works for you:

1) Navigate to your MID Server and open the MID Server record.

2) Scroll down to Mid Server Configuration tab and add this property "mid.log.level" and set the value of this property as "debug"

3) Now in the MID Server record there is a related link named as "Grab MID logs, files and thread dump". Click on that related link.

4) Now you will be able to get log file under the Tab "Agent Logs" and there you open the record as "agent0.log" in Notepad where you can find the details which will be helpful in troubleshooting these m=kind of MID Server issues.

Let me know how you re going on this, screenshots will be helpful here to assist you further.

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

[David131 · Accepted solution]

After some log review I ended up just spinning up a new mid-server. It was the quick and clean fix.