Runtime Error in PSE 9 Editor

When I attempt to access the editor in PSE9 either directly or from the organizer I get the following message:
"Runtime Error!
Program:...s\Adobe\PhotoshopElements9\PhotoshopElementsEditor.exe
This application has requested the Runtime to terminate it in an unusual way."
Uninstalling and reinstalling PSE9 has no effect on this error.

Oh, great...an "unknown" faulting module!
There's not a lot to go on, so I can only offer a couple of general troubleshooting suggestions:
Re-set the Editor's Preferences by holding down your Ctrl+Alt+Shift keys when launching the Editor and keep them held down until you see the prompt asking if you want to delete the Preferences.  Answer "Yes" and they will be re-built.  You may have to minimize any open windows in order to see that prompt.
If you have manually enabled the TWAIN interface for scanning, see this Adobe document:
http://kb2.adobe.com/cps/408/kb408850.html
See this Adobe document for general troubleshooting steps:
http://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
Ken

Similar Messages

  • Microsoft C++runtime error in Adobe Photoshop_10, editor,Windows 7

    Would like to fix this.
    Program opens, when I click on editor, Visual Runtime error occurs, and program will shut down when I closed window or click to cancel.
    I have been coming up with some solutions on the forum but some people have not been successful for other versions & I hve not found the specific one question like mine. Can some one send me the correct link for this fix for my particular stats
    Thank you

    Follow the steps in article:
    http://helpx.adobe.com/photoshop-elements/kb/microsoft-c-runtime-error-launcing.html

  • Runtime error in Elements 9, editor will not work

    I have Windows Vista. The organizer seems to work fine.  But right after a photo opens in editor, a window appears saying:  Microsoft Visual C++,    Runtime Library.  It says Runtime Error!  Program....PhotoshopElementsEditor.exe  This application has requested the Runtime to terminate it in an unusual way.  Please contact the applications support team for more information.
    A couple days ago the computer shut down unexpectedly (my computer has been doing that alot in the last month, there was also a power outage due to a storm).  I tried restarting the computer, closing and restarting Elements, updating Elements (it did not need it) I also tried restoring the system to a restore point where Elements was working fine and that did not work. 
    Would really appreciate any help.  Thanks so much.

    Oh, great...an "unknown" faulting module!
    There's not a lot to go on, so I can only offer a couple of general troubleshooting suggestions:
    Re-set the Editor's Preferences by holding down your Ctrl+Alt+Shift keys when launching the Editor and keep them held down until you see the prompt asking if you want to delete the Preferences.  Answer "Yes" and they will be re-built.  You may have to minimize any open windows in order to see that prompt.
    If you have manually enabled the TWAIN interface for scanning, see this Adobe document:
    http://kb2.adobe.com/cps/408/kb408850.html
    See this Adobe document for general troubleshooting steps:
    http://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
    Ken

  • Runtime Error causes Elements 11 editor to crash

    I've had this happen twice now over the last 10 days. After the first time, I removed the whole program & re-installed from the disc. Its now just happened again and editor will not load & I just get the Runtime Error! notification. As before, I can open Organiser but Editor will not either open directly or from within Organiser.

    Uninstall and reinstall.

  • Receiving runtime error in  PSE 11 on opening program.

    Anyone have an idea what the problem is. PSE (all versions) have run just fine until today.

    Oh, great...an "unknown" faulting module!
    There's not a lot to go on, so I can only offer a couple of general troubleshooting suggestions:
    Re-set the Editor's Preferences by holding down your Ctrl+Alt+Shift keys when launching the Editor and keep them held down until you see the prompt asking if you want to delete the Preferences.  Answer "Yes" and they will be re-built.  You may have to minimize any open windows in order to see that prompt.
    If you have manually enabled the TWAIN interface for scanning, see this Adobe document:
    http://kb2.adobe.com/cps/408/kb408850.html
    See this Adobe document for general troubleshooting steps:
    http://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
    Ken

  • 308 Runtime Error ! in Schema Editor

    Hi Friends,
    I am tring to create a service using schema editor it is showing 308 error and schema editor is closing.how can i resolve that problem,i saw some information regarding this in forums that this problem happen due to previous invalid service
    in the registry, where can i found this registery or anything else i did mistake.Pls help me out.
    thans in advance
    sivaram

    thaks luckys for your reply! i need some information where i get this folder location CISXAI ,i already searched for this .do we need any setup requirements for schema editor ,just installed it directly using setup.exe and i have oracle client in my system.
    HKEY_CURREN_USER\Software\VB and VBA Program Settings\CISXAI\Recents
    HKEY_USERS{Class ID}\Software\VB and VBA Program Settings\CISXAI\Recents
    under key 'G3Service'.
    thanks & regards
    sivaram

  • Java iView Runtime error occurs whilw changing Theme Editor

    Hi,
    i have to face the following error while changing Theme.
    <b>Java iView Runtime
    Version : 6.4.200512140312
    + Copyright 2002 SAP AG. All rights reserved.
    An exception occured while processing your request.
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:284)
         ... 20 more
    Caused by: java.lang.OutOfMemoryError
    If this situation persists, please contact your system administrator.</b>
    Please give me right solution.
    Thanks & Regards,
    Nisarg Patel

    Hi,
         Try out the answers given in the following threads:
    Theme Editor : Runtime error
    Problem with Theme Editor
    Regards,
    Pooja.

  • I loaded actions into my PSE 10, then when I restarted my PC (windows 7) and PSE 10 I got a Runtime Error (Microsoft Visual C    Runtime Library)

    I loaded actions into my PSE 10, then when I restarted my PC (windows 7) and PSE 10 I got a Runtime Error (Microsoft Visual C    Runtime Library)

    Are these actions you put into the C:\ProgramData\Adobe\Photoshop Elements\10.0\Photo Creations\photo effects folder?
    If so, did you delete both the
    ThumbDatabase.db3  in C:\ProgramData\Adobe\Photoshop Elements\10.0
    and
    MediaDatabase.db3 in C:\ProgramData\Adobe\Photoshop Elements\10.0\Locale\en_us
    after installing the actions?
    Then let the pse 10 editor run for about 10 to 20 minutes to rebuild the effects database.

  • I have been getting a "Runtime Error" and can't open Adobe Photoshop Elements Editor

    We are using Adobe Photoshop Elements version 9.0.3 (20110328.m.11320).  For several weeks it has not been possible to open the Editor, although the Organizer opens as usual.  We get an error message that says "Runtime Error! Program: ...\Adobe\Photoshop Elements 9\PhotoshopElementsEditor.exe This application has requested the Runtime to terminate it in an unusual way.  Please contact the application's support team for more information."  What can we do to correct this problem?

    Thanks, Ken!  I have to reply by e-mail, as the Forum site has been down
    for maintenance since last night.
    I am running Windows 7 Professional SP1.
    Uninstalling and booting should be straightforward.  I saved the
    following files in my Downloads folder from my initial installation of
    Adobe PSE 9.0 on 4/22/11:
    Adobe_Photoshop_Elements_9-AkamaiDLM.exe (355 kb application)
    PhotoshopElements_9_LS15.exe (1,200 kb application)
    PhotoshopElements_9_LS15.7z (1,838,546 kb WinRAR archive)
    Will these suffice for reinstalling the program?  Can you tell me how I
    should go about the reinstallation?  (I tried to find a page to download
    the Adobe PSE 9.0 program on the Adobe website, but could only locate a
    patch for 9.0.3, which I think must already have been included in the
    original installation.)
    Also, there are four folders, corresponding to four catalogs, in
    C:\ProgramData\Adobe\Elements Organizer\Catalogs.  Will those survive
    the uninstall/reinstall process?  Should I back them up just prior to
    uninstalling to preserve them for restoration after the reinstall?
    Finally, should I back up the 9.0 and Organizer folders in
    C:\ProgramData\Adobe\Elements Organizer for restoration as well?  And
    the C:\ProgramData\Adobe\Photoshop Elements folder?
    Thank you.  I am grateful for your help!
    Peter

  • Elements 10, Editor runtime error

    I get a runtime error when launching editor in Elements 10.  Just started happening.

    If you are using Windows 7 then the preference file that needs to be renamed is at this location:
    <C:\Users\USERNAME\AppData\Roaming\Adobe\Photoshop Elements\10.0\Editor>
    In the above path, replace USERNAME with your windows profile name  which could be something like jblogetc or whatever.  Also the preference file is called: Adobe Photoshop Elements 10 Prefs.psp and this needs to be renamed to Adobe Photoshop Elements 10 Prefs.old
    Once this done, restart PSE 10 and then see if it works.

  • PSE 7 runtime error

    Hi, I'm trying to resolve an issue with PSE 7 installed on a Secondary School network.
    The program runs fine when logged in to a PC as a local or Domain Administrator but crashes when logged in as a student if you select "edit" from the opening screen ("create" works OK!)
    The error message is "Visual C++ runtime error!" followed by "the exception unknown software exception (0xc000000d) occurred in the application at location 0x78138aa0" if you click Ok on the first message.
    I've already found several references to this error message on the forums and on the web and have followed all the Adobe troubleshooting procedures, knowledge base articles etc. but to no avail - I don't think it's a problem with the program itself so much as with the security settings applied to the PC's for "student" users, who all share the same Mandatory Profile.
    I can modify the Mandatory profile or the local security settings of the PC's within reason, but my real problem is that I can't identify the restriction that's responsible for causing the error message in the first place!
    Any suggestions welcomed!

    Are these actions you put into the C:\ProgramData\Adobe\Photoshop Elements\10.0\Photo Creations\photo effects folder?
    If so, did you delete both the
    ThumbDatabase.db3  in C:\ProgramData\Adobe\Photoshop Elements\10.0
    and
    MediaDatabase.db3 in C:\ProgramData\Adobe\Photoshop Elements\10.0\Locale\en_us
    after installing the actions?
    Then let the pse 10 editor run for about 10 to 20 minutes to rebuild the effects database.

  • PSE 10 Runtime error

    Photoshop Elements 10 working fine but suddenly came up with Runtime error saying the 'application had requested the Runtime to terminate it in an unusual way'. Suggests 'contact the applications support team for more information'. Can anyone help?
    (thread title edited by forum host)

    If you are facing the issue on the editor try to reset the prefernces of the editor.
    To do so, close PSE first if its open and before relaunching
    Hold down the Alt + Ctrl + Shift(Windows) Opt + Cmd + Shift(Mac) keys as you click on the icon to open Elements. When asked if you want to delete the settings file, say yes.
    Reset the preferences as above.
    Close Elements and Relaunch it again.
    Check is the error coming again or not.
    -Harshit yadav

  • Portal runtime error in Theme editor:Urgent

    Hi All,
    I am getting the following error when i am logging as a j2ee_admin user in Theme Editor and
    also when i click on theme transport it is not displaying any contents.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration
    /com.sap.portal.system_admin_ws/com.sap.portal.themes/com.sap.portal.theme_editor/com.sap.portal.styleeditor
    Component Name : null
    Page could not create the iView.
    See the details for the exception ID in the log file.
    the default trace is as below
    "application webdynpro/dispatcher Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: java.lang.NullPointerException: null
    Exception id: [0003BA3630CD0076000005BF00005B3B00044B53786F03CB]
    The iview for theme editor does not exist . any clue how to over come this.
    Thanks & Regards
    santosh

    Hi All,
    Issue is resolved . Deleted one of the standard theme through system admin->support->support desk->theme and restarted the server.
    Regards
    Santosh

  • Runtime Error in  Web Page Composer (WPC) : Page Editor

    Hello,
    We are using the Web page Composer to design our portal homepage. The portal version is 7.02 SP6.
    We created a site, some site content like banners and articles, and a blank web page. When we try to add the site content to the web page from the "Page Editor" by clicking on the pencil icon -> "Add", a runtime error occurs on the Web Content Browser pop up page. The drag and drop feature to add content is not working either.
    The error message is as follows:
    Runtime Error
    An exception occured while processing the request.
    Additional information: null
    Exception ID = 0076b5e1-fea6-2e10-b49e-9e1f27bd085c
    Runtime Error
    An exception occured while processing the request.
    Additional information: null
    Exception ID = 30ebb5e1-fea6-2e10-7d8e-b34b3229cd35
    ANy idea what the problem could be?
    Thanks and Regards,
    Reena

    Hello,
    Below is an extract from the trace file for the exception ID:
    Exception ID = 60843375-7baa-2e10-2097-c764acd6ad4c java.lang.NullPointerException
    at com.sapportals.wcm.portal.component.base.ControllerComponent.prepareRequest(ControllerComponent.java:229)
    at com.sapportals.wcm.portal.component.base.ControllerComponent.getPage(ControllerComponent.java:124)
    at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:114)
    at com.sapportals.wcm.portal.component.base.ControllerComponent.doContent(ControllerComponent.java:83)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
    at java.security.AccessController.doPrivileged(AccessController.java:246)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:434)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(AccessController.java:219)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Any clue?
    Regards,
    Reena

  • Theme Editor : Runtime error

    Hi,
    I am facing some problems with theme editor
    System details:
    - Windows 2000 with SQL server
    - Only Java stack installed
    - EP6 SP7 patch 2
    When I open any theme for editing it does not display the preview; instead gives me an error
    =========================================
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.themes/com.sap.portal.theme_editor/com.sap.portal.styleeditor
    Component Name : com.sap.portal.themes.editor.default
    The exception was logged. Inform your system administrator..
    Exception id: 06:42_18/11/04_0001_4623250
    See the details for the exception ID in the log file
    =======================================
    From this point onwards any other link in theme editor (or else where) starts giving error
    ================================
    Java iView Runtime
    Version : 6.4.200408122048
    + Copyright 2002 SAP AG. All rights reserved.
    An exception occured while processing your request.
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:296)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:339)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:317)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:810)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:276)
         ... 20 more
    Caused by: java.lang.OutOfMemoryError
         at com.ddtek.util.UtilPagedTempBuffer.getBlock(Unknown Source)
         at com.ddtek.util.UtilPagedTempBuffer.write(Unknown Source)
         at com.ddtek.jdbc.sqlserver.tds.TDSRequest.getColumnDataForRow(Unknown Source)
         at com.ddtek.jdbc.sqlserver.SQLServerImplResultSet.getData(Unknown Source)
         at com.ddtek.jdbc.base.BaseResultSet.getClob(Unknown Source)
         at com.sap.sql.jdbc.basic.BasicResultSet.getClob(BasicResultSet.java:432)
         at com.sap.sql.jdbc.direct.DirectResultSet.getClob(DirectResultSet.java:1046)
         at com.sap.sql.jdbc.common.CommonResultSet.createClob(CommonResultSet.java:1160)
         at com.sap.sql.jdbc.common.CommonResultSet.getClob(CommonResultSet.java:314)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.readFirstValue(AttributeHeadersTable.java:773)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.readAttributeHeader(AttributeHeadersTable.java:745)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.selectSubtreeObjectsAttributeHeaders(AttributeHeadersTable.java:913)
         at com.sapportals.portal.pcd.pl.PlFactory.getSubtreeSegment(PlFactory.java:897)
         at com.sapportals.portal.pcd.pl.PlFactory.getSubtree(PlFactory.java:823)
         at com.sapportals.portal.pcd.pl.PlContext.lookupSubtree(PlContext.java:289)
         at com.sapportals.portal.pcd.pl.PlContext.lookupSubtree(PlContext.java:310)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.(XfsContext.java:146)
         at com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink.(XfsDeltaLink.java:149)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getXfsChildFromPlChild(XfsContext.java:585)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.readXfsObjectFromPersistence(XfsContext.java:503)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getChildAtomicName(XfsContext.java:416)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getChild(XfsContext.java:283)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getChild(XfsContext.java:274)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getChild(XfsContext.java:274)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getChild(XfsContext.java:274)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getChild(XfsContext.java:274)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.lookup(XfsContext.java:222)
         at com.sapportals.portal.pcd.gl.xfs.XfsFactory.getXfsObjectCached(XfsFactory.java:286)
         at com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink.dlGetUnitRootOfTarget(XfsDeltaLink.java:378)
         at com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink.dlGetVirtualTree(XfsDeltaLink.java:292)
         at com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink.deepClone(XfsDeltaLink.java:3063)
         at com.sapportals.portal.pcd.gl.xfs.XfsList.deepClone(XfsList.java:604)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.deepClone(XfsContext.java:2723)
         at com.sapportals.portal.pcd.gl.xfs.XfsList.deepClone(XfsList.java:604)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.deepClone(XfsContext.java:2723)
         at com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink.dlBuildupVirtualTree(XfsDeltaLink.java:468)
         at com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink.dlGetVirtualTree(XfsDeltaLink.java:316)
         at com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink.deepClone(XfsDeltaLink.java:3063)
         at com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink.dlBuildupVirtualTree(XfsDeltaLink.java:468)
         at com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink.dlGetVirtualTree(XfsDeltaLink.java:316)
         at com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink.getAttributes(XfsDeltaLink.java:1486)
         at com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink.getAttributes(XfsDeltaLink.java:1468)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getAttributes(XfsContext.java:1575)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getAttributes(XfsContext.java:1586)
         at com.sapportals.portal.pcd.gl.xfs.BasicObject.getAttributes(BasicObject.java:210)
         at com.sapportals.portal.pcd.gl.xfs.BasicDeltaLink.getAttributes(BasicDeltaLink.java:64)
         at com.sapportals.portal.pcd.gl.PcdPersObject.getAttributes(PcdPersObject.java:114)
         at com.sapportals.portal.pcd.gl.PcdGlObject.getAttributesInternal(PcdGlObject.java:146)
         at com.sapportals.portal.pcd.gl.PcdFilterContext.getFilter(PcdFilterContext.java:928)
         at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:369)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1064)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1070)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1070)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1070)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1070)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1166)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1113)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:907)
         at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:77)
         at com.sapportals.portal.pcd.gl.PcdURLContext.lookup(PcdURLContext.java:238)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1873)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:226)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:307)
         at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
         at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:434)
         at com.sapportals.portal.prt.service.document.DocumentHookServiceNew.doDocumentHook(DocumentHookServiceNew.java:218)
         at com.sapportals.portal.prt.connection.PortalHook.doDocumentHook(PortalHook.java:763)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:795)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
         ... 20 more
    If this situation persists, please contact your system administrator.
    ======================================================
    If any of you have faced this problem and found solution, please help.
    Regards,
    Vittal.

    Hi,
    since you get an out of memory error, I would start by increasing the Maximum Heap Size in the JVM settings of the J2EE Engine to at least 1GB. I beleive this mught help.
    Best Regards,
    Elad

Maybe you are looking for