|
Home > Archive > SQL Anywhere database > June 2005 > Re: Path issue on Windows 2003 after installing ASA 8.03
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Path issue on Windows 2003 after installing ASA 8.03
|
|
| Steve M 2005-05-23, 8:23 pm |
| I had another report of this problem from a colleague today. Standalone development
PC with Windows XP on, not sure what version. Problem reported as Net Stop
and Net Start not recognised after installing ASA 8.03, error message: Command
"Net" not recognised.
Steve
> After installing ASA 8.03 on a customer Windows 2003 server, it
> stopped recognising commands such as NET (used to stop and start
> services with NET STOP and NET START). The puzzling thing is that it
> still showed the right path, with %windowssystem% or similar (working
> from memory here) environment variable as the first thing in the path,
> same as before the install. To make it work again they had to add the
> actual path to the Windows system folder to the end of the path. Does
> this ring any bells?
>
> Steve
>
| |
| Greg Fenton 2005-05-23, 8:23 pm |
| Steve M wrote:
> I had another report of this problem from a colleague today. Standalone
> development PC with Windows XP on, not sure what version. Problem
> reported as Net Stop and Net Start not recognised after installing ASA
> 8.03, error message: Command "Net" not recognised.
>
Can you post the PATH that they have before and after the install?
To get the PATH, start a new CMD shell and enter the command: path
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
| |
| Steve M 2005-05-25, 7:23 am |
| I can't get the PATH "before" but I've got the PATH after and the comment
from my colleague, "Apart from an entry from Pervasive, It looks as if everything
bar Delphi and Visual Studio has gone. This could explain a lot!"
PATH=C:\Program Files\Borland\Delphi
7\Bin;C:\Program Files\Borland\Delphi
7\Proje
cts\Bpl\;%SystemRoot
%\system32;%SystemRo
ot%;%SystemRoot%\sys
tem32\WBEM;C:\PVSW\B
IN;C:\PROGRA~1\Borla
nd\Delphi5\Projects\
Bpl;C:\PROGRA~1\Borl
and\Delphi5\Bin;C:\g
gpwin\programs;C:\Pr
ogram Files\Common Files\Adaptec Shared\System;C:\Pro
gram
Fi
les\Sybase\SQL Anywhere 8\win32;C:\Program Files\Sybase\Shared\
Sybase Central
4.
1;C:\Program Files\Microsoft Visual Studio\Common\Tools\
WinNT;C:\Program
Files\M
icrosoft Visual Studio\Common\MSDev9
8\Bin;C:\Program Files\Microsoft Visual
Stud
io\Common\Tools;C:\P
rogram Files\Microsoft Visual Studio\VC98\bin;C:\W
innt\Syste
m32
(Note: Winnt\System32 has been added manually to the end to correct the problem.)
Steve
> Steve M wrote:
>
> Can you post the PATH that they have before and after the install?
>
> To get the PATH, start a new CMD shell and enter the command: path
>
> greg.fenton
>
| |
| Greg Fenton 2005-05-25, 11:23 am |
| Steve M wrote:
> I can't get the PATH "before" but I've got the PATH after and the
> comment from my colleague, "Apart from an entry from Pervasive, It looks
> as if everything bar Delphi and Visual Studio has gone. This could
> explain a lot!"
>
I don't know what to say. Without the PATH before hand or a reliable
repro, it would be hard for anyone to figure out what caused the PATH to
get munged. Since the SQLAnywhere paths are in the "middle" of the
PATH, I find it hard to believe that the SQLAnywhere installer caused
the problem.
What are the USER and SYSTEM values of the PATH environment variables?
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
| |
| Steve M 2005-05-26, 7:23 am |
| WINNT and SYSTEM32 respectively.
Steve
> Steve M wrote:
>
> I don't know what to say. Without the PATH before hand or a reliable
> repro, it would be hard for anyone to figure out what caused the PATH
> to get munged. Since the SQLAnywhere paths are in the "middle" of the
> PATH, I find it hard to believe that the SQLAnywhere installer caused
> the problem.
>
> What are the USER and SYSTEM values of the PATH environment variables?
>
> greg.fenton
>
| |
| Greg Fenton 2005-05-26, 8:23 pm |
| Steve M wrote:[color=darkred
]
> WINNT and SYSTEM32 respectively.
>
Sorry, I meant what is the user's PATH and the system's PATH? You
likely need to look at them via Control Panel >> System >> Advanced >>
Environment Variables (though the location might be different under W2003).
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
| |
| Steve M 2005-06-13, 7:23 am |
| I haven't been able to extract any further information relating to that incident.
However a new report today from a customer site where we upgraded them last
week. Here is the text I received:
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).
Steve
> Steve M wrote:
>
> Sorry, I meant what is the user's PATH and the system's PATH? You
> likely need to look at them via Control Panel >> System >> Advanced >>
> Environment Variables (though the location might be different under
> W2003).
>
> greg.fenton
>
| |
| Greg Fenton 2005-06-13, 9:23 am |
| Steve M wrote:
> 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
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
| |
| Steve M 2005-06-13, 9:23 am |
| Okay, I take the point about new issues. I have a little more info on this
now. I got the following response to a query about PATH:
<<
This is what it is now after we changed it. There was one other value at
the start which we took out which was something like C:\Program~03\... but
didn't write it all down unfortunately.
%SystemRoot%\system3
2;%SystemRoot%;%Syst
emRoot%\System32\Wbe
m;C:\Program
Files\Common Files\Compuware;C:\P
rogram Files\Microsoft SQL Server\MSSQL\binn;C:
\Program
Files\Microsoft SQL Server\80\Tools\Binn
\;C:\Program Files\Sybase\SQL Anywhere
8\win32;C:\Program Files\Sybase\Shared\
win32;C:\Program Files\Sybase\Shared\
Sybase
Central 4.1
[color=darkred]
> Steve M wrote:
>
> Please post new issues in a new thread. Otherwise people may not pay
> attention to your new issue.
>
> 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
>
| |
| Steve M 2005-06-13, 11:23 am |
| I'll make a note to record the PATH before and after the next time I do an
upgrade from 7 to 8.
|
|
|
|
|