I'm baffled about a connection problem when running dbisql after upgrading to Windows 10.
Before Win10 I ran commands like these from batch files or directly from the command prompt:
dbisql -nogui -c "uid=dba;pwd=***;dbn=fred;" START DATABASE 'c:\fred\source.db' AS "sourcedb" WITH TRUNCATE AT CHECKPOINT AUTOSTOP OFF; dbisql -nogui -c "uid=dba;pwd=***;dbn=fred;" read ENCODING CP1252 'C:\SVN\fred\trunk\Common\dbinit.sql' dbisql -nogui -c "uid=dba;pwd=***;dbn=fred;" select * from sys.systable
After upgrading to Win 10 I get no connection. From the command prompt I get "You are not connected to a database".
I tried using the both architectures of the full path to run dbisql.exe.
I can start ISQL if I run dbisql.exe with the connection string and then run individual commands that way, but that doesn't work with my batch files.
If I run:
dbisql -nogui -c "uid=dba;pwd=***;dbn=fred;"
I get a command prompt but any command I run just gives a "(Not Connected)" message.
I tried opening the command prompt in Administrator mode. No joy.
For now I'm using an ODBC connection in my parameters, and that lets me get my work done.
The dbisql with the "dbn" parameter and cmd.exe are not playing well together.
I am using SA 220.127.116.1154.
I did an uninstall, reboot and reinstall of SA.
Good new: That fixed the problem in my test "fred" database. It now queries from the command prompt with DBN and DSN. (woo hoo!)
Bad news: The reinstall hosed my real application, but that is a different problem. (crap! crap! crap!)
answered 29 Jul '16, 12:18