cancel
Showing results for 
Search instead for 
Did you mean: 

TP CANNOT CONNECT SYSTEM: TP RC 0232:

Former Member
0 Kudos

Hello All

I am trying to apply latest spam/saint package so I can go up NW SP12, however I am getting errors.

SYSTEM BACKGROUND

This is running on W23K Ent Edition, SQL Server 2005 Ent Edition, NW 7.0 kernel 102. SP 9

Do I need a table svers and do i need to create sapevepath on a NW 7 system?

Are thhe arnings ok

Any feedback will be appreciated.

Import phase 'CHECK_REQUIREMENTS' (20.02.2008, 07:04:07)

Error during executing the tp command 'tp CONNECT ERP ...'

tp return code: '0232' , tp message: 'connect failed' , tp output:

This is tp version 371.02.23 (release 700, unicode enabled)

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBNAME is no longer used.

ERROR: Connect to ERP failed (20080220070407), failed to read table SVERS.

TRACE-INFO: 1: [dev trc ,00000] Wed Feb 20 07:04:07 2008 16469 0.016469

TRACE-INFO: 2: [dev trc ,00000] load shared library (dbmssslib.dll), hdl 0 11 0.016480

TRACE-INFO: 3: [dev trc ,00000] using "D:\usr\sap\ERP\DVEBMGS10\exe\dbmssslib.dll" 9 0.016489

TRACE-INFO: 4: [dev trc ,00000] Thread ID:144 1462 0.017951

TRACE-INFO: 5: [dev trc ,00000] Thank You for using the SLOLEDB-interface 9 0.017960

TRACE-INFO: 6: [dev trc ,00000] Using dynamic link library 'D:\usr\sap\ERP\DVEBMGS10\exe\dbmssslib.dll'

TRACE-INFO: 7: 19 0.017979

TRACE-INFO: 8: [dev trc ,00000] dbmssslib.dll patch info 19 0.017998

TRACE-INFO: 9: [dev trc ,00000] patchlevel 0 7 0.018005

TRACE-INFO: 10: [dev trc ,00000] patchno 87 8 0.018013

TRACE-INFO: 11: [dev trc ,00000] patchcomment MSSQL: UTAB/ATAB/Dynp-access via clientside cursor (1002914)

TRACE-INFO: 12: 12 0.018025

TRACE-INFO: 13: [dev trc ,00000] np:(local) connection used on IWDFVM2160 54 0.018079

TRACE-INFO: 14: [dev trc ,00000] CopyLocalParameters: dbuser is 'dbo' 9 0.018088

TRACE-INFO: 15: [dev trc ,00000] Using Provider SQLNCLI 57076 0.075164

TRACE-INFO: 16: [dev trc ,00000] OpenOledbConnection: MARS property was set successfully. 80 0.075244

TRACE-INFO: 17: [dev trc ,00000] Provider Release:9.00.3042.00 108316 0.183560

TRACE-INFO: 18: [dev trc ,00000] Using Provider SQLNCLI 384 0.183944

TRACE-INFO: 19: [dev trc ,00000] OpenOledbConnection: MARS property was set successfully. 60 0.184004

TRACE-INFO: 20: [dev trc ,00000] CheckCodepageType: line 24329. hr: 0x80040e37 Invalid object name 'DBPROPERTIES'.

TRACE-INFO: 21: 3564 0.187568

TRACE-INFO: 22: [dev trc ,00000] sloledb.cpp [CheckCodepageType,line 24329]: Error/Message: (err 208, sev 16), Invalid object

name 'DBPROPERTIES'.

TRACE-INFO: 23: 27 0.187595

TRACE-INFO: 24: [dev trc ,00000] Procname: [CheckCodepageType no proc] 8 0.187603

TRACE-INFO: 25: [dev trc ,00000] Cache sizes: header 68 bytes, 100 names (157600 bytes), 100 dynamic statements (568800

bytes), total 726468 bytes

TRACE-INFO: 26: 39 0.187642

TRACE-INFO: 27: [dev trc ,00000] Initializing private procedure name cache. 9 0.187651

TRACE-INFO: 28: [dev trc ,00000] procedure cache created/attached 14 0.187665

TRACE-INFO: 29: [dev trc ,00000] Connected to db server : [IWDFVM2160] server_used : [np:(local)], dbname: ***, dbuser: dbo

TRACE-INFO: 30: 13 0.187678

TRACE-INFO: 31: [dev trc ,00000] pn_id:IWDFVM2160_*** 7 0.187685

TRACE-INFO: 32: [dev trc ,00000] Using MARS (on sql 9.0) 8 0.187693

TRACE-INFO: 33: [dev trc ,00000] The IRow interface is supported by this OLEDB provider 513 0.188206

TRACE-INFO: 34: [dev trc ,00000] ParamStmtExec: line 12988. hr: 0x80040e14 Statement(s) could not be prepared.

TRACE-INFO: 35: 20 0.188226

TRACE-INFO: 36: [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 12988]: Error/Message: (err 8180, sev 0), Statement(s) could

not be prepared.

TRACE-INFO: 37: 20 0.188246

TRACE-INFO: 38: [dev trc ,00000] Procname: [##Y4IWDFVM21***00000063200000000001070407] 8 0.188254

TRACE-INFO: 39: [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 12988]: Error/Message: (err 208, sev 16), Invalid object

name 'SVERS'.

TRACE-INFO: 40: 53 0.188307

TRACE-INFO: 41: [dev trc ,00000] Procname: [##Y4IWDFVM21***00000063200000000001070407] 9 0.188316

TRACE-INFO: 42: [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 VERSION FROM

SVERS ]

TRACE-INFO: 43: 19 0.188335

TRACE-INFO: 44: [dev trc ,00000] Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum: 1112300

TRACE-INFO: 45: 13 0.188348

TRACE-INFO: 46: [dev trc ,00000] DbSlRead - Error 103 (dbcode 208) on open 14 0.188362

TRACE-INFO: 47: [dev trc ,00000] DbSlRead - <##Y4IWDFVM21***00000063200000000001070407> 9 0.188371

TRACE-INFO: 48: [dev trc ,00000] DbSlRead - Error 103 (dbcode 208) on fetch 10 0.188381

TRACE-INFO: 49: [dev trc ,00000] DbSlRead - <##Y4IWDFVM21***00000063200000000001070407> 9 0.188390

TRACE-INFO: 50: [dblink ,01299] ***LOG BZA=>table SVERS does not exist on database ["dblink#3 @ 1299]

TRACE-INFO: 51: 38 0.188428

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0232

standard output from tp and from tools called by tp:

Danial Khan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member

Juan Reyes

Thanks....Where can I verify or update this?

Danial

juan_reyes
Active Contributor
0 Kudos

My computer -> Properties -> Advanced -> Enviromental variables.

Regards

Juan

Former Member
0 Kudos

Juan

dms_type = mss....should be something else?

juan_reyes
Active Contributor
0 Kudos

There must be a parameter pointing at the SAP Schema and or instance.

read, SAP Note 534765 - db connect fails because of wrong db schema in environment

also

Read, SAP Note 351586 - TP: DBSL error 107, DB error 208 with Connect

Regards

Juan

Edited by: Juan Reyes on Feb 20, 2008 5:03 PM

Former Member
0 Kudos

Both the notes helped, specially 351586.

Followed the note per instruction...however now all other messages are gone except

ERROR: Connect to ERP failed (20080220111636, probably wrong environment.)

Furthermore did a cmd> tp connect to <SID> and got this...not sure if related.

D:\usr\sap\ERP\SYS\exe\uc\NTI386>tp connect hostname

This is tp version 371.02.23 (release 700, unicode enabled)

E-TPSETTINGS could not be opened.

EXIT

ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.

Error in TPSETTINGS: transdir not set.

Danial

juan_reyes
Active Contributor
0 Kudos

read this thread, it should solve that issue...

Regards

Juan

Answers (3)

Answers (3)

Former Member
0 Kudos

This was messy. Here was the end result

.............. FIX

TP TOOL CHECK ERROR : instead of erp, it takes dbo from local parameters

MCOD or Non-MCOD system ????

If MCOD , then Schema = "erp" else it should be "dbo"

sp_check_sap_login : erp, dbo, SAPERPDB .....

WTS : MSSQL_SCHEMA -> pointed to erp ( it was pointing to ERP)

Added system variable MSSQL_SCHEMA = erp

R/3 : STMS - added parameter MSSQL_SCHEMA = erp

Restarted R/3 ...

R/3 :

-


STMS - Check TP Tool : No errors reported now

SICK - No errors reported

SPAM - Updated successfully

..................... FIX END

Notes for fixing

The notes that eventually led me to this were:

First at all, please check if your current database version is

supported by SAP; you can inquire this by reading SAP Note 62988.

I also ask you to carefully read and check point per point the

following SAP notes, that are the basis for all the configuration

of an MS SQL Server 2005 for its use with SAP:

98678 - SQL Server Connection Issues

128126 - Database Connect for external tools

592514 - MSSQL: internal database users, permissions and security

799058 - Setting Up Microsoft SQL Server 2005

879941 - Configuration Parameters for SQL Server 2005

SAP Note 508140 - Customer messages - Customer logon data

SAP Note 610640 - sp_check_sap_login

Former Member
0 Kudos

Not fully answered

juan_reyes
Active Contributor
0 Kudos

Table SVERS cointain the information about SAP Version... usually this happen when the enviromental variable is pointing to the wrong instance in the Database.

Regards

Juan