Installation of SAP NetWeaver 7.X into MS Windows Server 2016 / MS SQL Server 2017. Highlighting of some important steps.
Prerequisites.
You want to install SAP System based on NetWeaver 7.X into MS Windows Environment and want to know about some essential steps and known issues.
Environment.
MS Windows 2016 Server
MS SQL Server 2017
MS SQL Management Studio 2017
Resolution for MS SQL Server 2017.
Prepare our MS SQL Server 2017 for SAP installation.
The step-by-step installation process below.
Step #1.
Mount disk image with media via PowerShell command (PowerShell Run As Administrator):
Mount-DiskImage -ImagePath "E:\Distr\SW_DVD9_NTRL_SQL_Svr_Standard_Edtn_2017_64Bit_English_OEM_VL_X21-56945.ISO"
Step #2.
New SQL Server stand-alone installation
Step #3.
Use Microsoft Update to check for updates
Step #4.
Database Engine Services only. This is enough for SAP installation.
Step #5.
Database Engine Services only. This is enough for SAP installation.
Step #6.
Named Instance
Step #7.
Specify the service accounts and collation configuration.
At this point - Account name this is Active directory User with rights for:
Log-on as a service
Log-on as a batch job
The lock pages in memory
Perform volume maintenance tasks
Provide Startup Type - Auto and Grant Perform Volume Maintenance Task privilege to SQL Server Database Engine Service.
Step #8.
Mixed Mode - on. Create 'sa' account and specify the SQL Server administrator's AD-group.
Step #9.
Installation completed successfully
Post-installation steps in SQL Management Studio 2017
EnableAutoGrowAllFiles - DBCC TRACEON (1117, -1)
EnableAutoUpdateStatistics - DBCC TRACEON (2371, -1)
EnableFullExtentsOnly - DBCC TRACEON (1118, -1)
Checking procedure:
-- If Number of cores not equivalent Number of files
-- Check. MS SQL Studio -> connect to DB -> tempdb -> Files and fix it
SELECT os.Cores, df.Files
FROM
(SELECT COUNT(*) AS Cores FROM sys.dm_os_schedulers WHERE status = 'VISIBLE ONLINE') AS os,
(SELECT COUNT(*) AS Files FROM tempdb.sys.database_files WHERE type_desc = 'ROWS') AS df;
Post-installation steps in Windows Firewall
Allow the connection for such TCP/UDP ports in the Windows Firewall:
TCP 1433
TCP 1434
TCP 4022
TCP 7022
TCP 135
TCP 2382
UDP 1434
System Restart is required
Notes/Links:
1774329 - Preparing your SAP instance to connect to remote SQL server
Native client for MS SQL Server installation
https://docs.microsoft.com/en-us/sql/connect/oledb/oledb-driver-for-sql-server?view=sql-server-ver15
1881155 - Native client for MS SQL Server is not installed.
2484674 - Setting up Microsoft SQL Server 2017
Resolution for MS Windows 2016.
Prepare Windows 2016 Server for SAP installation
For firts look at important prerequisites:
1710950 - Inst. SAP Systems Based on NW 7.1 and higher: Windows
1.System Locale. Must be set to English 'en-US'
2. Swap size
3. Notes 2445952,1823833,2515202 must be implemented
Some facts about
Note #1823833 - Accessing shares via SMB3.0 can result in long waiting times
Changes in regedit:
Some facts about
2445952 - Correct user account authorization to run SWPM / 70SWPM on Microsoft Window
Some facts about
2515202 - A required privilege is not held by the client.
Troubleshooting during SAP installation.
Error - saplikey: failed to load shared library when connecting to the database in SWPM
Resolution - Something wrong with the Kernel files - <drive>:\usr\sap\<SID>\SYS\exe\uc\NTAMD64
Error - Required MS SQL Server collation for the SAP system installation is: SQL_Latin1_General_CP850_BIN2 .
Your server uses collation: Cyrillic_General_CI_AS .
Resolution - Read the installation guide on how to set the correct server collation for the SAP system
Stop SQL Server
Run command:
cd C:\Program Files\Microsoft SQL Server\MSSQL14.XXXX\MSSQL\Binn (Path to a sqlservr utility)
sqlservr -m -T4022 -T3659 -s"YOUR_NAMED_INSTANCE" -q"SQL_Latin1_General_CP850_BIN2"
More information about a sqlservr and its parameters here.
Links:
Error -
Installation fails with error
Execution of the command "\\<HOST>\sapmnt\<>\SYS\exe\uc\NTAMD64\dipgntab.exe -rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT" finished with return code -1. Output:
ERROR in initialization (can't get SVERS-version)
Resolution -
Note
2106205 - dipgntab failed with: "ERROR in initialization (can't get R/3-version)" or "ERROR in initialization (can't get SVERS-version)"
Check Kernel & DBSL patch levels from OS-level
<drive>:\usr\sap\<SID>\SYS\exe\uc\NTAMD64\disp+work.exe -version
Conclusion.
SAP BASIS Routine task with examples from real life was provided/
- SAP Managed Tags:
1 Comment
