csadmin gets timeout when trying to create a repository on maxdb

[Former Member]

Hi *,

i'am trying to install a ContentServer on a Windows 2003 Server system with an ECC 6.0 SR2 IDES installation.

The Installation worked only with SR3 media-set because of the 64-bit server-system.

I can connect to the db vi dbmcli, DB50N works well and DB59 also has a connection.

But if i try to create a repository on that DB I'll get an timeout:

IF_HTTP_CLIENT->RECEIVE 1 ICM_HTTP_TIMEOUT

I worked through note 794919, 631790 and many more which faced that error but nothing helped.

Here are some details of my installation:

sdbverify.exe

VERIFICATION SUMMARY:

*********************

INVALID PACKAGES: 0

VALID PACKAGES: 16

INCONSISTENT PACKAGES: 0

TOTAL FILES: 469

MISSED FILES: 0

MODIFIED FILES: 0

FILES WITH MODIFIED PERMISSIONS: 0

C:sapdbprograms in>sdbregview.exe -l

DB Analyzer c:/sapdb/programs 7.6.03.09 64 bit valid

Server Utilities c:/sapdb/programs 7.6.03.09 64 bit valid

PCR 7300 c:/sapdb/programs 7.3.00.59 valid

PCR 7301 c:/sapdb/programs 7.3.01.22 valid

PCR 7500 c:/sapdb/programs 7.5.00.46 64 bit valid

SAP Utilities c:/sapdb/programs 7.6.03.09 64 bit valid

Redist Python c:/sapdb/programs 7.6.03.09 64 bit valid

Base c:/sapdb/programs 7.6.03.09 64 bit valid

JDBC c:/sapdb/programs 7.6.03.03 valid

Messages c:/sapdb/programs MSG 0.5603 valid

ODBC c:/sapdb/programs 7.6.03.09 64 bit valid

Database Kernel c:/sapdb/sdb/db 7.6.03.09 64 bit valid

Loader c:/sapdb/programs 7.6.03.09 64 bit valid

SQLDBC c:/sapdb/programs 7.6.03.09 64 bit valid

SQLDBC 76 c:/sapdb/programs 7.6.03.09 64 bit valid

Fastload API c:/sapdb/programs 7.6.03.09 64 bit valid

C:sapdbprogramspgm>dbmcli.exe inst_enum

OK

7.6.03.09 C:sapdbSDBdb

C:sapdbprogramspgm>dbmcli.exe db_enum

OK

SDB C:sapdbSDBdb 7.6.03.09 fast running

SDB C:sapdbSDBdb 7.6.03.09 quick offline

SDB C:sapdbSDBdb 7.6.03.09 slow offline

SDB C:sapdbSDBdb 7.6.03.09 test offline

These are the only errors I can find but I have no ideas what to do next

2008-08-12 21:54:35 Monitoring C:sapdbdatawrkdbmsrv_ECSNMS005.prt

2008-08-12 22:05:02 2008-08-12 22:05:02 0x0000092c INF 216 DBMSrv DBM Server client connection (established at 2008-08-12 22:05:02): PID 2544 on computer ECSNMS005

2008-08-12 22:05:02 2008-08-12 22:05:02 0x0000092c INF 283 DBMSrv command file_getfirst ...

2008-08-12 22:05:02 2008-08-12 22:05:02 0x0000092c ERR -24994 DBMSrv ERR_RTE: Runtime environment error

2008-08-12 22:05:02 0x0000092c ERR -24778 DBMSrv 1,wrong file or device name

2008-08-12 22:05:02 2008-08-12 22:05:02 0x0000092c INF 226 DBMSrv DBM Server client disconnected: PID 2544 on computer ECSNMS005

2008-08-12 22:20:02 2008-08-12 22:20:02 0x00000774 INF 216 DBMSrv DBM Server client connection (established at 2008-08-12 22:20:02): PID 2956 on computer ECSNMS005

2008-08-12 22:20:02 2008-08-12 22:20:02 0x00000774 INF 283 DBMSrv command file_getfirst ...

2008-08-12 22:20:02 2008-08-12 22:20:02 0x00000774 ERR -24994 DBMSrv ERR_RTE: Runtime environment error

2008-08-12 22:20:02 0x00000774 ERR -24778 DBMSrv 1,wrong file or device name

2008-08-12 22:20:02 2008-08-12 22:20:02 0x00000774 INF 226 DBMSrv DBM Server client disconnected: PID 2956 on computer ECSNMS005

2008-08-12 22:35:02 2008-08-12 22:35:02 0x000017d0 INF 216 DBMSrv DBM Server client connection (established at 2008-08-12 22:35:02): PID 320 on computer ECSNMS005

2008-08-12 22:35:02 2008-08-12 22:35:02 0x000017d0 INF 283 DBMSrv command file_getfirst ...

2008-08-12 22:35:02 2008-08-12 22:35:02 0x000017d0 ERR -24994 DBMSrv ERR_RTE: Runtime environment error

2008-08-12 22:35:02 0x000017d0 ERR -24778 DBMSrv 1,wrong file or device name

2008-08-12 22:35:02 2008-08-12 22:35:02 0x000017d0 INF 226 DBMSrv DBM Server client disconnected: PID 320 on computer ECSNMS005

2008-08-12 22:50:02 2008-08-12 22:50:02 0x00000138 INF 216 DBMSrv DBM Server client connection (established at 2008-08-12 22:50:02): PID 348 on computer ECSNMS005

Tx DB59 connectiontest

13.08.2008 Dynamische Listenausgabe 1

-

-

---

Verbindungstest für die ausgewählte DB-Verbindung: SDB

-

-

---

|Servername |Rechner | Prüfergebnis |DBMRFC-Release|DBMCLI-Release|Kernel-Release|Kernel-Patch|Dbsl-Release|Dbsl-Patch|SQLDBC-Version|SQLDBC-Runtime

-

-

---

ECSNMS005_N2E_00

ecsnms005

@01QVerbindungstest erfolgreich@

7.6.03.09

7.6.03.09

700_REL

75

700.08

75

7.6.00.07

7.6.03.09

-

-

---

thanks in advance,

Dirk

[Melanie · Accepted solution]

Hello Dirk,

did you already open a SAP support message?

As you don't see any error messages which are directly related to the database, I would suggest to open

a message on component KM-KW.

The error messages in dbm.prt just mean that a database log file should be displayed, which does not exist.

Best regards,

Melanie

Edited by: Melanie Handreck on Aug 13, 2008 9:21 AM

[Former Member · Accepted solution]

SAPNote: 301352 brought the solution. The ODBC-Driver had to reregistered.

greetings

Dirk