MicrosoftTouch

ABSConfig.exe : ABS is not enabled or activated on this server

BOUCETTA Christophe
Par défaut, lorsque vous voulez utiliser l'utilitaire absconfig.exe du ressource kit tools, vous pouvez avoir ce genre d'erreur :

ou

Voila la solution a votre probleme :

http://support.microsoft.com/kb/954749/en-us

05:24 | Ajouter un commentaire | Lien permanent | Ajouter au blog | Juillet 2009

Exchange Messagerie Unifiée : You cannot resume setup by performing the action “BuildtoBuildUpgrade”
Apres avoir passé le SP1 dans le cadre d'un lab de présentatios, je me suis retrouvé dans l'incapacité de faire tourner le service de messagerie unifiée :

Setup previously failed while performing the action “install”. You cannot resume setup by performing the action “BuildtoBuildUpgrade”

Microsoft Knowledge Article KB947281 describes this problem and has a resolution for it. Unfortunately the article is a little bit incomplete.

It tells you to delete the Watermark and Action entries from any of these Registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\ClientAccessRole

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\HubTransportRole

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\MailboxRole

But for my particular case the Watermark and Action entries were located at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\UnifiedMessagingRole.

So, the right solution should be to check for those entries at any of these keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\ClientAccessRole
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\HubTransportRole
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\MailboxRole
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\UnifiedMessagingRole
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\ClusteredMailboxServer

Communcator Web Access R2 (error 0-1-492)

Voila qui peut etre tres utile quand comme moi, le lien pour ce connecter a CWA n'est pas le fqdn hébergeant le role, d'ou l'erreur :

La solution :

Open ADSIEDIT and navigate to the OU where your CWA service account is stored.
Locate the CWA service account (mine is called 'CWAService') and right-click then choose Properties.
Turn on the checkbox to 'Show only attributes that have values' and scroll down to an entry called 'servicePrincipalName'.
Click the Edit button.
Type in the SPN using the following format (http/). For example, if your site is called “cwa.intel.com” then type in “http/cwa.intel.com”. NOTE: Do NOT type http://.
Click OK and you're done!

OCS R2 : Cannot Synchronize Address Book

Suggestion interessante dans le cas ou Communicator affiche le message : Cannot Synchronize Address Book

use the “Automatically detect settings” instead of specifying settings for a proxy server in IE
for IE7 under Advanced / Security, uncheck the option “Check for server certificate revocation” and restart the browser (manually or via Group Policy)
ascertain that the URL listed on the certificate points to the Certificate Revocation List (CRL) Distribution Point that is reachable on the inside and/or outside network
if OCS is deployed with digital certificates issued from an internal CA, add the .crl URL to the Trusted sites or Local Intranet zone on the Security tab in IE then exit and restart MOC e.g. http://*.swissitpro.ch. This enables the intranet URL for Address Book (AB) download to be recognized as safe and valid.
deploy certificates from trusted public Certificate Authority (CA) permits both domain and guest (non-domain) accounts to connect to internal OCS pools

Cannot synchronize with the corporate address book

Nouveau problème soulevé par un de nos clients aujourdhui suite a un changement de certificats :

Communicator affiche en haut à droite le message suivant “Cannot synchronize with the corporate address book because the file could not be found. Please contact your system administrator with this information.”.

Le certificat sur le site web par défaut de IIS ayant aussi était changé, on a résolu le pb en regénérant le carnet d'adresses :

- commande : abserver -regenUR

- commande : abserver -syncnow

puis supprimer le fichier galcontacts.gb situé dans Documents and Settings\<user>\Local Settings\Application Data\Microsoft\Communicator

Fermer Communicator puis relancé le.

Communicator 2007 R2 Evaluation qui expire prématurément

Un bug dans dans la version d'evaluation de communicator 2007 R2 a provoqué une expiration prématuré (180 jours d'evalution) des client. Panique, mais voila la solution et la cause :

This update package fixes the following issues:

The license expiration date for Office Communicator (OC) 2007 R2 Evaluation Edition was calculated incorrectly. This causes OC 2007 R2 Evaluation Edition to expire on June 13, 2009. This update fixes the license expiration date calculation for the OC 2007 R2 Evaluation Edition. By downloading this update, the expiration date will be based correctly on the installation date of the OC 2007 R2.

Get it here:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=515d6dba-4c6a-48bb-a06a-d99c5742676d

Problème suite aux mises a jour d’avril d’OCS R2

Je vais faire part d'un problème que je viens d'avoir suite a une mise a jour effectué sur mon front end OCS R2 qui empeche le service de demarré :

Source: OCS AppDomain Host Process, ID: 50007

An unhandled exception was encountered.

Exception Details. System.NullReferenceException: Object reference not set to an instance of an object.
2 Microsoft.Rtc.Server.McuFactory.McuFactoryHost.Main(String[] args)
2 Microsoft.Rtc.Server.McuFactory.ExecutableEntryPoint.Main(String[] args)
2 System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
2 System.AppDomain.ExecuteAssemblyByName(String assemblyName, Evidence assemblySecurity, String[] args)
2 Microsoft.Rtc.AppDomainHost.Launcher.AppDomainLauncher.RunThread()
2 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
2 System.Threading.ThreadHelper.ThreadStart()
Cause: One of the applications identified in the eventlog description failed.

Resolution:

Restart the server. If the problem persists contact product support.

Pour résoudre ce problème :

1. Uninstall all Frameworks on server.
2. Download and install a last version of Framework (3.5 SP1) from Microsoft site.
3. Download and install NDP20SP2-KB958481-x64.exe, NDP30SP2-KB958483-x64.exe, NDP35SP1-KB958484-x64.exe updates.
4. After that Windows update installs to updates to Communication Server (April and some for Monitoring Server, before that it don't want to install April updates).
5. Reboot server, services started.

Le 1er post

Merci à William pour m'avoir ouvrir un espace dans ce merveilleux cloud, j'espère que j'en serais à la hauteur!

Je vais à court terme déplacer ici le contenu de mes posts de mon blog http://ocsfrance.spaces.live.com/ et de mon site http://nissarte.fr.

Ici seront regroupés toutes mes expériences professionnelles, mes recherches, mes tests autour des communications unifiées de Microsoft.

Bienvenue a vous sur mon blog.

Le Cloud de Christophe BOUCETTA