Archive

Archive for the ‘Server 2008 R2’ Category

IIS errors when running 32-bit application pools on SBS 2008

August 17, 2010 12 comments

I have run into this problem a few times with customer migrations, and again recently when installing some service packs and updates.  Consider the following scenario:

You are running one or more 3rd-party web applications on a machine running Small Business Server 2003.  You decide it is time to upgrade to Small Business Server 2008 only to find that your web applications no longer function, and the application pool is crashing. 

This is because SBS 2008 is a 64-bit operating system, and the web application you are trying to run has 32-bit components.  If you look in the Event Viewer, you will likely see the following in the Application log as well:

A listener channel for protocol ‘http’ in worker process ‘####’ serving
application pool ‘DefaultAppPool’ reported a listener channel failure. The
data field contains the error number.

Application pool ‘DefaultAppPool’ is being automatically disabled due to a
series of failures in the process(es) serving that application pool.

If you edit the Advanced Settings for the Application Pool and set Enable 32-Bit Applications to True (see above), you will be met with a new problem: 500.19.

This can be remedied by editing a few lines the applicationhost.config file (C:\Windows\System32\inetsrv\config) like thus:

<add name=”PasswordExpiryModule” image=”C:\Windows\system32\RpcProxy\RpcProxy.dll” />

becomes

<add name=”PasswordExpiryModule” image=”C:\Windows\system32\RpcProxy\RpcProxy.dll” preCondition=”bitness64″ />

This, along with an IISRESET, will fix the IIS errors and let your 32-bit ASP web application play nice on SBS 2008.  Should you later install Exchange 2007 SP3, you will need to repeat the process for exppw.dll (it is listed twice – once in GlobalModules and once in Modules).

Just for the record, this problem is not limited to SBS 2008.  It’s the rpcproxy.dll that has the incompability with 32-bit application pools that causes this, and that DLL is needed for Outlook Anywhere and the Terminal Services Gateway role.  You may see this on any 64-bit Exchange 2007 server or Terminal Server Gateway server, depending on your configuration.

Microsoft announces Small Business Server 7!

We’ve had some people take vacations at Vision One recently, so the rest of us have been spread pretty thin, and I completely missed the fact that Microsoft revealed some of the details on the much-anticipated successor to Small Business Server 2008.  This announcement was made at the Microsoft Worldwide Partner Conference early this past Monday, July 12th, 2010.  According to The Official SBS Blog, there will be public preview releases for the next version of SBS within the next month or two.  And yes, you read that right; there will be TWO releases:

  • Windows Small Business Server “7”:  This next version of SBS will include a richer remote access experience, replaces Windows Server 2008 with Windows Server 2008 R2, replaces Exchange Server 2007 with Exchange Server 2010, and will also replace Windows SharePoint Services 3.0 with SharePoint 2010 Foundation.  SBS 7 will still have the 75 user limit.
  • Windows Small Business Server Code Name “Aurora”: This is a whole new type of SBS.  Aurora, as it is being called right now, will offer a mix of traditional and cloud capabilities.  Some of the features it boasts is automated backup and restore capabilities, organizing/accessing business information from almost anywhere, and will be limited to 25 users.

If you are familiar with the SBS platform, then there isn’t much I can tell you about SBS 7 that you didn’t already get from the above, so I won’t go into that.  Instead, I will elaborate on Aurora a little.  Aurora is meant only for new customers since it cannot be joined to an existing Active Directory domain, and must be the first server in a new domain.  Based on some of the screenshots and management features, a lot of the code base is likely shared with Microsoft Home Server “Vail”, which only makes sense as this is meant for customers with 5-25 PCs.  One big difference between SBS 7 and SBS Aurora is the lack of e-mail and collaboration on the box.  Instead, Aurora customers will leverage Microsoft’s hosted services for Exchange and SharePoint.  My feelings are torn on this idea until I see pricing, since SBS Aurora will mean a monthly fee for the hosted components, whereas SBS 7 has no monthly costs.  One nice perk with Aurora is that in addition to Windows Server Backup there will be a PC image backup tool for customers who need to backup client machines.

For those of you interested in beta-testing the new SBS line, head on over to this link to be notified on updates from Microsoft 🙂

Exchange 2010 – Cannot edit default E-mail Address Policy

February 9, 2010 4 comments

I wanted to try out the new version of Exchange and Server 2008 R2, so I downloaded and installed the Server 2008 R2 Enterprise Evaluation VHD (on my Hyper-V Server R2 machine), and installed Exchange 2010 RC.  Now, this problem could very well be limited to the RC, as I have not had a chance to test this on RTM, but I ran into a bit of a problem when trying to edit the default E-mail Address Policy.  I added an external domain name to the Accepted Domains and set it to Default, but when I tried to edit my Default EAP (via the Exchange Management Console) to include this new domain, I got the following:

Error:
The operation can’t be performed on the default e-mail address policy.

Exchange Management Shell command attempted:
set-EmailAddressPolicy -ConditionalDepartment @() -ConditionalCompany @() -ConditionalStateOrProvince @() -ConditionalCustomAttribute1 @() -ConditionalCustomAttribute2 @() -ConditionalCustomAttribute3 @() -ConditionalCustomAttribute4 @() -ConditionalCustomAttribute5 @() -ConditionalCustomAttribute6 @() -ConditionalCustomAttribute7 @() -ConditionalCustomAttribute8 @() -ConditionalCustomAttribute9 @() -ConditionalCustomAttribute10 @() -ConditionalCustomAttribute11 @() -ConditionalCustomAttribute12 @() -ConditionalCustomAttribute13 @() -ConditionalCustomAttribute14 @() -ConditionalCustomAttribute15 @() -RecipientContainer $null -EnabledEmailAddressTemplates ‘X400:c=US;a= ;p=MailOrg;o=Exchange;’,’SMTP:%f%l@v1testing.info’,’smtp:@exchtest.local’-Name ‘Default Policy’ -Identity ‘Default Policy’

I found a few posts out there on the InterWebs about this same problem, but everyone’s solution was to just create a new EAP.  My solution (after a lot of trial and error) was to copy the above command to the Exchange Management Shell and remove the -Name property.  Without this, my command ran fine, so it begs the question: If the -Name property of the set-EmailAddressPolicy cmdlet causes an error, why is it auto-generated from the Exchange Management Console?