Error Installing .Net Framework 2.0

I'm trying to install the .Net Framework 2.0 on my Windows 2003 Server SP1.
I am getting the following error:

Error 25015.Failed to install assembly
'C:\Windows\Microsoft.Net\Framework\v2.0.50727\Mic rosoft.VisualBasic.Vsa.dll'
because of system error: 0x80131107

I've seen this posted on a few websites but haven't never found a solution.
The server is not running any virus software, I went into the directory and
the file is there.

Anybody come across this and fix the issue?

Andrew

I've come across the same message. For an error with a specific number, no
one seems to know what to do about it.

"AWehrstedt" wrote:

> I'm trying to install the .Net Framework 2.0 on my Windows 2003 Server SP1.
> I am getting the following error:
>
> Error 25015.Failed to install assembly
> 'C:\Windows\Microsoft.Net\Framework\v2.0.50727\Mic rosoft.VisualBasic.Vsa.dll'
> because of system error: 0x80131107
>
> I've seen this posted on a few websites but haven't never found a solution.
> The server is not running any virus software, I went into the directory and
> the file is there.
>
> Anybody come across this and fix the issue?
>
> Andrew

BigEddieCalzone,

*Someone* does - Assembly installation error codes in .NET Framework
2.0 setup
http://blogs.msdn.com/astebner/archi...28/518610.aspx

MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============


BigEddieCalzone wrote:
> I've come across the same message. For an error with a specific number, no
> one seems to know what to do about it.
>
> "AWehrstedt" wrote:
>
>> I'm trying to install the .Net Framework 2.0 on my Windows 2003 Server SP1.
>> I am getting the following error:
>>
>> Error 25015.Failed to install assembly
>> 'C:\Windows\Microsoft.Net\Framework\v2.0.50727\Mic rosoft.VisualBasic.Vsa.dll'
>> because of system error: 0x80131107
>>
>> I've seen this posted on a few websites but haven't never found a solution.
>> The server is not running any virus software, I went into the directory and
>> the file is there.
>>
>> Anybody come across this and fix the issue?
>>
>> Andrew