Error in starting a workflow with a z event.
I have implemented an event in an object which gets generated through PA30. But when the event gets generated the workflow does not get triggerred and instead an error msg comes in event trace ie.
"Event EMPLOYEEI CHANGED for task WS90000048 not defined as start/end event"
And the linkage gets deactivated.
Can you please suggest what is the problem and the solution too.
Try making some checks :
Go to SWUD and - Task type : WS - Task:<your WF> and execute the step "Problem: Task not started". Here you'll find the declaration of the triggering event. Then execute the "Consistency check for tasks". If everything is green, it means we're on the right way.
Regards,
Gianluca
Similar Messages
-
Problem starting a workflow with a timed event.
Hi all,
I am trying to start a workflow with a timed event this way,
Start Date Expression: StringToDate("20:09", "HH:mm")
Reschedule: 1 day
I save the workflow at 20:07, but nothing happens at 20:09.
Any hints?
Thanks in advance.Hi Thomas,
Wf-XML was implemented when XI wasn't even a glint in SAP's eye. The message arrives in the SAP Web AS and triggers a workflow directly (or responds to an incoming workflow request message).
Exception: prior to the 6.10 release of the Web AS the incoming messages are received in an ITS.
Best regards,
Alan -
How to start a Workflow with a Dynpro action button.
Hi @ all,
i have the problem, that i want to start a workflow with a self-made dynpro.
The dynpro consist the following information who had to be transported in the workflow.
Stacknr.
User
Date
Time
and a tif data file
Somebody have an idea how it works?
i am very new in workflow. So if you want to help me than please with a step by step guide.
Thanks a lot.
Regards PhilHi,
Please go through the wiki. There are plenty of instructions. Also, this is commonly discussed topic, so try to search first. The key for your problem is that there are function modules to tirgger workflows (either directly or with an event).
Regards,
Karri -
i have already create a custom workflow with sharepoint designer and checked for error and it seem fine. i published it on my document library so apprear the first issue : the column that contain the name of my workflow apprear and the link to start my workflow(contain
the name of my first stap) doesn't appear. the second problem is that when i tried to start the workflow manually on a specific document i get an alert : Something went wrong. To try again, reload the
page and then start the workflow
i tried : -restart service bus message broker -restart service bus gateway -recycle workflowMgntpool -flushed the dsn resolver cache and the problem still occure
on uls log viewer it seems to be an error on w3wp.exe process
the workflow history is emptyHi Mokhtar,
For your first issue, when you publish a workflow to your document library, only after you start the workflow, then the link to go on the workflow(contain the name of the workflow stage) will appear.
For your second issue, my understanding is that you got an error when you manually start a SharePoint Designer 2013 Workflow.
Please go to Administrative Tools->Services, make sure the following services are started.
Workflow Manager Backend
Service Bus Message Broker
Service Bus Gateway
Windows Fabric Host Service
Here are similar posts for you as a reference:
https://social.msdn.microsoft.com/Forums/office/en-US/12f8ae26-6889-4227-a3fc-dd29a38230a6/something-went-wrong-to-try-again-reload-the-page-and-then-start-the-workflow?forum=sharepointcustomization
http://community.office365.com/en-us/f/154/t/277480.aspx
If the issue still exists, please check Event Viewer to check more information about this issue.
http://msdn.microsoft.com/en-us/library/jj193526(v=azure.10).aspx
I hope this helps.
Best Regards,
Lisa Chen
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] -
Error when starting Weblogic server with Coherence
We want to use Coherence 3.6 with Weblogic Server 10.3. During server startup, we get the following error. My understanding is the cluster should be started automatically based on the configuration listed below the error. Appreciate any pointers.
<Dec 15, 2011 3:20:11 PM PST> <Error> <Coherence> <BEA-000000> <2011-12-15 15:20:11.920/67.311 Oracle Coherence SE 3.6.0.4 <Error> (thread=Cluster, member=n/a): This member could not join the cluster because of a configuration mismatch between this member and the configuration being used by the rest of the cluster. This member specified a cluster name of "EPCIS" which did not match the name of the running cluster. This indicates that there are multiple clusters on this network attempting to use overlapping network configurations. Rejected by Member(Id=9, Timestamp=2011-11-16 13:58:42.941, Address=10.229.189.30:8088, MachineId=21022, Location=site:us.oracle.com,machine:adc2101177,process:30667, Role=WeblogicServer).>
<Dec 15, 2011 3:20:11 PM PST> <Error> <oracle.apps.pas.epc.framework.db.Cache> <BEA-000000> <java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)>
<Dec 15, 2011 3:20:11 PM PST> <Error> <Coherence> <BEA-000000> <2011-12-15 15:20:11.957/67.349 Oracle Coherence SE 3.6.0.4 <Error> (thread=[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Error while starting cluster: java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)
CONFIGURATION:
We have the following descriptor (epcis-coherence-cache-config.xml) in $DOMAIN_HOME/epc-config:
<?xml version="1.0"?>
<!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config>
<caching-scheme-mapping>
<cache-mapping>
<cache-name>*</cache-name>
<scheme-name>distributed</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<distributed-scheme>
<scheme-name>distributed</scheme-name>
<service-name>DistributedCache</service-name>
<backing-map-scheme>
<local-scheme></local-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
</caching-schemes>
</cache-config>
We also have tangosol-coherence-override.xml in the same dir:
<coherence>
<cluster-config>
<member-identity>
<cluster-name system-property="tangosol.coherence.clustername">EPCIS</cluster-name>
</member-identity>
</cluster-config>
<configurable-cache-factory-config>
<class-name>com.tangosol.net.DefaultConfigurableCacheFactory</class-name>
<init-params>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>epcis-coherence-cache-config.xml</param-value>
</init-param>
</init-params>
</configurable-cache-factory-config>
<license-config>
<edition-name system-property="tangosol.coherence.edition">SE</edition-name>
<license-mode system-property="tangosol.coherence.mode">dev</license-mode>
</license-config>
</coherence>
We have modified startWebLogic.sh by adding:
PRE_CLASSPATH="/slot/xyz/oracle/mwhome/oracle_common/modules/oracle.coherence_3.6/coherence.jar:${DOMAIN_HOME}/epc-config/:${PRE_CLASSPATH}"As the error message says, your WebLogic server is trying to join a cluster that has a different cluster name.
This bit in your tangosol-coherence-override.xml file or the tangosol.coherence.clustername system property must be the same in all members of the cluster
<cluster-name system-property="tangosol.coherence.clustername">EPCIS</cluster-name>JK -
Service Registry error while starting after configuring with DB2 database
Hi
I installed WLS 9.1 / ALSR 2.1 on RedHat Linux 4 EL.And DB2 8.2 FP12
It was started fine with the default HSQL database, after changing the database to DB2 and restarted the server, I am getting the following errors
Any one know about this ..please help me. Seems it was alredy posted on forums.bea.com but those threads are not accessioble now.Appriciate any quick response
error log - I also checked the account_list.xml file it looks fine.
JAVA Memory arguments: -Xms2048m -Xmx2048m -XX:MaxPermSize=128m
WLS Start Mode=Production
CLASSPATH=:/opt/bea/bea91/patch_weblogic910/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/Java5/jdk1.5.0_17/lib/tools.jar:/opt/bea/bea91/weblogic91/server/lib/weblogic_sp.jar:/opt/bea/bea91/weblogic91/server/lib/weblogic.jar:/opt/bea/bea91/weblogic91/server/lib/webservices.jar::/opt/bea/bea91/weblogic91/common/eval/pointbase/lib/pbclient51.jar:/opt/bea/bea91/weblogic91/server/lib/xqrl.jar::/opt/bea/bea91/weblogic91/integration/lib/util.jar:
PATH=/opt/bea/bea91/weblogic91/server/bin:/opt/bea/Java5/jdk1.5.0_17/jre/bin:/opt/bea/Java5/jdk1.5.0_17/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/weblogic/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.5.0_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_17-b04)
Java HotSpot(TM) Server VM (build 1.5.0_17-b04, mixed mode)
Starting WLS with line:
/opt/bea/Java5/jdk1.5.0_17/bin/java -server -Xms2048m -Xmx2048m -XX:MaxPermSize=128m -da -Dplatform.home=/opt/bea/bea91/weblogic91 -Dwls.home=/opt/bea/bea91/weblogic91/server -Dwli.home=/opt/bea/bea91/weblogic91/integration -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Djava.security.auth.login.config=/opt/bea/bea91/alsr21/conf/jaas.config -Dweblogic.ext.dirs=/opt/bea/bea91/patch_weblogic910/profiles/default/sysext_manifest_classpath -Dweblogic.Name=zsoaLAALSRAdminServer -Djava.security.policy=/opt/bea/bea91/weblogic91/server/lib/weblogic.policy weblogic.Server
<Dec 23, 2008 11:02:49 AM PST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/opt/bea/bea91/user_projects/domains/zsoaLALASRDomain/lib/db2jcc2.jar:/opt/bea/bea91/user_projects/domains/zsoaLALASRDomain/lib/db2jcc_license_cu2.jar>
<Dec 23, 2008 11:02:49 AM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0_17-b04 from Sun Microsystems Inc.>
<Dec 23, 2008 11:02:50 AM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.1 Mon Dec 12 19:26:33 EST 2005 689178 >
<Dec 23, 2008 11:02:53 AM PST> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /opt/bea/bea91/license.bea>
<Dec 23, 2008 11:02:53 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 23, 2008 11:02:53 AM PST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 23, 2008 11:02:53 AM PST> <Notice> <Log Management> <BEA-170019> <The server log file /opt/bea/bea91/user_projects/domains/zsoaLALASRDomain/servers/zsoaLAALSRAdminServer/logs/zsoaLAALSRAdminServer.log is opened. All server side log events will be written to this file.>
<Dec 23, 2008 11:02:53 AM PST> <Error> <Socket> <BEA-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that libmuxer library is in :'/opt/bea/Java5/jdk1.5.0_17/jre/lib/i386/server:/opt/bea/Java5/jdk1.5.0_17/jre/lib/i386:/opt/bea/Java5/jdk1.5.0_17/jre/../lib/i386:/opt/bea/bea91/patch_weblogic910/profiles/default/native:/opt/bea/bea91/weblogic91/server/native/linux/x86_64:/opt/bea/bea91/weblogic91/server/native/linux/x86_64/oci920_8'
>
<Dec 23, 2008 11:02:54 AM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 23, 2008 11:02:56 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 23, 2008 11:02:56 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
INFO: com.systinet.wasp.WaspImpl - Starting Systinet Server for Java/6.0 (Java/1.5.0_17; Linux/2.6.9-78.0.1.ELsmp; build SSJ-6.0-20060622-1136)
INFO: com.systinet.wasp.monitoring.LogEventModule - Starting event management
INFO: log4j.Log4JAdapter - Events Log File: /opt/bea/bea91/user_projects/domains/zsoaLALASRDomain/servers/zsoaLAALSRAdminServer/tmp/_WL_user/registry/4rin9e/public/systinetRegistry_logEvents.log
INFO: log4j.Log4JAdapter - Error Events Log File: /opt/bea/bea91/user_projects/domains/zsoaLALASRDomain/servers/zsoaLAALSRAdminServer/tmp/_WL_user/registry/4rin9e/public/systinetRegistry_errorEvents.log
INFO: com.idoox.config.xml.ConfigStore - Starting configStore with savingPeriod 2000
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [system][http://systinet.com/wasp/app/core_services_client][core_services_client][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [system][http://systinet.com/wasp/app/builtin_serialization][builtin_serialization][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [system][http://systinet.com/wasp/app/security_providers][security_providers][1.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [system][http://systinet.com/wasp/app/uddi/redirect/5.0][uddi-redirect][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/wasp/app/uddi/6.0][UDDI-services][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/statistics/5.0][Statistics-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/xslt2uddi/v3/5.5][UDDIClient-xslt2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/api/ext/5.0][UDDIClient-ext][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/approval_production/5.0][Approval-production-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/wsdl2uddi/v3/5.5][UDDIClient-wsdl2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/approval_management/5.0][Approval-management-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/configuratorCluster/5.0][Configurator-cluster-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/replication/v3/5.0][Replication-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/subscription/listener/v3/5.0][UDDIClient-subscription-listener-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/approval/5.0][Approval-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/taxonomy/v3/5.5][Taxonomy-client-v31][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/inquiryUI/6.0][UDDIClient-v3-ui][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/validate-values/v1/5.0][UDDIClient-validate-values-v1][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/custody/v3/5.0][UDDIClient-custody-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/subscription/v3/ext/6.0][UDDIClient-subscription-v3-ext][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/administrationUtils/5.5][AdministrationUtils-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/wasp/app/bsc/web/6.0][bsc][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/transformer_kr/5.5][Transformer-kr-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/v3/5.0][UDDIClient-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/wsdl2uddi/v2/5.0][UDDIClient-wsdl2uddi-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/validate-values/v2/5.0][UDDIClient-validate-values-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/v3_ext/5.0][UDDIClient-v3_ext][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/xml2uddi/v3/5.5][UDDIClient-xml2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/value-set-caching/v3/5.0][UDDIClient-value-set-caching-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/xsd2uddi/v3/5.5][UDDIClient-xsd2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/wasp/app/uddi/web/6.0][UDDI-web][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/approval_checker/5.0][Approval-checker-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/category/v3/5.5][Category-client-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/group/5.5][Group-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/subscription/v3/5.0][UDDIClient-subscription-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/v2/5.0][UDDIClient-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/configurator/5.0][Configurator-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/permission/5.5][Permission-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/taxonomy/v3/5.0][Taxonomy-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/v1/5.0][UDDIClient-v1][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/account/5.5][Account-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/value-set-validation/v3/5.0][UDDIClient-value-set-validation-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client-core/5.0][Client-core][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [system][http://systinet.com/wasp/app/core_services_client][core_services_client][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [system][http://systinet.com/wasp/app/builtin_serialization][builtin_serialization][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [system][http://systinet.com/wasp/app/uddi/redirect/5.0][uddi-redirect][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [system][http://systinet.com/wasp/app/security_providers][security_providers][1.0]
INFO: com.idoox.wasp.security.server.SecurityModule - SecurityModule starts.
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client-core/5.0][Client-core][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/statistics/5.0][Statistics-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/approval_management/5.0][Approval-management-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/replication/v3/5.0][Replication-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/transformer_kr/5.5][Transformer-kr-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/v3/5.0][UDDIClient-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/v2/5.0][UDDIClient-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/configurator/5.0][Configurator-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/v1/5.0][UDDIClient-v1][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/account/5.5][Account-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/xslt2uddi/v3/5.5][UDDIClient-xslt2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/api/ext/5.0][UDDIClient-ext][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/wsdl2uddi/v3/5.5][UDDIClient-wsdl2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/inquiryUI/6.0][UDDIClient-v3-ui][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/custody/v3/5.0][UDDIClient-custody-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/administrationUtils/5.5][AdministrationUtils-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/v3_ext/5.0][UDDIClient-v3_ext][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/xml2uddi/v3/5.5][UDDIClient-xml2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/value-set-caching/v3/5.0][UDDIClient-value-set-caching-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/xsd2uddi/v3/5.5][UDDIClient-xsd2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/category/v3/5.5][Category-client-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/subscription/v3/5.0][UDDIClient-subscription-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/taxonomy/v3/5.0][Taxonomy-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/value-set-validation/v3/5.0][UDDIClient-value-set-validation-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/approval/5.0][Approval-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/wsdl2uddi/v2/5.0][UDDIClient-wsdl2uddi-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/validate-values/v2/5.0][UDDIClient-validate-values-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/configuratorCluster/5.0][Configurator-cluster-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/validate-values/v1/5.0][UDDIClient-validate-values-v1][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/group/5.5][Group-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/permission/5.5][Permission-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/subscription/listener/v3/5.0][UDDIClient-subscription-listener-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/subscription/v3/ext/6.0][UDDIClient-subscription-v3-ext][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/taxonomy/v3/5.5][Taxonomy-client-v31][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/approval_checker/5.0][Approval-checker-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/approval_production/5.0][Approval-production-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/wasp/app/uddi/6.0][UDDI-services][6.0]
[Fatal Error] account_list.xml:1:1: Premature end of file.
<Dec 23, 2008 11:03:04 AM PST> <Error> <HTTP> <BEA-101216> <Servlet: "Registry Servlet" failed to preload on startup in Web application: "registry.war".
java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at com.systinet.uddi.security.destination.DestinationSecurityModule.load(DestinationSecurityModule.java:25)
at com.idoox.wasp.ModuleRepository.loadModule(ModuleRepository.java:120)
org.xml.sax.SAXParseException: Premature end of file.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at com.idoox.config.xml.XMLConfigurator.prepareConfigFile(XMLConfigurator.java:575)
at com.idoox.config.xml.XMLConfigurator.init(XMLConfigurator.java:420)
at com.idoox.config.xml.XMLConfigurator.init(XMLConfigurator.java:333)
Truncated. see log file for complete stacktrace
>
<Dec 23, 2008 11:03:04 AM PST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'registry'.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "Registry Servlet" failed to preload on startup in Web application: "registry.war".
<Dec 23, 2008 11:03:04 AM PST> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "zsoaLAALSRAdminServer" for domain "zsoaLALASRDomain" running in Production Mode>
<Dec 23, 2008 11:03:04 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Dec 23, 2008 11:03:04 AM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Exception in thread "Timer-3" java.lang.NoClassDefFoundError: com/systinet/wasp/webservice/FinalizationSupport
at com.systinet.wasp.ServiceManagerImpl$ReferenceQueueCleaner.run(ServiceManagerImpl.java:2617)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)I discovered, that the problem is probably caused by a collection, which is returned by a findBy method.
see detail of exception:
Caused by: javax.xml.bind.JAXBException: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
java.util.Collection is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at java.util.Collection
When I deploy an simple WS (summerizing 2 numbers) it is deployed fine and the WS is up and running.
Does anyone has experienced a similar problem? I want to expose the functionality of my BO methods in order to set up a small POC.
Can anyone please help?
Thanks & Regards,
Michael
null -
Hi everybody. I have recently started having problems with iCal (Version 2.05 (1069). Events that I thought I had deleted appear in Print Preview and Print Outs. Likewise Events that I have not deleted have disappeared from my calender (Month View) but appear in Print Preview and Print Outs. I see that there have been similar problems with Events disappearing especially in Month View. I wondered how print preview seemrd to be picking everything up deleted or not, and what the solution may be?. First time of Posting. I hope I haven't embarassed myself.
Hmmmm.
At the very least there must be a "com.apple.ical.plist"...iCal would not function without it.
Click on the Finder icon in the dock
Click on Go > Home
Double-click Library
Double-click Preferences
Look for a file called "com.apple.ical.plist" and remove it to the trash. -
Starting Participant Workflow WIth XOCP Message Sent From Application
IS it possible to send and XOCP message ot the hub from an application (like a
servlet) and then have that XOCP message received by a participant workflow?
The error in the log looks like <XOCP-Hub> INFO: No recipient trading partner(s)
found for message blah blah blah...
I have 2 roles set up in Collaborate. One of them has no WLPI Workflow associated
with it, the other does. That workflow is not specified as initiator and has conversation
properties associated with it and a Business Message start node.My guess is that when running on Ubuntu you're picking up the Gnu version of JavaMail
instead of the Sun version. If you enable session debugging, what version number does
it print? Look for other jar files in your jre/lib/ext directory. -
Error when starting a workflow in workspace
Hi!
I'm doing the tutorial of process management but when i'm trying to test it at workspace it gaves me this error:
An error occurred during the operation (endpoint id 1805). (ALC-WKS-007-027)
the server log says:
Caused by: ALC-DSC-012-000: com.adobe.idp.dsc.registry.ServiceNotFoundException: Service: TaskManagerConnector not found.
at com.adobe.idp.dsc.registry.service.impl.ServiceRegistryImpl.getService(ServiceRegistryImp l.java:1088)
at com.adobe.idp.dsc.registry.service.impl.ServiceRegistryImpl.getHeadActiveConfiguration(Se rviceRegistryImpl.java:939)
at com.adobe.idp.dsc.registry.naming.impl.NamingRegistryImpl.resolveName(NamingRegistryImpl. java:93)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.resolveConfiguration(ServiceEngineImpl.ja va:143)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:76)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:93)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:22 5)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:66)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.idp.dsc.registry.connector.impl.ConnectorRegistryImpl.getEndpointDefinition(Con nectorRegistryImpl.java:104)
... 273 more
Can anyone help me with this?It seems to me that your LiveCycle installation is not completely successfull...
-
InDesign CS3 error while starting a Javascript with a AppleScript
Hello,
I have a problem with InDesign CS3. An Apple Script controls in one end, a work flow, Indesign used JavaScript.
These are the Indesign module libraries (Extended Script Editor 2) is called.
Do I have these two scripts before, once opened, and with Indesign "linked" everything is running smoothly.
But I'm not starting this JavaScript manually before, hangs Indesign and the Apple Script increases with a timeout.
Is there a solution?
Many greetings
oli_luas well as it looking like the routing device has DoS or SPI feature there is no Ping in the Log so it is possible it is alos not allowing Responses to Internet Pings.
iChat sends a Ping so this also needs to be Disabled.
10:55 PM Saturday; August 16, 2008 -
Starting a workflow with inbound Wf-XML
Hi
I read on help.sap.com that a workflow can be started when an inbound Wf-XML document arrives. Can anyone clarify where the XML actually arrives?
Will the XML arrive at the integration layer (in our case SAP XI), and XI will have to trigger the workflow, or will the XML somehow arrive at the workflow? Can anyone clarify this?
Any help is, as usual, greatly appreciated.
Regards,
Thomas
Message was edited by: Thomas KjelsrudHi Thomas,
Wf-XML was implemented when XI wasn't even a glint in SAP's eye. The message arrives in the SAP Web AS and triggers a workflow directly (or responds to an incoming workflow request message).
Exception: prior to the 6.10 release of the Web AS the incoming messages are received in an ITS.
Best regards,
Alan -
Error in starting nidevldu and nipxirmu services (windows event viewer)
A computer running Windows XP SP1 and a Visual basic (V6.0) application that I've developped had crashed several times. I've seen lots of errors in the Windows event viewer saying that the nidevldu and nipxirmu services were trying to start (exact french message : Le service nidevldu est en attente de démarrage et Le service nipxirmu est en attente de démarrage). These messages are real errors (not warning or informations).
I use a 6034E PCI card, Visual basic V6.0 and NI-DAQ 7.4.
The crashes I've seen may be linked with this problem.
Is there a solution?Hi,
I think that you are not going to be starting and stopping the devldu service in normal circumstances... due to crashes !
The firsts steps you have to focus on is to optimize your program in order to avoid crashes, which is not a normal way of work I guess. Then you will be able to avoid these messages!
Regards,
David D. - Application Engineer - NI -
XSL Errors When Using AQ Adapter with EBS Business Events
I am triggering a BPEL process with an Oracle EBS Business Event. After receiving the event, I am trying to perform an XSL transformation to extract parameters from the event. However, I keep getting XSL errors because the BE field ERROR_SUBSCRIPTION comes in containing invalid XML characters (#).
It seems that BPEL or EBS do not properly escape the XML input. Is that a bug, or is there a way to work around this. I know I could filter the XML input in some way, but that seems likely to be more brittle to any future changes to the EBS BE message types.Adding to the above post, how will the PL/SQL program which triggers the Business Event ensure that the complete data is enqueued in the queue in form of XML?
What will be the additional logic to send complete data in the XML format? -
HI Gurus
In my customers company they implement an Upgrade from R/3 sytem release 4.7C to ECC 6.0.
After that we began with unit tests. We are facing an error when we try to start a Workflow. The error message says:
"Error while starting the workflow".
Message number: LR365
An analysis of TC SWU4 was done for task TS90000001 and during the "Tasks consistency verification" we got the following errors:
E SW: 006 MANDATORY IMPORT ELEMENT 'TS_DATE' IS NOT (EXPLICITY)
E SW: 006 MANDATORY IMPORT ELEMENT 'TS_TIME' IS NOT (EXPLICITY)
We found SAP Note 1228836 - Compatibility of conditions with
date/time constants.
Do somenone know if the application of that note will solve the problem?
Or can someone give me some light on that theme?
Thanks in advanced.
FranciscoSince it is a custom workflow, check the import and export elements
defined in the workflow in SWDD transaction in your latest version. -
Starting workflow with HTTP-Post
Hello,
like I wrote in Starting workflow with HTTP-Post I have a problem with starting a workflow with a http-post:
I have an installation of SAP ERP 2005 SR2 IDES on Win2003 SR2 SP2 and want to start a simple workflow with an external application. Therefor I created an elementary test-workflow and set the general task flag so everybody is allowed to start it. So far everything work fine as I start it manually.
Now I want to start the workflow by an external application over a HTTP-Post as described in
http://help.sap.com/saphelp_47x200/helpdata/EN/54/de9e3887d6174fe10000009b38f842/content.htm
I configured the webserver (Customizing Web-Server) as follows:
Service: WebFlow (Intranet)
Address: http://192.168.0.216:8000/
Path: SAP/BC/WORKFLOW_XML/?
and sent a post via perl to http://192.168.0.216:8000/SAP/BC/WORKFLOW_XML/?protocol=01&localkey=WS99900004
<?xml version="1.0" ?>
<WfMessage Version="1.0" xmlns="http://www.wfmc.org/standards/doc/WF-XML">
<WfMessageHeader>
<Request ResponseRequired="No">
<Key>http://192.168.0.216:8000/SAP/BC/WORKFLOW_XML/?protocol=01&localkey=WS99900004</Key>
</WfMessageHeader>
<WfMessageBody>
<CreateProcessInstance.Request StartImmediately="true">
<ObserverKey>http://192.168.0.224</ObserverKey>
</CreateProcessInstance.Request>
</WfMessageBody>
</WfMessage>
The Web-Server returns
C:\FH\SAP\perl-scripte>perl http-post.pl
HTTP/1.1 200 OK
Server: SAP Web Application Server (1.0;700)
Content-Length: 0
Content-Type: text/plain
Client-Date: Sun, 01 Jun 2008 11:00:24 GMT
Client-Peer: 192.168.0.216:8000
Client-Response-Num: 1
but it seems that nothing happens.
I also tried to post the XML via html-form-field with the same result.
Did I forgot something essential?Hello Daniel
It's 6 years after you posted your question, but I found your post very useful and thought it would be worth updating for future reference.
I've just managed to trigger a workflow via http.
URL :
http://server.domain:8000/sap/bc/workflow_xml?sap-client=110
Java :
URL obj = new URL(url);
URLConnection con = (URLConnection) obj.openConnection();
String userpass = "username:password";
String basicAuth = "Basic " + javax.xml.bind.DatatypeConverter.printBase64Binary(userpass.getBytes());
con.setRequestProperty ("Authorization", basicAuth);
con.setRequestProperty("Content-type", "text/xml");
con.setDoOutput(true);
DataOutputStream wr = new DataOutputStream(con.getOutputStream());
wr.write( xml.getBytes("UTF-8") );
wr.flush();
wr.close();
You can then read the response.
I found that until I added the sap_client parameter I couldn't debug in CL_HTTP_WORKFLOW_XML->IF_HTTP_EXTENSION~HANDLE_REQUEST. Then I found that the content type has to be "text/xml".
I set the xml variable (the data sent to ECC) to :
<?xml version="1.0" ?>
<WfMessage Version="SAP.1.0" xmlns="http://www.wfmc.org/standards/doc/WF-XML">
<WfMessageHeader>
<Request>
<ResponseRequired>Yes</ResponseRequired>
</Request>
<Key>HTTP://server.domain:8000/SAP/BC/WORKFLOW_XML/?~localkey=WS90000074</Key>
<Operation>CreateProcessInstance</Operation>
</WfMessageHeader>
<WfMessageBody>
<CreateProcessInstance>
<Key>HTTP://server.domain:8000/SAP/BC/WORKFLOW_XML/?~localkey=WS90000074</Key>
<ContextData>
<YOUR_CONTEXT_VARIABLE>x</YOUR_CONTEXT_VARIABLE>
</ContextData>
<StartImmediately>Yes</StartImmediately>
</CreateProcessInstance>
</WfMessageBody>
</WfMessage>
regards
Steve
Maybe you are looking for
-
Issue on Solution Manager 4.0 installation SR3
Dear all, During the Oracle Client installation phase of a SAP Solution Manager 4.0 system installation with sapinst, I get the following error ERROR 2008-01-21 16:04:06.776 [iaxxejsbas.cpp:178] EJS_ErrorReporter FJS-00003 TypeError: linkTarget has n
-
Problems setting logo - Forms 11g
I've read the manuals, and followed instructions but still cannot get my company logo to appear in the top right hand section of the window bar for Forms 11g using just a image/icon of GIF/JPG file type in any of my directories on my Linux box. On th
-
Process chain to run every other Thursday (with exception of 53rd week)
Hello Friends, I am trying to find a way to set up my Process chain to run every other Thursday (with exception of 53rd week). I am hoping that I can perform this via Decision variant. Any advice would be very much helpful. Regards, Vinoth V
-
hi all, i am trying to color a row in a table, my table contains 2 columns and about 100 row, whenever the second row contains the word "Updated", I want to highlight the ENTIRE row yellow, the code i provide below, only highlight the "cell" contains
-
Business scenario to define material combination via batch characteristics.
Dear all, There is one business scenario. Condition is some of the raw material just could only be available for some special material and not available for normal mixture on BOM master. Could you please help whether we can define the below scenario