500-Internal server error on saving release template

Hi Team,
I am facing this issue while saving the release template. I have added a new stage in this template, copied another stage to the new one and started editing the values. On saving the template this error is showing, please see the error message  screen
below.
As this is very urgent for me, please help me to resolve it.
Sreekanth Mohan

Hi SM,  
Thanks for your reply.
If this issue only happened in this current one release template and you cannot reproduce it in another new release template, seems I cannot reproduce this issue in my Release Management 2013 Update 4 environment too. We suggest you create a new release
template instead of this current one.  
To tracking this issue’s log, please refer to the steps in this article:
http://blogs.msdn.com/b/visualstudioalm/archive/2013/12/13/how-to-enable-detailed-logs-and-collect-traces-from-various-release-management-components.aspx.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

  • 500 Internal Server Error while saving variant in web

    Hi,
    I am facing "500 Internal Server Error" when I try to save a variant through web analyzer or wed application designer.It works fine for analyzer.Below are details shown with this error.Please help me to solve this issue.
    "The initial exception that caused the request to fail was:
    Termination message sent
    ABEND RS_EXCEPTION (000): Program GPCW9X9N1G25XUAAK0BDHYGKDGH does not exist
      MSGV1: Program GPCW9X9N1G25XUAAK0BDHYGKDGH does not exist"
    Thanks,
    Madhu.

    Madhu,
    Did you ever resolve this issue when saving a BEx WebVariant .  We are facing the same in our Development system, while it works OK in QA and Production.
    Below is more error message info:
    Root Cause
    The initial exception that caused the request to fail was:
    Termination message sent
    ABEND RS_EXCEPTION (000): Program GP3P3UYUGAR4W4ELP7JYBUFWK4G does not exist
      MSGV1: Program GP3P3UYUGAR4W4ELP7JYBUFWK4G does not exist
    com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent
    ABEND RS_EXCEPTION (000): Program GP3P3UYUGAR4W4ELP7JYBUFWK4G does not exist
      MSGV1: Program GP3P3UYUGAR4W4ELP7JYBUFWK4G does not exist
    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:173)
    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:117)
    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:169)
    Messages
    ABEND: Program GP3P3UYUGAR4W4ELP7JYBUFWK4G does not exist
    ABEND: An exception with the type CX_SY_PROGRAM_NOT_FOUND occurred, but was neither handled locally, nor declared in a RAISING clause
    ABEND: Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
    Server
    BI Java Release: 7 - Patch level: 0000000108 - Description: BI Web Applications Java - Additional info:  - Production mode: true
    BI JAVA SPS : 8, Patch : 20
    BI ABAP Release: 701 - Patch level: 0008 - Description: SAP Business Warehouse (SAP_BW) - Additional info:  - Production mode: true
    Java Virtual Machine Java HotSpot(TM) 64-Bit Server VM - Sun Microsystems Inc. - 1.4.2_26-b03
    Operating System SunOS - sparcv9 - 5.10

  • 500 Internal server error in web template  for specific users

    Hi We have issue with Web templates for some of the users giving error  "500 internal Server Error", all other users able to run the same report.
    We have authorization for the user and following variable which will give target currency selection in variable screen.
    SAP BI Environment
    BI Java : Release: 7 - Patch level: 0000000107 - Description: BI Web Applications Java - Additional info:  - Production mode: true  BI JAVA SPS : 7, Patch : 0
    BI ABAP : Release: 701 - Patch level: 0007 - Description: SAP Business Warehouse (PBICLNT005) - Additional info:  - Production mode: true
    Java Virtual Machine : Java HotSpot(TM) 64-Bit Server VM - Sun Microsystems Inc. - 1.4.2_28-b03
    Operating System :  Windows 2003 - amd64 - 5.2
    Error Message :
    ERROR: Specify a value for variable Select Target Currency
    ERROR: Specify a value for variable Select Target Currency
    Root Cause :
    The initial exception that caused the request to fail was:
    com.sap.ip.bi.bics.dataaccess.resource.impl.bi.exceptions.BicsResourceBwRuntimeException:
    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.initializeState(ProviderSelectionObject.java:932)
    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.queryview.ProviderQueryView.initializeState(ProviderQueryView.java:109)
    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.hasDefaultView(ProviderSelectionObject.java:1462)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.initializeState(SelectionObject.java:516)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QueryView.initializeState(QueryView.java:198)
    please let me know if any of you guys had this kind of problem.

    SLD is not down its in active , I checked SLD url and Technical system also
    Its in active , but when the problem is happend they done restart 
    but many times its happening every time restart is not preferrable ,upto that one is production system.
    SLD is in active , but why the JCO'S ARE DISABLE under content Admin
    where we can search the SLD user , we checked in SU01 but the user didn't exist there
    If user is lock in the sense after the restart again it's working fine
        I want to know the Root cause , why bcz it's simultaniously happend.
    Regards,
    SONY

  • New to OA Framework, getting 500 Internal Server Error

    Dear OAF Gurus,
    I am new in OA Framework development, I have developed first page following https://blogs.oracle.com/prajkumar/entry/oaf_hello_world_tutorial.
    But when i run the page got the error
    500 Internal Server Error
    oracle.apps.fnd.common.AppsException: oracle.apps.fnd.common.PoolException: Exception creating new Poolable object.
         at oracle.apps.fnd.profiles.Profiles.getProfileOption(Profiles.java:1509)
    Please help me in this regard.
    QZ

    Dear Zahid,
    Thanks for your reply,
    I have performed:
    Please perform the following steps:
    1. Go to Internet Explorer --> Tools --> Internet Options --> Connections tab --> LAN settings --> Advanced button
    2. In Exceptions, please include "192.168.*" <without quotes>
    3. Click Ok and Run your page again from Jdeveloper.
    Im using firefox and and in No Proxy Field i put 192.168.*.
    In addtition to above, also verify the following property in your Jdeveloper:
    Tools --> Embedded OC4J Server Properties --> Startup --> Host Name or IP Address used to refer to Embeded OC4J should be 'Default Local IP Address'.
    I also click on Default Local IP Address
    Now page url changed "http://192.168.92.1:8988/OA_HTML/runregion.jsp"
    but same error.
    I have searched
    Tip: A little Search would have helped you in not creating a duplicate thread.
    500 internal server error
    But you know 500 Internet server error is very common and generic error so lot of information there but my issue may be due to some problem in dbc file or db connection???
    i also change the dbc file name from template.dbc to domain_name.dbc copy from server and paste in
    C:\p9879989_R12_GENERIC\jdevhome\jdev\dbc_files\secure
    For Reference dbc file:
    # $Header: template.dbc 120.0 2005/05/07 16:45:30 appldev ship $
    # TEMPLATE.dbc
    #   Template database configuration file.
    #   Create one copy of this file for each database instance this
    #   Applications Server will connect to.  Each file should have the name
    #       <database_instance_name>.dbc
    #   and be located in this directory ($FND_TOP/secure).
    #   Change each of the parameters below to values appropriate for
    #   the database instance.  Do not change the syntax.
    #   This file can be gererated using the AdminAppServer tool.
    #   This is a java utility that can be run from the command line.
    #   Instructions to use this tool are documented in the Applications
    #   Sysadmin Manual.
    # TWO_TASK
    #   SQL*Net name of database.
    TWO_TASK=database
    # FNDNAM
    #   Oracle User to be used for Oracle Applications connection.
    #   The FNDNAM Oracle User must have Oracle Applications privilege level
    #   'Universal'.
    FNDNAM=APPS
    # GWYUID
    #   Oracle User/Password of the public account to be used for initial
    #   Oracle Applications connection.
    #   The GWYUID Oracle User must have Oracle Applications privilege level
    #   'Public'.
    GWYUID=APPLSYSPUB/PUB
    # GUEST_USER_PWD
    #   Applications User/Password of the Guest user.
    #   The Guest Applications User is a public Applications user
    #   with no responsibilities assigned.  If no such user exists,
    #   create one in the 'Define User' form.  Do not use a user with
    #   any active responsibilities. Note: This parameter is for
    #   an applications user NOT an Oracle user. The Guest user
    #   is seeded with 11i.
    GUEST_USER_PWD=GUEST/GUEST
    # THE FOLLOWING PARAMETERS ARE RELEVANT ONLY
    # IF JDBC IS BEING USED. IF THEY ARE NOT SUPPLIED, DEFAULTS
    # WILL BE USED.
    # APPS_JDBC_DRIVER_TYPE
    #   The type of JDBC driver being used. If no value is supplied,
    #   the thick (OCI) driver will be used. Give a value of THIN
    #   or THICK depending on the type of JDBC driver to be used.
    #   For a detailed discussion on the THIN vs the THICK driver,
    #   refer to the JDBC documentation. For Release 11i , this
    #   should be set to a value of THIN.
    APPS_JDBC_DRIVER_TYPE=THIN
    # DB_HOST
    #   The host machine on which the database resides. This parameter
    #   is required only if the THIN DRIVER is being used.
    DB_HOST=host_name
    # DB_PORT
    #   The port of the host machine on which the database resides.
    #   This is required only if the THIN driver is being used.
    DB_PORT=port_number
    # DB_NAME       
    # Database instance name.
    # This is required only if the THIN driver is being used.
    # If no value is provided, the TWO_TASK is used.
    # DB_NAME=db_name
    Best Regards,
    Qamar

  • Running a WD-Appl. results in 500   Internal Server Error

    Dear all,
    I installed both JAVA and ABAP stack (Sneak preview 6.40 SP15) on one box.
    In the NSP I created a Web Service via SE37 using an existing RFC function module of my own. Then I released my Web Service for SOAP Runtime via WSCONFIG.
    Next I checked the WSDL document and run a test via WSADMIN. On the right side I can see all retrieved data in a tree. Congratulation!
    Next I created a Web Dynpro Project in the NW DevStudio that uses my Web Service:
    - the model using my WSDL from above and
    - context and model binding
    - a view showing a table and a pushbutton .
    Eerything went fine ... saveing-deploying-running ...
    A html-page appears, I see my empty table and a shiny button ... I exspect that the Web Service Function Module will be triggered and the table shows me some entries, but instead, when I push the button, I get an error message: "500   Internal Server Error
    Failed to process request. Please contact your system administrator. " What did go wrong? Who can help me?

    Good evening,
    maybe some more info about my system:
    - both stacks are running (all traffic lights are green)
    - the function module sends 5 fields per line, but in the
      View of my WebDynpro I included only 4, excluded field
      MANDT
    - Web-Browser is running with lowest security level
    - here are som logfile info:  Thank you Armin
    I:\usr\sap\J2E\JC02\j2ee\cluster\server0\log\system
    server.1.log
    #1.5#02004C4F4F500061000000410000042800040CFC59A74859#1140177882312#/System/Server/WebRequests#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0####940e13809fad11daba2502004c4f4f50#SAPEngine_Application_Thread[impl:3]_38##0#0#Warning#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NoSuchFieldError: typeRegistry)].The error is: com.sap.engine.services.servletsjsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.null#
    #1.5#02004C4F4F50006B000000110000042800040D00A0D24CEF#1140196256171#/System/Server/SLDService#sap.com/tcwddispwda#com.sap.sldserv.SldApplicationService#admin#4020####1fd388809fd811da831202004c4f4f50#ID\#(J2EE23436000)ID1860686650DB20022690890746729240End.1fd5d2709fd811da919a02004c4f4f50##0#0#Warning#1#com.sap.sldserv.SldApplicationService#Plain###Insufficient permissions for getting SLD access information. You can add permissions for your application via the SLD service in the 'Visual Administrator'.#
    #1.5#02004C4F4F50006B000000140000042800040D00A0D27772#1140196256187#/System/Server/SLDService#sap.com/tcwddispwda#com.sap.sldserv.SldApplicationService#admin#4020####1fd388809fd811da831202004c4f4f50#ID\#(J2EE23436000)ID1860686650DB20022690890746729240End.1fd5d2709fd811da919a02004c4f4f50##0#0#Warning#1#com.sap.sldserv.SldApplicationService#Plain###Insufficient permissions for getting SLD access information. You can add permissions for your application via the SLD service in the 'Visual Administrator'.#
    #1.5#02004C4F4F500012000000010000042800040D00A0D97B46#1140196256640#/System/Server##com.sap.engine.services.deploy######5c0478009fd811da852e02004c4f4f50#SAPEngine_System_Thread[impl:5]_50##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminoverviewsys_mngt~wd finished successfully on server 23436050#
    #1.5#02004C4F4F500012000000020000042800040D00A0D97BBE#1140196256640#/System/Server##com.sap.engine.services.deploy######5c0478009fd811da852e02004c4f4f50#SAPEngine_System_Thread[impl:5]_50##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminoverviewsys_mngt~wd finished on current cluster node for 47 ms.#
    #1.5#02004C4F4F500002000000010000042800040D00A21BB95A#1140196277765#/System/Server##com.sap.engine.services.deploy######689be3509fd811dabf2402004c4f4f50#SAPEngine_System_Thread[impl:5]_34##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminoverviewmonitoring~wd finished successfully on server 23436050#
    #1.5#02004C4F4F500002000000020000042800040D00A21BB9D8#1140196277765#/System/Server##com.sap.engine.services.deploy######689be3509fd811dabf2402004c4f4f50#SAPEngine_System_Thread[impl:5]_34##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminoverviewmonitoring~wd finished on current cluster node for 31 ms.#
    #1.5#02004C4F4F500030000000010000042800040D00A3684B2F#1140196299562#/System/Server##com.sap.engine.services.deploy######7599d8a09fd811da82a002004c4f4f50#SAPEngine_System_Thread[impl:5]_36##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmlv~client_ui finished successfully on server 23436050#
    #1.5#02004C4F4F500030000000020000042800040D00A3684BA9#1140196299562#/System/Server##com.sap.engine.services.deploy######7599d8a09fd811da82a002004c4f4f50#SAPEngine_System_Thread[impl:5]_36##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmlv~client_ui finished on current cluster node for 47 ms.#
    #1.5#02004C4F4F500030000000030000042800040D00A3685B75#1140196299562#/System/Server##com.sap.engine.services.deploy######7599d8a09fd811da82a002004c4f4f50#SAPEngine_System_Thread[impl:5]_36##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminlvwd finished successfully on server 23436050#
    #1.5#02004C4F4F500030000000040000042800040D00A3685BEE#1140196299562#/System/Server##com.sap.engine.services.deploy######7599d8a09fd811da82a002004c4f4f50#SAPEngine_System_Thread[impl:5]_36##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminlvwd finished on current cluster node for 62 ms.#
    #1.5#02004C4F4F5006BD000000000000042800040D00B2D311C2#1140196558250#/System/Server##com.sap.engine.services.deploy######0fca80a09fd911da8f4b02004c4f4f50#SAPEngine_System_Thread[impl:5]_70##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminoverviewconfig~wd finished successfully on server 23436050#
    #1.5#02004C4F4F5006BD000000010000042800040D00B2D3123F#1140196558250#/System/Server##com.sap.engine.services.deploy######0fca80a09fd911da8f4b02004c4f4f50#SAPEngine_System_Thread[impl:5]_70##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminoverviewconfig~wd finished on current cluster node for 32 ms.#
    #1.5#02004C4F4F50003F000000010000042800040D00B4256808#1140196580421#/System/Server##com.sap.engine.services.deploy######1d0187509fd911da918902004c4f4f50#SAPEngine_System_Thread[impl:5]_40##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminlog_configwd finished successfully on server 23436050#
    #1.5#02004C4F4F50003F000000020000042800040D00B4256882#1140196580421#/System/Server##com.sap.engine.services.deploy######1d0187509fd911da918902004c4f4f50#SAPEngine_System_Thread[impl:5]_40##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminlog_configwd finished on current cluster node for 46 ms.#
    #1.5#02004C4F4F500025000000010000042800040D00DEFE7F57#1140197299343#/System/Server##com.sap.engine.services.deploy######c98451f09fda11dacf5d02004c4f4f50#SAPEngine_System_Thread[impl:5]_75##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminoverviewdebug~wd finished successfully on server 23436050#
    #1.5#02004C4F4F500025000000020000042800040D00DEFE7FD1#1140197299343#/System/Server##com.sap.engine.services.deploy######c98451f09fda11dacf5d02004c4f4f50#SAPEngine_System_Thread[impl:5]_75##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminoverviewdebug~wd finished on current cluster node for 15 ms.#
    #1.5#02004C4F4F500029000000010000042800040D00F460D8F4#1140197658015#/System/Server##com.sap.engine.services.deploy######9f4d52f09fdb11dac04c02004c4f4f50#SAPEngine_System_Thread[impl:5]_83##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminoverviewanalysis~wd finished successfully on server 23436050#
    #1.5#02004C4F4F500029000000020000042800040D00F460D978#1140197658015#/System/Server##com.sap.engine.services.deploy######9f4d52f09fdb11dac04c02004c4f4f50#SAPEngine_System_Thread[impl:5]_83##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminoverviewanalysis~wd finished on current cluster node for 47 ms.#
    #1.5#02004C4F4F50003E000000030000042800040D00F5660BBF#1140197675140#/System/Server##com.sap.engine.services.deploy######a98264409fdb11daa59302004c4f4f50#OrderedChannel for service##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminoverviewperform~wd finished successfully on server 23436050#
    #1.5#02004C4F4F50003E000000040000042800040D00F5660C39#1140197675140#/System/Server##com.sap.engine.services.deploy######a98264409fdb11daa59302004c4f4f50#OrderedChannel for service##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminoverviewperform~wd finished on current cluster node for 62 ms.#
    #1.5#02004C4F4F5000200000000B0000042800040D00F597B551#1140197678390#/System/Server##com.sap.engine.services.deploy######ab724d609fdb11dac12102004c4f4f50#SAPEngine_System_Thread[impl:5]_97##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminsession_tracewd finished successfully on server 23436050#
    #1.5#02004C4F4F5000200000000C0000042800040D00F597B5CA#1140197678390#/System/Server##com.sap.engine.services.deploy######ab724d609fdb11dac12102004c4f4f50#SAPEngine_System_Thread[impl:5]_97##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminsession_tracewd finished on current cluster node for 47 ms.#
    #1.5#02004C4F4F500041000000020000042800040D00F809240B#1140197719375#/System/Server##com.sap.engine.services.deploy######c3e01df09fdb11da90cd02004c4f4f50#SAPEngine_System_Thread[impl:5]_71##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminoverviewconf~wd finished successfully on server 23436050#
    #1.5#02004C4F4F500041000000030000042800040D00F8092486#1140197719375#/System/Server##com.sap.engine.services.deploy######c3e01df09fdb11da90cd02004c4f4f50#SAPEngine_System_Thread[impl:5]_71##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminoverviewconf~wd finished on current cluster node for 32 ms.#
    #1.5#02004C4F4F50002D0000000B0000042800040D01BC3F1359#1140201011218#/System/Server/SLDService##com.sap.sldserv.SldServerFrame.doCollect######664177909fe311da83fb02004c4f4f50#SAPEngine_System_Thread[impl:5]_57##0#0#Warning#1#com.sap.sldserv.SldServerFrame#Plain###SLD data collector run failed: Unable to open connection to host "localhost:50000". The host is down or unavailable..#
    #1.5#02004C4F4F50002D0000000C0000042800040D01BC3F1446#1140201011218#/System/Server/SLDService##com.sap.sldserv.SldServerFrame######664177909fe311da83fb02004c4f4f50#SAPEngine_System_Thread[impl:5]_57##0#0#Warning#1#com.sap.sldserv.SldServerFrame#Plain###Failed to collect SLD data. Unable to open connection to host "localhost:50000". The host is down or unavailable..#
    #1.5#02004C4F4F500062000000250000042800040D02694FB4F4#1140203914796#/System/Server/WebRequests#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0####30a256c09fea11dac94a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: java.lang.NoSuchFieldError: _typeRegistry
    Exception id: [02004C4F4F500062000000240000042800040D02694FB344]#
    #1.5#02004C4F4F500062000000270000042800040D02694FBDA8#1140203914796#/System/Server/WebRequests#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0####30a256c09fea11dac94a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Warning#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NoSuchFieldError: typeRegistry)].The error is: com.sap.engine.services.servletsjsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.null#
    I:\usr\sap\J2E\JC02\j2ee\cluster\server0\log\system
    userinterface.0.log
    #1.5#02004C4F4F500058000000180000042800040CFC451E5B5B#1140177537984#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Guest#0####c6d43c009fac11daa11602004c4f4f50#SAPEngine_Application_Thread[impl:3]_20##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Plain###ClientWindow with Id 9fbf1dd19faa11da982502004c4f4f50does not contain ApplicationWindow with Id Id9fbf1dd19faa11da982502004c4f4f501!#
    #1.5#02004C4F4F50006C0000000C0000042800040CFC4520D522#1140177538156#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Guest#0####c6ee7ac09fac11da96ec02004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Plain###ClientWindow with Id 5aaa43309fac11daa9e302004c4f4f50does not contain ApplicationWindow with Id Id5aaa43309fac11daa9e302004c4f4f502!#
    #1.5#02004C4F4F50005B0000000D0000042800040CFC557AD42C#1140177812281#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientSession#Guest#0####6a5031909fad11da952f02004c4f4f50#ID\#(J2EE23436000)ID1437660650DB21061510417884802850End.6a5031919fad11daa4e302004c4f4f50##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientSession#Java###ClientSession=, locale=#2#(J2EE23436000)ID1437660650DB21061510417884802850End#de#
    #1.5#02004C4F4F5000610000003C0000042800040CFC59A72A98#1140177882296#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientManager.handleThrowable#Guest#0####940e13809fad11daba2502004c4f4f50#ID\#(J2EE23436000)ID1437660650DB21061510417884802850End.6a5031919fad11daa4e302004c4f4f50##0#0#Error#1#/System/UserInterface#Plain###Exception(java.lang.NoSuchFieldError: _typeRegistry) during processing a Web Dynpro Application.#
    #1.5#02004C4F4F500070000000170000042800040CFC5E58E911#1140177961062#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Guest#0####c300d0609fad11daa29302004c4f4f50#SAPEngine_Application_Thread[impl:3]_17##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientManager#Plain###ClientWindow with Id 6a5031919fad11daa4e302004c4f4f50does not contain ApplicationWindow with Id Id6a5031919fad11daa4e302004c4f4f503!#
    #1.5#02004C4F4F50006B0000000E0000042800040D009AD602EE#1140196155750#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientSession#admin#4020####1fd388809fd811da831202004c4f4f50#ID\#(J2EE23436000)ID1860686650DB20022690890746729240End.1fd5d2709fd811da919a02004c4f4f50##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientSession#Java###ClientSession=, locale=#2#(J2EE23436000)ID1860686650DB20022690890746729240End#en#
    #1.5#02004C4F4F50006F000000130000042800040D02653B3545#1140203846359#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientSession#Guest#0####07d53d709fea11da9a6802004c4f4f50#ID\#(J2EE23436000)ID0131720150DB21013274501523920836End.07d7ae709fea11da844902004c4f4f50##0#0#Info#1#com.sap.tc.webdynpro.clientserver.cal.ClientSession#Java###ClientSession=, locale=#2#(J2EE23436000)ID0131720150DB21013274501523920836End#de#
    #1.5#02004C4F4F500062000000220000042800040D02694F9F64#1140203914796#/System/UserInterface#sap.com/tcwddispwda#com.sap.tc.webdynpro.clientserver.cal.ClientManager.handleThrowable#Guest#0####30a256c09fea11dac94a02004c4f4f50#ID\#(J2EE23436000)ID0131720150DB21013274501523920836End.07d7ae709fea11da844902004c4f4f50##0#0#Error#1#/System/UserInterface#Plain###Exception(java.lang.NoSuchFieldError: _typeRegistry) during processing a Web Dynpro Application.#
    I:\usr\sap\J2E\JC02\j2ee\cluster\server0\log\system\httpaccess
    responses.0.trc
    [Feb 17, 2006 8:14:52 PM  ] - 127.0.0.1 : GET /webdynpro/dispatcher/sap.com/tclmwebadminmainframewd/WebAdminApp?sap-wd-cltwndid=1fd5d2709fd811da919a02004c4f4f50&sap-wd-appwndid=Id1fd5d2709fd811da919a02004c4f4f504&sap-sessioncmd=unload HTTP/1.1 500 2117
    [Feb 17, 2006 8:17:26 PM  ] - 169.254.25.129 : GET /webdynpro/dispatcher/local/MyWDP/MyWDA?SAPtestId=4 HTTP/1.1 200 3221
    [Feb 17, 2006 8:18:34 PM  ] - 169.254.25.129 : POST /webdynpro/dispatcher/local/MyWDP/MyWDA?SAPtestId=4 HTTP/1.1 500 720
    I:\usr\sap\J2E\JC02\j2ee\cluster\server0\log\system\webcontainer
    requests.0.trc
    The error is: java.lang.NoSuchFieldError: _typeRegistry
    Exception id: [02004C4F4F500062000000240000042800040D02694FB344]#
    #1.5#02004C4F4F500062000000270000042800040D02694FBDA8#1140203914796#/System/Server/WebRequests#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0####30a256c09fea11dac94a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Warning#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NoSuchFieldError: typeRegistry)].The error is: com.sap.engine.services.servletsjsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.null#

  • Report printing with BI pubisher - 500 Internal server error

    Hi,
    I was having problems using BI publisher to print with. I thought we didn't have it at first, however since found we do have BI Publisher Enterprise edition.
    When I put the settings into APEX, reports don't display as expected. I get
    report error:
    ORA-20001: The printing engine could not be reached because either the URL specified is incorrect or a proxy URL needs to be specified.Now if I navigate to the URL in my web browser, http://[server]:[port]/xmlpserver/convert, I get a 500 - Internal Server Error page. The requets is definitely hitting something because if I change "convert" to say "convert1" then I get 404 (as expected). So it seems as if convert is found but then a problem occurs.
    If I navigate to just http://[server]:[port]/xmlpserver/ then I see the BI publisher enterprise login screen.
    Any ideas what might be causing this or what I could do to resovle it?
    Our APEX instance is on a unix box and BI on a M$ box if that matters (long story)?
    Thanks

    Ignacio Cobos wrote:
    Hello
    >
    > I get this error when i try to access to Bex Analyzer
    >
    > ERROR: URL used, "http://sesue:50300", is not fully qualified.
    > A fully-qualified URL has a schema with the format "<protocol>://server.company.com:<port>". URLs with the format "<protocol>://server:<port>" or "<protocol>://<ip address>:<port>" are not fully qualified.
    > See SAP Notes 581329 (Not possible to implement) , 596698 (Not possible to implement) and 654326 (Not yet released)
    >
    > Can anybody say me any idea how to solve the problem?
    >
    > Thanks in advance
    Dear Cobos, For FQDN related issues : Set profile param "icm/host_name_full" with corresponding FQDN via RZ10 transaction. Also check login/create_sso2_ticket & /accept_sso2_ticket parameters in the profile you have created.  Instead of "http://sesue:50300" you may to have the URL like "http://sesue.domain.com:50300//SAP/BW/BEX/". Please refer this #scn article for more details : http://goo.gl/QPlrx Similar Issues : http://goo.gl/mRCh0 Hope it helps. Thanks.

  • 500 internal server error when using attendance in ESS

    Hi All,
    when the user clicks on attendance & its related activities in ESS, the following error is displaying frequently and after sometime it is working properly.  why it is giving error frequently and how to avoid this error permanently? 
    Related Activities
    500 Internal Server Error
    Web Dynpro Container/SAP J2EE Engine/6.40
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
    com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
    at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
    at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
    at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
    ... 69 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:12:34[UTC], changelist=421181, host=pwdfm101), build date: Tue Oct 16 13:15:01 BST 2007
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: amd64
    Session & Other
    Session Locale en_GB
    Time of Failure Thu Jan 24 11:58:41 GMT 2008 (Java Time: 1201175921417)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:52:59[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:53:17[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:58:51[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0010.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:50:36[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0010.20061002110156.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:55:32[UTC], changelist=419397, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
    SapWebDynproGenerationCore 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:59:00[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/pb_api
    SapDictionaryGenerationCore 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:52:59[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:53:17[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:58:51[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0010.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:50:36[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0010.20061002110156.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:55:32[UTC], changelist=419397, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
    SapWebDynproGenerationCore 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:59:00[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to read deployment descriptor.
    at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.initializeDeployableObjectParts(AbstractDeployableObject.java:297)
    at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.getPart(AbstractDeployableObject.java:214)
    at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObjectPart(DeployableObjectFactory.java:113)
    at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObject.getDeployableObjectPart(WDDeployableObject.java:62)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:921)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:176)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createVACComponentUsage(FPMComponent.java:745)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:562)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
    at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:772)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:707)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1248)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
    at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
    at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:826)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:723)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    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:387)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
    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.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to find deployment descriptor '.\temp\webdynpro\public\sap.com\msseeproarchiveddocuments\webdynpro\portalapp.xml' on the file system. Please check if the application 'sap.com/msseeproarchiveddocuments' is deployed correctly.
    at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getDeploymentDescriptor(DeployableObject.java:278)
    at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.initializeDeployableObjectParts(AbstractDeployableObject.java:259)
    ... 58 more
    Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: Unexpected IO exception on GET<sap.com/msseeproarchiveddocuments>
    at com.sap.engine.services.webdynpro.WebDynproContainer.getDeployableObject(WebDynproContainer.java:209)
    at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeploymentDescriptor(WebDynproRuntimeServiceImpl.java:354)
    at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getDeploymentDescriptor(DeployableObject.java:274)
    ... 59 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
    at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
    at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76)
    at com.sap.engine.services.webdynpro.PApplication.load(PApplication.java:142)
    at com.sap.engine.services.webdynpro.WebDynproContainer.getDeployableObject(WebDynproContainer.java:204)
    ... 61 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
    at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
    at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
    at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
    at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
    at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
    at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
    ... 65 more
    Thanks in advance,
    v

    Hi,
    We  were also having the same problem; but we couldnt find a specific solution for that problem.
    But when we upgraded the ESS support packages to SP13 for some other reason this issue was also got resolved.
    May be helpful i guess.
    Regards,
    Vijay

  • 500 internal server error while submitting a pdf form

    HI,
    we have implemented SAP portal in our lanscape. few users are getting 500 internal server error.
    The root cause is showing as com.sap.tc.webdynpro.services.sal.util.cache.WDResourceNot FoundException:cant write binary content
    Can anyone provide any solution for this?
    thanks in advance.

    hi,
    the user is getting the following error.
    can you please give me any suggestions for solving this issue.
    thanks in advance
    500 Internal Server Error
    Web Dynpro Container/SAP J2EE Engine/6.40
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy
    of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
    com.sap.tc.webdynpro.services.sal.util.cache.WDResourceNotFoundException: Cant write binary content!
    at com.sap.tc.webdynpro.services.sal.util.cache.ResourcePool$FiledResourcePoolElement.writeTo(ResourcePool.java:813)
    at com.sap.tc.webdynpro.serverimpl.core.datatransport.AbstractMassDatasource.getBytes(AbstractMassDatasource.java:97)
    at com.sap.tc.webdynpro.clientimpl.html.uielements.uradapter.InteractiveFormAdapter.doSetAttribute(InteractiveFormAdapter.java:141)
    at com.sap.tc.webdynpro.clientimpl.html.uielib.activecomp.uradapter.AbstractActiveComponentAdapter.onACFSETATTRIBUTE(AbstractActiveComponentAdapter.java:450)
    at sun.reflect.GeneratedMethodAccessor382.invoke(Unknown Source)
    ... 26 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Amgen.v1b; .NET CLR 1.1.4322)
    Version
    DOM version
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, Build ID: 6.4015.00.0000.20051123162612.0000 (release=630_VAL_REL, buildtime=2005-12-14:21:51:22[UTC], changelist=377533, host=PWDFM026)
    J2EE Engine 6.40 patchlevel 100627.313
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: amd64
    Other
    Session Locale ja
    Time of Failure Fri Jan 12 04:18:29 GMT 2007 (Java Time: 1168575509171)
    Web Dynpro Code Generation Infos
    sap.com/pcui_gp~isr
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4011.00.0000.20041104124957.0000 (release=630_VAL_COR, buildtime=2005-02-16:02:02:27[UTC], changelist=298356, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    sap.com/pcui_gp~xssutils
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException
    at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.handleUIElementEvent(HtmlClient.java:853)
    at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.updateEventQueue(HtmlClient.java:740)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.initEvents(AbstractClient.java:131)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.prepareTasks(AbstractClient.java:99)
    at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:247)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    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: java.lang.reflect.InvocationTargetException
    at sun.reflect.GeneratedMethodAccessor382.invoke(Unknown Source)

  • 500 Internal Server Error in Portal

    Hi,
    I get an error when I try to open a saved report with Complex calculations in it, it is named Complex formula report in my favorites.
    When i run the URL the error which i am getting is:
    500 Internal Server Error
    >>>>> BEx Web Application Failed to process request; contact your system administrator
    But it runs fine in the portal.
    Thanks,
    Mani A

    Hi,
    Check the port number used in the URL! Normally when the report executed thro' the Portal, system uses the load balancing (if configured) and determines the App server automatically but while executing the report thro' URL it has 2 options. One is using the port which is load balanced and other option is by using port directly referring to App. server.
    Hope this helps.
    Cheers
    Bala Koppuravuri

  • APEX 3.2 Installation - 500 Internal Server Error

    Hi All,
    I am trying to get APEX 3.2 working on a 10.2.0.5 database, using Embedded PL/SQL Gateway. I have followed the steps from here.
    The installation is successful (no errors in install log). However, when I try to access the APEX admin page (http://host:port/apex/apex_admin) for the first time after installation, I get "500 Internal Server Error".
    Can somebody help me to figure out what is the issue ?
    Following are the details I think are relevant:
    SQL> select * from v$version ;
    BANNER
    Oracle Database 10g Release 10.2.0.5.0 - 64bit Production
    PL/SQL Release 10.2.0.5.0 - Production
    CORE     10.2.0.5.0     Production
    TNS for Linux: Version 10.2.0.5.0 - Production
    NLSRTL Version 10.2.0.5.0 - Production
    SQL> set lines 171 pages 999 arrays 151 long 10000
    SQL> select cast(substr(comp_name, 1, 40) as varchar2(40)) as comp_name, version, status from dba_registry ;
    COMP_NAME                     VERSION               STATUS
    Oracle Application Express           3.2.0.00.27               VALID
    Spatial                      10.2.0.5.0               VALID
    Oracle interMedia                10.2.0.5.0               VALID
    OLAP Catalog                     10.2.0.5.0               VALID
    Oracle Enterprise Manager           10.2.0.5.0               VALID
    Oracle XML Database                10.2.0.5.0               VALID
    Oracle Text                     10.2.0.5.0               VALID
    Oracle Expression Filter           10.2.0.5.0               VALID
    Oracle Rules Manager                10.2.0.5.0               VALID
    Oracle Workspace Manager           10.2.0.5.0               VALID
    Oracle Data Mining                10.2.0.5.0               VALID
    Oracle Database Catalog Views           10.2.0.5.0               VALID
    Oracle Database Packages and Types      10.2.0.5.0               VALID
    JServer JAVA Virtual Machine           10.2.0.5.0               VALID
    Oracle XDK                     10.2.0.5.0               VALID
    Oracle Database Java Packages           10.2.0.5.0               VALID
    OLAP Analytic Workspace            10.2.0.5.0               VALID
    Oracle OLAP API                 10.2.0.5.0               VALID
    18 rows selected.
    SQL> select dbms_xdb.gethttpport from dual ;
    GETHTTPPORT
           8080
    SQL> select username, account_status from dba_users ;
    USERNAME                 ACCOUNT_STATUS
    SYS                      OPEN
    SYSTEM                      OPEN
    DBSNMP                      OPEN
    ANONYMOUS                 OPEN
    APEX_PUBLIC_USER            OPEN
    SYSMAN                      EXPIRED
    SCOTT                      EXPIRED
    FLOWS_FILES                 LOCKED
    APEX_030200                 LOCKED
    OUTLN                      EXPIRED & LOCKED
    MGMT_VIEW                 EXPIRED & LOCKED
    MDSYS                      EXPIRED & LOCKED
    ORDSYS                      EXPIRED & LOCKED
    EXFSYS                      EXPIRED & LOCKED
    DMSYS                      EXPIRED & LOCKED
    WMSYS                      EXPIRED & LOCKED
    CTXSYS                      EXPIRED & LOCKED
    XDB                      EXPIRED & LOCKED
    ORDPLUGINS                 EXPIRED & LOCKED
    SI_INFORMTN_SCHEMA            EXPIRED & LOCKED
    OLAPSYS                  EXPIRED & LOCKED
    ORACLE_OCM                 EXPIRED & LOCKED
    TSMSYS                      EXPIRED & LOCKED
    BI                      EXPIRED & LOCKED
    PM                      EXPIRED & LOCKED
    MDDATA                      EXPIRED & LOCKED
    IX                      EXPIRED & LOCKED
    SH                      EXPIRED & LOCKED
    DIP                      EXPIRED & LOCKED
    OE                      EXPIRED & LOCKED
    HR                      EXPIRED & LOCKEDLet me know if any more details are needed.
    Thanks in advance.

    Hi Alberto,
    A revised version of the APEX Listener has been applied to the apex.oracle.com instance, containing a fix for bug 16210026. So you should now be able to carry out your RESTful Services tests successfully. Please note that the updated version of the APEX Listener release, release 2.0.1, is not yet available for download from OTN but hopefully should be soon. Keep an eye on the APEX Listener OTN page: http://www.oracle.com/technetwork/developer-tools/apex-listener/overview/index.html.
    Regards,
    Hilary

  • 500   Internal Server error while creating decision dialog type object

    Hi All
    I am working on one CAF application and creating Create an Alternative Block Type. Inside this block I am creating decision dialog type object.When i reached at 4th step [Set Configuration] and editing [Decision Options]. After giving [Option ID]  when i clicks on add button.
    Following errors occuring
    500   Internal Server Error
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.caf.eu.gp.ui.actions.decpage.VEditOption.onActionAddRule(VEditOption.java:290)
         at com.sap.caf.eu.gp.ui.actions.decpage.wdp.InternalVEditOption.wdInvokeEventHandler(InternalVEditOption.java:235)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:297)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:706)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:660)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         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)
    Those who have encountered such problem please provide me some help.
    With Thanks
    Ramshanker

    Refers to issue below... there is a patch available...
    ParserException when using a Decision Dialog CO
    SAP Note Number: 990460 
    Symptom
    ParserException with the attached stack trace occurs when a Decision Dialog CO is created or executed
       com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
        at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
        at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
        at com.sap.engine.lib.x ml.parser.XMLParser.scanDocument(XMLParser.java:2792)
    The following messages can be found:
    Failed to get Related Model Object for the object com.sap.caf.eu.gp.ui.actions.decpage.CDecisionPageInterfaceViewdecisionPageUsage1
    Or
    Failed to get Related Model Object for the object com.sap.caf.eu.gp.ui.co.exec.decision.COExecDecision
    Reason and Prerequisites
    Affected versions:
    Netweaver 04s SP 07 to SP 09
    Solution
    <b>A.) The issue is cleared in these deliveries:
    NW04s SP 09 Patch 1
    B.) Possible workaround before the release of mentioned deliveries:
    Redeploy the following component from SAP-EU SCA (if redeployment does not help undeploy and deploy again)
    caf/eu/gp/ui/actions</b>
    Header Data
    Release Status Released for Customer
    Released on 19.10.2006
    Priority Correction with high priority
    Category Program error
    Primary Component BC-GP Guided Procedure
    Release
    Soft. Component Release Track From Release To Release And Successors
    SAP-EU   7.00   7.00   7.00    
    Correction Instructions
    No correction instruction available 
    Support Packages
    No Support Packages available 
    Related notes
    No related notes available 
    Attributes
    No attributes available 
    Attachments
    No attachments available
    Reason - Side Effects
    SAP Notes / Patches corrected by this Note

  • 500 internal server error in R12

    while connecting R12 through front end, i am getting below error
    500 Internal Server Error
    java.lang.NoClassDefFoundError     at oracle.apps.fnd.sso.AppsLoginRedirect.AppsSetting(AppsLoginRedirect.java:126)     at oracle.apps.fnd.sso.AppsLoginRedirect.init(AppsLoginRedirect.java:170)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.loadServlet(HttpApplication.java:2231)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.findServlet(HttpApplication.java:4617)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.findServlet(HttpApplication.java:4541)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2821)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:740)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:299)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:187)     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)     at java.lang.Thread.run(Thread.java:595)
    could you help me to resolve this issue.

    Hi Venkat;
    It was working before?If yes what have you been changed?(patch etc.) Did you run autuconfig and retest issue?What is your OS?Do you have any error in alert.log?
    Please check below:
    500 Internal Server Error [ID 761869.1]
    "500 Internal Server Error - java.lang.NoClassDefFoundError: oracle.apps.fnd.profiles.Profiles" on 10G [ID 567554.1]
    Also check:
    Starting up AS10g services in an EBusiness Suite Release 12 environment [ID 743518.1]
    Hope it helps
    Regard
    Helios

  • 500 Internal server error when running SOLMAN_SETUP

    Hi experts,
    I'm configuring our solution manager with the SOLMAN_SETUP transaction. In the "initial Configuration", step "j2ee configuration", I click the "Start SLD configuration" button and appears an Internet explorer. After loggin with an administrator user/password, the following error appears:
    500 Internal Server Error
    SAP NetWeaver Application Server 7.00/Java AS 7.00
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.lm.ctc.ccl.wd.TemplateInstallerCompController.getSelectedForSkipActions(TemplateInstallerCompController.java:741)
        at com.sap.tc.lm.ctc.ccl.wd.ScenarioTemplateViewController.actionReexecuteSelectedTemplate(ScenarioTemplateViewController.java:141)
        at com.sap.tc.lm.ctc.ccl.wd.ScenarioTemplateViewController.init(ScenarioTemplateViewController.java:115)
        at com.sap.tc.lm.ctc.ccl.templateinstaller.ScenarioTemplateView.wdDoInit(ScenarioTemplateView.java:106)
        at com.sap.tc.lm.ctc.ccl.templateinstaller.wdp.InternalScenarioTemplateView.wdDoInit(InternalScenarioTemplateView.java:475)
        ... 37 more
    See full exception chain for details.
    Our solution mananger release is 7.0 EHP1.
    Do you have any idea of what the problem is, please?
    Thanks and best regards,
    Ana

    Hi,
    The E:\usr\sap\SOL\DVEBMGS00\j2ee\cluster\dispatcher\log\defaultTrace.0.trc last entries are:
    #1.5 #000C298948DC001C0000000200000FA80004765AE7A68A56#1256032712398#com.sap.engine.core.configuration##com.sap.engine.core.configuration#######SAPEngine_System_Thread[impl:6]_27##0#0#Error#1#/System/Server#Plain###Exception in ConfigurationChangedListener:
    null
    =======================================================
    java.lang.NullPointerException
    +     at com.sap.engine.services.monitor.common.MonitorConfigurationHandler.configurationChanged(MonitorConfigurationHandler.java:1105)+
    +     at com.sap.engine.core.configuration.impl.event.PathEventProcessor.sendEvents(PathEventProcessor.java:138)+
    +     at com.sap.engine.core.configuration.impl.event.EventProcessor.processEventListeners(EventProcessor.java:121)+
    +     at com.sap.engine.core.configuration.impl.event.QueuedEventProcessor.run(QueuedEventProcessor.java:48)+
    +     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)+
    +     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:80)+
    +     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:150)+
    #1.5 #000C298948DC001F0000001D00000FA80004765B772CB455#1256035120366#com.sap.engine.core.thread.impl6.ThreadManagerImpl##com.sap.engine.core.thread.impl6.ThreadManagerImpl#######Thread[Thread-30,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:6]_ThreadManager:
    Thread[SAPEngine_System_Thread[impl:6]_37]
    Task: com.sap.engine.core.thread.impl6.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: [email protected]7a6dd8e1] with classloader [[email protected]2254d@service:log_configurator]#
    #1.5 #000C298948DC001F0000001D000003680004765BBE6F6136#1256036315718#com.sap.engine.core.thread.impl6.ThreadManagerImpl##com.sap.engine.core.thread.impl6.ThreadManagerImpl#######Thread[Thread-1738,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:6]_ThreadManager:
    Thread[SAPEngine_System_Thread[impl:6]_12]
    Task: com.sap.engine.core.thread.impl6.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: [email protected]3f6a5bcb] with classloader [[email protected]0d8e1@service:log_configurator]#
    And the E:\usr\sap\SOL\DVEBMGS00\j2ee\cluster\server0\log\defaultTrace.8.trc entries related to the error message are:
    #1.5 #000C298948DC00540000033C00000F1400047684AAF47374#1256212082608#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#SISTEMAS#104##crosol203_SOL_2722150#SISTEMAS#bf43cb51bf0011de8147000c298948dc#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server/WebRequests#Plain###application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: java.lang.NullPointerException: null
    Exception id: [000C298948DC00540000033A00000F1400047684AAF47077]#
    Thanks and best regards,
    Ana Abad

  • 500   Internal Server Error while deploying InteractiveForm in Webdynpro

    I tried to deploy the Sample template from SDN
    when i tried to Deploy it on Server i am getting the ERROR
    <b>500   Internal Server Error</b>
    WebServices of the Server are installed properly and the settings are done.
    i will be thankful for Quick Response
    Regards,
    Srikanth

    Hi Bunny,
    Can you please tell me what have you done for getting the issue resolved.
    Regards,
    Samar.

  • Error 500--Internal Server Error when using BI Publisher within OBIEE 11g

    I'm using OBIEE 11.1.1.6.2BP1 on a Linux x86-64 server and it has been working just fine. We recently started playing around with the BI Publisher component of that installation and every time i go to http://hostname:port/xmlpserver and try to log in with an Administrator username and password, the following error shows up:
    Error 500--Internal Server Error
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    *10.5.1 500 Internal Server Error*
    The server encountered an unexpected condition which prevented it from fulfilling the request.
    I have looked around for solutions and tried a couple of them (created a new Admin user in Weblogic Console and checked the opmnctl status) and they did not help. I'm looking for an answer other than upgrade to the latest and greatest
    Any help is appreciated.

    Do you have any SSO setup as that might be preventing the ability of the user to log into BI Publisher, hence the Internal 500 error message.
    Are you using FMW security model for BIP and OBIPS integration which is by default. Check the xmlp-server-config.xml file from the repository [\Middleware\Oracle_BI1\clients\bipublisher\repository\Admin\Configuration\xmlp-server-config.xml] and see what your security model is pointing to?
    Also what happens when you try to access from Administration>BI Publisher >Manager BI Publisher ?
    Follow : http://docs.oracle.com/cd/E23943_01/bi.1111/e22255.pdf
    Oracle Fusion MiddlewareAdministrator's Guide for Oracle Business Intelligence Publisher 11g Release 1
    HTH,
    SVS

Maybe you are looking for

  • Slow cd import with imac 24 vs dual G5

    my new imac 24 is much slower at importing cd's (converting to mp3 at 192) than my G5... something like 7-8x with the imac vs 18-20x with the G5... ??? is this typical for your results or do I have a bum setting??? stephen

  • Nokia N8 softwere problem

    i have nokia n8 phone.. when i powering on its coming only nokia logo only........ any help.....

  • When down loaning updates, im ask what program to open it up with

    when i tried down loading updates, my computer would asked me what program i wanted to open it up with. Duplicate of [/questions/912713]

  • Help!!! Keynote is driving me mad

    After I installed Mavericks I cannot drag and drop images from other applications or from the web into keynote: instead of the image, it imports a link. I need to prepare a class!

  • CLI156 Could not start the domain domain1

    I installed successfully the Appserver on desktop, but when I try to start it from laptop, comes the message below. Both are w2k and 512 memory. Environment: C:\>set ALLUSERSPROFILE=C:\Documents and Settings\All Users APPDATA=C:\Documents and Setting