Apps no longer work with Framework 1.0 SP3

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Bert Hyman - 14 Sep 2004 16:14 GMT

Our administrators did an unannounced deployment of dotNet Framework
1.0 SP3 to all our Win2K machines last week and now the product we're
developing no longer works, nor does the dotNet Framework
Configuration tool.

The machines runnning dotNet Framework 1.1 appear to be OK.

When the app is executed, it produces this exception:

"Request for the permission of type
System.DelegateSerializationHolder failed."

Trying to run the Configuration tool merely produces an error dialog

"MMC cannot open the selected file"

This is ->serious.

Signature

Bert Hyman | St. Paul, MN | bert@visi.com

Reply to this Message

Bert Hyman - 14 Sep 2004 19:09 GMT

> Trying to run the Configuration tool merely produces an error dialog
>
> "MMC cannot open the selected file"
>
> This is ->serious.

A little more info... The new corrupt mscorcfg.msc file on my machine
is an XML file that starts out

<?xml version="1.0"?>
<MMC_ConsoleFile ConsoleVersion="2.0" ProgramMode="Author">
<ConsoleFileID>{92BF0122-2B3D-42DC-BB73-9102F9EF13E0}
</ConsoleFileID>

Does this mean anything to anybody?

Signature

Bert Hyman | St. Paul, MN | bert@visi.com

Reply to this Message

"Peter Huang" - 15 Sep 2004 02:56 GMT

Hi Bert,

It seems that there is something corrupted, you may try to install the .net
framework 1.1(in the repair installation mode) to see if that works for you.

Best regards,

Peter Huang
Microsoft Online Partner Support

Signature

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

Reply to this Message

Bert Hyman - 15 Sep 2004 13:41 GMT

> Hi Bert,
>
> It seems that there is something corrupted, you may try to install
> the .net framework 1.1(in the repair installation mode) to see if
> that works for you.

Installing dotNet Framework 1.1 is ->not an option. We need to build
and test our application on many OS levels and both 1.0 and 1.1
Framework levels. All of our Win2K systems with Framework 1.0 are
completely out of business right now.

I downloaded the Framework 1.0 SP3 package from MSDN yesterday and
re-installed it but had exactly the same result.

Signature

Bert Hyman | St. Paul, MN | bert@visi.com

Reply to this Message

Bert Hyman - 15 Sep 2004 14:18 GMT

>> Hi Bert,
>>
[quoted text clipped - 9 lines]
> I downloaded the Framework 1.0 SP3 package from MSDN yesterday and
> re-installed it but had exactly the same result.

Following up on my own post, I believe I've found a fix to our app's
immediate problem.

When creating our BinaryServerFormatterSinkProvider, I set the
typeFilterLevel property to "Full".

We already did this when running under Framework 1.1, and apparently,
this property was retrofitted to Framework 1.0 by the SP3 update.

I guess if the update had gone through our normal qualification
process instead of being forced on us by our administrators, we'd
have known about this.

Still, the fact that the "mscorcfg.msc" file was corrupted on all
systems that received the update is ->very troubling.

And, who knows what other incompatibilities have been introduced by
this "fix" that we haven't run into yet.

Short of re-installing the Framework from scratch, there doesn't
appear to be any way to back out SP3; is that correct?

Signature

Bert Hyman | St. Paul, MN | bert@visi.com

Reply to this Message

Bert Hyman - 15 Sep 2004 15:17 GMT

> I guess if the update had gone through our normal qualification
> process instead of being forced on us by our administrators, we'd
> have known about this.

Well, maybe not.

Looking at the long laundry list of changes in SP3, which one of
these would have told us of the changes to the properties of our
BinaryServerFormatterSinkProvider?

Further, how can we determine at runtime if our application is
running on a system with SP3 installed, since the "typeFilterLevel"
property didn't exist before?

Is this what DLL Hell is like?

Signature

Bert Hyman | St. Paul, MN | bert@visi.com

Reply to this Message

"Peter Huang" - 16 Sep 2004 03:15 GMT

Hi Bert,

Thank your for detailed information.
We can installed both .net FW 1.1 and .net FW 1.0 on one machine. Also in
the app.config file we can specify which version of framework to use. If
you have tried to look into the directory below, you will find that there
are two versions of .net framework.
C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\mscorcfg.msc
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorcfg.msc

So as for your scenario, there maybe a possibility that the 1.1 or 1.0 has
corrupted so I suggest you reinstall the framework. Because the
incompatibility between 1.1 and 1.0 so we can not guarantee the application
running on 1.1 will still running on 1.0.
Here is an article about Targeting a .NET Framework Version, you may take a
look.
Targeting a .NET Framework Version
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
l/cpcontargetingnetframeworkversion.asp

Best regards,

Peter Huang
Microsoft Online Partner Support

Signature

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

Reply to this Message

Bert Hyman - 17 Sep 2004 16:32 GMT

> If you have tried to look into the directory below, you will find
> that there are two versions of .net framework.
> C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\mscorcfg.msc
> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorcfg.msc

No.

On the Win2K systems in question, ONLY Framework 1.0 is installed.

What Knowlege Base article describes the "fix" that retrofitted the
"typeFilterLevel" property for BinaryServerFormatterSinkProvider into
Framework 1.0?

Did this happen in SP2 or SP3?

Signature

Bert Hyman | St. Paul, MN | bert@visi.com

Reply to this Message

"Peter Huang" - 20 Sep 2004 07:07 GMT

Hi Bert,

As you have said, the BinaryServerFormatterSinkProvider.TypeFilterLevel
Property is supported only on .net FW 1.1.

BinaryServerFormatterSinkProvider.TypeFilterLevel Property
Note: This namespace, class, or member is supported only in version 1.1 of
the .NET Framework.
Gets or sets the TypeFilterLevel of automatic deserialization the
BinaryServerFormatterSink performs.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/
frlrfSystemRuntimeRemotingChannelsBinaryServerFormatterSinkProviderClassType
FilterLevelTopic.asp

Also I have searched the internal website, but I did not find any official
document about the BinaryServerFormatterSinkProvider change between .net FW
1.0 to .net FW 1.0 sp2,sp3. As the document above I think the
TypeFilterLevel is not supported on .net FW 1.0. So have you tried to
remove TypeFilterLevel feature the the recompiled based on .net framework
1.0. To isolate the problem, I think we would better recompiled and run the
application on an machine with .net framework 1.0 + sp3 installed(I mean
the Configuration tool should be OK while on your problem machines the tool
did not work). So that we can isolate the problem.

Description of the Type Filtering feature in the Microsoft .NET Framework
(831687)
http://support.microsoft.com/default.aspx?scid=KB;EN-US;831687

BTW, from the description, I guess the "Request for the permission of type
System.DelegateSerializationHolder failed." is related with permission, to
remove the concern, we may try to put the necessary assemblies into GAC to
see if that helps.

Best regards,

Peter Huang
Microsoft Online Partner Support

Signature

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

Reply to this Message

Bert Hyman - 20 Sep 2004 13:46 GMT

> Also I have searched the internal website, but I did not find any
> official document about the BinaryServerFormatterSinkProvider
> change between .net FW 1.0 to .net FW 1.0 sp2,sp3. As the document
> above I think the TypeFilterLevel is not supported on .net FW 1.0.

Well, that's apparently the crux of the problem.

After installing Framework 1.0 SP3, our application began failing as I
described.

Setting the property "typeFilterLevel = full" in our
BinaryServerFormatterSinkProvider allowed the application to function
properly again.

Signature

Bert Hyman | St. Paul, MN | bert@visi.com

Reply to this Message

Jos Soetaert - 20 Sep 2004 17:19 GMT

We have the same error after downloading SP3.
I tried putting the typeFilterLevel="full" in the config file but the 1.0
framework does
not support this. I got a message in the eventlog that confirms this.

Does it work for you when implementing it in the code instead of in the
config file?

> > Also I have searched the internal website, but I did not find any
> > official document about the BinaryServerFormatterSinkProvider
[quoted text clipped - 9 lines]
> BinaryServerFormatterSinkProvider allowed the application to function
> properly again.

Reply to this Message

BTech - 28 Sep 2004 21:53 GMT

Is there a way to back to sp2 without starting from scratch

> Short of re-installing the Framework from scratch, there doesn't
> appear to be any way to back out SP3; is that correct?

Reply to this Message

Apps no longer work with Framework 1.0 SP3

Free Magazines