Support for WSF Jobs

Mon Nov 20, 2006 6:38 am

After upgrading to 4.1 I tried to open a WSF script I was working on in 4.0 a few days ago and the editor would not show any code. It did how ever list all four jobs and would allow me to run the code in debug mode. I was able to create a new WSF using your template that worked fine. However when I created a second Job via copy and paste (changing the job name) I saw the same behavior. Is this expected behavior or a bug?

Post by **Alexander Riedel** » Mon Nov 20, 2006 6:45 am

Nothing in regards to WSF file handling changed in 4.1
Can you email the WSF file (zipped) to support@sapien.com?
I assume the XML got mangled somewhere and if you send it I can take a look.

Alex

Post by **Alexander Riedel** » Mon Nov 20, 2006 7:02 am

I received your file and it loads fine.
I can open the embedded script in both jobs without problem.
Can you explain in more detail what it is that is not working on your machine?

Alex

Mon Nov 20, 2006 7:19 am

I had upgraded to 4.1 this morning when I was prompted by the editor. After starting the download I closed 4.0. I then ran through the setup. When running for the 1st time it prompted me for a role. I selected VBScript/System Admin. The next prompt was for registration. I logged on to the web site and completed the registration process. At that point I noticed I should have uninstalled my old product 1st but it was too late. I then looked up my old product key and fould the web page to give me my new key. I restarted 4.1 and pasted the new key when prompted again.
At 1st I though I had a bad install so I uninstalled 4.0 then 4.1 and rebooted. I reinstalled 4.1 and tested again. Same resaults.

My About PrimalScript... shows both 4.0 and 4.1 keys

Post by **Alexander Riedel** » Mon Nov 20, 2006 7:28 am

Ok. I understand that you basically have 4.0 and 4.1 licensing information but that has no bearing on WSF handling.

When I open the wsf you emailed me I see two jobs
in the workspace browser.

Expanding both I see an embedded script in both.

Double clicking on either script opens said script for editing.

Can you please verify this and tell me what it is exactly that is failing on your machine?

Thanks,

Alex

Mon Nov 20, 2006 7:47 am

I worked it out.

The Workspace Browser was hidden.

If I open a WSF with one job the embedded code opens in a tabbed window.

If I open a WSF with two or more jobs no window opens up. I had to open (unhide) the workspace Browser. Now I can double click the embedded tag to open the code window.

Thanks!

SAPIEN Technologies