Mon serveur exchange fonctionne parfaitement dans le réseau local.
Le webmail aussi fonctionne tres bien.
 
Cependant, j'ai voulu démarrer le service POP (serveur,POP 3, click droit démarrer), et la, impossible de démarrer, il veut pas.
 
'le service n'a pas répondu assez vite a la demande de lancement ou de controle'
 
Quelqu'un a une idée?  

up

up

up

up

Chercher dans l'eventlog le message d'erreur + www.eventid.net
 
Eventuellement utiliser la commande "net start [nom du service]" qui donne un numéro d'erreur.

oui, mais ca me dit rien de plus
 
 
Event ID: 929  
Source MSExchangeTransport  
Type Error  
Description Failed in reading Connector's DS Info Process Id: <id> Process location: <location> ConnectorDN: ConnectorDN  
Details Comments and links for event id 929 from source MSExchangeTransport  
     
Search Event id 929  :   Microsoft Support  -   Microsoft Search  -   Google Groups  -   Google Microsoft  -   EventID.Net Queue  
Submit New event id 929  

 
Il faut peut-être cliquer sur le lien pour afficher les commentaires, non ?
 
Event ID: 929  
Source MSExchangeTransport  
Type Error  
Description Failed in reading Connector's DS Info Process Id: <id> Process location: <location> ConnectorDN: ConnectorDN  
Comments Ionut Marin (Last update 6/22/2004):  
According to Microsoft this problem may occur in situations where the hotfix that is described in Q328905 is installed on the server, and where a NULL value is incorrectly dereferenced in Phatq.dll. See Q811302 for more information.
 
Also from Microsoft: "This problem occurs if you do not remove the Exchange 5.5 Connectors before you remove the last Exchange 5.5 server". See Q322123 to fix this problem.
 
Anonymous (Last update 2/16/2004):  
I started seeing these errors after I installed Faxmaker on my new Exchange server and then uninstalled it from my old Exchange server. The old server is still on the wire, but Exchange has been uninstalled.
 
Jeremiah Watson (Last update 2/16/2004):  
If you have an SMTP Connector in your first routing group without a default bridgehead server this can happen if you install a second server and remove the first. The fix is to add the second server back as the default server.
 
Ryan Russell (Last update 11/8/2003):  
As per Microsoft: "This problem can occur if the Exchange 2000 routing engine encounters an error when communicating with Active Directory. Because of this error, the routing engine does not update the routing table". See Q282506 for more details.
 
Alastair Smith (Last update 11/8/2003):  
I had this problem too but it was something far simpler. My problem was linked to an Exchange server being removed from the organization but its properties retained with the ''local bridgehead servers'' within the smtp connectors properties. All I had to do was to correct this so that only valid servers were used

Ensuite tu prends les numéros QXXXXXX tu fais un copier-coller (sans le Q, juste le numéro) dans Google et tu trouveras les articles chez Microsoft.

Parceque ce topic parle du prb que j'avais, j'y ajoute ce que j'ai trouvé.
 
 
J'avais le même prb, impossible de démarrer le service POP3 via la MMC d'Exchange.
Il suffit de passer le service (dans la liste des services de la machine) en manuel (ou automatique) au lieu de "Désactivé". Ensuite, il démarre sans prb..