78 views

Description

Several different files are left behind by Discovery and Service Mapping on target servers if LaunchProcess kills a script at timeout, or from particular pattern steps - C:\Temp.
There is no impact to functionality, and no errors are created. However the directory fills with junk which becomes a nuisance or potentially has issues with disk space.

This includes:

1/
When launchProcess is run, it will create a psscript-output txt file under C:\Temp on the host's disk. If this process fails and times-out, the process will be killed and the file that was created will be left behind.

2020-10-21 00:15:01 Running launchProcess
2020-10-21 00:15:01 $fullCommand: cmd /c "chcp 65001 & powershell > "\\127.0.0.1\c$\temp\psscript_output_163f05c1-6c6d-4ceb-a65c-4df43b38efea.txt" 2>&1"
2020-10-21 00:15:01 Using CIM session CimSession: 10.x.x.x to invoke CIM Method and create the process
2020-10-21 00:15:02 Running getProcess
2020-10-21 00:15:02 $proc: Win32_Process: cmd.exe (Handle = "69504")
2020-10-21 00:15:02 Running getProcess
2020-10-21 00:15:03 $proc: Win32_Process: cmd.exe (Handle = "69504")
2020-10-21 00:15:03 Running getProcess
2020-10-21 00:15:04 $proc: Win32_Process: cmd.exe (Handle = "69504")...........
2020-10-21 00:16:02 Running getProcess
2020-10-21 00:16:02 $proc: Win32_Process: cmd.exe (Handle = "69504")
2020-10-21 00:16:02 Command took more than 60 seconds, Killing process 69504

2/
Windows Server pattern
Failover step to get EC2 Details PS Script

2020-10-20 09:16:27: Put file on Windows host 10.x.x.x sucess [sic], file location is c:\temp\<instance name>\mid server name\<domain name>_cmdb_discovery\getEC2Detailsv3.ps1

Put script checking if this server is running on Azure

2020-10-20 09:16:33: Put file on Windows host 10.68.128.20 sucess, file location is c:\temp\<instance name>\mid server name\<domain name>_cmdb_discovery\ConfirmAzureVM.ps1

Steps to Reproduce

1/
This is tricky to reproduce. 
The left over psscript-output txt has been seen by a customer after upgrading to Orlando Patch 7.

2/
Discovery a windows host using pattern. These are likely to be left:

c:\temp\<instance name>\mid server name\<domain name>_cmdb_discovery\getEC2Detailsv3.ps1
c:\temp\<instance name>\mid server name\<domain name>_cmdb_discovery\ConfirmAzureVM.ps1

Workaround

This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available.


Related Problem: PRB1440904

Seen In

SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - SIG Assessment Legacy - Madrid 2019 Q1
SR - IRM - SIG Questionnaire - New York 2019 Q3
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - CMDB CI Class Models - 201909
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Security Incident Response UI Patch - London 2019 Q2 v.6.2.3
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - VR - Rapid7 - London 2019 Q2 v.6.2.1
SR - VR - Solution Management Madrid Q2
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Intended Fix Version

Rome

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-11-10 03:34:42
Published:2020-11-05