Knowledge Base : Glossary : Suggest a Question
Search The Knowledge Base
Browse The Knowledge Base
Knowledge Base : RPOS

During the Patch(Version) updation meanwhile tool the following message arises: " Please Make sure OSQL command is Working from command prompt (OR) Copy and run the Service pack from C:\ Or D:\ "

Problem :

During the Patch(Version) updation meanwhile tool the following message arises: " Please Make
sure
OSQL command is Working from command prompt (OR) Copy and run the Service pack from C:\
Or D:\ "






SQL Tool Issue (Please Make sure OSQL command is Working from command prompt ):
-----------------------------------------------------------------------------------------------------

Reason :

when the DDL statements are loaded to the database using the sqlcmd command line tool the following
message arises: " OSQL is not recognized as an internal or external command, operable program or
batch file.”








Cause :

There may be several causes of the issue:

1. The system can't find the sqlcmd.exe (or bcp.exe, isql.exe) tool, because the path to this tool is not
specified in the System Environment Variable “PATH”

2. The appropriate tool is not installed to your computer

3. You have the different version of SQL Server (I mean more than two ), like 2000 and earlier version


SQL Issue Solutions :

1.The system can't find the sqlcmd.exe (or bcp.exe, isql.exe) tool, because the path to this tool is not
specified in the System Environment Variable “PATH”

Solution1 : If the cause of the error is in the System
Environment Variable “PATH”, then please specify the full path to the “Binn” directory in the SQL Server
installation folder, where this tool resides. The full path is specified on the “Advanced” page of the
“Choose a Target Database” page in SQLWays Wizard

Like below down written the Steps:
----------------------------------------
Set path on Windows

Add the path to your PATH environment variable

1. Find where you installed SQL. The default position at:

SQL2000 is "C:\Program Files\Microsoft SQL Server\ 80\Tools\Binn"
SQL2005 is "C:\Program Files\Microsoft SQL Server\ 90\Tools\Binn"
SQL2008 is "C:\Program Files\Microsoft SQL Server\ 100\Tools\Binn"

2. Copy all that.

3. Right click on My Computer and select Properties. The System dialogue should have appeared. On
Vista, choose "Advanced system settings" in the sidebar. On XP, choose 'Advanced' tab.

4. Now, click on "Environmental Variables" which is a button at the bottom right.

5. Under the category "System variables" which is the lower box, scroll down to "Path" and double click
on it.

6. In "Variable value", go to the end of all that text (Remember to put a semicolon down at the end of
the original text first or something bad may happen) and paste in the path of your SQL/bin directory.
The one you copied earlier. Then put a semicolon at the end of the SQL/bin text.

7. Here's what my Path value looks like: "set
PATH=%PATH%%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\W
bem;C:\Program Files\Microsoft SQL Server\ 90\Tools\binn\" (The
text highlighted in bold is what you may have to put down)

2. The appropriate tool is not installed to your computer

Solution2 : If the cause of the error is that the SQL was not
installed, then please install it.

3. You have the different version of SQL Server (I mean more than two ), like 2000 and earlier version

Solution3 : If the cause of the error in versions differences
between SQL Server 2000 and 2005/2008.

Eg: S/W running into the SQL Server 2000 but specified the incorrect target version of the database
2008 (I mean Default Instances issue)

In this case the command for the DDL import will be created using the SQL Server 2000 isql.exe tool,
which is replaced with the sqlcmd.exe tool in the SQL Server 2005 and higher


Windows spaces Issue (Copy and run the Service pack from C:\ Or D:\)
----------------------------------------------------------------------------------------------

Reason :

OLE( Object Linking and Embedding) connections issue

May display a large blank space for program path

May be appwiz.cpl registry was corrupt

Causes :

There may be several causes of the issue:

Error1 :

Error 193: %1 is not a valid Win32 application.

Cause : This issue may occur if the path of the executable file for the service contains spaces.

For example: If the path of the executable file for a service is C:\Documents and
Settings\Admin\Desktop\Desktop files\RPos7
RC73\PATCHES\Source\CentralServer.exe, and if a folder that is named C:\Program
also exists on your hard disk, Windows locates the C:\Program folder on your hard disk before the
C:\DocumentsandSettings\Admin\Desktop\Desktopfiles\RPos7RC70\PATCHE
S\Source\CentralServer.exe file, and then tries to run it.


Error2 : Windows cannot find

Cause: This issue occurs because OLE links that are created in Windows Vista or in later versions of
Windows use long file names (LFN) instead of 8.3 file names (SFN). However, Windows XP and Windows
Server 2003 do not correctly parse OLE links that use LFN.

Error3 :

An unexpected error occurred. Class not registered
res://appwiz.cpl/listbox.htc
Line:225

Error4 :

Object doesn't support this property or method res://appwiz.cpl/default.hta
Line: 75

Cause: DLL registration Meanwhile this Error was occurred because of a program incorrectly removes
registry entries that are used by Windows and the Add/Remove Programs tool


Windows spaces Issue Solutions :

Solution For Error1 :

1. Run the Service pack from C:\ Or D:\)


Solution For Error2 :

2.Replace each space in the file path of the OLE link with an underline. Then, open the OLE link in
Windows XP or in Windows Server 2003


Solution For Error3 & Error4 :

3. Herewith I have Enclosed FIX exe (microsoft fix exe) Just run this exe it will be resolved this issue
itself


-----------------------------------------------------------------------------------------------------------

Regards,
SULTHAN-A



Related Articles
There are no related articles


Viewer Comments Add Comment
No viewers have posted comments

Powered By AutoKB