NW 7.1 Installation on SQL 2008 R2

[former_member183829]

Hello

I am facing problem in SAP NW 7.1 installation on Windows 2008 R2 and SQL 2008 R2.

Above combination is supported as per PAM.

Error

1) See Prerequisites Checker Result as below.

I have ingnored this warning and go ahead with installation.

2) Now I am stuck at phase, create/Modify database schema

Log does not provide any clear error.

Please note that I have already followed below notes:

1) I have patched SAPINST as per note: Note 929929 - Latest SAPinst Patch

2) I have modified kerner as per Note 1480785 - Creating a Modified Windows Kernel DVD

3) Updated Microsft DLLS Note 684106 - Microsoft runtime DLLs

Also note that I have already installed SQL 2008 R2 on this server. I have other 3 SIDs running on this server with SQL 2008 R2 as database.

Let me know your view.

[RonaldWerner · Accepted solution]

Hi,

we have the same problem and we found the following Note: 1076022

...

4. SAP releases based on Netweaver 7.1

...

d) Installing a 7.1 system on SQL Server 2008 (R2)

You cannot use the Netweaver 7.1 installation package to install a new  SAP system on SQL Server 2008 (R2). As a workaround, you need to install  on SQL Server 2005, apply the required SAP_BASIS and SAP_BW support packages, apply a supported SAP kernel and then upgrade the database release to SQL Server 2008 (R2).

that is really a miserable solution

[jairo_pedroza · Accepted solution]

Hello Ronald,

So far, the workaround is it! I don't think so it will be changed soon. I tried to use modified DVD in Lab, but it not worked properly. Too much errors.

1152240 - Setting Up Microsoft SQL Server 2008 (R2)

Suggestion: Install with MS SQL 2005, apply recommendations required, export/import in MS SQL Server 2008 R2 or 2012.

Regards,

Jairo Pedroza

[former_member183829 · Accepted solution]

Hello All,

I tried many ways to make this installation work. NW 7.1 on SQL 2008 R2.

By certain workarounds and manual steps, i could complete installation. However, i got various warning/wrong data in db02, st04 and spam etc.

I had to uninstall this and reinstall again on SQL 2005.

(I had also raised SAP message. Even after all pursuit, SAP suggested the same path).

Thanks.

[RonaldWerner · Accepted solution]

We have done the same.

There is no other option as installing NW Mobile with MS SQL 2005.

[Former Member]

Hi,

Ignoring the warning should not have an adverse affect, but would recommend to solve the version issue incase the installation is for productive usage.

With regards to error you get in create/modify database schema - please post what error SAPInst gives or check in the path C:\programs files\sapinst_instdir\..\..\.. you would see the sapinst.log and sapinst_dev.log. Check those for errors.

Regards,

Srikishan

[former_member183829]

Hi,

Below is few lines from sapinst.log

========================================================================

INFO 2012-05-11 17:14:53.576

Execute step CreateStdSchema of component |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|1|0|NW_MSS_DB|ind|ind|ind|ind|3|0|MssSchemaCreate|ind|ind|ind|ind|9|0

ERROR 2012-05-11 17:14:53.703

FCO-00011  The step CreateStdSchema with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|1|0|NW_MSS_DB|ind|ind|ind|ind|3|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateStdSchema was executed with status ERROR .

INFO 2012-05-11 17:14:53.883

Creating file C:\Program Files\sapinst_instdir\NW71\INSTALL\SYSTEM\MSS\STD\AS-ABAP\__instana_tmp.xml.

ERROR 2012-05-11 17:14:53.697

MDB-05053  Errors when executing sql command: [Microsoft][ODBC SQL Server Driver][SQL Server]Password validation failed. The password does not meet Windows policy requirements because it is not complex enough.

[Microsoft][ODBC Driver Manager] Function sequence error

<p> SOLUTION: If this message is displayed as a warning, you can ignore it. If this is an error, contact SAP support.</p>

========================================================================

[jairo_pedroza]

Hello Consult sap,

I had the same problem. This problem is related with user privileges in MS SQL

For solution, you have following steps:

1.Add user as Local Admin. If you are installing with domain user, Add user from domain in local admin group.

2.Open SSMS using local admin. Hold Shift key + Right click on SSMS + Open using diferent user. Logon with local administrator.

3.You should give Permission for user <SID>adm ( local user or domain user ). depend what you're using. Select all grants.

4.Retry SAPINST

Details in SAP note

592514 - MSSQL: internal database users, permissions and security

If above procedure doens't work. Please generate more log detail using steps.

1.Set environment variable MSSQL_DBSLPROFILE set to 1

2.Logoff / logon, Restart SAPINST and go ahead until generate error. It will produce files named dbsl_p<n>, where <n> is the operating system process ID.

3.Please, post last 20 lines.

98678 - SQL Server Connection Issues

1248222 - ODBC DBSL profile parameters and connect options

I hope it help you.

Jairo Pedroza

[former_member183829]

Hello,

I have been able to solve earlier error.

Now I am facing error at phase 18 - Perform MS-SQL Server Post-Load Activities. Here, 96 our of 100 procedures are completed successfully.

However, it gives error while executing 96th procedure.

Below are last few lines of MSSlog.log

===========================================================

use NML

setuser 'nml'

-- (C) SAP Labs, 2001, 2003

-- =============================================

-- Check whether the MSSQL DB collector job

-- is scheduled and enabled. If not, create all

-- required objects and start the job.

-- =============================================

-- Remove the temporary DBCOLL schema creation

-- stored procedure

IF NOT OBJECT_ID('tempdb..#sap_coll_user') IS NULL

DROP PROCEDURE #sap_coll_user

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

-- Create table sap_perfhist

if  ((select object_id(user + '.' + 'sap_perfhist'))

IS NULL )

CREATE TABLE sap_perfhist

( entry_id   int           IDENTITY ,

udate      datetime      NOT NULL ,

frequency  int           NOT NULL ,  -- minutes

retention  int           NOT NULL ,  -- days

enabled    tinyint       NOT NULL ,

activity   nvarchar(128)     NULL ,

PRIMARY KEY CLUSTERED (entry_id)  )

-- Initialise collector job status -----------------------------------

declare @enabled    smallint

declare @job_flag   smallint

declare @job_exists smallint

select @enabled    = enabled ,

@job_flag   = job_flag ,

@job_exists = job_exists

from sap_p_status(default)

-- Create the needed tables

--   sap_perfcntr always gets re-created

EXECUTE sap_create_cntr 0

-- Re-create the job, if necessary

IF ( @job_exists <= 0 )

EXECUTE sap_perfadd ' '

-- Enable the job

IF ( @job_exists > 0 and @job_flag <> @enabled )

EXECUTE sap_p_parameter @agtflag = @enabled

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

[Microsoft][ODBC SQL Server Driver]Associated statement is not prepared

===============================================================

Let me know your view.

[jairo_pedroza]

Hello sap,

I sent some procedures. Does it help you? From my technical point of view, it is another error?

Please, if information that I sent help you, please answer in this post. If not, write how you solved in order to share with our colleagues.

For your NEW error, make sure that you are using the newest dbmssslib.dll available for that release. Update your Kernel including new dbmssslib.dll. It solve problem like that.

Regards,

Jairo Pedroza

[former_member183829]

Hi Jairo,

I did not had to follow steps you had mentioned.

As a workaround I manually created the logon by executing the following command on SQL Studio Managment:

exec sp_addlogin N'nml', 'passwd', N'NML'

This is how i got though earlier error.

For current error, i have already applied latest kernel. Still the error.

look at previously shared MSSLOG.log file.

Thanks.