4.6c on MS SQL 2000 Problem

[Former Member]

Hello SAP Gurus,

I'm trying to install a database Instance (on a database cluster system).

I allready installed the central instance, the database, database software and the r3setup-tool.

The Installation failed about 3%

The log says:

"WARNING 2009-05-29 11:05:23 DBCOMMONDBENV_NT_MSS CmdNGo:0

sp_server_info

[Shared Memory]SQL Server does not exist or access denied.

[Shared Memory]ConnectionOpen (Connect()).

ERROR 2009-05-29 11:05:23 DBCOMMONDBENV_NT_MSS InstallationDo:0

Phase failed.

ERROR 2009-05-29 11:05:23 InstController Action:0

Step DBCOMMONDBENV_NT_MSS could not be performed.

ERROR 2009-05-29 11:05:23 Main

Installation failed.

ERROR 2009-05-29 11:05:23 Main

Installation aborted."

it seems that the sapsetup cannot connect to the existing SQL2000 Database- buts definitive not a problem with user/permission cause I tried the installation with an global/domain/local/dbcluster admin too

The SAP Notes talking about checking the services and permissions but that isn't a solution for my problem...

[Former Member]

please send us detailed errro logs.

and also check if enough space present on all the filesystems.

[Former Member]

this is the whole error log:

INFO 2009-06-02 09:40:49 CommandFileController SyFileVersionSave:736

Saving original content of file G:\SAP\Install\DATABASE.R3S ...

INFO 2009-06-02 09:40:49 CommandFileController SyFileCopy:676

Copying source file G:\SAP\Install\DATABASE.R3S to target file

G:\SAP\Install\DATABASE.R3S.7 ...

INFO 2009-06-02 09:40:49 CommandFileController SyPermissionSet:2207

Changing permission for file G:\SAP\Install\DATABASE.R3S from 777

to 666.

INFO 2009-06-02 09:40:50 Main

Preparation successfully completed.

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:434

checking host name lookup for '<DB hostname>'

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:467

offical host name for '<DB hostname>' is

'wdfdv-dbcl01a.de.realtech.net'.

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:535

hostdb host name' has ip address '10.0.2.10'

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:575

offical host name for '10.0.2.10' is

'<DB hostname domain>'.

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:434

checking host name lookup for '<DB hostname>'

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:467

offical host name for '<DB hostname>' is

'DB hostname domain'.

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:535

host 'DB hostname' has ip address '10.0.2.10'

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:575

offical host name for '10.0.2.10' is

'DB hostname domain'.

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:434

checking host name lookup for '<central instance host>'

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:467

offical host name for '<central instance host>' is

'<central instance host domain>'.

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:535

host '<central instance host>' has ip address '10.0.2.85'

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:575

offical host name for '10.0.2.85' is <central instance host domain>'.

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:434

checking host name lookup for '<DB Host>

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:467

offical host name for '<db host> is

'<db hostname + domain>'.

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:535

host 'wdfdv-dbcl01a' has ip address '10.0.2.10'

INFO 2009-06-02 09:40:50 DATABASEINSTANCE_NT_MSS SyCheckHostnameLookup:575

offical host name for '10.0.2.10' is

'<db host name>'.

INFO 2009-06-02 09:40:50 CDSERVER46CSR2_NT_MSS CheckCopyDirectoryForCD:0

The directory, where the CD should be copied to, is not empty. We

will not copy to a notempty directory. This is not an error if

the directory contains already the CD.

WARNING 2009-06-02 09:40:50 CDSERVER46CSR2_NT_MSS CheckCopyDirectoryForCD:0

The CD KERNEL seems already be copied to G:\medien\Kernel. So we

will not copy. Please check this directory.

INFO 2009-06-02 09:40:50 CDSERVER46CSR2_NT_MSS InternalColdKeyCheck:0

The CD RDBMS will not be copied.

INFO 2009-06-02 09:40:50 CDSERVER46CSR2_NT_MSS CheckCopyDirectoryForCD:0

The directory, where the CD should be copied to, is not empty. We

will not copy to a notempty directory. This is not an error if

the directory contains already the CD.

WARNING 2009-06-02 09:40:50 CDSERVER46CSR2_NT_MSS CheckCopyDirectoryForCD:0

The CD EXPORT1 seems already be copied to G:\medien\Export\CD1.

So we will not copy. Please check this directory.

INFO 2009-06-02 09:40:50 CDSERVER46CSR2_NT_MSS CheckCopyDirectoryForCD:0

The directory, where the CD should be copied to, is not empty. We

will not copy to a notempty directory. This is not an error if

the directory contains already the CD.

WARNING 2009-06-02 09:40:50 CDSERVER46CSR2_NT_MSS CheckCopyDirectoryForCD:0

The CD EXPORT2 seems already be copied to G:\medien\Export\CD2.

So we will not copy. Please check this directory.

INFO 2009-06-02 09:40:50 CDSERVER46CSR2_NT_MSS CheckCopyDirectoryForCD:0

The directory, where the CD should be copied to, is not empty. We

will not copy to a notempty directory. This is not an error if

the directory contains already the CD.

WARNING 2009-06-02 09:40:50 CDSERVER46CSR2_NT_MSS CheckCopyDirectoryForCD:0

The CD EXPORT3 seems already be copied to G:\medien\Export\CD3.

So we will not copy. Please check this directory.

INFO 2009-06-02 09:40:50 CDSERVER46CSR2_NT_MSS CheckCopyDirectoryForCD:0

The directory, where the CD should be copied to, is not empty. We

will not copy to a notempty directory. This is not an error if

the directory contains already the CD.

WARNING 2009-06-02 09:40:50 CDSERVER46CSR2_NT_MSS CheckCopyDirectoryForCD:0

The CD EXPORT4 seems already be copied to G:\medien\Export\CD4.

So we will not copy. Please check this directory.

INFO 2009-06-02 09:41:01 DATABASEINSTANCE_NT_MSS CheckValueForKey:0

The installation phase is starting now. Please look in the log

file for further information about current actions.

INFO 2009-06-02 09:41:01

Requesting Installation Details

INFO 2009-06-02 09:41:01

Requesting Database Installation Details

INFO 2009-06-02 09:41:01 DBCOMMONDBENV_NT_MSS SyCoprocessCreate:931

Creating coprocess osql.exe ...

INFO 2009-06-02 09:41:01 DBCOMMONDBENV_NT_MSS SyCoprocessExecute:171

The process osql.exe puts out:

WARNING 2009-06-02 09:41:10 DBCOMMONDBENV_NT_MSS CmdNGo:0

select @@version

[Shared Memory]SQL Server does not exist or access denied.

[Shared Memory]ConnectionOpen (Connect()).

INFO 2009-06-02 09:41:10 DBCOMMONDBENV_NT_MSS SyCoprocessCreate:931

Creating coprocess osql.exe ...

INFO 2009-06-02 09:41:10 DBCOMMONDBENV_NT_MSS SyCoprocessExecute:171

The process osql.exe puts out:

WARNING 2009-06-02 09:41:21 DBCOMMONDBENV_NT_MSS CmdNGo:0

sp_server_info

[Shared Memory]SQL Server does not exist or access denied.

[Shared Memory]ConnectionOpen (Connect()

INFO 2009-06-02 09:41:21 DBCOMMONDBENV_NT_MSS SyCoprocessCreate:931

Creating coprocess osql.exe ...

INFO 2009-06-02 09:41:21 DBCOMMONDBENV_NT_MSS SyCoprocessExecute:171

The process osql.exe puts out:

WARNING 2009-06-02 09:41:29 DBCOMMONDBENV_NT_MSS CmdNGo:0

sp_server_info

[Shared Memory]SQL Server does not exist or access denied.

[Shared Memory]ConnectionOpen (Connect()).

ERROR 2009-06-02 09:41:29 DBCOMMONDBENV_NT_MSS InstallationDo:0

Phase failed.

ERROR 2009-06-02 09:41:29 InstController Action:0

Step DBCOMMONDBENV_NT_MSS could not be performed.

ERROR 2009-06-02 09:41:29 Main

Installation failed.

ERROR 2009-06-02 09:41:29 Main

Installation aborted.

edit: sorry- my blank lines aren't show in my post

Edited by: Karl Tim on Jun 2, 2009 9:51 AM

[Former Member]

If it's WIN 2000 check note 162266:

Step DBCOMMONDBENV_NT_MSS

Message:

"Could not find SQL-Server Instance "MSSQLSERVER" on your DB host "<host>". You must install SAP into the default instance or into a named instance that has the same name as your SAP system (SID)." (or similar).

Cause and solution:

This message has two typical causes:

* You are using Windows 2000 and the "Remote Registry Service" does not run. R3SETUP itself always uses the remote access locally on the registry. Ensure that this service is running.

Sven

[Former Member]

Hello Sven,

I thought that too cause thats what one SAP Note talking about but the service is running.

I solved my problem this morning. I'm using a database cluster and the database instance tried to install on a clusternode and not on the virtual host name of the cluster. So I changed that line in the database instance install template