Java VM terminated with a non-zero exit code

hi all,
the java process dies down after startup. analyzing the logs, the jvm_bootstrap contains the following text:
Bootstrap MODE:
<INSTANCE GLOBALS>
determined by parameter [ID0034352].
Exception occurred:
com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
     at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:476)
     at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
     at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
     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:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
==[ Caused by: ]==----
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
     at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
     at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
     at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
     at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:74)
     at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:473)
     at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
     at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
     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:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: java.sql.SQLException: ORA-28000: the account is locked
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)
     at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:790)
     at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:362)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)
     at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
     at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)
     ... 14 more
[Bootstrap module]> Problem occurred while performing synchronization.
checking the database log, i found the ORA-01017 and subsequent ORA-28000 errors. the log reads as follows:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/system/database.log]/>
<!PATTERN[database.log]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[0, 5, 10485760]/>
<!PREVIOUSFILE[database.4.log]/>
<!NEXTFILE[database.1.log]/>
<!LOGHEADER[END]/>
#1.5 #001E0B45D0F6004600000197000037F600045C9F24E45E5A#1227738495312#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory####n/a##1d2e0e50a92311dda473001e0b45d0f6#SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#1017#72000#ORA-01017: invalid username/password; logon denied
#jdbc:oracle:thin:@nakeqas1:1527:EQA#<null>#
#1.5 #001E0B45D0F6004600000199000037F600045C9F2505B6B6#1227738497528#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory####n/a##1d2e0e50a92311dda473001e0b45d0f6#SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#1017#72000#ORA-01017: invalid username/password; logon denied
#jdbc:oracle:thin:@nakeqas1:1527:EQA#<null>#
#1.5 #001E0B45D0F600460000019B000037F600045C9F25269BAC#1227738499684#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory####n/a##1d2e0e50a92311dda473001e0b45d0f6#SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#1017#72000#ORA-01017: invalid username/password; logon denied
#jdbc:oracle:thin:@nakeqas1:1527:EQA#<null>#
#1.5 #001E0B45D0F600460000019D000037F600045C9F2547B441#1227738501853#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory####n/a##1d2e0e50a92311dda473001e0b45d0f6#SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#1017#72000#ORA-01017: invalid username/password; logon denied
#jdbc:oracle:thin:@nakeqas1:1527:EQA#<null>#
#1.5 #001E0B45D0F600460000019F000037F600045C9F2568BE7C#1227738504018#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory####n/a##1d2e0e50a92311dda473001e0b45d0f6#SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#1017#72000#ORA-01017: invalid username/password; logon denied
#jdbc:oracle:thin:@nakeqas1:1527:EQA#<null>#
#1.5 #001E0B45D0F60046000001A1000037F600045C9F2589BEDD#1227738506181#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory####n/a##1d2e0e50a92311dda473001e0b45d0f6#SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#1017#72000#ORA-01017: invalid username/password; logon denied
#jdbc:oracle:thin:@nakeqas1:1527:EQA#<null>#
#1.5 #001E0B45D0F60046000001A3000037F600045C9F25AAA2B5#1227738508336#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory####n/a##1d2e0e50a92311dda473001e0b45d0f6#SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#1017#72000#ORA-01017: invalid username/password; logon denied
#jdbc:oracle:thin:@nakeqas1:1527:EQA#<null>#
#1.5 #001E0B45D0F60046000001A5000037F600045C9F25CB6176#1227738510482#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory####n/a##1d2e0e50a92311dda473001e0b45d0f6#SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#1017#72000#ORA-01017: invalid username/password; logon denied
#jdbc:oracle:thin:@nakeqas1:1527:EQA#<null>#
#1.5 #001E0B45D0F60046000001A7000037F600045C9F25EC3271#1227738512633#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory####n/a##1d2e0e50a92311dda473001e0b45d0f6#SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#1017#72000#ORA-01017: invalid username/password; logon denied
#jdbc:oracle:thin:@nakeqas1:1527:EQA#<null>#
#1.5 #001E0B45D0F60046000001A9000037F600045C9F260D07AE#1227738514785#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory####n/a##1d2e0e50a92311dda473001e0b45d0f6#SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#1017#72000#ORA-01017: invalid username/password; logon denied
#jdbc:oracle:thin:@nakeqas1:1527:EQA#<null>#
#1.5 #001E0B45D0F60046000001AB000037F600045C9F262E03A2#1227738516946#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory####n/a##1d2e0e50a92311dda473001e0b45d0f6#SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#28000#99999#ORA-28000: the account is locked
exactly which user is the system pointing to as locked? can this be the cause of the java process dying down? the R3trans -d check returns 0000 and database connection is normal.
ur help is greatly appreciated.
regards,
Amer

hi raghu,
thanx for your replies.
i found that the user for java instance "SAPSR3DB" was locked and unlocked the user account. additionally, i also tried connecting to the database with this user and got connected successfully.
tried restarting the instance again but no success.
the jvm_bootstrap.out file still shows ORA-01017: invalid username/password - logon denied.
any suggestions?
kind regards,
Amer

Similar Messages

*** ERROR = The Java VM terminated with a non-zero exit code.

DEAR MASTERS
          after configuring SLD on integerated ABAP+JAVA   server0 not starting
trc file: "D:\usr\sap\W55\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
node name   : ID9278150
pid         : 4140
system name : W55
system nr. : 00
started at : Sat Mar 21 08:45:23 2009
arguments       :
       arg[00] : D:\usr\sap\W55\DVEBMGS00\exe\jlaunch.exe
       arg[01] : pf=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
       arg[02] : -DSAPINFO=W55_00_server
       arg[03] : pf=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
       arg[04] : -DSAPSTART=1
       arg[05] : -DCONNECT_PORT=1060
       arg[06] : -DSAPSYSTEM=00
       arg[07] : -DSAPSYSTEMNAME=W55
       arg[08] : -DSAPMYNAME=wipro5_W55_00
       arg[09] : -DSAPPROFILE=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
       arg[10] : -DFRFC_FALLBACK=ON
       arg[11] : -DFRFC_FALLBACK_HOST=localhost
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 4668] Sat Mar 21 08:58:30 2009
[Thr 4668] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 4668] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 4668] JLaunchISetClusterId: set cluster id 9278150
[Thr 4668] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 4668] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 4428] Sat Mar 21 08:59:58 2009
[Thr 4428] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 4428] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
[Thr 4616] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 4616] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.

Hi,
Please find the link below for J2EE start up problem.
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e09e4a5e-8280-2a10-ca98-a59dd47d396d]
Please refer to following note for VM settings.
[https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=723909]
Please also check the license validity on this server.
Hope this helps.
Manoj Chintawar

Java VM terminated with a non-zero exit code (rc = -337)

Hi,
It seems that our portal (7.0) was unavailable for five minutes (all users experienced problems which after a few minutes solved itself). We had a look at the logs, and dev_server0 shows that the server node did shut down and start again:
[Thr 6688] Wed Aug 13 10:19:36 2014
[Thr 6688] JLaunchIExitJava: exit hook is called (rc = -337)
[Thr 6688] **********************************************************************
[Thr 6688] *** ERROR => The Java VM terminated with a non-zero exit code.
[Thr 6688] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
[Thr 6688] *** for additional information and trouble shooting.
[Thr 6688] **********************************************************************
[Thr 6688] JLaunchCloseProgram: good bye (exitcode = -337)
The referenced note doesn't offer much help. I've tried to find more info about rc -337, and the only info I've found is that rc -337 is: "Exiting listener loop - restart the node (MSLib)."
Do you guys know what exiting listener loop means, or what the rc -377 is?
Thanks!
M.

Hi Moye,
Hope you are doing good.
Such issues can also be caused due to a network failure. Can you check the below notes along with the network administrator to ascertain that there are no network related issues presently:
#124562     Hostname resolution problems (DNS timeouts)
#500235     Network Diagnosis with NIPING
#413330     Network timeout
If you run the niping tool at the time the issue occurred, it should check the whole network and report the error.
It is also possible to optimize the j2ee server in the manner it interacts with the message server for better performance. As Divyanshu mentioned, the note 1658385 - J2EE System fails with "exitcode = -334" explains, you need to optimize the manner in which the message server reconnects with the Java instances.
This can happen sometimes if you have quite a few nodes in cluster. To make sure the issue does not happen again, you need to increase for each server node the timeout it waits for the confirmation,
that is the value of 'ms.confirmation.timeout' property of ClusterManager along with the other parameters mentioned in the note. Also add the below parameters to the SCS instance file:
<sid>_SCS01_<host> in folder /usr/sap/<sid>/SYS/profile
ms/max_clients = 600
ms/max_open_requests = 2000
ms/audit=1
and
jstartup/keep_old_logfiles=3
The latter 2 parameters will prevent overwritting log files in case of restart. Once the values are increased, the time for the timeout should increase enabling the server to connect to the message server.
Thank you!
Kind Regards,
Hemanth
SAP AGS

The Java VM terminated with a non-zero exit code.

Hi,expert,
I have got this error when I am trying to restart the sap Instance use
command STARTSAP,
The error log as below:
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 940893 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
trc file: "/usr/sap/J2E/JC00/work/dev_jcontrol", trc level: 1,
release: "640"
ERROR => can't retrieve client list (rc=24) [jcntrms_mt.c960]
May 21, 2010 12:53:14... com.sap.engine.core.Framework [SAP
J2EE Engi
ne|MS Socket Listener] Fatal: Critical shutdown was invoked. Reason is:
Exiting
Listener Loop. This requires a restart of the node. Possible reason is
an interr
upted reconnect session to the message server.
Thanks and Best regards,
Michael

Hi Michael,
I am also facing the same issue, can you please let me know where to find the ms.hostname and enqu.hostname...It's very urgent.
Thanks in advance..
Regards,
Krishna.M

Java VM terminated with a non-zero exit code (-337)

We are running a J2EE application on NW7.0 and IBM i5 V5R4.
The application server restarts itself after the server0 proces terminates with the following messages in the dev_server0.log
[Thr 2057] Sat Jun 20 09:34:12 2009
[Thr 2057] JLaunchIExitJava: exit hook is called (rc = -337)
[Thr 2057]
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 2057] SigISetIgnoreAction : SIG_IGN for signal 20
[Thr 2057] JLaunchCloseProgram: good bye (exitcode = -337)
The mentioned Sapnote 943602 refers to Note 940893, which suggest to send the logfiles to Support (which we did).
But can anyone shed a light on this? What can we learn from the mentioned exit codes?
Thanks
Anita

Hi Sunny,
Here's the last part of the dev_server0 log:
Sat Jun 20 09:17:38 2009
GC 12352: live objects 6177736; collected objects 7188118; collected(KB) 775717.
GC 12352: queued for finalization 0; total soft references 8982; cleared soft references 0.
GC 12352: current heap(KB) 2416964; current threshold(KB) 786432.
GC 12352: collect (milliseconds) 3423.
GC 12352: current cycle allocation(KB) 317872; previous cycle allocation(KB) 786457.
GC 12352: total weak references 15151; cleared weak references 0.
GC 12352: total final references 11901; cleared final references 7466.
GC 12352: total phantom references 0; cleared phantom references 0.
GC 12352: total JNI global weak references 0; cleared JNI global weak references 0.
GC 12352: collection ending 20/06/09 09:17:38
Sat Jun 20 09:17:41 2009
GC 12353: starting collection, threshold allocation reached.
GC 12353: collection starting 20/06/09 09:17:41
Sat Jun 20 09:17:44 2009
GC 12353: live objects 6220831; collected objects 7043383; collected(KB) 785764.
GC 12353: queued for finalization 0; total soft references 8974; cleared soft references 0.
GC 12353: current heap(KB) 2415944; current threshold(KB) 786432.
GC 12353: collect (milliseconds) 3003.
GC 12353: current cycle allocation(KB) 294375; previous cycle allocation(KB) 786464.
GC 12353: total weak references 15151; cleared weak references 0.
GC 12353: total final references 10853; cleared final references 6411.
GC 12353: total phantom references 0; cleared phantom references 0.
GC 12353: total JNI global weak references 0; cleared JNI global weak references 0.
GC 12353: collection ending 20/06/09 09:17:44
Sat Jun 20 09:17:47 2009
GC 12354: starting collection, threshold allocation reached.
GC 12354: collection starting 20/06/09 09:17:47
Sat Jun 20 09:17:54 2009
GC 12355: starting collection, threshold allocation reached.
Sat Jun 20 09:18:23 2009
GC 12355: starting collection, threshold allocation reached.
Sat Jun 20 09:20:10 2009
GC 12355: starting collection, threshold allocation reached.
Sat Jun 20 09:20:23 2009
GC 12355: starting collection, threshold allocation reached.
Sat Jun 20 09:20:30 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:31 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:32 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:34 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:35 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:36 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:38 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:39 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:45 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:46 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:50 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:20:58 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:21:00 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:21:21 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:21:50 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:22:40 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:22:42 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:22:50 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:24:46 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:24:47 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:24:50 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:25:06 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:25:51 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:27:04 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:28:28 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:28:42 2009
GC 12355: starting collection, maximum allocation reached.
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:29:19 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:30:46 2009
GC 12355: starting collection, maximum allocation reached.
Sat Jun 20 09:31:08 2009
GC 12354: live objects 6994240; collected objects 6961336; collected(KB) 789682.
GC 12354: queued for finalization 0; total soft references 8976; cleared soft references 3.
GC 12354: current heap(KB) 4194292; current threshold(KB) 786432.
GC 12354: collect (milliseconds) 801210.
GC 12354: current cycle allocation(KB) 0; previous cycle allocation(KB) 4242195.
GC 12354: total weak references 15151; cleared weak references 0.
GC 12354: total final references 10905; cleared final references 6451.
GC 12354: total phantom references 0; cleared phantom references 0.
GC 12354: total JNI global weak references 0; cleared JNI global weak references 0.
GC 12354: collection ending 20/06/09 09:31:08
GC 12355: collection starting 20/06/09 09:31:08
Sat Jun 20 09:31:18 2009
GC 12356: starting collection, maximum allocation reached.
Sat Jun 20 09:32:38 2009
GC 12356: starting collection, maximum allocation reached.
Sat Jun 20 09:33:48 2009
GC 12355: collected class sun/reflect/GeneratedMethodAccessor3620979168.
Sat Jun 20 09:33:59 2009
GC 12355: live objects 6717156; collected objects 29066552; collected(KB) 3256489.
GC 12355: queued for finalization 0; total soft references 8973; cleared soft references 89.
GC 12355: current heap(KB) 4193652; current threshold(KB) 786432.
GC 12355: collect (milliseconds) 170434.
GC 12355: current cycle allocation(KB) 75; previous cycle allocation(KB) 0.
GC 12355: total weak references 15164; cleared weak references 0.
GC 12355: total final references 32619; cleared final references 28210.
GC 12355: total phantom references 0; cleared phantom references 0.
GC 12355: total JNI global weak references 0; cleared JNI global weak references 0.
GC 12355: collection ending 20/06/09 09:33:59
GC 12356: collection starting 20/06/09 09:33:59
Sat Jun 20 09:34:01 2009
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor746382538.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor3780712466.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor168496322.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor980237086.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1886738503.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1251676621.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1433437257.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1328663959.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor3914321935.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor333360639.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor3292847473.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor752085389.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor416310187.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor3620979168.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor2138604126.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor2058455930.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor599442064.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor853421746.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1143931263.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor379179616.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1925696964.
GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor57815531.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor843740711.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor2093346596.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor1446511408.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor1446703216.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor1522492322.
Sat Jun 20 09:34:02 2009
GC 12356: collected class sun/reflect/GeneratedMethodAccessor1786850049.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor515968301.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor1786794657.
GC 12356: collected class sun/reflect/GeneratedMethodAccessor516161133.
GC 12356: collected class sun/reflect/GeneratedConstructorAccessor2753180717.
GC 12356: live objects 4366863; collected objects 2655706; collected(KB) 255573.
GC 12356: queued for finalization 0; total soft references 8976; cleared soft references 0.
GC 12356: current heap(KB) 3147644; current threshold(KB) 786432.
GC 12356: collect (milliseconds) 3478.
GC 12356: current cycle allocation(KB) 25809; previous cycle allocation(KB) 0.
GC 12356: total weak references 15164; cleared weak references 0.
GC 12356: total final references 4422; cleared final references 11.
GC 12356: total phantom references 0; cleared phantom references 0.
GC 12356: total JNI global weak references 0; cleared JNI global weak references 0.
GC 12356: collection ending 20/06/09 09:34:02
[Thr 2057] Sat Jun 20 09:34:12 2009
[Thr 2057] JLaunchIExitJava: exit hook is called (rc = -337)
[Thr 2057] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 2057] SigISetIgnoreAction : SIG_IGN for signal 20
[Thr 2057] JLaunchCloseProgram: good bye (exitcode = -337)
trc file: "/usr/sap/P01/DVEBMGS01/work/dev_server0", trc level: 1, release: "700"

The Java VM terminated with a non-zero exit code.(rc = -11113)

Hi All,
We are having ABAP + JAVA stack but server0 process is not coming up.
Please find the below logs.
...xt.<init>(UserContextSpi, Properties) [Session Reader for cluster node 9680100] Fatal: Can not instantiate UserContext with given properties.
service security ================= ERROR =================
Core service security failed. J2EE Engine cannot be started.
com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
     at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
     at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
     at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
     at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
     at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
     at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
     ... 5 more
com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
     at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
     at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
     at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
     at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
     at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
     at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
     ... 5 more
Please help me out asap.
Thanks

I have checked and found this also
ION    CPIC (TCP/IP) on local host with Unicode
ERROR       service 'sapgw000' unknown
TIME        Thu Apr 03 11:37:43 200
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -3
MODULE      ninti.c
LINE        530
DETAIL      NiPGetServByName2: service 'sapgw000' not found
SYSTEM CALL getservbyname_r
COUNTER     1
passwd=********
receiverid=master
sysnr=$$
client=001
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=localhost
poolmaxwait=10000
#1.5#001D0904A999001D0000000200001EE4000449F1D1D4C30F#1207202863171#/System/Security/Usermanagement##com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init()#######SAPEngine_System_Thread[impl:5]_66##0#0#Error#1#com.sap.security.core.persistence.datasource.imp.R3PersistenceBase#Java#An exception was thrown in the UME/ABAP user management connector. Message: .##An exception was thrown in the UME/ABAP user management connector. Message: .#1#Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=localhost SYSNR=000 GWHOST=localhost GWSERV=sapgw000 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       service 'sapgw000' unknown
TIME        Thu Apr 03 11:37:43 200
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -3
MODULE      ninti.c
LINE        530
DETAIL      NiPGetServByName2: service 'sapgw000' not found
SYSTEM CALL getservbyname_r
COUNTER     1
#1.5#001D0904A999001D0000000400001EE4000449F1D1D4C611#1207202863171#/System/Security/Usermanagement##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_66##0#0#Error#1#com.sap.security.core.persistence#Java#User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to initialize the ABAP data source: ##User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to initialize the ABAP data source: #1#Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=localhost SYSNR=000 GWHOST=localhost GWSERV=sapgw000 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       service 'sapgw000' unknown
TIME        Thu Apr 03 11:37:43 200
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -3
MODULE      ninti.c
LINE        530
DETAIL      NiPGetServByName2: service 'sapgw000' not found
SYSTEM CALL getservbyname_r
COUNTER     1
#1.5#001D0904A999001D0000000600001EE4000449F1D1D4C775#1207202863171#/System/Security/Usermanagement##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_66##0#0#Fatal#1#com.sap.security.core.persistence#Java#Initialization of UME persistence adapter "" failed.##Initialization of UME persistence adapter "" failed.#1#R3_DATASOURCE#
#1.5#001D0904A999001D0000000900001EE4000449F1D1D4CA16#1207202863171#/System/Security/Usermanagement##com.sap.security.core.server.ume.service.UMEServiceFrame#######SAPEngine_System_Thread[impl:5]_66##0#0#Error#1#com.sap.security.core.server.ume.service.UMEServiceFrame#Plain###UME initialization failed.#

JAVA could not start with NON - zero exit code after Config UME

Dear Expert,
I found some problem with JAVA. We have been success to install for JAVA.
We can logon to that. But since we configuration for UME. We found the problem
with startup JAVA. We can not startup for JAVA. It show for error.
====================================
Error==> The JAVA VM terminated with a non - zero exit code.
Please see SAP note 943602, section 'J2EE Engine exit codes'
for additional information and trouble shooting.
====================================
Critical shutdown was invoked. Reason is Core service security failed.
J2EE Engine can not be started.
====================================
MAC ADDRESS can not be access
====================================
Java framework can not be find .... D:\usr\sap\...\jvm.jsp ==> can not remember
Could you analyze for me ? How to solved for this problem ?
Regards,
Somkeit

Somkeit,
What did you change in UME Configuration?
Please look in defaulttrace_# log and paste error here.
What is exit code ?
Can you revert back your UME changes and see if system starts or no.
Thanks,
Digesh Joshi

Non-zero exit code

Hi experts,
im facing a porblem in starting the j2ee engine,
The error in the developer trace says :
[Thr 4768] Sat Oct 14 13:26:47 2006
[Thr 4768] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 4768] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 4768] JLaunchISetClusterId: set cluster id 318458550
[Thr 4768] Sat Oct 14 13:26:48 2006
[Thr 4768] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 4768] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 4628] Sat Oct 14 13:27:15 2006
[Thr 4628] JLaunchIExitJava: exit hook is called
(rc = -11113)
[Thr 4628] *****************************************************
ERROR => The Java VM terminated with a non-zero exit code.
is any one familiar with this error ?

Hi Ahmed,
Please have a look at <a href="https://service.sap.com/sap/support/notes/940893">SAP Note 940893</a>. In short, rc = -11113 means that some essential service has failed to start. More information could be found in:
\usr\sap\<SID>\<instance>\j2ee\cluster\server<N>\log\system\server.log
\usr\sap\<SID<\<instance>\j2ee\cluster\server<N>\log\defaultTrace.trc
HTH!
-Vladimir

ShellScriptResourceAdapter ignores STDERR and non zero exit codes?

My ShellScript Resource seems to ignore any output to STDERR and also ignores script commands failing with exit codes other than 0.
Let's say I run this in bash:
meh@moo ~$ perl -e 'print(STDERR "Error "); die("foo");' 1>/dev/null
Error foo at -e line 1.
meh@moo ~$ echo $?
255Perl clearly exits with STDERR Output and exit code -1.
Now, if I run this as the "Update User" ResourceAction in IDM 6 SP1, it always tells me everything went fine without any errors.
Running it as "Create User" ResourceAction at least gives me:
Error foo at -e line 1.
null
Result Code = 255
And the CREATE actually fails.
But Update and Delete seem to ignore STDERR and exit codes.
Or am I missing something? It would be great to see any error in IDM when one of the ResourceAction scripts' steps is failing...

Somkeit,
What did you change in UME Configuration?
Please look in defaulttrace_# log and paste error here.
What is exit code ?
Can you revert back your UME changes and see if system starts or no.
Thanks,
Digesh Joshi

Export failing with non zero return code on windows

exp returning non zero return code on windows .
we have some scrips that depends on return code of exp .
There are two tables one is present (test1) and other is not present (test2)
and we are exporting
screen shot --
WITH EXP :-
on windows --
C:\>exp tables= test1,test2
Export: Release 10.2.0.2.0 - Production on Fri Jun 11 13:55:16 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Username: dev
Password:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
About to export specified tables via Conventional Path ...
. . exporting table TEST1 6291456 rows exported
EXP-00011: DEV.TEST2 does not exist
Export terminated successfully with warnings.
C:\>echo %ERRORLEVEL%
3
Edited by: user2015671 on Jun 11, 2010 4:32 AM

no the issue is there.we have problem with non zero return code by exp on windows not on unix .
I had done same on unix it returning zero return code.
Screen shot:-
> exp tables=temp,temp3
Export: Release 10.2.0.1.0 - Production on Fri Jun 11 16:52:48 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Username: dev
Password:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
About to export specified tables via Conventional Path ...
. . exporting table TEMP 3 rows exported
EXP-00011: DEV.TEMP3 does not exist
Export terminated successfully with warnings.
echo $?0
Edited by: user2015671 on Jun 11, 2010 4:59 AM

While creating OpenDirectory replica, I get a "non-zero status code". How do I fix this?

I'm trying to create an OpenDirectory replica with OS X 10.9.2 servers running Server 3.1.1. The server seems to connect to the master momentarily, but ultimately the connection fails. The log file shows:
May 21 11:25:01 inglewoodmirror.local Server[323]: An error occurred while configuring InglewoodMirror as a directory replica:
Error Domain=XSActionErrorDomain Code=69 "Server returned a non-zero status code"
UserInfo=0x608000a73500 {NSLocalizedDescription=Server returned a non-zero status code}
The Apple Discussion titled, "Error occurred creating OD replica" addressed the issue by running Workgroup Manager to backup users, before destroying and recreating the OD. However, that user also botched the master-replica relationship by changing the host name of the master without destroying the replica's first.
I'm hoping that there is a simpler method to solve this issue. It is my understanding that Workgroup Manager is a depricated app, so I am hesitant to use the method recommended by the referenced solution.
What causes this error? How can one attempt to remedy this without destroying the master?

Update
I have been trying to diagnose this by analyzing the network traffic, which has been enlightening, but it suddenly dawned on me that I had not checked the "Logs" section of the Server application. Checking the Log and changing the specific Log to "Configuration Log" in the OpenDirectory section, I see the following:
This error is much more clear than the text described above. It seems that the problem is not network communication, rather it is that the OpenDirectory administrator is not the same as the system administrator. I had thought that the user account was one and the same.
So, now the question becomes.....
How do I determine the userId of the directory administrator?
The password is known. We have a standard password that we use in this company for such things, but the user account is not known. That changes based on the machine which houses the directory. Does anyone have a suggestion?

ZTIERROR: Non-zero return code by ZTIPowershell, rc = 10904

My Scenario:
i have a Windows 2008 R2 server with MDT 6.2.5019.0.
i have 2 deployment shares on this server: Windows 7 x64 Enterprise & Windows 8.1 Enterprise x64
in both my base images (win 7 & win 8.1) i updated to Powershell 4.0
Using task sequence in MDT i try to Run Powershell scripts that i created in "STATE RESTORE">"CUSTOM TASKS" folder using "ADD>GENERAL>RUN POWERSHELL SCRIPT". On the Windows 7 x64 deployment share all my Powershell
scripts- task sequences run fine but for my Windows 8.1 i get the following error:
ZTIERROR: Non-zero return code by ZTIPowershell, rc = 10904
i have no clue whats going on.
here are some steps troubleshooting steps I've taken:
1. updated the deployment share>Completely regenerate the boot images
2. Added computer to workgroup instead of Domain (Prevent any GPO's from affecting)
any help would be appreciated

Also you can add this in CustomSettings.ini (is located in \\<SERVER>\DeploymentShare$\Control):
;Logging
SLShare=\\<SERVER>\DeploymentShare$\Logs
SLShareDynamicLogging =\\<SERVER>\DeploymentShare$\Logs\%ComputerName%
and in appropriate %ComputerName% folder on <SERVER> during OSD will be generated dinamically updated BDD.log. After OSD is finished rest logs will appear in that folder.
You can inspect this with trace32 from System
Center Configuration Manager 2007 Toolkit V2.

Sqlldr non-zero return code

We recently switched from Oracle 7.3.4 to Oracle 8.1.7. The input to a sqlldr has duplicate records which causes unique constraint errors. That's not a problem.
The table updates are going fine on the new machine. I'm just curious as to why the script that was used to execute the sqlldr on Oracle 7.3.4 returned a 0 (zero) return code when there were unique contraint warnings, and the identical script and sqlldr code is returning a 2 return code on 8.1.7.
I'm concerned that the non-zero return code may be pointing to something other than the unique constraint issue, that we're not seeing.
The only discernable difference in the log file between the 7.3.4 version and the 8.1.7 version is the following:
Space allocated for bind array: 2560 bytes(64 rows) (old machine)
Space allocated for memory besides bind array: 55256 bytes
Space allocated for bind array: 2560 bytes(64 rows) (new machine)
Space allocated for memory besides bind array: 0 bytes
Does the above "Space allocated" statement mean anything?
SQLLDR Code:
OPTIONS (SILENT=(FEEDBACK))
LOAD DATA
INFILE 'IOR_out.csv'
APPEND
INTO TABLE sap_so_mstr
div_ln position(1:4) CHAR,
acct_so_iwo_ln position(7:16) CHAR,
rec_type position(42:43) CHAR,
SAP_CHG_NBR position(46:53) CHAR,
task_ln constant '0000000'
Sample input to SQLLDR (in real life these values are lined up in columns):
27 , 009911AAAA, 19991126, 20991231, C, IO, 9911AAAA
27 , 009912AAAA, 19991126, 20991231, C, IO, 9912AAAA
27 , 0099H2HRCM, 19991126, 20991231, C, IO, 99H2HRCM
Code within the script calling above SQLLDR code:
sqlldr userid=${DB_USER}/${DB_PASSWORD}, control=${ctlfile} errors=100000
Any ideas? Thanks.

Also you can add this in CustomSettings.ini (is located in \\<SERVER>\DeploymentShare$\Control):
;Logging
SLShare=\\<SERVER>\DeploymentShare$\Logs
SLShareDynamicLogging =\\<SERVER>\DeploymentShare$\Logs\%ComputerName%
and in appropriate %ComputerName% folder on <SERVER> during OSD will be generated dinamically updated BDD.log. After OSD is finished rest logs will appear in that folder.
You can inspect this with trace32 from System
Center Configuration Manager 2007 Toolkit V2.

SSIS fails with error : The process exit code was -1073741701

Hello All,
I am having issues with SSIS packages running from SQL agent job.
The server we are running the job is used for SSIS and there are lot of other SSIS jobs that are running.
We were able to run the job once successfully and the later runs are failing with the below error.(nothing has been changed)
The step did not generate any output. The return value was unknown. The process exit code was -1073741701. The step failed.
Nothing is being logged in the [catalog].[operations] or operation_messages view. When tuned the profiler ON we do not see the job trying to connect to SSISDB at all. I am assuming that the job is failing much before if does any thing.
I have moved the package to a different server and ran it with the same proxy account and it works fine there.
Any help or suggestion on this issue would be helpful.
Thanks !

Hi SQL_Help,
You can run the job once successfully and the later runs are failing with the below error ran it as a Job. “The step did not generate any output. The return value was unknown. The process exit code was -1073741701. The step failed.” It
was really a generic error message with no information with it.
We can use Process Monitor and Event Viewer to capture the detail error message. Then based on the error message to fix this issue. The following similar issue is for your reference:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2014/05/22/ssis-package-fails-with-error-the-step-did-not-generate-any-output-the-return-value-was-unknown.aspx
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Export terminated with ORA-00600: internal error code, arguments: [kcfrbd_1

when i am taking an export of a particular table , i got following message. please help
ORA-00600: internal error code, arguments: [kcfrbd_1], [0], [400], [], [], [], [], []
Export terminated successfully with warnings.

with out a versioninfo it's not possible tomgive appropiate information. Anyway, an ORA-00600 is almost certainly a job for the oracle support.
And lastly, the right forum for this question would be a database forum, maybe the Database-General-forum.

Java VM terminated with a non-zero exit code

Similar Messages

Maybe you are looking for