Application Builder: error in building DLL from a VI

I have a VI which I have been compiling into a DLL for use with Labwindows. Suddenly yesterday the build would no longer compile. Instead the error message (see attached picture) persisted all day no matter what I changed in the VI. Before the error message appeared, the Labview project window went blank for a moment, then showed some "C" code from somewhere, and then back to the project window. It's almost like something blew up in the compile process.
I've tried all suggestions in the error message. Checked data types and names. I believed the VI is wired back to where it was. There is not much to the VI but it does reference some .NET assemblies.
Thanks for any comment or help,
Doug Wendelboe
Attachments:
VI-DLL-Pictures.zip ‏21 KB

Hi Eriquito:
Thanks for your response. I've included some snapshots of appropriate Ap Builder setup pages. My DLL is named "CVIMESQueryTray.dll". I had this compiling quite well up until a few days ago, so Ap Bldr didn't object then.
See if you can spot something in my ApBuilder setup that I might be doing wrong.
Thanks for your help.
Doug Wendelboe
(Hmmm.. I guess I can't attach more than three items, so I ZIPped them into one file).
Attachments:
ApBuilderPics.zip ‏154 KB
ProjectFile.JPG ‏60 KB
ApBuilderPage1.JPG ‏31 KB

Similar Messages

Error: -112 extracting dll from cab

Hi
i got this error -112(extracting dll from cab) while connecting AddOns to SBO.
<b>could it be a problem of patch upgradation</b> ???
Thx

Check that the DI API version installed matches the B1 version installed.
Also try deleting the folder SM_OBS_DLL from %TEMP% if it exists. Upgrades often leave old file versions in here that can cause various issues.
John.

C++ build error with LabVIEW DLL

Hi, I'm a student at UC Irvine learning to use LabVIEW. I am working on a practice project for which I have to use a PID system to control the temperature of an object. Things are starting to get a little messy with nested control statements, loops, etc., so I figured I'd export a LabVIEW DLL with all the hard to code stuff, such as interfacing with my instruments, and plotting data or whatever, and do the number crunching and keeping track of stuff in C++.
The DLL file I made in LabVIEW went off without a hitch as far as I can tell, but when linking it to my C++ test program (which at this point is just including the LabVIEW's .h file for the DLL and an empty main() function), I get a lot of build errors. I am using Dev-C++ which uses g++ to compile the code.
Here is a pic of my build errors:
Solved!
Go to Solution.
Attachments:
LabVIEW_compile_error.JPG ‏184 KB

Normal windows apps are not as forgiving about where you can put your DLL as LabVIEW. You have to have a DLL either in the direcotry where the executable file itself resides (that would be your build directory, not the source directory), the windows or system directory, or any directory that is set in the PATH environment variable. Anythin else will most likely not work, or at least not reliably.
No need to add the cintools directory into your include file paths nor the library file paths. you would only need that if you decided to let the DLL export native LabVIEW data types in which case you would need the LabVIEW manager functions to prepare the correct data buffers.
Rolf Kalbermatter
Message Edited by rolfk on 07-30-2009 07:49 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Getting build error when building HelloService

I have installed the Sun application server (at D:\Sun\Appserver) and the J2EE tutorial (at C:\j2eetutorial14).
1. Checked on the PATH variable and D:\Sun\AppServer\bin was automatically added during app server install.
2. asadmin help at the command prompt shows the asadmin help topics just fine which tells me that the path is fine.
3. Started the sun app server and it started fine
4. Modified the C:\j2eetutorial14\examples\common\build.properties file to reflect the correct j2ee.home and j2ee.tutorial.home as follows:
j2ee.home=D:\\Sun\\AppServer
j2ee.tutorial.home=C:\\j2eetutorial14
5. asant listprops shows the right values for the above two properties
C:\j2eetutorial14\examples\jaxrpc\helloservice>asant listprops
Buildfile: build.xml
listprops:
[echo] Path information
[echo] j2ee.home = D:\Sun\AppServer
[echo] j2ee.tutorial.home = C:\j2eetutorial14
[echo] env.Path = C:\Program Files\Java\jdk1.5.0_02\bin;D:\Sun\AppServer\bin;d:\oracle\ora9i\bin;C:\Program Files\Documentum\DFCRE41\bin;C:\WINNT\system
2;C:\WINNT;C:\WINNT\System32\Wbem;C:\ant\bin;D:\Sun\AppServer\bin;
[echo] env.PATH = ${env.PATH}
[echo] Classpath information
[echo] classpath = ${env.CLASSPATH}
[echo] Admin information
[echo] admin.password = sunshine
[echo] admin.password.file = C:\j2eetutorial14 /examples/common/admin-pass
ord.txt
[echo] admin.host = localhost
[echo] admin.user = admin
[echo] admin.port = 4848
[echo] https.port = 8181
[echo] Domain information
[echo] domain.resources = "domain.resources"
[echo] domain.resources.port = 8080
[echo] Database information
[echo] db.root = D:\Sun\AppServer /pointbase
[echo] db.driver = com.pointbase.jdbc.jdbcUniversalDriver
[echo] db.host = localhost
[echo] db.port = 9092
[echo] db.sid = sun-appserv-samples
[echo] db.url = jdbc:pointbase:server://localhost:9092/sun-appserv-samples
[echo] db.user = pbpublic
[echo] db.pwd = pbpublic
6. And yet when I do a asant build I get a build error pointing to j2ee.home in the build.properties file
C:\j2eetutorial14\examples\jaxrpc\helloservice>asant build
Buildfile: build.xml
j2ee-home-test:
BUILD FAILED
C:\j2eetutorial14\examples\common\targets.xml:10: The j2ee.home property is not
properly set in <INSTALL>/j2eetutorial14/examples/common/build.properties.
Set the j2ee.home property to the location of your Application Server installati
on.
On Windows, you must escape any backslashes in the j2ee.home property with anoth
er backslash or use forward slashes as a path separator. So, if your Application
Server installation is C:\Sun\AppServer, you must set j2ee.home as follows:
j2ee.home = C:\\Sun\\AppServer
or
j2ee.home=C:/Sun/AppServer
j2ee.home is currently set to: D:\Sun\AppServer
Seems like everything is set to what it needs to be set. But the build still fails.
What could I be doing wrong? Could anyone shed some light on this please?

David,
I can’t say for certain what’s going on here but I do have a few suggestions before you “recreate the installer for legacy code reasons.” First, I would delete everything from the Build Directory. This may be where the recursive issues are coming from. Lastly, in the My Installer Properties window, I would look at the Source Files and make sure everything is there and check for any broke links.
Charlie M. CLD

How to get last Build date of a dll in the real time target

Info On My Project
I am working on LabWindows CVI 12.0 for development . This project is a real time application for hardware, which is having Phar Lap ETS as RTOS...
I am facing some problems while checking Build date of my Application file( .dll)
I have tried to use GetFileDate API. But it is not supporting for realtime Target..
So i have tried __DATE__ macro.. That also having some problems..
How to get last Build date of a dll from the real time target ??
Please Help to solve this....
Thanks
Vaishakh A K

Please reply if any one have suggestion...

Xcode build error

Hey, i get this error on build:
error: PCH file built from a different branch ((clang-425.0.24)) than the compiler ((clang-425.0.27))
Any ideas on how to fix?
- Thanks, Kez.

I had the exact same problem, but only with command line builds (xcodebuild).
So after doing some cleanups (and even Clean Build Folder (Alt key on Menu: "Product" > "Clean Build Folder...") the only thing that worked for me was:
http://stackoverflow.com/questions/7071523/xcode-4-1-fatal-error-stdlib-modified -since-the-precompiled-header-was-built#comment18214650_7072227
So, "touch" you PCH file first and retry.
Cheers,
Carlos

Build error after upgrading from 8.2.1 to 8.5 "Error 1055 occurred at Invoke Node..."

After upgrading to 8.5, I'm getting the following error when trying to build an EXE:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1055 occurred at Invoke Node in AB_Source_Library.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.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: Object reference is invalid.
I have been building this application for both Windows and Mac OS, and I even get the same error when building the .app on an Intel Mac.
Things that I've already tried:
* Mass-compiling all my code
* Created the project from scratch
* Enabled each panel of the "diagram disable structure" one at a time and compiled again
Any ideas?

Hi Travis,
Ben’s advice if definitely the best place to start. Error 1055 is a very general LabVIEW error for “Object reference is invalid.” The cause is usually a bad install where important LabVIEW function aren’t placed in the right directory or aren’t installed at all.
Charlie M. CLD

Build Error while trying to import a dc from the track.

Hi All,
I imported a Java perspective Dc from a track to local developement,
When i tried to build locally developed dc, but i was getting a build error as
"error reading C:\Documents and Settings
.dtc\0\DCs\dc_ext_lib\_comp\gen\default\public\Excel_API\lib\java\Jexcel-install.jar; error in opening zip file"
There was a error in opening the JExcel file.
Any Ideas?
Thanks,
Anil

Hi Anil,
I think the jar file(Jexcel-install.jar) is zipped.Unzip the zar file from the folder......lib/java.
Or else remove the jar file and import the application into NWDS,then add the jar externally from the NWDS.
Make sure that the dc does not have any files.
Once you import the dc rightclick on the prj-.properties-.add the external jar file or directly place the jar file in java folder.
Regards,
Lavanya.G

Error during Custom Build - error PRJ0019: A tool returned an error code from "Performing Custom Build Step"

Hi All,
I was trying to develop C++ web service using GShop with Visual Studio 2005.I refered a tutorial :-
http://guruce.com/blogpost/hosting-webservices-on-windows-embedded-compact-windows-ce-using-gsoap .
AS per the tutorial i proceeded. But, i stuck-up when making a custom build with Helloworld.wsdl.Here is the output :
1>------ Rebuild All started: Project: HelloWorldWebService, Configuration: Debug Pocket PC 2003 (ARMV4) ------
1>Deleting intermediate and output files for project 'HelloWorldWebService', configuration 'Debug|Pocket PC 2003 (ARMV4)'
1>Performing Custom Build Step
1>'D:\Test' is not recognized as an internal or external command,
1>operable program or batch file.
1>Project : error PRJ0019: A tool returned an error code from "Performing Custom Build Step"
1>Build log was saved at "file://d:\Test Code\HelloWorldWebService\HelloWorldWebService\Pocket PC 2003 (ARMV4)\Debug\BuildLog.htm"
1>HelloWorldWebService - 1 error(s), 0 warning(s)
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========
As given in the tutorial i kept my custom build command line as : -
$(SolutionDir)\gsoap-2.8\gsoap\bin\win32\wsdl2h.exe -s $(InputPath) -o $(ProjectDir)$(InputName).h
and outpouts : $(InputName).h
I kept GSHOP in the project filder :- D:\Test Code\HelloWorldWebService
Kindly help.
Jyotiranjan

Hi Jyotiranjan,
I’m glad to hear that you got it working.
Thank you for sharing your solutions
experience here. It will be very beneficial for other community members who
have similar questions.
Best regards,
Lucy
Lucy Liu [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Application builder error 1041

Dear All,
I have a problem to build a application in Labview 8.5.
It's the first time that I try to build this application in fact it's the first application every I try to build.
I found the following problem.
Authentication: "Error Code Database.vi is password-protected. Enter the password to acces the block diagram."
I do not know the password for this file.
The building errors details I get are:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1041 occurred at Invoke Node in AB_Source_VI.lvclass:Apply_VI_Properties.vi->AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.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: Incorrect password.
Method Name: Lock Stateet
When I start looking for the file that causes the problems I find that it is "Get File Type.vi" it's protected.
This is an NI file and I do not know the password and I do not know why it is locked.
The VI general properties of the file are:
C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\lvfile.llb\Get File Type.vi
File revision is 78
I tried to solve the problem as discribed in tread
http://forums.ni.com/ni/board/message?board.id=170&message.id=297099&requireLogin=False
But that did not work for me. A build with a new file also gives the same error.
So I tried something else in the Build specification there is a menu "source file settings". There is a selection about passwords
You can choose 3 settings 1) No passord change 2) Remove password 3) Apply new password. I changed this setting from 2 to 1.
And I can build the project now. So I change back from 1 to 2 and I should get the error back again. And I did not. How can this happen?
What is going on?
Thanks in advance

Mike, you can't change the password if you don't know the old one. Why do you want to change the password? I do't wanna change the password. The application builder is asking for it and I do not have it. The same problem occured at thread http://forums.ni.com/ni/board/message?board.id=170&message.id=297099&requireLogin=FalseIt looks almost the same but the solutions there did not work. The problem kept occuring. So I tried someting else:
In the Build specifications there is a menu "source file settings" for your project files. I only have 1 main.vi project file
There is a selection about passwords for your source file settings. See attachment 3. You can choose 3 settings
1) No passord change
2) Remove password
3) Apply new password.
I changed this setting from 2 to 1.And I can build the project now. So problem solved.
Then I changed back from 1 to 2 and I should get the error back again. And it did not.
I do not understand why it works and I would like to.
What is going on?
Attachments:
Authentication.JPG ‏13 KB
VIPropertiesProtection.JPG ‏131 KB
SourceFileSettings.JPG ‏52 KB

Error when building DLL using Keithley library

I'm trying to build a Labview Shared DLL of my VI's, however I'm using Keithley's KPCI-PIO24 Labview driver. When I include any of their library calls into my DLL, I will get a "LABVIEW.LIB was not called from a Labview process". I have mass compiled all the Keithley libs but this hasn't helped. Any ideas??
Bob Wirth

I am not 100% sure but I beleive that the KPCI line of drivers are DOS based. I know that Keithley's GPIB driver is DOS based. I am not sure about the labview drivers. This may have some effect on building a DLL. You may have to settle for building a llb instead of a DLL.
- tbob
Inventor of the WORM Global

Error when building my VI to DLL in LV6.1

pls see the attachment! It's the error display when building my VI to DLL in LV6.1. My lv is PDS Version and i tried reinstall Application Builder , but the same error occurs. How can i resolve it? Thanks a lot!
Attachments:
error_when_builging_DLL.zip ‏44 KB

Goto
..\National Instruments\LabVIEW 6.1\applibs\lvdllbuilder
and double click lvdb.exe. It will run (you will not see anything), registering itself. After running, you might want to goto Task Manager and kill lvdb.exe process manually. Try it now.
A Rafiq

Building DLLs from VIs with array as output

Is there any special way to build DLLs from VIs having arrays as outputs. Suppose I have a VI "Random" with input "nrand" and output an array "the_random2". When I build DLL from the VI, I have something like this in my header file
void __stdcall Random(long nrand, double the_random2[]);
Now it returns void. So I have to pass the array as pointer and retrieve it. If I use Mathscript to load the DLL and call this function, how do I pass the pointer to the array "the_random2"? Simply speaking, any useful method to build DLLs with array outputs and the right way to call them from Mathscript would be appreciated.
Regards
NRK

Hi,
Building DLLs in LabVIEW is described in this tutorial.
Mathscript can call shared libraries such as DLLs, however make sure
that they are compliant with the supported data types as stated here in
this help page. All supported functions for calling/loading shared libraries is described here.
Note that these functions are not supported with the base package. The
details of the sytax of each function is described in their specific
help page.
Hope this helps!
Regards,
Nadim
Applications Engineering
National Instruments

Maven Build Errors from XMExtensionGuide.pdf - Tools & Frameworks 3.1.0

I've downloaded the required files and have followed the instructions in the XMExtensionGuide, and am receiving the following error when trying to execute:
mvn -Pinstall-api
[INFO] Scanning for projects...
[WARNING] The POM for com.adobe.flex:compiler:pom:4.5.1.21328 is missing, no dependency information available
[WARNING] The POM for com.adobe.flex.compiler:mxmlc:jar:4.5.1.21328 is missing, no dependency information available
[WARNING] The POM for com.adobe.flex.compiler:digest:jar:4.5.1.21328 is missing, no dependency information available
[WARNING] The POM for com.adobe.flex.compiler:optimizer:jar:4.5.1.21328 is missing, no dependency information available
[WARNING] The POM for com.adobe.flex.compiler:asdoc:jar:4.5.1.21328 is missing, no dependency information available
[WARNING] The POM for com.adobe.flex.compiler:swcdepends:jar:4.5.1.21328 is missing, no dependency information available
[WARNING] The POM for net.sf.saxon:saxon-dom:jar:9.0 is missing, no dependency information available
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.endeca:sample_editors:0.1 (C:\Endeca\ToolsAndFrameworks\3.1.0\editor_sdk\reference\build\maven\pom.xml) has 1 error
[ERROR] Unresolveable build extension: Plugin org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-RC1 or one of its dependencies could not be resolved: The following artifacts could not be resolved: com.adobe.flex.compiler:mxmlc:jar:4.5.1.21328, com.adobe.flex.compiler:digest:jar:4.5.1.21328, com.adobe.flex.compiler:optimizer:jar:4.5.1.21328, com.adobe.flex.compiler:asdoc:jar:4.5.1.21328, com.adobe.flex.compiler:swcdepends:jar:4.5.1.21328, net.sf.saxon:saxon-dom:jar:9.0, com.adobe.flex:compiler:pom:4.5.1.21328: Failure to find com.adobe.flex.compiler:mxmlc:jar:4.5.1.21328 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
I've read a few articles online and tried to download the plugin, but the download page gives a 404 error. The closest available was flexmojos-maven-plugin-4.0-alpha-5.jar, so I got that, changed the POM reference and tried again. It got further, but ended up with the same basic errors after a lot of downloading:
-1.0.RC6.jar (13 KB at 36.4 KB/sec)
Downloaded: http://repo.maven.apache.org/maven2/com/googlecode/apparat/apparat-core/1.0.RC6/apparat-core-1.0.RC6.jar (18
93 KB at 1332.7 KB/sec)
Downloaded: http://repo.maven.apache.org/maven2/org/scala-lang/scala-library/2.8.0/scala-library-2.8.0.jar (6017 KB at 1
620.4 KB/sec)
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.endeca:sample_editors:0.1 (C:\Endeca\ToolsAndFrameworks\3.1.0\editor_sdk\reference\build\maven
\pom.xml) has 1 error
[ERROR] Unresolveable build extension: Plugin org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-alpha-5 or one of it
s dependencies could not be resolved: The following artifacts could not be resolved: com.adobe.flex:compiler:pom:4.1.0.1
6076, com.adobe.flex.compiler:mxmlc:jar:4.1.0.16076, com.adobe.flex.compiler:digest:jar:4.1.0.16076, com.adobe.flex.comp
iler:optimizer:jar:4.1.0.16076, com.adobe.flex.compiler:asdoc:jar:4.1.0.16076, com.adobe.flex.compiler:swcdepends:jar:4.
1.0.16076, net.sf.saxon:saxon-dom:jar:9.0, jgoogleanalytics:jgoogleanalytics:jar:0.2: Failure to find com.adobe.flex:com
piler:pom:4.1.0.16076 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be
reattempted until the update interval of central has elapsed or updates are forced -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
Any thoughts?

Thanks to Ben Trafton for the answer:
It turns out that Flex compiler dependencies are not hosted on Maven Central, so that is causing the build to fail. This issue would be masked if it is tested in an environment where Maven has access to other repositories with these dependencies (e.g. Endeca Maven repository).
Specifying an additional repository either in the project POM file or in the Maven settings.xml fixed the problem for me. Based on information on this web page -http://www.adobe.com/devnet/flex/articles/flex-maven-flexmojos-pt1.html, this is what I added into the project pom.xml right before the build element:
<repositories>
<repository>
<id>flex-mojos-repository</id>
<url>http://repository.sonatype.org/content/groups/flexgroup</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>flex-mojos-repository</id>
<url>http://repository.sonatype.org/content/groups/flexgroup</url>
</pluginRepository>
</pluginRepositories>
The first build failed for me because of a timeout during artifact download. The second time the build succeeded.

Creative Cloud Packager 1.2 Builds error on Install...

As I posted in this thread, with no resolution, I am running into issues with Creative Cloud Packager 1.2 Builds. The builds create fine, the applications install fine (when you unpack and rename the Set-up.dat to Set-up.exe), however trying to run the build .exe or .msi fails and never installs anything. It appears the build is trying to uninstall the CC applications before doing an install, but fails as there are no CC applications installed. I have tried with the Creative Cloud App running and not running, restarted with all services stopped, etc as directed in the other thread, but still no successful installs. A snippet (as it is the same error for every application in the build) of the error I am being given in the log is:
Exit Code: 33 - The product is not installed, cannot uninstall.
Please see specific errors and warnings for troubleshooting. For example, ERROR: DW040 ...
?08/02/13 17:11:59:044 | [INFO] | | OOBE | DE | | | | 57508 | DEVersion: 5.0.0.0
08/02/13 17:11:59:044 | [INFO] | | OOBE | DE | | | | 57508 | Loading library from C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\DECore\DE5\Setup.dll
[   57508] Fri Aug 02 17:11:59 2013 INFO
::START TIMER:: [Total Timer]
CHECK: Single instance running
CHECK : Credentials
Load Deployment File
Create Required Folders
Assuming uninstall mode
Lookup for master payload
[   57508] Fri Aug 02 17:11:59 2013 ERROR
DW040: The product "{9bcd38e7-1f9a-4536-8cd4-96448263f367}" is not installed. Cannot proceed with the uninstall
[   57508] Fri Aug 02 17:11:59 2013 INFO
##### Running EDT Workflow #####
:: END TIMER :: [Total Timer] took 22.9717 milliseconds (0.0229717 seconds) DTR = 174.127 KBPS (0.170046 MBPS)
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 1 error(s), 0 warning(s)
ERROR: DW040: The product "{9bcd38e7-1f9a-4536-8cd4-96448263f367}" is not installed. Cannot proceed with the uninstall
Please search the above error/warning string(s) to find when the error occurred.
These errors resulted in installer Exit Code mentioned below.
Exit Code: 33 - The product is not installed, cannot uninstall.
Please see specific errors and warnings for troubleshooting. For example, ERROR: DW040 ...
The machine that this is being built and tested on, and will be deployed on, are Windows 7 x64 so what is the cause of this error? Is there anyway to work around to this? Can I creating a batch install with command-line flags for each package Set-up.exe? Is there a way to get a previous or beta build of Creative Cloud Packager so that I can properly deploy the application?
-Eric

Hi eacraft,
Please quit CC desktop if running at the backend and try installing in the given sequence:
Note: It is recommended that Creative Cloud Packager should not be installed on a system where one or more Creative Suite products or Creative Cloud Manager products have been installed.
Adobe Application Manager 3.1 and Creative Cloud Packager can be installed and used on the same machine. However, they should not be running simultaneously for package creation.
Sequence of installation of packages in the Exceptions folder
Except for Acrobat for Windows, all packages in the Exceptions folder should be deployed afteryou have deployed the main MSI or PKG package. However, Acrobat for Windows should be deployed before you deploy the main package.
Therefore, if you are using Exceptions Deployer Application to deploy Acrobat on Windows, you should run Exceptions Deployer Application before deploying the main MSI package. For all other packages, you run Exceptions Deployer Application after deploying the main packages. If theExceptions folder contains Acrobat for Windows as well as other packages, you run Exceptions Deployer Application twice—once before deploying the main MSI package (this will deploy Acrobat for WIndows) and once after deploying the main MSI package (this will deploy the other packages).
Please check for any conflicting processes if running at the backend: http://helpx.adobe.com/creative-cloud/packager/resolving-process-conflicts.html
Regards,
Romit Sinha

Applicatio​n Builder: error in building DLL from a VI

Similar Messages

Maybe you are looking for

Application Builder: error in building DLL from a VI