LNK1105 when CPP module is referenced

[Scott]

I am consistently getting
LINK : fatal error LNK1105: cannot close file
'C:\Code3\JusticeLinkCommon\Debug\JLTranSvcWrapper.dll'

whenever I compile this program.

I finally chased this down to a C# program in the same solution using the
JLTranSvcWrapper project as a reference. This is something I thought I did
all the time.

The wrapper project is a managed CPP dll program that is used as a general
DCOM wrapper class for C# and VB programs.

This seems to have started after applying some recent Microsoft system
updates, but which one is impossible to determine.

Does anyone have any way of getting around this?
--
Scott

[Charles Wang [MSFT]]

Hi Scott,
From this article,
http://msdn.microsoft.com/en-us/library/80z106bx(VS.80).aspx, we can find
that this error can be caused if there was insufficient disk space
available. I recommend that you first check your disk space to see if this
is the problem.

If not, I would like to know:
Did you use incremental link for a large project?

Based on my research, there is a known issue that had been reported to
Microsoft:
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedbac
kID=206512

I found that we had a hotfix for this issue internally, however I have not
found a published KB article for clarification. I am trying to contact the
related developer to confirm this and will update you later. Sorry for
bringing you any inconvenience.

In addition, from your description, it seemed that this issue did not occur
before but that it raised until a recent Windows update, right? Could you
please also confirm with me whether you can reproduce this issue on other
machine?

Look forward to your response. If you have any other questions or concerns,
please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msd...@microsoft.com.
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================

[Scott]

I am really suspecting that at some point something changed in the solution
file for this project. It is not a very large solution just 17 projects, that
are a mix of C# and CPP, 32 and 64 bit, with 3 of these are exe projects (CPP
and C# for testing ) the rest are class dlls.

I have removed and recreated the project, that has the problem, in two
different solutions and the symptoms are the same. The symptoms are also
consistent, I can remove the project reference from the exe and everything
compiles. Put the reference back and it fails.

So to test I need to remove the reference in my test program (in the same
solution), compile my changes, put the reference back in the exe test program
and then recompile that program also. Then everything executes as (I think)
it should.

I am only suspecting a windows update, as far as I can remember this started
after windows update requested a reboot. But any number of other things could
have happened as well. I don't have the time to remove the last windows
updates, one at a time to see if the problem disappears.

Again, the only time I have seen this is in this solution where the test
program is a C# and the DLL is a CPP (DCOM Client) class. I use this for
testing both 32 and 64 bit implementations on my Vista 64 bit machine.
--
Scott

[Scott]

I moved the entire solution to a XP machine (32 bit) that has VS2008 and it
compiles clean.

The other thing that I thought was interesting. I added a file copy to the
project of the CPP DLL (post build) to copy the dll to another location and
then changed the test exe to get the reference from that location, and I got
the same results. This makes no sense to me at all!
--
Scott

[Charles Wang [MSFT]]

Hi Scott,
Thank you for your response.

Did you mean that:
If you first built your CPP DLL project to produce the DLL and then
directly copied the CPP DLL to a separate project (maybe C# or VC++.NET)
and if you referenced the DLL in the project, when you compiled the
project, you encountered the error?

If so, could you please mail me (changliw_at_microsoft_dot_com) the CPP DLL
and your test project so that I can reproduce this issue at my side?

Thank you for your cooperation.

Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================

Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msd...@microsoft.com.
=========================================================

[Wynn]

Charles,

I have the same fatal error but on a completely empty application. To see
what might be the underlying issue, I created a new Forms project. It
compiled with no issues.

I added a menu strip and compiled, and I added a status strip and rebuilt.
At each step, there were no issues.

Then I pulled a toolbar strip from the Toolbox (same method used on the menu
and status strips). This time, I got the fatal error...
1>LINK : fatal error LNK1105: cannot close file (my file name)

In trying to remedy the link-time error, I deleted the toolbar strip. It
didn't help. I removed the status and menu strips, but your linker continued
to dislike my application.

After I first got the link-time error, the only solution that I can find is
to remove the project completely and create another from scratch. This
solution works until I do something to cause the link-time error.

[Charles Wang [MSFT]]

Hi Wynn,
Could you please have a new post at the community so that we can assist you
and monitor the issue more dedicatedly?

Currently I recommend that you check if your DLL file is read-only, if so,
change it to read-write to see if it helps.

[usenet...@gmail.com]

I started getting this exact same problem just yesterday, but with an
old C++ project which has existed for years. I thought at first the
problem was related to the fact that I started using VS2005 SP1 under
Vista (Enterprise) SP1 just a week ago, however after digging around I
see that there are some suggestions that the problem began after
installing recent updates.

As it happens a whole *bunch* of updates were automatically installed
on my machine early yesterday afternoon, and the link problem started
shortly afterwards. I have no idea which update is causing the
problem, however I *can* list exactly which updates that were applied:

Security Update for Microsoft Windows (KB948590)
Security Update for Microsoft Windows (KB950759)
Security Update for Microsoft Windows (KB950760)
Security Update for Microsoft Windows (KB950762)
Security Update for Microsoft Windows (KB951376)
Security Update for Microsoft Windows (KB951698)
Update for Microsoft Windows (KB938371)
Security Update for Microsoft Windows (KB941693)
2007 Microsoft Office Suite Service Pack 1 (SP1)
Security Update for Excel 2007 (KB946974)
Security Update for Microsoft Office Publisher 2007 (KB950114)
Security Update for Microsoft Office system 2007 (KB951808)
Security Update for Microsoft Office Word 2007 (KB950113)
Security Update for Office 2007 (KB947801)
Update for Office 2007 (KB946691)
Update for Outlook 2007 Junk Email Filter (kb950378)

Now, determining WHICH update(s) have caused this problem is another
matter. Looks like I'll just have to start removing them and see what
happens...

John

On 11 Jun, 15:41, Scott <snorb...@newsgroups.nospam> wrote:
> I am consistently getting

> LINK : fatal errorLNK1105: cannot close file

[Ovdiienko@discussions.microsoft.com Dmytro Ovdiienko]

Hello, Charles

Did you find hotfix?

[Charles Wang [MSFT]]

Hi,
Thank you for your interesting. Scott opened a case at CSS, however the root cause has not been
found yet.

Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================

Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msd...@microsoft.com.
=========================================================

[Dmytro Ovdiienko]

Hi Charles,

Not so far you woute that you found hotfix without KB article. Does this hot
fix not solve problem?
What is CSS mean?

[Charles Wang [MSFT]]

Hi,
CSS refers to Microsoft Customer Support Services. Based on the case history, the original hotfix seemed not resolving Scott's issue and the issue was still being observed.

For contacting CSS, you can obtain the phone numbers for specific technology request at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see http://support.microsoft.com for regional support phone numbers. Please be advised that the call will be charged.