Error 1073 when building LabVIEW app which calls LabVIEW dll

I am trying to use application builder to build an application that calls a dll created in LabVIEW. I get an error referencing a vi within the dll (Parse Stored String(multibyte).vi) saying that "This property is writable or this method is available only when the VI is in edit mode." The only option is to Continue which cancels the build. I had sucessfully built this application prior to including vis that call the dll and the program runs fine in the development environment.
Do you have any idea what is causing this and what I cam do about it?

I have found a temporary workaround in which I created a dummy dll that removed all functionality from exported vis but had the same name and function signatures. I then built the application using this dummy dll. Once complete, I replaced the dummy dll with the real dll.
This is not a satisfactory work around because we have to build and maintain two dlls. Also, I'm not sure we can do the same trick when creating the installer with application builder. So, I'd still appreciate any help you can give.

Similar Messages

Error 1305 when installing LabVIEW 7.1 app built with app builder

I have built an executable with installer from LabVIEW 7.1 app builder. The app installs/works fine, however 1 user reported 'Error 1305' when installing the app from a DOS subset on a WinXP machine. For example, a virtual drive is created using the DOS 'subst' command (see http://www.easydos.com/subst.html for more info), e.g. 'subst z: c:\temp'. Now when running z:\setup.exe, the error 1305 is encountered. If the same app is run from c:, e.g. 'c:\temp\setup.exe', it works fine. Is this a bug in the installer, or in the OS...?

Greetings,
This is an architectural issue with the Microsoft Windows Installer and Windows, and will occur with any MSI (not just those from the app builder). Under XP, a MSI cannot install from OR install to a location created by the "subst" command. My understanding of why is that installSequence runs in the context of the MSI engine, which is running as "system" user. But the subst command is a per-user setting (local to your account) so the MSI engine doesn't see it.
The only workaround is to run the MSI from a non-subst drive, or instead use network file shares (you can simulate what "subst" does by mounting an exported file share from the same machine).
Regards,
- WesW / NI

App-v 5.0 SP2 hotfix 5, an error occurred when querying the App-V WMI provider

Hi,
We have installed App-v 5.0 SP2 + hotfix 5 (via SCCM 2012 R2 CU1) on some Windows 7 clients. That worked fine but no app-v applications go through.
Error:
AppVPackageQueryClient5X::GetPackageDataByPackageGUID() failed for virtual application [a835fa1-f82a-4efe-957a-8c6678d4a431]. (0x87d01290)   AppVHandler   5/08/2014 10:23:56   3440 (0x0D70)
CAppV5XHandler::DiscoverIndividuleApp() failed. (0x87d01290)   AppVHandler   5/08/2014 10:23:56   3440 (0x0D70)
+++ Discovery of application [AppDT Id: ScopeId_8B8D93AF-5181-48FE-9202-2CFE5FC93EE2/DeploymentType_50eba242-3688-4b4f-9b61-84f0123f667d, Revision: 7] returned an error (0x87d01290).   AppVHandler   5/08/2014 10:23:56
3440 (0x0D70)
CAppV5XHandler::DiscoverApp() failed. (0x87d01290)   AppVHandler   5/08/2014 10:23:56   3440 (0x0D70)
Deployment type detection failed with error 0x87d01290.   AppDiscovery   5/08/2014 10:23:56   3440 (0x0D70)
Failed to perform detection of app deployment type Microsoft - Console, revision 6) for user. Error 0x87d01290   AppDiscovery   5/08/2014 10:23:56   3440 (0x0D70)
Error = 0x87d01290 = An error occurred when querying the App-V WMI provider.
Please advise on this specific error. Should we look for corruption in app-v client, problem in sccm client ...?
J.
Jan Hoedt
Update: clients which don't have problems are client which had hotfix 4 THEN hotfix 5 installed. Should we install it that order? Client WITH problems have App-v 5.0 SP2 then hotfix 5 directly.
Update2: I installed the app-v client via setup.exe, the hotfix 4 also via setup.exe but since it installed all language packs, I decided to extract hotfix 5 and use the msp.
Could that be cause of the issue? I could use the exe of hotfix 5 but then I need to be sure how NOT to install all the language packs.

I think we found a solution ourselves.
My update2 (question) explains it:
Update2: I installed the app-v client via setup.exe, the hotfix 4 also via setup.exe but since it installed all language packs, I decided to extract hotfix 5 and use the msp.
Could that be cause of the issue? I could use the exe of hotfix 5 but then I need to be sure how NOT to install all the language packs.
We installed App-v 5.0 SP2 via exe then installed hotfix via msp (extracted msp), this doesn't seem to work (though installation was succesfull). When we deploy the hotfix via the exe it works correctly.
Not sure why though.
Jan Hoedt

An error occurred when executing a REMOTE FUNCTION CALL.

Dear all,
We have two syetms called DXD and GRD , we have a remote enabled function module in the DXD system , when i am trying to call this Function module from
GRD system it is going for the short dump, and giving the follwing error,
<b>Error analysis
    An error occurred when executing a REMOTE FUNCTION CALL.
    It was logged under the name "RFC_NO_AUTHORITY"
    on the called page.</b>
But i do have the access for the DXD system also, i am really struggling to solve this problem, if any lights are there to help me , i will be thank full for then,
some body suggested for me that we need to maintain the Trusted system tables in the target system.
Thanks & regards
Satya.

first u( user id ) have to get the Authorizations to use RFC ?
object will be like S_RFC or some thing like this.
when u get this kind of error just call /NSU53 then u will come to know which Authorization Object is missing from ur User Profile.
Regards
Prabhu

I always got error message when opening BlackBerry App World using 3g

Hi there, I always got error message when opening BlackBerry App World using 3g network, but it's fine if I open it through wifi network. Does anyone ever had the same problem and how to fix it? Thanks.

You need the latest version of BlackBerry World installed on your smartp

Calling primary dll which calls secondary dll

Hi all
I have a visual C++ file which calls a dll named mpusbapi.dll . The visual C++ file has some additional
functions also. I want to make this visual C++ file itself a dll and then call this dll from call library function
in labview. Please guide me in making this visual C++ file dll.
To make functions visible in call library function what do i use.
_declspec (dllexport) or Extern C
I have also read the tutorial of making Writing a DLL with Microsoft Visual C++
Are there any steps required in doing this? Please tell
Regards

I want to add one more thing that in the tutorial of Writing Win32 Dynamic Link Libraries (DLLs) and Calling Them from LabVIEW
What is this for
BOOL WINAPI DllMain (
            HANDLE    hModule,
            DWORD     dwFunction,
         LPVOID    lpNot)
    return TRUE;
Is it necessary to write this in order to create our own dll?

Error 1073 When trying to build app.

"Error 1073 occurred at... Possible reasons: This property is writable only when the VI is in the edit mode.
Application builder: The source VI must have its diagram in order to be included in an application."
When I save my vi as an app. distrib. without diagram I get this message when I try to build app. No problem if the diagram is included. Didn't have this problem in 6.1... any suggestions? Would like to build without diagrams.
Attachments:
open_dialog.vi ‏33 KB

That's exactly the same problem I am having. I have purchased some third party VIs that do not have diagrams. Previously in LV6.1, I could build them into an executable, but now with LV7.0 I can't (even though I now have the LV7.0 versions of these VIs). It seems that NI have changed the rules without telling anyone.
A work-around that I have tried successfully is to get DLL versions of the VIs.

Error 1073 (on Clear Errors.vi) When Building Application in LV 8.2

I have seen numerous posts about this problem when building an application without a block diagram in LV 7.x, however, I am recieving this error on LV 8.2. Whats most disturbing about it, is that it always hangs when processing Clear Errors.vi. I have tried my source on two different machines, to no avail. Also I tried to do a mass recompile of the entire vi.lib again no help. It is very important that this program compiles, however I cannot get past this error. Any suggestions?
My specific error message is here:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1073 occurred at ABAPI Dist disconnect td-poly.vi -> ABAPI Dist Chg and Save VIs.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: This property is writable only when the VI is in edit mode, or this method is available only when the VI is in edit mode.
-Paul

Hello Paul,
I am sorry for not elaborating previously. This issue has been documented previously for further investigation to our R&D group (# 3ZK9LGP2). In the report I found that this error, though vague in the description, is fixed by enabling MathScript Support.
To enable MathScript support, check the checkbox in the application properties for the 'Enable MathScript support' option.
-Bob
-Bob

Error 1 when building my application in Labview 2010 Version 10.0f2

I am getting the following error trying to build my application in Labview 2010 Version 10.0f2 and I get the following error:
Error 1 occurred at Invoke Node in AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
Method Name: Linker:Write Info To File
I have searched and can find no real sollutions to this problem. I did the updates and still nothing. Now I can't even build an app with Laview 8.6. I reference several .NET items and refuse to rebuild each and every one of them. My only option at this point is to uninstall all Labview and then reinstall 8.6 so I can do something.
Help if you can.

Hello RBrown
I am really sorry for this inconvenience! This is a known issue.
Can you please attempt the following for me:
When you are building an application, under Advanced please check the last box "Use LabVIEW 8.x file layout"
If that doesn't work, you may need to rebuild the LLB in a separate directory with new names, and use it as the build inclusion.
Here are some forum posts strictly for your information:
I have found users that have had similar issues. I am trying to make this workaround work for you.
http://forums.ni.com/t5/LabVIEW/error-1052/m-p/912192
This is a known issue that some customers have already commented on:
http://forums.ni.com/t5/LabVIEW/NI-Please-don-t-put-illegal-vi-names-in-your-toolkits-thanks/m-p/745...
I have filed a corrective action for this issue and I will add you to the list of individuals who need this issue resolved.
Sincerely,
Greg S.

Error message when building an application for Labview PDA

When using LabView PDA module to build an application for a PDA target, I receive the following message: "Error building executable. Unable to create file". Why is this happening?
When looking at the error log, it reads "The system cannot find the file specified."
This happens even when looking at one of the Labview PDA example VI's, so it is not a result of the VI containing functions of features not supported by Labview PDA.
When installing Labview PDA, I installed files as follows, and in this order:
(i) Labview 7.1 (installed previously)
(ii) Microsoft eMbedded Visual C++ 4.0
(iii) Microsoft eMbedded Visual C++ 4.0 SP 3.0
(iv) Microsoft SDK for Windows Mobile 2003-based Pocket PCs
(v) Microsoft ActiveSync 3.8
(vi) NI Labview 7.1 PDA module for PocketPC
(vii) DAQmx Base 1.0 for PDA or later
Any ideas?

Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Error -30, when building new installer

LabVIEW 2010 sp1, just upgraded and lost the ability to build installer. Error dialog:
LabVIEW 2010 sp1
Win 7 64bit
Thanks in advance.

For example, which version of LabVIEW did you upgrade from? Did you modify any of your code? Are you having problems building ANY installers or just a single application?
Original installed version: NI Developer Suite 2010 DS2
Code is unmodified
Application Builder Error occurs from any project.
Currently configured installers cannot be built either. When build configuration is viewed the additional installers section is empty.
I am currently working with an NI Applications Engineer to resolve the issue.
So far, article:
http://digital.ni.com/public.nsf/allkb/1B53A6FDFC20B8058625752400687F42?OpenDocument
has been suggested.
From my team of 6 the 3 that have upgraded have the same issue.
I will update the status once I try this fix.

Error 1003 when building executable

Hi, I'm using Labview 2010 on Windows 7 and I'm getting an error when I try to build an executable:
Error 1003 occurred at Open VI Reference in AB_Engine_EXE_Call_Write_Icons.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Create_Build_Application.vi->EBUIP_Global_OnCommand.vi->EBUIP_Global_OnCommand.vi.ProxyCaller
Possible reason(s):
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.
VI Path: C:\Program Files\National Instruments\LabVIEW 2010\vi.lib\Platform\icon.llb\Read Icons from ICO File.vi
This happens even when I try to build a simple vi, like a random number generator.

Same problem here. Error 1003 and error 8 I encoutered often.
For error 8 during build process, I needed to save the executable on a higher level in the file hierarchy.
For error 1003, I did not find a solution. Restarting LabView does not help. Sometimes (but not always) restarting the computer helps. Sometimes I need to reinstall the labview system.
More details: I have a first vi, starting the actual vi with a hidden front panel (second vi). This vi can also be started directly. Sometimes, the build process runs smoothly then when I include the second vi as main vi to start the program.
The program runs fine when the build process succeeds, and it runs fine in LabView.

Error -12 when building installer

OS: Win7
LabVIEW: 2012 SP1
I am having issues with the application builder while trying to build an installer.
The installler has the following "Aditional Installers" selected:
LabVIEW Runtime Engine
NU USI 2.0.1
NI DAQmx Core Runtime 9.8
NI DAQmx MAX Configuration 9.8
NI VISA Runtime
If I remove the "NI DAQmx Core Runtime 9.8" & "NI DAQmx MAX Configuration 9.8" then the installer builds without error. How can I get it to succesfully build with these selected?
I have upgrated the DAQmx from 9.5.5 to 9.8 and performed a mass compile but no luck.
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment information
Adding files to installer
Validating...
Copying files...
Scanning files...
Updating files...
Build complete successfully.
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'SiriusXM Mad Max' from: C:\Users\bbanacki\AppData\Local\Temp\7ZipSfx.000\Mad Max Installer\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem
Windows function FindFirstFile returned an error. Error code: 3
*** End Error Report
Done building deployment
Solved!
Go to Solution.

Siriusly wrote:
Copying distribution 'SiriusXM Mad Max' from: C:\Users\bbanacki\AppData\Local\Temp\7ZipSfx.000\Mad Max Installer\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem
Windows function FindFirstFile returned an error. Error code: 3
*** End Error Report
Done building deployment
It looks like your installer build is trying to pull the "SiriusXM Mad Max" distribution from an unusual temp location. If this distribution was hiding inside a 7zip file and has since been altered or deleted, that we certainly confuse the installer builder. Do you know if this distribution contained the DAQmx installers you are trying to build with?
Here are a few things you could try if this is the case.
1. If an installer build ever suceeded while pulling source from this temp location, the location may have been saved as known good source. To undo this saved information, you can delete the file at C:\ProgramData\National Instruments\MDF\Bin\MDFInfo.xml
2. If C:\Users\bbanacki\AppData\Local\Temp\7ZipSfx.000\Mad Max Installer\ is a valid path on your machine, try moving or renaming this folder. This should cause the installer builder to prompt you for source media. This prompt window will allow you to configure which distributions you provide as source for the build (depending on the version of the installer builder tool installed, you may have to click "No" to the question "Do you have all of these installers?" to get to the configuration page).
3. Install the latest version of the installer build tool. A new one released with LV 2013, and it should be available to download either through NI Update Service or on the web somewhere
4. All else fails... post your full installer build log! LabVIEW generates this for us at %temp%\LVProjectName_InstallerName_build.log

Unexpected error (0xE8000001) when building in xcode

help, does anyone get this error message when they build in xcode, [device] and [debug]?

Nope, you're the only one:
http://www.google.com/search?client=safari&rls=en-us&q=%220xE8000001%22&ie=UTF-8 &oe=UTF-8

Error 1706 when installing LabVIEW 7.1

Hi,
When installing the device drivers that come with LabVIEW 7.1, near the end of the installation I get the following error message:
Error 1706: No valid source could be found for product LabVIEW 6.0.2. The Windows installer cannot continue. Continue?
The installer completes after this but says that the installation has failed. Any suggestions? Thanks.
Bob

Robert_Deschambault wrote:
Hi,
When installing the device drivers that come with LabVIEW 7.1, near the end of the installation I get the following error message:
Error 1706: No valid source could be found for product LabVIEW 6.0.2. The Windows installer cannot continue. Continue?
The installer completes after this but says that the installation has failed. Any suggestions? Thanks.
Bob
Hello Robert,
You can find out more information about this error at the following post.
what does Error 1706 mean during LabView 6.1 installation
This error is not specific to the install of LabVIEW but with the upgrade of the IMAQ device driver.
Please let me know if you have any other questions
Regards,
Matt F
Keep up to date on the latest PXI news at twitter.com/pxi

Error 1073 when building LabVIEW app which calls LabVIEW dll

Similar Messages

Maybe you are looking for