KB2742596 and KB2756918 causing Error?

Question

Is any body seeing the folloiwng error after installing KB2742596 and KB2756918 on Windows Server 2003 with WCF calls?

System.InvalidProgramException Common Language Runtime detected an invalid program.

This error begins right after the patches are installed.  

---

Steve

Answer 1

Hi Steve,

Thanks for your post.

How did you install those updates? Via Windows Update?

I checked the update KB2742596 and KB2756918  and it seems they replaces "WCF update for the .NET Framework 3.5 Service Pack 1 ". May be that's why your error occured.

Since they are windows updates so I would recommend you ask on the following forum:

http://answers.microsoft.com/en-us/windows/forum/windows_update

Regards,

---

Barry Wang
MSDN Community Support | Feedback to us
Develop and promote your apps in Windows Store
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 2

Thanks for the information and suggestion.

Before trying the windows form let me add this - we have the patch installed on our dev, cert, and production environments.  In Dev it works fine - so I can't even reproduce the issue there.  If we remove these two updates in Cert - the WCF calls in the app work again.  We put the patches back and it breaks again.

To make things stranger - the site is compiled to target the 3.5 framework - but if I change IIS in Cert to target 4.0 - the site WCF calls work again.

So what even happens if the app is compiled to target 3.5 and IIS is set on 4???

Any ideas???

---

Steve

Answer 3

Hi Steve,

Please reopen a new case on the site I mentioned or file a report here:

http://connect.microsoft.com/VisualStudio

Thanks for your understanding.

Regards,

---

Barry Wang
MSDN Community Support | Feedback to us
Develop and promote your apps in Windows Store
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 4

Hi, have you found an answer?

I'm experiencing the same issue and I could not find anything googling nor in the bulletin: the http://technet.microsoft.com/en-us/security/bulletin/ms13-004

As soon as we apply the update on the server, the WCF web service stops with the same error as you got.

Regards,

Daniel

Answer 5

No - but I've opened an incident with Microsoft via our MSDN license and have been workign with them.  They tried a few things - they've found no bug in the code - they've done a memory dump of the server and analyzed it and nothing.  Was suppose to have a confernece call with them today but I'm too busy so I have one tomorrow morning.  I'll let you know what I find out.  For now we have removed the patch from our production server.  I'll point them to your post saying you are expereincing the same issue.

---

Steve

Answer 6

Daniel,

By any chance are you using SiteMinder to or Actional/SoapStation to proxy your calls?

-Steve

---

Steve

Answer 7

Hi Steve,

Thank you for your quick response!

Unfortunately no, we are not using SiteMinder nor Actional/SoapStation.

I've figure out that the particular update that breaks down my web service is the KB2742596.

I have two different stacks for the same issue.

Event Type:	Error
Event Source:	System.ServiceModel 3.0.0.0
Event Category:	WebHost 
Event ID:	3
Date:		1/23/2013
Time:		6:14:37 AM
User:		NT AUTHORITY\NETWORK SERVICE
Computer:	MyComputer
Description:
WebHost failed to process a request.
 Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/53180767
 Exception: System.ServiceModel.ServiceActivationException: The service '/ws/mywebservice.svc' cannot be activated due to an exception during compilation.  The exception message is: Common Language Runtime detected an invalid program.. ---> System.InvalidProgramException: Common Language Runtime detected an invalid program.
   at System.ServiceModel.Dispatcher.DispatchRuntime..ctor(EndpointDispatcher endpointDispatcher)
   at System.ServiceModel.Dispatcher.EndpointDispatcher..ctor(EndpointAddress address, String contractName, String contractNamespace)
   at System.ServiceModel.Description.DispatcherBuilder.BuildDispatcher(ServiceHostBase service, ServiceDescription serviceDescription, ServiceEndpoint endpoint, ContractDescription contractDescription, EndpointFilterProvider provider)
   at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)
   at System.ServiceModel.ServiceHostBase.InitializeRuntime()
   at System.ServiceModel.ServiceHostBase.OnBeginOpen()
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   --- End of inner exception stack trace ---
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath)
 Process Name: w3wp
 Process ID: 1604

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

And this is the other stack:

Event Type:	Error
Event Source:	System.ServiceModel 3.0.0.0
Event Category:	WebHost 
Event ID:	3
Date:		1/23/2013
Time:		6:14:37 AM
User:		NT AUTHORITY\NETWORK SERVICE
Computer:	MyComputer
Description:
WebHost failed to process a request.
 Sender Information: System.ServiceModel.Activation.HostedHttpRequestAsyncResult/11865849
 Exception: System.ServiceModel.ServiceActivationException: The service '/ws/mywebservice.svc' cannot be activated due to an exception during compilation.  The exception message is: Common Language Runtime detected an invalid program.. ---> System.InvalidProgramException: Common Language Runtime detected an invalid program.
   at System.ServiceModel.Dispatcher.DispatchRuntime..ctor(EndpointDispatcher endpointDispatcher)
   at System.ServiceModel.Dispatcher.EndpointDispatcher..ctor(EndpointAddress address, String contractName, String contractNamespace)
   at System.ServiceModel.Description.DispatcherBuilder.BuildDispatcher(ServiceHostBase service, ServiceDescription serviceDescription, ServiceEndpoint endpoint, ContractDescription contractDescription, EndpointFilterProvider provider)
   at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)
   at System.ServiceModel.ServiceHostBase.InitializeRuntime()
   at System.ServiceModel.ServiceHostBase.OnBeginOpen()
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   --- End of inner exception stack trace ---
   at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result)
 Process Name: w3wp
 Process ID: 1604

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

We decided to uninstall the update until we find a solution, the problem is there's no related information.

Please let me know if you have an answer.

Best regards,

Daniel

---

.NET Sr Software Developer

Answer 8

Hi Steve,

I've found that there is a similar (not equal) issue with the Exchange when installing the KB2756920, please check the link http://support.microsoft.com/kb/2802139

Based on this, I've checked the System.ServiceModel.dll and the System.ServiceModel.WasHosting.dll versions.

I've found that the version for System.ServiceModel.dll is 4.0.30319.1001, and the version of System.ServiceModel.WasHosting.dll is 4.0.30319.1.

They are different and I've also checked into the error page and the version information throws this:

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1

Could this be the reason?

Could you please check which are the versions that you have for these 2 dlls?

- System.ServiceModel inside C:\WINDOWS\Microsoft.NET\assembly\GAC_MSIL\System.ServiceModel\

- System.ServiceModel.WasHosting inside C:\WINDOWS\Microsoft.NET\assembly\GAC_MSIL\System.ServiceModel.WasHosting\

Best regards,

Daniel

---

.NET Sr Software Developer

Answer 9

We are using .NET 3.5 - not 4 and I believe those DLLs are only applicable to 4.  The produciton server with the problem doesn't even have .NET 4 installed - just 3.5.  Glad to hear your not using SiteMinder or SOAPStation - I thought maybe they were are issue.

---

Steve

Answer 10

Hi Steve,

That's weird, we are also using framework 3.5 but the server has framework 4 installed also.

Have you got any update or clue about the issue?

---

.NET Sr Software Developer

Answer 11

Not much movement.  Microsoft has acknowledged that they have several incident tickets now surrounding this issue and the development teams is looking at it.

I did confirm for them that the problem is specific to KB2742596, but that was a week ago and I’ve heard nothing back.

I’m working with our coproate hosting group to try and move this to a new server with IIS7 as our fix -- because I’m not hopeful that Microsoft is going to fix this anytime soon.

It’s also annoying that they’ve told me to post this in at least 3 different forums and every time they say no this should go in a different forum.  If they put half the time into fixing issues as they do in moving posts around in forums – it may be fixed.  This is the "off-topic" forum....

---

Steve

Answer 12

Hey Steve, glad to here you again!

I completely agree with you regarding the off-topic issue, because this not seems to be 100% caused by only one of the topics.

We are moving forward creating a ticket using our MSDN license too, because we could not find the root cause nor a work around.

If we get a solution, I'm going to post it here.

Regards,

Daniel

---

.NET Sr Software Developer

Answer 13

Feel free to reference my ticket with them too - our ticket with MS is:  REG:113020610197266

---

Steve

Answer 14

Microosft believes the issue is with CA Wily Introscope monitoring and the patch.  I know we have this tool so we are going to try disabling and reinstalling the patch.  I'll let you know what we find out, but wanted to pass along the information.  Do you have Wily installed?

---

Steve

Answer 15

Hi Steve,

Thank you very much for the update!

Well, we have CA Wily also.

I hope it is not Wily causing these troubles.

I'm going to keep you posted if we get a different clue from Microsoft support team.

---

.NET Sr Software Developer

Answer 16

We had the same problem.

Deactivating Wily fixxed the problem for us.

Answer 17

I've confirmed that turning off Wily fixes the problem for us too.

---

Steve