Task ALE/EDI: Error handl cannot be started immediately

When an IDOC is being created in SAP(3.1I) from an external system(Gentran GIS), it is added with errors status 56. The error text states as 'Task ALE/EDI: Error handl cannot be started immediately
'The task ALE/EDI: Error handl (no. TS00008068) cannot be started immediately by user GIS'.
Can anyone advise where the user 'GIS' need to be added to avoid getting that IDOC error

Hi Bhaskara,
This can be caused by several issues:
1. The user GIS has NO authorization to run workflows or to run this specific workflow task (TS00008068).
2. The user GIS has NO authorization to run function module EDI_ROLE_FOR_PROCESSING (or when running this function module it will return data in the ACTOR_TAB, which means that the workflow cannot be started by default users).
3. Within the partnerprofile (transaction WE20) at the specific inbound parameters for the message on the tab "Post processing: permitted agent) an agent has been defined that will not resolve to the user GIS (and therefore this user is NOT allowed to do post processing).
Most likely issue 3 is here at hand. If this is the case, REMOVE the entry for the agent (or consider to setup an organisational unit/work center and make GIS a member).
The error, by the way, is an inbound processing error. It is possible that in the ALE layer something has not been defined properly.
Within the partnerprofile (transaction WE20) at the specific inbound parameters for the message on the tab "Inbound options" and double-click on the entered Process code.
You must now check the entries here.
Example:
If you use an own function module (named in the Identification field) you must set the radio buttons to Processing with ALE service AND Processing by function module. The little button behind the identification field will show some details.
At least the detail fields (on tab IDoc) Object type, Start event and End event must be filled.
Default values for these are: IDOCAPPL (=Object type), INPUTERROROCCURRED (=Start event) and ERRORPROCESSCOMPLETD (=End event).
Of course within ALE you can define different types of process codes (what you like most for your specific handling).
Hope this helps you a bit on your way.
Regards,
Rob.

Similar Messages

Steps for ALE/EDI error handling using workflow

Hi
I need to handle errors in outbound IDoc generation using workflow. Can you please let me know the steps to be used for this. Step-by-step answer would be appreciated.
Thanks

Seetha,
I have this already..
IDOCPACKET
Object type                         IDPKWMMBXY
End event                           MASSINPUTFINISHED
IDOC
Object type                         IDOCWMMBXY
Start event                         INPUTERROROCCURRED
End event                           INPUTFINISHED
Application object
Object type                         BUS2017
Start event

ALE Inbound Error Handling

Hi
Here I have problem in setting up Error handling in outbound/inbound processing of Idocs in ALE....
Can any one please explain how to do it....
My requirement is, if ever idoc goes in to error then the user has to be intimated by mail in SAP Inbox.As per my knowledge it can be done through partner profile...if specify user name in partner profiles/post processing agent place.
My doubt is will it be same in outbound/Inbound?
Do i need to do anything other than specifying usernames in partner profiles?
What is the use of Idoc Administrator?
Please explain how to do that....
Awaiting your valuable answers...
Thanks
Suresh
Message was edited by: Suresh Babu Mannem

I think you also need to specify the "post processing agent" in your Partner profile - Message Type.
Check WE20.
In case you don't want to use organizational assignment then leave the task as it is as general task.
So only the user specified in "post processing agent" will be taken into consideration.
Here are the steps that you need to do for a complete error handling procedure ( but you can avoid organizational assignment if you just need to use User Name as receipient ):
I've taken it from F1 help on error handling:
Error Handling
In this section, you can make the settings for error handling:
Create organizational units and assign standard tasks
Maintain EDI administration ( Idoc administrator section on Xn OYEA or We40 )
Maintain error process code ( Xn OYEA or We40 )
Further you can check it using Verification Processing on OYEA / WE40 .
Errors are processed in the system in which the error occurred.
You can repost IDocs that were not posted (with status 51) using program RBDMANIN.
Requirements
ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
Workflow functions as follows:
A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
If an error occurs, the system determines:
1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
Activities
Create organizational units and assign standard tasks
Maintain EDI administration
Maintain error process code
If you used EDI communication in an earlier version, you can check the assignment of error process codes to the standard tasks.
Check names of the employees responsible in the partner profiles.

IDOC scenario: MATMAS02 (Application document not posted ALE/EDI errors)

Hi!
I am almost ready with with my first File to Idoc scenario and having the following error.
(Idoc of type MATMAS.MATMAS02)
The IDOC will be received on business system B.
Unfortunately the following errors come in tcode BD87 or MM90
Enter a material type
Message no. M3098
No material number transferred
Message no. M3752
Can some one help me to trace and solve this problem?
Thank you very much!
regards
Holger

Hi!
I corrected the error!
Now the Idoc has the status "yellow" which mean "IDOC ready to be transformed to application".
Is that still an error/warning or is everything is ok?
I mean does some background job started and create a material from this IDoc?
I loooked into tcode MM03 and cannot unfortunately detect any new materials....
kein Filtern , kein Umsetzen , kein Versionswandel .
Message no. B1005
In Log I could find:
IDoc successfully processed in the ALE layer
The IDoc has passed through the ALE layer successfully and can now be passed to the application. This transfer is either done online or as a background job, depending on the settings in the partner profile.
If there are no further status records, the IDoc waits for the next run of the transfer report to the application.
Success or failure when passing the IDoc to the application is documented in the subsequent status records.
Actions in the ALE layer
The parameter 'kein Filtern' indicates whether the processing in the ALE layer led to segments of the inbound IDoc being omitted. The important criteria here are the settings in the segment filter and in the distribution model for this sender.
The parameter 'kein Umsetzen' indicates whether field values were converted in the ALE layer. This is the case if the IDoc contains organizational units to be converted, or if the ALE conversion tool for this sender is activated.
The parameter 'kein Versionswandel' indicates whether the IDoc was converted into an earlier version of the IDoc type. This happens if the IDoc type of the sender is different from its own IDoc type.
Holger

503 Service Unavailable Error: Application cannot be started!

Hi Experts,
   I have NWE 7.11 SP 01 installed . While try to update to SP04, the server restarted automatically & when i try to access the portal link http:<host>:<port>/irj/portal am getting err as 503 service unavailable. I am able to see irj, JMS_Provider,tcjewebservice_srv,tcwddispwda services in failed state. Please help me out.
   I got the log file in dev_server0 as follows
[Thr 1122040128] *** ERROR => NiHsLGetNodeAddr: NiPGetHostByName failed (rc=-1) [nixxhsl.cpp 308]
[Thr 1122040128] *** ERROR => NiHsLGetHostName: NiPGetHostByAddr failed (rc=-1) [nixxhsl.cpp 507]
M [Thr 1211640128] Mon Jul 4 11:44:31 2011
M [Thr 1211640128] ***LOG Q0I=> NiPConnect2: 172.20.50.242:3300: connect (111: Connection refused) [nixxi.cpp 3150]
M [Thr 1211640128] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 31/sock 92
    (SI_ECONN_REFUSE/111; I4; ST; 172.20.50.242:3300) [nixxi.cpp    3150]
2.#2011 07 04 15:02:37:289#+0530#Error#/System/Server#
#BC-JAS-JMS#jms#001A6406631A001F0000001800002B3A#4513750000000005##com.sap.jms.server.JMSServerFrame####4083D980A61D11E0842E001A6406631A#4083d980a61d11e0842e001a6406631a#4083d980a61d11e0842e001a6406631a#0#Services Start Processor#Plain##
An error occurred starting the jms_provider service. The applications using JMS resources may not work as expected. For more details, refer to the trace file.#
#2.#2011 07 04 15:02:37:290#+0530#Error#/System/Server#
com.sap.ASJ.krn_srv.000059#BC-JAS-JMS#sap.com/jms_provider#001A6406631A001F0000001B00002B3A#4513750000000005##com.sap.engine.core.service630.container.ServiceRunner####4083D980A61D11E0842E001A6406631A#4083d980a61d11e0842e001a6406631a#4083d980a61d11e0842e001a6406631a#0#Services Start Processor#Java#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
Service [{0}] error. Nested exception is: [{1}]#2#jms_provider#java.lang.NoClassDefFoundError: com/sap/engine/services/rmi_p4/interfaces/LocalRemoteByRef
------------------------- Loader Info -------------------------
ClassLoader name: [service:jms_provider]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [library:core_lib]
   [library:j2eeca]
   [service:timeout]
   [service:naming]
   [service:cross]
   [service:dbpool]
   [service:jmx]
   [service:security]
Resources:
   /usr/sap/CEP/J00/j2ee/cluster/bin/services/jms_provider/lib/private/sap.com~tc~je~jms_provider~impl.jar
Error occurred while trying to load com.sap.jms.server.remote.JMSRemoteServerImpl#
#2.#2011 07 04 15:02:37:296#+0530#Error#/System/Server/Services/Deploy#
com.sap.ASJ.dpl_ds.002038#EP-PIN-PRT#sap.com/irj#001A6406631A00520000000300002B3A#4513750000000003##com.sap.engine.services.deploy#Guest#0##4083D980A61D11E0842E001A6406631A#4083d980a61d11e0842e001a6406631a#4083d980a61d11e0842e001a6406631a#0#Thread[HTTP Worker [@1593095773],5,Dedicated_Application_Thread]#Java#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
Global operation [{0}] over [{1}] [{2}] finished with errors for [{3}]ms on server [{4}]#2#500#true#
#2.#2011 07 04 15:02:37:298#+0530#Warning#/System/Server/WebRequests#
com.sap.ASJ.web.000132#BC-JAS-WEB#servlet_jsp#001A6406631A00520000000500002B3A#4513750000000003##com.sap.engine.services.servlets_jsp.server.DeployContext#Guest#0##4083D980A61D11E0842E001A6406631A#4083d980a61d11e0842e001a6406631a#4083d980a61d11e0842e001a6406631a#0#Thread[HTTP Worker [@1593095773],5,Dedicated_Application_Thread]#Java#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
Error occurred during retrieving web module context needed for 'Lazy' startup of [irj] web module.
For more details on the problem please check traces searching by logId: null#
Thanks,
Arun

Hi,
NiPGetHostByName failed
NiPGetHostByAddr failed
Looks like network related issue. Make sure the server is in the network and has proper hostname to IP address mapping maintained.
SiPeekPendConn failed 172.20.50.242:3300
Next check if the port 3300 is free using the netstat command.
Regards,
Srikishan

ALE outbound error handling

Hi gurus,
I've implemented some ALE systems successfuly. I mean the distribution of information is alright but, now, I want to get some notification when any outbound error occurs.
I,ve filled the 'Post processing: permited agent' tab in the partner profile (both for partner and message type) but it doesn't work. I suppose I need to do something else.
Can anybody help me with this matter?
Thank you in advance.
JM Parra.

Hi,
Just an added information
Message Type : ALEAUD,is present which is used to give successful notification/confirmation in case of the posting of the IDocs, this Message type should be configured on the inbound side( Partner Profile and the Distribution Model) after which an IDoc of ALEAUD Message Type would be generated and the segments in this IDoc would contains the details of the Message Type(Including IDoc no) for which the confirmation is generated.
Thanks
Krithika

503 Service Unavailable : Application cannot be started.

I'm trying to deploy an application. The application, a JSP web module, consumes a web service. I have tried doing this on local dev, it works perfectly but when I transfer it to our dev track an error occurs. When I try to access it, it gives this error
Application cannot be started.
Details: com.sap.engine.services.deploy.container.ExceptionInfo: Application webserviceear cannot be started. Reason: it has hard reference to resource webserviceproxy with type application, which is not active on the server.
I have tried to deploy the dc for webserviceproxy then deployed the ear again but I still get the same error. I know that my web service is running because I can see and test it on wsnavigator. When I change my reference type to weak, I get compiling error instead. I don't have an access to our Visual Admin so I can't be sure what's the cause of the error.
What could be the solution to my problem? Thanks

Still having the same problem. Here's the log error for the EAR. Hope someone can help me.
Jul 6, 2011 9:20:17 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] WARNING:
[038]Deployment finished with warning
Settings
SDM host : bdhp4639
SDM port : 50918
URL to deploy : file:/C:/DOCUME1/saldua/LOCALS1/Temp/temp29002xx.comlftsclft~dc_webmoduleear.ear
Result
=> deployed with warning : file:/C:/DOCUME1/saldua/LOCALS1/Temp/temp29002xx.comlftsclft~dc_webmoduleear.ear
Finished with warnings: development component 'lft/sclft/dc_webmoduleear'/'xx.com'/'GGD_LFMGTDEV_D'/'20110706211929'/'0':Caught exception during application startup from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while starting application pg.com/lft/sclft/dc_webmoduleear and wait. Reason: Clusterwide exception: server ID 98155850:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application pg.com/lftsclftdc_webmoduleear cannot be started. Reason: it has hard reference to resource dc_webserviceproxy with type application, which is not active on the server. at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:597) at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:399) at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:328) at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:162) at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:136) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4741) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4646) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4619) at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137) 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.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: pg.com/dc_webserviceproxy', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: pg.com/dc_webserviceproxy at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:550) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4395) at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:589) ... 21 moreCaused by: com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: SAPJ2EE::xx.com/lftsclftdc_webserviceear', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: SAPJ2EE::xx.com/lftsclftdc_webserviceear at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:906) at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:523) ... 23 moreCaused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [ExternalApplicationItem.prepare]: SAPJ2EE::xx.com/lftsclftdc_webserviceear at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:188) at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:232) at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.start(SAPJ2EEApplicationItem.java:192) at com.sapportals.portal.prt.service.sapj2ee.Mediator.getAndStartExternalApplication(Mediator.java:127) at com.sap.portal.prt.sapj2ee.StartPortalApplication.coreRun(StartPortalApplication.java:59) at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:902) ... 24 moreCaused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application dc_webserviceproxy at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:460) at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:180) ... 29 more (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : Got problems during deployment
Edited by: mlsaldua on Jul 6, 2011 3:38 PM

Service cannot be started. Microsoft.VirtualManager.DB.CarmineSqlException: Unable to connect to the VMM database. Ensure that the SQL Server is running and configured correctly

Hi All,
I am setting up SCVMM 2012 R2 in a production environment. Whenever I restart the SCVMM virtual machine the VMM service doesn't start automatically, I have to manually start it. I checked the VMM logs and in the event viewer i find the below error,
Service cannot be started. Microsoft.VirtualManager.DB.CarmineSqlException: Unable to connect to the VMM database. Ensure that the SQL Server is running and configured correctly. ---> System.Data.SqlClient.SqlException: Cannot open database "VirtualManagerDB"
requested by the login. The login failed. Login failed for user 'NXTRA\VMMSVC'. at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean&
dataReady) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.Sq...
I added the 'VMMSVC' account as db_owner and sysadmin and also NT_Authority\System with same permissions still the service doesn't start on the start up.
I googled a lot and I find the threads with the error containing "General failure" but not with the above. Can someone please help me to find out why this error is occuring.
Thanks,
Ravi

It's often only a problem of the service dependencies. SCVMM starts to fast, SQL server on the same machine in not initialized yet. Here are working service dependencies to ensure SQL server is initializes before SCVMM starts.
You can set the service dependencies directly in regedit (as always: be careful modifying the registry ...)
Here is the content of a reg file setting the dependency.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SCVMMService]
"DependOnService"=hex(7):53,00,51,00,4c,00,53,00,45,00,52,00,56,00,45,00,52,00,\
41,00,47,00,45,00,4e,00,54,00,00,00,53,00,51,00,4c,00,42,00,72,00,6f,00,77,\
00,73,00,65,00,72,00,00,00,53,00,51,00,4c,00,57,00,72,00,69,00,74,00,65,00,\
72,00,00,00,4d,00,53,00,53,00,51,00,4c,00,46,00,44,00,4c,00,61,00,75,00,6e,\
00,63,00,68,00,65,00,72,00,00,00,00,00

RWB application cannot be started after PI 7.1 installation

Hi Guys,
I have installed PI 7.1 and when open the RWB i am getting the following error
Application cannot be started!
Details:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5004] Cannot create application loader for application sap.com/com.sap.xi.rwb.
     at com.sap.engine.services.deploy.server.utils.LoadContextUtils.defineSharedApplicationLoader(LoadContextUtils.java:100)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.bindLoader(DeployServiceImpl.java:1780)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:216)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:495)
any help would be really appreciated
Thanks,
Srini

Hi!
How to restart: SAP Note Number: 1031321
Restart of applications is offered by the Visual Administrator (6.40, 7.0 and subsequent) or Netweaver Administrator (7.10 and subsequent):
6.40, 7.0
Start the Visual Administrator, navigate to
Server>Services>Deploy
Check "Applications" (on the bottom of the page), select applications and restart them.
7.10
Enter the start page of the J2EE engine in your browser (http://<host>:<port>) and click the link to Netweaver Administrator.
Then navigate:
Netweaver Admnistrator --> Operations Management --> Infrastructure Management (Systems) --> Start&Stop --> Java EE Applications

Watch the NI-Week 2009 Presentation: Updating the LabVIEW Error Handling Core

The resources for the "Updating the LabVIEW Error Handling Core" NI-Week 2009 Presentation are now online.
See them here: http://lavag.org/topic/10741-updating-the-labview-error-handling-core/
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

I have always gone the latter route when I needed it. I usually use an action engine to keep track of the error messages. Said action engine can be used to combine and suppress errors, as well. I have posted an example below (LabVIEw 7.1). In this case, the error propagation is occurring in a task handler which is processing multiple command/data pairs. The command is set at the beginning of the task and the error handler is sprinkled liberally throughout the task code. In this particular case, the desired behavior is to continue execution on error, but log the errors.
I prefer this type of method because it gives me complete control over the error propagation. It has the down side of requiring more code and effort, but I think it is worth it. I like functionality to be explicit on my block diagrams. It makes long-term maintenance much easier.
This account is no longer active. Contact ShadesOfGray for current posts and information.
Attachments:
ErrorPropagation.llb ‏65 KB

VM Server stuck in "Error" state - cannot start or stop any VMs

I have Oracle VM Server 3.0.2, VM Manager 3.0.2, and have a VM server stuck in an "Error" state. I've gone into all the Event tabs for the server + guests and acknowledged all the errors, but it's still in this state.
When I try to start a VM for example, I get this error on screen (I've obfuscated the server names):
OVMRU_005007E Virtual Machine: <vmname>, cannot be started/resumed on Server: <servername>. Reasons:
Server: <servername>, is in error
AdminServer-diagnostic.log reports:
[2012-03-23T16:58:05.078+13:00] [AdminServer] [ERROR] [] [com.oracle.ovm.mgr.faces.model.EO] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 87aae679e5ee7e1d:-14aa5e4e:1363307a070:-8000-000000000000eb79,0] [APP: ovm_console] Programming error![[
java.lang.NoSuchMethodException: com.oracle.ovm.mgr.api.collectable.ManagedObjectHandleImpl.getUser()
at java.lang.Class.getMethod(Class.java:1605)
at com.oracle.ovm.mgr.faces.model.EO.invokeStringAccessor(EO.java:551)
at com.oracle.ovm.mgr.faces.model.EO.invokeStringAccessor(EO.java:1124)
at com.oracle.ovm.mgr.faces.model.JobEO.getUsername(JobEO.java:608)
at com.oracle.ovm.mgr.faces.backing.task.TaskFilter.isAssociatedUser(TaskFilter.java:216)
at com.oracle.ovm.mgr.faces.backing.task.TaskFilter.isAssociatedWith(TaskFilter.java:241)
at com.oracle.ovm.mgr.faces.model.collection.EOList.isAssociatedWith(EOList.java:239)
at com.oracle.ovm.mgr.faces.model.collection.EventSupport.handleInsert(EventSupport.java:60)
at com.oracle.ovm.mgr.faces.model.collection.EOList.handleInsert(EOList.java:211)
at sun.reflect.GeneratedMethodAccessor1446.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.oracle.ovm.mgr.faces.model.ChangeSupport.fireChangeEvent(ChangeSupport.java:127)
at com.oracle.ovm.mgr.faces.model.ChangeSupport.fireInsert(ChangeSupport.java:66)
at com.oracle.ovm.mgr.faces.model.DataProvider$EventListener.fireInsert(DataProvider.java:312)
at com.oracle.ovm.mgr.faces.model.DataProvider$EventListener.timerExpired(DataProvider.java:284)
at weblogic.timers.internal.commonj.ListenerWrap.timerExpired(ListenerWrap.java:37)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Nothing gets written to AdminServer.log
Any ideas?

Hi Mannyabdon,
Based on your description, I recommend to check the things below:
1. Run the PowerShell command below to check the status of the Secure Store Service:
Get-SPServiceInstance |Where {$_.typename -like "Document Conversions Load Balancer Service"}
If it is not showing online, please stop the service first and then start it to see if the issue still occurs (the
<ServiceGUID> can be obtained obtained from the command above).
Stop the service:
Stop-SPServiceInstance -Identity <ServiceGUID>
Start the service:
Start-SPServiceInstance -Identity <ServiceGUID>
2. Check the ULS log for detailed error message.
For SharePoint 2013, by default, ULS log is at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS.
Thanks,
Victoria
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

For IDOC monitoring, analysis and error handling in ALE & idoc

Hello...experts..can u please tell me about idoc monitoring,analysis and error handling..and can u please tell as per interview point of view in this area..if availble can u send material about this...
thx
Message was edited by:
durga kottapalli

Hi,
Reprocessing IDocs with errors
Outbound (BD88)
Once the error has been determined and corrected it is not necessary to resend the IDoc again. You simply resend the IDocs that have already been generated.
Using the IDoc overview screen you need to take note of the following for each IDoc that was not processed:
Error number: 2, 4, 5, 25, 29
Error number: 30 (Execute Check IDoc dispatch to process)
IDoc number
Using the Error number, the IDoc number and the transaction BD88 , with the required message type you can resend the IDoc. Match the error number with this transaction and execute the function for the IDocs incorrectly processed.
Just check the below link, u will get all IDOC related Interview questions
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sappoint.com/abap.html
http://www.sap-img.com/
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://www.sappoint.com/abap.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sap-img.com/
http://www.allsaplinks.com/
Regards,
Suresh.
Message was edited by:
SureshKumar Ramamoorthy

Determining which EDI Error Messages are related to "Tasks"

Our company uses EDI heavily and have many errors which our business community wiill process. I do not know how other companies are handling this "EDI workflow", but we do this through transaction PPOM. We have created an overall EDIORG organization along with positions for different areas of responsibility. We then need to assign the "appropriate tasks" to each position & also assign the correct position to the Partner profiles to ensure the correct people see the errors.
My question is how can II determine which "Tasks" are assign to the specific message errors that end up coming in? Most Tasks are by Idoc type --- do I just have to assume that any error related to that IDoc type would be covered?
Thanks so much for any input as to "Controlling the EDI Error processing" by business users!
Britte

Hi surya,
You are saying 1122124 is IDOC numner & its not relevant to this idoc.
What it means,can u explain??? Actually there will be a chance an IDOC can mapped to N no of documents. This mapping will done through a BADI internally.
Regards
KER

About ale error handling in workflow?

Hi,
can any one explian in detail ale error handling through workflow,its urgent for me.
Regards,
phani

Hi Srikanth,
follw the steps it will helpful u,
Pre-requisites.
It is assumed that the reader of this article has some knowledge in SAP workflow BOR objects and ALE Idoc process like process code, Partner Profile etc.
Description
Here, we will be discussing in details the Error handling of an Inbound Idoc through triggering an event, which in turn will be triggering a workflow attached to the workflow.
Steps:-
1.     Create custom BOR object with the events, Start and Stop event
2.     Create a workflow for the error handling, like generating a notification whenever an error occurred in the Inbound Idoc.
3.     Creation of Function Module and attachment with the Process Code
4.     Create the settings for the Inbound Process of the Idoc through the Process Code.
Creation of BOR objects. Go to the[http://www.****************/Tutorials/ALE/ErrorHandling/page3.htm] transaction SWO1.
Enter a name for the Object type and click CREATE button for creating the custom BOR object.
Enter the details required for creating the BOR objects...
Create the Key fields and events of the BOR object.
For creating the Key fields place the cursor on the Key fields and Click on the Create Button
Create events for triggering the workflow and stopping the workflow.
For creating the event place the cursor on the EVENTS and Click the create button like Key fields.
Create two events.
Enter the event name description etc and proceed further to create it.
Similarly create another event for ending the Workflow in the similar manner like that created earlier.
Now, Generate the BOR object through the generate button
Release the EVENTS and subsequently release the BOR object.
After the creation of BOR object
Create a workflow for the generation of notification whenever an error is reached in the Inbound Idoc.
Execute the transaction SWDD.
Click on the CREATE button for creating the workflow for error handling.
Choose the Step type to be inserted for the notification like here we are using Send Mail option for sending a mail to the user whenever any error occurred.
Activate the Workflow and test it whether it is working as per the requirement.
After the successful completion it is required to attach the workflow with the event.
Go to the Header section (Denoted by CAP).
Go to the Start Events TAB.
Enter the details of the event with which the workflow should be linked like the category, BOR object type and the event with which that should be linked.
Enter here the BOR object that has been created and give the name of event created for starting the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Generate the binding and click OK button to save the binding.
Click on Activate / deactivate button for activating the linkage.
After the successful linkage the following sign will appear on the workflow.....
This shows that the workflow has been linked to the event and it will be triggered whenever that particular event will be triggered.
After the creation and successful linkage of workflow with the event it is required it is required to generate a function module and attached it to the process code.
Go to SE37 transaction and copy a standard process code function module to a custom one. Do no delete any parameters from the function module as the SAP standard program itself is calling this.
In that function module do the required validation and whenever the validation fails set a standard parameter WORKFLOW_RESULT to 9999 from within the function module, otherwise normally proceed to set the status to 53.
After the creation of function module it is required to attach it to the process code and corresponding attached to the message type at the Partner Profile stage.
The process code is being created through the transaction WE42
Go to the change mode and click the New Entries button for creating new process code.
Enter the Process Code Name, description and choose the processing type as Processing by function module. Click on the extension button of Identification.
The details for the of the Process Code after clicking the identification button will be
Whenever idoc arrives into the Destination system then the standard SAP triggers the Process code attached to the Message type in the partner profile. The partner profile is being maintained in the transaction WE20.
Since, it is and inbound scenario so the message type and the corresponding process code will be maintained for the Inbound Parameters.
Click on Create Inbound Parameters button for creating new Inbound Message type and the corresponding message type.
Enter the process code for the corresponding message type.
Click SAVE button for saving the changes.
Whenever the IDOC arrives into the target system, it checks the partner profile and finds the corresponding process code. The process code is being linked with the function module through which the IDOC is required to be processed.
Regards,
Phani.

Error APPX0002: Task 'ValidateAppxPackage' failed. Value cannot be null.

Hi, I have been working on Windows Phone apps, and have created several packages and submitted them to the store. Starting today, for no apparent reason, I can't create packages for the store any more. When creating the Store package, using Visual Studio
2013 Ultimate Update 4, build fails with this error:
Error APPX0002: Task 'ValidateAppxPackage' failed. Value cannot be null.
I have not been able to fix this. I've tried:
- uninstalling and reinstalling Visual Studio
- rebooting
- deleting the Package.StoreAssociation.xml in the file (but it cannot be recreated).
I am able to compile and run the project, but it fails when creating the store package to submit to dev center.
Any suggestions?
Here is the detailed compile report:
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error APPX0002: Task 'ValidateAppxPackage' failed. Value cannot be null.
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error APPX0002: Parameter name: source
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error APPX0002:
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error MSB4018: The "ValidateAppxPackage" task failed unexpectedly.
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error MSB4018: System.ArgumentNullException: Value cannot be null.
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error MSB4018: Parameter name: source
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error MSB4018: at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector,
IEqualityComparer`1 comparer)
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error MSB4018: at Microsoft.Build.AppxPackage.DumpResourceIndexMap..ctor(ITaskItem[] indexedPayloadFiles)
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error MSB4018: at Microsoft.Build.AppxPackage.ValidateAppxPackage.CheckImages()
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error MSB4018: at Microsoft.Build.AppxPackage.ValidateAppxPackage.ExecuteImplementation()
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error MSB4018: at Microsoft.Build.AppxPackage.AppxPackagingTaskHelper.Execute()
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error MSB4018: at Microsoft.Build.AppxPackage.ValidateAppxPackage.Execute()
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error MSB4018: at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1706,9): error MSB4018: at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
el_ber

Hi el_ber,
From your information, I see that you used VS2013. Could you please tell us how did you build the project? Using VS directly, using command line or writing a script to involve MSBuild to run it? I guess you used the command line or write a build script to
run the project because I see the path is "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0" instead of "C:\Program Files (x86)\MSBuild\12.0\Bin\msbuild.exe". If that is the case, please use "C:\Program Files (x86)\MSBuild\12.0\Bin\msbuild.exe"
to build the project.
If not, can you reproduce this issue? If you can, please provide us with the steps to reproduce this issue or provide us with a sample project on onedrive.
Best regards,
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.

Task ALE/EDI: Error handl cannot be started immediately

Similar Messages

Maybe you are looking for