Forums » Beta

Thread: Exception running automation scripts from earlier beta

This question is not answered. Helpful answers available: 2. Answered answers available: 1.


Permlink Replies: 7 - Pages: 1 - Last Post: Sep 7, 2011 7:17 AM by: GeorgeJ
GeorgeJ

Posts: 4
Registered: 8/16/11
Exception running automation scripts from earlier beta
Posted: Aug 16, 2011 4:19 PM
 
  Click to reply to this thread Reply

Running Beta 6.0.0.1563.

None of my automation scripts that were created with beta 1454 will compile. I get the upgrade message when I open the script and say "yes" but when I try to run the script, I get the following exception...


Timestamp Message
8/16/2011 4:40:46 PM 'System.NullReferenceException' while invoking the validator 'System.Workflow.ComponentModel.Compiler.CompositeActivityValidator' on activity 'Workflow1': System.NullReferenceException: Object reference not set to an instance of an object.
at Quest.Toad.Workflow.Activities.Database.ImportWizardActivityValidator.Validate(ValidationManager manager, Object obj)
at System.Workflow.ComponentModel.Compiler.ValidationHelpers.ValidateObject(ValidationManager manager, Object obj)
at System.Workflow.ComponentModel.Compiler.ValidationHelpers.ValidateActivity(ValidationManager manager, Activity activity)
at System.Workflow.ComponentModel.Compiler.CompositeActivityValidator.Validate(ValidationManager manager, Object obj)
at Quest.Toad.Workflow.Activities.Database.DatabaseConnectionActivityValidator.Validate(ValidationManager manager, Object obj)
at System.Workflow.ComponentModel.Compiler.ValidationHelpers.ValidateObject(ValidationManager manager, Object obj)
at System.Workflow.ComponentModel.Compiler.ValidationHelpers.ValidateActivity(ValidationManager manager, Activity activity)
at System.Workflow.ComponentModel.Compiler.CompositeActivityValidator.Validate(ValidationManager manager, Object obj)
at System.Workflow.ComponentModel.Compiler.XomlCompilerHelper.ValidateActivity(Activity activity, WorkflowCompilerParameters parameters, WorkflowCompilerResults results)

The only way to get around this seems to be to create a new empty script and copy the activities from the old script to the new one.

Thanks...george


IgorM

Posts: 402
Registered: 2/16/10
Re: Exception running automation scripts from earlier beta
Posted: Aug 16, 2011 4:46 PM   in response to: GeorgeJ
 
  Click to reply to this thread Reply

George,

Can you post or send me directly (igor.manokhin@quest.com) any script (preferrably the simplest one ) that cause that error?
Thanks,

Igor.



GeorgeJ

Posts: 4
Registered: 8/16/11
Re: Exception running automation scripts from earlier beta
Posted: Aug 17, 2011 11:31 AM   in response to: IgorM
 
  Click to reply to this thread Reply

Hi Igor,

Attached are the problem files. "problem-before" is the script before the conversion and "problem-after" is the script after conversion that causes the exception.

george


IgorM

Posts: 402
Registered: 2/16/10
Re: Exception running automation scripts from earlier beta
Posted: Aug 17, 2011 1:09 PM   in response to: GeorgeJ
 
  Click to reply to this thread Reply

Thanks, I'll take a look.

Igor.


GeorgeJ

Posts: 4
Registered: 8/16/11
Re: Exception running automation scripts from earlier beta
Posted: Aug 17, 2011 5:59 PM   in response to: IgorM
 
  Click to reply to this thread Reply

Well, I am completely dead in the water as far as automation goes with this release.

First, I have completely cleaned Toad from my machine, including Application Data,AppData,ProgramData,Program Files (x86), and the registry, then re-installed 1563.

I create a new connection to my local database.
I go to Tools,Automation which opens a new Automation window.
I drag a Database Connection to the new window.
The connection pre-fills in the Activity Info pane.
I get an error saying the connection hasn't been specified.
Nothing I do removes the error.

I keep going anyway...
I go to the script Settings and make sure that Embed Sql is NOT checked.
I drag a Select to File activity to the connection.
I select a simple sql query.
The file name shows in the box, the Link Sql File checkbox selects itself, and the query text appears.
I go back to script settings, then back to the Select to File activity.
The file name is gone, the Link checkbox is unselected and greyed out.
The Sql is still there but I don't want the Sql embedded.

With a larger query, it gets even stranger...
I drag a Select to File activity to the connection.
I select a large sql query (about 3kbytes)
The file name shows in the box, the Link Sql File checkbox selects itself, and the query text appears.
I go back to script settings, then back to the Select to File activity.
The file name is replaced by the actual text of the query,the Link checkbox is unselected and greyed out, and the query text is gone from the box below.

I don't know what to do next.


IgorM

Posts: 402
Registered: 2/16/10
Re: Exception running automation scripts from earlier beta
Posted: Aug 18, 2011 12:14 PM   in response to: GeorgeJ
 
  Click to reply to this thread Reply

Let's go one step at a time.

First, about your problem with "...None of my automation scripts that were created with beta 1454 will compile...". I want to clarify that this particular problem persists for the scripts containing ExportWizardActivity and ImportWizardActivity only. Right between the betas you're talking about we made a change in those two guys adding connection properties to both but we didn't pay proper attention to compatibility with previous versions problems. Unfortunately, I cannot advise a workaround right now but I'll submit a CR (change request) and we'll try to address this problem in the near future. We will try but I cannot guarantee we will be able to fix this in the current release.

About problems you described in the last post. Some of them I can advise right now and to answer others I need to make a small investigation. I'll be back with more info a little bit later. The only thing I would like to mention right now is about using Database Connection activity. In current version of Automation we're making it obsolte. We're keeping it for compatibility only. Any database activity that needed Database Connection activity as a parent (container) in the previous release can live without it now. Any such activity has connection information in itself. That is why we advise not to use Database Connection activity when creating scripts in the new Automation from scratch.

Sorry for the inconvenience,

Igor.




IgorM

Posts: 402
Registered: 2/16/10
Re: Exception running automation scripts from earlier beta
Posted: Sep 2, 2011 10:02 AM   in response to: IgorM
 
  Click to reply to this thread Reply

Hello George,

Sorry for the late response but I'm glad to say that we addressed majority of the problems you've described in your post. I'm not sure all fixes are in the latest build but they will be for sure in the release  version.

Thanks,

Igor.



GeorgeJ

Posts: 4
Registered: 8/16/11
Re: Exception running automation scripts from earlier beta
Posted: Sep 7, 2011 7:17 AM   in response to: IgorM
 
  Click to reply to this thread Reply

Thanks Igor! I'll make copies of my scripts and give the new beta a try.


Legend
Guru: 2001 + pts
Expert: 751 - 2000 pts
Enthusiast: 31 - 750 pts
Novice: 0 - 30 pts
Moderators
Helpful answer (5 pts)
Answered (10 pts)

Point your RSS reader here for a feed of the latest messages in all forums