View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002532 | SymmetricDS | Bug | public | 2016-03-22 16:01 | 2016-03-29 18:13 |
Reporter | elong | Assigned To | elong | ||
Priority | normal | ||||
Status | closed | Resolution | fixed | ||
Product Version | 3.7.0 | ||||
Target Version | 3.7.31 | Fixed in Version | 3.7.31 | ||
Summary | 0002532: Some Windows environments unable to command line sym and symcc | ||||
Description | Some Windows environments are failing to run command line utilities (sym.bat, symcc.bat, symadmin.bat). When the installation includes installing the service and running the service, that fails also. The setenv.bat script sets up the SYM_HOME environment variable using the following: pushd %~dp0.. for /f "delims=" %%i in ('cd') do set SYM_HOME=%%i popd It starts in the script's directory represented by ~dp0, which it remembers with pushd, and also changes to the parent directory. Then it runs the "cd" command to get the current directory, but a system directory is returned instead. Using the %CD% environment variable worked instead: for /f "delims=" %%i in ('echo %CD%') do set SYM_HOME=%%i | ||||
Steps To Reproduce | Setting a registry key that forces each command run to start in a specified directory: HKLM\Software\Microsoft\Command Processor ; AutoRun - REG_SZ - "CD /D C:\Program Files\Amazon\AWSCLI" | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2016-03-22 16:01 | elong | New Issue | |
2016-03-22 16:01 | elong | Status | new => assigned |
2016-03-22 16:01 | elong | Assigned To | => elong |
2016-03-22 16:46 | elong | Steps to Reproduce Updated | View Revisions |
2016-03-22 17:04 | elong | Status | assigned => resolved |
2016-03-22 17:04 | elong | Fixed in Version | => 3.7.31 |
2016-03-22 17:04 | elong | Resolution | open => fixed |
2016-03-22 18:00 | admin | Changeset attached | => SymmetricDS 3.7 158761b9 |
2016-03-29 18:13 | chenson | Status | resolved => closed |