Article ID: 113091, created on Jan 10, 2012, last review on Feb 19, 2015

  • Applies to:
  • Operations Automation 5.x
  • Operations Automation 2.x

Symptoms

While performing branding configuration for new resellers, POA background task "Configure Exchange branding" fails as below:
Task ID 12345 
Queue name      ExchangeHostConfig1234  
Task name       Configure Exchange branding (host: 1234; brand: 5; service: ExchProtocols)      
Task description        Configure Exchange branding (host: 1234; brand: 5; service: ExchProtocols)      
Queue status     Failed 
Start not earlier than  Jan-01-2011 01:01       
Method name     addBrandingHandler on SCREF:Exchange:0  
Last execution output   Command ("%SystemRoot%\Sysnative\cscript.exe" //Nologo "C:\Program Files (x86)\SWsoft\PEM\bin\ConfigureExchnageProtocolsService.vbs" ConfigureBrandingSite CAS01 1234 owa.provider.com "C:\Program Files (x86)\SWsoft\PEM" "127.0.0.1" "") failed to execute on host 1234 with code 1: Exchnage web site created: IIS://EXCAS01/W3SVC/1234
Rpc virtual directory configured
Command 'New-OwaVirtualDirectory -OwaVersion Exchange2007 -WebSiteName 'owa.provider.com'' failed.(ErrCode: 0x1)


The task may fail with another diagnostics:
Task ID 4407785
Queue name      ExchangeHostConfig5061
Task name       Configure Exchange branding (host: 5061; brand: 40; service: ExchProtocols)
Task description        Configure Exchange branding (host: 5061; brand: 40; service: ExchProtocols)
Queue status    Failed        
Start not earlier than  Jan-22-2012 13:48
Method name     addBrandingHandler on SCREF:Exchange:0
Last execution output   Command ("%SystemRoot%\Sysnative\cscript.exe" //Nologo "C:\Program Files (x86)\SWsoft\PEM\bin\ConfigureExchnageProtocolsService.vbs" ConfigureBrandingSite EXCAS01 1722 owa.provider.com "C:\Program Files (x86)\SWsoft\PEM" "10.20.30.40" "") failed to execute on host 5061 with code 1: Exchnage web site created: IIS://EXCAS01/W3SVC/1722
Rpc virtual directory configured
OWA virtual directories configured
Active Sync virtual directory configured
Command 'New-WebServicesVirtualDirectory -WebSiteName 'owa.provider.com(1722)'' failed.(ErrCode: 0x1)


The following errors are logged in the Event Log on the corresponding CAS server:
Event Type:     Warning
Event Source:   W3SVC
Event Category: None
Event ID:       1013
Date:           1/1/2011
Time:           01:01:11 PM
User:           N/A
Computer:       CAS01
Description:
A process serving application pool 'MSExchangeSyncAppPool' exceeded time limits during shut down. The process id was '21780'.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:     Error
Event Source:   ASP.NET 2.0.50727.0
Event Category: Setup
Event ID:       1024
Date:           1/1/2011
Time:           01:01:11 PM
User:           N/A
Computer:       CAS01
Description:
Failed while restarting W3SVC.  Error code: 0x8007041d

Cause

During provisioning of a new brand for Exchange, POA executes a standard Exchange cmdlets like "New-OwaVirtualDirectory", "New-WebServicesVirtualDirectory". As part of its job, these cmdlets appliy a new IIS configuration on the CAS server. To apply the new configuration smoothly, IIS waits until there are no requests to be served. On actively-used installations, it may take a while and could incur a timeout. The error code 0x8007041d stands for "ERROR SERVICE REQUEST TIMEOUT". Such behavior is not specific to only Exchange systems integrated with POA; it happens on standalone Exchange installations as well.

Resolution

To overcome this issue, stop IIS on the CAS server, resubmit the "Configure Exchange branding" task, and restart IIS.

2554725ed606193dd9bbce21365bed4e 5356b422f65bdad1c3e9edca5d74a1ae 80fcf07a72a3fc2739554dff85ce8fe7 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF