"VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors"

Hi,
I had created an executable in LabVIEW 8.6 on a windows XP 32 bit PC. The application uses some Vision VIs. The executable runs in most of the PCs except one. the PC is a windows 7 64bit. Initially i got the error "Labview Load error code 3: could not load front panel". I fixed this by changing the source file settings in the application builder. Now i am getting the error "VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors" and the exe shows a broken run button.
But if i build the exe in the same PC i get no errors and it works fine. Moreover i have tested this exe in a different PC with the same configuration, it works there. I have tried reinstalling labview in the PC the problem still persists.
Solved!
Go to Solution.

Hi Rajshekar.
> Which version of LabVIEW are you using on PC with Win7 64bit? would like to check if there are any issues with LV2009 32bit on 64bit OS..
      - The version of Labview on the win7 64bit PC is also lv8.6 full development system.
> Do you get the same error on the other PC with same config(Win7) when running the .exe generated using LV 8.6 on WinXP 32bit? just to make sure the problem is with OS or LV..
      - the same problem occured at one more PC with the same configuration. but when i tested in an another PC of the same config it worked i am not able to isolate and decide that the error is based on one particular PC config.
I have listed the environments in which application ran and how the application was put in to the PC.
I would also like you to know that i have created an installer for the exe. I am also using NI vision in my application and this is the error "An error occured loading VI 'IMAQ GetImagePixelPtr'. LabVIEW load error code 3: could not load front panel"....and rest is what i said in my previous post
1. Use the installer to install the application.
2. just copy the exe created in LV 8.6 into a PC that already has LV development system installed in it
3. The PCs might either be a blank one with no history of LV installed in them
4. The PCs might have diffrent versions of LV development systems installed in them (8.2,8.5,8.6,2009)
All PCs that have LV development system(s) installed in them, was able to run the application except the one with win7 64, where i have tried uninstalling all NI software and use only the installer to install, install LV 8.6 full development system and try runnning the exe, nothing works.
Thanks

Similar Messages

  • I recieve the following error when running an executable ("This VI is not Executable. The full development version of Labview is required to fix the errors"

    I recieve the following error when trying to build and run a labview executable. I am able to build the executable but when trying to run the executable, a pop up window comes up asking the user to select a dll. (please see screen shot attached). Once the DLL is selected, I get the error that This VI is not Executable. The full development version of Labview is required to fix the errors. (please see screen shot attached). I have also attached a snapshot of the project window.
    I have the professional development system
    I can run the main VI
    all the required DLL's are in the dependencies section of the project window.
    I am trying to find the root cause of this error but to no avail. can anyone give me a clue to what i am missing here. Any suggestions on where i should look to find the problem ?
    Thanks in advance to all labview users for your help
    Attachments:
    project window.PNG ‏36 KB

    other PNG
    Attachments:
    Broken Arrow on EXE.PNG ‏179 KB

  • Please help suggestions for solving built-only compiler error: 'The VI is not executable. The full development version of LabView is required tofix this error.'

    We have develoepd a software tool and build it on regular basis. It currently runs error free when compiled in the editor, but when we built it and run the executable stand alone we get the error.
    'The VI is not executable. The full development version of LabView is required tofix this error.' plus a broeken error.
    This menas an compiler error that is not present in the editor but in the stand alone version. We tried to identify errors as suggested in several posts in this forum, but so far unsuccesfull.
    As the editor and its compiler do not see the error  and are running fine and the stand alone version just syas 'find the error in the editor' in this case LabView is of no help.
    Can anyone suggest a sensible or 'good practice ' way of searching for the source of this error?
    Our project  comprises hundreds of Vis over several libraries.
    Thanks,
    Chris

    Thanks Craig for all your suggestions.
    We seem to have located the problem in a new vi just added to the package causing conflicts by using the same vi names as other vis already present in the package. Excluding this vi removed the error.
    It seems related to a conflict by having two vis with the same name, which was mentioned by LabView and interactively resolved when running the main vi from the editor. When successfully building the main vi the builder did not mention this conflict and reported a successful build, but when trying to run the executable it gave the cryptic error. The error caused us problems because there was no hint for the cause, just the suggestion to solve this in the editor, while at the same time in the editor the VI was running fine.
    We will post about this in detail after we have positively proven that this actually was the case.
    The .net version issue was already checked.
    Performance was the same on all machines we tested on including the dev machine.
    Debugging was tried nut did not help as the vi could not run (broken arrow). We assumed that debugging only helps in running faulty functioning vi''s. We did not check for broken arrows in sub-vis (after connecting), that could have helped, although our application has hundreds of our own vis.
    In relation to your remark: 
    'Are you using many classes? Have you verified that the proper access scopes are set for functions calling those vis?'
    Could you elaborate on setting access scopes. We were not aware of this option in LabView, although we realize this is a basic element of the underlying c code.
    Ragrds,
    Chris

  • The VI is not executable. The full development version...

    "The VI is not executable. The full development version of LabVIEW is required to fix the errors." That is the error I've been dealing with all day. Actually it is repeated 3 to 4 times in the error message, seen when first launching the EXE. Also of note is that the run-arrow is broken. This is in an EXE that was developed well before version 2013, but I recently upgraded it to 2013 to hopefully fix some random LVRT crashes. There is obviously no issue running the code on my development machine, only once it's deployed.
    The good news is I've been able to solve the problem (mostly). My EXE now runs without the errors. I found that the problem wasn't actually in the EXE.
    We have a separate project with no files, but in the build specification we have the LabVIEW 2013 Run-Time Engine, as well as NI-VISA for serial support. We then bundle the deployment in a self-extracting RAR and it does its business. In the past this has worked just fine, but with LV2013, it seems that there is a component missing from the deployment.
    I found that if I download the Run-Time Engine directly from NI.com and run it, the only things I need to install are the Run-Time Engine, and the DEPLOYABLE LICENSE. If I do this, my EXE runs great, but with the custom installer, it is not included for some reason!
    Putting aside the fact that I don't know why the Deployable License package is needed (we aren't connecting to remote panels), I can't seem to modify my custom installer to install the Deployable License. There are versions for LabVIEW 2009 and 2011 SP1 in the Additional Installers list, but I don't see 2013.
    Can anyone explain why this is??? For now I will just distribute the 257MB Run-Time Engine and the NI-VISA installers separately I guess. But I'd really like to get back to a single, simple package to install all the prerequisites we need. HELP!

    iannicholson wrote:
    Yes, but then every installer I build will contain the runtime engine. That gets very large very quick. So I have an installer for JUST the runtime engine and VISA runtime.
    Just remove them from the "Additional Installers" tab of the Installer dialog.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • A full development version of labview required to fix the errors.

    When i tried to run my exe file, it gives following error.
    "A subvi is not executeable.A full development version of labview required to fix the errors."
    i do have full version of 6.02.
    Am i missing something something when i built exe?
    any Help will be appreciated.

    Well, here we go again...
    I have seen this error way too many times in my day.
    The problem is you have a bad linkage, or unsaved or compiled VI in your hierarchy when you built the application.
    Open your main, or otherwise open (into memory) ALL VIs in your hierarchy. Then, do a save all from the file menu. This should solve the issue.
    The other reason I have seen this is if you have bad linkage. As there is no real way to tell what your linkage is, you need to go into the hierarchy, select View Full Path in Title and make sure everything is where you think it is. I have often seen this occur even when the application I was building from was in perfect condition. Often times, when the app builder is used, VIs will be called from locations you
    don't expect.
    You have to be VERY careful about developing in a hierarchy. I actually got to a point where I had to even place all the NI VIs into my directory structure.
    Take a careful look at the hierarchy. Chances are the executable is calling the wrong code, or is compiling with the wrong version.
    If in doubt, go to a fresh machine, and move all of your VIs (individually if you have to, or as a .llb preferably) to the new machine and build it from there. Alternatively, you can try doing a save as from your main and select "application distribution" this will resolve any issue with VI locations, except where Dynamic VIs are being used.
    Good luck, 'cause you are going to need it.

  • I downloaded trial of LR4 and then bought the full boxed version...how do I transfer my catalog?

    I downloaded the trial of Lightroom and liked it enough to buy it. I bought the full, boxed version. Do I install again from the cd? Or do I just put in my new serial number next time it asks me if I want to "try or buy?"
    Thanks

    Hi misskayrenee,
    You can simply put the serial number next time its asks and the trial version would be converted to full.
    To transfer catalogs please refer : http://digital-photography-school.com/moving-a-lightroom-catalog
    http://blogs.adobe.com/jkost/tag/working-with-catalogs
    http://helpx.adobe.com/lightroom/kb/catalog-faq-lightroom.html

  • Two days ago, I loaded Light Room 6. Today I went back to Light Room 5. LR 6 corrupted an entire folder of images, and caused errors on my Raid 5 causing win 7 to run "Chk Dsk" and fix the errors to the operating system. LR 5 has not shut down for the las

    Two days ago, I loaded Light Room 6. Today I went back to Light Room 5. LR 6 corrupted an entire folder of images, and caused errors on my Raid 5 causing win 7 to run "Chk Dsk" and fix the errors to the operating system. LR 5 has not shut down for the last 5 hours. LR 6 has a serious bug. Anyone else experiencing this problem. Yesterday I was on tech support, waiting for 3 hours, finally they picked up and informed me there department was closing and someone else would call me on Monday. So, I'm working today and all day Sunday to make up for the down time using LR 6.
    I don't know if the bug exists in the program or the "Creative Cloud.
    Question: Does anyone know why if I bought Light Room 6 [NOT Light Room CC with the monthly rental], I have to enter my serial number if I want to use it?

    Entering the serial number is probably part of the registration process.
    Just out of curiosity, what were you doing on LR6 when the folder of images became corrupted?

  • My Iphone 4 will not start up, when i connect it to itunes i says : Activation error This device is not registered as part of the iPhone Developer Program.If you are a member of the Program, please register your device in the iPhone Developer Program Port

    my Iphone 4 will not start up, when i connect it to itunes i says : Activation error This device is not registered as part of the iPhone Developer Program.If you are a member of the Program, please register your device in the iPhone Developer Program Port

    Well, you downloaded a bootleg copy of iOS 7 beta and have installed it on your phone without being a developer. It has bricked your phone and you cannot get help here because doing what you did has voided your warranty. Have a nice day.

  • The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error

    We are getting the below error when we see in Crawl logs
    "The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error."
    This is happening in FAST search.
    Here I can see soke of the logs related to this search crawl.
    Could anyone please help on this?
    web application 'http://xvy/' doesn't use search application 'FAST Query SSA', skipping it.
    ABC\sp_search' on web application 'http://xvy/'. 2d7dba01-3d2e-4903-b59f-9a8601627bcd
    07/30/2014 01:30:46.65  OWSTIMER.EXE (0x28DC)                    0x1BC0 SharePoint Server Search       Administration               
     dl2m Verbose  Search application 'Search Service Application 1': Skipping web application '48ed7882-9f70-424e-bf72-e3c9f5340b97' because its outbound url 'http://ebc:30347' was automatically added once.
    Ensure full read access to the indexing account 'ABC\sp_search' on web application 'http://nvcp/'. 85041609-d618-4132-ac8e-195a910d99a0
    07/30/2014 01:31:46.53  OWSTIMER.EXE (0x28DC)                    0x05F4 SharePoint Server Search       Administration               
     dl2m Verbose  Search application 'FAST Query SSA': Skipping web application '57718ea1-8cb5-4adc-abd2-9e55415e5791' because its outbound url 'http://nvcp' was automatically added once. 85041609-d618-4132-ac8e-195a910d99a0
    07/30/2014 01:31:46.53  OWSTIMER.EXE (0x28DC)                    0x05F4 SharePoint Server Search       Administration               
     dl2n Verbose  Search application 'FAST Query SSA': Adding start address 'http://nvcp' for web application '57718ea1-8cb5-4adc-abd2-9e55415e5791' to list of valid start addresses. 85041609-d618-4132-ac8e-195a910d99a0
    07/30/2014 01:31:46.53  OWSTIMER.EXE (0x28DC)                    0x05F4 SharePoint Server Search       Administration               
     dmb6 Verbose  Ensure full read access to the indexing account 'ABc\sp_search' on web application 'http://nvcp'ext/'. 85041609-d618-4132-ac8e-195a910d99a0
    07/30/2014 01:31:46.53  OWSTIMER.EXE (0x28DC)                    0x05F4 SharePoint Server Search       Administration               
     dl2m Verbose  Search application 'FAST Query SSA': Skipping web application '64d562a1-535e-4917-8979-88840e2a67fe' because its outbound url 'http://nvcp'ext' was automatically added once. 85041609-d618-4132-ac8e-195a910d99a0
    07/30/2014 01:31:46.53  OWSTIMER.EXE (0x28DC)                    0x05F4 SharePoint Server Search       Administration               
     dl2n Verbose  Search application 'FAST Query SSA': Adding start address 'http://nvcpext' for web application '64d562a1-535e-4917-8979-88840e2a67fe' to list of valid start addresses. 85041609-d618-4132-ac8e-195a910d99a0
    07/30/2014 01:31:46.53  OWSTIMER.EXE (0x28DC)                    0x05F4 SharePoint Server Search       Administration               
     dmb6 Verbose  Ensure full read access to the indexing account 'ABC\sp_search' on web application 'http://nvcpnew/'. 85041609-d618-4132-ac8e-195a910d99a0
    executing SQL query {? = call dbo.proc_MSS_PropagationIndexerGetReadyQueryComponents}  [propdatabase.cxx:70]  d:\office\source\search\native\ytrip\tripoli\propagation\propdatabase.cxx 
    07/30/2014 01:32:04.31  mssearch.exe (0x0588)                    0x1DE4 SharePoint Server Search       Propagation Manager          
     e3o3 Verbose  executing SQL query {? = call dbo.proc_MSS_PropagationIndexerGetReadyQueryComponents}  [propdatabase.cxx:70]  d:\office\source\search\native\ytrip\tripoli\propagation\propdatabase.cxx 
    07/30/2014 01:32:04.68  mssdmn.exe (0x15CC)                      0x1060 SharePoint Server Search       HTTP Protocol
    Handler          du4i                     0x29E4 SharePoint Server Search       HTTP
    Protocol Handler          du4i Verbose  CHttpAccessorHelper::InitRequestInternal - opening request for '/robots.txt'.   [httpacchelper.cxx:353]  d:\office\source\search\native\gather\protocols\http\httpacchelper.cxx 
    07/30/2014 01:32:04.70  mssdmn.exe (0x15CC)                      0x29E4 SharePoint Server Search       HTTP Protocol
    Handler          du54 High     CHttpAccessorHelper::InitRequestInternal - unexpected status (503) on request for 'http://ppecpnew/robots.txt' Authentication 0.  [httpacchelper.cxx:703] 
    d:\office\source\search\native\gather\protocols\http\httpacchelper.cxx 
    07/30/2014 01:32:04.70  mssearch.exe (0x0588)                    0x130C SharePoint Server Search       Gatherer                     
     cd11 Warning  The start address http://nvcp'/sites/quipme cannot be crawled.  Context: Application 'FAST_Content_SSA', Catalog 'Portal_Content'  Details: 
    The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error.   (0x80041200) 
    07/30/2014 01:32:04.70  mssdmn.exe (0x15CC)                      0x104C SharePoint Server Search       HTTP Protocol
    Handler          du4i Verbose  CHttpAccessorHelper::InitRequestInternal - opening request for '/robots.txt'.   [httpacchelper.cxx:353]  d:\office\source\search\native\gather\protocols\http\httpacchelper.cxx 
    07/30/2014 01:32:04.70  mssdmn.exe (0x15CC)                      0x104C SharePoint Server Search       HTTP Protocol
    Handler          du54 High  
    07/30/2014 01:32:04.70  mssearch.exe (0x0588)                    0x2948 SharePoint Server Search       Gatherer                     
     cd11 Warning  The start address
    http://nvcp'/sites/MDPPubng cannot be crawled.  Context: Application 'FAST_Content_SSA', Catalog 'Portal_Content'  Details:  The crawler could not communicate with the server. Check that the server is
    available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error.   (0x80041200) 
     CHttpProbeHelper::ProbeServer: InitRequest failed for 'http://ppecpnew/_vti_bin/sitedata.asmx'. Return error to caller, hr=80041200  [stscommon.cxx:490]  d:\office\source\search\native\gather\protocols\common\stscommon.cxx 
    07/30/2014 01:32:26.06  mssdmn.exe (0x15CC)                      0x193C SharePoint Server Search       PHSts                        
     dvg0 High     STS3::COWSServer::InitializeClaimsCookie: Probing url 'http://pncvr' failed. Return error to caller, hr=80041200  [sts3util.cxx:1332]  d:\office\source\search\native\gather\protocols\sts3\sts3util.cxx 
    07/30/2014 01:32:26.06  mssdmn.exe (0x15CC)                      0x193C SharePoint Server Search       PHSts                        
     en0e High     CSTS3Accessor::InitURLType: Return error to caller, hr=80041200                 [sts3acc.cxx:2214]  d:\office\source\search\native\gather\protocols\sts3\sts3acc.cxx 
    07/30/2014 01:32:26.06  mssdmn.exe (0x15CC)                      0x193C SharePoint Server Search       PHSts                        
     dv3p High     CSTS3Accessor::GetServer fails, Url sts4://pnvpr/siteurl=sites/product/siteid={7ebfb072-08a8-4df7-8f74-e06730325d9a}/weburl=/webid={bd7ae724-1256-4b26-9633-416447d6bc5c}, hr=80041200  [sts3acc.cxx:185] 
    d:\office\source\search\native\gather\protocols\sts3\sts3acc.cxx 
    07/30/2014 01:32:26.06  mssdmn.exe (0x15CC)                      0x193C SharePoint Server Search       PHSts                        
     dvb1 High     CSTS3Accessor::Init fails, Url sts4:/mngbv/siteurl=sites/product/siteid={7ebfb072-08a8-4df7-8f74-e06730325d9a}/weburl=/webid={bd7ae724-1256-4b26-9633-416447d6bc5c}, hr=80041200  [sts3handler.cxx:312] 
    d:\office\source\search\native\gather\protocols\sts3\sts3handler.cxx 
    07/30/2014 01:32:26.06  mssdmn.exe (0x15CC)                      0x16FC SharePoint Server Search       HTTP Protocol
    Handler          du2z Verbose  CHttpProbeHelper::ProbeServer: Probing server with url 'http://pnvpr/_vti_bin/sitedata.asmx'.  [stscommon.cxx:476]  d:\office\source\search\native\gather\protocols\common\stscommon.cxx 
    07/30/2014 01:32:26.08  mssdmn.exe (0x15CC)                      0x193C SharePoint Server Search       PHSts                        
     dvb2 High     CSTS3Handler::CreateAccessorExD: Return error to caller, hr=80041200            [sts3handler.cxx:330]  d:\office\source\search\native\gather\protocols\sts3\sts3handler.cxx 
    07/30/2014 01:32:26.08  mssdmn.exe (0x15CC)                      0x16FC SharePoint Server Search       HTTP Protocol
    Handler          du4i Verbose  CHttpAccessorHelper::InitRequestInternal - opening request for '/_vti_bin/sitedata.asmx'.  [httpacchelper.cxx:353]  d:\office\source\search\native\gather\protocols\http\httpacchelper.cxx 
    earch application 'FAST Query SSA': Adding start address 'http://mnvfgext' for web application '64d562a1-535e-4917-8979-88840e2a67fe' to list of valid start addresses. a6b7948a-dc16-419d-b58a-0ee798a0bb9c
    07/30/2014 01:32:46.53  OWSTIMER.EXE (0x28DC)                    0x1444 SharePoint Server Search       Administration               
     dmb6 Verbose  Ensure full read access to the indexing account 'ABC\sp_search' on web application 'http://nvpr/'. a6b7948a-dc16-419d-b58a-0ee798a0bb9c
    07/30/2014 01:32:46.53  OWSTIMER.EXE (0x28DC)                    0x1444 SharePoint Server Search       Administration               
     dl2m Verbose  Search application 'FAST Query SSA': Skipping web application 'cea7b67b-fd5f-4c9a-a300-64a7d7ca3093' because its outbound url 'http://pnvpr' was automatically added once. a6b7948a-dc16-419d-b58a-0ee798a0bb9c
    07/30/2014 01:32:46.53  OWSTIMER.EXE (0x28DC)                    0x1444 SharePoint Server Search       Administration               
     dl2n Verbose  Search application 'FAST Query SSA': Adding start address 'http://pnvpr' for web application 'cea7b67b-fd5f-4c9a-a300-64a7d7ca3093' to list of valid start addresses. a6b7948a-dc16-419d-b58a-0ee798a0bb9c
    07/30/2014 01:32:46.53  OWSTIMER.EXE (0x28DC)                    0x1444 SharePoint Server Search       Administration               
     dl2k Verbose  web application 'http://abcrsp/' doesn't use search application 'FAST Query SSA', skipping it. a6b7948a-dc16-419d-b58a-0ee798a0bb9c
    07/30/2014 01:32:46.53  OWSTIMER.EXE (0x28DC)                    0x1444 SharePoint Server Search       Administration               
     dl2k Verbose  web application 'http://excb/' doesn't use search application 'FAST Query SSA', ski
    Anil Loka

    Hi,
    According to your post, my understanding is that you got error when communicating to the server.
    This happens when crawler is not able to connect to the server. Make sure server name is correct. Couple of steps to troubleshoot it
    You should be able to ping the server from the server having crawl component. Make sure there is an entry for the server in the host file under c:\Windows\System32\drivers\etc folder.
              Ping <servername>
          2.  You should be able to connect to the server using telnet command
    Telnet< servername> <port number>
    More information:
    Troubleshooting of FAST Search Configuration
    If the issue still exists, you can delete the old search application and recreate from the beginning.
    You can also reset the index and do a full crawl after.
    Here is a similar thread for your reference:
    http://social.technet.microsoft.com/Forums/en-US/f3c61b53-304a-4c2a-a370-d0e573219d1d/an-unrecognized-http-response-was-received-when-attempting-to-crawl-this-item?forum=sharepointadminprevious
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support

  • How do I get the full blown version of Mavericks download?

    Some of my best software has been made obsolete and I need to make a partitioned drive with Yosemite on one partition and Mavericks on the other. I can't find the full blown version anywhere. The downloads I have got require the version before...no good for me...I need the complete version of 10.9 so that I can then update to 10.9.5...from what I understand. Please help. Where can I find this software...I have exhausted my searches with no results. Anyone know a source? PLEASE? Thank YOU!

    Assuming you originally got Mavericks through your App Store account, open that and click on the Purchases tab. Mavericks will be listed there. Click the Download button. You will get the full 10.9.5 installer.

  • After upgrading to Yosemite, I had to upgrade my iPhoto, now the full res versions of my images cannot be found.

    After upgrading to Yosemite, I had to upgrade my iPhoto, now the full res versions of my images cannot be found.  I had created a book to print (before upgrade) but, after the upgrade the book can't be created as I get the message that images can't be found. However, if I search for the filename I can find the image. I tried repairing library as per support instructions but it hasn't helped. Any advice gratefully received. Thanks.

    Do the following:
    1 - launch iPhoto with the Command+Option keys held down to open the First Aid window. Be sure to follow the circled recommendation in the screenshot.
    2 - apply Option #4, Rebuild Database.

  • My iTunes background has gone gray and black. What did I do and how do I fix the issue?

    My iTunes background has gone gray and black. What did I do and how do I fix the issue?

    Had the same problem.  Go to Users/Library/Preferences.  Discard every file that begins with com.apple.iTunes...

  • Ok so I cant open my Itunes due to Windows Error 2 and the message says to uninstall and re-install Itunes but I'm pretty sure that would wipe the library right? Is there any way to fix the problem and keep my library?

    Ok so I cant open my Itunes due to Windows Error 2 and the message says to uninstall and re-install Itunes but I'm pretty sure that would wipe the library right? Is there any way to fix the problem and keep my library?

    Hi neffn!
    I have an article for you that can help you go through that process of uninstalling and reinstalling iTunes. If you have Windows 7, you will want to see this article:
    Removing and reinstalling iTunes, QuickTime, and other software components for Windows Vista or Windows 7
    http://support.apple.com/kb/ht1923
    and if you are using Windows XP, you will want to reference this article:
    Removing and Reinstalling iTunes, QuickTime, and other software components for Windows XP
    http://support.apple.com/kb/ht1925
    Note that, as it says in those articles:
    iTunes Store purchases or songs imported from CDs are saved in your My Music folder by default and are not deleted by removing iTunes. While it is highly unlikely that you will lose any contents of your iTunes Library when following these steps, it is always a good idea to ensure that your iTunes library is backed up. If you're unsure how to backup, see iTunes: Back up your iTunes library by copying to an external hard drive.
    Thanks for using the Apple Support Communities. Have a good one!
    -Braden

  • There is a problem with the photo with the filename "null". The full resolution version of this photo either cannot be located or is corrupt. Please replace this photo or delete it from your book.

    Absolutely INFURIATING.
    I have spent absolute hours building a photo album for the first year or my sons life. Sorting through quite literally thousands and thousands of images. Got a brilliant looking album using 177 of them.
    Now everytime I try to check out it won't get past page 1 of building the book.
    It says the following "There is a problem with the photo with the filename "null". The full resolution version of this photo either cannot be located or is corrupt. Please replace this photo or delete it from your book.".
    The images all look perfect. I have even tried taking them out and re adding the first page images from the library.
    Same problem.
    This is so annoying. So far I have NOT been happy with this iphoto application having nothing but problems with missing thumbnails. Corrupted images. Things that have never happened to me using a windows machine.

    Do the filenames contain special characters, like "ä,ü,..." or white space or are the vry long? Is there anything special about the image format? Try to export the edited versions in that case and reimport it with a different, shorter filename.
    For testing, create a new book with only the images you want to check.
    If this does not fix it, try rebuilding. Depress the option and command keys, launch iPhoto and rebuild the library.

  • HT1551 When using Airplay, the display on my tv isn't being fully used (its not taking up the full widescreen tv display). How do I fix that issue?

    When using Airplay, the display on my tv isn't being fully used (its not taking up the full widescreen tv display). How do I fix that issue?

    Intermittent issues will point to a local network/wifi issue.
    Reboot ATV and router, make sure both are up to date
    Try ethernet
    The home sharing connection will cut out if the iMac goes to sleep.

Maybe you are looking for