Error in output processing analysis

Hi,
we have maintained ZA output types corresponding to partner number as Personnel number and we have not maintained the address for the Pernr as thats how our business works. now the issue is when we process the output type ZA , we get an error in "output processing analysis" that adrnr is not maintained how can we suppress the error ??
the error comes after it does not receives adrnr in FM 'ADDR_GET_NEXT_COMM_TYPE' for the form output.
below ins the error i get
http://img9.imageshack.us/img9/8894/sdnt.jpg

In your delivery in the Picking tab, check if the Picking status says 'Not relevant for Picking'.
If that is the case, then you have to see if that is intentional or by mistake.
if it is not intentional, then you can change the delivery item category config to make the item relevant for picking.

Similar Messages

  • Error in automatic processing of output of a delivery

    Dear All,
    In the stock tranport scenario, I am using an output type SPED in an outbound delivery. When this is processed an inbound delivery is created automatically from the outbound.
    The problem is that the output is not being processed automatically. The error I get is "Output processing has been triggered in a new task".
    Dispatch time is already maintained as 4. If I process the output manually using VL71, it works fine.
    Any ideas!!
    Regards,
    VJ

    I have already checked in SM58. I do not see anything there.
    Details of the error:
    Message no. /SPE/VL300
    Diagnosis
        Output processing was triggered immediately when the delivery was saved.
        The actual processing of this output started a new task.
        This task might still be running - or might have terminated with an
        error.
    Procedure
        You can wait for a while and then recheck the processing status.
        If the processing log has not been updated, please take a look at the
        monitor for tRFC calls (transaction code SM58).

  • Error in automatic processing of output of an outbound delivery

    Dear All,
    In the stock tranport scenario, I am using an output type SPED in an outbound delivery. When this is processed an inbound delivery is created automatically from the outbound.
    The problem is that the output is not being processed automatically. The error I get is "Output processing has been triggered in a new task".
    Dispatch time is already maintained as 4. If I process the output manually using VL71, it works fine.
    Any ideas!!
    Regards,
    VJ

    SPED is having default Transmission Medium as 8 ( Special Function ) .
    Can you change it to 1 and try.
    thanks,

  • ESS Persoanl Data Error(Screen output without connection to user)

    Hi All,
            When i am trying to Save my data in my ESS----->Personal Info -
    >Personal Data, i am getting below error, any body know how to resolve this issue, please let me know.
    Screen output without connection to user., error key: RFC_ERROR_SYSTEM_FAILURE:
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Screen output without connection to user., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.per.fc.persinfo.FcPersInfo.save(FcPersInfo.java:440)
         at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfo.save(InternalFcPersInfo.java:770)
         at com.sap.xss.per.fc.persinfo.FcPersInfoInterface.save(FcPersInfoInterface.java:186)
         at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface.save(InternalFcPersInfoInterface.java:275)
         at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface$External.save(InternalFcPersInfoInterface.java:435)
         at com.sap.xss.per.vc.reviewnavi.VcPersInfoReviewNavi.onEvent(VcPersInfoReviewNavi.java:213)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNavi.onEvent(InternalVcPersInfoReviewNavi.java:171)
         at com.sap.xss.per.vc.reviewnavi.VcPersInfoReviewNaviInterface.onEvent(VcPersInfoReviewNaviInterface.java:115)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNaviInterface.onEvent(InternalVcPersInfoReviewNaviInterface.java:124)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNaviInterface$External.onEvent(InternalVcPersInfoReviewNaviInterface.java:200)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:533)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseSaveEvent(FPMComponent.java:951)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseSaveEvent(FPMComponent.java:1114)
         at com.sap.xss.per.vc.reviewnavi.VcPersInfoReviewNavi.next(VcPersInfoReviewNavi.java:227)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNavi.next(InternalVcPersInfoReviewNavi.java:175)
         at com.sap.xss.per.vc.reviewnavi.ReviewNaviView.onActionNext(ReviewNaviView.java:153)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalReviewNaviView.wdInvokeEventHandler(InternalReviewNaviView.java:173)
         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:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         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.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1299)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:868)
         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:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         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:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         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(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Screen output without connection to user., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.per.model.mac.HRXSS_PER_MAC.hrxss_Per_Save(HRXSS_PER_MAC.java:478)
         at com.sap.xss.per.model.mac.Hrxss_Per_Save_Input.doExecute(Hrxss_Per_Save_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 64 more
    and after that i went to ST22 Transaction Code in my ECC System i found two types of DUMP errors,
    the below are those details.
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
    Exception              CX_SY_REF_IS_INITIAL
    Date and Time          09/09/2008 08:19:16
    Short text
    Access via 'NULL' object reference not possible.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLHRXSS_PER_MAC" had to be terminated because it
    has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
    caught in
    procedure "HRXSS_PER_CLEANUP" "(FUNCTION)", nor was it propagated by a RAISING
    clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component.
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
    "SAPLHRXSS_PER_MAC" or "LHRXSS_PER_MACU04"
    "HRXSS_PER_CLEANUP"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "HRXSS_PER_CLEANUP" "(FUNCTION)", or its possible occurrence must be declared
    in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    System environment
    SAP-Release 700
    Application server... "ERPDEV01"
    Network address...... "10.88.1.6"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "ERPDEV01"
    Database type..... "MSSQL"
    Database name..... "DE1"
    Database user ID.. "de1"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Oct 23 2007 00:33:51"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 133
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0"
    Memory consumption
    Roll.... 16192
    EM...... 4189840
    Heap.... 0
    Page.... 0
    MM Used. 1229856
    MM Free. 2957360
    User and Transaction
    Client.............. 210
    User................ 937048
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "68211f907e6911ddbfef005056833439"
    Program............. "SAPLHRXSS_PER_MAC"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "########"
    Database Release.... 645
    Kernel Release...... 645
    Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. "###"
    User................ "############"
    Transaction......... " "
    Call Program........." "
    Function Module..... "HRXSS_PER_CLEANUP"
    Call Destination.... "<unknown>"
    Source Server....... "ERPDEV04"
    Source IP Address... "10.88.1.9"
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0
    Note: For releases < 4.0, information on the RFC caller are often
    only partially available.
    Information on where terminated
    Termination occurred in the ABAP program "SAPLHRXSS_PER_MAC" - in
    "HRXSS_PER_CLEANUP".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 13
    of the (Include) program "LHRXSS_PER_MACU04".
    The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
    procedure "HRXSS_PER_CLEANUP" "(FUNCTION)", but it was neither handled locally
    nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLHRXSS_PER_MAC "; its source code begins in
    line
    1 of the (Include program "LHRXSS_PER_MACU04 ".
    Source Code Extract
    Line
    SourceCde
    1
    FUNCTION hrxss_per_cleanup.
    2
    3
    ""Local interface:
    4
    *"  EXPORTING
    5
    *"     VALUE(MESSAGES) TYPE  BAPIRETTAB
    6
    7
    8
    CALL METHOD mac_adapter->cleanup
    9
       IMPORTING
    10
         messages = messages.
    11
    12
    TRY.
    >>>>>
    CALL METHOD xss_adapter->cleanup
    14
    15
    CATCH CX_HRPA_VIOLATED_ASSERTION .
    16
    ENDTRY.
    17
    18
    ENDFUNCTION.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    2
    SY-TABIX
    0
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC and RFC Control
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080909
    SY-UZEIT
    081916
    SY-XPROG
    SAPLHRXSS_PER_MAC
    SY-XFORM
    HRXSS_PER_CLEANUP
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    4 FUNCTION     SAPLHRXSS_PER_MAC                   LHRXSS_PER_MACU04                      13
    HRXSS_PER_CLEANUP
    3 FORM         SAPLHRXSS_PER_MAC                   LHRXSS_PER_MACU04                       1
    HRXSS_PER_CLEANUP
    2 FORM         SAPMSSY1                            SAPMSSY1                               85
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.       4 Ty.          FUNCTION
    Name  HRXSS_PER_CLEANUP
    MESSAGES
    Table[initial]
    %_DUMMY$$
    2222
    0000
    0000
    0000
    No.       3 Ty.          FORM
    Name  HRXSS_PER_CLEANUP
    SYST-REPID
    SAPLHRXSS_PER_MAC
    5454455555545544422222222222222222222222
    310C82833F052FD1300000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    %_%_MESSAGES
    Table[initial]
    No.       2 Ty.          FORM
    Name  REMOTE_FUNCTION_CALL
    %_DUMMY$$
    2222
    0000
    0000
    0000
    SY-REPID
    SAPMSSY1
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SYST-REPID
    SAPMSSY1
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    HEADER
    000000000000
    000000000000
    TYPE
    3
    0000
    3000
    SY-XPROG
    SAPLHRXSS_PER_MAC
    5454455555545544422222222222222222222222
    310C82833F052FD1300000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    RC
    0
    0000
    0000
    SY-XFORM
    HRXSS_PER_CLEANUP
    455555545544444552222222222222
    82833F052F3C51E500000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    %_SPACE
    2
    0
    0
    0
    No.       1 Ty.          MODULE (PBO)
    Name  %_RFC_START
    %_PRINT
    000                                                                                0###
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    RFCTYPE_INTERNAL
    3
    0000
    3000
    Internal notes
    The termination was triggered in function "method_call_iref"
    of the SAP kernel, in line 2207 of the module
    "//bas/700_REL/src/krn/runt/abmethod.c#8".
    The internal operation just processed is "METH".
    Internal mode was started at 20080909081916.
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=3864)
    When      : 9/9/2008 8:19:16.162
    Threads   : 2
    Computer Name       : ERPDEV01
    User Name           : SAPServiceDE1
    Number of Processors: 4
    Processor Type: AMD64 Family 15 Model 65 Stepping 2
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id d90
    FramePtr         ReturnAd         Param#1          Function Name
    0000000007d1bb20 0000000077d704bf 000000003879a800 ntdll!ZwWaitForSingleObject
    0000000007d1bbc0 0000000001722981 0000000000000180 kernel32!WaitForSingleObjectEx
    0000000007d1be10 00000000006110c5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]
    0000000007d1be40 0000000000af8e9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]
    0000000007d1be90 0000000000afe0c0 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7091)]
    0000000007d1c870 000000000081768a 0000000001adae28 disp+work!ab_rabax [abrabax.c (1231)]
    0000000007d1c8d0 0000000000830b12 0000000000000000 disp+work!method_call_iref [abmethod.c (2215)]
    0000000007d1ca50 0000000000a0bac7 0000000000000008 disp+work!ab_extri [abextri.c (554)]
    0000000007d1caa0 0000000000ac830c 0000000000000008 disp+work!ab_xevent [abrunt1.c (281)]
    0000000007d1cb30 000000000066f348 0000000000000008 disp+work!ab_dstep [abdynpro.c (492)]
    0000000007d1ccb0 0000000000672f1d 000007fe571fc890 disp+work!dynpmcal [dymainstp.c (2403)]
    0000000007d1cd40 000000000067291a 000007fe571414a0 disp+work!dynppbo0 [dymainstp.c (543)]
    0000000007d1cdf0 00000000006320d5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]
    0000000007d1fc30 00000000004d7393 0000000000000003 disp+work!dynpen00 [dymain.c (1629)]
    0000000007d1feb0 000000000042d5a6 000000000a595080 disp+work!TskhLoop [thxxhead.c (4470)]
    0000000007d1fee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1121)]
    0000000007d1ff10 00000000019c7dd1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
    0000000007d1ff70 0000000077d5964c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
    0000000007d1ffa0 0000000000000000 00000000019c7c60 kernel32!BaseProcessStart
    State Dump for Thread Id 1e0c
    FramePtr         ReturnAd         Param#1          Function Name
    000000000edffe40 0000000077d5f691 0000000007d86460 ntdll!NtFsControlFile
    000000000edffeb0 00000000018ae00f 0000000000000000 kernel32!ConnectNamedPipe
    000000000edfff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
    000000000edfff70 0000000077d6b6da 0000000077d6b6a0 msvcrt!endthreadex
    000000000edfffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    SAPMSSY1
    0
    04/11/2005
    09:27:15
    22528
    E
    1
    Prg
    SAPLSYST
    1
    02/13/2005
    17:31:56
    35840
    E
    2
    Prg
    SAPLHRXSS_PER_MAC
    2
    07/03/2008
    12:14:05
    58368
    E
    3
    Prg
    CX_SY_REF_IS_INITIAL==========CP
    3
    07/05/2005
    13:10:16
    10240
    E
    4
    Typ
    SCX_SRCPOS
    0
    05/18/2004
    14:07:11
    2048
    5
    Prg
    CX_DYNAMIC_CHECK==============CP
    5
    07/05/2005
    13:10:16
    10240
    E
    6
    Prg
    CX_ROOT=======================CP
    6
    02/06/2008
    15:43:48
    11264
    E
    7
    Prg
    CX_NO_CHECK===================CP
    7
    07/05/2005
    13:10:16
    10240
    E
    8
    Prg
    CX_SY_NO_HANDLER==============CP
    8
    07/05/2005
    13:10:16
    10240
    E
    9
    Typ
    SYST
    0
    09/09/2004
    14:18:12
    31744
    Directory of Application Tables
    Name                                     Date       Time       Lngth
    Val.
    Program  SAPMSSY1
    SYST                                       /  /       :  :     00004612
    \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0
    ABAP Control Blocks (CONT)
    Index
    Name
    Fl
    PAR0
    PAR1
    PAR2
    PAR3
    PAR4
    PAR5
    PAR6
    Source Code
    Line
    243
    FUNC
    03
    001F
    LHRXSS_PER_MACU03
    1
    244
    PAR2
    02
    0000
    001F
    C000
    LHRXSS_PER_MACU03
    1
    246
    FUNC
    13
    0003
    LHRXSS_PER_MACU03
    1
    247
    PAR2
    01
    0000
    0014
    C001
    LHRXSS_PER_MACU03
    1
    249
    FUNC
    FF
    0000
    LHRXSS_PER_MACU03
    1
    250
    ENDF
    00
    0000
    LHRXSS_PER_MACU03
    1
    251
    00
    0000
    LHRXSS_PER_MACU03
    1
    252
    STCK
    02
    C001
    LHRXSS_PER_MACU03
    1
    253
    CPOP
    00
    0000
    LHRXSS_PER_MACU03
    1
    254
    00
    0000
    LHRXSS_PER_MACU03
    1
    255
    FUNP
    3E
    0000
    0014
    8000
    0000
    8000
    0000
    0000
    LHRXSS_PER_MACU04
    1
    259
    FUNP
    80
    0000
    0000
    0000
    0000
    0000
    0000
    0000
    LHRXSS_PER_MACU04
    1
    >>>>>
    METH
    03
    0000
    0000
    8006
    0000
    0000
    0000
    0000
    LHRXSS_PER_MACU04
    13
    267
    PAR2
    00
    0000
    0001
    0000
    LHRXSS_PER_MACU04
    13
    269
    FUNE
    00
    0000
    LHRXSS_PER_MACU04
    18
    270
    00
    0000
    LHRXSS_PER_MACU04
    18
    271
    PERP
    00
    0000
    LHRXSS_PER_MACU04
    1
    272
    FUNC
    03
    E844
    LHRXSS_PER_MACU04
    1
    273
    FUNC
    03
    0020
    LHRXSS_PER_MACU04
    1
    274
    FUNC
    13
    0003
    LHRXSS_PER_MACU04
    1
    Second Dump
    Runtime Errors         DYNPRO_SEND_IN_BACKGROUND
    Date and Time          09/09/2008 08:19:15
    Short text
    Screen output without connection to user.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSTRD" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    During background processing, the system attempted to send a
    screen to a user.
    Current screen: "SAPLSTRD " 0351.
    How to correct the error
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove the error.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DYNPRO_SEND_IN_BACKGROUND" " "
    "SAPLSTRD" or " "
    "SYSTEM-EXIT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "ERPDEV01"
    Network address...... "10.88.1.6"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "ERPDEV01"
    Database type..... "MSSQL"
    Database name..... "DE1"
    Database user ID.. "de1"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Oct 23 2007 00:33:51"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 133
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0"
    Memory consumption
    Roll.... 16192
    EM...... 12569520
    Heap.... 0
    Page.... 131072
    MM Used. 8307376
    MM Free. 4259072
    User and Transaction
    Client.............. 210
    User................ 937048
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "68211f907e6911ddbfef005056833439"
    Program............. "SAPLSTRD"
    Screen.............. "SAPLSTRD 0351"
    Screen Line......... 0
    Information on caller of Remote Function Call (RFC):
    System.............. "########"
    Database Release.... 645
    Kernel Release...... 700
    Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Nam

    Hello Abhiram,
    Please i request weather you have assign 0105 - Communication infotype to ESSuser and
    check the following JCos has been configured.
    SAP_R3_Financials
    SAP_R3_Financials_Metadata
    SAP_R3_HumanResources
    SAP_R3_HumanResources_MetaData
    SAP_R3_SelfServiceGenerics
    SAP_R3_SelfServiceGenerics_MetaData
    SAP_R3_Travel
    SAP_R3_Travel_MetaData
    SAP_R3_SelfServiceGenerics_MetaDataFIN
    SAP_R3_SelfServiceGenericsFIN
    let me know this
    points if problem solved
    please close thread if problem solved
    thanksyou,
    regards
    Vijai

  • Error in output determination via collective billing VF06

    Hi,
    We are facing error in output determination when collective billing is done. Multiple Orders numbers are entered in VF06 and processed to generate billing documents. VF06, which is used for batch billing, creates a batch job which internally calls VF04 to do this. For some of the invoices generated from the documents, we do not have anything in the Output, i.e. when we open the invoices in VF03 and go to Goto->Header ->Output, nothing appears.
    Say out of the 5 documents, 2 should have output determined and 3 do not. Then we see that it appears for either of the 2 or does not appear at all.
    This does not happens when the documents are processed one by one in VF04. We have to do collective billing and generate one invoice for each document. The condition records are also maintained correctly.
    Regards,
    Tarun

    Go to some of the invoices on which no output has appeared in change mode and do a output determination analysis in Go to Header-Output and then Ouptut Determinatino analysis.
    Please do this analysis for atleast 10 problamatic invoices. This will give yousome insight into the problem

  • Quicktime Export Error: "An output module stopped responding."

    I'm experiencing an odd export error whenever I use any Quicktime codecs:
    "After Effects error: An output module stopped responding. The file may be damaged or corrupted. You may need to restart After Effects."
    Similarly, Adobe Media Encoder hangs when outputting to Quicktime codecs. Neither program makes any progress at all before the hang occurs. At that point, I have to manually "end task" to exit. Also, it doesn't seem to matter what I try to export. In AME, for example, I can simply try to convert one video format to another and have it hang, so I don't think the problem is due to a problem with the source settings or effects. Also, I'm not attempting any multiprocessing since I don't really have enough RAM for that. Other output modules work, so I'm just exporting image sequences for the time being.
    System specs:
    Windows 7 64-bit
    Intel i7-2600k processor
    8 GB RAM
    GTX 580 GPU
    Software:
    Adobe CS6
    AE Plugins include Tracode Suite 12 and Optical Flares
    Quicktime 7.7.3
    Any thoughts on this? I've seen very few references to this error in other places, and not really found a solution that seems to apply to my situation. Thanks in advance for your help.
    Josh

    Thanks for setting me in the right direction. Clicking through to the 25 :: 101 error page (http://myleniumerrors.com/2013/01/06/25-101-4/) led me to a reference about other software, such as remote access software, using the same ports that AE needs for communication with its various processes. In my case, LogMeIn was the culprit. I had no idea that AE even used TCP for these types of operations, so that's very helpful to know.
    *EDIT*
    That worked temporarily, and now it doesn't work. I ran into a similar effect when I first disabled the Windows Firewall. But of course, as I type this and piddle around, it works again. It SEEMS like if I open AME and click into the output settings and scrub through the video preview, it makes everything work when I go to actually export. That's exactly the type of thing I would say is completely unrelated under normal circumstances, but at the moment all I know is that it is currently working and I don't want to test anything else until I finish the rendering I need to accomplish today. I'll work on it more later and post an update at that time.
    Thanks,
    Josh

  • Error message during processing in BI

    1.i am loading the data into infoobject.
    2.got error in text data load.
    3.master info object have compound obj 0COUNTRY
    4.and other normal fields are 0TXTSH,0LANGU,sold-to-party.
    5.there is no PSA in this..its direct update to INFOobject.
    The error message is:
    Error message during processing in BI
    Diagnosis
    An error occurred in BI while processing the data. The error is documented in an error message.
    System Response
    A caller 01, 02 or equal to or greater than 20 contains an error meesage.
    Further analysis:
    The error message(s) was (were) sent by:
    Update
    Diagnosis
    There are duplicates of the data record 2. with the key '3.' for characteristic 1..
    Procedure
    If this message appears during a data load, maintain the attribute in the PSA maintenance screens. If this message appears in the master data maintenance screens, leave the transaction and call it again. This allows you to maintain your master data.

    Hi KP,
    In the details tab,
    1.under Transfer (IDOC and Trfc):
       Data Package 1 : arrived in BW ; Processing : Error records written to application log
    2.Processing (data packet): Errors occurred
       Update ( 0 new / 0 changed ) : Errors occurred
       Error records written to application log
       0TRZONE : Data record 1 ('0000000001D ') : Duplicate data record
       0TRZONE : Data record 2 ('0000000002D ') : Duplicate data record
       Error 4 in the update
    3. Process chain error
    these are the error details.

  • 500   Internal Server Error Failed to process request in portal

    Hi ,* We face problems to run Dev and Qual systems on our Sap portal devices. Production is OK The error message (see hereafter) does not occur on welcome page but on any page that communicate by Web Dynpro with ECC SAP system 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, ... com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'SSOL_WS_METADATA_DEST' and WS interface 'ZGetListCustomerAgent'. One possible reason is that the metadata destination 'SSOL_WS_METADATA_DEST' has not been properly configured; check configuration. at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:440) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248) at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.(WSTypedModel.java:41) at com.bluestarsilicones.ssol.models.customer.WS_GetListCustomersForAgentModel.(WS_GetListCustomersForAgentModel.java:53) at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.initalListCustomerAgentModel(OrderCreationComponent.java:587) at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.initalModels(OrderCreationComponent.java:555) at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.wdDoInit(OrderCreationComponent.java:193) at com.bluestarsilicones.ssol.wd.ordercreation.wdp.InternalOrderCreationComponent.wdDoInit(InternalOrderCreationComponent.java:943) 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:430) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) 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:869) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229) at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344) at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356) at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549) at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193) at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150) 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:430) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) 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:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) 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(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:157) at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.(DGenericServiceImpl.java:56) at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:88) at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:141) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:429) ... 60 more Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Proxy generation problem. See nested exception. at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:284) at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:154) ... 64 more Caused by: java.io.IOException: Compilation fails... Compilation process error : Not enough space at com.sap.engine.services.webservices.jaxrpc.util.Compiler.compile(Compiler.java:53) at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compileExternal(PackageBuilder.java:328) at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.traversThrough(PackageBuilder.java:291) at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compileExternal(PackageBuilder.java:485) at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compilePackage(PackageBuilder.java:215) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:271) ... 65 more Thanks for your help. TY.

    Hi,
    I think you are accessing the portal via one of the dialog instance and not using the Central instance.So you are not getting the error displayed in iview. If you want to activate navigate to system administration-system configuration-services and in portal runtime central configuration open the object and in portal .runtime .print cause .exception make it to true and restart the service. This may be for print but some where here in the services you can activate that.
    For productive environment detailed exception is not recommended.Administrator can see the error log in
    log files.
    Thanks and regards,
    gopal.sattiraju

  • Socket Adapter Request-Reply ~ Error occured in processing client request ~

    Dear Friends,
    Need your help in resolving a Issue regarding Socket Adapter Request/Reply.
    We have a requirement to recieve Message from a External Vendor using Socket based communication,to achieve this Created a Process which has Socket Adapter Inbound Synchronous Request-Reply. I have also created a sample Outbound Service to test and it was able to send & Receive Message Sucessfuly .
    When i try to Recieve a Message from the External Vendor on Port 8008 in this I am unable to receive the message(No Bpel Instance Created) message coming to the SOA Server, in the logs I can see Below Error-
    Socket Adapter ClientProcessor:run() Error occured in processing client request
    Socket Schema Translation Error.
    Error while trying to translate from native.
    Please ensure that the schemas are set up with native annotations and comply with the output XML. Contact Oracle support if error is not fixable.
    Pls. find my Input XSD Below-
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
    xmlns:tns="http://TargetNamespace.com/InboundService"
    targetNamespace="http://TargetNamespace.com/InboundService"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified"
    nxsd:version="NXSD"
    nxsd:stream="chars"
    nxsd:encoding="US-ASCII"
    >
    <xsd:element name="R1">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="C1" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" nxsd:quotedBy="&quot;" />
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    Sample Incoming Message-
    <?xml version="1.0" encoding="UTF-8"?>
    <ExitRequest>
    <ExitRequestID>1234</ExitRequestID>
    <Timestamp>28-11-2012 01:19:11</Timestamp>
    <ActiveTagData>23456</ActiveTagData>
    <DriverID>5555</DriverID>
    <LicensePlate>6546</LicensePlate>
    <DriverName> Sujit Nair</DriverName>
    <DriverDOB>06-06-2012</DriverDOB>
    <DriverEmployer>Testing</DriverEmployer>
    <DriverSex>Male</DriverSex>
    <DriverLang>ENGLISH</DriverLang>
    <DriverNationality>TEST</DriverNationality>
    <LaneID>Gate Testing</LaneID>
    <CardReaderID>07700</CardReaderID>
    </ExitRequest>
    Can anyone pls. help me on this , still not able to understand what I am doing wrong. Pls. let me know if any other details required.
    Thanks,
    Sujit Nair

    Hi,
    You don't need a NSXD (Native Format Builder) to receive a message that is XML already, and the NXSD you listed above has nothing to do with the sample incoming message. So, no surprises it is complaining "Error while trying to translate from native.".
    You have to fix the incoming message element on the Socket Adapter.
    Cheers,
    Vlad

  • Errors in the OLAP storage engine: An error occurred while processing the indexes for the partition of the measure group of the cube from the database.

    Errors in the OLAP storage engine: An error occurred while processing the indexes for the partition of the measure group of the cube from the database.
    I have dropped and recreated a fact table to refresh the data as the table is having identity columns. So not able to directly insert data. After that cube is throwing above error.
    Please suggest.

    Hi Md,
    It hard to analyse the issue base on the limited information, Are there any error message on the log? Under C:\Program Files\Microsoft SQL Server\MSAS11.\OLAP\Log (this could be different for your server), there are 3 log files that are generated:
    msmdrrv.log
    FlightRecorderCurrent.trc
    FightRecorderBack.trc
    The msmdrrv.log simply points to the other two logs. There might be some detail information for this error. Please provide us the detail information about it, so that we can make further analysis.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Getting Date error when I process

    Hi All,
    I have DEV & QA Analysis services on 2 different server. This is 2005 SSAS
    I am using same solution so DEV process OK but QA gives me date error
    when  I check with SSMS , date fields  look fine .
    But I am getting this error in QA
    Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_view_ftblCharge, Column: SrvDateKey, Value: 12/13/2005. Errors in the OLAP storage engine: The record
    was skipped because the attribute key was not found. Attribute: Date of Dimension: Service Date from Database: Charges, Cube: Charges, Measure Group: Charges, Partition: Charges, Record: 1. Errors in the OLAP storage engine: The process operation ended because
    the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while processing the 'Charges' partition of the 'Charges' measure group for the 'Charges'
    cube from the Charges database
    Thanks,
    Gok

    12/13/2005 is an American date format (mm/dd/yyyy) whereas you need a british date format 13/12/2005 (dd/mm/yyyy).
    Have a look at this topic on how you can force the correct collation (date format)
    http://sqlmag.com/blog/forcing-collation-where-clause-22-jun-2011
    Please click "Mark As Answer" if my post helped. Tony C.

  • Errors in the OLAP storage engine: An error occurred while processing the 'vFactUTC_201304_INCR_UPDATE_TEMP_qtfcw_' partition of the 'vFact' mea

    <Error
    ErrorCode="3240034318"
    Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFactUTC_201304_INCR_UPDATE_TEMP_qtfcw_' partition of the 'vFact' measure
    group for the 'vAMGenericUTC' cube from the AC_OLAP database."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
    Any idea abt this error
    Putting details error ..
    <return
    xmlns="urn:schemas-microsoft-com:xml-analysis">
      <results
    xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults">
        <root
    xmlns="urn:schemas-microsoft-com:xml-analysis:empty">
          <Exception
    xmlns="urn:schemas-microsoft-com:xml-analysis:exception"
    />
          <Messages
    xmlns="urn:schemas-microsoft-com:xml-analysis:exception">
            <Error
    ErrorCode="3238395904"
    Description="OLE DB error: OLE DB or ODBC error: Cannot execute the query
    &quot;SELECT
    &quot;Tbl1002&quot;.&quot;idUTCDateTime&quot;
    &quot;Col1145&quot;,&quot;Tbl1002&quot;.&quot;idLocalDateTime&quot;
    &quot;Col1146&quot;,&quot;Tbl1002&quot;.&quot;idDateKey&quot;
    &quot;Col1147&quot;,&quot;Tbl1002&quot;.&quot;idUTCDateKey&quot;
    &quot;Col1148&quot;,&quot;Tbl1002&quot;.&quot;idMinuteKey&quot;
    &quot;Col1149&quot;,&quot;Tbl1002&quot;.&quot;idUTCMinuteKey&quot;
    &quot;Col1150&quot;,&quot;Tbl1002&quot;.&quot;idInstance&quot;
    &quot;Col1151&quot;,&quot;Tbl1002&quot;.&quot;idMetricKey&quot;
    &quot;Col1152&quot;,&quot;Tbl1002&quot;.&quot;idKSKey&quot;
    &quot;Col1153&quot;,&quot;Tbl1002&quot;.&quot;idMaintenanceKey&quot;
    &quot;Col1154&quot;,&quot;Tbl1002&quot;.&quot;MetricMin&quot;
    &quot;Col1155&quot;,&quot;Tbl1002&quot;.&quot;MetricMax&quot;
    &quot;Col1156&quot;,&quot;Tbl1002&quot;.&quot;MetricCount&quot;
    &quot;Col1157&quot;,&quot;Tbl1002&quot;.&quot;MetricSum&quot;
    &quot;Col1158&quot;,&quot;Tbl1002&quot;.&quot;MetricLog&quot;
    &quot;Col1159&quot;,&quot;Tbl1002&quot;.&quot;MetricSumOfSquares&quot;
    &quot;Col1160&quot;,&quot;Tbl1002&quot;.&quot;MetricSumOfLogSquares&quot;
    &quot;Col1161&quot;,&quot;Tbl1002&quot;.&quot;idTextData&quot;
    &quot;Col1162&quot;,&quot;Tbl1002&quot;.&quot;idLoad&quot;
    &quot;Col1143&quot;,CONVERT(smalldatetime,&quot;Tbl1002&quot;.&quot;idDateKey&quot;,0)
    &quot;Expr1004&quot;,CONVERT(smallint,&quot;Tbl1002&quot;.&quot;idMinuteKey&quot;,0)
    &quot;Expr1006&quot;,(1)
    &quot;Expr1008&quot; FROM
    &quot;DM_VSQL51_SOPM33_QDB&quot;.&quot;dbo&quot;.&quot;vData&quot;
    &quot;Tbl1002&quot; WHERE
    &quot;Tbl1002&quot;.&quot;idLocalDateTime&quot;&gt;=(1362096000)
    AND &quot;Tbl1002&quot;.&quot;idLocalDateTime&quot;&lt;=(1364774399)
    AND &quot;Tbl1002&quot;.&quot;idLoad&quot;&gt;=(9243)
    AND &quot;Tbl1002&quot;.&quot;idLoad&quot;&lt;=(9304)&quot;
    against OLE DB provider &quot;SQLNCLI10&quot; for linked server
    &quot;DM_DS_SOPM33_QDB&quot;. ; 42000; The OLE DB provider
    &quot;SQLNCLI10&quot; for linked server
    &quot;DM_DS_SOPM33_QDB&quot; reported an error. Execution terminated by the provider because a resource limit was reached.;
    42000." Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3240034318"
    Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFact_201303_INCR_UPDATE_TEMP_he3dx_' partition of the 'vFact' measure
    group for the 'vAMGeneric' cube from the AC_OLAP database."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3238002695"
    Description="Internal error: The operation terminated unsuccessfully."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3238002695"
    Description="Internal error: The operation terminated unsuccessfully."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3239837698"
    Description="Server: The operation has been cancelled."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3238395904"
    Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3240034318"
    Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFact_201304_INCR_UPDATE_TEMP_kq5tw_' partition of the 'vFact' measure
    group for the 'vAMGeneric' cube from the AC_OLAP database."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3238002695"
    Description="Internal error: The operation terminated unsuccessfully."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3238002695"
    Description="Internal error: The operation terminated unsuccessfully."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3238395904"
    Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3240034318"
    Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFactUTC_201304_INCR_UPDATE_TEMP_qtfcw_' partition of the 'vFactUTC'
    measure group for the 'vAMGenericUTC' cube from the AC_OLAP database."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3238002695"
    Description="Internal error: The operation terminated unsuccessfully."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
            <Error
    ErrorCode="3238002695"
    Description="Internal error: The operation terminated unsuccessfully."
    Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
          </Messages>
        </root>
      </results>
    </return>

    against OLE DB provider
    &quot;SQLNCLI10&quot; for linked server
    &quot;DM_DS_SOPM33_QDB&quot;. ; 42000; The OLE DB provider
    &quot;SQLNCLI10&quot; for linked server
    &quot;DM_DS_SOPM33_QDB&quot; reported an error. Execution terminated by the provider because a resource limit was reached.;
    42000." Source="Microsoft SQL Server 2008 Analysis Services"
    HelpFile="" />
    Hi Born,
    Have you check your disk space? This issue might be caused by not enougl disk sapce. Here is a similar thread about this topic:
    http://social.technet.microsoft.com/Forums/en-US/sqlanalysisservices/thread/1783c640-5d4d-4086-bbdc-05adc45e3816/
    If you have any feedback on our support, please click
    here.
    Regards,
    Elvis Long
    TechNet Community Support

  • "Caller 09 contains an error message "in Process chain

    Hi
    Most of my process chains have failed today.All are showing the same error i.e
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System Response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Extractor .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
    If I am repeating the process it is showing the same error again
    Please help

    Hi,
    Even I got the same problem. All you need to do is:
    1) Go to Infopackage
    2) Update Tab:
        Choose: Initialize Delta process
            under that choose: Initialization with Data Transfer
    3) Save
    4) Go to Schedule Tab:
    5) Start the Load
    6) Refresh the page: /nRSA1
    7) Once it is done, then again go to the Update tab of the Infopackage
    8) Select Delta Update
    9) Save
    And now run the Process Chain.
    You should be able to run it smoothly.
    Thanks & Regards
    Hemendra Sharma

  • ERROR: TF246021: An error occurred while processing your request.

    Since last week the CI build on our integration branch fails when setting the label for the branch, I tried to create a new (default) build definition, which fails with the same error. Any other branch can build successful.  We get the following error:
    Exception Message: TF246021: An error occurred while processing your request.
    Technical information (for administrator):
    SQL Server Error: 2601 (type VersionControlException)
    Exception Stack Trace: 
    Server stack trace: 
       at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.HandleReply(TfsClientOperation operation, TfsMessage message, Object[]& outputs)
       at Microsoft.TeamFoundation.VersionControl.Client.Repository5.LabelItem(String workspaceName, String workspaceOwner, VersionControlLabel label, LabelItemSpec[] labelSpecs, LabelChildOption children, Int32 maxClientPathLength, Failure[]& failures)
       at Microsoft.TeamFoundation.VersionControl.Client.WebServiceLayer.LabelItem(String workspaceName, String workspaceOwner, VersionControlLabel label, LabelItemSpec[] labelSpecs, LabelChildOption children, Failure[]& failures)
       at Microsoft.TeamFoundation.VersionControl.Client.VersionControlServer.CreateLabel(VersionControlLabel label, LabelItemSpec[] itemSpecs, LabelChildOption options, Failure[]& failures)
       at Microsoft.TeamFoundation.Build.Workflow.Activities.TfLabel.TfLabelInternal.RunCommand(VersionControlScope versionControlScope, String nonFatalError, VersionControlLabel label, IEnumerable`1 items, LabelChildOption childOption)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
       at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
       at System.Func`6.EndInvoke(IAsyncResult result)
       at Microsoft.TeamFoundation.Build.Workflow.Activities.TfLabel.TfLabelInternal.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
       at System.Activities.AsyncCodeActivity`1.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)
       at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
    Inner Exception Details:
    Exception Message: TF246021: An error occurred while processing your request.
    Technical information (for administrator):
    SQL Server Error: 2601 (type SoapException)SoapException Details: <soap:Detail xmlns:soap="http://www.w3.org/2003/05/soap-envelope" />
    Exception Stack Trace:
    When I manually create a Label on the branch it works fine, please advice?
    additional information: 
    By changing "Label sources" to false the build does complete. Does SQL Server Error: 2601 indicate a duplicate key error in the TFS database? 
    (Cannot insert duplicate key row in object '%.*ls' with unique index '%.*ls'.)
    see also: https://technet.microsoft.com/en-us/library/aa258747(v=sql.80).aspx

    Hi,
    For this issue, you can check if you can connect to TFS and perform operations on other client machines. If yes, the problem related to your environment.
    You can also delete the current workspace and cretea a new one, then do a workspace mapping. To delete the workspace, use tf workspace or delete it via Team Explorer. If the problem still exist, please let us know your environment, settings etc. for further
    investigation.
    Best regards,

  • 500   Internal Server Error Failed to process request

    Hi ,
    We face problems to run Dev and Qual systems on our Sap portal devices. Production is OK
    The error message (see hereafter) does not occur on welcome page but on any page that communicate by Web Dynpro with ECC SAP system
    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, ...
    com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'SSOL_WS_METADATA_DEST' and WS interface 'ZGetListCustomerAgent'. One possible reason is that the metadata destination 'SSOL_WS_METADATA_DEST' has not been properly configured; check configuration.
            at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:440)
            at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
            at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
            at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)
            at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)
            at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)
            at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)
            at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
            at com.bluestarsilicones.ssol.models.customer.WS_GetListCustomersForAgentModel.<init>(WS_GetListCustomersForAgentModel.java:53)
            at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.initalListCustomerAgentModel(OrderCreationComponent.java:587)
            at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.initalModels(OrderCreationComponent.java:555)
            at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.wdDoInit(OrderCreationComponent.java:193)
            at com.bluestarsilicones.ssol.wd.ordercreation.wdp.InternalOrderCreationComponent.wdDoInit(InternalOrderCreationComponent.java:943)
            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:430)
            at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
            at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
            at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
            at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
            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:869)
            at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
            at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
            at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
            at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
            at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
            at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
            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:430)
            at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
            at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
            at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
            at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
            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:386)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
            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(Native Method)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
            at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:157)
            at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:56)
            at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:88)
            at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:141)
            at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:429)
            ... 60 more
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Proxy generation problem. See nested exception.
            at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:284)
            at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:154)
            ... 64 more
    Caused by: java.io.IOException: Compilation fails...
    Compilation process error : Not enough space
            at com.sap.engine.services.webservices.jaxrpc.util.Compiler.compile(Compiler.java:53)
            at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compileExternal(PackageBuilder.java:328)
            at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.traversThrough(PackageBuilder.java:291)
            at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compileExternal(PackageBuilder.java:485)
            at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compilePackage(PackageBuilder.java:215)
            at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:271)
            ... 65 more
    Thanks for your help.
    TY.

    Hi,
    Please check the following,
    1. JCO connections are configured properly and working fine.
    2. Check the SLD connection is successful.
    3. System definition is available for the ECC system.
    Thanks.
    Sushil

Maybe you are looking for

  • Install library receipts from a MacBook Pro onto a Mac Mini PPC

    I have a pay per Mbyte internet connection at home, but unlimited internet where I work. I am hoping to install updates on the MacBook Pro at work and keep the receipt .pkg files and install them on the Mac Mini PPC at home so I don't have to pay for

  • Oracle Streams PIT on Source DB

    I'm testing backup/recovery in my streams environment, simulating a PITR on the source. The objective is to get both the source and destination to the same point in time, driven by the source. That being said, if recover to a time 5 hours prior, on b

  • I am using Elements 10.

    For some reason i keep loosing the installed templates. Any ideas what would be causing this? When I go to reinstall, I am given yhe message that thet are installed.

  • Creating IP which doesn't link RTL / uses netlist

    Hi, I created IP for my project in Vivado and it contains the source code.  I am looking for a way of creating IP where it is just a netlist and doesn't have the source code linked (so I can give it to third parties to use without them knowing the so

  • Nationwide Waste of Time Day

    How do you report misuse these days. As you will doubtless have noticed, some spam has crept into our revered forum. But how to get someone to get rid of it?