Trend Micro OfficeScan IIS 503.2 Error Work Around

One of my Trend Micro OfficeScan servers recently started to experience problems resulting in IIS 503.2 error messages being displayed. This was rather poor timing as I was actually in the process of migrating OfficeScan clients to this new server running version 12 or XG as they are calling it. After some work with Trend Micro I now have a hotfix deployed which appears to have resolved the matter. During the troubleshooting period we made a range of setting changes to IIS however none of them really helped.

As I needed to be able to manage clients already on the server and continue to migrate others to it I came up with an easy workaround to maintain functionality. I reduced the IIS application pool recycling period from the default of 1740 minutes to 5 minutes. Hopefully the hotfix from Trend Micro will be released on the OfficeScan download page in the very near future so keep an eye on their site if you are experiencing the issue.

 

Now to take a look at the problem and then the workaround.

First off this is the error presented in browsers when attempting to access the OfficeScan console. On some occasions I would instead get a message simply saying the service was unavailable.

IIS 503.2 Error Message

 

GUI Workaround

In IIS manager we can browse to the ‘Application Pools’ menu and then select the OfficeScanAppPool.

IIS Application Pools

Next we can right-click on the selected application pool and choose the ‘Recycling’ option.

IIS Application Pool Recycling

This will open a new menu allowing us to change the default application pool recycling time of 1740 minutes (29 hours) to a lower value thereby causing the pool to recycle frequently and negating the 503.2 error.

Edit Application Pool Recycling Settings 1740 Default

Edit Application Pool Recycling Settings 5 Minute New Value

 

Command Line Workaround

We can also make use of Microsoft PowerShell and the traditional IIS appcmd commands to recycle the application pool.

First I will get a listing of the application pools using the PowerShell Get-wmiObject cmdlet.

PS C:\> Get-WmiObject -namespace "root\MicrosoftIISv2" -class "IIsApplicationPool"
__GENUS : 2
__CLASS : IIsApplicationPool
__SUPERCLASS : CIM_LogicalElement
__DYNASTY : CIM_ManagedSystemElement
__RELPATH : IIsApplicationPool.Name="W3SVC/APPPOOLS/DefaultAppPool"
__PROPERTY_COUNT : 5
__DERIVATION : {CIM_LogicalElement, CIM_ManagedSystemElement}
__SERVER : BSA-TOS01
__NAMESPACE : root\MicrosoftIISv2
__PATH : \\BSA-TOS01\root\MicrosoftIISv2:IIsApplicationPool.Name="W3SVC/APPPOOLS/DefaultAppPool"
Caption :
Description :
InstallDate :
Name : W3SVC/APPPOOLS/DefaultAppPool
Status :
PSComputerName : BSA-TOS01

__GENUS : 2
__CLASS : IIsApplicationPool
__SUPERCLASS : CIM_LogicalElement
__DYNASTY : CIM_ManagedSystemElement
__RELPATH : IIsApplicationPool.Name="W3SVC/APPPOOLS/OfficeScanAppPool"
__PROPERTY_COUNT : 5
__DERIVATION : {CIM_LogicalElement, CIM_ManagedSystemElement}
__SERVER : BSA-TOS01
__NAMESPACE : root\MicrosoftIISv2
__PATH : \\BSA-TOS01\root\MicrosoftIISv2:IIsApplicationPool.Name="W3SVC/APPPOOLS/OfficeScanAppPool"
Caption :
Description :
InstallDate :
Name : W3SVC/APPPOOLS/OfficeScanAppPool
Status :
PSComputerName : BSA-TOS01

PS C:\>

 

The application pool we are interested in is called “OfficeScanAppPool” – this can be recycled with Restart-webAppPool PowerShell cmdlet.

PS C:\>Restart-WebAppPool -Name "OfficeScanAppPool"

We can also use appcmd to achieve the same thing.

C:\windows\system32\inetsrv\appcmd recycle apppool "OfficeScanAppPool"

 

 


This isn’t a long term fix but it does allow one to continue working with OfficeScan while waiting for the hotfix to be deployed.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.