Peter044
asked on
Unable To Import Tasks
I have just upgraded from a desktop running Vista to a laptop running Vista. They were different versions of Vista, but I am not sure which was which. The big difference that I've noticed is that the new machine is running 64 bit OS and the old one was 32 bits, which is causing some of my old applications not to run.
I had a number of tasks (as in Task Scheduler) saved by exporting them from the Task Scheduler so they could be imported to the new machine. However, when I try and import them, I get an invalid format message. Specifically:
"The format of the task is not valid. The following error was reported: (1,2)::"
I am unable to figure out what the error message means. The default extension the Task Scheduler is looking for is XML, while the saved format of the tasks is JOB, which the OS recognizes as a Task Scheduler Object.
Can anyone tell me how to import these tasks into the upgraded Task Scheduler?
Thanks,
Peter
I had a number of tasks (as in Task Scheduler) saved by exporting them from the Task Scheduler so they could be imported to the new machine. However, when I try and import them, I get an invalid format message. Specifically:
"The format of the task is not valid. The following error was reported: (1,2)::"
I am unable to figure out what the error message means. The default extension the Task Scheduler is looking for is XML, while the saved format of the tasks is JOB, which the OS recognizes as a Task Scheduler Object.
Can anyone tell me how to import these tasks into the upgraded Task Scheduler?
Thanks,
Peter
ASKER
Hi,
Thanks for your reply. The original export did not produce XML files, but these JOB files. I've uploaded one as an example though. It would be fantastic if that were the fix.
I've had to change the extension on the file to .TXT from .JOB to get it to upload here.
Peter
Morning-Edition--Weekdays-.txt
Thanks for your reply. The original export did not produce XML files, but these JOB files. I've uploaded one as an example though. It would be fantastic if that were the fix.
I've had to change the extension on the file to .TXT from .JOB to get it to upload here.
Peter
Morning-Edition--Weekdays-.txt
How did you try to export it from your vista Desktop?
On my Vista Home, I right click on the task and select export.
It's default format for saving it is XML and as you note it most definately is not XML.
On my Vista Home, I right click on the task and select export.
It's default format for saving it is XML and as you note it most definately is not XML.
Also as per http://social.technet.microsoft.com/Forums/en-US/itprovistamigration/thread/76b6276b-49f2-41e2-b4ea-f537e0eb88a8
There does not seem to be any native method for Vista to import job files.
I still find it interesting you got job files from your original export on your old vista machine.
There does not seem to be any native method for Vista to import job files.
I still find it interesting you got job files from your original export on your old vista machine.
Also as per my link (second to last comment) you could try this command on your new vista box.
schtasks /query /s xpmachine /tn taskname /XML > taskname.xml
So for each of your tasks it would connect to the machine called xpmachine, and export the task called taskname to a file called taskname.xml.
You might need to use the /U and /P parameters (for username and password) to connect to your old machine.
schtasks /query /s xpmachine /tn taskname /XML > taskname.xml
So for each of your tasks it would connect to the machine called xpmachine, and export the task called taskname to a file called taskname.xml.
You might need to use the /U and /P parameters (for username and password) to connect to your old machine.
ASKER
Sorry - just got back.
I'm not sure how either. To explain the complication, I had three machines at home. The one in question was some sort of a Vista upgrade from XP. I don't remember which flavor of Vista it was, but it seemed to act differently in several minor ways from my other machines. For example, it would always ask permission to run or change a task, even though it had administrative privs. It was an educational upgrade, but I don't recall if it was premium, home, office or whatever.
I can't do anything now as I'm on the road. The other machines are either packed or stored and the laptop I have is brand new, so connecting to the other machine is not really an option.
Was there anything recognizable in the files?
Peter
I'm not sure how either. To explain the complication, I had three machines at home. The one in question was some sort of a Vista upgrade from XP. I don't remember which flavor of Vista it was, but it seemed to act differently in several minor ways from my other machines. For example, it would always ask permission to run or change a task, even though it had administrative privs. It was an educational upgrade, but I don't recall if it was premium, home, office or whatever.
I can't do anything now as I'm on the road. The other machines are either packed or stored and the laptop I have is brand new, so connecting to the other machine is not really an option.
Was there anything recognizable in the files?
Peter
Hi Peter,
No worries,
For your first difference, thats actually pretty normal for Vista.
User Access Control (UAC) would have been enabled (which is the default), your other machines more than likely had it turned off.
Recognisable, Yes.
I could see that particular job ran up IE directing it to a URL. I have no idea on the frequency or when it was told to run.
Unfortunately it's not just a copy and paste of the bits you can read. (There are hex 00 characters after every character)
Heres an example of whats inside the job file if opened with Notepad.
C : \ P R O G R A ~ 1 \ I N T E R N ~ 1 \ i e x p l o r e . e x e
I still feel theres got to be some way, but running out of ideas.
No worries,
For your first difference, thats actually pretty normal for Vista.
User Access Control (UAC) would have been enabled (which is the default), your other machines more than likely had it turned off.
Recognisable, Yes.
I could see that particular job ran up IE directing it to a URL. I have no idea on the frequency or when it was told to run.
Unfortunately it's not just a copy and paste of the bits you can read. (There are hex 00 characters after every character)
Heres an example of whats inside the job file if opened with Notepad.
C : \ P R O G R A ~ 1 \ I N T E R N ~ 1 \ i e x p l o r e . e x e
I still feel theres got to be some way, but running out of ideas.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Huge effort - much appreciated.
Cheers Peter,
Never knew it would be such an antiquated way especially since Vista suppots creating them for backwards compatability.
If you want to get rid of the old .job files don't just delete them (Vista will re-create them I think)
In the scheduled task you have a "configure for" option, The Vista or Windows server 2008 only creates XML files in c:\windows\system32\tasks.
Up to you as to wether you need the ability to edit these tasks from Windows XP/2003.
Think it's time for a beer, and Microsoft should pay.
Glad to have helped.
Terry
Never knew it would be such an antiquated way especially since Vista suppots creating them for backwards compatability.
If you want to get rid of the old .job files don't just delete them (Vista will re-create them I think)
In the scheduled task you have a "configure for" option, The Vista or Windows server 2008 only creates XML files in c:\windows\system32\tasks.
Up to you as to wether you need the ability to edit these tasks from Windows XP/2003.
Think it's time for a beer, and Microsoft should pay.
Glad to have helped.
Terry
ASKER
Cheers Terry. We'll pay that.
Peter
Peter
Considering I'm in New Zealand I might take you up on that some day. LOL! :)
Have a good one.
Have a good one.
When you export your tasks it should most definately create am XML file you can load into notepad or the such.
Any chance you could upload a basic xml file thats failing to import?