1

Closed

Issue with automated pal report generation

description

I have a series of process that collect blg files from remote server and during off hours it generates a whole bunch of pal reports. When i run this process while logged on it works fine. when i schedule it i get the following errors in random. It is never the same each day.

12:29:29 - INFO - System.Management.Automation.PSArgumentNullException: Cannot process argument because the value of argument "exception" is null. Change the value of argument "exception" to a non-null value.
at System.Management.Automation.ErrorRecord..ctor(Exception exception, Object targetObject, String fullyQualifiedErrorId, ErrorCategory errorCategory, String errorCategory_Activity, String errorCategory_Reason, String errorCategory_TargetName, String errorCategory_TargetType, String errorCategory_Message, String errorDetails_Message, String errorDetails_RecommendedAction)
at System.Management.Automation.PSRemotingChildJob.ProcessJobFailure(ExecutionCmdletHelper helper, Exception& failureException, ErrorRecord& failureErrorRecord)
at System.Management.Automation.PSRemotingChildJob.DeterminedAndSetJobState(ExecutionCmdletHelper helper)
at System.Management.Automation.PSRemotingChildJob.HandleOperationComplete(Object sender, OperationStateEventArgs stateEventArgs)
at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
at Microsoft.PowerShell.Commands.ExecutionCmdletHelperComputerName.RaiseOperationCompleteEvent(EventArgs baseEventArgs)
at Microsoft.PowerShell.Commands.ExecutionCmdletHelperComputerName.StopOperation()
at System.Management.Automation.Remoting.ThrottleManager.StopAllOperations()
at System.Management.Automation.PSRemotingJob.StopJob()
at Microsoft.PowerShell.Commands.RemoveJobCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()

file attachments

Closed Oct 3, 2013 at 7:08 PM by ClintH

comments

ClintH wrote Oct 24, 2012 at 4:13 AM

It just looks like you are missing an argument to one of your WMI calls in your script. You must have this script run as a domain account that has admin rights to the target computers.