We are upgrade ecc 6.0 to ehp4 level
Severe error(s) occured in phase PREP_INPUT/INITPUT_PRE!
Last error code set: Cannot open 'E:\usr\sap\EHPI\abap\log\MSSCONCHECK.LOG': The system cannot find the file specified.
Errors were found in the logfile MSSCONCHECK.LOG
after execution of the script MSSCONCHECK.SQL.
SAPehpi cannot proceed until these errors are fixed.
Please, examine MSSCONCHECK.LOG, fix reported errors and then call R3UP again
SAPehpi> Starting subprocess sqlcmd.exe with id 4600 at 20091126153716
EXECUTING sqlcmd.exe -S HYDHTC4524 -E -d ISI -i E:\usr\sap\EHPI\abap\bin\MSSCONCHECK.SQL -o E:\usr\sap\EHPI\abap\log\MSSCONCHECK.LOG -h-1
Environment: PATH=C:\SYSROOT\system32;C:\SYSROOT;C:\SYSROOT\SYSTEM;C:\SYSROOT\system32\Wbem;C:\Program Files\CA\eTrustITM\;C:\Program Files\CA\SharedComponents\ScanEngine\;C:\Program Files\CA\SharedComponents\CAUpdate\;C:\Program Files\CA\SharedComponents\ThirdParty\;C:\Program Files\CA\SharedComponents\SubscriptionLicense\;E:\usr\sap\ISI\SYS\exe\uc\NTAMD64
'sqlcmd.exe' is not recognized as an internal or external command,
operable program or batch file.
Process with ID 1640 terminated with status 1
It appears that the EhP is trying to execute the program sqlcmd.exe but it does not
exist in your server.
Is the DB running on a separate machine? If so, could you please try the
Copy from the ...\binn and ....\Resource\1033 library the sqlcmd.exe and
sqlcmd.rll and put them into the Windows library to get this to work.
You can get them from your DB server.
I hope this is helpful here.
I'm having same issue.
Our database is on a separate server as CI and I copied the 2 files as you suggested.
Again same error: Cannot open logfile for read D:\usr\sap\TE1\EHPI\abap\log\MSSCONCHECK.LOG
SAPehpi> Starting subprocess sqlcmd.exe with id 7684 at 20100603045111
EXECUTING sqlcmd.exe -S AM270S3403 -E -d TE1 -i D:\usr\sap\TE1\EHPI\abap\bin\MSSCONCHECK.SQL -o D:\usr\sap\TE1\EHPI\abap\log\MSSCONCHECK.LOG -h-1
Environment: Path=C:\Program Files\Support Tools\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\sysWOW64;C:\Program Files\System Center Operations Manager 2007\;C:\Program Files (x86)\Dell\SysMgt\oma\bin;D:\usr\sap\TE1\SYS\exe\uc\NTAMD64
Process with ID 4036 terminated with status 128
If you run into this error too, simply install "Microsoft SQL Server 2008 Command Line Utilities" if you use MSSQL 2008
an "Microsoft SQL Server 2005 Command Line Query Utility" if you use MSSQL 2005
btw. don't forget to set the Environment Variable PATH like: xyz;C:Program FilesMicrosoft SQL Server100ToolsBinn
save, start cmd, check if sqlcmd works, and start EHPI again!
Edited by: Tobias Pätz on Jul 15, 2010 6:33 PM
I am facing the same problem while doing EHP4 upgrade. Below is the error log of MSCONCHECK file:
SAPehpi> Starting subprocess sqlcmd.exe with id 4472 at 20100903020824
EXECUTING sqlcmd.exe -S LFTSQLECCD -E -d DEC -i D:\EHPI\abap\bin\MSSCONCHECK.SQL -o D:\EHPI\abap\log\MSSCONCHECK.LOG -h-1
Process with ID 5444 terminated with status -1073741515
Please do let me knothe steps in order to solve this error.
I am struck in same issue, i have installed the SQLCMD as told, but the environment variable you are mentioning... like ....\100\Tools\Binn there is no folder structure exist..... and after installing also i am struck in same phase.
EXECUTING C:\Program Files\Microsoft SQL Server\90\Tools\binn\sqlcmd.exe -S SOLAR04 -E -d P54 -i E:\usr\sap\P54\EHPI\abap\bin\MSSCONCHECK.SQL -o E:\usr\sap\P54\EHPI\abap\log\MSSCONCHECK.LOG -h-1
Environment: Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\j2sdk1.4.2_16\bin;C:\j2sdk1.4.2_12-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;E:\usr\sap\P54\SYS\exe\uc\NTAMD64
Sqlcmd: 'Files\Microsoft': Unknown Option. Enter '-?' for help.
Process with ID 6584 terminated with status 1
Hi Balaji, im facing the same issue, and it seems sqlcmd does not like spaces between folders name
EXECUTING C:\Program Files\Microsoft SQL Server\90\Tools\binn\sqlcmd.exe -S SOLAR04
Sqlcmd: 'Files\Microsoft': Unknown Option. Enter '-?' for help.
So it thinks Files\Microsoft is a parameter because its executing SQLCMD with the full path instead the command
As a workaround you can copy the entire binn directory into a temp directory like c:\SQL and then put in on the beginning of the PATH environment variable, restart the systema and it should work
How did you fix that?
The phase tries to start MSS command sqlcmd.exe but this file
is not recognized. You can see this from MSSCONCHECK.OUT.
So the command is not started and therefore the phase log cannot be
File sqlcmd.exe exists in directory
\binn, while this directory is not included in env variable PATH.
Please add it and then try again.
There was some problem in the OS .I have followed the below step
1)Click Start, click Run, type secpol.msc, and then click OK.
2)In the left pane, expand Local Policies, and then click User Rights Assignment.
3)In the right pane, double-click Impersonate a client after authentication.
4)Click Add User or Group.
5)Type service in the Enter the object names to select box, and then click OK two times.
6)Restart the computer.
Now i am to continue the installation
I have same issue outline above using SOLMAN upgrade program latest version 22 hence I think they could be an issue with the ABAP portion of the SAP upgrade tools
When I manually run the sqlcmd.exe -S OCSSLM1 -E -d SLM -i D:\SOLMANUP\abap\bin\MSSCONCHECK.SQL -o D:\SOLMANUP\abap\log\MSSCONCHECK.LOG -h-1 it does create the log file and response correctly.
When it runs through the upgrade it removes the log file .. very strange because it doesn't happen if I use the Solman upgrade version 13 released in June, but this Solman version create other issue like remove the instance SAP services in the down time phase.
Appreciate if anyone had other idea on the matter
Logged a call with SAP who provided a solution that fixed the issue. Basically I had to check %WINDIR% directory if sqlcmd.exe exists.
If so rename it and repeat the phase.
If you still cannot pass this issue, check if you have sqlcmd.exe & sqlcmd.rll in
C:\Program Files\Microsoft SQL Server\90\Tools\Binn. There should be one in the directory.
Please copy both items to the %WINDIR% directory and repeat the phase which works hence Solution manager upgrade could continue
Hope that may help someone else issue