Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

SQL server doesn't exist or access denied || SAP NW 7.4 installation || Distributed environment

Hello Experts,

We're installing SAP NW 7.4 Gateway in a distributed environment (Windows server 2012) where APP server resides on SAPDEVNGAPP1 and DB server resides on SAPDEVNGDBS1. We are using the APP server for both ASCS and PAS instances.

I'm able to install the SQL db 2012 on DB host and also ASCS instance is installed successfully on APP server. I'm unable to install the PAS instance because it is not able to connect to the SQL database. Below is the error that I am facing:

Small background on the environment:

-> App server {APP zone} is in different zone than DB server {DB zone}.

-> Both servers are not assigned to same domain (they are put up on WORKGROUP). Can this be the cause that both are not under same domain?

-> Ping <dest IP/hostname> from APP to DB and vice-versa are successful.

-> Telnet <dest IP> <port> are not successful in both servers.

-> I'm performing the installation using Administrator user ID.

-> SQL Database has been installed using setup.exe. We didn't use SWPM (I guess this will not cause a problem).

Here is the warning/error captured in the sapinst.log file:

WARNING 2015-07-30 18:38:11.658 (SAPDEVNGAPP1\Administrator) id=dbmodmssql.odbcdll.connection

Cannot connect to the database server. Errors returned: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).

Call your SAP Support.

Here is the warning/error captured in the sapinst_dev.log file:


TRACE      2015-07-30 18:37:29.517 (SAPDEVNGAPP1\Administrator) [csistepexecute.cpp:1109]

Execution of preprocess block of |NW_ABAP_CI|ind|ind|ind|ind|0|0|NW_GetSidFromProfilesPartial|ind|ind|ind|ind|getSid|0|NW_getDBInfo|ind|ind|ind|ind|db|0|NW_MSS_DBINFO|ind|ind|ind|ind|mss|0|MssLoginInfo|ind|ind|ind|ind|login|0|dCheckGivenServer returns TRUE

TRACE      2015-07-30 18:37:29.564 (SAPDEVNGAPP1\Administrator)

t_MssLogin.remove(WHERE Key='std')

WARNING    2015-07-30 18:38:11.658 (SAPDEVNGAPP1\Administrator) [iaxmbcom.cpp:120] id=dbmodmssql.odbcdll.connection CMssLogger::logMessage

Cannot connect to the database server. Errors returned: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).

Call your SAP Support.

TRACE      2015-07-30 18:38:11.658 (SAPDEVNGAPP1\Administrator) [tablecpp.cpp:286] TableCpp::insertRow()

Table(t_MssLogin).insertRow({

  Host:SAPDEVNGDBS1

  Key:std

  LoginType:WIN

  MachineName:SAPDEVNGDBS1

}, WHERE 1=1)

inserting

TRACE      2015-07-30 18:38:11.658 (SAPDEVNGAPP1\Administrator)

MSSTRC: odbc driver is installed.

TRACE      2015-07-30 18:38:11.658 (SAPDEVNGAPP1\Administrator)

t_MssMessages.remove(WHERE 1=1)

WARNING    2015-07-30 18:38:32.705 (SAPDEVNGAPP1\Administrator) [iaxmbcom.cpp:120] id=dbmodmssql.odbcdll.connection CMssLogger::logMessage

Cannot connect to the database server. Errors returned: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).

Call your SAP Support.

TRACE      2015-07-30 18:38:32.705 (SAPDEVNGAPP1\Administrator)

Cannot connect to SAPDEVNGDBS1

SQL Server does not exist or access denied.

Tags:
Former Member
replied

Hi Hardeep,

Have you installed SQL Server Native Client on your application server? You'll need it in order for SAP and SQL Server to communicate with each other. On our distributed systems we also install the SQL Command Line Tools on the application servers. Make sure the versions for these match the service pack/patch state of your SQL Server install.

What do you mean by "SQL Database has been installed using setup.exe"? Do you mean the Microsoft installer for the SQL Server engine? Or sapinst.exe (for whatever installer version you used)? You should install SQL Server on the database server and the client tools on the application server first, then do the SAP install and let the SAP installer create the database so it can set the permissions it wants.

What steps did you use for the install? We don't have an ASCS instance on our distributed systems because they pre-date it and use either global host preparation or SCS instance install instead, but the order should be:

1. Install ASCS instance (on the app server) - or global host preparation if not using ASCS

2. Install SCS instance (on the app server) - if required

3. Install database instance (on the database server)

4. Install central instance (on the app server)

When prompted for the profiles for the system you'll need to use UNC paths (\\appserverhostname\sapmnt\SID\SYS\profile for the later stages. The ASCS/global host preparation install should have set up the shares for you, so if the installer can see the profiles then the two servers are basically talking to each other. Obviously port blockages from firewalls can still cause problems, but you'd expect to get an error message complaining about not being able to talk to port x if so.

Julie

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question