I had this issue last week and had to change the paths in the bat
On a related note, when I had both installed side by side there was an
issue with a workspace runner. The batch file would specify the
program path to FME 2011, but the workspace runner would use the
default c:\program files\fme which was FME 2012. I kept having errors
until I ran the batch in 2012 so they matched. I don't think it was a
universal problem but impacted some of my workspaces.
Once everything was running on the same version, the errors went away.
On May 13, 10:26 pm, Hendrik Pischel <hendrik.pisc...@goog...>
> Hi Brendan,
> you should check if you have set the full path to your FME if yes you
> must change the tasks. If not this might be a path problem.
> Search for path and your Windows version to get a description how to
> change it. Delete the old FME path and add the new one.
> Regards Hendrik
> On 12 Mai, 23:26, BC <brendo.cunning...@gmai...> wrote:
> > Hi,
> > I instealled FME 2012 SP2 (Desktop) alongside FME 2011.
> > After the successful upgrade, I uninstalled FME 2011... leaving me
> > with only one version installed.
> > However I cannot get my batch files to run as scheduled tasks with the
> > new version installed.
> > The FME 2011 instance was installed at C:/APPS/FME, while I installed
> > the upgrade to C:/APPS/FME2012.
> > Is there something I need to do to tell Mr. Windows that all FME batch
> > files should be run with the new version?
> > thanks,
> > Brendan- Hide quoted text -
> - Show quoted text -