A Unified Communication Blog
Get Adobe Flash player

Monthly Archives: March 2009

Microsoft has released a new update for OC 2007. The udate includes the previous updates for Communicator

Communicator 2007 hotfix rollup package: March 2009 KB Article:
http://support.microsoft.com/Default.aspx?kbid=961552

Get the update here:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=1ad57f8f-78f7-45f6-a8c0-805936f46645

Microsoft Forefront Security for Office Communications Server (FSOCS) RTM Now Available

This release includes:
· 64bit support
· Support for OCS 2007 R2
· Support for OCS 2007 Enterprise Edition server roles
· Integration with OCS 2007 Access Edge role to protect corporate IM from external public IM threats
· Localization in 11 languages

Read more here:

An updated Forefront Security for Office Communications Server 2007 has been released at MS (Still beta 3)

Get it here:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=d128fd1a-42a2-47cb-9de8-e4ea8ba2382d

Rasmus

I have just had some problems installing an Exchange 2007 SP1 CCR cluster on a Windows 2008 platform.
I got the above error code and the ExchangeSetupLogs says:
[09-03-2009 10:07:13] [2] [ERROR] Cluster Common Failure Exception: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)
[09-03-2009 10:07:13] [2] [ERROR] The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)

Microsoft writes about the error here: http://support.microsoft.com/kb/947345/en-us

And suggest to run the setup from command prompt.
I then tried to install with this command:

Setup.com /roles:Mailbox /newcms /CMSname:MBX01 /CMSIPAddress:172.16.1.20 “/CMSDataPath:H:Exchange Server” /dc:dc01.contoso.com

That didn’t help.
I noticed in the cluster administrator that I couldn’t start System Attendant. In the event log it told me that it couldn’t find the virtual computername in AD.
I waited a couple of minutes, and then I could start the system attendant.

But that didn’t help me a lot, so I contacted Microsoft support and they suggested, that after the setup fails with the error code, then I should run this command:
Setup.com /newcms /CMSname:MBX01 /CMSIPAddress:172.16.1.20 “/CMSDataPath:H:Exchange Server” /dc:dc01.contoso.com

The first time it didn’t worked, but if I wait approx. 1 min after the failure and then run the command, then it worked.
So it seems like a replication problem with my AD.

Also I learned from Microsoft Support that it’s possible to install the passive nodes first, with this command:

Setup.com /mode:install /roles:Mailbox

This command can be run on both nodes.
Afterwards you execute the /newcms command which dosn’t copy any files – it only creates the cluster in Exchange.

Hope this can help others.

Regards,

Joachim

I have just made a Exchange 2007 SP1 CCR installation on a Windows 2008 that failed with the above error code:

The ExchangeSetupLogs says the following:
[11-03-2009 10:44:46] [2] [ERROR] Unexpected Error [11-03-2009 10:44:46] [2] [ERROR] Cluster Common Failure Exception: The cluster resource could not be brought online by the resource monitor. (Exception from HRESULT: 0x8007139A)
[11-03-2009 10:44:46] [2] [ERROR] The cluster resource could not be brought online by the resource monitor. (Exception from HRESULT: 0x8007139A)
[11-03-2009 10:44:46] [2] Ending processing. [11-03-2009 10:44:46] [1] The following 1 error(s) occurred during task execution: [11-03-2009 10:44:46] [1] 0. ErrorRecord: Cluster Common Failure Exception: The cluster resource could not be brought online by the resource monitor. (Exception from HRESULT: 0x8007139A)


I looked in my cluster administrator and the System Attandant and Information Store resource was running fine, but it couldn’t start the mailbox store.
I then waited a couple of minutes to make sure that the AD replication of the new mailbox store was in place.
I could then bring the resource mailbox store resource online from the cluster administrator.
Afterwards I run this command:
Setup.com /newcms /CMSname:MBX01 /CMSIPAddress:172.16.1.20 “/CMSDataPath:H:Exchange Server” /dc:dc01.contoso.com

And then the setup of the CCR cluster completed, and I could go on installing the passive node.

So I seems like this error is related to AD replication of the new mailbox store when it’s created in the setup process.

Hope this can help others.

Regards,

Joachim

Yesterday I was called to a customer because the customers brand new test environment for Exchange was falling in the setup of the Exchange 2007 SP1 CCR cluster on Windows 2008.

The pre checks works fine and the installation seems to run fine, but at the end of the setup where ithe setup creates the actual Cluster it fails with these errors:

[03-03-2009 12:56:24] [2] [WARNING] Object EXCH01 has been corrupted and it is in an inconsistent state. The following validation errors have occurred:
[03-03-2009 12:56:24] [2] [WARNING] Cannot calculate value of property “AdminDisplayVersion”: “SerialNumber property is not present.”.
[03-03-2009 12:56:24] [2] Ending processing.

And also

[03-03-2009 12:57:04] [2] Actual arguments passed to create EVS do not match existing server object in AD
[03-03-2009 12:57:04] [2] ScSetupExchangeVirtualServer (f:8.01.0240sourcesdevadminsrcudogexsetdataexsetds.cxx:2013)
Error code 0XC103FD2C (64812): One or more of these parameters: Administrative Group, Routing Group, Administrative Group containing Routing Group, Install path, and Data path did not match the existing Active Directory object. Please use Exchange System Manager to retrieve the correct parameters for this operation.
[03-03-2009 12:57:04] [2] Leaving ScSetupExchangeVirtualServer
[03-03-2009 12:57:04] [2] [ERROR] Unexpected Error
[03-03-2009 12:57:04] [2] [ERROR] Error of unknown type occurred while performing exsetdata operation; the original error code was 0xc103fd2c.
[03-03-2009 12:57:04] [2] Ending processing.
[03-03-2009 12:57:04] [1] The following 1 error(s) occurred during task execution:
[03-03-2009 12:57:04] [1] 0. ErrorRecord: Error of unknown type occurred while performing exsetdata operation; the original error code was 0xc103fd2c.
[03-03-2009 12:57:04] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Tasks.ExsetdataUnknownException: Error of unknown type occurred while performing exsetdata operation; the original error code was 0xc103fd2c.
[03-03-2009 12:57:04] [1] [ERROR] Error of unknown type occurred while performing exsetdata operation; the original error code was 0xc103fd2c.
[03-03-2009 12:57:04] [1] Setup is halting task execution because of one or more errors in a critical task.
[03-03-2009 12:57:04] [1] Finished executing component tasks.
[03-03-2009 12:57:04] [1] Ending processing.

The setup was made in HyperV so I deployed two new servers from a template (clone with sysprep), and it ended up with the same error.
First after I made two completely fresh installations of Windows 2008 it worked.

I’m not sure what is causing the problem, but in the templates I used first, dot.framework 3.5 was installed (which I don’t normally have on my CCR clusters). In the new installation framework 3.5 wasn’t installed.

If you have any idea what was wrong in the first installations I would appreciate your comments.

Regards,
Joachim

I will just share some of my experience with HP Nic Teaming in Windows 2008.

My setup is HP blade servers BL460C G5. I only have two virtual connect modules in the c7000 chassis for my nics, so I have 2 nics per blade.

I my setup I needed to setup a cluster which I’m going to use for an Exchange 2007 CCR cluster.
The cluster needs two nics, one for the client traffic and one for the heartbeat traffic for the cluster. I also need to use VLANs on both networks, and the nics should be teamed, so I can make service on one part of the network without interrupting the network traffic to the cluster.

I’m using HP Network Configuration Utility 9.40 (9.50 doesn’t seems to work at all in my setup) to setup the teaming and the VLANs.

I have created a team with the two nics in the blade, and configured two VLANs on this team. The network configuration utility then creates two new nics for me, one that I can use for the client traffic and one for the cluster traffic.
It seems that it works fine, but if you disabled one of the virtual nics, then the traffic to the other nics will also stop.

The Issue with the 9.50 version was that I looses a lot packets when I ping the server. Firmware upgrade of the blades helped a lot, but it didn’t solved the problem completely so I downgraded to version 9.40.
I have tested with both 32 and 64 bit versions of Windows 2008. Windows 2003 doesn’t seems to have the same problems.

As part of the installation of a Windows 2008 cluster you are asked to run a configuration validation before the actual cluster setup. The report it gives you are required by Microsoft support if you at some point should need support from Microsoft.
The validation test will fail the IP configuration test, because the two virtual VLAN nics share the same MAC address, so the cluster will not work with this. It’s not possible to change the MAC address in the HP Network Configuration Utility.

The solution for me was to get two Virtual Connects more and mezzanine cards for the blades so I can have four nics in each blade.

Hope that it can save some time for you, so you don’t make the same mistake.

Regards,
Joachim

After installing OCS 2007 R2 you might receive an Office Communicator “Limited External Calling” error on all your OC clients.

Validation wizard on the OCS 2007 R2 front end server shows this error:

A/V Authentication Edge Server: Could not contact A/V Authentication Edge Server. To resolve this error, check for the following
1. The outbound proxy is reachable.
2. The outbound proxy and A/V Authentication Edge Server are in trusted server list of each other.
3. The outbound proxy and A/V Authentication Edge Server have valid certificates.
4. Conference Server certificate is valid.
5. A/V Authentication Edge Server Gruu is correct.

Also you are using Regional Settings other than English (United States) on the OCS 2007 R2 Access Edge server.

This is caused by a bug in OCS 2007 R2 with regional settings.

From MS Support I got this work around:

  • Log on to OCS 2007 R2 Access Edge Server
  • Change the regional settings to English (United States) Dont forget to Copy your language and regional settings to system accounts on administrative tab.
  • Add the RTCProxyService to the local administrators group
  • In another session; log in as the RTCProxyService users
  • Change the regional settings to English (United States)
  • Log off the RTCProxyService
  • Remove the RTCProxyService from the local administrators group
  • Restart the server

This procedure works

Also Joachim Farla has more on this bug:

http://unified-communications.blogspot.com/2009/01/ocs-2007-r2-and-localization.html

I hope this helps,
Rasmus

Note: For more solutions for this error also see here:
http://it-proknowledge.blogspot.com/2008/05/office-communicator-limited-external.html

Search

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 75 other subscribers

Follow me on Twitter