I am trying to create a folder only if the folder does not already exist. I have a condition to detect when the folder is already created; however, it appears that an error message is being generated:

4/16/2009 11:44:57 AM Err Error in JobProcess (TaskConditionCheck), ex: Object reference not set to an instance of an object.


This is on 4.9.40.

Could you export your settings, the Condition and the Job, and attach it here? Alternatively, send it to support@visualcron.com

---

I think I already sent the settings. We have since upgraded to the latest version. and are receiving the same error message.

5/15/2009 10:24:43 AM Debug Job (353) was added to processlist: Internal_Backup_PRD_ALL_DB_Weekly_Full-Native
5/15/2009 10:24:43 AM Debug Running SQL Notification: 'Job Start - job_stats table on egovern'
5/15/2009 10:24:43 AM Debug Running SysLog Notification: 'Syslog: Task Start
5/15/2009 10:24:43 AM Debug Running Condition Set: 'native backup folder exists' for Task: make backup folder
5/15/2009 10:24:43 AM Err Error in JobProcess (TaskConditionCheck), ex: Object reference not set to an instance of an object.5/15/2009 10:24:43 AM Debug Running Condition Set: 'native backup folder exists' for Task: make backup folder
5/15/2009 10:24:43 AM Err Error in JobProcess (TaskConditionCheck), ex: Object reference not set to an instance of an object.


Sending email containg VC settings, logs, in separate email outside of this forum.

Perhaps you are referencing (in the Condition) to a Task or Job that no longer exists.

---

The condition does not name any specific jobs, but did have a macro in the condition.

The condition tests for whether a folder already exists based on a macro.

The macro is the same that is used by the make folder task bound to the condition that is reporting an error condition in the logs.


5/15/2009 12:11:34 PM Debug Running Condition Set: 'native backup folder exists' for Task: make backup folder
5/15/2009 12:11:34 PM Err Error in JobProcess (TaskConditionCheck), ex: Object reference not set to an instance of an object.

I tried to hard code the folder that it checks for instead of using a macro, and I get the same result.

Were you guys able to look at this?

Sorry for the delay. The problem is that VisualCron version 4 does not support Variables in that place. Support for this is added in version 5.

---

We are running 5.1.2 now and have the same problem.

What we did was running the Condition with a Variable. Got the same problem as you in version 4. When using this in version 5 we got not problems.

What if you simply this. Create a simple folder Condition containing a known path. Then change this value to a Variable.

There could be something with the Credential and access to the folder as well. That is why we need to take this step by step.

---

Okay, I've done this before, but have edited as suggested under 5.1.2. I hard coded the folder name in the condition, and set the condition to True if the folder exists.

5/20/2009 1:35:32 PM Debug Saving Jobs
5/20/2009 1:35:54 PM Info User "VisualCron Default Admin" - Updated ConditionSet (fde9d578-65ee-4db2-82dd-b7eeb94507ed)
5/20/2009 1:35:54 PM Debug Saving Conditions
5/20/2009 1:35:55 PM Info User "VisualCron Default Admin" - Updated Task: make backup folder
5/20/2009 1:35:58 PM Debug Job (911) was added to processlist: Internal_Backup_PRD_ALL_DB_Weekly_Full-Native
5/20/2009 1:35:58 PM Debug Running SQL Notification: 'Job Start - job_stats table on egovern'
5/20/2009 1:35:58 PM Debug Running SysLog Notification: 'Syslog: Task Start'
5/20/2009 1:35:58 PM Debug Running Condition Set: 'native backup folder exists' for Task: make backup folder
5/20/2009 1:35:58 PM Err Error in JobProcess (TaskConditionCheck), ex: Object reference not set to an instance of an object.
5/20/2009 1:35:58 PM Debug Task (2155) was added to processlist: make backup folder
5/20/2009 1:35:58 PM Info Task started: make backup folder (2155)
5/20/2009 1:35:58 PM Debug Running SQL Notification: 'Job Start - job_stats table on egovern'
5/20/2009 1:35:58 PM Debug Running SysLog Notification: 'Syslog: Task Start'
5/20/2009 1:35:58 PM Err Folder: \\stripped\Backup\Database\Auto\0000\0000\ did already exist.

😁

🤣

😕

Well, I tried this with both a UNC and a local path and it responds the same. The credentials for the task run under a Domain Admin for now.

I'm thinking of head butting a brick wall to solve this problem as it would be more productive than my current efforts.

We are trying to prepare your Job in our environment. The problem is something with the flow. Perhaps the Condition actions walk in a strange loop. This has nothing to do with with UNC path or other but rather how the task flows (what happens upon success and what happens upon failure).

We will try to reproduce this but it would be faster just to recreate the Condition that is used and make sure that you are pointing to right Task and Job in your Conditions that the Job or Task uses.

😁

🤣

😕

Well, I tried this with both a UNC and a local path and it responds the same. The credentials for the task run under a Domain Admin for now.

I'm thinking of head butting a brick wall to solve this problem as it would be more productive than my current efforts.

---

Are we talking about this Job: "Internal_Backup_PRD_ALL_DB_Weekly_Full-Native"?

If so, the problem might be a Condition that you have set on the first Copy files Task. It is not referring to any Task. It tries to refer to the previous Task but since it is the first Task there is no previous Task.

---

Yes, Internal_Backup_PRD_ALL_DB_Weekly_Full-Native is the job.

Perhaps this could be resolved by putting something into the make folder task that is able to handle the condition of a folder already existing, instead of making a separate condition for this.

The Previous task you are referring to may be due to me running this as a single task, without running the job. The behavior is the same for running the job or the task however.

The job does loop over tasks within it, it is part of the flow of the job. It basically acts like a while loop, with the value 0000 signifying the end of the loop. It should be noted that the behavior is still the same at the first instance of a task running or the last instance.

The first Condition will never work properly as you are not referring explicitly to the Task. You are using the Active which won't work as there is no Active Task before any Task within the Job has been run. Try removing that Condition from the Task and run the Job and see if the error disappears.

---