| Steve M 2005-06-22, 8:23 pm |
| This is happening every time. I have not been able to capture a before and
after, because other people are doing the installing, and yadda yadda. However,
the PATH variable is always corrupted after installing Sybase 8.03 in some
way (not sure how) that results in commands (including NET STOP etc.) are
not recognised and batch processes that normally run every evening will fail
after the installation. If somebody can just try it they will see. Just standard
issue version 8.03.5002, no EBF's or anything else. Here is a bit of text
from earlier:
> However a new report today from a customer site where we upgraded them
last week. Here is the text I received:
Please post new issues in a new thread. Otherwise people may not pay attention
to your new issue.
> We noticed a problem on Friday when trying to run a batch file we use to
copy files over from [------] for backing up files. It seems that when you
installed the new version of Sybase the other day it changed the path system
variable to look at a folder that didn't exist and thus the batch file couldn't
recognise any DOS commands. We've taken the first one out of the list now
and our batch files work again, (Sybase one is still there though).
We'd need a lot more technical details on this. Having a directory in one's
PATH that does not exist will NOT stop a batch file from executing.
greg.fenton
|