After PDK Update J2EE will not start

Question

Hello,
I have just updated the .Net Runtime on our portal to version 2.5 The system was working fine but after I restarted the portal it will not come back up again. The developer trace is show below.
Does anyone have any ideas? Not sure if the .Net Runtime has anything to do with it!
trc file: "C:\usr\sap\EPZ\JC00\work\dev_server0", trc level: 1, release: "640"
node name   : ID2349050
pid         : 4016
system name : EPZ
system nr.  : 00
started at  : Fri Sep 01 10:02:51 2006
arguments   :
    arg[00] : C:\usr\sap\EPZ\JC00/j2ee/os_libs/jlaunch.exe
    arg[01] : pf=C:\usr\sap\EPZ\SYS\profile\EPZ_JC00_ability
    arg[02] : -DSAPINFO=EPZ_00_server
    arg[03] : pf=C:\usr\sap\EPZ\SYS\profile\EPZ_JC00_ability
[Thr 3988] Fri Sep 01 10:02:51 2006
[Thr 3988] INFO: Unknown property [box.number=EPZJC00ability]
[Thr 3988] INFO: Unknown property [ms.host=ability]
[Thr 3988] INFO: Unknown property [ms.port=3601]
[Thr 3988] INFO: Unknown property [system.id=0]
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\EPZ\JC00\j2ee\cluster\instance.properties]
-> ms host    : ability
-> ms port    : 3601
-> OS libs    : C:\usr\sap\EPZ\JC00\j2ee\os_libs
-> Admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : C:\usr\sap\EPZ\JC00\j2ee\cluster\instance.properties
Instance properties
-> ms host    : ability
-> ms port    : 3601
-> os libs    : C:\usr\sap\EPZ\JC00\j2ee\os_libs
-> admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : C:\usr\sap\EPZ\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID2349000  : C:\usr\sap\EPZ\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID2349050  : C:\usr\sap\EPZ\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID2349000            : C:\usr\sap\EPZ\JC00\j2ee\cluster\instance.properties
-> [01] ID2349050            : C:\usr\sap\EPZ\JC00\j2ee\cluster\instance.properties
[Thr 3988] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 3988] JLaunchRequestQueueInit: create pipe listener thread
[Thr 4928] JLaunchRequestFunc: Thread 4928 started as listener thread for np messages.
[Thr 5604] WaitSyncSemThread: Thread 5604 started as semaphore monitor thread.
[Thr 3988] NiInit2: NI already initialized; param 'maxHandles' ignored
[Thr 3988] INFO: Unknown property [JLaunchParameters=]
[Thr 3988] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx512M [jstartxx.c   2313]
[Thr 3988] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [ID2349050]
-> node name       : server0
-> node type       : server
-> node execute    : yes
-> java path       : C:\j2sdk1.4.2_08
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -XX:MaxNewSize=85M -XX:NewSize=85M -XX:DisableExplicitGC -XX:MaxPermSize=192M -XX:PermSize=192M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Xbootclasspath/p:C:/usr/sap/ccms/wily/connectors/connector.jar;C:/usr/sap/ccms/wily/Agent.jar  -Dcom.wily.introscope.agentProfile=C:/usr/sap/ccms/wily/sap_IntroscopeAgent.profile  -Dcom.wily.introscope.agent.agentName=EPZ_EP_ID002349050 -Drdbms.driverLocation=C:/usr/sap/EPZ/JC00/j2ee/jdbc/base.jar:C:/usr/sap/EPZ/JC00/j2ee/jdbc/util.jar:C:/usr/sap/EPZ/JC00/j2ee/jdbc/sqlserver.jar:C:/usr/s
ap/EPZ/JC00/j2ee/jdbc/spy.jar -Dsys.global.dir=C:/usr/sap/EPZ/SYS/global/ -XX:+JavaMonitorsInStackTrace
-> java vm version : 1.4.2_08-b03
-> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 512M
-> init heap size  : 512M
-> root path       : C:\usr\sap\EPZ\JC00\j2ee\cluster\server0
-> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path    : C:\usr\sap\EPZ\JC00\j2ee\os_libs
-> main class      : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path  : C:\usr\sap\EPZ\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class  : com.sap.engine.boot.Start
-> parameters      :
-> debuggable      : no
-> debug mode      : no
-> debug port      : 50021
-> shutdown timeout: 120000
[Thr 3988] JLaunchISetDebugMode: set debug mode [no]
[Thr 2632] JLaunchIStartFunc: Thread 2632 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 262144 Bytes
-> arg[  0]: exit
-> arg[  1]: abort
-> arg[  2]: -Djava.security.policy=./java.policy
-> arg[  3]: -Djava.security.egd=file:/dev/urandom
-> arg[  4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[  5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[  6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[  7]: -Djco.jarm=1
-> arg[  8]: -Dsun.io.useCanonCaches=false
-> arg[  9]: -Djava.awt.headless=true
-> arg[ 10]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 11]: -verbose:gc
-> arg[ 12]: -XX:+PrintGCDetails
-> arg[ 13]: -XX:+PrintGCTimeStamps
-> arg[ 14]: -XX:+UseParNewGC
-> arg[ 15]: -XX:MaxNewSize=85M
-> arg[ 16]: -XX:NewSize=85M
-> arg[ 17]: -XX:+DisableExplicitGC
-> arg[ 18]: -XX:MaxPermSize=192M
-> arg[ 19]: -XX:PermSize=192M
-> arg[ 20]: -XX:SurvivorRatio=2
-> arg[ 21]: -XX:TargetSurvivorRatio=90
-> arg[ 22]: -Xbootclasspath/p:C:/usr/sap/ccms/wily/connectors/connector.jar;C:/usr/sap/ccms/wily/Agent.jar
-> arg[ 23]: -Dcom.wily.introscope.agentProfile=C:/usr/sap/ccms/wily/sap_IntroscopeAgent.profile
-> arg[ 24]: -Dcom.wily.introscope.agent.agentName=EPZ_EP_ID002349050
-> arg[ 25]: -Drdbms.driverLocation=C:/usr/sap/EPZ/JC00/j2ee/jdbc/base.jar:C:/usr/sap/EPZ/JC00/j2ee/jdbc/util.jar:C:/usr/sap/EPZ/JC00/j2ee/jdbc/sqlserver.jar:C:/usr/sap/EPZ/JC00/j2ee/jdbc/spy.jar
-> arg[ 26]: -Dsys.global.dir=C:/usr/sap/EPZ/SYS/global/
-> arg[ 27]: -XX:+JavaMonitorsInStackTrace
-> arg[ 28]: -Dsys.global.dir=C:\usr\sap\EPZ\SYS\global
-> arg[ 29]: -Dapplication.home=C:\usr\sap\EPZ\JC00\j2ee\os_libs
-> arg[ 30]: -Djava.class.path=C:\usr\sap\EPZ\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 31]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\EPZ\JC00\j2ee\os_libs;C:\usr\sap\Python\.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN\;C:\j2sdk1.4.2_08\bin;C:\usr\sap\EPZ\JC00\exe;C:\usr\sap\EPZ\SYS\exe\run
-> arg[ 32]: -Dmemory.manager=512M
-> arg[ 33]: -Xmx512M
-> arg[ 34]: -Xms512M
-> arg[ 35]: -DLoadBalanceRestricted=no
-> arg[ 36]: -Djstartup.mode=JCONTROL
-> arg[ 37]: -Djstartup.ownProcessId=4016
-> arg[ 38]: -Djstartup.ownHardwareId=O0250832349
-> arg[ 39]: -Djstartup.whoami=server
-> arg[ 40]: -Djstartup.debuggable=no
-> arg[ 41]: -DSAPINFO=EPZ_00_server
-> arg[ 42]: -DSAPSTARTUP=1
-> arg[ 43]: -DSAPSYSTEM=00
-> arg[ 44]: -DSAPSYSTEMNAME=EPZ
-> arg[ 45]: -DSAPMYNAME=ability_EPZ_00
-> arg[ 46]: -DSAPDBHOST=
-> arg[ 47]: -Dj2ee.dbhost=ability
[Thr 2632] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 5048] Fri Sep 01 10:03:04 2006
[Thr 5048] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 5048] JLaunchISetClusterId: set cluster id 2349050
[Thr 5048] Fri Sep 01 10:03:06 2006
[Thr 5048] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 5048] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 5896] Fri Sep 01 10:03:37 2006
[Thr 5896] JLaunchIExitJava: exit hook is called (rc=-11113)
[Thr 5896] JLaunchCloseProgram: good bye (exitcode=-11113)

Answer 1

Welcome to Apple Discussions!
Boot off the operating system disk that installed your operating system, and go to the Utilities menu of the installer program and select Disk Utility. Attempt to select the hard drive, and click on Repair Permissions.
Quit from Disk Utility, and Quit from the Installer. If your Mac doesn't start, the only way would be to recover from backup, or go through a more arduous data recover, duplicate the recovered data, erase and install, and recover your recovered data. Let us know which process you need to follow.