reboot an XP machine remotely

by ebarcza 9/26/2011 7:05:00 AM

start a command prompt

type in shutdown -r

hit enter


Could not load file or assembly 'Microsoft.Practices.ObjectBuilder2

by ebarcza 9/19/2011 9:07:00 AM

Simple Solution to this error:

The solution is simply to copy the C:\Program Files\Microsoft Enterprise Library 4.0 - May 2008\Bin\Microsoft.Practices.ObjectBuilder2.dll to the bin directory that my application uses are stored, and then add a reference to it in my Visual Studio project.

done and done


ASP.NET Enterprise Library

Enabling WCF Services on IIS 7.0

by ebarcza 9/2/2011 1:05:00 PM
Out of the box, IIS 7.0 (Windows Server 2008) does not support WCF Services. If you navigate via browser to the svc file you will get a 404 error. I check for the availability of the service by opening a browser and navigating to the service (.svc) page. On IIS 6.0, this just worked if I had the .NET 3.5 framework installed. On IIS 7.0, even after installing the the .NET 3.5 framework, we were still unable to reference the service and getting an error (404.3 to be precise). The trick to make this work requires registering a all of the service handlers. Fortunately, it can be done by running a simple script Open a command prompt and run the following: %windir%\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe –r –y Now you should be able to navigate to the .svc page.


500.19 Error When Enabling 32-bit Application Pool

by ebarcza 9/2/2011 10:49:00 AM

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid. Module DynamicCompressionModule
Notification SendResponse
Handler StaticFile
Error Code 0x8007007e
Requested URL http://localhost:80/
Physical Path C:\inetpub\wwwroot
Logon Method Anonymous
Logon User Anonymous


Error Code 0x8007007e is:

ERROR_MOD_NOT_FOUND - The specified module could not be found.

This problem occurs because the ApplicationHost.config file or the Web.config file references a module that is invalid or that does not exist. To resolve this problem: In the ApplicationHost.config file or in the Web.config file, locate the module reference or the DLL reference that is invalid, and then fix the reference. To determine which module reference is incorrect, enable Failed Request Tracing, and then reproduce the problem.

For above specific error (mentioned in this example), DynamicCompressionModule module is causing the trouble. This is because of the XPress compression scheme module (suscomp.dll) which gets installed with WSUS. Since Compression schemes are defined globally and try to load in every application Pool, it will result in this error when 64bit version of suscomp.dll attempts to load in an application pool which is running in 32bit mode.

This module entry looks like:

<scheme name="xpress" doStaticCompression="false" doDynamicCompression="true"
dll="C:\Windows\system32\inetsrv\suscomp.dll" staticCompressionLevel="10"
dynamicCompressionLevel="0" />

Hence to get rid of this problem:

Ø Remove/Disable the XPress compression scheme from the configuration using the command below:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']


Ø Add an attribute of "precondition= "64bitness" for this module entry so that it loads only in 64bit application pools

Refer this blog for more details on Preconditions in IIS7


Ø Use a 32bit version of suscomp.dll


Powered by BlogEngine.NET
Theme by Mads Kristensen

About the author

Name of author Author name
Something about me and what I do.

E-mail me Send mail


<<  July 2017  >>

View posts in large calendar

Recent comments



The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2017

Sign in