STMS problem

[Former Member]

hi,

i have three system landscape, transport domain controller is my dev system,Quality is also included in it ,

but when i try to connect the production or when i try to configure STMS on Production system it gives error of duplicate entry at the time of define the domain system at start of STMS.

can any one tell me how to get rid of this .

[michael_mulvey · Accepted solution]

Hi grewal77,

Can you paste the exact error you are receiving into a post. I should be able to assist as soon as I know what error you are experiencing.

Michael

[Former Member · Accepted solution]

i remove TMS in STMS > extra > delete TMS Configuration

n after that used SE06 > Standerd installation >Perform Post-Installation Actions

it gives only> Perform after Installation Completed, configure TMS.

there is no orher option in between this

this is the error what i get at the time of using STMS n fill the required parametter.

-

---

Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC

Except. CX_SY_OPEN_SQL_DB

Date and Time 23.09.2010 13:09:28

Short text

The ABAP/4 Open SQL array insert results in duplicate database records.

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLSUU1" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "INTERNET_TO_DB" "(FORM)", nor was it propagated by a RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

If you use an ABAP/4 Open SQL array insert to insert a record in

the database and that record already exists with the same key,

this results in a termination.

(With an ABAP/4 Open SQL single record insert in the same error

situation, processing does not terminate, but SY-SUBRC is set to 4.)

HOW to correct the error

Use an ABAP/4 Open SQL array insert only if you are sure that none of

the records passed already exists in the database.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"

"SAPLSUU1" or "LSUU1F01"

"INTERNET_TO_DB"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"INTERNET_TO_DB" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

System environment

SAP-Release 701

Application server... "system"

Network address...... "172.164.110.36"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "16x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "system"

Database type..... "MSSQL"

Database name..... "DEV"

Database user ID.. "dev"

Terminal.......... "PC"

Char.set.... "C"

SAP kernel....... 701

created (date)... "Jan 28 2010 20:07:00"

create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"

Database version. "SQL_Server_8.00 "

Patch level. 69

Patch text.. " "

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version. 701

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0, Windows NT 6.1"

Memory consumption

Roll.... 16192

EM...... 12569520

Heap.... 0

Page.... 57344

MM Used. 1667936

MM Free. 2519280

[Former Member · Accepted solution]

Hi

See if this note is relevant Note 1412609 - DUPREQ when configuring the transport domain

[Former Member · Accepted solution]

Hi ,

The note 1412609 says to import the sap_basis package sapkb70107, but when i am importing this, it says TP error, no transport dir .

As said by David I delete transport on all the system's , and when I am reinstalling the Transport domain controller on DEV the error is same as described above in this post . So I am not been able to upload the SP sapkb70107.

what to do I am stuck here.

[Former Member · Accepted solution]

Use the Note Assistant (tcode: SNOTE) to implement the correction instructions

[Former Member · Accepted solution]

thanks to all as said by sap note 1412609

[former_member254755]

The simple resolution i found was to delete the TMSADM user and try the STMS again. It worked for me.

Thanks,

[Former Member]

Perfekt, delete SAP User TMSADM. Its work!

[Former Member]

Thanks vikram, my problem is solved by your advice.

Regards,

Satish

[Former Member]

Hi,

Instead of going for the support pack upgrade, implement this SAP note. There are entries in the tables that are double.

Implement and this should resolve the problem.

Regards

Sushant