Serial.llb, sub vi is not executable

Hi ALL
I am not sure what happend for serial.llb in my labview program. serial port write.vi, serial port read.vi, serial port init,vi are not exexcutable. So my program can not run.
Could you help me check it?

broken line
Attachments:
serial port write.JPG ‏45 KB

Similar Messages

Simulation interface toolkit: SUB VI not executable error

Hi;
I have a real-time application where I model things in Simulink and use Simulation Interface Toolkit to carry out hardware-in-the-loop simulations. As a real-time target, I am using NI-PXI8106 with NI-PXI6251 DAQ card on it. Up until now, I was able to run my code just fine. However, for some reason, my vi didn't work today and gave several errors such as:
SubVI NI_SIT_sitclient.Lvlib:RVE.vi: SubVI is not executable
Details:The SubVI is not executable. You must fix all error in the subVI before this VI can run.
SubVI NI_SIT_sit Init Model.vi: SubVI is not executable
Details:The SubVI is not executable. You must fix all error in the subVI before this VI can run.
This is just few of many error that I received...In the details section of the error list window, the error statement are usually like the following:
SUBVI not supported for current target..
Type not supported in the current target...
The only thing that changed since the last time I ran this program with success is the IP change of the target machine..However, when I use Measurement and Automation tool, I am able to access my target machine (PXI8106) without a problem...Maybe there are some certain rules for IP settings on the PXI target? ...I can provide the details of my new IP configuration numbers if necessary...
I also reinstalled the SIT 5.0 on the target machine but It didn't do the trick. I am wondering if there is anyone out there who can help me out with this problem..
Thank you so much!
Kind Regards.

Hi there,
I was just wondering if you did manage to solve this problem. I'm a new user and have recently started using the Simulation interface toolkit. I have created my model using Simulink and used the real-time workshop to convert it to a .dll file. I tried to run it on labview and it seems to build it on the realtime target, however as soon as map it to the hardware (using a NI BNC-2111,It's just a bunch of analog inputs and output which I have connected to a voltmeter), a dialog box pops up with the the following error:
Error 1003 occurred during host VI initialization: SIT_test1.vi >> NI_SIT_sitclient.lvlib:sit Init Model.vi >> NI_SIT_sitclient.lvlib:sit Connect to Target.vi
<append>=========================
Simulation Interface Toolkit: The driver VI (SIT_Test_Driver.vi) is not executable.
Check the following:
1) You have not modified the driver VI.
2) You properly installed SIT and any necessary driver software on the target.
3) The target has not been locked from Measurement and Automation Explorer.
Do you want to launch the SIT Connection Manager dialog box and reconfigure the simulation?
Please look at the JPEG picture attached below to see how the error looks on my monitor.
Thanks
Attachments:
error1.JPG ‏135 KB

I have some problems while passing control array as refernce to the sub vi and sub VI crashes not deterministically after few minutes

Hallo every body,
i have some questions when i am passing the refernces to the sub_VI
1)when i run the application, the blink indicator(in main VI) starts blinking. even in sub_vi for true case i set it true and for false case i set it false. why from begining of the execution it starts blinking?
2)the stop button i am using in main VI is too slow. when i press the stop button it takes too much time to stop the application. why?
3)the array control (amplitude, freq,total time taken )
i am creating references of array. then these references i am sending to for loop. where it will convert as scalr values and then these scalar values to the sub_vi. opposite to it i am getting the reference of scalar cycles value and i am buliding an array of these scalar cycles to show it in indicator. it seems not to be working properly. why?
for this exexution some times i get error 91.
4) sometimes in the begining i get error 1055. why?
5) my sub vi crashes not deterministically.some time times after 2 minutes. some times after 5 minutes. by crash i mean i dont get an error but on the oscilloscope i see not smooth sine signal, but some strange broken, unbroken, delayed(all together mixed signals). why?
thanks for the important suggestions.
Regards
Attachments:
Check0.llb ‏204 KB

1) At some point the Blinking property gets set. Then the errors result in the program terminating. The property never gets reset. Setting a Property node in the main VI with Blinking = False prevents this.
2) You have 1 second Wait until next multiple delays in both the main and subVI loops. Depending upon which delays have executed when you push the Stop button it can take two seconds or more before all the loops execute again and note the Stop button.
3) The references are to arrays. (Time Taken, Amplitude, Cycles and Frequency) but you are connecting scalar values to the Values properties. Variant does not mean you can connect anything and it will convert to what you want. Once the Type has been set (when the control was created), the property node input matches that type.
4) 5) I never got this far so I cannot explain these errors. However, I suspect that once you fix the others, these will either be fixed also or the cause will become more apparent.
Lynn

Why is VI not executable using Labview 7.1 Run-Time Engine?

Hi,
In our Teststand sequence, we have a Labview Action step which is returning an error: "The VI is not executable", along with the error code: -18002.
This error occurs on a Production PC using the L.V. 7.1 Run-Time Engine.
I'm aware of Mass Compiling to ensure all the VI's are the correct version, but this has not resolved the problem.
The software was installed on the production PC using a Teststand created installer, with the Labview Adapter set
correctly to the Run-Time Engine, i.e. not trying to open the Labview Developer Server to execute the step at run time.
Because it's the 1st Labview module to be executed, I added another similar step to run beforehand, i.e. the new simple
Labview code ran first. This executed correctly, but then the next step caused the error above.
The small number of associated sub-vi's are on the target PC, and have been mass compiled.
I've had -18002 errors before, but this is one I cannot cure.
All suggestions gratefully received.
Gary.

Hi Guys,
Regarding this -18002 error when using the Run Time Engine instead of the Development Environment, what is the VI within the step that is failing (in any of the cases you've mentioned) trying to do? Are they built around any toolkits?
In my experiments with a simple VI (with just a user dialogue) using the LabVIEW 7.1 RTE in both TestStand 3.1 and 3.5 this morning, I haven't found any issues
There is a possibility if any of the sub-VIs or toolkits you use contain a Merge Errors.vi, that the Run Time Engine picks up a copy of the VI built for previous versions of the RunTime Engine (due to the order in which the sub-VI directories are scanned), and it cannot convert it.
There are a few solutions for this, the easiest one looks to be to copy the error.llb\Merge Errors.vi for LabVIEW 7.1 into the same directory as the VI you're calling (so TestStand can pick it up easily).
Can you let me know if this solution helps at all? If not, would it be possible to post up any of the code or sequence you're having problems with?
Best wishes,
Mark
Applications Engineer
National Instruments

TestStand - Call Package VIs for Distribusion.vi is not executable

I am trying to assemble my VIs for Run-Time distribution using the TestStand tool. How ever on selecting the Run-Time distribution option, the following error is displayed
"An error occurred in the 'Package VIs' step of the 'Package VIs' sequence in 'VI Packager.seq'.
LabVIEW : VI is not executable.
An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001"
On oppening the vi (TestStand - Call Package VIs for Distribusion.vi)it was seen to have brken arrows. The problem appears to be located in the sub vi, TestStand - Build dist for TestStand.vi which is password protected. Could this be a problem with my ActiveX connection(TestStand is using the LabView standard prototype Ada
pter with the LabView Development environment serving as the ActiveX server.The sequence I am trying to package runs successfully under these condisions)?

Hi,
One of the things you need to do is to ensure all your vi's are at the same version of labview. All TestStand assoicated llb's and Vi's are at version 5.1.1 when you first install it.
Therefore, if you have updated your labview, you will need to mass compile the TestStands folders.
Also, check the Updates for TestStand, http://digital.ni.com/softlib.nsf/954feaeea92d90918625674b00658b83/e047ebba4b45a98786256949007bc2a7?OpenDocument this may or may not affect depending on what TestStand and LabVIEW versions you are using.
Regards
Ray Farmer
Regards
Ray Farmer

I get a "vi is not executable" error when building an application.

I have an ongoing project that has worked fine in the past when building an application. I have recently added some report generation toolkit vis(Excel) and get an error for some of the ni vis and some of my own that call lower level excel vis. The error is that he vi is not executable, however they run fine in the development environment. I do not get this error if I save all vi's into one llb with save with options command and then build. However, when I try to run the app, this error re-appears. Also, do I have to add the dynamically loaded vi's that are part of the toolkit in my build script? Could this be the cause of the problem? If so, what's the best way to find all of them? Any suggestions?

You have hit in on the nail! You do need to add the dynamically loaded VIs when you are creating an executable from your VI. You need to add _wordsub.lib and _exclsub.lib as dynamically loaded VIs into your executable. Try this and let us know if you have any more problems with it.
J.R. Allen

SSIS Script task not executing macro through SQL Agent (but it does through bids)

Hello everyone,I am having an issue with SQL Agent when executing a macro contained in a script task component. The script task actually opens an excel file, runs the macro, save and closes the file. When
I execute the package via BIDS/Visual studio, it works like a charm. However, when i execute the package with SQL agent, the package runs successfully but it seems that the macro is not executed as the excel file has not been modified as it should have. Also,
the history log does not show any error messages. Could 

Thanks!I did create a credential and a proxy too but still the macro is not executed.I have searched online for solutions but no one has experimented this kind of issue before it seems. Please have a look at the script task code:
Imports
Excel = Microsoft.Office.Interop.Excel
Imports
System
Imports
System.Data
Imports
System.Math
Imports
Microsoft.SqlServer.Dts.Runtime
<System.AddIn.AddIn(
"ScriptMain", Version:="1.0",
Publisher:="", Description:="")>
<System.CLSCompliantAttribute(
False)> _
Partial
Public
Class ScriptMain
Inherits Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTARTScriptObjectModelBase
Enum ScriptResults
Success = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Success
Failure = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Failure
End
Enum
Public
Sub Main()
Dim Macro_name
As
String
Dim ExcelObject
As
New Microsoft.Office.Interop.Excel.Application
Dim oBook
As Microsoft.Office.Interop.Excel.Workbook
Dim oBooks
As Microsoft.Office.Interop.Excel.Workbooks
Try
Macro_name =
"Macro001"
ExcelObject =
CType(CreateObject("Excel.Application"),
Excel.Application)
ExcelObject.Visible =
True
ExcelObject.UserControl =
False
ExcelObject.DisplayAlerts =
False
oBooks = ExcelObject.Workbooks
oBook =
CType(oBooks.Open("C\Book1.xls"),
Excel.WorkbookClass)
ExcelObject.Run(Macro_name)
Catch ex
As Exception
ExcelObject.Application.Quit()
ExcelObject.DisplayAlerts =
True
ExcelObject =
Nothing
End
Try
Dts.TaskResult = ScriptResults.Success
End
Sub
End
Class

Error 1003 - The vi is not executable. Simulated DAQ-cards.

Hi all,
I am updating an application written in LabVIEW 7.1 for a customer. The code is not made by my company and is pretty horrendous but it works. I can not develop the code on the machine that it is supposed to run on so I have to do it on my own computer which means that I have to simulate two DAQ-cards that the program needs. I have pretty much finished the program and I want to test if I can build an exe-file. This is where I run in to trouble an get the error message:
Error 1003 occurred at \\Server1\Users\martinh\LabVIEW Data\app\internal.llb\_Main.vi
Possible reason(s):
LabVIEW: The VI is not executable.
I know that this has been discussed at length here and that one has to look out for global variables, dynamically loaded VI:s etc. My question is, does anyone think that the simulated DAQ-cards give me trouble? Do they use some VI:s placed somewhere odd which I need to include when I build the application?
Sincerely
Martin

Hi Martin,
I suggest you try what is suggested in this link, some of the information is already covered in the posts above but some might be new.
http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02?OpenDocument
If you are using the office toolkit, it might be an idea to masscompile the _office folder and you might also need to uncheck the "Disconnect type definitions and remove unused polymorphic VI instances".
Good Luck
Andreas E
Applications Engineer
National Instruments

The VI is not executable. The full development version...

"The VI is not executable. The full development version of LabVIEW is required to fix the errors." That is the error I've been dealing with all day. Actually it is repeated 3 to 4 times in the error message, seen when first launching the EXE. Also of note is that the run-arrow is broken. This is in an EXE that was developed well before version 2013, but I recently upgraded it to 2013 to hopefully fix some random LVRT crashes. There is obviously no issue running the code on my development machine, only once it's deployed.
The good news is I've been able to solve the problem (mostly). My EXE now runs without the errors. I found that the problem wasn't actually in the EXE.
We have a separate project with no files, but in the build specification we have the LabVIEW 2013 Run-Time Engine, as well as NI-VISA for serial support. We then bundle the deployment in a self-extracting RAR and it does its business. In the past this has worked just fine, but with LV2013, it seems that there is a component missing from the deployment.
I found that if I download the Run-Time Engine directly from NI.com and run it, the only things I need to install are the Run-Time Engine, and the DEPLOYABLE LICENSE. If I do this, my EXE runs great, but with the custom installer, it is not included for some reason!
Putting aside the fact that I don't know why the Deployable License package is needed (we aren't connecting to remote panels), I can't seem to modify my custom installer to install the Deployable License. There are versions for LabVIEW 2009 and 2011 SP1 in the Additional Installers list, but I don't see 2013.
Can anyone explain why this is??? For now I will just distribute the 257MB Run-Time Engine and the NI-VISA installers separately I guess. But I'd really like to get back to a single, simple package to install all the prerequisites we need. HELP!

iannicholson wrote:
Yes, but then every installer I build will contain the runtime engine. That gets very large very quick. So I have an installer for JUST the runtime engine and VISA runtime.
Just remove them from the "Additional Installers" tab of the Installer dialog.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Insert statement is not executing.....

From below procedure the insert statement is not executing....
update statement is working perfectly but insert......
create or replace PROCEDURE PAYMENT(AMT NUMBER,UID NUMBER) IS
AMT1 NUMBER;
AMT NUMBER;
PD VARCHAR2(100);
C1 NUMBER;
PER NUMBER;
ACC1 VARCHAR2(15);
CF NUMBER;
CRF NUMBER;
ACC2 VARCHAR2(15);
begin
SELECT PAY_DESC INTO PD FROM SUB.PAYMENT_TY WHERE ORD=0;
SELECT NVL(AMOUNT,0) INTO C1 FROM FOOD.MEMBER WHERE LTRIM(RTRIM(UPPER(NAME))) LIKE
LTRIM(RTRIM(UPPER(PD)))
AND USER_ID=UID;
IF NVL(C1,0)>AMT THEN /*CASH*/
C1:=C1-AMT;
SELECT ACCOUNT_CODE INTO ACC1 FROM SUB.MASTER WHERE PAY_CODE=2;
INSERT INTO ACC(AMOUNT_TD,ACC_CODE,EN_DATE,FO_TYPE,PART) VALUES(AMT,ACC1,SYSDATE,'JV','CASH
PERCENTAGE FOR '||45457);
STANDARD.COMMIT;STANDARD.COMMIT;STANDARD.COMMIT;
UPDATE FOOD.MEMBER_DET SET AMOUNT=C1 WHERE USER_ID=UIDAND C_COD=2;
STANDARD.COMMIT;STANDARD.COMMIT;STANDARD.COMMIT;
END IF;
end;the values receiving in insert statement is correct values.
how to resolve this?
Thanks skud...

Check for too many rows or no data found exception.
And also check the number of rows either inserted or updated.
Something like this:
create or replace PROCEDURE PAYMENT(AMT NUMBER,UID NUMBER) IS
AMT1 NUMBER;
AMT   NUMBER;
PD    VARCHAR2(100);
C1    NUMBER;
PER   NUMBER;
ACC1 VARCHAR2(15);
CF    NUMBER;
CRF   NUMBER;
ACC2 VARCHAR2(15);
begin
begin
    SELECT PAY_DESC
    INTO PD
    FROM SUB.PAYMENT_TY
    WHERE ORD=0;
    exception
      when too_many_rows then
        dbms_output.put_line('Too many rows in first SELECT');
      when no_data_found then
        dbms_output.put_line('No data found in first select');
end;
begin
    SELECT NVL(AMOUNT,0)
    INTO C1
    FROM FOOD.MEMBER
    WHERE LTRIM(RTRIM(UPPER(NAME))) LIKE LTRIM(RTRIM(UPPER(PD)))
    AND USER_ID=UID;
    exception
      when too_many_rows then
        dbms_output.put_line('Too many rows in second SELECT');
      when no_data_found then
        dbms_output.put_line('No data found in second select');
end;
IF NVL(C1,0)>AMT THEN /*CASH*/
    C1:=C1-AMT;
    begin
      SELECT ACCOUNT_CODE
      INTO ACC1
      FROM SUB.MASTER
      WHERE PAY_CODE=2;
      exception
        when too_many_rows then
          dbms_output.put_line('Too many rows in third SELECT');
        when no_data_found then
          dbms_output.put_line('No data found in third select');
    end;
    INSERT INTO ACC(AMOUNT_TD,ACC_CODE,EN_DATE,FO_TYPE,PART) VALUES(AMT,ACC1,SYSDATE,'JV','CASH PERCENTAGE FOR '||45457);
    dbms_output.put_line('Insert ' || sql%rowcount);
    COMMIT;
    UPDATE FOOD.MEMBER_DET SET AMOUNT=C1 WHERE USER_ID=UIDAND C_COD=2;
    dbms_output.put_line('Update ' || sql%rowcount);
    commit;
END IF;
end;
/UNTESTED!!

App Builder produces "Not Executable" error with Strictly Typed VI Refs

There is a very frustrating problem with the app builder in LV 8.0.1. Certain VIs compile and run fine in labview, but the app builder
refuses to make them into applications.
The error message is very long and ends with something like "The VI is not
executable". Standard advice for this problem is to force LV to recompile
everything you're building by either mass compiling or ctrl-shift clicking the
run arrow, but this hasn't worked for me in two separate cases (completely
different projects).
It seems that this problem is caused by wiring a strictly typed VI reference to
an invoke node with the FP.open method selected. In both cases I resolved
the issue by changing the Static VI Reference to be weakly typed (right-click
the static vi reference and make sure "Strictly Typed VI Reference"
is unchecked). After that, the project build successfully.
This is very hard for a user to track down for several reasons:
- The error message in the application builder does not give any
indication as to what the real problem is
- The app builder reports that the top-level VI is broken, even when the
strictly typed reference and invoke node may occur in a sub VI
- Nothing (that I can
find at least) in the documentation suggests that strictly typed references
won't work with the Open.FP method.
There is a page that says "some of the properties and methods do
not work when you configure this function to output a strictly typed VI
reference," but no indication is given of which methods fail
Note that in one case I was also able to make the project
build by deleting an instance of "IMAQ Create.vi" from the top-level
VI. I
have no explanation for this.
Hopefully this post will save some other users the trouble
of tracking this down and maybe even get NI to correct the issue for future
versions.
Adam Brewster

Hello Adam,
Thank you for sharing your experience and insight. Your post was well thought-out and offered a
good description of the problem as well as some possible workarounds. I believe that the issue has been filed and
is under investigation (3TU8T8V9). Feel
free to post back after the next LabVIEW release and inquire as to its status.
Thanks again,
Travis M
LabVIEW R&D
National Instruments

Please help suggestions for solving built-only compiler error: 'The VI is not executable. The full development version of LabView is required tofix this error.'

We have develoepd a software tool and build it on regular basis. It currently runs error free when compiled in the editor, but when we built it and run the executable stand alone we get the error.
'The VI is not executable. The full development version of LabView is required tofix this error.' plus a broeken error.
This menas an compiler error that is not present in the editor but in the stand alone version. We tried to identify errors as suggested in several posts in this forum, but so far unsuccesfull.
As the editor and its compiler do not see the error and are running fine and the stand alone version just syas 'find the error in the editor' in this case LabView is of no help.
Can anyone suggest a sensible or 'good practice ' way of searching for the source of this error?
Our project comprises hundreds of Vis over several libraries.
Thanks,
Chris

Thanks Craig for all your suggestions.
We seem to have located the problem in a new vi just added to the package causing conflicts by using the same vi names as other vis already present in the package. Excluding this vi removed the error.
It seems related to a conflict by having two vis with the same name, which was mentioned by LabView and interactively resolved when running the main vi from the editor. When successfully building the main vi the builder did not mention this conflict and reported a successful build, but when trying to run the executable it gave the cryptic error. The error caused us problems because there was no hint for the cause, just the suggestion to solve this in the editor, while at the same time in the editor the VI was running fine.
We will post about this in detail after we have positively proven that this actually was the case.
The .net version issue was already checked.
Performance was the same on all machines we tested on including the dev machine.
Debugging was tried nut did not help as the vi could not run (broken arrow). We assumed that debugging only helps in running faulty functioning vi''s. We did not check for broken arrows in sub-vis (after connecting), that could have helped, although our application has hundreds of our own vis.
In relation to your remark:
'Are you using many classes? Have you verified that the proper access scopes are set for functions calling those vis?'
Could you elaborate on setting access scopes. We were not aware of this option in LabView, although we realize this is a basic element of the underlying c code.
Ragrds,
Chris

Event R401 not executing

Dear Experts,
During billing i am posting some debits and credits at the same time to customer account. I want them to be cleared when i invoice them. i read posts of other people who have similar problems but after debugging i realised that system is not executing event r401 at all for some reasons.
i have made the config where we need to define clearing type and clearing category and check the acct maint indicator. table te514 and te529 also configured
Also please tell if there is any way of knowing which clearing variant is being executed at acct maint(if any)
Any help would be highly appreciated
Thanks!

Dear Experts,
I have been debugging ISU_INV_ACC_MAINTENANCE but I still havenu2019t achieved what I wanted to do so I tried a few different scenarios. Please let me know if it is supposed to work the way I want it to. Please assume that the necessary configs have been done
Scenario 1
-     I billed a consumer using periodic billing. The schema was such that two debit items were posted of say Rs 100 and a credit item was posted for say Rs 100. So in effect the receivables are 100.
-     I ran invoicing
-     Using fpl9 when I see consumer balance it shows three line items. Two for the debit receivable and one for the credit.
-     Desired result was that during invoicing, the system would run something like automatic clearing and would clear one of the debit with the credit(as per clearing rules). However this did NOT happen
Scenario 2
-     I posted a downpayment request for some consumer of Rs 100(Downpayment has clearing restriction 8)
-     Customer paid Rs 100.
-     I billed the consumer using periodic billing. The schema was such that two debit items were posted of say Rs 100 and a credit item was posted for say Rs 100. So in effect the receivables are 0 because we already have received a downpayment of 100.
-     Desired result was that the credit posted during billing would clear with one of the debits of the bill and the downpayment would clear against the other debit posted during billing(as per clearing rules). However, no clearing took place and all documents are intact
These are the comfigs I have made
i)     Acct maint has been set to active against the clearing type in u2018additional controls for invu2019
ii)     Table TE514 maintained with mains and subs and clearing categ and clearing type
iii)     Clearing variant assigned to R41 and R4 in FI-CA
iv)     Invoicing document shows clearing type R41 in ea40
Please suggest if this isnu2019t the way the system is supposed to behave
Would really appreciate. Feel free to ask if any confusions

VI seen as not executable from LV runtime, correct in LV development

My current problem is the following:
On the same PC, having TestStand 4.0 & LabVIEW Development 8.5, I try running a sequence with both adapters: LV development 8.5 and LV runtime 8.5.
My sequence steps call VIs that call subVIs in a full hierarchy (let's say 1500 VIs are involved in a test sequence).
The sequence runs with the development adapter, and with the runtime, I got a -18002 LabVIEW error: Vi not executable, broken, etc.
Of course, when I open the VI within the development environment, everything is correct.
As I'm testing both adapters on the same PC, the full hierarchy, including LV libraries provided with LV development are at the same location.
Due to the large amount of VIs I use, I cannot guess which LLB could be missing or not inaccessible.
Is there a way to investigate the cause, despite the fact that everything is correct under the development environment?
Is it possible to tell the LV runtime where it should search for LLBs or other required dependencies that the LV development seams able to find?
Thanks in advance for your help,
JJD
Solved!
Go to Solution.

Hello,
I've seen this error when two VIs withthe same name were loaded in memory; this VI was called from a TestStand sequence and from the user interface (very poor design of a customer that I will not mention ^^).
I'm not sure to understand youy problem: everything works fine when you are using Developpment system (Active Version 8.5) but, do you have this error when you set the adapter to LabVIEW Run-Time Engine 8.5, right? Are LabVIEW and/or VIs used in your sequence open when you run your sequence in Run-Time mode?
Cordially,
.mrLeft{float:left} .mrInfo{border-left:solid 1px #989898;font-size:x-small;color:#989898}
Mathieu R.
  CTD - Certified TestStand Developer / Développeur TestStand Certifié
  CLAD - Certified LabVIEW Associate Developer

Waiting for approval item does not execute attached procedure !

Hi.
Using 3.0.8 on Solaris.
Create one custom item type and associate one on plsql procedure to be run in place when item is listed within its folder.
Go to folder, add item, look for the plsql result : Good it's working !
After that create an item as a create with approval ACL and come back as folder owner, look at the plsql result : NOTHING !!!
My PLSQL procedure is displaying some attributs in order for the folder owner to approve or not the waiting item. So if wainting for approval items does not execute associated plsql function as they are "waiting" (active=0) then I've got some problems!
Any suggestions ?

Hi all,
Thanks very much for your feedback.
In reply to Brian's suggestions
1. I checked to see if WS14500013 was defined as general task; it was not and this has has now been rectified. Went through the other workflows also.
Double checked the contents of the tables:
APPROVAL_TABLE, ITEM_APPROVAL_TABLE, ITEM_APPROVAL_OBJECT.
All appeared OK.
Created a simple one line SC. Invoked approval preview and the message: 'Approval step without ad-hoc capability. No preview possible' was displayed. This is odd since WS14500015 and sub-workflows do not use AD-HOC approval. Or am I not understanding this correctly.
Followed Smitas suggestions but to no effect.
Here are the contents of the said tables which I lifted from the workflow tables:
Again, many thanks for your responses...
**APPROVAL_TABLE****
NAME="APPROVERLIST:ApproverList:" <APPROVAL_INDEX>0000000001</APPROVAL_INDEX>
<APPROVAL_BRANCH>0000000001
<APPROVAL_AGENT>USMGRR11000
<APPROVAL_STATE>0000000002
<INITIAL_AGENT>USMGRR11000
<INITIAL_INDEX>0000000002
**ITEM_APPROVAL_OBJECT***.
NAME="ITEMAPPOBJTABLE:ItemAppObjTable:" - <item>
<SC_GUID>957117374BC6434882B0BFD5462A2724</SC_GUID>
<APP_CRIT_NAME1>COST_CTR</APP_CRIT_NAME1>
<APP_CRIT_NAME2>ORDER_NO</APP_CRIT_NAME2>
<APP_CRIT_NAME3 />
<APP_CRIT_VALUE1>R11000</APP_CRIT_VALUE1>
<APP_CRIT_VALUE2 />
<APP_CRIT_VALUE3 />
<APPROVAL_OBJECT_GUID>9E6EFAC500B681458284BBB60BF99C8A
*****ITEM_APPROVAL_TABLE***,
NAME="APPROVALITEMLIST:ApprovalItemList:"
<item>
<APPROVAL_OBJECT_GUID>9E6EFAC500B681458284BBB60BF99C8A <APPROVAL_ITEM_GUID>1137519335F51C4DB3D2844A8AD484C0

Serial.llb, sub vi is not executable

Similar Messages

Maybe you are looking for