Error Cluster Propagation Issue

Consider the following diagram:
This VI is intended to be used in a chain of VIs.
This VI copies a file to a folder, and in case of error, tries with another path of the file (located in a "backup" location)
Due to the intrinsic dataflow programming model, how can I manage the error in the arrow place????
The behaviour I want is this:
if (error in == true) --> skips all and propagates error_in to error_out
else { try to copy, and in case of error try with backup copy. If errors again then report the error (custom error code) }
Is it possible???
thanks
Solved!
Go to Solution.

thanks all,
the note about the "lost warning" was really interesting, I never noticed it because I never used warning.
I discovered another source of bug.
Consider the following:
If error_in is true, the error_out would be false.
The reason is that the filename array is EMPTY and the for case is never executed, so error_out takes a default value.
As a consequence the error is not correctly propagated.
I think this is not trivial to see at a first glance.

Similar Messages

Error during propagation process in streaming

I am getting following error during propagation
ORA-12170: TNS:Connect timeout occurred ORA-12170: TNS:Connect timeout occurred
In order to resolve this i add following lines in sqlnet.ora on both nodes, but problem is still there....
SQLNET.SEND_TIMEOUT=300
SQLNET.RECV_TIMEOUT=300
SQLNET.INBOUND_CONNECT_TIMEOUT=300
SQLNET.DEFAULT_SDU_SIZE=32767
SQLNET.RECV_BUFF_SIZE=655336
SQLNET.SEND_BUF_SIZE=65536Need your help in resolving this issue........

Hi,
What is Resp. Resolver Name and Decision Type in your Process Level Definition? Did you create custom agent BADI implementation?
Regards,
Masa

Windows server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
Any suggestion on resolving this problem?
Thanks
Ikad

Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
Ikad

Stub out Error Cluster from Error Code.vi?

When I profile my application, I find that the biggest consumer of CPU time is the Error Cluster from Error Code.vi, called from a number of locked NI libraries. How can I stub out this .vi, replacing it with basically a pass-through? I tried creating a project specific .vi with the same name, and when I open my project all the project and vi.lib .vis used link to it, but they all come up broken and have to be re-linked, which I can't do in the locked .vis (I matched the ins and outs and connector pattern). I can't edit the Error Cluster...vi directly, getting a message about the .vi being used by another application even with a clean start of LV and going directly to that .vi in the library (and I would prefer to not mess with the vi.lib version anyway). Any suggestions? Thanks. LV 2011.
Matt

If you have the LLB manager open it reserves your VI in a different appliation instance, therefore it is locked and no editing. Simply close the LLB manager and you can whack away at that VI.
I doubt that the shared clone setting plays much of a role here, there are some deeper issues. A rather amusing VI in a few ways:
In order to show the VI Title instead of the Name you Open a VI reference which is going to stick you into the root loop. 10 reentrent clones simply means 10 copies waiting in line for the root loop. A non-reentrent version would simply have 10 copies waiting to run. Minus the root loop issue, reentrency is the way to go, and on a desktop machine shared clones is typically quite effective.
It can't be a slow VI, look Trim Whitespace was inlined manually to avoid a performance hit! In a loop maybe, but really, shaving off the overhead of a single subVI? That's optimization.
But wait, all of that and much, much more is given right back by the use of Delete From Array to remove the first element of the Array. Bad on so many levels. Delete From Array is a data copy machine, and now you are doing one needlessly. Array subset is your friend here, tells the compiler you are only reading, nothing to get excited about. Pull it outside the case structure, you are ditching the first element twice in the two branches.
Concatenating strings in a loop, also a recipe for fun. Often there are ways to leverage Array to Spreadsheet string for better performance, or build a string array and then concatenate at the end. Probably not a big deal here, how big are call chains really, but if you are inlining subVIs by hand then you should really be frying the bigger fish.
I find myself in your shoes fairly often. Some clunker in vi.lib causes a bug or sluggish performance. You either ditch the NI code and roll your own, or make it work on your machine but not others, or chalk it up to the cost of doing business. I have tried on numerous occasions to suggest that all patches to vi.lib be made readily and freely available to all previous versions of LV that are compatible. Let's say this VI got tweaked so it was a bit more performant for you, at least enough to be viable. Then you could happily use the patched version in LV11, and if you went to a different machine you would simply make sure vi.lib was up-to-date. These types of patches could roll out incrementally as needed, less need to cross your fingers that you won the CAR lottery with each new version of LV. (I guess most lottery winners don't shell out $$$ to collect their "winnings" though).
After all that what would I do here? I would wrap that sucker inside a disable structure (provide minimal functionality, like pass through caller name, code and error instead). Then I would check the performance again. Now you have a data point as to whether or not it is worth it to proceed.

Adding server in DAG failing with error Error: Cluster API failed: "AddClusterNode() (MaxPercentage=25) failed with 0x800706ba. Error: The RPC server is unavailable

Hi, Below is teh environments
DC: Win 2008 R2 SP1
Exchange Server OS: Win 2012 R2 Std
Exchange : 2013 SP1 Ent
Two Servers with CAS+MB role, already part of one DAG. I am trying to add one new server in existing DAG. The installation of exchange 2013 competed successfully. However when i am adding it to the existing DAG, the below error is coming. Please help
to solve the issue. Thanks in advance.
A server-side database availability group administrative operation failed with a transient error. Please try the operation again. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "AddClusterNode() (MaxPercentage=25)
failed with 0x800706ba. Error: The RPC server is unavailable" [Server: cluster owner FQDN]
Manu

Hi Manu,
As Deepak mentioned, please try to enable IPv6 on all member servers first.
Based on my research, In Microsoft Exchange Server 2013, IPv6 is supported only when IPv4 is also installed and enabled. If Exchange 2013 is deployed in this configuration, and the network supports IPv4 and IPv6, all Exchange servers can send data to and
receive data from devices, servers, and clients that use IPv6 addresses.
Please also configure or disable Firewall to allow the connection.
Thanks
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]
Mavis Huang
TechNet Community Support

Should a dot net Invoke node fill the error cluster?

Situation, a dll called by LabVIEW attempts to communicate with an instrument and can not because the instrument is not present. The DLL returns a standard LabVIEW error cluster with no error.
Person A says this is wrong : it must return an error. Further modules in the chain can not succeed with no communication. And that it is possible to return an error by throwing an exception.
Person B says : The program ran and did not die. This is our module not a LabView function. The error cluster should return no error. And that it can not return an error either,
The questions are Who is right A or B? And , since is has already gotten to a ‘is to, is not’ kind of disagreement, Where is any supporting documentation to reference that will authoritatively resolve the issue?
Solved!
Go to Solution.

In order for the dll to produce an error in LabVIEW, it must be programmed to throw an exception if no instrument is available. LabVIEW will then convert this exception into a generic error with code 1172 (see attached article.) LabVIEW can be programmed to give a custom error message using the attached example. In this case, it should be possible to have the .NET dll throw an exception, and then have LabVIEW generate a custom error message to display to the user. In this instance, it appears that Person A is correct. Hope this helps resolve the issue.
LabVIEW and .NET Exceptions
http://digital.ni.com/public.nsf/allkb/B15CE9F2715434C386256D3500601878
Programmatically Generate Custom Error Codes/Messages
https://decibel.ni.com/content/docs/DOC-9557
Regards,
Chris L
Applications Engineer
National Instruments
Certified LabVIEW Associate Developer

Error cluster constant appears different in two locations on a block diagram

I am a newbie to LabVIEW. I have taken Core 1 & 2 and Machine Vision and I have not com across this before.
The image on the right is obviously an Error cluster constant used in the block diagram to create an Error cluster and wire it to an error out terminal. As far as I can tell the image on the left is about the same thing, but why does it look different? The different appearance causes raises a concern that there is a difference in behavior that I do not understand. LabVIEW help suggets that both are Error constants. When I create a new error constant, it always ends up appearing like the right image above. I have not been able to create someting looking like the image on the left.
Could someone please confirm what the image on the left is on a blck diagram?
Thanks,
Bill
Solved!
Go to Solution.

The image on the left is an error cluster control. It has a front panel presence and can be set either via the front panel or through a property node or local variable. The image on the right is an error cluster constant. It is a static value.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

ERROR: The Propagation operation ended in error. java.lang.reflect.Undeclar

Dear all,
i am using bea weblogic 10.0 ant i am downloading the running Inventory.
but the below problem occurc when i run ant task for downloading that is
ant -buildfile propagation_ant.xml downloadSrc the below problem occurs. i am new to bea so how can i debug the problem
VERBOSE: InventoryTreeWalker: visiting node: Application:ContentServices:BEA Repository:ContentNodes:Webmasters:Sports:I won`t step down from presidency Khan.txt
ERROR: The Propagation operation ended in error.
java.lang.reflect.UndeclaredThrowableException
at weblogic.security.providers.xacml.authorization.XACMLAuthorizerMBeanImpl.policyExists(XACMLAuthorizerMBeanImpl.java:245)
at sun.reflect.GeneratedMethodAccessor477.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.p13n.security.internal.SecurityProviderProxy.invoke(SecurityProviderProxy.java:48)
at $Proxy54.policyExists(Unknown Source)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate$3.run(SecurityPolicyDelegate.java:241)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate$3.run(SecurityPolicyDelegate.java:239)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.kernelRunAs(SecurityPolicyDelegate.java:433)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.policyExists(SecurityPolicyDelegate.java:246)
at com.bea.p13n.entitlements.management.internal.RDBMSSecurityPolicyManager.getSecurityPolicy(RDBMSSecurityPolicyManager.java:204)
at com.bea.p13n.entitlements.management.SecurityPolicyManager.getSecurityPolicy(SecurityPolicyManager.java:119)
at com.bea.propagation.content.online.util.SecurityHelper.getSecurityPolicy(SecurityHelper.java:146)
at com.bea.propagation.content.online.util.SecurityHelper.getSecurityPolicies(SecurityHelper.java:122)
at com.bea.propagation.content.online.hierarchy.ContentNodeHierarchy.discoverChildren(ContentNodeHierarchy.java:113)
at com.bea.propagation.framework.hierarchy.ListNodeHierarchy.getChildrenNodes(ListNodeHierarchy.java:113)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:215)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst(InventoryTreeWalker.java:158)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst(InventoryTreeWalker.java:102)
at com.bea.propagation.framework.tool.io.InventoryTreeExport.walkDepthFirst(InventoryTreeExport.java:88)
at com.bea.propagation.framework.tool.io.InventoryFolderExport.walkDepthFirst(InventoryFolderExport.java:110)
at com.bea.propagation.framework.tool.io.InventoryArchiveExport.walkDepthFirst(InventoryArchiveExport.java:103)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.writeInventoryToLocalFile(InventoryManagementServlet.java:1017)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.writeInventoryToLocalFile(InventoryManagementServlet.java:991)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.downloadOperation_Remote(InventoryManagementServlet.java:510)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.downloadOperation(InventoryManagementServlet.java:453)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.doService(InventoryManagementServlet.java:318)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.doPost(InventoryManagementServlet.java:199)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
ERROR: The Propagation operation ended in error.
java.lang.reflect.UndeclaredThrowableException
at weblogic.security.providers.xacml.authorization.XACMLAuthorizerMBeanImpl.policyExists(XACMLAuthorizerMBeanImpl.java:245)
at sun.reflect.GeneratedMethodAccessor477.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.p13n.security.internal.SecurityProviderProxy.invoke(SecurityProviderProxy.java:48)
at $Proxy54.policyExists(Unknown Source)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate$3.run(SecurityPolicyDelegate.java:241)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate$3.run(SecurityPolicyDelegate.java:239)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.kernelRunAs(SecurityPolicyDelegate.java:433)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.policyExists(SecurityPolicyDelegate.java:246)
at com.bea.p13n.entitlements.management.internal.RDBMSSecurityPolicyManager.getSecurityPolicy(RDBMSSecurityPolicyManager.java:204)
at com.bea.p13n.entitlements.management.SecurityPolicyManager.getSecurityPolicy(SecurityPolicyManager.java:119)
at com.bea.propagation.content.online.util.SecurityHelper.getSecurityPolicy(SecurityHelper.java:146)
at com.bea.propagation.content.online.util.SecurityHelper.getSecurityPolicies(SecurityHelper.java:122)
at com.bea.propagation.content.online.hierarchy.ContentNodeHierarchy.discoverChildren(ContentNodeHierarchy.java:113)
at com.bea.propagation.framework.hierarchy.ListNodeHierarchy.getChildrenNodes(ListNodeHierarchy.java:113)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:215)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst(InventoryTreeWalker.java:158)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst(InventoryTreeWalker.java:102)
at com.bea.propagation.framework.tool.io.InventoryTreeExport.walkDepthFirst(InventoryTreeExport.java:88)
at com.bea.propagation.framework.tool.io.InventoryFolderExport.walkDepthFirst(InventoryFolderExport.java:110)
at com.bea.propagation.framework.tool.io.InventoryArchiveExport.walkDepthFirst(InventoryArchiveExport.java:103)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.writeInventoryToLocalFile(InventoryManagementServlet.java:1017)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.writeInventoryToLocalFile(InventoryManagementServlet.java:991)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.downloadOperation_Remote(InventoryManagementServlet.java:510)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.downloadOperation(InventoryManagementServlet.java:453)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.doService(InventoryManagementServlet.java:318)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.doPost(InventoryManagementServlet.java:199)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

your error seems to indicate that your embeddedLdap isnt in sync with the Database ? Did you either delete files from your file systems or cleanup the portal db or finally used a copy of some existing database for your domain?

ESB errors not propagating to BPEL process

I am working in SOA Suite 10.1.3.3. I have an asynchronous BPEL process that is orchestrating a number of ESB services, most of which perform database operations. Occasionally an attempt is made to insert a record into a table which results in an error (e.g., null value inserted into a non-null field, record already exists, non-existent record in parent table upon which current table depends, etc.). This correctly results in an error in the ESB service that shows up in the ESB Control console.
The problem is that the error is NOT propagated upward to the invoking BPEL process (which contains all manner of fault catching branches to process the error, log it, send email notifications, and perform other database operations dependent upon the success or failure of the ESB operations). The BPEL process is therefore left "hanging" and never appears in the BPEL Control console as an instance. It shows up in the Manual Recovery queue as an essentially unrecoverable process.
I am assuming that this change in behavior (such errors formerly propagated to the calling BPEL) is a direct result of the new Fault Handling Framework. My question is: what do I have to do in order to restore the original behavior of the system (ESB service encounters an error and propagates the fault to the async BPEL process, which catches it and does whatever it needs to do to fulfill the requirements of the overall system)? Is this something that can be handled by changes to the BPEL/ESB system configuration, the BPEL process definition, the ESB service definitions, or some combination thereof?
Thanks for your time.
Paul Camann

Hello. We applied 10.1.3.3.1 MLR14 in late October 2008.
We are seeing large numbers of errors like this in the ESB log ($ORACLE_HOME/j2ee/oc4j_soa/log/oc4j_soa_default_group_1/oc4j/log.xml):
<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2009-01-26T13:11:15.497-05:00</TSTZ_ORIGINATING>
<COMPONENT_ID>tip</COMPONENT_ID>
<MSG_TYPE TYPE="ERROR"></MSG_TYPE>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID>biwsvlbat027.gdbiw.com</HOST_ID>
<HOST_NWADDR>1.2.3.4</HOST_NWADDR>
<MODULE_ID>esb.server.service.impl.soap</MODULE_ID>
<THREAD_ID>98</THREAD_ID>
<USER_ID>oracle</USER_ID>
<SUPPL_ATTRS>
<ATTR NAME="J2EE_MODULE.name">provider-war</ATTR>
<ATTR NAME="J2EE_APP.name">esb-rt</ATTR>
<ATTR
NAME="WEBSERVICE_PORT.name">__soap_Router_ODS_STAGE_Insert_ODS_STAGE_I_PortType</ATTR>
<ATTR NAME="WEBSERVICE.name">ESB_Router_ODS_STAGE_Insert_Service</ATTR>
</SUPPL_ATTRS>
</HEADER>
<CORRELATION_DATA>
<EXEC_CONTEXT_ID><UNIQUE_ID>1232993475:1.2.3.4:7097:0:307</UNIQUE_ID><SEQ>5</SEQ></EXEC_CONT
EXT_ID>
</CORRELATION_DATA>
<PAYLOAD>
<MSG_TEXT>Exception while print response</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[java.lang.NullPointerException
at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage
(EventOracleSoapProvider.java:215)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing
(ProviderProcessor.java:956)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation
(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing
(ProviderProcessor.java:466)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest
(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke
(ServletRequestDispatcher.java:713)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal
(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest
(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest
(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run
(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run
(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
]]></SUPPL_DETAIL>
</PAYLOAD>
</MESSAGE>
which is possibly the message that would come back from ESB to BPEL failing?
Thank you.

Prompt Propagation Issue across dashboard pages in a dashboard

I have a issue of prompt propagation in a dashboard, that is the various dashboard page prompts use same presentation layer column then the prompts are taking the filter values filters on each other dashboard. Even if I try to change the scope of each dashboard prompt to only dashboard page only the value propagates to next dashboard page.
I cannot redesign the whole dashboard as it will need lot of effort , I have implemented a fix for now but I am searching for some java script code which I could invoke using OnPageLoad event to clear and reset all the page prompts to defalut values.
Can you guys let me know if you have any java script like this.

Can some one provide a alternative solution to this issue.
Once more I am writing down the issue:
On a dashboard is multiple dashboard pages multiple prompts, but if there are some prompts common between those dashboard pages which basically shares the same column formula, then these dashboard do propagate their values from one dashboard page to another.
Even setting the dashboard page prompt scope to page only cant stop this values propagation issue form one dashboard to another.
I know to fix it I will have to redesign the whole dashboard but that will take lot of time and effort starting from RPD to Reports.
is there some fix to fix it in the OBIEE Answers itself without touching the RPD. I cant try changing the column formula with case statement as then the case will flow in the report query and it will not use the index defined on the columns.
Please let me know if some one can throw some light on this.

Feedback nodes in Error cluster

Some time back I
had posted a VI called Simple StateMachine template. Based on the
comments from fellow members I have redone it and am attaching it
herewith. ( LV7.1 + Win_XP Professional )
If you just open it and check the block diagram, you will notice that
LV has introduced a feedback node in the error cluster looping between
DAQMx function Write Digital Output and Read Analog input. I am not
sure why LV does this even though the two functions have no common
reference or relevance between them.
You can also try this : Just remove the data lines to the two Digital
Out functions, and also the error cluster with Feedback node . Rewire
the Error cluster but this time without the feedback node. And now if
you try to connect the Digital Out data lines, you will find that the
Data lines are drawn with feed back nodes !!
I am sure LV is trying to tell me something - only that I don't understand what it is. Can some one elaborate on this ?
Thanks
Raghunathan
Message Edited by Raghunathan on 07-04-2005 08:29 PM
Raghunathan
LV2012 to Automate Hydraulic Test rigs.
Attachments:
PRP_Main.vi ‏288 KB

You have an impossible loop in your code (Run it with execution highlighting to verify):
Dig8-15 relies on data from the case structure.
analog input 0-7 provides data into the big case structure
This means that Dig8-15 cannot execute until the case has executed, but the case must wait for data from analog out. LabVIEW is smart enough to insert a feeback node such that AI0-7 gets the error from the previous interation. This is NOT a desirable situration.
Without the feedback node, yuor code is broken. AI0-7 cannnot run because it must wait for DO8-15 to execute. DO8-15 cannot execute because it must wait for AI0-7.
You should:
Uncheck the diagram option "Auto insert feedback nodes in cycles" to make sure to get broken wires so it is easier to find the problem.
FIx your dataflow. Please make sure your wires flow left-to-right, it make errors like this less likely. You need to wire the error clusters in the order the subVIS execute.
I hope this is clear enough, but please ask is you continue to have problems. Good luck!
Message Edited by altenbach on 07-04-2005 07:18 PM
LabVIEW Champion . Do more with less code and in less time .

Pass an error cluster in and out of a C/C++ dll?

Hi all,
I'd like to know if it is possible to pass a LabVIEW error cluster to a C/C++ function from a dll. This would greatly help error handling in the different VIs.
I am able to access and modify the first two members of the error cluster; the error status and the error code, which are, respectively, boolean and integer. But I cannot modify the string. LabVIEW crashes completely doing so.
I first define a structure in C++ like this:
const int N = 512;
#pragma pack(push,1)
typedef struct lvcluster {
bool status;
int code;
char source[N];
} lvcluster;
#pragma pack(pop)
Then, I define a function that will access the members status, code and source:
int TestCluster(lvcluster *err)
err->code = 1;
err->status = false;
sprintf(err->source, 'Test');
I then use LabVIEW's "Call Library Function" to call this dll's function. I have set the parameter "err" to "Adapt to Type" and "Handles by Value". Trying to write characters to the source array crashes LabVIEW.
Is this possible at all? How should it be done?
Thanks!

Thanks all for the comments.
I've been looking at extcode.h where I saw the defeninition of a LStrHandle. It seems to be a pointer to pointer to "character array":
typedef struct {
int cnt; /* number of bytes that follow */
unsigned char str[1]; /* cnt bytes */
} LStr, *LStrPtr, **LStrHandle;
The "character array" is different than a C character array, see http://www.ni.com/white-paper/4877/en/#toc4
The first 4 bytes contain a signed 32 bit integer representing the number of characters. There is no NULL-termination character.
So the error structure should be something like this (modulo the size of boolean, thanks rolfk):
const int N = 512;
#pragma pack(push,1)
typedef struct lvcluster {
bool status;
int32 code;
LStrHandle source;
} lvcluster;
#pragma pack(pop)
From there, I was able to access a LabVIEW string from C. But I am unable to modify any of it. I might be able to change the characters from an alreay allocated string, but resizing or even creating a new string crashes LabVIEW. As reported by others, manipulating these strings would require linking against labview's library to access the string manipulation functions, but this is not possible as the library must be independant of LabVIEW.
The only last possible way I can think of is to allocate a new cluster inside the DLL. Then I might be able to change the string in it, and hopefully LabVIEW would pick it up. I don't know how LabVIEW manages its memory; would it garbage collect the input cluster that is not used anymore?
Thanks for all the feedback.

IMac error: Failed to issue COM RESET

After my iMac got slower en and freezed i tried resetting the Pram and in single user mode i did *fsck -fy*
then i get the following error:
*Failed to issue COM RESET successfully after 3 attempts. Failing...*
after that nothing worked anymore!!! only the Windows vista partition worked for a day or two. is this a harddrive failure something worse?
Message was edited by: Birkhoff (title changed)

I believe posting relevant facts is productive, & a very relevant fact here is that you are trying to use a drive with an interface (SATA-II) that Apple does not currently support in its laptops.
SATA-I controllers are supposed to be compatible with SATA-II drives, but many of them are not. The problem is how some controllers implement auto negotiation, which is supposed to tell the drive to fall back to SATA-1 speeds with the slower controllers. Some SATA-II drives have a jumper to force the slower speed if auto negotiation doesn't work; some do not.
How this compatibility problem came about, & why the jumper is required, is complicated but the short version is that at least four different specification bodies had some responsibility in producing SATA specifications, & not all controllers were designed to the same standards. This includes not just the controllers Apple has been using but those in many PC's as well.
So I agree that Apple dropped the ball, but not necessarily the way you might think: it should have made it very clear that the firmware update implemented an unsupported interface speed, that it might cause problems, & (most importantly) provided a reversion strategy to the former firmware if it did.
Hopefully, Apple will take another 'swing' at this & either provide that reversion strategy or a new update that at least allows the controller to work more reliably with the faster interface. But until then, unless your drive has the jumper, my previous suggestion is probably the best you can do.
BTW, none of the current mechanical drives available for laptops can saturate a SATA-1 bus except for brief bursts from the drive's buffer, so the real loss in performance of running a single SATA-II drive at SATA-1 speeds is almost negligible, something you might notice in a benchmark but not in real-world use.

Error during goods issue-Posting period not open

Hi ,
I am getting an error during goods issue which says posting period not open.I guess that we have had deliveries that were created and in process while crossing over from one financial period to another quite frequently before, but we were still able to goods issue them in the next period. Can anyone tell me why this error happens and if there is any work around for this?
Thanks,
Hari.

Hi,
Goods issue takes place, say on a given date and this should be updated, so that the plant valuation changes are recorded. But the periods need to opened to do this. Normally there are two posting periods available, one is in MM, done by t.code MMPV and the other in FI, t.code is OB52.
So, in MMPV we need have the current month as the posting period. But in your case it was allowing, probably because you have marked the indicator " allow posting in previous period " in MMRV t.code as our friend just conveyed.
Hope it helps. Please reward if useful.
Thanks & Regards
Sadhu Kishore

Does the error of the error cluster appear at invoke node?

I use a "Open VI Reference" with "Invoke Node: Run VI and Wait until Done= True" if the VI run and have an error. Does the error return to the caller/server?

No, you will need to use a CallByReference node to run the VI and then you can see the error cluster (if it is wired in the called VI's connector pane). Another option is to use the "Get Control Value" VI Server Method on the VI, to return the "error out" cluster of the called VI after the Run method is completed.
-Jim

Error Cluster Propagation Issue

Similar Messages

Maybe you are looking for