So the program works perfect fine, runs without errors, etc during a build/run in the IDE but when I move to the Installshield Install and attempt to install it all files appear to install but the program doesn't load any kind of display. I can see that the program is open when I do a ctrl+alt+del and go to task manager but it doesn't appear to be running any other way. I don't receive any kind of errors and I'm unsure of how else to check what's going on here. While building the projects the only indicator of a problem is the following warning which has been around since I've started my project it seems and previous builds of the install have worked
Warning: 2>ISEXP : warning : -7235: InstallShield could not create the software identification tag because the Tag Creator ID setting in the General Information view is empty.
Also during build of the program I get these:
1>SOIL.lib(image_DXT.obj) : warning LNK4099: PDB 'vc120.pdb' was not found with 'SOIL.lib(image_DXT.obj)' or at 'C:\Users\Daddy\Downloads\3 Jul 2016\Final New AI\Final\Battleship\Debug\vc120.pdb'; linking object as if no debug info
1>SOIL.lib(image_helper.obj) : warning LNK4099: PDB 'vc120.pdb' was not found with 'SOIL.lib(image_helper.obj)' or at 'C:\Users\Daddy\Downloads\3 Jul 2016\Final New AI\Final\Battleship\Debug\vc120.pdb'; linking object as if no debug info
1>SOIL.lib(SOIL.obj) : warning LNK4099: PDB 'vc120.pdb' was not found with 'SOIL.lib(SOIL.obj)' or at 'C:\Users\Daddy\Downloads\3 Jul 2016\Final New AI\Final\Battleship\Debug\vc120.pdb'; linking object as if no debug info
1>SOIL.lib(stb_image_aug.obj) : warning LNK4099: PDB 'vc120.pdb' was not found with 'SOIL.lib(stb_image_aug.obj)' or at 'C:\Users\Daddy\Downloads\3 Jul 2016\Final New AI\Final\Battleship\Debug\vc120.pdb'; linking object as if no debug info
Not sure if that means anything though. The vc120.pdb is located in the debug folder of the project.
If a program does not work once deployed to a fresh machine, then something is missing in the deployment. One of the more common cases is a missing dependency DLL, either one of your own, or something from a third party. However this often results in an error message when attempting to run your executable, so if your scenario is a missing dependency, it's a softer dependency than the typical static link dependency. So, rather than being told by Windows, you need to dive in to figure out what isn't there.
You will probably need to debug into the running but headless behavior of your app. Try a tool like Process Monitor to identify relevant missing files, registry? Or get a developer of the app to help if you're not a developer yourself; they may know better what missing dependencies would result in this behavior. Is it missing a registry key or configuration file? Is it missing a dynamically loaded DLL? Does it log anything, or can it be configured to do so? Can you figure out what it's doing by grabbing your PDBs and attaching with WinDbg? Can it be modified to log or to issue errors in these or similar scenarios so you can better debug deployment problems?
Once you identify what's missing, you can configure the installation to deploy those items as well.
Related
I'm receiving the message below when I attempt to start the Local Windows Debugger on this project in Visual Studio 2022 . I had some earlier challenges adding and linking the additional include libraries and files for MySql as well as some earlier notifications about missing .dll files. I thought these were resolved since I was able to successfully build. What do I need to check to start trying to fix this? Let me know if any additional information is needed.
I was able to resolve the issue by re-writing the project from scratch on my laptop, starting with an empty C++ project. In the course of doing that, I did run into some of the same messages regarding missing .dll files. This was resolved by copying and pasting these into the appropriate /debug folder for the project directory. As suggested, I did implement the scan for corrupt files, which fortunately did not turn up any issues. Once this was completed, I achieved a successful build and execution of the program.
When running my Visual Studio C++ application debug version through VS2010 by Project Only > ProjectName the generated exe runs well. However when I generate a release version and go to the folder where the exe is created I get the following error:
The application was unable to start correctly (0xc000007b). Click Ok to close the application
The files in the folder is only the exe file whereas my project uses various boost libraries.
Is it possible that its giving this message because of the missing boost dlls ? Is there a way to make the compiler paste all the necessary dlls in the exe folder.
Is there any way to launch the release version from VS2010 like we have for the debug version as in Debug >> Start new instance
I hate when that happens. It could be the fact that its missing the bloost DLL's: the easiest way to fix this is to add the folder to the Path environment variable. Sadly enough, we don't have enough information from your post to confirm that this is the problem. Common other problems include: you are linking to libraries that were built for a different architecture/are using a different runtime library, you are missing other 3rd party dlls, the .lib file you used in the linker is pointing to a different version of the code than the dll you are pointing to...the list goes on.
As for copying the dlls at runtime, you can do this using the custom build events [http://msdn.microsoft.com/en-us/library/e85wte0k%28v=vs.80%29.aspx]. Just write a batch script that copies the dlls as a "Post Build Event" and you should be good to go, but I'd suggest the Path way first.
I'm writing a game (with Angel engine) in Visual C++ Express 2010, and even after commenting out everything in main, the program crashes on startup (the application was unable to start correctly). This started happening after installing VS2012. I have tried restarting, rebuilding, using Release and Debug, running VS as Administrator etc.
Initially I had to put this into the Post-Build Event Command Line to get it to compile:
#echo off
echo Copying $(OutDir)$(TargetName)$(TargetExt) as $(TargetName)D$(TargetExt)
copy /Y $(OutDir)$(TargetName)$(TargetExt) $(OutDir)$(TargetName)D$(TargetExt)
It used to not find the PDB files correctly, but I turned on Microsoft Symbol Servers for the .pdb locations and gave it a cache directory. Now, the Debug output says:
'ClientGame.exe': Loaded 'C:\Windows\SysWOW64\ntdll.dll', Symbols loaded (source information stripped).
with about 20 different dlls, most of which looking like standard windows things, and opengl. A few don't have "source information stripped" after them. A few say this:
'ClientGame.exe': Loaded 'C:\Windows\SysWOW64\devil.dll', Binary was not built with debug information
In Solution output, I get:
directorytoproject\Libraries\libogg- 1.3.0\win32\VS2008\libogg_static.vcxproj : warning : Platform 'x64' referenced in the project file '_libogg' cannot be found. Please make sure you have it installed under '%VCTargetsPath%\Platforms\x64'.
with a couple of other libraries as well.
Runtime library setting is on "Multi-threaded Debug DLL (/MDd)"
I would really appreciate any ideas! Thanks a lot!
I've recently downloaded Assimp and I've run into some troubles.
I've linked the libraries and I can get the program to compile and it runs fine in Release mode; however, the Debug .exe hits me with this error:
The application was unable to start correctly (0xc0150002). Click OK to close the application.
Some more details:
I'm using VS2010 with Target Machine set to x86.
I am using the 32bit debug dll (Assimp32d.dll) that was provided, and I've tried setting runtime libraries to /MT, /MTd, /MD, and /MDd with no luck.
I read from other similar threads that I should run Dependency Walker on the .exe, but I'm not sure what the output means. I'll paste it here if this helps you guys.
Error: The Side-by-Side configuration information for "c:\users\-----\documents\visual studio 2010\projects\AssimpTest\debug\ASSIMP32D.DLL" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail (14001).
Error: At least one required implicit or forwarded dependency was not found.
Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Rather than rebuilding the libraries, I downloaded a different set of libraries (it was the SDK installer) and the debug dll's from that are working perfectly.
Just in case anyone has the same problem with the same software, this was the exact name of the installer that worked for me: assimp-sdk-3.0-setup.exe
I ran into the same problem when trying to run a 64-bit project in Debug mode when using Assimp 3.0.
What I did was go to assimp/workspaces/vc9, open assimp.sln in Visual Studio 10, convert the project, then rebuild the 32 and 64-bit dll.
Mind you, you've got to install boost for that as well, and edit the project properties so it points to the boost directory for includes.
There's probably a way to do it using CMake as well, but I found the whole process too cumbersome to bother with in the first place.
My solution was just to link the debug build to the release .dll files. No more issues, and I wasn't that interested in debugging the Assimp library anyway!
I faced the same issue, later on I downloaded the "assimp-sdk-3.0-setup.exe" file & installed it as a standard windows application.
I pointed Visual Studio Solution Include & Lib directories to respective folders from newly installed location, copied DLL to my application location. The problem was resolved. Hope this helps someone.
Cheers.
I need to compile a code in C++ which has some OpenCV functions and does a kind of test. The fact is that the code has worked in other computers, I just need to set the includes and libraries properly to make it work on my PC.
I get this strange error in release mode when building.
Error: general error c101008d: Failed to write the updated manifest to the resource of file ".\bin\pcTest.exe". The process cannot access the file because it is being used by another process. mt.exe
I found other answers that say mt.exe has to do with the antivirus, or something like that. Anybody knows why is this happening or how can I solve it?
Is the .exe file there when you look for it? If so, check whether something else is locking it using LockHunter (http://lockhunter.com). The only time I've had this error is when I've already been running the program and then tried to build it again -- make sure that's not what's happening :)
I get this error when I try to output the debug version of an executable into a directory that exists in my C:/Program Files (x86) directory. This is a Visual Studio project property I set. (Right click project | Properties | General | Output Directory).
I fixed this issue by temporarily disabling Symantec Endpoint Protection. If your privs don't allow you to do that, you can try outputting the executable somewhere else then copy/pasting it into the desired directory.