framework service pack issues

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I get the following or similar *trying* to apply both 1.0 SP3 and 1.1 SP1:


An unhandled exception of type 'System.Reflection.TargetInvocationException' occurred in mscorlib.dll

Additional information: Exception has been thrown by the target of an invocation.
 
Hi Alex,

Currently I am looking for somebody who could help you on it. We will reply
here with more information as soon as possible.
If you have any more concerns on it, please feel free to post here.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hello Alex,

This is a relatively new issue and we don't have much past experience on
this. To track this issue, could you help me to collect the verbose
installation log of the installation session?

Please follow the steps below:

1. Download the Service Pack at the following site and save the file
¡°NDP1.1sp1-KB867460-X86.exe¡± to ¡°C:\¡±

http://www.microsoft.com/downloads/details.aspx?familyid=A8F5654F-088E-40B2-
BBDB-A83353618B38&displaylang=en

2. Issue the following command:

c:\NDP1.1sp1-KB867460-X86.exe /xp:c:

As a result, a Windows Installer Patch file will be extracted as
¡°C:\S867460.msp¡±.

3. Issue the following command:

msiexec /p c:\S867460.msp /l*v c:\sp1.log REINSTALL=ALL

After the installation failure, please add the file "c:\sp1.log" to a zip
and attach the zip as an attachment here. The verbose log will show which
action causes the exception.

I look forward to hearing from you.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
OK. I will try your steps out and email you the log you are looking for.
Meanwhile, here is the failure log from my windowsupdate.log


2004-09-14 22:26:32-0400 1740 4bc WU client is installing update
{AFCFDECF-2B9F-4881-8CFE-F56ED0DD81AF}.100
2004-09-14 22:26:37-0400 1740 6e0 REPORT EVENT:
{231FDC92-53D3-4C3F-BFB0-E00A10D4BFB8} 122 2004-09-14 22:26:32-0400 1 182
101 {EC9E6BF6-0733-4064-A23D-08E58427E553} 100 80070643 WindowsUpdate
Failure Content Install Installation Failure: Windows failed to install the
following update with error 0x80070643: Microsoft .NET Framework 1.0 Service
Pack 3, English Version.
2004-09-14 22:26:37-0400 1740 6e0 REPORT EVENT:
{F709CC83-A717-4AA2-80D6-16675DDFEA8D} 123 2004-09-14 22:26:32-0400 1 182
101 {8D85DEE0-C2D2-4421-A893-8F0CCACA001C} 100 80070643 WindowsUpdate
Failure Content Install Installation Failure: Windows failed to install the
following update with error 0x80070643: Microsoft .NET Framework 1.0 Service
Pack 3, English Version.
2004-09-14 22:27:13-0400 1740 4bc WU client finishes installing update
{AFCFDECF-2B9F-4881-8CFE-F56ED0DD81AF}.100 with result 0x8024200b
2004-09-14 22:27:13-0400 1740 4bc system restore point set
2004-09-14 22:27:13-0400 1740 4bc Agent state changed, signalling AU to
redetect with NO delay
2004-09-14 22:27:13-0400 1740 4bc WU client finished installing updates
2004-09-14 22:27:13-0400 1740 d0 AU received event of 3
2004-09-14 22:27:13-0400 1740 d0 AU received event of 1
2004-09-14 22:27:13-0400 1740 d0 WU client succeeds
CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id
{AF8CBD40-C914-43EF-A729-D93D275A9F14}
2004-09-14 22:27:13-0400 1740 6e0 WU client calls back to install call
{0834DAC8-5B76-4B87-A036-6ADF8BBC4479} with code Call complete and error 0
2004-09-14 22:27:13-0400 1740 6e0 WU client completed and deleted call
{0834DAC8-5B76-4B87-A036-6ADF8BBC4479}
2004-09-14 22:27:13-0400 1740 6e0 WU client executing call
{AF8CBD40-C914-43EF-A729-D93D275A9F14} of type Search Call
2004-09-14 22:27:13-0400 1740 6e0 WU client found 0 updates and 10
categories in search
2004-09-14 22:27:13-0400 1740 6e0 WU client finished Searching for update
2004-09-14 22:27:13-0400 1740 6e0 AU Detection callback: 0 updates detected
2004-09-14 22:27:13-0400 1740 6e0 Setting AU scheduled install time to
2004-09-15 10:00:00
2004-09-14 22:27:13-0400 1740 6e0 WU client calls back to search call
AutomaticUpdates with code Call complete and error 0
2004-09-14 22:27:13-0400 1740 6e0 WU client completed and deleted call
{AF8CBD40-C914-43EF-A729-D93D275A9F14}
2004-09-14 22:27:14-0400 1740 3d8 ISusInternal API failed
CClientCallRecorder::DisconnectCall with error 0x8024000c
2004-09-14 22:27:14-0400 3088 c24 ISusInternal::DisconnectCall failed,
hr=8024000C
2004-09-14 22:27:18-0400 1740 6e0 REPORT EVENT:
{083A2310-6417-489B-B740-90F52333653E} 124 2004-09-14 22:27:13-0400 1 182
101 {6F5DC828-0F05-4577-9A8A-74AB1CBE00A9} 100 80070643 WindowsUpdate
Failure Content Install Installation Failure: Windows failed to install the
following update with error 0x80070643: Microsoft .NET Framework 1.1 Service
Pack 1.
2004-09-14 22:27:18-0400 1740 6e0 REPORT EVENT:
{32A8B88E-F1AB-4C61-AE97-A7F1BBB92B6F} 125 2004-09-14 22:27:13-0400 1 182
101 {AFCFDECF-2B9F-4881-8CFE-F56ED0DD81AF} 100 80070643 WindowsUpdate
Failure Content Install Installation Failure: Windows failed to install the
following update with error 0x80070643: Microsoft .NET Framework 1.1 Service
Pack 1.
2004-09-14 22:27:28-0400 1740 408 ISusInternal API failed
CClientCallRecorder::DisconnectCall with error 0x8024000c
2004-09-14 22:27:28-0400 3088 c24 ISusInternal::DisconnectCall failed,
hr=8024000C
 
Following these directions, my problems were resolved. When updating the (2)
frameworks to 1.0SP3 and 1.1SP1 manually, there were no issues.
 
Hi Alex,

Thanks for your update. The exception is actually thrown by the wrapper EXE
file.

It will be great if we can get a CLR callstack of the exception. Do we have
VS.Net installed on that machine which can reproduce the problem?

VS.Net should be able to handle the managed exception better than the C++
debugger. When the exception occurs, do we have a chance to select which
debugger to use?

Since your problem has been fixed, you may ignore these extra questions.
However, I would appreciate it if you could help :-)

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
I am still having the problem described above, I have tried debuging
the 1.1SP1 with VS2003 and got the following call stack
ntdll.dll!7c90eb94()
Click to expand...
ntdll.dll!7c90e9c0()
kernel32.dll!7c8025db()
kernel32.dll!7c8399f3()
kernel32.dll!7c8399f3()
kernel32.dll!7c802542()
mscorwks.dll!7928118a()
mscorwks.dll!79282320()
mscorwks.dll!79246526()
mscorwks.dll!7936ddfd()
mscorwks.dll!7936dfa2()
mscorwks.dll!792a7dbc()
mscorwks.dll!792201e1()
mscorwks.dll!79220203()
mscorwks.dll!792a7ea1()
kernel32.dll!7c862cd3()
ntdll.dll!7c910732()
ntdll.dll!7c910732()
mscorwks.dll!791b74e3()
mscorwks.dll!791ba0e8()
msvcr70.dll!7c00702f()
mscorwks.dll!791b9a8a()
mscorwks.dll!791b9a3a()
mscorwks.dll!791bd6fe()
mscorwks.dll!791bc304()
mscorwks.dll!791bc2d4()
mscorwks.dll!791bc2e0()
mscorwks.dll!7923a0e3()
mscorwks.dll!79203e01()
mscorwks.dll!7921f764()
mscorwks.dll!792201e1()
mscorwks.dll!79220203()
ntdll.dll!7c910551()
ntdll.dll!7c91056d()
ntdll.dll!7c910833()
kernel32.dll!7c8399f3()
ntdll.dll!7c90e21f()
kernel32.dll!7c87f67e()
kernel32.dll!7c8399f3()
kernel32.dll!7c843622()
kernel32.dll!7c839a54()
ntdll.dll!7c9037bf()
ntdll.dll!7c90378b()
kernel32.dll!7c8399f3()
ntdll.dll!7c937860()
kernel32.dll!7c8399f3()
mscorwks.dll!79202db1()
mscorwks.dll!79202eda()
mscorwks.dll!79202ee7()
mscorwks.dll!79202eef()
ntdll.dll!7c90eafa()
kernel32.dll!7c81eb33()
kernel32.dll!7c81eb33()
ntdll.dll!7c913e6f()
ntdll.dll!7c913e62()
ntdll.dll!7c910945()
ntdll.dll!7c91094e()
ntdll.dll!7c91402e()
ntdll.dll!7c910970()
ntdll.dll!7c9140ef()
ntdll.dll!7c9140bb()
SL122.tmp!006c002e()
kernel32.dll!7c81eb33()
mscorwks.dll!791ba50c()
mscorwks.dll!791bdb64()
mscorwks.dll!791bdb4e()
mscorwks.dll!792206a8()
kernel32.dll!7c81eb33()
mscorwks.dll!7922063e()
mscorwks.dll!792205f1()
mscorwks.dll!792fdc6c()
mscorwks.dll!791e4b1a()
mscorwks.dll!792fd720()
mscorwks.dll!792fd736()
mscorlib.dll!79b4df68()
mscorlib.dll!System.Reflection.RuntimeMethodInfo.InternalInvoke(System.Object
obj, System.Reflection.BindingFlags invokeAttr,
System.Reflection.Binder binder, System.Object[] parameters,
System.Globalization.CultureInfo culture, bool verifyAccess) + 0x14a
bytes
mscorlib.dll!System.Reflection.RuntimeMethodInfo.Invoke(System.Object
obj, System.Reflection.BindingFlags invokeAttr,
System.Reflection.Binder binder, System.Object[] parameters,
System.Globalization.CultureInfo culture) + 0x18 bytes
SL122.tmp!XStart.Main(string[] args) + 0x49 bytes

Any help would be appreciated
 
I also have this problem and the call stack I looked at using VS2002 was much
like this.

Paul said:
I am still having the problem described above, I have tried debuging
the 1.1SP1 with VS2003 and got the following call stack
ntdll.dll!7c90eb94()
Click to expand...
ntdll.dll!7c90e9c0()
kernel32.dll!7c8025db()
kernel32.dll!7c8399f3()
kernel32.dll!7c8399f3()
kernel32.dll!7c802542()
mscorwks.dll!7928118a()
mscorwks.dll!79282320()
mscorwks.dll!79246526()
mscorwks.dll!7936ddfd()
mscorwks.dll!7936dfa2()
mscorwks.dll!792a7dbc()
mscorwks.dll!792201e1()
mscorwks.dll!79220203()
mscorwks.dll!792a7ea1()
kernel32.dll!7c862cd3()
ntdll.dll!7c910732()
ntdll.dll!7c910732()
mscorwks.dll!791b74e3()
mscorwks.dll!791ba0e8()
msvcr70.dll!7c00702f()
mscorwks.dll!791b9a8a()
mscorwks.dll!791b9a3a()
mscorwks.dll!791bd6fe()
mscorwks.dll!791bc304()
mscorwks.dll!791bc2d4()
mscorwks.dll!791bc2e0()
mscorwks.dll!7923a0e3()
mscorwks.dll!79203e01()
mscorwks.dll!7921f764()
mscorwks.dll!792201e1()
mscorwks.dll!79220203()
ntdll.dll!7c910551()
ntdll.dll!7c91056d()
ntdll.dll!7c910833()
kernel32.dll!7c8399f3()
ntdll.dll!7c90e21f()
kernel32.dll!7c87f67e()
kernel32.dll!7c8399f3()
kernel32.dll!7c843622()
kernel32.dll!7c839a54()
ntdll.dll!7c9037bf()
ntdll.dll!7c90378b()
kernel32.dll!7c8399f3()
ntdll.dll!7c937860()
kernel32.dll!7c8399f3()
mscorwks.dll!79202db1()
mscorwks.dll!79202eda()
mscorwks.dll!79202ee7()
mscorwks.dll!79202eef()
ntdll.dll!7c90eafa()
kernel32.dll!7c81eb33()
kernel32.dll!7c81eb33()
ntdll.dll!7c913e6f()
ntdll.dll!7c913e62()
ntdll.dll!7c910945()
ntdll.dll!7c91094e()
ntdll.dll!7c91402e()
ntdll.dll!7c910970()
ntdll.dll!7c9140ef()
ntdll.dll!7c9140bb()
SL122.tmp!006c002e()
kernel32.dll!7c81eb33()
mscorwks.dll!791ba50c()
mscorwks.dll!791bdb64()
mscorwks.dll!791bdb4e()
mscorwks.dll!792206a8()
kernel32.dll!7c81eb33()
mscorwks.dll!7922063e()
mscorwks.dll!792205f1()
mscorwks.dll!792fdc6c()
mscorwks.dll!791e4b1a()
mscorwks.dll!792fd720()
mscorwks.dll!792fd736()
mscorlib.dll!79b4df68()
mscorlib.dll!System.Reflection.RuntimeMethodInfo.InternalInvoke(System.Object
obj, System.Reflection.BindingFlags invokeAttr,
System.Reflection.Binder binder, System.Object[] parameters,
System.Globalization.CultureInfo culture, bool verifyAccess) + 0x14a
bytes
mscorlib.dll!System.Reflection.RuntimeMethodInfo.Invoke(System.Object
obj, System.Reflection.BindingFlags invokeAttr,
System.Reflection.Binder binder, System.Object[] parameters,
System.Globalization.CultureInfo culture) + 0x18 bytes
SL122.tmp!XStart.Main(string[] args) + 0x49 bytes

Any help would be appreciated


Hi Alex,

Thanks for your update. The exception is actually thrown by the wrapper EXE
file.

It will be great if we can get a CLR callstack of the exception. Do we have
VS.Net installed on that machine which can reproduce the problem?

VS.Net should be able to handle the managed exception better than the C++
debugger. When the exception occurs, do we have a chance to select which
debugger to use?

Since your problem has been fixed, you may ignore these extra questions.
However, I would appreciate it if you could help :-)

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Click to expand...
Click to expand...
 
Back
Top