on 07-24-2011 12:48 PM
Hi, SDN fellows.
I finished applying SPs for Solman Manager 7.0 (updated to Solman 7.1 EHP1 - just the Java Stack with JSPM). Then, I decided to start install SAP ECC 6.0 IDES in D drive (solman currently installed in C drive). When I ran the SAP ECC installer till the screen where it require Solution Key, I stopped the process due to invalid solution key provided.
After that, my Solman system became not able to connect to MS SQL server anymore. Here is the trans messages I got from "R3Trans -d".
Not sure what isthe root cause, but I found couple messages maybe the leads to root cause.
I wonder why the DBNAME become empty on this line: 2EETW169 no connect possible: "DBMS = MSSQL --- SERVER = 'MYSERVER101' DBNAME = ''".
These message also shown that this maybe login related issue:
4 ETW000 [ dev trc,00000] CopyLocalParameters: dbuser is 'dbo' 19 0.004714
...
4 ETW000 [ dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000
............
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000
.................
LOG BY0=>Login timeout expired [dblink#4 @ 433]
.....
Thanks for advices,
KC
I had this challenge too during installation of ECC6, In my case, changing the environment variables and restarting the system could not solve the problem, even though the echo %DBMS% was returning mss. Each time the installation is restarted with Run new option, sapinst will still take the old value it has taken before. The first time sapinst attempted installation, environment variables for MSSQL was not set in user environment variable and so, sapinst generate some values not in a standard format. this variables are put in a file in usr directory. the best thing to do is to remove the content of usr\sap\<SID>. with the new environment set, the sapinst will generate fresh server information for the installation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I resolved the issue. It is due to the local environment variables are not configured right. After installing SAP ECC on the same server, the local environment variables for database name and schema and etc. for the SAP solution manager service admin account need to reconfigure. I think initially it was taken from the TP profile when no values are found in local environment variables initially. When both systems are using the same EPS path, both service admin account should configure their local environment variables to work properly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi KC,
"Database is not available via R3trans" indicates that your user SAPA4H is locked or the credentials have expired.
You can test it from Hdbstudio.
Start the installed SAP HANA Studio
Try to add a new system with user id as SAPA4H and password as your master password.
It will fail with an error message
"You have reached the maximum no. of invalid password entry attempts. User is locked until.....XXXXXXX.
Try again later or contact your system administrator"
Thus if you know how to reset the password (do share it, as even I am looking for the same (http://help.sap.com/hana/html/sql_alter_user.html)), do it and try starting SAP again by shutting down the SAP followed by HANA and then starting HANA followed by SAP.
Regards,
Anuj Kumar
Detail Log:
==============================
4 ETW000 R3trans.exe version 6.14 (release 701 - 19.01.11 - 11:44:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 24.07.2011 - 07:23:10
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans.exe -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [ dev trc,00000] Sun Jul 24 07:23:12 2011 0 0.000000
4 ETW000 [ dev trc,00000] db_con_init called 0 0.000000
4 ETW000 [ dev trc,00000] create_con (con_name=R/3) 0 0.000000
4 ETW000 [ dev trc,00000] Loading DB library 'C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\dbmssslib.dll' ...
4 ETW000 0 0.000000
4 ETW000 [ dev trc,00000] DlLoadLib success: LoadLibrary("C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\dbmssslib.dll"), hdl 0, addr 0000000186CD0000
4 ETW000 1506 0.001506
4 ETW000 [ dev trc,00000] using "C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\dbmssslib.dll" 17 0.001523
4 ETW000 [ dev trc,00000] Library 'C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\dbmssslib.dll' loaded 21 0.001544
4 ETW000 [ dev trc,00000] function DbSlExpFuns loaded from library C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\dbmssslib.dll
4 ETW000 31 0.001575
4 ETW000 [ dev trc,00000] Version of 'C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\dbmssslib.dll' is "700.08", patchlevel (0.134)
4 ETW000 176 0.001751
4 ETW000 [ dev trc,00000] function dsql_db_init loaded from library C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\dbmssslib.dll
4 ETW000 27 0.001778
4 ETW000 [ dev trc,00000] function dbdd_exp_funs loaded from library C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\dbmssslib.dll
4 ETW000 28 0.001806
4 ETW000 [ dev trc,00000] New connection 0 created 33 0.001839
4 ETW000 [ dev trc,00000] 000: name = R/3, con_id = -000000001, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,
4 ETW000 reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 54 0.001893
4 ETW000 [ dev trc,00000] db_con_connect (con_name=R/3) 28 0.001921
4 ETW000 [ dev trc,00000] find_con_by_name found the following connection for reuse: 19 0.001940
4 ETW000 [ dev trc,00000] 000: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,
4 ETW000 reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 46 0.001986
4 ETW000 [ dev trc,00000] Thread ID:6104 2463 0.004449
4 ETW000 [ dev trc,00000] Thank You for using the SLOLEDB-interface 25 0.004474
4 ETW000 [ dev trc,00000] Using dynamic link library 'C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\dbmssslib.dll'
4 ETW000 33 0.004507
4 ETW000 [ dev trc,00000] dbmssslib.dll patch info 39 0.004546
4 ETW000 [ dev trc,00000] patchlevel 0 68 0.004614
4 ETW000 [ dev trc,00000] patchno 134 22 0.004636
4 ETW000 [ dev trc,00000] patchcomment UPSERT retry corrected (1566676) 19 0.004655
4 ETW000 [ dev trc,00000] np:(local) connection used on MYSERVER101 40 0.004695
4 ETW000 [ dev trc,00000] CopyLocalParameters: dbuser is 'dbo' 19 0.004714
4 ETW000 [ dev trc,00000] Using Provider SQLNCLI 6750 0.011464
4 ETW000 [ dev trc,00000] OpenOledbConnection: MARS property was set successfully. 120 0.011584
4 ETW000 [ dev trc,00000] Sun Jul 24 07:23:28 2011 15136554 15.148138
4 ETW000 [ dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000 41 15.148179
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
4 ETW000 49 15.148228
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 15.148245
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000 75 15.148320
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 18 15.148338
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
4 ETW000 42 15.148380
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 15.148397
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
4 ETW000 39 15.148436
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 16 15.148452
4 ETW000 [ dev trc,00000] Using Provider SQLNCLI 5440 15.153892
4 ETW000 [ dev trc,00000] OpenOledbConnection: MARS property was set successfully. 68 15.153960
4 ETW000 [ dev trc,00000] Sun Jul 24 07:23:43 2011 15118145 30.272105
4 ETW000 [ dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000 42 30.272147
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
4 ETW000 45 30.272192
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 30.272209
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000 63 30.272272
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 20 30.272292
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
4 ETW000 42 30.272334
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 30.272351
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
4 ETW000 38 30.272389
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 30.272406
4 ETW000 [ dev trc,00000] Using Provider SQLNCLI 10214 30.282620
4 ETW000 [ dev trc,00000] OpenOledbConnection: MARS property was set successfully. 75 30.282695
4 ETW000 [ dev trc,00000] Sun Jul 24 07:23:58 2011 15172939 45.455634
4 ETW000 [ dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000 41 45.455675
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
4 ETW000 43 45.455718
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 45.455735
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000 75 45.455810
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 27 45.455837
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
4 ETW000 43 45.455880
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 16 45.455896
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
4 ETW000 38 45.455934
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 45.455951
4 ETW000 [ dev trc,00000] failed to establish conn to np:(local). 6519 45.462470
4 ETW000 [ dev trc,00000] Retrying without protocol specifier: (local) 30 45.462500
4 ETW000 [ dev trc,00000] Using Provider SQLNCLI 60 45.462560
4 ETW000 [ dev trc,00000] OpenOledbConnection: MARS property was set successfully. 57 45.462617
4 ETW000 [ dev trc,00000] Sun Jul 24 07:24:14 2011 15636603 61.099220
4 ETW000 [ dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000 51 61.099271
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
4 ETW000 45 61.099316
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 61.099333
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000 60 61.099393
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 61.099410
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
4 ETW000 41 61.099451
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 61.099468
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
4 ETW000 37 61.099505
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 61.099522
4 ETW000 [ dev trc,00000] Using Provider SQLNCLI 5453 61.104975
4 ETW000 [ dev trc,00000] OpenOledbConnection: MARS property was set successfully. 59 61.105034
4 ETW000 [ dev trc,00000] Sun Jul 24 07:24:29 2011 15620154 76.725188
4 ETW000 [ dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000 43 76.725231
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
4 ETW000 45 76.725276
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 18 76.725294
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000 79 76.725373
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 76.725390
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
4 ETW000 42 76.725432
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 76.725449
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
4 ETW000 103 76.725552
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 25 76.725577
4 ETW000 [ dev trc,00000] Using Provider SQLNCLI 5413 76.730990
4 ETW000 [ dev trc,00000] OpenOledbConnection: MARS property was set successfully. 78 76.731068
4 ETW000 [ dev trc,00000] Sun Jul 24 07:24:45 2011 15600542 92.331610
4 ETW000 [ dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000 42 92.331652
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
4 ETW000 45 92.331697
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 92.331714
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000 60 92.331774
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 16 92.331790
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
4 ETW000 42 92.331832
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 16 92.331848
4 ETW000 [ dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
4 ETW000 38 92.331886
4 ETW000 [ dev trc,00000] Procname: [OpenOledbConnection - no proc] 17 92.331903
4 ETW000 [ dev trc,00000] failed to establish conn. 0 5491 92.337394
4 ETW000 [ dblink ,00433] ***LOG BY2=>sql error -1 performing CON [dblink#4 @ 433] 119 92.337513
4 ETW000 [ dblink ,00433] ***LOG BY0=>Login timeout expired [dblink#4 @ 433] 27 92.337540
2EETW169 no connect possible: "DBMS = MSSQL --- SERVER = 'MYSERVER101' DBNAME = ''"
This is dev_w0 log file. Seems like the connection is established successfully. But I am still facing "tp connecting to database" error when updating SAINT/SPAM.
========================
- Error in phase: CHECK_REQUIREMENTS
- Reason for error: TP_CANNOT_CONNECT_SYSTEM
- Return code: 0232
- Error message: connect failed
================
C Ping: DoPing returned 99 (233)
B Reconnect state is entered by connection:
B 000: name = R/3, con_id = 000000000, state = INACTIVE , tx = NO , hc = NO , perm = YES,
B reco = YES, frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
B RECONNECT: rsdb/reco_trials: 3
B RECONNECT: rsdb/reco_sleep_time: 5
B RECONNECT: rsdb/reco_sync_all_server: OFF
B db_con_reconnect: reconnecting to connection 0:
B 000: name = R/3, con_id = 000000000, state = INACTIVE , tx = NO , hc = NO , perm = YES,
B reco = YES, frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
B disconnecting from connection 0 ...
B disconnected from connection 0
B opening connection 0 ...
C Thread ID:3424
C Thank You for using the SLOLEDB-interface
C Using dynamic link library 'C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\dbmssslib.dll'
C dbmssslib.dll patch info
C patchlevel 0
C patchno 134
C patchcomment UPSERT retry corrected (1566676)
C Local connection used on MYSERVER101 to named instance: np:MYSERVER101\SQL05_DEV
C CopyLocalParameters: dbuser is 'sm1'
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C Provider Release:9.00.5000.00
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C Cache sizes: header 104 bytes, 20000 names (32960000 bytes), 500 dynamic statements (2876000 bytes), total 35836104 bytes
C Using shared procedure name cache MYSERVER101_SQL05_DEV_SM1SM1_SM1_MEM initialized by another process.
C Connected to db server : [MYSERVER101\SQL05_DEV] server_used : [np:MYSERVER101\SQL05_DEV], dbname: SM1, dbuser: sm1
C pn_id:MYSERVER101_SQL05_DEV_SM1SM1_SM1
C Using MARS (on sql 9.0)
B Connection 0 opened (DBSL handle 0)
B successfully reconnected to connection 0
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.