Labview fail to build exe for a perfect VI?

I build a small example VI,which simply uses a T/F constant to control a case structure. The false case passes through the data, the true case does a filter on the data. This VI runs fine for when the constant is set to either True or False.
However, if I set the constant to False, and try to build the VI into exe file, Labview fails to build exe and give out this error:
An error occurred while saving the following file:
C:\testfilter\Main.vi
Invoke Node in AB_Source_VI.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_Build.lvclass:Build_from_Wizard.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>
If I set the constant to true, then the VI builds fine. That makes no sense, since whatever the constant value is, it should not affect the building process.Anyone knows why Labview is making this error?
Please see the attached sample project, I build it in Labview 8.6.1.   Set the constant to false, and the build fails.  BTW, the code does not do any real "meaningful" thing, it's just an abstraction of a complex program.
Attachments:
testfilter.zip ‏10 KB

I knew this would solve the problem, because I believe the problem is that there is a case that "seems" will never be executed, so the blocks inside the case does not get included (dumped by "smart" compiler) but somehow later needs to be referenced in the build process. If you put it outside the case structure, a copy of that block will be included anyway so later it can be referenced.  I have seen similiar problems in languages like Java.   Good to hear it probabily has been solved in lv 2009, so another reason to fork a few dollars to NI for upgrades...
Dennis Knutson wrote:
I got the same error. I then deleted the code in the true case, selected the low pass filter function that you had outside the case structure, and dragged a copy inside. The build was then successfull. I can't explain what was corrupt and the error message is pointing to functions you did not have.

Similar Messages

  • Labview crashes when building exe

    Hi all,
    I have created a Project and have a main vi which works fine in the development environment. When I try to build exe for the same, LabVIEW crashes. I dont get it why. If anyone could help on this, you are welcome.
    LabVIEW version:2013, 64 bit
    Thanks,
    Prabhu
    Solved!
    Go to Solution.

    Hi Prabhu,
    either provide full error descriptions - or your complete project so somebody else can try to build your EXE…
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Failed to build StructureDefinition for - POJO Datacontrol

    Hi
    I found a message - "<BeanHandler> <getStructure> Failed to build StructureDefinition for : oracle.****.***.model.services.HomeService" in weblogic server log, while the pages renders completely, i did not define any action / actionlistener though.
    The HomeService is simple POJO data control:
    -------------------------------------HomeService.java-----------------------------------
    package oracle.****.***.model.services;
    import oracle.****.***.model.bean.HomeSearchParams;
    public class HomeService {
    private HomeSearchParams homeSearchParams = new HomeSearchParams();
    public HomeService() {
    public HomeSearchParams getHomeSearchParams() {
    return homeSearchParams;
    --------------------------DataControls.dcx---------------------------------------
    <AdapterDataControl id="HomeService" FactoryClass="oracle.adf.model.adapter.DataControlFactoryImpl"
    ImplDef="oracle.adf.model.adapter.bean.BeanDCDefinition" SupportsTransactions="false"
    SupportsSortCollection="true" SupportsResetState="false" SupportsRangesize="false"
    SupportsFindMode="false" SupportsUpdates="true"
    Definition="oracle.****.***.model.services.HomeService"
    BeanClass="oracle.****.***.model.services.HomeService"
    xmlns="http://xmlns.oracle.com/adfm/datacontrol">
    <CreatableTypes>
    <TypeInfo FullName="oracle.****.***.model.bean.HomeSearchParams"/>
    <TypeInfo FullName="oracle.****.***.model.services.HomeService"/>
    </CreatableTypes>
    <Source>
    <bean-definition BeanClass="oracle.****.***.model.services.RdcHomeService"
    xmlns="http://xmlns.oracle.com/adfm/adapter/bean"/>
    </Source>
    </AdapterDataControl>
    --------------------------DataBindings.cpx---------------------------------------
    <dataControlUsages>
    <dc id="RdcHomeService" path="oracle/****/*****/model/services.RdcHomeService"/>
    </dataControlUsages>
    I wonder if there could be any issue here.
    Can anybody advice here..
    Thanks in advance,
    Mayil
    Edited by: user10254453 on Oct 21, 2011 12:08 AM

    Hi,
    does the application run fine ? If so then I don't see why you should worry about this
    Frank

  • Build exe for DSC security tools

    Hi All,
    I am developing an application in LV7.0 which has Visa read/write functions, alongwith that i want to implement some security features using Dsc module's vi present in function palette. My requirement is wen Login button is clicked a login dialog box gets popped up, this i have done by using NI SEC Invoke login dialog. vi. I have also used other security tools like NI SEC User account info.vi, programmatic logout.vi etc.........Vi is working perfectly fine but after making exe, and running it on same pc, login dialog box doesn't gets popped on login button clicked.
    So my doubt is do i need to add some security library files while building exe and creating installer???
    Your reply will be valuable to me
    Thanks & Regards,
    Ratna 

    Hi Sahil,
    Thanks for ur reply. wanted to inform u that i m using only security tools of DSC module, apart from that no other DSC tools. Even though i add all supporting files which was listed in the document named Support Files to Include when Building a LabVIEW DSC Module Application (available on http://zone.ni.com/devzone/cda/tut/p/id/4189) link. In addition to this i also add .rtm file for viewing tool bar while running application and security.llb (available at development machine directory:LabVIEW7.0\Vi.lib\lvdsc>. But still the problem remains as it is. So my question is do i need to add any other supporting files related to DSC security tools, which can solve my problem???????
    If u have any clue, kindly recommend me.
    Regards,
    Ratna 

  • How To Build exe for Previous Versions

    I'm new to LabView and still struggilng a little with all the files associated with a project, so I'm sure this is a simple question.
    I'm running LabView v10 for development, but wish to create an exe that can run on a v8.5 runtime version. I've seen the threads that suggest that this is as simple as 'Save For Previous Version'... but for some reason I cannot seem to make this work. I have tried saving the vi for 8.5, then choosing to build the exe, but upon being prompted to create an associated project, I'm told there are unsaved changes - that the subvi's have been converted to version 10. I've tried declining the changes and opting to use those in memory, but this also doesn't work; the built exe then gives me a runtime error, complaining it does not have LV Runtime 10.
    I've tried saving the project with 'Save for Previous Version', then building. Again, this doesn't work - even though when i open, then immediately close either the project or it's contained vi's, I'm told there are unsaved changes where it has been converted to LV10 - implying the saved files were indeed saved in LV8.5 format.
    I seem to be going round in circles here. Would someone mind laying out the necessary steps to build an exe that can run on a previous runtime environment?
    Thanks in advance
    Solved!
    Go to Solution.

    To my knowledge, none of NI's device drivers can have multiple versions co-existing.  Now, that doesn't necessarily mean if you use any hardware that you will run into problems.  If the hardware is NI hardware, then they will also have specific drivers which can be in conflict, but if they are another manufacturer, it'll come down to NI-VISA probably.  If you are using any NI data acquisiton cards, then you have DAQmx installed.
    As long as your program doesn't access these devices, you are OK.  You are not required to update the drivers if you don't use the hardware.  You need to look in the relase notes for each of the drivers you need to update and see if you can find a version that supports both 8.5 and LV2010.
    Even if you do this, it is not a 100% guarantee that you won't have problems.  I had written an application for a customer once that used NI-RFSA.  I had a control on the front panel based on a typedef in the driver.  I updated my laptop for a new project, but later had to come back and make an update for the original project.  The typedef had changed and caused a recompile.  Nothing broke on my end.  When I sent the update, it crashed on the customer PC because of the typedef change.  I ended up getting them to upgrade the driver on their machine.

  • How to build an .exe for cFieldPoint on a PC ?

    Hi all,
    A couple of weeks ago I installed a system with a compact FieldPoint running a in RT mode (cFP 2020 and LV 7.1.1).
    To load the .exe on the cFP, I connected my PC to the cFP (ethernet), selected the cFP as execution target for LabVIEW and then opened the application builder. I assume this is the normal way to do... but is this the only way ?
    In fact, my customer is asking for some more features, so my question is quite simple :
    Can I build an .exe for the cFP on my PC (without connecting to the cFP target), mail it to the customer and tell him to replace the .exe file on the module ?
    Thanks for any help
    When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

    Hi Kahlid ,
    I noticed you were reply someone on pretty much close to same problem whatever i am having , I am working on LabVIEW8.2 with cFP. I created a project with an executable (run from My Computer),  the other executable is running in the field point , I used shared variable to transfer data from field point to host program. Now I want to Uninstall LabVIEW from the same computer but want to keep MAX  and one .exe file to run host VI. How to do that , any  suggestion about copying or moving only .exe file ? or lets say if I want to run the same program in another new PC with same Field Point hardware and program how to copy/install executable in the new PC?
    Thanks and best regards,
    Faiyaz Syed

  • Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)

    Hi all,
    I have TFS2012 and run several projects.
    We encounterwed with such an error while using Build server.
    Overall Build Process
    Initial Property Values
    AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
    BinariesSubdirectory = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MSBuildArguments = 
    MSBuildPlatform = Auto
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TestResultsSubdirectory = 
    Verbosity = Diagnostic
    00:00
    Get the Build
    00:00
    Update Build Number
    Initial Property Values
    BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
    Final Property Values
    BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
    Result = Ephone_DIT_Deploy_20150424.1
    01:56
    Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
    Initial Property Values
    MaxExecutionTime = 00:00:00
    MaxWaitTime = 04:00:00
    ReservationSpec = Name=*, Tags=
    00:00
    Get the Build Directory
    Initial Property Values
    Result = d:\temp\217\CTI\Ephone_DIT_Deploy
    01:53
    If Not String.IsNullOrEmpty(ConfigurationFolderPath)
    Initial Property Values
    Condition = True
    01:53
    Run TfsBuild for Configuration Folder
    Initial Property Values
    BinariesSubdirectory = 
    BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
    CommandLineArguments = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MaxProcesses = 1
    NodeReuse = False
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TargetsNotLogged = 
    TestResultsSubdirectory = 
    ToolPath = 
    ToolPlatform = Auto
    Verbosity = Diagnostic
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp" 
    00:08
    Getting sources
    00:02
    Labeling sources
    00:19
    Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.
    00:19
    Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.
    00:19
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.
    00:05
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:10
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:05
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    MSBuild Log File
    00:08
    Generating list of changesets
    00:20
    Built Skins\SkinEPhone.cs for default targets.
     Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
     C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
    Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
       at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
       at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
       at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
       at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
       at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
       at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
    00:03
    Creating work item
     Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
    Exception Stack Trace:    at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
       at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
       at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
    Final Property Values
    BinariesSubdirectory = 
    BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
    CommandLineArguments = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MaxProcesses = 1
    NodeReuse = False
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TargetsNotLogged = 
    TestResultsSubdirectory = 
    ToolPath = 
    ToolPlatform = Auto
    Verbosity = Diagnostic
    Final Property Values
    Condition = True
    Final Property Values
    MaxExecutionTime = 00:00:00
    MaxWaitTime = 04:00:00
    ReservationSpec = Name=*, Tags=
    Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
    Final Property Values
    AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
    BinariesSubdirectory = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MSBuildArguments = 
    MSBuildPlatform = Auto
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TestResultsSubdirectory = 
    Verbosity = Diagnostic
    Please have a look and guide where to find a problem
    Thanks ahead

    Hi Hooi,
    I'd like to know whether you can build successfully in your local machine with MSBuild. You have to build succeed with MSBuild beore you can build with TFS Build since TFS build use MSBuild as its default compiler.
    From the error message, you might build with wrong platform for your project. Please check if the build platfrom is proper. If you have customization of your build process template, it would be better to elaborate the reproduce steps and customization details.
    Best regards,

  • Building exe file fails (not enough memory) in LV 2011

    Hello,
    I have a project with about 900 VIs. I'm using Win7 32 Bit with 4 GB RAM (a 32 Bit OS can address about 3,3 GB) with LabVIEW 2011 SP1.
    When trying to build an executable, I allways get the error "Not enough memory to complete the operation" (or something like that).
    My RAM is full at this time.
    Without building the exe file I can start the project without any problems and with only half RAM usage.
    What can I do to generate the exe file with my system?
    Are there any options I can set, that the application builder will not use so much memory?
    Regards
    Matthias

    Hello
    "how much memory do those 900+VIs take on disk????"
    53 MB
    "Ctrl+Run Button is a force compile for a single VI"
    I used Ctrl + Shift + Run
    I also tried the mass compilation tool itself and it doesn't change anything.
    "If the source distribution also plows the memory, you want to split the distribution into several packages"
    That sounds very coimplicated ...
    Did I understand it correctly? I have to create several source distributions (option "directory" and not "llb"). And in my build specification for my exe file, I can chose these source distributions?
    Do I need to prepare my VIs or can I directly create the source distribution with the option "remove block diagram"?
    "I had that problem several times in a large project. I did a mass compile, saved all the VIs, then closed out of the project and LabVIEW. I opened up LabVIEW again and loaded only the main VI. I performed a build and it worked successfully."
    I tried it and a still get the same error.
    My customer need to get the update because it a critical one. And I can't build it.
    An update to Win7 64 bit on my machine is also not a solution because all our customers use Win7 32 bit and the 64 bit executable won't run on a 32 bit operating system.
    Regards
    Matthias

  • Labview shuttin down while trying to Build EXE

    Hello,
     I am trying to develop a program using LabVIEW 8.0 and when I am trying to build exe the Entire LabVIEW software is getting closed. There hadn't been any such problem till now and I had even made EXE files of the same program many times earlier.. Can anyone help me in finding out a solution for this.
    Regards,
    Nitzy 

    hello,
    Does the CPU goes to a 100% while you build the installer? Also doe isclose abruptly (may it says not responsding)
    Why dont you try calling your local NI representative and explain the situation ?
    GUru
    Regards
    Guru (CLA)

  • Labview 8.5 installer build *.exe wrong date code

    In Labview 8.5 application installer build *.exe has a date code of 7/17/2007 even though it was built today.  It will not update even after deleting it.  Is this a known bug?  SS

    Hi SS,
    The Date Modified property of setup.exe shows the date the MetaInstaller was built.  This was true in earlier versions of LabVIEW as well.  It was reported to R&D (# 3T87DAP4) but was determined to be expected behavior.  The actual date and time the installer was built can be determined by looking at the properties of \bin\dp\install.msi.  Feedback is always appreciated, so please feel free to create a product suggestion if you think this should be changed. 
    Jennifer R.
    National Instruments
    Applications Engineer

  • Building Dll for labVIEW RT gives errors

    Hi All
    Does building dll for labVIEW RT using CVI require labview runtime engine to be installed?
    becuase i get some errors of unsatisfied referances to some library while building the dll with target selceted to "labVIEW real time only".
    Regards
    Arun

    Hello Arun,
    You don't need to have LabVIEW Run Time installed on your machine. Please check the link below to see the function that are supported by exporting the LabWindows/CVI LabVIEW RT Engine
    http://digital.ni.com/public.nsf/websearch/D3EFE7C6F073384886256FDD005FBCDA?OpenDocument
    Ame G.
    National Instruments

  • Cbs build portal application dc fail.  Build Plugin IS NOT DEFINED for this

    hi all
    I use NW7.0 ehp1,have portal and a nwdi.
    I create a track at nwdi . and develop a portal application .
    local build is ok . but when i check in .run a activitce.  dc is broken.
    log is -
    CBS Request Log - [  300/DEP_PESKM_D  ]
    Build number assigned: 314
    Change request state from QUEUED to PROCESSING
    REQUEST PROCESSING started at 2010-11-05 02:17:38.921 GMT
        ACTIVATION request in Build Space "DEP_PESKM_D" at Node ID: 13,975,650
         [id: 300; parentID: 0; type: 4]
         [options: NO OPTIONS]
        Waiting for access: 79 ms
        ===== Pre-Processing =====  started at 2010-11-05 02:17:39.000 GMT
            List of requested for activation activities:
                'deep.com_PESKM_1' compartment
                    tet
                        [ISN 111][created by YANLIANG at 2010-11-05 10:17:31.0][OID 6b2f604ae87c11df94ff000000d54062]
                There is 1 activity in compartment deep.com_PESKM_1
                1 activity will be processed by this request
            Analyze dependencies to predecessor activities... started at 2010-11-05 02:17:39.031 GMT
                Analyzing predecessors in compartment "deep.com_PESKM_1"
                    No dependencies to predecessor activities found.
            Analyze dependencies to predecessor activities... finished at 2010-11-05 02:17:39.046 GMT and took 15 ms
            Analyze versions... started at 2010-11-05 02:17:39.046 GMT
                List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2010-11-05 02:17:41.812 GMT and took 2 s 766 ms
                Synchronize metadata for [deep.com.cn/dc_logo_par] started at 2010-11-05 02:17:41.812 GMT
                    Verification of DL [ws/PESKM/deep.com_PESKM/dev/active/] finished at 2010-11-05 02:17:41.906 GMT and took 0 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2010-11-05 02:17:41.937 GMT and took 31 ms
                Synchronize metadata for [deep.com.cn/dc_logo_par] finished at 2010-11-05 02:17:41.937 GMT and took 125 ms
                < CHANGE > 'deep.com.cn/dc_logo_par' DC
            Analyze versions... finished at 2010-11-05 02:17:41.937 GMT and took 2 s 891 ms
            Analyze activities... started at 2010-11-05 02:17:41.937 GMT
                Loading component definitions
                1 component to be build in compartment "deep.com_PESKM_1"
            Analyze activities... finished at 2010-11-05 02:17:42.000 GMT and took 63 ms
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2010-11-05 02:17:42.109 GMT
                    'deep.com.cn/dc_logo_par' variant 'default'
                    'deep.com.cn/dc_logo_par' variant 'default' cannot be built. ACTIVATION will fail.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
            Analyze request DC BV... finished at 2010-11-05 02:17:42.140 GMT and took 31 ms
        ===== Pre-Processing =====  finished at 2010-11-05 02:17:42.187 GMT and took 3 s 187 ms
        Change request state from PROCESSING to FAILED
        Error! The following problem(s) occurred  during request processing:
        Error! The following error occurred during request processing:Activation failed due to component "deep.com.cn/dc_logo_par" variant "default". The component is BROKEN.
    REQUEST PROCESSING finished at 2010-11-05 02:17:42.187 GMT and took 3 s 266 ms
    No build logs available for the request.
    Edited by: yan liang on Nov 5, 2010 3:12 AM

    Hi Yan,
    please check the NWDI troubleshooting guide:
    http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CBS%29Q0030
    --> Understanding Broken and Dirty DCs
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51309e
    Did you import the dependent build plugins for the track in question?
    (tab "development" in the /devinf --> CMS webui --> Transport studio)
    See also the sap note: #1080927 - Creating CMS Tracks for Common Application Types (http://service.sap.com/sap/support/notes/1080927)
    Best Regards,
    Ervin

  • Is LabVIEW application builder needed for TS deployment?

    Does the LabVIEW application builder need to be installed for TS deployment of a project containing LabVIEW VI's?

    LabVIEW Application Builder is only necessary if you are deploying LabVIEW files, even then you can use the flag "Include without Processing Item or Dependencies" in all your LabVIEW files to create an image and optionally an installer without requiring LabVIEW (or app builder) at all; however, using this flag is not recommended becuase if you use it you would have to include all the files and their dependencies in your deployment manually (either by including the root directory of your test system or by adding all the files to your workspace) and you would have to make sure that they are not broken and can be called from the run-time engines you are including in your installer. 

  • System Partition Not Set. Bcdboot failed! bcdboot.exe

    Hey guys,
    I have an issue that I can't get past, and I've completely run out of ideas.
    I have an SCCM 2012 SP1 server and it has KB2801987 applied.
    From this server, I run a Windows 7 Enterprise x86, and a Windows 7 Enterprise x64 task sequence for bare metal deployment to workstations.
    Everything works perfectly fine, EXCEPT when I deploy the Windows 7 Ent x64 WIM, and I've used bootable USB media.
    PXE Booting a machine, and running the task sequence that deploys Win7x64 = works perfectly.
    Advertising the Win7x64 task sequence to a machine = works perfectly
    Booting from a 32-bit boot usb media, running the Win7x64 task sequence -> downloads the boot(x64) WinPE image, then starts deployment = works perfectly
    Booting from 64-bit boot usb media, running the Win7X64 task sequence = Task Sequence Error (0x8004005).
    I've recreated my USB boot media several times. I've tried different brands/models of USB keys, and I always get the exact same error.
    And this is the same error that always happens in my SMSTS.LOG.  It seems it can't set the boot partition, and fails at the every end of applying the WIM image.  And again, this is ONLY when I use USB boot media for THIS particular task sequence. 
    The exact same TS, WinPE boot image and WIM image work just fine when deployed via any other method.  I guess the only thing I haven't tried yet is to make a bootable CD with the same media to see if I get the same issue.  I will try that as soon
    as I can. 
    But any ideas/help is appreciated.  Thanks guys.
    <![LOG[Expand a string: WinPE]LOG]!><time="14:21:09.154-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="executionenv.cxx:782">
    <![LOG[Executing command line: OSDApplyOS.exe /image:BAC0004C,%OSDImageIndex% "/config:BAC00054,%OSDConfigFileName%" /target:0,2 /runfromnet:False]LOG]!><time="14:21:09.154-600" date="02-21-2013" component="TSManager" context="" type="1" thread="1084" file="commandline.cpp:827">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="14:21:09.186-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="commandline.cpp:228">
    <![LOG[Set command line: "OSDApplyOS.exe" /image:BAC0004C,2 "/config:BAC00054,bac_unattend_soe_64.xml" /target:0,2 /runfromnet:False]LOG]!><time="14:21:09.186-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="commandline.cpp:731">
    <![LOG[Found run from net option: 0]LOG]!><time="14:21:09.186-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="applyos.cpp:283">
    <![LOG[Not a data image]LOG]!><time="14:21:09.186-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="applyos.cpp:433">
    <![LOG[ApplyOSRetry: ]LOG]!><time="14:21:09.186-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="applyos.cpp:445">
    <![LOG[TSLaunchMode: UFD]LOG]!><time="14:21:09.186-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="applyos.cpp:446">
    <![LOG[OSDUseAlreadyDeployedImage: FALSE]LOG]!><time="14:21:09.201-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="applyos.cpp:447">
    <![LOG[Adding logical drive: C:]LOG]!><time="14:21:09.201-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="diskutils.cpp:1537">
    <![LOG[Adding logical drive: D:]LOG]!><time="14:21:09.201-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="diskutils.cpp:1537">
    <![LOG[Skipping non-local logical drive: E:]LOG]!><time="14:21:09.201-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="diskutils.cpp:1543">
    <![LOG[Skipping non-local logical drive: F:]LOG]!><time="14:21:09.201-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="diskutils.cpp:1543">
    <![LOG[Skipping non-local logical drive: X:]LOG]!><time="14:21:09.201-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="diskutils.cpp:1543">
    <![LOG[The volume D:\ exists and is a local hard drive.]LOG]!><time="14:21:09.201-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installcommon.cpp:557">
    <![LOG[The volume D:\ is using a valid file system.]LOG]!><time="14:21:09.279-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installcommon.cpp:600">
    <![LOG[Windows target partition is 0-2, driver letter is D:\]LOG]!><time="14:21:09.279-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="applyos.cpp:491">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="14:21:09.279-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="util.cpp:963">
    <![LOG[The machine does not have a local client cache.]LOG]!><time="14:21:09.279-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="installcommon.cpp:1029">
    <![LOG[ResolveSource flags: 0x00000001]LOG]!><time="14:21:09.279-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="resolvesource.cpp:3265">
    <![LOG[SMSTSPersistContent: . The content for package BAC0004C will be persisted]LOG]!><time="14:21:09.279-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="resolvesource.cpp:3274">
    <![LOG[The package BAC0004C is found locally in the cache D:\_SMSTaskSequence\Packages\BAC0004C]LOG]!><time="14:21:09.279-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="resolvesource.cpp:3301">
    <![LOG[Opening image file D:\_SMSTaskSequence\Packages\BAC0004C\Win7 (x64) - Build and Capture v1.0.wim]LOG]!><time="14:21:09.279-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="wimfile.cpp:416">
    <![LOG[Image file BAC0004C version "" will be applied]LOG]!><time="14:21:09.311-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installimage.cpp:463">
    <![LOG[Starting to apply image 2 from Win7 (x64) - Build and Capture v1.0.wim to D:\]LOG]!><time="14:21:09.311-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installimage.cpp:671">
    <![LOG[Wiping D:\]LOG]!><time="14:21:09.311-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installcommon.cpp:799">
    <![LOG[Set "D:\_SMSTaskSequence" to not be wiped]LOG]!><time="14:21:09.311-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installcommon.cpp:808">
    <![LOG[Set "%OSDStateStorePath%" to not be wiped]LOG]!><time="14:21:09.311-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installcommon.cpp:839">
    <![LOG[Set "%_SMSTSClientCache%" to not be wiped]LOG]!><time="14:21:09.311-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installcommon.cpp:839">
    <![LOG[Set "%_SMSTSNewClientCachePathToCleanup%" to not be wiped]LOG]!><time="14:21:09.311-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installcommon.cpp:839">
    <![LOG[Calculating expected free space.]LOG]!><time="14:21:09.326-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="380" file="installcommon.cpp:232">
    <![LOG[Reporting deletion progress.]LOG]!><time="14:21:09.420-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="380" file="installcommon.cpp:250">
    <![LOG[Skipping D:\System Volume Information for wipe]LOG]!><time="14:21:35.627-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="ccmfile.cpp:983">
    <![LOG[Skipping D:\_SMSTaskSequence for wipe]LOG]!><time="14:23:14.716-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="ccmfile.cpp:983">
    <![LOG[Successfully wiped D:\]LOG]!><time="14:23:14.716-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installcommon.cpp:918">
    <![LOG[Applying image to D:\]LOG]!><time="14:23:14.716-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installimage.cpp:710">
    <![LOG[Applying image 2 to volume D:]LOG]!><time="14:23:14.716-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="wimfile.cpp:607">
    <![LOG[Successfully applied image to D:\]LOG]!><time="14:30:47.797-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installimage.cpp:730">
    <![LOG[OfflineRegistry::Init("D:\Windows")]LOG]!><time="14:30:47.797-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="offlineregistry.cpp:168">
    <![LOG[Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1]LOG]!><time="14:30:47.797-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="offlineregistry.cpp:60">
    <![LOG[Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2]LOG]!><time="14:30:49.830-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="offlineregistry.cpp:60">
    <![LOG[CurrentControlSet is mapped to ControlSet001]LOG]!><time="14:30:50.124-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="offlineregistry.cpp:215">
    <![LOG[System root for target OS is D:\Windows, System drive is D:]LOG]!><time="14:30:50.139-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installimage.cpp:919">
    <![LOG[OS Version is 6.1]LOG]!><time="14:30:50.155-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installimage.cpp:938">
    <![LOG[Successfully loaded a source BCD boot system]LOG]!><time="14:30:50.171-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="bootsystem.cpp:1196">
    <![LOG[SetupNewOS: Loaded source boot system from target volume "D:\"]LOG]!><time="14:30:50.171-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="installimage.cpp:1013">
    <![LOG[!sBootDevicePath.empty(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\bootvolume.cpp,34)]LOG]!><time="14:30:50.873-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="bootvolume.cpp:34">
    <![LOG[System partition not set]LOG]!><time="14:30:50.873-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="3" thread="1160" file="bootvolume.cpp:34">
    <![LOG[Unable to find the partition that contains the OS boot loaders. Please ensure the hard disks have been properly partitioned
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="14:30:50.873-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="3" thread="1160" file="bootvolume.cpp:62">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="14:30:50.873-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="commandline.cpp:228">
    <![LOG[Set command line: "bcdboot.exe" D:\Windows /l en-US]LOG]!><time="14:30:50.873-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="commandline.cpp:731">
    <![LOG[Executing command line: "bcdboot.exe" D:\Windows /l en-US]LOG]!><time="14:30:50.873-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="commandline.cpp:827">
    <![LOG[Process completed with exit code 15299]LOG]!><time="14:30:50.889-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="commandline.cpp:1123">
    <![LOG[uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\bcdbooter.cpp,88)]LOG]!><time="14:30:50.889-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="bcdbooter.cpp:88">
    <![LOG[Bcdboot failed! bcdboot.exe D:\Windows /l en-US failed (15299)
    stdout:
    Failure when attempting to copy boot files.
    stderr:
    ]LOG]!><time="14:30:50.889-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="3" thread="1160" file="bcdbooter.cpp:88">
    <![LOG[TS::Boot::BcdBooter::InstallBootFilesAndConfigBCD (sTargetSystemRoot, this->defaultLanguage, sBootVolume), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1065)]LOG]!><time="14:30:50.889-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="installimage.cpp:1065">
    <![LOG[Unloading offline SOFTWARE registry hive]LOG]!><time="14:30:50.889-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="offlineregistry.cpp:270">
    <![LOG[Unloading offline SYSTEM registry hive]LOG]!><time="14:30:52.766-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="offlineregistry.cpp:284">
    <![LOG[SetupNewOs(&pBootSystem), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1543)]LOG]!><time="14:30:53.019-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="installimage.cpp:1543">
    <![LOG[Configure(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1721)]LOG]!><time="14:30:53.019-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="installimage.cpp:1721">
    <![LOG[Installation of image 2 in package BAC0004C failed to complete..
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="14:30:53.019-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="3" thread="1160" file="installimage.cpp:1732">
    <![LOG[installer.install(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1787)]LOG]!><time="14:30:53.019-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="installimage.cpp:1787">
    <![LOG[Closing image file D:\_SMSTaskSequence\Packages\BAC0004C\Win7 (x64) - Build and Capture v1.0.wim]LOG]!><time="14:30:53.019-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="wimfile.cpp:452">
    <![LOG[Entering ReleaseSource() for D:\_SMSTaskSequence\Packages\BAC0004C]LOG]!><time="14:30:53.034-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="resolvesource.cpp:3616">
    <![LOG[reference count 1 for the source D:\_SMSTaskSequence\Packages\BAC0004C before releasing]LOG]!><time="14:30:53.034-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="resolvesource.cpp:3623">
    <![LOG[Released the resolved source D:\_SMSTaskSequence\Packages\BAC0004C]LOG]!><time="14:30:53.034-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="1" thread="1160" file="resolvesource.cpp:3656">
    <![LOG[InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName, bOEMMedia, g_RunFromNet ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,509)]LOG]!><time="14:30:53.034-600" date="02-21-2013" component="ApplyOperatingSystem" context="" type="0" thread="1160" file="applyos.cpp:509">
    <![LOG[Process completed with exit code 2147500037]LOG]!><time="14:30:53.034-600" date="02-21-2013" component="TSManager" context="" type="1" thread="1084" file="commandline.cpp:1123">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="14:30:53.050-600" date="02-21-2013" component="TSManager" context="" type="1" thread="1084" file="instruction.cxx:3012">
    <![LOG[Failed to run the action: Apply Operating System.
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="14:30:53.050-600" date="02-21-2013" component="TSManager" context="" type="3" thread="1084" file="instruction.cxx:3103">
    <![LOG[MP server http://sccm2012svr.domain.local. Ports 80,443. CRL=false.]LOG]!><time="14:30:53.050-600" date="02-21-2013" component="TSManager" context="" type="1" thread="1084" file="utils.cpp:5300">
    <![LOG[Setting authenticator]LOG]!><time="14:30:53.066-600" date="02-21-2013" component="TSManager" context="" type="1" thread="1084" file="utils.cpp:5322">
    <![LOG[Set authenticator in transport]LOG]!><time="14:30:53.066-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="libsmsmessaging.cpp:7751">
    <![LOG[Sending StatusMessage]LOG]!><time="14:30:53.151-600" date="02-21-2013" component="TSManager" context="" type="1" thread="1084" file="libsmsmessaging.cpp:4025">
    <![LOG[Setting message signatures.]LOG]!><time="14:30:53.151-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="libsmsmessaging.cpp:1297">
    <![LOG[Setting the authenticator.]LOG]!><time="14:30:53.151-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="libsmsmessaging.cpp:1327">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: sccm2012svr.domain.local:80 CCM_POST /ccm_system/request]LOG]!><time="14:30:53.151-600" date="02-21-2013" component="TSManager" context="" type="1" thread="1084" file="libsmsmessaging.cpp:8621">
    <![LOG[Request was succesful.]LOG]!><time="14:30:53.214-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="libsmsmessaging.cpp:8956">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=-2147467259]LOG]!><time="14:30:53.214-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="14:30:53.214-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="executionenv.cxx:668">
    <![LOG[Clear local default environment]LOG]!><time="14:30:53.214-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="executionenv.cxx:807">
    <![LOG[Let the parent group (Install Operating System) decides whether to continue execution]LOG]!><time="14:30:53.214-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="instruction.cxx:3212">
    <![LOG[The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="14:30:53.230-600" date="02-21-2013" component="TSManager" context="" type="3" thread="1084" file="instruction.cxx:2425">
    <![LOG[Failed to run the last action: Apply Operating System. Execution of task sequence failed.
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="14:30:53.230-600" date="02-21-2013" component="TSManager" context="" type="3" thread="1084" file="engine.cxx:214">
    <![LOG[MP server http://sccm2012svr.domain.local. Ports 80,443. CRL=false.]LOG]!><time="14:30:53.230-600" date="02-21-2013" component="TSManager" context="" type="1" thread="1084" file="utils.cpp:5300">
    <![LOG[Setting authenticator]LOG]!><time="14:30:53.252-600" date="02-21-2013" component="TSManager" context="" type="1" thread="1084" file="utils.cpp:5322">
    <![LOG[Set authenticator in transport]LOG]!><time="14:30:53.252-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="libsmsmessaging.cpp:7751">
    <![LOG[Sending StatusMessage]LOG]!><time="14:30:53.252-600" date="02-21-2013" component="TSManager" context="" type="1" thread="1084" file="libsmsmessaging.cpp:4025">
    <![LOG[Setting message signatures.]LOG]!><time="14:30:53.268-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="libsmsmessaging.cpp:1297">
    <![LOG[Setting the authenticator.]LOG]!><time="14:30:53.268-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="libsmsmessaging.cpp:1327">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: sccm2012svr.domain.local:80 CCM_POST /ccm_system/request]LOG]!><time="14:30:53.268-600" date="02-21-2013" component="TSManager" context="" type="1" thread="1084" file="libsmsmessaging.cpp:8621">
    <![LOG[Request was succesful.]LOG]!><time="14:30:53.315-600" date="02-21-2013" component="TSManager" context="" type="0" thread="1084" file="libsmsmessaging.cpp:8956">
    <![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="14:31:12.004-600" date="02-21-2013" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:857">
    <![LOG[The command completed successfully.]LOG]!><time="14:31:12.004-600" date="02-21-2013" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:939">
    <![LOG[Successfully launched command shell.]LOG]!><time="14:31:12.004-600" date="02-21-2013" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:430">
    http://www.dreamension.net

    I am getting the exact same issue as the original post, however strangely only with one model of computer (HP Compaq 6300 Pro tower desktops).
    We are using SCCM 2012 SP1 but are not using PXE, USB media only.
    Same symptoms, running a deployment task sequence for x64 Windows 7 Enterprise makes it all the way through the Apply OS step which installs a .wim I've captured previously and fails when attempting to copy down the WinPE environment to continue the task
    sequence.
    All boot images have been updated to WinPE 4.0 and have the according driver packs added. My format and partition step creates 1 partition to use the whole drive. We do not use a separate partition for system reserved because our FDE product does not play
    well with encrypting that partition because it is not an active partition.
    Running the initial attempt from an x64 boot key results in failure, but running on an x86 boot key that requires the x64 boot image for deployment will complete. After the initial failure from the x64 key, the machine can't even be deployed from an x86
    boot key because it still fails to write to the partition. No combination of diskpart and format from the command prompt has been able to get it deployed yet.
    Any other ideas or steps to troubleshoot? I'm open to anything because this is hindering our ability to fully migrate to our 2012 environment.

  • Can't find files when building EXE unless the WHOLE codebase is in an auto-populating folder

    I have a project with FPGA (specifically a couple cRIO targets).
    I have a build spec for a PC target, then a target that's set up for Scan Mode, then a couple targets set up for FPGA mode.
    When I try and build the FPGA or Scan Mode targets, I NEED to have the entire code folder (and sub-folders) in an auto-populating folder.
    What's strange is that I manually added the same folder, and then pulled the Top-level VI out so that it was easier to see within the project.  When I did that, I got errors that files were broken and missing.  I then removed that folder and added the same folder as auto-populating and all is well.
    Yes, I was able to make the build work by including debugging, not removing TypeDefs, etc.  This also cause the build to go from 2MB and 30 secodns build time to 50MB + 10 min build time.
    Why si this?  I would like to remove the files for other targets from the Source of each of the targets.  If I do this, I can't build (these are other top-level VIs that are not appropriate on a per target basis).
    Any ideas?

    Hey Jed,
    It sounds like the problem you are having is coming from a file path issue.  When you manually add folders as "Snapshot" the file paths are set and will generate errors if the files are moved.  The autopopulating folder updates file path locations so you don't have those same issues.  Debug mode allows for the file paths to be reassociated, but at the expense of time, and in some cases resources.  Enabling debugging will cause the compilation to take longer.
    You wrote:
    So what I am trying to say is that ALL I did when I removed the auto-populate was to click "Stop Auto Populate" and moved the Top-level VI up one folder level within the project.  This causes it to fail compile (unless debugging is checked).
    This makes complete sense.  By moving ANY VI in a project and not having the folder set to auto-populate or having debugging enabled will cause an error because that VI that you moved isn't where it is supposed to be.  This is the way that projects and the compilation of programs was designed.
    To avoid this, don't move files around after they have been added to the project unless you have folders set to autopopulate, or have debug mode enabled.  When you start shuffling file paths, associations get broken and compilations will fail.
    Ben N.
    Applications Engineering
    Certified LabVIEW Developer

Maybe you are looking for