Windows 2008 cscript.exe Application error 0xc0000142 - heap-memory

After cscript.exe crashed, which ran fine for a few days then crashed at every and all instances, after that, Tidal agent (a batch jobs management s/w) started to crash. Need reboot to recover from the errors. Does anyone have any experience about this rarely used cscript.exe, and its behaviors, and what applications may have spawned this process, or how to trace the sources?
errors:
Faulting application cscript.exe, version 5.7.6002.18960,
time stamp 0x5257601e, faulting module kernel32.dll, version 6.0.6002.19623,

Most likely source is Win 2008 Health Service Modules, which launches cscript.exe at every 2 to 15 minutes interval. The script may be blocked by AV. After a few days, it may have caused heap to overflow, and crashed the system. The root cause may be that someone is configuring SCOM or AV incorrectly.
ETW: Operations manager event ID 21406:
Command executed: "C:\Windows\system32\cscript.exe" /nologo "MpDiscovery.vbs" {47E94BF5-C34B-7BDD-F6DA-DD648464CCB3} {02CB7C34-1EEB-821E-2E9C-488387B6266F} HOUCO2IMAGE1..com
Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 1662\3047\
and event 21405:
The process started at 6:21:25 AM failed to create System.PropertyBagData, no errors detected in the output. The process exited with 1
Command executed: "C:\Windows\system32\cscript.exe" /nologo "Microsoft.Windows.Server.Legacy.FreeSpace.vbs" HOUCO2IMAGE1..com false
Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 1184\1409\
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.Server.2008.Legacy.LogicalDisk.FreeSpace.Monitor

Related

Plesk Scheduled Tasks - Deny: Previous script did not finished yet

I had a script added to the Plesk's scheduled task, then, I removed it from the scheduled task, but it was still running in background and using lots of CPU, so I killed it via shell htop, Now I am trying to add that script back to the scheduled task again, But when I run it I am getting following error
Deny: Previous script did not finished yet
I have tried deleting the entries from "longtasks" table via a shell command
plesk db "delete from longtasks"
But that didn't work.
I have the following version of Plesk and operating system on my server
Plesk Version: Onyx 17.8
Operating System: Ubuntu 16.04 Server LTS
ScreenShot of error
please Let me know if anybody have any suggestion, Thanks!
Looks like the script is finished properly, as far as Plesk concerns, while Deny: Previous script did not finished yet message is the output of the script itself.
Try running it manually to make sure, and then review its's content to fing why it is not executing as expected.

How to Correctly Setup the Backup and Restore App?

Each time I run the Microsoft Windows Backup and Restore App that is left over since the Microsoft Windows 7 Operating System, I get an error that some Files are missing and the Backup Process fails.
The Files are actually Folders. I have uninstalled some Apps in the meantime and now there is only one missing Folder that the Backup App does not find.
I have tried to run a Batch File within the CMD.EXE Command-Line Processor App with System Administrator Rights:
#ECHO OFF
SET DIR1="C:\Windows\System32\config\systemprofile\OneDrive\Pictures\Saved Pictures"
MKDIR %DIR1%
PAUSE
The Folder does get created well and nice, but the Backup App is still failing.
Could it be a Rights Dead-Lock?
I am creating the Folder using System Administrator Privileges because it is not possible otherwise.
I suspect that the Backup App is run with Normal Rights. However, the User Account that I am using is also part of the Administrators Group.
Please advise.
I could not reproduce this Issue.
The reason why I guess that this is happening is the following one:
The Microsoft Windows Insider Program is constantly rewriting the whole C:\Windows Folder on each Update, therefore the Folders that are missing have to be constantly recreated.
Earlier, I might have manually started the Microsoft Windows Backup and Restore Application and forgot to run the Batch File. The Application might have started to work on the Files and Folders to back up. Then, I might have manually run the Batch File that correctly created the Files and Folders, but that might have been too late - that is, after the Application already considered them as missing. Therefore, the error was happening.
I do not know for sure whether this is the cause for this error since I have encountered it a number of times, not only once, and I do not feel that it was possible to have manually run the Batch File later than needed each time.
Anyway, a possible workaround for this Issue might be the following one:
Create a Scheduled Task that first runs the Batch File and then runs the Microsoft Windows Backup and Restore Application. I do not know yet how to tell the Scheduler to automatically run the Application, but I can imagine that it might not be difficult to achieve this goal.
Then, whenever the manual Backup is needed to be performed, one can simply manually run the Scheduled Task. This way, this Issue might not reoccur, at least because the previously suspected behavior should be avoided.
I need to perform the backup manually because I am using Removable Disks as a Third Backup Solution. The First One is the ASUS Web Storage Cloud Provider and Synchronizer Application and the Second One is the File History Application run on an External Winchester Hard Disk Drive.
If anybody has a better solution for this Issue, then please let me know.

Batch File to automatically abort shutdown

My computer shuts down every night starting at 9:59 and continuing until 11:59. I do not know why. I'm wondering if a .bat file could be written to automatically abort the shutdowns, or at least require confirmation?
It seems some unwanted software installed in your system. Check in the startup directory, remove any unwanted exe or batch files.
Check the scheduled task in windows using below command in older windows
at
After windows 7
schtasks.exe
Delete the unwanted tasks. Scan your system using Windows Defender
Below is the command used to abort the shutdown.
shutdown -a

Microsoft Release Management timeout during deploy step

We're using Microsoft's Release Management to deploy our web application to our test environment (QA). It is a straight-forward MVC.Net web application. Our build generates a web deploy package and we have a command script that sets some parameters based on the target environment (QA is just the first step), and then runs the standard Web Deploy command line tool. The command script works without errors when run from the command line outside of Release Management.
When we move this process into Release Management using the command-line tool, we encounter a timeout during the deploy step of the workflow. The error is:
The installation command \"powershell -command ./RunCommandLine.ps1 -FilePath 'Deployment\Deploy.cmd' -Arguments '/T:QA /E:intranet' -UserDomain 'domain' -UserName 'username' -UserPassword '*****'\" reached the configured timeout (2 minutes); the process was terminated.
We've checked the output log and there is no information from the script at all. We have echo commands in the beginning that should at least dump some output to the log before any action is taken.
The interesting thing is that when we click the "Retry failed deployment" button, the retry succeeds in about 15 seconds without any issues. This happens for each release - fails with timeout, retry succeeds in 15 seconds.
Any ideas from any release management gurus is greatly appreciated.
In release management , what deployment steps have you chosen ? i am assuming a powershell command ? can we do it using a xcopy ( works for me). Also i would request you do follow this blog on debugging the release mangement agent. opening the agent in debug mode has solved my problems or atleast told me about my problem most of the times. http://blogs.msdn.com/b/visualstudioalm/archive/2013/12/13/how-to-enable-detailed-logs-and-collect-traces-from-various-release-management-components.aspx

Slow backup routine message in Starcounter

I have Starcounter installed on my laptop (i7 mobile). Checking the logfile I found that I had several messages like this:
Memory manager unable to acquire the SE_MANAGE_VOLUME_NAME privilege. Applying slow backup routine
Why does this happen? If this affects the performance is there some way I can improve the installation to avoid this problem, or is this something that will only occur outside a server installation?
Memory manager unable to acquire the SE_MANAGE_VOLUME_NAME privilege. Applying slow backup routine
This is a warning message. It means that the backup will slow. It happens if the code host sccode.exe is run in not elevated mode (without Administrative privilege), which is normal case for Personal server and development environment.
This message will show performance problem in the case of running System server, i.e., in production.
The message should not appear if sccode.exe process runs in elevated mode. Note, that in this case all Starcounter processes and Visual Studio (if used) should be run in elevated mode.

Resources