Upgrade Problem Solution Manager 7.01->7.1 in phase PREP_INPUT/INITPUT_PRE

[tobiasharmes]

Hi.

We have a little trouble with our upgrade (Solman 7.01, MS SQL Server 2005 SP4).

In phase PREP_INPUT/INITPUT_PRE we get this error:

Errors were found in the logfile MSSINCHK.LOG
after execution of the script MSSINCHK.SQL.
SAPup cannot proceed until these errors are fixed.
Please, examine MSSINCHK.LOG, fix reported errors and then call R3UP again

MSSINCHK.LOG:

HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. 
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

Our SQL 2005 allows TCP/IP and named pipe log ins.

We broke it down to this call (logged in toolout.log)

EXECUTING sqlcmd.exe -S ourhostname\SPS -E -d SPS -i D:\UPG\0_SOLMANUP\abap\bin\MSSINCHK.SQL -o D:\UPG\0_SOLMANUP\abap\log\MSSINCHK.LOG -h-1

If we execute it manually without "\SPS" after our hostname we get this:

 sqlcmd.exe -S ourhostname -E -d SPS -i D:\UPG\0_SOLMANUP\abap\bin\MSSINCHK.SQL -o D:\UPG\0_SOLMANUP\abap\log\MSSINCHK.LOG -h-1

SCRIPT MSSINCHK
=================
Msg 208, Level 16, State 1, Server Q021SPWMV1038, Line 6
Invalid object name 'SVERS'.
Execution completed successfully

So my question is: where does solmanup gets the SID from and how do we suppress this because it seems that solmanup is using the wrong parameters.

Cheers, Tobias

[Former Member · Accepted solution]

hi tobias,

please see if this might help you

http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

kind regards

marius

[tobiasharmes · Accepted solution]

Hi Marius.

Thanks. But we checked that already.

- Remote connections: TCP/IP and Named pipes

- Browser Service is enabled and running

- No firewall installed (this is Win Server 2003 and we are coming from localhost)

Cheers, Tobias

[Former Member · Accepted solution]

Hi,

chk out this

Thanks,

Jansi

[tobiasharmes · Accepted solution]

Hi Jansi.

Thanks. But still no luck.

- Service runs under Domain-Account

- We are not asked for credentials if we connect -> we are coming from localhost

Also in the meantime we updated our database library (lib_dbsl_166-10006351.sar) and Kernel (150 for Basis 7.01).

Just been thinking this could may be a 32-Bit problem -> Server is running Windows 2003 32 Bit.

Cheers, Tobias

[Former Member]

Hi Tobias,

have you tried this thread ?

Kind Regards

Marius

[tobiasharmes]

Hi Marius.

Checked the login credentials. Still no change.

SAP will make RDP on the server to make further checks.

Cheers, Tobias

[tobiasharmes]

I got an update from SAP support:

We had some rests of an old SQL Server Installation in our path environment variable:

"Microsoft SQL Server\80\Tools\Binn\" came before "Microsoft SQL Server\90\Tools\Binn\". We removed the old directory from our path. Unfortunately we still get the same connection error.

[sunny_pahuja2]

Hi,

Check below link:

http://technet.microsoft.com/en-us/library/ms190181.aspx

Thanks

Sunny

[tobiasharmes]

Hi.

Thanks for your repsonse. I checked the article, but it did not solve the problem. If I check "nestat -ban" I can see the services listening to 1433 and 1434 tcp and udp.

Cheers, Tobias