Installer build error LV2010

Hello,
I am using LV2010 32bit, vision tools, database tools, Win7 64bit.
I am getting the following error when I try to build an installer. The executable builds without any problems only the installer:
CodeSignAPI.lvlib:Get Signing Error String.vi<ERR>
Error: The Timestamp Authority URL specified does not point to a valid Timestamp Authority server, or an unknown error occurred.
<b>Complete call chain:</b>
     CodeSignAPI.lvlib:Get Signing Error String.vi
     CodeSignAPI.lvlibign with Certificate.vi
     IB_MSI.lvclassign_Setup.vi
     IB_MSI.lvclass:Build.vi
     CDK_Engine_Main.vi
     CDK_Build_Invoke.vi
     CDK_Build_Invoke.vi.ProxyCaller
Loading product deployment information
*** Abort requested.
*** Error Details:
Loading product deployment information
Adding files to installer
Validating...
Copying files...
Scanning files...
Updating files...
Build complete successfully.
Done adding files
Preparing to build deployment
Copying products from distributions
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
Copying files...
Scanning files...
Updating files...
Creating merged database...
Creating installer files...
Build complete successfully.
Copying additional setup files
Compressing installer files
Done building deployment
Solved!
Go to Solution.

Well the error message clearly suggest that there is something wrong with the "Windows Security" section of you installer's specs, try removing the settings from that section and see if it builds properly, then if it does you know where you have to dig.
Good luck
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Similar Messages

Installer Build Error using LV Runtime Engine 2010

I had an executable and installer working that were built in LV2009. Since then I modified my source code and saved as LV version 2010. I rebuilt the executable, but when I tried to run it on the target computer, I got an error message saying that LV Runtime Engine 2010 was needed. So I tried to rebuild the installer using LV Runtime Engine 2010 as an Additional Installer. However, this build was unseccessful and I got a lenghty error msg that I don't understand (see attached).
Thanks in advance.
Solved!
Go to Solution.
Attachments:
Installer Build Error Message.docx ‏13 KB

Hello,
I am building an installer with LV2010 SP1. I have added the runtime engine to be included in the installer. I get the following error
------------------ERROR MESSAGE-----------------------------------
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem
Windows function FindFirstFile returned an error. Error code: 3
*** End Error Report
Done building deployment
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment informationAdding files to installerDone adding filesPreparing to build deploymentCopying products from distributionsCopying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ to: C:\ProgramData\National Instruments\MDF\ProductCache\ ***************** Error: Windows SDK function returned an error. (Error code -12)The system cannot find the path specified.
***************** Error Details:Error in MDF API function: _MDFDistCopyList_CopyItemWindows function FindFirstFile returned an error. Error code: 3*** End Error Report************** Done building deployment
--------------------MESSAGE END------------------
In the additional installer page: I see the installer source location (see attached image file) as 'C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume' which is really my installer's source location. But I am not sure how this location got assigned. I have tried to create new build spec from the same project, still the installer source location stays the same. How do I get this issue solved?
Attachments:
Additional.jpg ‏174 KB

Installer Build Error

Hi,
I am rebuilding an existing Labview application (originally done in LV8.6) using LabVIEW 2011. The application works in LV2011 as stand alone but when I try to build the installer, I get the error for which the details are in the attached text file.
Please help figure out the issue.
Thanks
Jeet
Solved!
Go to Solution.
Attachments:
Installer builder error.txt ‏4 KB

The issue with installer build is fixed. It wasn't able to read the drivers from the CD drive because the CD drive had gone bad.
We replaced the CD drive and it started working.

Installer build issue LV2010

Hello All,
After installing DAQmx 9.8 with my LV2010 installation I can no longer build an installer, I can however build an executable. I removed LV2010 but not everything unfortunatly and reinstalled LV2010 with original device drivers distrubution DVD on my PXI-1042Q with a PXI-8106 Win7 64bit controller and still get the identical "Build Errors" message:
I loaded the _edit.log file and searched for "Edit code -30" and there is not and error in the log as per instructions from this link:
http://digital.ni.com/public.nsf/websearch/8E5E6C58C625B88A8625786A005B21E0?OpenDocument
Any ideas? PLEASE SEE ERROR LOG BELOW
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> NI_MDF.lvlib:MDFConfig_SetDistributionLanguage.vi
Loading product deployment information
*** Error: Improper function call or command line argument. (Error code -30)
*** Error Details:
Error in MDF API function: _MDFConfig_SetDistributionLanguage
The MDF does not have support for distribution language LANGID 9.
*** End Error Report

It sounds like you re-installed LabVIEW 2010 after DAQmx was installed on your computer. This can cause errors.
You may want to make sure you install DAQmx drivers after your LabVIEW 2010. (Re-install DAQmx)
Mark P.
Applications Engineer
National Instruments
www.ni.com/support

Installer build error code-21 Labview 8.6.1

While attempting to build an installer I get an error code -21. What is the error and how do I correct it?

I also have this problem. The executable build itself works correctly, but the installer fails to build. There are a number of DLL dependencies, but they are all included and present in the build and in the installer Source Files. I put CDK.EnableLog=True in my LabVIEW.ini and logged the error from the installer build process. Here is an excerpt from the relevant section:
    [LOG ON] Fri Apr 30 13:46:02 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\MyPrograms\MyApp_Working\Install
<<<MDFConfig_SetBuildMode>>> Build mode: 1
    [NMDK BEGIN] Fri Apr 30 13:46:02 2010
     Building developer part
> Adding files to installer
<<<MDFBuildDevPart_SetFileNames>>>
<<<MDFBuildDevPart_SetDefaultInstallDir>>>
<<<MDFBuildDevPart_SetUpgradeInfo>>>
<<<MDFBuildDevPart_SetOtherProperties>>>
>
> **************
> *** Error: An internal tool or library returned an error. (Error code -21)
Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
nmdkSetInformationalProperties returned error code 26024
> *** End Error Report
> **************
>
Adding product dependencies to developer part
>
> **************
> *** Error: Windows SDK function returned an error. (Error code -12)
Closing dist kit
***** About to begin MAXImportConfig:oMAXPartModifications...
No MAX import files specified - nothing to do - returning.
Error in MDF API function: _MDFBuildDevPart_Close
Error in MDF::BuildDeveloperPart::Close.
ERROR: Caught MSI Exception:
<Unable to format error record.>
MSI error code: 6
> *** End Error Report
> **************
>
    [LOG OFF] Fri Apr 30 13:46:02 2010
    [MDF END] Fri Apr 30 13:46:02 2010
     Closing MDF.
I've also tried the same with a simple test application and it build/installs correctly, so I know it is my project somehow. One notable difference is that I previously had namespace conflicts in the executable build that were resolved by the following these instructions:
http://digital.ni.com/public.nsf/allkb/47272B69E2C167DB862574AC006A258B?OpenDocument
I hope someone can help. I need to deploy this application soon.
Regards,
- Ray

Installer Builder - Install application installer error, NI Variable Engine 2.6.0

Dear All,
Good Day!
Im Shahril.
My PC have 2 version of LV, 2012 and 2013.
The application required NI Variable Engine to be installed.
When i build the installer, nothing got wrong. AKA completed.
But when tested it by install the application installer, the error occurred as attached.
I do many times reinstalling the labview 2013. Still got the same problem.
And i did run the NI Update Service. Update everthing in urgent needs to update.
Please help me.
TQ.
Attachments:
Error NI Variable.png ‏36 KB

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

LV2010 SP1 Installer Build Issue- Cannot find the file it need on requesyed disk

I am migrating a project from LV8.6.1 to 2010SP1 and had issues building the installer that I was finally able to overcome, but something is amiss with the process.
Brand new development PC, running XP SP3, fresh install of LV2010SP Dev Suite and also installed VDM2010 SP1 (even though the project does not use any vision modules).
-          Copied 8.6.1 project to the PC, did a mass compile of it and built the exe from scratch without issues.
-          Now it’s time to build the installer from scratch. Additional Installers were:
LV2010 RTE, MAX 4.7, NI-DAQmx Full App Devel Support 9.2.3, and NI-VISA 5.03.
-          Get the message that it will need some disks to build it which I have on hand:
Dev Suite DVD#2, Drivers DVD, and VDM DVD (huh, why VDM?)
-          The installer build progresses through the first two disks fine but will not find the files it needs on the VDM DVD (it is looking for “NI System Components”).
-          Installer build bails out with a message box and no installer is created (1st attachment). The installer logs are also attached.
-          Try the build process gain, same result.
-          Copied the VDM DVD to my hard drive and point it to that folder to get the files, same result.
-          Try again saying I don’t have the disks on hand. It lists some alternate disks to use but to get all the files it still wants the VDM DVD to complete it. Not much use, the build still fails.
-          Try one last time again selecting that I don’t have the disks on hand. I now notice that the folder the VDM was copied to on the hard drive is an option to select. Select that one and lo and behold the installer is built successfully.
So I guess it boils down to:
            - Why does it need the VDM DVD when there are no components of vision used?
            - Why can’t the installer find the files it needs on the VDM DVD or a copy of the DVD on the hard drive?
            - Why will it only work if I choose that I do not have the disks and point it to a copy of the DVD that resides on the hard drive?
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
Attachments:
MessageDuringVDMCopyForInstaller2010.JPG ‏127 KB
TowersSPCv225Installer_build.log ‏3126 KB
TowersSPCv225Installer_edit.log ‏915 KB

Che:
It gave no specific indication of what it was looking for, the only message that came up was in the screenshot jpg I originally posted.
The only other vague clue I had was it needed NI System Component from the VDM DVD.
Does not make sense that it required the VDM DVD since there were no vision components in the project. I presume it would have taken VISA off of the Dev Suite DVD's.
I can't replicate the problem since I had the build cache the system components required for the project. I'd rather not start deleting folders at this point since I have a viable installer at this time (after many hours of troublshooting expended).
Thanks
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Installer build: When run, error: Windows can't open this file xyz.vi

Hello all, I've taken my vi. I"ve created it as an executable. I've taken that...and made an Installer project... This is with LV 2011, and installing to Win7. The installer seems to work fine...but when I try to run the application from the start menu, I get a windows error, saying it doesn't know what to do with my file xyz.vi...that it needs to know what application to open it with....? Any ideas what to do here? The installer seems to install the NI runtime engine just fine...? Would this be due to, on the Installer builder...setting the vi to be read-only and hidden? When I'd done this a previous time, I believe it all worked then... Suggestions? Thank you, cayenne
Attachments:
screen_shot_windows_error.jpg ‏35 KB

Please disregard...I found the problem after going through the older working one....
Late nights and working two jobs...you start to overlook things.
FOr the dependency, I'd put the vi instead of the exe of the vi.....that did the trick.
Thanks all,
cayenne

Labview 2012 Installer builder issues with Windows 7 64 bit

I have a clients project application program I am working on and am having a lot of trouble getting installed applications to work on Windows 7 properly. The Labview Installer sets the default installation directory to "c:\Program Files\" on Windows Xp and on Windows 7 64bit this defaults to "C:\Program Files (x86). When I install the application on Windows 7 and run it, because Windows 7 64 bit unreasonably protects this directory and every folder under it, if you try to write file to any subdirectory under it (like a reports directory), windows 7 will not let the file write to the directory and the file(s) disappear and you get permission errors. This has been difficult to address. Even logging in as administrator, I have difficulty changing the folder permissions. In addition, when I am in the file write process, if the default directory is coded to come up in the file Open/Save dialog, will not properly
go to and display these protected directories. So thinking that OK, I'll just chage the install directory to something direct to the C: drive and not the Program Files (x86) directory, so I have better control of the folder permissions. Now the Installer build gives errors. It built, but the install fails. Looks like National did not test this for Windows 7 very well. I have run into just about every issue possible with Windows 7 and Labview. Clearly Labview was not very well tested with Windows 7 6 bit. I do not have the Internet toolkit added to the application, only the VISA 5.2 driver. Anyone else having application issues with Labview and Windows 7 and have ideas how to work around this??
Attachments:
BuildErrors.txt ‏11 KB

It's no NI's fault and has nothing to do with 64 Bit either. It is something MS changed starting with Vista, namely tightening security of the whole system to a similar level as was usual on more professional OSes like Unix 20 years earlier. A user has not rights anymore to write into the location where applications are installed. This is for one reason to protect installed applications from being modified by malicious code.
Instead every application should write its runtime data in one of the user writable loacations such as the user's Documents directory for data files, or in the user's or the machine's configuration directory for configuration settings. For single installations you could always set the directory which your application got installed into to be user writable by changing the rights of that directory afterwards but for applications that get installed on normal user computers this is a VERY hacky and discouraged move. Same about installing your application into the root of your system drive. I think it was an oversight by MS to not protect that directory too from user modifications, but was most likely unavoidable to allow DOS application installations to still work.
LabVIEW has functions to retrieve a whole bunch of those preconfigured and user writeable locations and you really should change your application to make use of those locations, instead of trying to write into the installation directory or installing the application into the root location of the system drive, if you want to be compatible with Windows Vista/7/8.
Windows 7 also requires for a number of actions such as installing programs or drivers so called elevated rights. This means that even if you are logged in as administrator you have to explicitedly provide the admin password again to be able to perform the action. This can be done by starting the program as administrator, when this is available in the right click pop-up menu, and is also sometimes done automatically for applications that Windows determines to need those rights such as setup programs for installations.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Custom UDI Pages - Visual Studio Build Error MSB3073

Hello All,
I am attempting to following the MDT 2013 documentation "User Driven Installation - Developers Guide.docx". In this documentation, it walks you through preparing the UDI Development Environment, and then Verify the UDI Development Environment.
It is at this point that I encounter the build error.
I have followed all the steps required to prepare the environment, by copying the required files from the MDT installation directory. I am following the steps within the "Verify That the SamplePage Project Builds Correctly." I have made the modifications
the documentation lists, but after step 13, which starts the debug build, instead of the
No Debugging Information dialog box (as indicated by the documentation), I encounter a dialog stating there were build errors.
Here is the various outputs.
1>------ Build started: Project: SamplePage, Configuration: Debug Win32 ------
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\BDDRun.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\BGInfo.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\CcmCore.dll
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\CcmUtilLib.dll
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\Config.app.xsd
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\Config.xsd
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\EXTRACT.EXE
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\InternationalSettings.xml
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\InternationalSettings.xsd
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\ListOfLanguages.xml
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\ListOfLanguages.xsd
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\Microsoft.BDD.PnpEnum.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\Microsoft.BDD.Utility.dll
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\msvcp100.dll
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\msvcr100.dll
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\OSDRefreshWizard.dll
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\OSDSetupWizard.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\ServiceUI.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\SharedPages.dll
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\Smsboot.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\SmsCore.dll
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_01.BGI
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_01.BMP
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_02.BGI
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_02.BMP
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_03.BGI
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_03.BMP
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_04.BGI
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_04.BMP
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_05.BGI
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_05.BMP
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_06.BGI
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\STEP_06.BMP
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\TsCore.dll
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\TSEnv.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\TsManager.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\TsmBootstrap.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\TsMessaging.dll
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\TsProgressUI.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\TsResNlc.dll
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\UDI_Wizard_Banner.bmp
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\WindowHide.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\WinRERun.exe
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\xprslib.dll
1> 44 file(s) copied.
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\en-us\OSDRefreshWizard.dll.mui
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\en-us\OSDSetupWizard.exe.mui
1> C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\en-us\SharedPages.dll.mui
1> 3 File(s) copied
1> The system cannot find the file specified.
1> 1 file(s) copied.
1> The system cannot find the file specified.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: The command "copy /y "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\*.*" "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\Debug\"
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: xcopy /y /i "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\en-us" "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\Debug\en-us"
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: copy /y "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\OSDResults\Images\UDI_Wizard_Banner.bmp" "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\header.bmp"
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: copy /y "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\Config.xml" "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\Debug\”
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: copy /y "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\header.bmp" "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\Debug\header.bmp"
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: :VCEnd" exited with code 1.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
Error:
Error 1 error MSB3073: The command "copy /y "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\*.*" "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\Debug\"
xcopy /y /i "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\x86\en-us" "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\Debug\en-us"
copy /y "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\..\..\..\..\OSDSetupWizard\OSDResults\Images\UDI_Wizard_Banner.bmp" "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\header.bmp"
copy /y "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\Config.xml" "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\Debug\”
copy /y "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\SamplePage\header.bmp" "C:\Users\AErmie\Documents\UDI Development\SDK\UDI\SamplePage\Debug\header.bmp"
:VCEnd" exited with code 1. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets 113 6 SamplePage
Please remember to click “Mark as Answer” on the post that helps you.
AdinE MCSE, MCSA, MCITP, MCTS; (Specializing in System Center and Private Cloud)
LinkedIn: http://ca.linkedin.com/in/adinermie
Website: http://AdinErmie.Wordpress.com

Hi Kamrun,
Looks exactly like a problem I had earlier in the year when I started creating projects on a new machine. My solution is in the thread below:
http://forums.adobe.com/thread/675154?tstart=0
The key post was...
function(){return A.apply(null,[this].concat($A(arguments)))}
I've done a little more investigation and have tracked the problem down to the xxxODFRC.rsp file. Each path in an rsp file is put on a newline. This is done by appending a Carriage Return character (0x15) to the end of each path.
If you specify a different path for the headers (i.e. ".\headers"), it will be added to the end of the ODFRC.rsp and CPP.rsp files.
The problem is that a Carriage Return is not added to the end of the headers path. The "s" is the last character in the file. If I add a carriage return to the end of the line, the project compiles correctly. If you don't specify a different path, the last characters in the ODFRC.rsp file are 0x0A 0x0A 0x0A and in the CPP.rsp file 0x0A 0x0A.
This would appear to be a bug in Dollyxs. Probably introduced with CS5?
I can't say if this is a proper solution of just a hack that works on my machine. But there's no harm in giving it a go.
Cheers,
APMABC

Labview 2009 SP1 Installer build help needed

Hello,
First time posting here. I have a rather large project that I recently converted from Labview 7.0 to 9.0. I am able to build an executable and it starts up Ok but I don't know for sure if it works. Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1. The executable then complains that it needs the full development version to work. I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.
Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer. Here's the Build Errors from the pop-up dialog:
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_SetOtherProperties.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
*** Error: An internal tool or library returned an error. (Error code -21)
*** End Error Report
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
The build log file has slightly more info:
    [LOG ON] Mon May 31 20:55:07 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
<<<MDFConfig_SetBuildMode>>> Build mode: 1
    [NMDK BEGIN] Mon May 31 20:55:07 2010
     Building developer part
> Adding files to installer
<<<MDFBuildDevPart_SetFileNames>>>
<<<MDFBuildDevPart_SetDefaultInstallDir>>>
<<<MDFBuildDevPart_SetUpgradeInfo>>>
<<<MDFBuildDevPart_SetOtherProperties>>>
>
> **************
> *** Error: An internal tool or library returned an error. (Error code -21)
Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
nmdkSetInformationalProperties returned error code 26024
> *** End Error Report
> **************
>
Adding product dependencies to developer part
>
> **************
> *** Error: Windows SDK function returned an error. (Error code -12)
Closing dist kit
***** About to begin MAXImportConfig:oMAXPartModifications...
No MAX import files specified - nothing to do - returning.
Error in MDF API function: _MDFBuildDevPart_Close
Error in MDF::BuildDeveloperPart::Close.
ERROR: Caught MSI Exception:
<Unable to format error record.>
MSI error code: 6
> *** End Error Report
> **************
>
    [LOG OFF] Mon May 31 20:55:07 2010
    [MDF END] Mon May 31 20:55:07 2010
     Closing MDF.
I realize that I should post my project file but I can't do that until tomorrow. From those 2 errors, can you tell me what the installer builder is looking for? I have gone through all my dependencies and they look Ok at the moment.
Thanks for you time.

Hi Celeb,
I had to help out on another project and finally only getting back to looking at this issue yesterday. As you suggested, I went ahead and created a new project and created new build specifications (exe and installer). I was able to properly build both items but won't be able to check out the executable til later this week.
I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View. I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder. Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly. This might have been the cause of my inability to build an installer with the converted project/build specs.
I hope NI could add in more details into the build error messages. As it is, it's really difficult to know why a build failed because there's no details in those messages.
Thanks again,
T.

Application builder error coder 21

I get this error code when trying to build an application and include the visa runtime install files
What can i do to fix this error
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Validating...
Copying files...
Scanning files...
Updating files...
Build complete successfully.
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'LabVIEW 2009, Media 1' from: \\dtads2\it_software$\Labview 2009\DVD 1 of 2\Distributions\LabVIEW\LabVIEW2009\ to: C:\Documents and Settings\brockmaa\Desktop\11164 Carnivore\builds\FVT1_4 test\My Installer\
Copying distribution 'National Instruments Device Drivers - February 2010' from: C:\National Instruments Downloads\NI Device Drivers\Feb10\ to: C:\Documents and Settings\brockmaa\Desktop\11164 Carnivore\builds\FVT1_4 test\My Installer\
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
*** Error: An internal tool or library returned an error. (Error code -21)
Error Messages
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper32.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-ORB' not found for part 'niorbi.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-ORB {F2D3406A-0A97-4EB9-9A09-F20A874C16F9}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-ORB' not found for part 'niorbi64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-ORB {F2D3406A-0A97-4EB9-9A09-F20A874C16F9}.xml'.
*** Error Details:
Error in MDF API function: _MDFBuildDist_Build
Error List
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper32.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
While validating input parts.
and so on

Hi brockmaa,
It seems that the files it needs to include the VISA runtime are not being found on your system. Try re-installing the correct version of VISA you need from:
http://www.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:du,n8:3.25.123.1640,ssna...
and try to build the installer again and it should be able to find the correct files.
DylanC

SSDT Build Error - SQL72001: File ... does not exist

I am new to SSDT.
My general workflow is to use SQL Schema Compare (comparing the database to the project) to update an SSDT project. When the Compare ends up deleting some script files from the project, sometimes I got this error.
SQL72001: File "C:\TFS\Source\Dev\Testdb\dbo\Stored Procedures\usp_test.sql" does not exist.
The symptom was that the script file was deleted, the script icon was removed from SSDT, this script was not referenced by any other script files, but somehow TFS still showed the error
when I built the project.
The way i went around of the problem was to copy the file back to the file system, and added it to the project, make sure that the build was OK, and then delete the script and
build again.
I found an related post https://social.msdn.microsoft.com/Forums/en-US/44c186e8-5fd9-44fb-94f1-a8a139cbc9fd/vs2k13-build-errors?forum=ssdt, but it does not seem to be the same issue.
I am using the free SSDT downloaded from Microsoft site. The SSDT version is 11.1.40403.0.
I cannot find a button from the Visual Studio to check the update of SSDT. What is the proper way to keep SSDT updated? Should I manually download the installation file and install it?
Thanks.

Hi Seaport, there are two things here:
- Where is this failure occurring - when building in VS, from the command line, after a commit to TFS? The most likely cause of this build error is that the project changes have not been saved to disk. For example, if you manually delete a file from a project
in VS then you need to save the project file for this change to be pushed to disk. The recommended solution is to ensure you save the project, or hit "Build" which should do this automatically.
- Check for updates in VS2012 by clicking SQL -> Check For Updates... You can also go to our
website and check the latest version from there.
Thanks,
Kevin

Application builder Error: Windows SDK function returned an error. (Error code -12) *** End Error Report

try to create an installer in Labview 8.6. The build fail and I got this message.
CDK_CreateNewWizard_Invoke.vi.ProxyCaller >> CDK_CreateNewWizard_Invoke.vi >> CDK_InstallerConfiguration_Editor.vi
>> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'NI LabVIEW 8.6.1 Datalogging and Supervisory Control Module' from:
D:\software\application\LabView\NI.LABVIEW\NI-Labview 8.6.1 DSC Module\ to: C:\Documents and Settings\Lidaoling\桌面
\Builds\generate waveform\My Installer\
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
Copying files...
Updating files...
Creating merged database...
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
Done building deployment

Solution

ITunes gives me an error and asks for re-installation, the error is "The procedure entry point CMBlockBufferCopyDataBytes could not be located in the dynamic link library coreMedia.dll", and the iTunes can not be lunched any more

iTunes gives me an error and asks for re-installation, the error is "The procedure entry point CMBlockBufferCopyDataBytes could not be located in the dynamic link library coreMedia.dll", and the iTunes can not be lunched any more.
can you please help, as I also tried to re-install it but pr

Entry point errors can often be fixed by deleting the offending dll, then repairing the component it is part of. CoreMedia.dll is part of Apple Application Support.
For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down the page in case one of them applies.
Your library should be unaffected by these steps but there is backup and recovery advice elsewhere in the user tip.
If the advice above doesn't resolve things you could try this alternate version:
iTunes 12.1.0.71 for Windows (64-bit - for older video cards) - itunes64setup.exe (2015-01-28)
which is a 64-bit installer for the 32-bit version of the core application, similar to previous 64-bit releases.
Or roll back to the previous build:
iTunes 12.0.1.26 for Windows (32-bit) - iTunesSetup.exe (2014-10-16)
iTunes 12.0.1.26 for Windows (64-bit) - iTunes64Setup.exe (2014-10-16)
tt2

Installer build error LV2010

Similar Messages

Maybe you are looking for