Packed project library 1003 error when building it

Hi,
I am trying to build packed project library, but I get 1003 error. I have tried all things suggested in other threads regarding the 1003 error, but nothing helps.
My two project HardwareSpecificFunctionalities and ModuleTemplate are attached. HardwareSpecificFunctionalities PPL is used in the ModuleTemplate's VIs. When I am trying to build ModuleTemplate PPL I get 1003 error saying that one VI is broken, but actually it is not. If I remove the ReadOffset.vi from the AcquisitionInitialization_Main.vi, the ModuleTemplate PPL is build successfully.
Have anybody an idea what is wrong?
Attachments:
PPL problem.zip ‏1230 KB

Hello Andrej.
I just noticed that in document LabVIEW 2011 and 2011 SP1 Known Issues (http://www.ni.com/white-paper/13164/en#323425_by_Category) it is stated that this bug will be fixed in LV 2012 (32 bit).
This version of LV will be available in August 2012.
All workarounds that are known, are the one that are described in this link.
Kind regards,
Sofija

Similar Messages

Packed Project Library error: contains compiled code

I was trying to figure out how the packed library works for LVOOP, but face a wall with an error and don't know how to solve it.
i) I made a class 'Class 1', which I then put in a library called 'library'.
ii) I create a Packed Library and set the top-level library in the source files
iii) Once compiled and saved, I create a new project and add the newly create Packed Project Library to it. Second I add a newly create class, named 'Class 2'.
iv) I set the inheritance of the Class 2 as a child of Class 1.
v) select new VI for Override
vi) get Error 1035
What am I doing wrong or how to solve this?
Solved!
Go to Solution.

The default setting for packing VIs into lvlibp's will remove the block diagram.
You must not remove the block diagram for dynamic dispatch VIs you are going to override.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Error When building ess/tra/tre and ess/tra/tre/trs DC's

I had customized the ess/tra/tre and ess/tra/tre/trs DC's and had them working, but I do not know what I did or what happened that am now getting the following errors when building, can anyone help tell what the problem could be?
Error
-     The project was not built since its classpath is incomplete. Cannot find the class file for com.sap.xss.tra.model.openccmodel.OVSOpenCostcenterModel. Fix the classpath then try rebuilding this project.
-     HDI_HNS15.02_Desstratresap.com
Error
-     This compilation unit indirectly references the missing type com.sap.xss.tra.model.openccmodel.OVSOpenCostcenterModel (typically some required class file is referencing a type outside the classpath)
-      InternalVcTreReview.java
-      HDI_HNS15.02_Desstratresap.com/gen_wdp/packages/com/sap/xss/tra/tre/vc/review/wdp
-     line 0

For anyone who might need to know, I managed to fix this by adding tra to the required projects on the build path. On the Navigator View, right click -> Properties -> Java Build Path -> Projects tab -> check dependant project.

Packed Project Library (lvlibp) slows LabVIEW Project

Hello,
My LabVIEW project (2010SP1) perfoms well except when I add a critical library provided by my customer in the form of a LabVIEW Packed Project Library. Activities like loading the project, opening VIs, running VIs, editing VIs respond VERY SLOW (about 20X). In contrast, if I open VIs in the LVLIBP without loading the project, everything responds at a normal rate.
Any suggestions?
Jorge

Hi Jorge,
May I know what does that Packed Library contain? I have read about a similar issue but in that case they were running some TestStand benchmarks that loaded a packed library.
Jorge
Applications Engineer
National Instruments
Certified LabVIEW Associate Developer (CLAD)

Packed Project Library Shared With OI?

I have an application which needs to share some resources/instruments with TestStand steps. The requirements require the application to communicate with these resources/instruments with or without the TestStand Engine running.
I understand that the suggested approach is to ONLY place instrumentation code in a test sequence. However, what is the best approach if the application requirements dictate the resource/instrument must be shared?
Can a packed project library be shared with the operator interface?
Is a source distribution the only option?
CLA, CTA
Solved!
Go to Solution.

> What Language are you using?
LabVIEW
> Is it possible to get a more detailed explanation of what you are trying to do?
Read and write from instruments in both my Code Modules and my Operator Interface
Implement Diagnostic Panels without requiring the TestStand Engine
When the TestStand engine is not running, I would like to read and write from the instruments in debug panels on the operator interface.
Implement Status Panels without requiring the TestStand Engine
During a TestStand Sequence, I only wish to read from the instruments in the operator interface (IO status panels).
Implement a few high-speed timed loop state machines within LabVIEW. These loops must start running as soon as the application is launched and for the lifetime of the application. I would like to share the state/data of these loops with TestStand and allow a command/response interface.
> It is possible in TestStand to run the test Sequence in a independent execution as long as it has the references to the source files.
What if I want to start a VI that talks with an instrument. Why can't I open a serial port in the OI and pass the session to the TestStand API?
Why is is "better" to call a Code Module VI in a new execution vs just calling the VI from the Operator Interface? For example, if I want to display the "status panel" of a digital input card...
> You mentioned that you need the program to sometimes run even if TestStand is not running, will these programs ever be running at the same time?
There will only be a single application that launches the TestStand Engine.
The idea is that the program utilizes the TestStand engine to run automated tests. I would like to allow the OI to read the current values (status panels) while TestStand both reads and writes.
Additional Questions
I would like to understand how TestStand executes LabVIEW VIs differently with the Development and Run-Time adapters.
If I run a TestStand sequence with the LabVIEW Development System Adapter, from my Operator Interface (OI) I can call code modules and vice versa. This will work for VIs within the context "Main Application Instance" (no project).
When I deploy this system using the LabVIEW Run-Time Engine with a built "Operator Interface" EXE, it seems they may run in different "Contexts".
Why is the separation between User/Operator Interface and Code Modules required?
The TestStand Reference Manual states "Do not use instrumentation code in user interfaces". Why?
If I change the Preferred Execution System in the LabVIEW VI (that is running in the OI) settings to "standard" is this ok?
I hope this detailed response explains my goals adequately. Thanks for your assistance.
CLA, CTA

"no ocijdbc11 in java.library.path" error when connecting a TNS database co

Hi
"no ocijdbc11 in java.library.path" error when connecting a TNS database connection
I have the same problem 'error code' when testing the connection to a database although I have an APEX db that connects without a problem.
I have re downloaded jre & SQL Developer just to ensure all files are where they should be with no luck.
I've also tried most of the suggestions in various threads.
Does anyone know what exactly causes this error?
eg; should I be looking for a file called 'ocijdbc11' & put it into the 'java.library.path' path?
Can anyone explain to a newbie at db connections what I should do?
I'm using the 'thin' client as the checkbox is clear & I don't know what path to enter into the correct file to make this work??
This is & needs to connect as a TNS connection & was working fine until recently, the only change I can think of is a move of files from the 'C' drive but I thought redownloading SQL Developer would slove this.
Thanks

When you reinstalled SQL Developer, did you install into a new directory (ie rename or delete the old directory first)?
I don't know if system setup contains directory references (which might be invalid after moving the location of SQL Developer). Does renaming your system2.1.1.64.45 directory (in C:\Documents and Settings\username\Application Data\SQL Developer) help? Note that your connections are in the connections.xml file in the o.jdeveloper.db.connection.11.1.1.2.36.55.30 subdirectory of system2.1.1.64.45 - you will either need to export connections before renaming and then import again after or copy this file to test if you can connect.
Finally, the TNS Names directory preference is just a way of telling SQL Developer where to look for the tnsnames.ora file, rather than just assuming it will pick the right one. If you go to create a new connection, do you get the right list of TNS aliases? If not, then set this preference to the directory where the right tnsnames.ora file lives.
theFurryOne

Icon path restricted error when building release version for ipad3

Hi,
i get the following error when building the release build ipa file for ipad 3: "The path icon.png is restricted. If you were trying to package Icon.png you should correct the case." In debug mode everything works. My icon is under assets folder and added in the app-xml with:
<icon>
<image72x72>assets/icon_72.png</image72x72>
</icon>
Did I missed something in configuration? Seems to be that the problem is known but cant find a solution for it. If i try to packegae per command line despite the fact building works I could not install the app. When I change the icon tag to use no icon everything works fine. Any ideas?
Greetz and thanks in advance!

I solved it. When you export the release build you can choose package contents to be compiled in the ipa. When I tried to add an icon at first I named it icon.png, which seems to be a reserved name. The configuration to include this icon.png was still saved though i deleted it. Wired... After unchecking the ceckbox for icon.png not to be compiled in the ipa, the release build was build.

Error when building Azure project

A few days ago I started to see an error when compiling my Azure Project (cloud service with web and worker roles). I've been working with this Azure project for almost 3 years without seeing this before. When I attempt to build my Azure Project, 9 times
out of 10 it fails with this error:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Windows Azure Tools\2.2\Microsoft.WindowsAzure.targets(1371,5): error : Could not find file '<SourceCode>\SomeProject\bin\Debug\ServiceDefinition.csdef'.
Here's another when I attempt to build again:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Windows Azure Tools\2.2\Microsoft.WindowsAzure.targets(985,5): error : Could not find a part of the path 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\csx\Debug\ServiceDefinition.csdef'.
Sometimes the error refers to ServiceDefinition, sometimes to ServiceConfiguration. The problem is that it is looking for the two files in places where it's not supposed to be. I have a single Azure Project in my solution, and a single service definition
in my solution, but when building the error message says it can't find the service definition/config in some other Project in the solution. For example, it may try to find the service definition in some unit testing C# Project instead of in the Azure Project.
Some isolation:
Building same source code works fine for my colleauges.
I've set up a new computer with Windows 8, VS2013, VS2013 Update 1, Azure SDK 2.2. Still same error.
I've turned off multi-core builds. Still same error.
I've seen another post on SO with a similar issue, but then it was related to publish settings files in his solution which were missing.

Hi,
Did your colleague build the same solution or create a new solution with the existing code? If they have exactly the same solution as you have, then please check if the environment of your machine (both old and new) is different from theirs. For instance,
please check Azure version, VS extension, etc. If they created a new solution with the existing code, you can try to do that yourself to see whether it works.
Best Regards,
Ming Xu
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error when building a MP in VS 2013

Hi Guys,
I'm starting to learn how to create custom management packs with Visual Studio 2013 and the Authoring extensions. I'm trying to build my first solution, which contains 2 management packs. both of these packs just have a fragment called project in them. When
I hit build, it ends with the error
"Error 1 Element Info with Identity DisplayString,ElementReference=9d30fa12-ed40-aff7-c609-5a07d0030d02,LanguageID=ENU refers to an invalid element MPAuthors.Stores.Dashboards.   (Path = DisplayString,ElementReference=9d30fa12-ed40-aff7-c609-5a07d0030d02,LanguageID=ENU) C:\Program
Files (x86)\MSBuild\Microsoft\VSAC\Microsoft.SystemCenter.OperationsManager.targets 255 6 MPAuthor.Stores.Dashboards"
My project fragment has the XML below
<
ManagementPackFragmentSchemaVersion="2.0"xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <
LanguagePacks>
    <
LanguagePackID="ENU"IsDefault="true">
      <
DisplayStrings>
        <
DisplayStringElementID="MPAuthors.Stores.Dashboards">
          <
Name>MPAuthor
Stores Dashboards</Name>
        </
DisplayString>
      </
DisplayStrings>
    </
LanguagePack>
</
LanguagePacks>
</
ManagementPackFragment>
Have I missed something obvious?
Chris
Chris Gibson

Hi Chris,
it's impossible to say seeing only the fragment above. In general, the error says "I can't find the element (class, workflow, module type etc) with ID = MPAuthors.Stores.Dashboards". Can you check your MP and find this ID? Maybe it's just a typo
somewhere...
http://OpsMgr.ru/

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

Why do I get 'ResolveManifestFiles task failed' error when building a WPF app that references WinRT API?

0
down vote
favorite
I am working on a WPF app that I want to create for Windows 8. I followed steps mentioned in
Hansleman's blog to make some manual modifications using WinRT functions in a WPF app. Everything worked well, until I tried to publish the app. When I clicked on publishing the app I got error "The 'ResolveManifestFiles' task failed unexpectedly.
System.ArgumentException: Value does not fall within the expected range."
Afterwards, it will produce the same error when attempting a simple solution build.
Even if you create a simple WPF project and add the references mentioned in blog to access WinRT functions and publish, this issue can be reproduced.
I think it would be common scenario to call WinRT functions from WPF and someone should have done it. Is anyone aware what should be done to fix this issue?

I am having the same problems and came across this article while researching a workaround.
It is surprising more people aren’t talking about this.
Here are the steps to reproduce the problem; Using Visual Studio Express 2012 (x64) create a new VB Windows Forms Application.
Unload the project and edit the [ProjName].vbproj in the solution explorer.
Add <TargetPlatformVersion>8.0</TargetPlatformVersion> to the <PropertyGroup>.
Save and reload the project. In Add Resource/Reference Manager add the Windows.minmd found under Windows/Core.
This WinRT/Desktop solution will run as expected. Now try to Publish this solution.
It will FAIL with the following ERROR; “The ResolveManifestFiles task failed unexpectedly, Value does not fall within the expected range.”
Attempting to build or run the solution again now will fail with the same Error.
The only way to build the project now is to remove the “Enable ClickOnce security settings” option under the project properties Security settings.
Occasionally using this trick, the solution will build but not run.
When that happens jiggle around with Debug/Release Solution Configurations and the Any CPU/x64 Solution Platforms then rebuild and try the run again.
This fussing around will get you through development however any attempt to publish with restore the ClickOnce security setting and create the previous Error.
The first question here is how do you publish a WinRT app for the desktop with VS2012 Express.
Then secondly, if that is not possible can we publish this Express solution with a 3rd party deployment tool like InstallShield Limited Edition or the WIX Toolset.
Neither however seems functional in a VS Express environment.
Then thirdly, are there ways to access hardware sensor devices from a desktop solution without resorting to the WinRT API.
Any ideas or new research directions would be greatly appreciated.

Geting error when build installer

I'm getting Error 33 and dotnet x86 ni language pack error and build stops
how can I solve this issue?
Building executable is fine, but the problem occurs during building installer.
Please advice
regards
Pierre Tannoury
Pevatech International S.A.R.L

thanks for helping,
i still receive another messages but the dotnet error message is gone
please see below the building status and what's errors remaining
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
Copying files...
Updating files...
*** Error: Fatal runtime error. (Error code -10)
*** Error Details:
Access violation! Structured exception code 3221225477
*** End Error Report
*** Error: An internal tool or library returned an error. (Error code -21)
Error Messages
*** Error Details:
Error in MDF API function: _MDFBuildDist_Build
Error List
.\InputParser.cpp(819): IInstallerError 108
Problem with updating Part DataSocket64.msi.
*** End Error Report
Done building deployment

Packed project Library Labview Class Issues

I packed my whole Labview project as a packed proj library during teststand Deployment
I am using classes in my labview project
unfortunalely by one of sub seq calls got the following error !
"Type mismatch. The LabVIEW Class does not match the class expected by the VI.
Cannot pass a base LabVIEW Class to call a method initially defined in a derived LabVIEW Class."

The error message is quite clear:
You are using inheritance where you do have methods which are not part of the parent class (as dynamic dispatch).
During the call, you pass an object of the parent class and try to call the (unknown) method of the child.
Why this is happening can only explain your code....
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Error when building application with Excel included

Hi All !
I've read several post on problems with Report Generation Toolkit when building applications that uses Excel or Word interactivity.
I've included both _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi in my project and added them to the dynamic vis and support files.
When building I get the error :
The VI is broken. Open the VI in LabVIEW and fix the errors.
C:\Programmer\National Instruments\LabVIEW 8.2\vi.lib\addons\_office\_exclsub.llb\_Excel Dynamic VIs.vi
When opening that VI there is no broken arrow and all the vi's included in this is not broken either.
I've tried mass compiling and so on but so far luck.
Regards Morten Kahr
Regards Kahr
Certified LabVIEW Architect
CIM A/S

If you do a search on this forum you will find this to be a common and vexing problem. I myself had this same exact problem about a year ago, and it took me the better part of a day to track it down. As you will find by reading the various threads on this problem, there seems to be no specific cause for this, and it remains a mystery, and the solutions are no better than chanting voodoo, and probably just as effective.
One thing you can try is to force a recompile of your VI hierarchy. Open you top-level VI. If it's set up to run when opened, stop it. Hold down the Control key and click the run button. This will force a recompile of the application. Sometimes this works, sometimes it doesn't. Like I said, voodoo.
Another thing to look for is to check if you are using any diagram disable structures or case structures with a constant wired, as in trying to use the case structure to comment out code.
Are you using classes and passing by reference? There was a mention of this here.

Error when building the Java pricing userexit manual code

I went throught the manual for the pricing userexit manual... it tells you to ignore the errors when you do an ant build but I want to remove all the errors since they dont let the rest the code compile.... where are the jars for these errors:
[javadoc] C:\DEV\PRC_UE_CUSTOMER\lib_src\src\com\sap\spc\document\DocumentConstants.java:16: package com.sap.vmc.logging does not exist
     [javadoc] import com.sap.vmc.logging.Category;
     [javadoc]                            ^
     [javadoc] C:\DEV\PRC_UE_CUSTOMER\lib_src\src\com\sap\spc\document\DocumentConstants.java:26: cannot resolve symbol
     [javadoc] symbol : class Category
     [javadoc] location: class com.sap.spc.document.DocumentConstants
     [javadoc]     public static final Category CATEGORY = Category.getCategory(Category.APPLICATIONS, "/AP/SPC/Document");
     [javadoc]                         ^

See the [SAP note 809820 - Userexit concept for pricing|https://service.sap.com/sap/support/notes/809820]
Use ZIP file the attached to the above note - PRC_UE_CUSTOMER_V105.zip
ZIP file contains an Eclipse .project file that has the required build path. If you read the documents carefully, it does refer this project file.
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
     <classpathentry kind="src" path="src"/>
     <classpathentry sourcepath="lib_src/src" kind="lib" path="lib_api"/>
     <classpathentry kind="lib" path="lib_vmc_api/base_services_stripped_api.jar"/>
     <classpathentry kind="output" path="bin"/>
</classpath>
Again read the documents thoroughly. They are neither fictions nor non-fictions, but technical documents written with care. So, we must also read them with care. If we don't follow them, then it is time to engage someone who does. )
BTW, coming back to the Java basics - One must have a class and source files to debug. You won't get a class file unless it is compiled. The Java file won't compile correctly if it has syntax / reference errors. Unfortunately or fortunately, all these apply to the IPC java userexit development as well.
Easwar Ram

Packed project library 1003 error when building it

Similar Messages

Maybe you are looking for