Isql is not recognized as an internal or external command, operable program or batch file

Hi Guys,

We recently installed SAP NW7.3 Ehp1 on Windows 2008 server with Sybase database version 15.7,installation was successful without any error's,when I try to login to database its throw error

I logged in as SIDADm and exeuted below command and end up with below error,

D:\sybase\SBP\OCS-15_0\bin>isql

Password:

CT-LIBRARY error:

ct_connect(): directory service layer: internal directory control layer

error: Requested server name not found.

Could any one help me out with how this can be fixed?

Regards

Uday

1. cant get ISQL to work with xp_cmdshell

   I have copied a script from the web that allows me to run scripts from a file over multiple databases(have attached file). Now everything works fine on my local SQL server but when I try to run it on my web server I get this msg
   ''isql' is not recognized as an internal or external command, operable program or batch file.'

   I have tried to use the full path to the isql.exe file but still get the msg

   Thats about as much info I can provide, my understanding of this is very slight

   ---

2. Do you have SQL Client (isql.exe) installed in your web server?

   Do you use sql login or windows login to run isql.exe?

   ---

3. ISQL is installed

   Yeah I have ISQL on the server. I can run it fine from the command prompt window by typing 'isql'.

   If my understanding is right doesn't the xp_cmdshell just run as if it were the typed in to the command prompt.

   ---

4. How are you running the script in your web server? You said running isql from command prompt is fine.

   Are you scheduling it using AT command?

   ---

5. I'm running the script from Query Analyzer. I have included the script as an attachment to this post, but here is the line thats causing the problem -

   SELECT @SQLString= ' Exec('' master..xp_cmdshell '+ '''''isql -E -d'+'"'+'['+@dbname+ ']'+'"'+' -i'+ @file + ' -o'+'"' + @OutputFile + '"'+ ''''' '')'
   EXEC(@SQLString)

   All the variables are correct but it's the running of the ISQL thats causing the problem: confused:

   If you have any ideas on how I can run a script over multiple databases that doesn't involve ISQL that would help loads. All the database names are stored in a table for easy access.

   ---

6. Fixed it for now

   I have managed to fix the problem.

   

   I had to put the exact path to ISQL in 8.3 file format ie 'Progra~1\Micros~3\80\Tools\Binn\isql.exe'

   Not sure if this was a windows thing or an SQL thing but it's working again so thank you for your help

   ---

Hi,

I have TCL (scripting language) running on my server.  I can run it from the command line, but when I type in:

exec master..xp_cmdshell "tcl c:\tcl_scripts\finddate.tcl"

in an isql window, I get the error:

'tcl' is not recognized as an internal or external command,

operable program or batch file.

Any ideas as to why I can run this from the command line and not the isql window?

Thanks!

We've got a couple of scripts that we routinely run on several SQL
servers, and they usually run fine. But we're trying to run them on one
particular server, and we're running into problems. I'm no expert with
SQL, but two DBA's who I work with have spent hours on this and they're
stumped, so I don't feel so stupid. Maybe someone here can help.

Basically, we've got a .bat file that calls a .sql file. Within the
..bat file, isql is called a couple of times with no problems. Within
the .sql file, there are several lines like:

exec master..xp_cmdshell @@cmd

@@cmd has previously been defined as a text string that begins with
isql.

Whenever this runs, we get the error:

'isql' is not recognized as an internal or external command,
operable program or batch file.

In other words, it can't find the file isql.exe.

We already made sure that the Windows PATH variable for the user
running the .bat file includes the folder that has isql.exe in it.
Someone said that they once had a problem where that folder had to be
the first folder in the PATH variable in order to recognize isql, so we
even made that change (and logged off and back in, then checked the
path from a DOS prompt to make sure the change took effect).

Anyone know anything else to check that would explain why our sql
script would be unable to find the isql.exe command? Any help would be
greatly appreciated.

--Richard

How do I connect to Isql on Windows?

What is Isql command?