locked
the application failed to initialize propertly(0x80000003). click on OK to terminate the application RRS feed

  • Question

  • hello to all
    i succeeded compile all project with vs2005 pro.
    but when i try to run the app from "app folder" it gave me error mesagge:
    the application failed to initialize propertly(0x80000003). click on OK to terminate the application
    this error cam after i chang back the manifest to YES on all project.
    (the reason it was on NO, is that the app will run with non vs2005 environment. but i show her beter solution)
    it look like dll problam but i did take the dlls from winsxs "WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_dec6ddd2" AND
    "\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd"

    HOPE anyone has know thi error situation
    thank
    Wednesday, November 23, 2005 4:07 PM

Answers

  • no i didn't but i did forget to change one project from NO to YES.
    look like it pass the manifest situation, i hope it will run on non vs2005 with this solution http://blogs.msdn.com/nikolad/archive/2005/03/18/398720.aspx

    thank Paz
    Wednesday, November 23, 2005 5:25 PM
  • Take a look at http://msdn2.microsoft.com/en-us/library/ms235624.aspx.

    Hope this is helpful!

    Thanks,
      Ayman Shoukry
      VC++ Team
    Wednesday, November 23, 2005 6:02 PM
  • I have just gone through this myself.  The application needs to be able to find both ATL80.DLL itself, and its matching manifest file.  There is no other way to solve this problem (ATL80.DLL will refuse to load without a manifest).

    So either those two files need to be in the current directory, or they need to be installed under the WinSXS/Manifests directory.
    Saturday, November 26, 2005 11:08 AM
  • If you are simply looking for a quick and easy way to install the VS2005 dll's on your other machine you can run vcredist_x86.exe found under your VS2005 install dir at SDK\v2.0\BootStrapper\Packages\vcredist_x86 on the target machine to install the release (you should only run in release on non dev machines) .DLLs in the Windows Side by Side for use by your application.  However, if you are looking to redistribute your application to others, you should better understand the concepts and choose the appropriate option from http://msdn2.microsoft.com/en-us/library/ms235299.aspx.

    Basically, the VS dlls will not load if they are not installed in the Side by Side cache because this allows future servicing of the DLLs if, for instance, a security hole is discovered.  Since the only way to use the DLLs is from SxS, future releases need only install themselves in SxS and set the appropriate rules for which version to load. 

    Hopefully this helps,

    Ben

    Wednesday, November 30, 2005 2:49 AM

All replies

  • Did you move such dlls from the SxS directory?

    Thanks,
      Ayman Shoukry
      VC++ Team
    Wednesday, November 23, 2005 4:33 PM
  • no i didn't but i did forget to change one project from NO to YES.
    look like it pass the manifest situation, i hope it will run on non vs2005 with this solution http://blogs.msdn.com/nikolad/archive/2005/03/18/398720.aspx

    thank Paz
    Wednesday, November 23, 2005 5:25 PM
  • Yes, Nikola's blog should be very helpful!

    Thanks,
      Ayman Shoukry
      VC++ Team
    Wednesday, November 23, 2005 5:27 PM
  • dear all
    after changing back manifest to yes still cant run on non vs 2005
    the computer i am try to run the app on has:
    1. net framework2 (has the compiler has) 2. all dll that need by dependency wallker (mfc/d, msvcm/d, msvcr/d, msvcp/d)
    3. I copy the manifest dll has describe on the link above.

    and now i back to error message "This application has failed to start because the application configuration is incorrect"

    i don't want to give up manifest tools

    thank all Paz

    Wednesday, November 23, 2005 5:59 PM
  • Take a look at http://msdn2.microsoft.com/en-us/library/ms235624.aspx.

    Hope this is helpful!

    Thanks,
      Ayman Shoukry
      VC++ Team
    Wednesday, November 23, 2005 6:02 PM
  • i read but i didnt find any solution, what i did see is something about "private assemblies". did you mean to this ? and if you did, please, how can i use it ?
    i am dilling with this to for long time and still get error message

    Thanks Paz
    Thursday, November 24, 2005 4:50 PM
  • I have just gone through this myself.  The application needs to be able to find both ATL80.DLL itself, and its matching manifest file.  There is no other way to solve this problem (ATL80.DLL will refuse to load without a manifest).

    So either those two files need to be in the current directory, or they need to be installed under the WinSXS/Manifests directory.
    Saturday, November 26, 2005 11:08 AM
  • If you are simply looking for a quick and easy way to install the VS2005 dll's on your other machine you can run vcredist_x86.exe found under your VS2005 install dir at SDK\v2.0\BootStrapper\Packages\vcredist_x86 on the target machine to install the release (you should only run in release on non dev machines) .DLLs in the Windows Side by Side for use by your application.  However, if you are looking to redistribute your application to others, you should better understand the concepts and choose the appropriate option from http://msdn2.microsoft.com/en-us/library/ms235299.aspx.

    Basically, the VS dlls will not load if they are not installed in the Side by Side cache because this allows future servicing of the DLLs if, for instance, a security hole is discovered.  Since the only way to use the DLLs is from SxS, future releases need only install themselves in SxS and set the appropriate rules for which version to load. 

    Hopefully this helps,

    Ben

    Wednesday, November 30, 2005 2:49 AM
  • i am getting the same error message when i try to start outlook 2007. does anyone know the way to fix this?

     

    Wednesday, April 18, 2007 5:14 AM
  • I am also having the same problem when I use outlook. The process repeats even if I reinstall again and again and the other Office software just don't work properly too after that . Unfortunately I cannot find any solution on the web. Please help. Thanks.
    Thursday, June 14, 2007 10:05 PM
  • Hello

    I've solve thi issue , it toke me 3 days.

    1. First copy RTFHTML.dll to system32 folder in windows directory.

    2 Make shure thet 'outlook.exe.manifest' exists in 'Office12' folder. If not copy manifest file from access (access.exe.manifest) or any other office12 program  and chane it name to outlook.exe.manifest.

    3. Run outlook, It should run and configure. When it finish, if it ask you to run computer agein click no. (Outlook shoud run additional instaler. Wait again. ) Now outllook it's running.

    4. While outlook is running go to register. (regedit) find a key:  

    HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Setup

    find the binary data:

    'First-Run'

    and clear all values to '0'

    "First-Run"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

     

    5.Now close outlook. It shoud be working now.

    Smile

     

    • Proposed as answer by Sandip Karia Monday, March 19, 2012 7:04 AM
    Sunday, July 15, 2007 8:37 AM
  • thanks for the help but i went through all of that and as soon as i started outlook again it tried to configure itself again and now i am back at stage one again with that error message popping up again. what have i done wrong
    Wednesday, July 18, 2007 2:32 AM
  • For problems with Office software I'd suggest for you to post on an Office forum so you can get better help.

     

    Its one thing to get this message when testing an application you're developing and quite another thing if you get it when running a Microsoft or 3rd party installed product. I can't give you any more help than the 'uninstall/reinstall' that you've already tried. Also, this message is pretty generic, just because a registry change fixes the problem for one person doens't mean that everyone who has this error should start hacking on their registry.

    Saturday, August 11, 2007 12:19 AM
  • i've got a small question it could be its allready somewhere up here, but i just can't find the solution. When i (try to) open my msn live messenger it allways gives me the error:

    the application failed to initialize properly (0x80000003). Click on ok to terminate the application.

    How do i get rid of this problem i' ve been searching for ages right now and i still didn't find a solution, could someone help me please

    and just de-instaling and re-instaling isn't a solution Tongue Tied

     

    thanks Stijn

     

    Saturday, January 19, 2008 1:30 PM
  • This works for me. Thanks.

    I suspect that it got corrupted when I tried to uninstall Visio 2010 from my machine using some third party tool (as it was giving error in uninstall). That impact outlook 2007 also.

    Monday, March 19, 2012 7:04 AM