Linker error Help!

[Jon Pope]

For the last six months, I've been able to compile my C# solution in VS2003.
Suddenly this morning I get the following error:

"Satellite build for culture 'fr' failed. The assembly linker could not be
launched. The system cannot find the file specified."

I've deleted my entire folder structure, and recreated from VSS. I've
deleted the contents of my temp folder. I've looked online for solutions.
All to no avail.

What am I doing wrong?

Cheers, Jon

[John Puopolo]

Hi...

I've seen this behaviour once I installed VS.NET 2005 Beta. Do you have
this on your machine? It even impact MS Word and PowerPoint, I noticed. I
solved the problem by going into Word and making sure my language was
explicitly set to English for everything.

John
"Jon Pope" <jo******@healthlinkinc.com> wrote in message
news:O9**************@TK2MSFTNGP14.phx.gbl...

For the last six months, I've been able to compile my C# solution in VS2003. Suddenly this morning I get the following error:

"Satellite build for culture 'fr' failed. The assembly linker could not be launched. The system cannot find the file specified."

I've deleted my entire folder structure, and recreated from VSS. I've
deleted the contents of my temp folder. I've looked online for solutions.
All to no avail.

What am I doing wrong?

Cheers, Jon

[Jon Pope]

John,
Thanks for the reply. The machine on which I'm having these problems is a
dedicated build machine. We use it to perform regular QA builds for our
products. It's only got VS.NET 2002 & 2003 installed on it. No MS Office
of any sort. Like I said, I've been successfully building on this machine
for 6+ months, but suddenly today that's stopped.

Cheers, Jon

"John Puopolo" <jo**********@fastsearch.com.nospam> wrote in message
news:eS**************@TK2MSFTNGP09.phx.gbl...

Hi...

I've seen this behaviour once I installed VS.NET 2005 Beta. Do you have
this on your machine? It even impact MS Word and PowerPoint, I noticed.
I
solved the problem by going into Word and making sure my language was
explicitly set to English for everything.

John
"Jon Pope" <jo******@healthlinkinc.com> wrote in message
news:O9**************@TK2MSFTNGP14.phx.gbl...

For the last six months, I've been able to compile my C# solution in

VS2003.

Suddenly this morning I get the following error:

"Satellite build for culture 'fr' failed. The assembly linker could not

be

launched. The system cannot find the file specified."

I've deleted my entire folder structure, and recreated from VSS. I've
deleted the contents of my temp folder. I've looked online for
solutions.
All to no avail.

What am I doing wrong?

Cheers, Jon

[Jon Pope]

John,
Thanks for the reply. The machine on which I'm having these problems is a
dedicated build machine. We use it to perform regular QA builds for our
products. It's only got VS.NET 2002 & 2003 installed on it. No MS Office
of any sort. Like I said, I've been successfully building on this machine
for 6+ months, but suddenly today that's stopped.

Cheers, Jon

"John Puopolo" <jo**********@fastsearch.com.nospam> wrote in message
news:eS**************@TK2MSFTNGP09.phx.gbl...

Hi...

I've seen this behaviour once I installed VS.NET 2005 Beta. Do you have
this on your machine? It even impact MS Word and PowerPoint, I noticed.
I
solved the problem by going into Word and making sure my language was
explicitly set to English for everything.

John
"Jon Pope" <jo******@healthlinkinc.com> wrote in message
news:O9**************@TK2MSFTNGP14.phx.gbl...

For the last six months, I've been able to compile my C# solution in

VS2003.

Suddenly this morning I get the following error:

"Satellite build for culture 'fr' failed. The assembly linker could not

be

launched. The system cannot find the file specified."

I've deleted my entire folder structure, and recreated from VSS. I've
deleted the contents of my temp folder. I've looked online for
solutions.
All to no avail.

What am I doing wrong?

Cheers, Jon

[John Hazell via DotNetMonster.com]

I just installed XP Service Pack 2 and some updates... I am now also
experiencing this odd behavior. I may try to uninstall the updates if I
can't find another resolution.

--
Message posted via http://www.dotnetmonster.com