Error (-1200) DBMCconnBase; End Transaction- Error -1 detected, auto rollba

Que tal!!!
Pues ahora tengo este problema, este sap nos esta sacando canas verdes!!
resulta que cuando se esta realizaondo una factura y aparece la ventana donde se ingresa el numero de folio del documento y se da el OK aparece ese error
(-1200) DBMCconnBase; End Transaction- Error -1 detected, auto rollback flag is off, Throwing exception
cuando lo aceptamos solo cierra SAP, ingresamos de nuevo yse puede facturar durante el dia se presenta de manera aleatoria!!
siento que es grave el error.. asi que espero que me puedan ayudar!!

Mi estimado, ese es un bug segun nota 1401013 de SAP, ocurre cuando dos usuarios estan trabajando simultaneamente.
Aqui el texto de la misma nota.
Summary
Symptom
You work in localization where folio numbers for documents are used.
Two users are working simultaneously on SAP Business One (either via SAP Business One application or via an Add-on).
Both users are creating Invoice (or performing any action when max folio number is retrieved from the numbering table NNM1).
It may happen that one of the users will encounter deadlocks while working, usually with one of the following error messages:
'-2038 Internal error'
'Error (-1200) DBMCconnBase:: EndTransaction - Error -1 detected. auto rollback flag is off. throwing exception'
'Internal error NNM1 2038'
The deadlock can appear on NNM1 table and OINV table.
Other terms
Lock, Add, Error, Crash, Close, Exit, Operation, Action, Parallel, Same Time
Reason and Prerequisites
Application error
En que parche andas?
Esto se arreglo con el parche 09 del service pack 01

Similar Messages

Could we get a deadlock error on COMMIT (END TRANSACTION) in BDB-SQL

According to the DB_TXN->commit documentation at:
http://download.oracle.com/docs/cd/E17076_02/html/api_reference/C/txncommit.html
"After DB_TXN->commit() has been called, regardless of its return, the DB_TXN handle may not be accessed again.
If DB_TXN->commit() encounters an error, the transaction and all child transactions of the transaction are aborted."
Since BDB-SQL uses the BDB engine, should the code handle such errors in BDB-SQL?
Another point to keep in mind is that, post BDB-SQL version 5.1 upon receiving a potential deadlock error all the previous operations(child transactions) in the same transaction are still valid and can be committed.
It would be great if someone can throw some light on this.
Edited by: user10942853 on Jul 28, 2011 9:31 AM

user10942853 wrote:
LaurenFoutz wrote:
I do not think commit can experience a deadlock error since it does not obtain any new locks, and it could not have been in a blocked state if you are able to call commit. Either way, after calling commit on a transaction in SQL the transaction is done, even if an error is returned. At that point if an error is returned the transaction (and all the work its children have done) is either aborted under the covers, or the database has been corrupted, and all future calls to it will return a corruption error that will require restarting the database to restore it (and the restoration will roll back any work done by the transaction since it did not complete cleanly).
Hope that answers your question.
Lauren FoutzLauren, thanks for the reply. From your reply, though there is little possibility that we can get an error on commit looks like we should be prepared to handle such errors in BDB-SQL. We have had instances where we experienced an error on commit while using native BDB (without SQL API) and wanted to confirm the same.You are correct. Error when committing are rare in both the SQL and native API, but they can happen and you should deal with them when they do.
Lauren Foutz

"Could not commit transaction: Error -1 detected during transaction"

hi guys,
im getting this error "Could not commit transaction: Error -1 detected during transaction" when trying to create standard document/s. i am now using B1 8.8, MS SQL 2008.
originally, my program was written for B1 2005, MS SQL 2005, and it WORKED.
we upgraded into B1 8.8, MS SQL 2008, and now my program is not working. it is now having the mentioned error upon committing transaction (vCompany.EndTransaction(wf_Commit)). tried removing transaction handling, and it WORKED. also, tried simplifying the program, instead of creating multiple documents, i modified it in just creating one document with transaction handling, and it WORKED.
initialliy, this issue seems to be related to MS SQL 2008.
please help, thanks.

Hi Emmanuel........
You get this error due to the Approval Procedure.
Please check if it is activated then please deactivate it from Administration> Approval> Approval Template.......
Then try.......
Regards,
Rahul

'Receiving Transaction Processor' ends with error. Receipt not saved.

Trying to make receipt. On header done add to receipt. When the receipt is selected and saved. & then tried to open receving transaction. Receipt NOT found also 'Receiving Transaction Processor' ends with error.
Plz Suggest soluntion.
Regds
9999

When we do receipts then atomatically receiving transaction process runs. On header of receipt there is add to receipt oprtion. User adding in erliar made receipt. But when done add to receipt transction get saved but this receipt number not able to find in receiving transaction.
Now kindly help..!!!
9999

Transaction errors: The lock operation ended unsuccessfully because of deadlock.

Hi,
One of our process is getting "Transaction errors: The lock operation ended unsuccessfully because of deadlock." error while processing Partitions in AS 2005.
We have a process that processes dimensions and partitions based on a SQL table. Sometimes when the it is processing two partitions at the same time (multi-threaded) for same measure group, server throws deadlock error. This does not happen all the time.
Both partitions are bound to different tables in relational database and I also traced the SQL Server and did not get any deadlock error.
I searched for this error on Google and did not find anything.
Anyone have any idea about this error?
Thanks

Hi All,
when i execute the job for cube refreshment,sometimes it is executing successfully,but sometimes it is getting failed with below error
Started: 4:08:08 AM Error: 2015-01-14 04:55:21.03 Code: 0xC11D0005 Source: Analysis Services Processing Task Analysis Services Execute DDL Task Description: Transaction errors: The lock operation
ended unsuccessfully because of deadlock. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 4:08:08 AM Finished: 4:55:21 AM Elapsed: 2832.18 seconds. The package execution failed. The
step failed.
If any find the solution please post on it.
Thanks
Rambabu

Could not commit transaction Error 1 Detected During Transaction G/L Account

hi experts
when i was adding Sales Order i am getting an error as Could not commit transaction Error 1 Detected During Transaction G/L Account

Hi,
Plz find the following threads:
Transaction failure with error message \"Error -1 detected during transaction\" when update the G\\L Account D…
"Could not commit transaction: Error -1 detected during transaction"
Could not commit transaction: Error -1 detected during transaction 'Payment Methods for Payment Wizard' (OPYM)
Could not commit transaction when inserting new items

The report l runs very night and gets ended with error

Dear all,
I am facing a problem in solution manger. There is an report (Program/Command RDSMOPSOL_MONIREFRESH ) will runs very night and get ended with error and there is Run-time error "MESSAGE_TYPE_X".
Please suggest how to solve the problem.
Is this report is necessary   for the system because it is not mention in the sap stand jobs.
SM37 log
Job started
Step 001 started (program RDSMOPSOL_MONIREFRESH, variant &0000000000875, user ID BASIS)
Opening and closing session started. Session SM2000000000065
Opening and closing the session was successful. Session: SM2000000000065
Opening and closing session started. Session SM2000000000005
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled
SM:CSA SESSION REFRESH
No. Program/Command       Prog. type Spool list Parameter      User Lang.
1 RDSMOPSOL_MONIREFRESH ABAP                  &0000000000876 BASIS EN
Sm21 log
00:00:50 DIA 00 000 SAPSYS            EEA OPERATION MODES: Switch to operation mode Normal triggered
00:30:57 BTC 08 200 BASIS             R68 Perform rollback
00:30:57 BTC 08 200 BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
00:30:57 BTC 08 200 BASIS             AB1 > Short dump "081112 003057 sapsm BASIS " generated
00:30:57 BTC 08 200 BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081112003057sapsm BASIS 2001 )
00:30:57 BTC 08 200 BASIS             R68 Perform rollback
00:30:57 BTC 08 200 BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
Details
Recording at local and central time........................ 12.11.2008 00:30:57
Task................ 05312 . 08 B8 BTC background processor No. 08
User................ BASIS
Client.............. 200
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... T    Transaction Problem
Development class... SABP
Further details for this message type
Module name......... abdynpro
Line................ 1133
Error text.......... ab_jmess
Documentation for system log message AB 0 :
The specified runtime error has occurred in the system.
Parameter
a.. MESSAGE_TYPE_X
Technical details
File................ 000048
Position............ 0000253620
Entry type.......... l      ( Error (Module, Row)            )
Message ID.......... AB 0
Variable parts...... ab_jmess                                            abdynpro1133
Time     Ty. Nr Cl. User         Tcod MNo Text                                                                    Date : 12.11.08
00:30:57 BTC 08 200 BASIS             AB1 > Short dump "081112 003057 sapsm BASIS " generated
etails
ecording at local and central time........................ 12.11.2008 00:30:57
ask................ 05312 . 08 B8 BTC background processor No. 08
ser................ BASIS
lient.............. 200
erminal............
ession............. 1
ransaction code....
rogram name........
roblem class....... K    SAP Web AS Problem
evelopment class... SABP
BAP Mini dump
ate................ 20081112
ime................ 003057
ost................ sapsm
ser................ BASIS
ocumentation for system log message AB 1 :
A short dump was generated for the specified program termination.
You can analyze this short dump in the system log evaluation by
selecting this line or evaluating Table SNAP (Transaction ST22).
echnical details
ile................ 000048
osition............ 0000253800
ntry type.......... s      ( ABAP Runtime Error             )
essage ID.......... AB 1
ariable parts...... 081112003057sapsm   BASIS
Time     Ty. Nr Cl. User         Tcod MNo Text                                                                    Date : 12.11.08
00:30:57 BTC 08 200 BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081112003057sapsm BASIS 2001 )
Details
Recording at local and central time........................ 12.11.2008 00:30:57
Task................ 05312 . 08 B8 BTC background processor No. 08
User................ BASIS
Client.............. 200
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... K    SAP Web AS Problem
Development class... SDYN
Module name.........
Location............
T100................ 00                  671
Parameters..........
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Additional documentation for message 00                  671
ABAP/4 processor: &
No documentation exists for message 00671
Parameter
a.. MESSAGE_TYPE_X
00:30:57 BTC 08 200 BASIS             R68 Perform rollback
Details
Recording at local and central time........................ 12.11.2008 00:30:57
Task................ 05312 . 08 B8 BTC background processor No. 08
User................ BASIS
Client.............. 200
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... W    Warning
Development class... STSK
Further details for this message type
Module name......... thxxhead
Line................ 1240
Error text..........
Caller.............. ThIRoll
Reason/called....... roll ba
Documentation for system log message R6 8 :
An error has causes an SAP rollback. All database updates are reset.
Technical details
File................ 000048
Position............ 0000254520
Entry type.......... m      ( Error (Function,Module,Row)    )
Message ID.......... R6 8
Variable parts......                                       ThIRollroll bathxxhead1240
Regards,
Shiva

Hi karteek,
I have check there is Switch of operation mode but when I have checked the t-code sm63 there is no new mode are in normal mode.
There is one thing I want to ask dose this report (Program/Command RDSMOPSOL_MONIREFRESH ) run   in your system or any one server because I have think there is some problem in job shued
and is also not mention in the sap stand jobs.
there is an error in sm21 in job.
BASIS        SM36 EFK BP_CHECK_REPORT_VALUES: Invalid program values found. Reason:
BASIS        SM36 EFC > Program RDSMOPSOL_MONIREFRESH has no variants, but a variant was specified
Is this SM37 log
Job started
Step 001 started (program RDSMOPSOL_MONIREFRESH, variant &0000000000875, user ID BASIS)
Opening and closing session started. Session SM2000000000065
Opening and closing the session was successful. Session: SM2000000000065
Opening and closing session started. Session SM2000000000005
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled
Sm21 log
SAPSYS            EEA OPERATION MODES: Switch to operation mode Normal triggered
BASIS             R68 Perform rollback
BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
BASIS             AB1 > Short dump "081111 003056 sapsm BASIS " generated
BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081111003056sapsm BASIS 2001 )
BASIS             R68 Perform rollback
BASIS             R49 Communication error, CPIC return code 017, SAP return code 223
BASIS             R64 > CPI-C function: CMINIT(SAP)
*BASIS        SM36 EFK BP_CHECK_REPORT_VALUES: Invalid program values found. Reason:*
*BASIS        SM36 EFC > Program RDSMOPSOL_MONIREFRESH has no variants, but a variant was*
specified
BASIS             R68 Perform rollback
BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
BASIS             AB1 > Short dump "081111 220948 sapsm BASIS " generated
BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081111220948sapsm BASIS 2001 )
Details Page 2 Line 6 System Log: Local Analysis of sapsm                     1
Time     Ty. Nr Cl. User         Tcod MNo Text
00:00:51 DIA 00 000 SAPSYS            EEA OPERATION MODES: Switch to operation mode Normal triggered
Details
Recording at local and central time........................ 13.11.2008 00:00:51
Task................ 04100 . 00 D0 Dialog work process No. 00
User................ SAPSYS
Client.............. 000
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... S    Operation Trace
Development class... SBTC
Sm63
Start/end time   Name of the active operation mode
   00.00 - 01.00    Normal
   01.00 - 02.00    Normal
   02.00 - 03.00    Normal
   03.00 - 04.00    Normal
   04.00 - 05.00    Normal
   05.00 - 06.00    Normal
   06.00 - 07.00    Normal
   07.00 - 08.00    Normal
   08.00 - 09.00    Normal
   09.00 - 10.00    Normal
   10.00 - 11.00    Normal
   11.00 - 12.00    Normal
   12.00 - 13.00    Normal
   13.00 - 14.00    Normal
   14.00 - 15.00    Normal
   15.00 - 16.00    Normal
   16.00 - 17.00    Normal
   17.00 - 18.00    Normal
   18.00 - 19.00    Normal
   19.00 - 20.00    Normal
   20.00 - 21.00    Normal
   21.00 - 22.00    Normal
   22.00 - 23.00    Normal
   23.00 - 00.00    Normal
Regards,

Error while comitting a transaction in oSB. The following is the error stack

Error while comitting a transaction in OSB. The following is the error stack
<Apr 20, 2015 12:00:15 AM MDT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-1AE41F1CAE45F2B146FD(296700848),Status=Rolled back. [Reason=Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=2,seconds left=120,XAServerResourceInfo[WLStore_SOA_PRDKS_DOMAIN_FileStore_SOA_MS2]=(ServerResourceInfo[WLStore_SOA_PRDKS_DOMAIN_FileStore_SOA_MS2]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1]=(ServerResourceInfo[WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1]=(state=rolledback,assigned=OSB_MS1),xar=WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_11603460297,re-Registered = false),XAServerResourceInfo[weblogic.jdbc.jta.DataSource]=(ServerResourceInfo[weblogic.jdbc.jta.DataSource]=(state=ended,assigned=none),xar=CMSDS,re-Registered = false),SCInfo[OSB_PRDKS_DOMAIN+OSB_MS1]=(state=rolledback),SCInfo[SOA_PRDKS_DOMAIN+SOA_MS2]=(state=pre-prepared),properties=({}),local properties=({weblogic.jdbc.jta.CMSDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=OSB_MS1+soaprd-vip-osb-ms1.cos.is.keysight.com:8001+OSB_PRDKS_DOMAIN+t3+, XAResources={eis/wls/Queue, WEDB_EVEREST_OSB_PRDKS_DOMAIN, XREFDS_OSB_PRDKS_DOMAIN, eis/activemq/Queue, CustomSchemaDS_OSB_PRDKS_DOMAIN, MobileApps_CIA_DS1_OSB_PRDKS_DOMAIN, eis/tibjmsDirect/Queue, eis/jbossmq/Queue, eis/Apps/Apps, MobileApps_AOS_MDS_OSB_PRDKS_DOMAIN, MobileApps_AOS_DRDS_OSB_PRDKS_DOMAIN, WSATGatewayRM_OSB_MS1_OSB_PRDKS_DOMAIN, eis/webspheremq/Queue, eis/AQ/aqSample, SBLPROD_OSB_PRDKS_DOMAIN, wlsbjmsrpDataSource_OSB_PRDKS_DOMAIN, eis/aqjms/Queue, CMSDS_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN_WseeFileStore_auto_1, FAP_OSB_PRDKS_DOMAIN, eis/sunmq/Queue, eis/pramati/Queue, FMWAPPDS_OSB_PRDKS_DOMAIN, weblogic.jdbc.jta.DataSource, GSDC_OSB_PRDKS_DOMAIN, eis/tibjms/Topic, eis/fioranomq/Topic, WLStore_OSB_PRDKS_DOMAIN_FileStore_MS1, PresidioOracleAppsDS_OSB_PRDKS_DOMAIN, GSDCDS_OSB_PRDKS_DOMAIN, eis/aqjms/Topic, CustOutDS_OSB_PRDKS_DOMAIN, OFMW/Logging/BAM, MobileAppsDS_OSB_PRDKS_DOMAIN, FIDDS_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN__WLS_OSB_MS1, HRMSDS_OSB_PRDKS_DOMAIN, WEDB_OSB_PRDKS_DOMAIN, OracleAppsDS_OSB_PRDKS_DOMAIN, eis/wls/Topic, eis/tibjms/Queue, eis/tibjmsDirect/Topic, IntrastatDS_OSB_PRDKS_DOMAIN, MobileApps_AOS_COSDS_OSB_PRDKS_DOMAIN, MobileApps_CIA_DS2_OSB_PRDKS_DOMAIN, EVEREST_WEDB_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1, Everest_OSB_PRDKS_DOMAIN},NonXAResources={})],CoordinatorURL=SOA_MS2+soaprd-vip-soa-ms2.cos.is.keysight.com:8002+SOA_PRDKS_DOMAIN+t3+): javax.transaction.SystemException: Lost connection to server while commit was in progress, ignoring because initiating server is not coordinating server. Remote Exception received=weblogic.rjvm.PeerGoneException: ; nested exception is:
        java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
        java.io.InvalidClassException: oracle.jdbc.xa.OracleXAException; local class incompatible: stream classdesc serialVersionUID = -2542408691177300269, local class serialVersionUID = -4551795881821760665
        at weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:376)
        at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:237)
        at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:224)
        at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:552)
        at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:423)
        at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:325)
        at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
        at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
        at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
        at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
        at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hi,
Have you tried Cancelling the release before adding the version?
Select the active version of the IDOC Segment and cancel its release first. Only then you will be able to add a version.
Please let me know if it worked!
Vijay

Error: failed to prepare transaction (could not satisfy dependencies)

Hi,
I was going to install a winff package (a GUI front end to ffmpeg for converting between video formats), but when I ran yaourt -S winff and tried to install it refused because it isn't for the x86_64 architecture. So I decided to edit the PKGBUILD and perhaps try to force it anyway, but then I saw that the PKGBUILD is actually getting the precompiled RPM package and as I checked, while there was no precompiled 64bit version of the RPM there was one for a deb version that is offered on winff site.
Since deb's are just archives I ended up, after a few tries, with this PKGBUILD which uses ar and tar commands to get to the binaries inside of the amd64 deb:
# Contributor: yugrotavele <[email protected]>
# Modified by libervisco for x86_64
pkgname=winff-amd64
pkgver=0.42
pkgrel=1
pkgdesc="GUI for ffmpeg"
url="http://www.winff.org"
license=('GPL')
depends=('ffmpeg gtk gdk-pixbuf')
makedepends=('')
source=('http://winff.googlecode.com/files/winff-0.42-amd64.deb')
arch=('x86_64')
md5sums=('1febf5fd19fa76bdc1da06d3e6c4d3b8')
build() {
ar vx winff-0.42-amd64.deb
tar xvzf data.tar.gz
install -Dm755 $startdir/src/usr/bin/winff $startdir/pkg/usr/bin/winff
install -Dm755 $startdir/src/usr/share/winff/presets.xml $startdir/pkg/usr/share/winff/presets.xml
install -Dm755 $startdir/src/usr/share/winff/winff.png $startdir/pkg/usr/share/winff/winff.png
So what I basically do is run yaourt -S winff and when it asks whether I want to edit it, I edit it and replace the original PKGBUILD content with above.
It successfully runs the build() commands, finds and installs the dependencies, but when it's time to install the actual new winff package is throws up this:
loading package data...
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: winff: requires ffmpeg gtk gdk-pixbuf
I don't get it. It installed all the dependencies (and I even checked whether winff works in one of the earlier tries when I manually installed gdk-pixbuf when the binary asked for it). What does it want now?
Here is the whole process:
[daniel@memeport ~]$ yaourt -S winff
==> Downloading winff PKGBUILD from AUR...
Comment by: yugrotavele on 20080518 [04:36:56]
A nice GUI frontend for ffmpeg.
First Submitted: Sun, 18 May 2008 04:28:31 +0000
Last Updated: Mon, 30 Jun 2008 04:23:08 +0000
winff 0.42-1 (Unsupported): GUI for ffmpeg
==> winff dependencies:
- ffmpeg (already installed)
- rpmextract (already installed)
==> Edit the PKGBUILD (recommended) ? [Y/n] ("A" to abort)
==> ----------------------------------------------
==>y
Please add $EDITOR to your environment variables
for example:
==> Edit PKGBUILD with: (replace gvim with your favorite editor)
==> Edit ./PKGBUILD with: gedit
==> winff dependencies:
- ffmpeg (already installed)
- gtk (already installed)
- gdk-pixbuf (package found)
==> Continue the building of 'winff'? [Y/n]
==> ----------------------------------------------
==>y
==> Building and installing package
==> Making package: winff 0.42-1 (Tue Jul 1 21:34:12 CEST 2008)
==> Checking Runtime Dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for inter-conflicts...
Targets: gdk-pixbuf-0.22.0-4
Total Download Size: 0.00 MB
Total Installed Size: 0.70 MB
Proceed with installation? [Y/n]
checking package integrity...
(1/1) checking for file conflicts [############################################################] 100%
(1/1) installing gdk-pixbuf [############################################################] 100%
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Downloading winff-0.42-amd64.deb...
--2008-07-01 21:34:13-- http://winff.googlecode.com/files/winff-0.42-amd64.deb
Resolving winff.googlecode.com... 64.233.187.82
Connecting to winff.googlecode.com|64.233.187.82|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1383594 (1.3M) [application/x-archive application/x-debian-package]
Saving to: `winff-0.42-amd64.deb'
100%[=============================================================================>] 1,383,594 191K/s in 7.4s
2008-07-01 21:34:21 (183 KB/s) - `winff-0.42-amd64.deb' saved [1383594/1383594]
==> Validating source files with md5sums...
winff-0.42-amd64.deb ... Passed
==> Extracting Sources...
==> Entering fakeroot environment...
==> Starting build()...
x - debian-binary
x - control.tar.gz
x - data.tar.gz
./usr/
./usr/bin/
./usr/bin/winff
./usr/share/
./usr/share/doc/
./usr/share/doc/winff/
./usr/share/doc/winff/copyright
./usr/share/doc/winff/winff.pdf
./usr/share/doc/winff/README.txt
./usr/share/doc/winff/README-Icons.txt
./usr/share/doc/winff/README-Presets.txt
./usr/share/doc/winff/changelog
./usr/share/applications/
./usr/share/applications/winff.desktop
./usr/share/winff/
./usr/share/winff/winff.png
./usr/share/winff/presets.xml
./usr/share/winff/languages/
./usr/share/winff/languages/winff.es.po
./usr/share/winff/languages/winff.nl.po
./usr/share/winff/languages/winff.fr.po
./usr/share/winff/languages/winff.pb.po
./usr/share/winff/languages/winff.tr.po
./usr/share/winff/languages/winff.de.po
./usr/share/winff/languages/winff.zh.po
./usr/share/winff/languages/winff.it.po
./usr/share/winff/languages/winff.pt.po
./usr/share/winff/languages/winff.pl.po
./usr/share/winff/languages/winff.bg.po
./usr/share/winff/languages/winff.po
==> Tidying install...
-> Removing info/doc files...
-> Compressing man pages...
-> Stripping debugging symbols from binaries and libraries...
==> Creating package...
-> Generating .PKGINFO file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: winff (Tue Jul 1 21:34:22 CEST 2008)
==> Continue installing 'winff'? [Y/n]
==> [v]iew package contents [c]heck package with namcap
==> ----------------------------------------------
==>y
loading package data...
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: winff: requires ffmpeg gtk gdk-pixbuf
==> WARNING: Your package is saved in /tmp/winff-0.42-1-x86_64.pkg.tar.gz
I tried doing it without changing the package name to winff-amd64, but same thing happens. What's going on?

Ahh man, and that's it! It works.
I'm just wondering now how can I contribute this PKGBUILD to AUR, but I can read that in the wiki too.
Thanks!

Transport control program tp ended with error code 0203

when i import queue and transport queue from dev to prd ,error show:
Transport control program tp ended with error code 0203
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: IMPORT DEVK900298 P01 clientP01 U0 pf=/usr/sap/tra
Return code: 0203
Error text: wrong syntax in tp call
Request: DEVK900298
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.

Dear Allen,
The transport control program tp collects all return codes that occur when a tp command is executed. From all of these single return codes, a combined return code is calculated that tp outputs as a result at the end the command. During an import, for example, all return codes for individual import steps are handled. If a special return code does not occur, then the combined return code at the end is the maximum of individual return codes that occur. In addition to the value of the return code, tp also gives a short description of this return code. You can display this short description using the command explainrc.
Normally, all return codes that occur originate from individual transport steps. Since these individual return codes can only have the following values 0, 4, 6, 8, 12, 13, 14, 16, the combined return code also has one of these values. However, if a general error occurs, a single return code over 200 is generated. For example, this could arise if tp cannot establish a connection to the database. The maximum return code for all single transport steps is output in a separate message before specifying the combined returned code. In this case, the combined return code is always the return code of the general error message.
<b>tp Commands:</b>
tp addtobuffer <request> <sapsid>
As of Release 4.6A, an explicit addtobuffer command leaves the position of the entry unchanged, if the relevant transport request is already in the buffer. Only the status of the entry is changed:
Unconditional modes appearing in the command line are added to the unconditional modes in the buffer.
All the steps of the entry are re-initialized.
If the entry found is not an initial entry, the import step for the command file is set to *4000 .
Before you call this command and its options, consider the effects of changing the import sequence.
tp cleanbuffer <sapsid>
This deletes successfully imported change requests from the list of requests that are marked for import into the SAP System <SAPSID>. This function is contained in the commands tp import all <sapsid> and tp put <sapsid> .
tp delfrombuffer <request> <sapsid>
If the specified request is marked for import into the specified SAP System, this flag is deleted from the import list.
Before you call this command, consider the effects of changing the import sequence.
As of Release 4.6A: If a transport request was only partially imported, you can delete this type of transport request from the buffer. However, if a deleted transport request is placed in the buffer (without having been initially or completely imported), the attributes of the old entry are reactivated. This means the return codes, the unconditional modes and tags of the deleted entry appear in the new entry.
tp delstopmark <sapsid>
If the list of requests marked for import into the specified SAP System contains a STOP mark, the mark is deleted.
tp export <request>
This exports the complete request from the source system. This command starts the export of a request from the operating system level. Only use this command in exceptional cases. The SAP System uses the command expwbo to release requests from CTS transactions.
tp reformatbuffer <sapsid> [options]
This automatically reformats the entire buffer.
As of Release 4.5A, there are 2 different formats for buffer entries. (As of Release 4.5A, tp can work with both formats, and with a puffer containing heterogeneous entries. As of Release 4.6A, tp can work with 3 formats.)
However, in certain cases entries with the old formatting have to be reformatted during the normal run of tp . In this case, the entire buffer is automatically reformatted.
If you use the options downtorelease and Iagree for command reformatbuffer , you can format the buffer so that its formatting is compatible with an older release:
Option downtorelease <Release>
The command reformatbuffer with this option formats the buffer so that the formatting corresponds to the one used in an old release. This is necessary if tp writes buffer entries to the buffer of another system, but uses a buffer format that the transport control programs does not understand in this system.
Since older formats cannot store the same amount of information as the newer ones, some information contained in the original buffer may not be stored in the unformatted buffer. This may lead to data loss.
To avoid data loss, the original buffer is stored. In addition, you have the following functions:
Displaying the unformatted buffer (using showbuffer <SID> )
Displaying the original buffer (using showbuffer buffer=<SID>SAV )
Accepting the unformatted buffer (using reformatbuffer and the option Iagree yes )
Resetting the changes (using reformatpuffer and the option Iagree no )
If you call reformatpuffer using downtorelease , tp displays in detail if information was lost by reformatting, and what that information was. tp also names the commands that is has to execute to accept or reject the changes.
If you use the option downtorelease , you must also specify the option Iagree with yes or no . You cannot use the transport system until you decide to accept or reject the changes.
Option Iagree
Here are the following values for this option:
yes ( true )
Accept the change made by tp reformatbuffer <SID> downtorelease <rel>
In this case, tp deleted the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
no ( false )
Reject the change made by tp reformatbuffer <SID> downtorelease <rel> In this case, tp copies the backup of the original buffer back and deletes the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
tp setstopmark <sapsid>
A special STOP mark is added to the list of requests registered for import into the specified SAP System. The commands tp import all <sapsid> and tp put <sapsid> only process the requests in front of this stop mark.
If there is no stop mark, it is automatically generated by the commands
tp import all <sapsid> and tp put <sapsid> .
When all the requests in front of the stop mark have been imported successfully, at the end of all the calls the related marks and the mark itself are deleted.
A STOP mark can only be placed at the end of the change requests that have already been marked. In addition, it can only be set if no other mark of the same kind already exists.
tp showparams <sapsid>
This tp function displays which values the individual parameters of the transport profile have for the current SAP System.
tp verse <request>
This creates versions of the objects in the specified request. This transport step is contained in command export .
As of Release 4.5A, more actions that prepare the export are performed in this step.
Thanks and Regards,
Naveen.

Transport control program tp ended with error code 0212 | URGENT

Hi All,
         We are trying to import requests in our PRD system. As soon as we select the request and try to import it , we get the error "Transport control program tp ended with error code 0212".
This is tp version 305.12.42 (release 46D) for ANY database
/usr/sap/trans/cofiles/K915883.<SID> for transport: <SID>K915883: Permissio
HALT 20070222114323
ERROR: /usr/sap/trans/cofiles/K915883.<SID> : cant open
: Permission denied
ERROR: EXIT(16) -> process ID is: 6878
tp returncode summary:
TOOLS: Highest return code of single steps was: 16
ERRORS: Highest tp internal error was: 0212
Output from tools called by tp:
This is R3trans version 6.05 (release 46D - 18.10.01 - 11:30:00).
R3trans finished (0000).
When i checked the transport tool and rfc destinations, everything was successful.
When i tried to do tp connect -
23> tp connect <SID> pf=/usr/sap/tran/bin/TP_DOMAIN_<SID>.PFL
This is tp version 305.12.42 (release 46D) for ANY database
E-/usr/sap/tran/bin/TP_DOMAIN_<SID>.PFL could not be opened.
EXIT
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0212
tp finished with return code: 212
meaning:
could not access file as supposed (see SLOG for more details)
We are having SAP 4.6C with DB -Oracle and OS HP-UX.
Please let me know whow to rectifiy the issue. The situation here is getting worse.
Regards,
NK

Hi Ruchit, Sorry for the delay. Here is the file you wanted -
steic25q:root>ls
DOMAIN.CFG          TPPARAM.bak         TP_DOMAIN_ID1.PFL   TP_DOMAIN_IQ1.PFL
TMS_TEST.IS1        TPPRAMA0918         TP_DOMAIN_ID1.orig nik.dev_evt
TPPARAM             TP_DOMAIN_ID1.BAK   TP_DOMAIN_IP1.BAK
steic25q:root>more TP_DOMAIN_ID1.PFL
#TMS:0078:DOMAIN_ID1
Caution !
This file was generated by the Transport Management System.
Do not change this file using a text editor.
For more information, refer to the online documentation of the
Transaction STMS.
If this file was destroyed, it can be regenerated in the TMS.
To do this, log on to the domain controller (system ID1) and call
transaction STMS. In the System Overview, you can distribute the TMS
configuration. This regenerates the file.
STMS -> Overview -> Systems -> Extras -> Distribute TMS configugration
TRANSDIR            = /usr/sap/trans
DU1/CTC             = 1
DU1/DUMMY           = 1
DU1/NBUFFORM        = 1
DU1/TP_VERSION      = 266
DU2/CTC             = 1
DU2/DUMMY           = 1
DU2/NBUFFORM        = 1
DU2/TP_VERSION      = 266
ID1/CTC             = 0
ID1/DBHOST          = steic24q
ID1/DBLIBPATH       = /usr/sap/ID1/SYS/exe/run
ID1/DBNAME          = ID1
ID1/DBSWPATH        = /oracle/ID1/817_64
ID1/DBTYPE          = ora
ID1/NBUFFORM        = 1
ID1/TP_VERSION      = 266
IP1/CTC             = 0
IP1/DBHOST          = steic25q
IP1/DBLIBPATH       = /usr/sap/IP1/SYS/exe/run
IP1/DBNAME          = IP1
IP1/DBSWPATH        = /oracle/IP1/817_64
IP1/DBTYPE          = ora
IP1/NBUFFORM        = 1
IP1/TP_VERSION      = 266
IQ1/CTC             = 1
IQ1/DBHOST          = cbnysap2
IQ1/DBLIBPATH       = /usr/sap/IQ1/SYS/exe/run
IQ1/DBNAME          = IQ1
IQ1/DBSWPATH        = /oracle/IP1/817_64
IQ1/DBTYPE          = ora
IQ1/NBUFFORM        = 1
IQ1/TP_VERSION      = 266
TRN/CTC             = 1
TRN/DUMMY           = 1
TRN/NBUFFORM        = 1
TRN/TP_VERSION      = 266
steic25q:root>

Screen Error while saving VA02 Transaction

Dear All,
Yesterday there was a sudden power failure in my company. Even UPS also got fail. Due to which some errors are coming in Production Server.
The error is coming in VA02 transaction while saving the transaction. The error is: "SAP SYSTEM MESSAGE - ERROr IN LOADING SCREEN: NO END LABEL".
Here is the below log from SM21 transaction.
Date : 31.10.2009
Time -Type-Nr-Clt-User-TCode-Priority-Grp-N-Text
18:54:00-DIA-000-554-ITDEPT--VA02-D0-1-ransaction Canceled 00 029 ( SAPLSPO2 0301 )
18:54:01-DIA-000-554-ITDEPT----
R4-7-Delete session 001 after error 024
So can you please explain, what I need to do to resolve the error. Although I have already activated the program SAPMV45A.
Regards,
Vishal

This link describes similar circumstances.
Error Loading Screens - No End Label
No solution was found and OSS logging was suggested.

Getting error after enabling the Transaction in SSIS package in Windows Server 2008 R2 Standard machine

Hi,
I created a package with "Execute SQL Task and Data Flow Task". I am able to execute successfully in my server having
"Windows Server 2008 R2 Standard" Operating System.
But after enabling the Transaction in my SSIS Package I am not able to execute it. It is giving error. The same package is running in my local machine with Transaction enabled on
Windows 7 Operation System.
The error which I got in my server after enabling the Transaction is
"The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D025
"The partner transaction manager has disabled its support for remote/network transactions.". End Error "
I search with this error message in google and found some solutions in the following links
http://social.msdn.microsoft.com/Forums/en-US/7172223f-acbe-4472-8cdf-feec80fd2e64/the-partner-transaction-manager-has-disabled-its-support-for-remotenetwork-transactions
http://technet.microsoft.com/en-us/library/cc753510(WS.10).aspx
http://support.microsoft.com/kb/817064
But none of the above solution is not working. Kindly help me to resolve this issue.
Thanks in Advance.
Sridhar

Hi Sridhar,
Please compare the DTS settings on the Windows 7 computer and the Windows Server 2008 R2 computer and make sure they are identical. Make sure the “Allow Inbound” and “Allow Outbound” options are check, and pay attention to the authentication mode as
well.
Besides, make sure both Distributed Transaction Coordinator (TCP-In) and Distributed Transaction Coordinator (TCP-Out) rules in Firewall are enabled.
If the issue persists and there are any security/anti-virus software, temporarily disable the security/anti-virus software and check the issue again.
Regards,
Mike Yin
TechNet Community Support

EclipseLink Error looking up external Transaction resource under JNDI name

I want to verify my EJB 3.0 setup for a Java EE project to be deployed on Weblogic 10.3.3 (11gR2) - however when trying to run the JUnit test from eclipse I keep getting the following exception :
Exception [EclipseLink-23004] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.TransactionException
Exception Description: Error obtaining the Transaction Manager
Internal Exception: Exception [EclipseLink-23001] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.TransactionException
Exception Description: Error looking up external Transaction resource under JNDI name [weblogic.transaction.TransactionManager]
Internal Exception: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
     at org.eclipse.persistence.exceptions.TransactionException.errorObtainingTransactionManager(TransactionException.java:125)
     at org.eclipse.persistence.transaction.JTATransactionController.<init>(JTATransactionController.java:69)
     at org.eclipse.persistence.transaction.wls.WebLogicTransactionController.<init>(WebLogicTransactionController.java:27)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at java.lang.Class.newInstance0(Class.java:355)
     at java.lang.Class.newInstance(Class.java:308)
     at org.eclipse.persistence.internal.security.PrivilegedAccessHelper.newInstanceFromClass(PrivilegedAccessHelper.java:354)
     at org.eclipse.persistence.platform.server.ServerPlatformBase.initializeExternalTransactionController(ServerPlatformBase.java:247)
     at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.preConnectDatasource(DatabaseSessionImpl.java:656)
     at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:581)
     at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:228)
     at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:369)
     at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:151)
     at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:207)
     at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:195)
     at com.junit.ejb.orclperf.EjbValidation.setUp(EjbValidation.java:27)
     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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
     at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
     at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
     at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
     at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
     at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73)
     at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
     at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
     at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
     at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
     at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
     at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
     at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
     at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46)
     at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: Exception [EclipseLink-23001] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.TransactionException
Exception Description: Error looking up external Transaction resource under JNDI name [weblogic.transaction.TransactionManager]
Internal Exception: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
     at org.eclipse.persistence.exceptions.TransactionException.jndiLookupException(TransactionException.java:47)
     at org.eclipse.persistence.transaction.AbstractTransactionController.jndiLookup(AbstractTransactionController.java:434)
     at org.eclipse.persistence.transaction.wls.WebLogicTransactionController.acquireTransactionManager(WebLogicTransactionController.java:35)
     at org.eclipse.persistence.transaction.JTATransactionController.<init>(JTATransactionController.java:67)
     ... 40 more
Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at org.eclipse.persistence.transaction.AbstractTransactionController.jndiLookup(AbstractTransactionController.java:432)
     ... 42 more
[EL Finest]: 2010-05-23 21:29:36.629--ServerSession(30149247)--Thread(Thread[main,5,main])--End deploying Persistence Unit PERFEJB; session file:/C:/Users/owner/workspace/PERFEJB/build/classes/_PERFEJB; state Deployed; factoryCount 2The code for the JUnit test is the following:
package com.junit.ejb.orclperf;
import static org.junit.Assert.*;
import java.util.Calendar;
import java.util.Date;
import javax.persistence.EntityManager;
import javax.persistence.EntityManagerFactory;
import javax.persistence.Persistence;
import javax.persistence.Query;
import org.junit.Before;
import org.junit.Test;
import eJBgetSet.Attachment;
import eJBgetSet.Request;
public class EjbValidation {
     private static final String PERSISTENCE_UNIT_NAME="PERFEJB";
     private EntityManagerFactory factory;
     @Before
     public void setUp() throws Exception {
          factory = Persistence.createEntityManagerFactory(PERSISTENCE_UNIT_NAME);
          EntityManager em = factory.createEntityManager();
          em.getTransaction().begin();
          Query q = em.createQuery("select r from Request r");
          Calendar c = Calendar.getInstance();
          c.add(Calendar.DAY_OF_MONTH,5);
          Date dnow = c.getTime();
          String[] type= {"Databank","SQL File","Script","Scenario Recording","Other"};
          byte[] junitattachment = (byte[])"abcdefghijklmnopqrstuvwxyz".getBytes();
          boolean createNewEntries = (q.getResultList().size()==0);
          if(createNewEntries){
               assertTrue(q.getResultList().size() == 0);
               Request request = new Request();
               request.setRequestid(0);
               request.setReqdescription("JUnit Testing record addition with JPA");
               request.setReqjustification("Validate EclipseLink/WebLogic/EJB 3.0 setup for this project");
               request.setProjectreference("Development Task Performance Analysis 1");
               request.setReqresultdate(dnow);
               request.setReqstatus(0);
               em.persist(request);
               int x=0;
               for(int i=0; i<10;i++){
                    Attachment attachment = new Attachment();
                    attachment.setAttachmentid(i);
                    attachment.setAttachname("File"+i);
                    attachment.setAttachdate(c.getTime());
                    if(i==5){
                         x=0;
                    }else{
                         x++;
                    attachment.setAttachtype(type[x]);
                    attachment.setAttachuser("User"+i);
                    attachment.setAttachsize(String.valueOf(junitattachment.length));
                    attachment.setAttachfile(junitattachment);
                    em.persist(attachment);
                    request.getPerfAttachments().add(attachment);
                    em.persist(attachment);
                    em.persist(request);
               em.getTransaction().commit();
               em.close();
     @Test
     public void testFindAll() {
          EntityManager em = factory.createEntityManager();
          Query q = em.createQuery("select a from perf_attachment a");
          assertTrue(q.getResultList().size() == 10);
          em.close();
     @Test
     public void testSave() {
          EntityManager em = factory.createEntityManager();
          Query q = em.createQuery("select r from req_perf_header");
          assertTrue(q.getResultList().size() == 1);
          assertTrue(((Request) q.getResultList()).getPerfAttachments().size() ==10);
          em.close();
}Finally the persistence.xml file being used is the following:
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
     xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
     <persistence-unit name="PERFEJB" transaction-type="JTA">
          <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
          <jta-data-source>jdbc/ORCLPERF</jta-data-source>
          <class>eJBgetSet.User</class>
          <class>eJBgetSet.Transaction</class>
          <class>eJBgetSet.Request</class>
          <class>eJBgetSet.PerfStatus</class>
          <class>eJBgetSet.Attachment</class>
          <class>eJBgetSet.Approver</class>
          <properties>
               <property name="eclipselink.target-server" value="WebLogic_10" />
               <property name="eclipselink.logging.level" value="FINEST" />
               <property name="eclipselink.jdbc.driver" value="oracle.jdbc.OracleDriver" />
               <property name="eclipselink.jdbc.platform"
                    value=" org.eclipse.persistence.platform.database.oracle.OraclePlatform " />
               <property name="eclipselink.jdbc.url"
                    value="jdbc:oracle:thin:@localhost:1521:orcl11g:create=true" />
               <property name="eclipselink.jdbc.user" value="<username>" />
               <property name="eclipselink.jdbc.password" value="<password>" />
               <property name="eclipselink.logging.level" value="ALL" />
               <property name="eclipselink.logging.timestamp" value="true" />
               <property name="eclipselink.logging.exceptions" value="true" />
               <property name="eclipselink.logging.session" value="true" />
               <property name="eclipselink.ddl-generation" value="drop-and-create-tables" />
               <property name="eclipselink.ddl-generation.output-mode"
                    value="database" />
          </properties>
     </persistence-unit>
</persistence>Any help would be much appreciated. Many Thanks

You have it set to run on the WebLogic platform so it is looking up the TransactionManager from JNDI, but are running the test from within the EclipseIDE. Try deploying it to Weblogic and running it there, or change your persistence.xml settings so that it can connect/run outside the server.
Best Regards,
Chris

How to upload error records in call transaction method

Hi all,
While uploading data by using call transaction. If any errors occured, how can we process that error records to database.
If all records are processed. How can we display the recent records which where uploaded.
AdvanceThanks for all.

Hi Bharath
You can handle this in many ways. But the easiest option to do is as below,
once the call transaction ends in error, move that particular upload data to a separate internal table. Then finally download all these data to an error file.
Besides this after processing all the records diplay the log for error. So that users can modify the error in the file and can use the same for uploading again. For the data that has been processed successfully you can display the log similarly.
The error as well as sucess messages can be obtained from the messages table.
    CALL TRANSACTION TCODE USING BDCDATA
                     MODE   CTUMODE
                     UPDATE CUPDATE
                     MESSAGES INTO MESSTAB.
Regards
Kathirvel

Error (-1200) DBMCconnBase; End Transaction- Error -1 detected, auto rollba

Similar Messages

Maybe you are looking for