Problem enabling Unified Messaging.

  • Thread starter exchsam
  • Start date Views 3,268
Status
Not open for further replies.
E

exchsam

Hi All,

To enable Unified Messaging, I am firing following powershell commad:

Enable-UMMailbox -Identity '<DN of user>' -UMMailboxPolicy 'UMPolicy1' -Extensions 12345 -PINExpired $false -DomainController '<DC>'

I am getting following error message:

WARNING: An unexpected error has occurred and a Watson dump is being generated: Default Scope and Search Root cannot be set at the same time.
Default Scope and Search Root cannot be set at the same time.
+ CategoryInfo : NotSpecified: :)) [Enable-UMMailbox], NotSupportedException
+ FullyQualifiedErrorId : System.NotSupportedException,Microsoft.Exchange.Management.Tasks.UM.EnableUMMailbox

I have two setups having different builds installed.

Version 14.1 (Build 115.5)

Version 14.0 (Build 639.21)

The server on which the powershell command is failing is having build Version 14.1 (Build 115.5) installed and on the other server I am able to enable Unified Messaging without any error.

Can any one help me ?

Thanks in advance,

Sam.
 
E

exchsam

I observed that Unified Messaging service is failing to start, can it be the reason of the issue I am facing ? Well, Unified Messaging service is failing with following error message:

Log Name: Application
Source: MSExchange Unified Messaging
Date: 4/28/2010 2:11:12 PM
Event ID: 1038
Task Category: UMService
Level: Error
Keywords: Classic
User: N/A
Computer: <FQDN>
Description:
The Microsoft Exchange Unified Messaging service was unable to start. More information: " Microsoft.Exchange.UM.UMService.UMServiceException: The Microsoft Exchange Unified Messaging service can't create a worker process because SIP ports (" 5065" or " 5067" ) are unavailable.
at Microsoft.Exchange.UM.UMService.WorkerProcessManager.OnWorkerExited(WorkerInstance workerInstance, Boolean resetRequested, Boolean fatalError)
at Microsoft.Exchange.UM.UMService.WorkerInstance.MonitorResetHandle(Object stateinfo)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)"
Event Xml:
<Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event" >
<System>
<Provider Name=" MSExchange Unified Messaging" />
<EventID Qualifiers=" 49156" >1038</EventID>
<Level>2</Level>
<Task>4</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=" 2010-04-28T08:41:12.000Z" />
<EventRecordID>114389</EventRecordID>
<Channel>Application</Channel>
<Computer><FQDN></Computer>
<Security />
</System>
<EventData>
<Data>Microsoft.Exchange.UM.UMService.UMServiceException: The Microsoft Exchange Unified Messaging service can't create a worker process because SIP ports (" 5065" or " 5067" ) are unavailable.
at Microsoft.Exchange.UM.UMService.WorkerProcessManager.OnWorkerExited(WorkerInstance workerInstance, Boolean resetRequested, Boolean fatalError)
at Microsoft.Exchange.UM.UMService.WorkerInstance.MonitorResetHandle(Object stateinfo)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)</Data>
</EventData>
</Event>

Any help ?

Thanks

Sam.
 
R

Roendi

Firewall you have disabled?

You tried to enable a user with the GUI not Powershell?

Roendi
 
E

exchsam

Not using GUI (Exchange Management Console) but using Powershell command.
 
C

Casper Pieterse

I'll worry about getting your UM services up and running first and then worrying about enabling the users. Do you have any other applications installed on this server except Exchange? Is it dedicated to UM or multi-role server?

Casper Pieterse, Principle Consultant - UC, Dimension Data South Africa, Microsoft Certified Master: Exchange 2007
 
E

exchsam

It is multiple role server and other software installed are:

Visual Studio 2005

MS SQL 2005 (But all services of SQL server are stopped)
 
E

exchsam

I prepared another MS Exchange 2010 server with same build Version 14.1 (Build 115.5) and Unified Messaging service is running on it without any issue. But Enable-UMMailbox still throws same error message. But I observed that it enables the UM of the user mailbox on both the setups even though powershell command is throwing an exception. Both (old and new) MS Exchange 2010 severs are in the same domain. Can anyone help me ?
 
Status
Not open for further replies.
Top