Why does fatal error "LNK1104: cannot open file 'C:\Program.obj'" occur when I compile a C++ project in Visual Studio?

Visual C++Linker

Visual C++ Problem Overview

I've created a new C++ project in Visual Studio 2008. No code has been written yet; Only project settings have been changed.

When I compile the project, I receive the following fatal error:

> fatal error LNK1104: cannot open file 'C:\Program.obj'

Visual C++ Solutions

Solution 1 - Visual C++

This particular issue is caused by specifying a dependency to a lib file that had spaces in its path. The path needs to be surrounded by quotes for the project to compile correctly.

On the Configuration Properties -> Linker -> Input tab of the project’s properties, there is an Additional Dependencies property. This issue was fixed by adding the quotes. For example, changing this property from:

> C:\Program Files\sofware > sdk\lib\library.lib

To:

> "C:\Program Files\sofware > sdk\lib\library.lib"

where I added the quotes.

Solution 2 - Visual C++

This can happen if the file is still running as well.

> :-1: error: LNK1104: cannot open file 'debug\****.exe'

Solution 3 - Visual C++

The problem went away for me after closing and re-opening Visual Studio. Not sure why the problem happened, but that might be worth a shot.

This was on VS 2013 Ultimate, Windows 8.1.

Solution 4 - Visual C++

Check also that you don't have this turned on: Configuration Properties -> C/C++ -> Preprocessor -> Preprocess to a File.

Solution 5 - Visual C++

My problem was a missing .lib extension, I was just linking against mylib and VS decided to look for mylib.obj.

Solution 6 - Visual C++

I had the same problem.It caused by a "," in the name of a folder of additional library path.It solved by changing the additional library path.

Solution 7 - Visual C++

Solution 1 (for my case): restart windows Explorer process (yes, the windows file manager).

Solution 2:

  1. Close Visual Studio. Windows Logoff
  2. Logon, reopen Visual Studio
  3. Build as usual. It now builds and can access the problematic file.

I presume sometimes the file system or whoever is controlling it gets lost with its permissions. Before restarting the windows session, tried to kill zombie msbuild32.exe processes, restart visual studio, check none even showing the problem file on. No build configuration issues. It happens now and then. Some internal thing in Windows does not fix up, needs a restart.

Solution 8 - Visual C++

In my case it was a matter of a mis-directed reference. Project referenced the output of another project but the latter did not output the file where the former was looking for.

Solution 9 - Visual C++

I had the same error, just with a Nuget package i had installed (one that is not header only) and then tried to uninstall.
What was wrong for me was that i was still including a header for the package i just uninstalled in one of my .cpp files (pretty silly, yes).
I even removed the additional library directories link to it in Project -> Properties -> Linker -> General, but of course to no avail since i was still trying to reference the non-existent header.

Definitely a confusing error message in this case, since the header name was <boost/filesystem.hpp> but the error gave me "cannot open file 'llibboost_filesystem-vc140-mt-gd-1_59.lib'" and no line numbers or anything.

Solution 10 - Visual C++

I had the same problem, but solution for my case is not listed in answers. My antivirus program (AVG) determined file MyProg.exe as a virus and put it into the 'virus storehouse'. You need to check this storehouse and if file is there - then just restore it. It helped me out.

Solution 11 - Visual C++

For an assembly project (ProjectName -> Build Dependencies -> Build Customizations -> masm (selected)), setting Generate Preprocessed Source Listing to True caused the problem for me too, clearing the setting fixed it. VS2013 here.

Solution 12 - Visual C++

I run into the same problem with linker complaining about the main executable missing. This happened during our solution port to the new Visual Studio 2013. The solution is a varied mix of managed and un-managed projects/code. The problem (and fix) ended up being a missing app.config file in the solution folder. Took a day to figure this one out :(, as output log was not very helpful.

Solution 13 - Visual C++

I checked all my settings according to this list: http://msdn.microsoft.com/en-us/library/ts7eyw4s.aspx#feedback . It is helpful to me and for my situation, I find out that Link Dependency of projects' properties has double-quote, which should not be there.

Solution 14 - Visual C++

in my case it was the path lenght (incl. file name).

..\..\..\..\..\..\..\SWX\Binary\VS2008\Output\Win32\Debug\boost_unit_test_framework-vc90-mt-gd-1_57.lib;

as for the release the path was (this has worked correctly):

..\..\..\..\..\..\..\SWX\Binary\VS2008\Output\Win32\Release\boost_unit_test_framework-vc90-mt-1_57.lib;

==> one char shorter.

  1. i have also verified this by renaming the lib file (using shorter name) and changing this in the

Linker -> input -> additoinal dependencies

  1. i have also verified this by adding absolut path instead of relative path as all those ".." has extended the path string, too. this has also worked.

so the problem for me was the total size of the path + filename string was too long!

Solution 15 - Visual C++

I'm answering because I don't see this particular solution listed by anyone else.

Apparently my antivirus (Ad-Aware) was flagging a DLL one of my projects depends on, and deleting it. Even after excluding the directory where the DLL lives, the same behaviour continued until I restarted my computer.

Solution 16 - Visual C++

In my case, I had replaced math library files from a previous Game Engine Graphics course with GLM. The problem was that I didn't add them to the project within Visual Studio's Solution Explorer (even though they were in the project repository).

Solution 17 - Visual C++

I had this issue in conjunction with the LNK2038 error, followed this post to segregate the RELEASE and the DEBUG DLLs. In this process I had cleaned up the whole folder where these dependencies were residing.

Luckily I had a backup of all these files, and got the file for which this error was throwing back into the DEBUG folder to resolve the issue. The error code was misleading in some way as I had to spend a lot of time to come to this tip from one of the answers from this post again.

Hope this answer, helps someone in need.

Solution 18 - Visual C++

I solved it by adding an existing project to my solution, which I forgot to add in the first time.

Solution 19 - Visual C++

I had the same error:

fatal error LNK1104: cannot open file 'GTest.lib;'

This was caused by the ; at the end. If you have multiple libraries, they should be separated by empty space (spacebar), no comma or semi-colons!

So don't use ; or any anything else when listing libraries in Project properties >> Configuration Properties >> Linker >> Input

Solution 20 - Visual C++

I tried above solution but didnt work for me. So i rename the exe and rebuild the solution. It works for me.

Solution 21 - Visual C++

I had this exact error when building a VC++ DLL in Visual Studio 2019:

> LNK1104: cannot open file 'C:\Program.obj'

Turned out under project Properties > Linker > Input > Module Definition File, I had specified a def file that had an unmatched double-quote at the end of the filename. Deleting the unmatched double quote resolved the issue.

Solution 22 - Visual C++

Killed msbuild32.exe and built again. It worked for me.

Solution 23 - Visual C++

My issue was caused by other application using the .dll file I was trying to debug.

Closing the application that was using the .dll solved it for me.

Solution 24 - Visual C++

Possible solutions:

  1. Check if path contain any white spaces, Go to Properties > Linker > Input > additional path and include "path with white space"

  2. If program are still running, close everything and restart.

  3. Check if .obj file is not created. This happens when you directly build a project while Properties > C++ > Preprocessor > Generate preprocessor file is on. Turn it off and build the project then you can onn Properties > C++ > Preprocessor > Generate preprocessor file.

Solution 25 - Visual C++

I had a similar problem. I solved it with the following command to kill the running task:

> taskkill /f /im [nameOfExe]

/f: Forces the task to close. /im: The next parameter is a image name aka executable name e.g. Program.exe.

Solution 26 - Visual C++

I hit the same problem with "Visual Studio 2013".

LNK1104: cannot open file 'debug\****.exe

It resolved after closing and re-starting Visual studio.

Solution 27 - Visual C++

I was having the same problem , I have just copied the code to new project and started the build . Some other error started coming. error C4996: 'fopen': This function or variable may be unsafe. Consider using fopen_s instead

To solve this problem again, I have added my one property in the Project project as below. Project -> Properties -> Configuration property -> c/c++ . In this category there is field name Preprocessor Definitions I have added _CRT_SECURE_NO_WARNINGS this to solve the problem Hope it will help ...

Thank You

Categories
Recommended Visual C++ Solutions
Recommended Linker Solutions

Previous Solution:

How do I create a WPF Rounded Corner container?

WpfRounded Corners

Next Solution:

How to make a cross-module variable?

PythonModuleGlobal

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionJosh SklareView Question on Stackoverflow
Solution 1 - Visual C++Josh SklareView Answer on Stackoverflow
Solution 2 - Visual C++CarolView Answer on Stackoverflow
Solution 3 - Visual C++Daniel NeelView Answer on Stackoverflow
Solution 4 - Visual C++Assaf LevyView Answer on Stackoverflow
Solution 5 - Visual C++Patrizio BertoniView Answer on Stackoverflow
Solution 6 - Visual C++harsiniView Answer on Stackoverflow
Solution 7 - Visual C++LissandroView Answer on Stackoverflow
Solution 8 - Visual C++NewtopianView Answer on Stackoverflow
Solution 9 - Visual C++MatthiasView Answer on Stackoverflow
Solution 10 - Visual C++Nazarii PlebanskiiView Answer on Stackoverflow
Solution 11 - Visual C++MadeOfAirView Answer on Stackoverflow
Solution 12 - Visual C++Nicko PoView Answer on Stackoverflow
Solution 13 - Visual C++DavidView Answer on Stackoverflow
Solution 14 - Visual C++Alfred MeierView Answer on Stackoverflow
Solution 15 - Visual C++easuterView Answer on Stackoverflow
Solution 16 - Visual C++Artorias2718View Answer on Stackoverflow
Solution 17 - Visual C++N00b Pr0grammerView Answer on Stackoverflow
Solution 18 - Visual C++Markus WeberView Answer on Stackoverflow
Solution 19 - Visual C++zarView Answer on Stackoverflow
Solution 20 - Visual C++user3500315View Answer on Stackoverflow
Solution 21 - Visual C++MikeOnlineView Answer on Stackoverflow
Solution 22 - Visual C++ImadView Answer on Stackoverflow
Solution 23 - Visual C++NAGAView Answer on Stackoverflow
Solution 24 - Visual C++Faizanur RahmanView Answer on Stackoverflow
Solution 25 - Visual C++MarciView Answer on Stackoverflow
Solution 26 - Visual C++user3860869View Answer on Stackoverflow
Solution 27 - Visual C++SunilView Answer on Stackoverflow