Solution : https://service.sap.com/sap/support/notes/1282975 (SAP Service marketplace login required)
Summary :
This SAP Note outlines procedures for implementing SAP systems using virtual host names instead of physical network identities, specifically for environments based on SAP NetWeaver 7.0 and above and using Microsoft SQL Server. Key steps include starting the 'Remote Registry' service, assigning a static IP to the server, creating required registry entries, and maintaining these settings in DNS for connectivity. The note warns against using TCP alias names and installing with local users, as these practices are unsupported and can lead to installation failures and connection issues. Problems during installation include errors stemming from incorrect registry settings and misconfigured host files.
Key words :
add account <primary_hostname>\sap_aa5_globaladminto group <primary_hostname>\sap_localadmin, \\vsystest3\sapmnt\aa5\sys\profile\start_d07_vsystest3-, \usr\sap\aa5\d07\exe\sapstartsrv, sharing center --> manage network connections --> properties, programs --> control panel --> network connections--> properties, netsh interface ip add address, programs --> control panel --> network, microsoft failover cluster installations, local group local groupbecause, exe sapinst_use_hostname=<virtual host
Related Notes :
| 1624061 | Use of virtual TCP/IP host names |
| 962955 | Use of virtual TCP/IP host names |
| 360515 | TCP/IP Alias host names in UNC path in Windows 2000 / 2003 |
| 129997 | Hostname and IP address lookup |