Configtool Error occurred while scanning DB Msg: Error while connecting to DB

[Former Member]

Hi Experts,

Our SQL team implemented some security base line on one of our SAP JAVA system, later  SAP Java is not coming up.

As part of troubleshooting, we tried to connect to configtool we are getting error(screen shot attached)

.

As part of security base line, the SQL server port is changed and the same is updated in secure store(Url = jdbc:sqlserver://<Hostname>:<port>;databasename=<SID>) from SAP end, still we get the same error.

We have implemented similar change on many systems, but we didn't get any issue on other system.

The below error is seen in jvm_bootstrap.out log. please suggest.

Starting to initialize database connection

Exception occurred for component [internal/unkown] of type [unkown]

1. com.sap.engine.bootstrap.SynchronizationException: Storage access initialization failed due to OpenSQL error.Check if your db driver file is available on the file system or if the user has correct permissions for that file

at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:146)

Regards,

Leela.

[Former Member]

The same issues is mentioned in the below scn with oracle DB, but our system is on SQL Server.

In below scn, starting oracle lisener fixed the issue, where as SQL server don't have listener... not sure exactly what needs to be checked, FYI i checked the sql server port and it is listening...

Jstart ending with error details as "Node 'bootstrap' failed with exit code 558."

Anyone having clue on this, please update...

Regards,

Leela.

[luisdarui]

Hi Leela,

Can you please attach here your jvm_bootstrap.out log file?

I've worked on some cases but most of them were caused by the SAP<SID>DB user having sysadmin role assigned, after removing it, it worked.

Regards,

Luis

[Former Member]

Luis,

FYI my system is clustered, below is my jvm_bootstrap.out file

Starting to initialize database connection

Exception occurred for component [internal/unkown] of type [unkown]

com.sap.engine.bootstrap.SynchronizationException: Storage access initialization failed due to OpenSQL error.Check if your db driver file is available on the file system or if the user has correct permissions for that file

                at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:146)

                at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:79)

                at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:273)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                at java.lang.reflect.Method.invoke(Method.java:597)

                at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:162)

----------==[ Caused by: ]==----------

com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.

                at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:496)

                at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.<init>(DBConnectionPoolImpl.java:197)

                at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandlerImpl.<init>(PersistenceHandlerImpl.java:50)

                at com.sap.engine.core.configuration.impl.cache.ConfigurationController.<init>(ConfigurationController.java:139)

                at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:309)

                at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:59)

                at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:138)

                at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:79)

                at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:273)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                at java.lang.reflect.Method.invoke(Method.java:597)

                at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:162)

Caused by: com.sap.sql.log.OpenSQLException: Exception of type com.microsoft.sqlserver.jdbc.SQLServerException caught: Connection reset.

                at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)

                at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143)

                at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.java:286)

                at com.sap.sql.connect.datasource.DBDataSourceImpl.getPooledConnection(DBDataSourceImpl.java:181)

                at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:213)

                at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:482)

                ... 13 more

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset

                at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1352)

                at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1339)

                at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1654)

                at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:3694)

                at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:5026)

                at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:4978)

                at com.microsoft.sqlserver.jdbc.SQLServerConnection$1ConnectionCommand.doExecute(SQLServerConnection.java:1441)

                at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4575)

                at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1400)

                at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectionCommand(SQLServerConnection.java:1446)

                at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:1907)

                at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:41)

                at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:1893)

                at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4575)

                at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1400)

                at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1045)

                at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:817)

                at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:700)

                at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:842)

                at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendorConnection(DriverPooledConnectionFactory.java:50)

                at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:37)

                at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:690)

                at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceImpl.java:1034)

                at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceImpl.java:45)

                at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool.java:95)

                at com.sap.sql.connect.pool.Pool.get(Pool.java:734)

                at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.java:263)

                ... 16 more

[Bootstrap]> Error during synchronization. More details: the previous log entries

Regards,

Leela.

[luisdarui]

Hi Leela,

1. Does this error happens in both nodes?
2. Are you using AlwaysOn with SQL Server?
3. What is the URL you're using for connection?
4. Are you using the proper JDBC driver according to your SAP NetWeaver release? Check the following notes: 1398807, 2142959 and 639702.

Regards,

Luis

[Former Member]

Hi Luis,

1)Yes, this happens on both the nodes.

2)Always on --- No much idea on this feature.

3) URL - jdbc:sqlserver://<Hostname>:<Port>;databasename=<SID> is being used.

4)We are using correct jdbc driver and permissions on this file were good, we also tried replacing the driver from other system(which is working fine), still no luck

Still we have the same issue.

Regards,

Leela.

[Sriram2009]

Hi Leela

1. Could you share the screen shot of failover cluster mmc with MS Sql & SAP groups?

2. Are you able to ping the Ms Sql or SAP group either ip or virtual host name?

3. Refer the SCN thread with same issue but the DB differenet

https://scn.sap.com/thread/3546999

Regards

SS

[luisdarui]

Hi Leela,

Have you considered restoring file system on this server? If there were any change on the configuration it might resolve your problem. However, If you're looking forward for a root cause analysis, I would suggest to open a support incident with SAP. I'm still not sure what would be the best component either BC-DB-MSS (SQL Server), BC-JAS-COR (Core J2EEE Framework) or BC-OP-NT (Windows, Cluster). Each one would have tools to at least identify where is the problem and forward to the proper component. I would also suggest to open with WTS connection for both nodes.

Best Regards,

Luis Darui

[Former Member]

Hi Luis,

We raised a OSS with SAP. If we get any fix I will keep posted.

Regards,

Leela.

[waelkensd]

Hi Leelakrishna,

we're encountering a similar problem.

Did SAP get back to you on this?

We also logged an incident and are currently waiting for feedback.

Regards,

Dieter

[Former Member]

Hi Dieter,

As we expected our's is a an issue with the some DB parameters... we asked our DB team to revert all the parameters which were changed and then the issue is fixed...But we are still not aware of what is the exact parameter that caused this issue in our case.

Regards,

Leela.

[waelkensd]

Hi,

thanks for the feedback.

I chose to re-import the export and the connection was ok again. SAP Support was informed on the issue, but didn't come with any useful feedback.

Regards,

Dieter

[luisdarui]

HI Leela,

This error doesn't look like caused by port changes.

1. Have you restarted SQL Server after changing the tcp port in SQL Server configuration manager?
2. Can you access remotely SQL server by using client tools such SQLCMD or SQLPS?
3. If you revert the tcp port changes, does it work?

Best regards,

Luis

[Former Member]

Hi Luis,

1)Yes SQL server is restarted after the change

2)We are able to connect to the DB using SQL Server Management Studio and no major errors in db       error log

3)All the changed were reverted, restart done... still the same issue now...

I see the below error on configtool log...

Error: com.sap.ASJ.cft.000205 Error occurred while scanning DB.

Error details: Error while connecting to DB.

below error on jvm_bootstrap.out log log...

Starting to initialize database connection

Exception occurred for component [internal/unkown] of type [unkown]

1. com.sap.engine.bootstrap.SynchronizationException: Storage access initialization failed due to OpenSQL error.Check if your db driver file is available on the file system or if the user has correct permissions for that file

at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:146)

FYI I checked the DB driver file as per above error msg and it is in correct location.

Regards,

Leela.

[Sriram2009]

Hi Leela

I think SAP DB user id permission changed, Could you refer the SAP KBA & Note

1950926 - System cannot start due to login SQLServerException

592514 - MSSQL: internal database users, permissions and security

Regards

SS

[Former Member]

Sriram,

I checked/compared the SAPSIDDB with other system, it looks good.

Regards,

Leela.

[Sriram2009]

Hi Leela

Thanks for your info,

1. On SAP system  logon using SAP SIDADM user id ? and SIDADM part of local administrator group? Is this any firewall or UAC enabled at OS level?

2. Check the instance .properties file after change the port number.

2012156 - Setting the properties of a new instance.properties file

Refer the basic checks as mention in the SAP KBA

1656923 - Netweaver AS Java is not starting due to bootstrap related errors

Regards

SS

[Former Member]

Sriram,

Thanks for your response!

1)Yes my sidadm is part of admin group, firewall and UAC looks good and also compared with other system.

2)SAP Note 202156, 1656923 doesn't apply in our case, as jvm_bootstrap.out doesn't have those error mentioned in the notes. we have different error...

Starting to initialize database connection

Exception occurred for component [internal/unkown] of type [unkown]

1. com.sap.engine.bootstrap.SynchronizationException: Storage access initialization failed due to OpenSQL error.Check if your db driver file is available on the file system or if the user has correct permissions for that file

at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:146)

First I want to make sure configtool was able to connect to DB, once this is fixed... I guess starting SAP will not be a problem...

Regards,

Leela.