You can turn up logging on that process.
In the EMS type Set-eventloglevel "MSExchange EdgeSync\Synchronization" -Level 
Expert

For a list of all Processes with Configurable Event Logging Levels see the 
following link.
http://technet.microsoft.com/en-us/library/bb201661(EXCHG.80).aspx

Typically you can do a Set-eventloglevel and it will give you all the current 
logging levels of all processes.


Chuck Robinson, MCSE: Messaging, VCP
Senior Practice Consultant
EMC Global Services, Microsoft Practice
tel 732-321-3644 xt.45, mobile 973-865-0394, fax 732-321-6855
email: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>
www.emc.com/mspractice<http://www.emc.com/>

From: Angie Urtel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2008 2:35 PM
To: MS-Exchange Admin Issues
Subject: logging for edge synchronization?

Is there such a thing as a log file or some way for me to get more information 
on why my edge synchronization is not staying synched?  I thought it might show 
up in the App log, but no such luck.  Ops Mgr is alerting on it, so that's how 
I know it isn't working as expected.  I can start the synch manually, but I'd 
rather find the source of the problem.  Not having much luck with The Google.

Name                        : gatewayServer
LeaseHolder                 : transportServer
LeaseType                   : Option
ConnectionResult            : Succeeded
FailureDetail               :
LeaseExpiry                 : 4/2/2008 2:10:34 PM
LastSynchronized            : 4/2/2008 1:10:34 PM
CredentialStatus            : Synchronized
TransportServerStatus       : Synchronized
TransportConfigStatus       : Synchronized
AcceptedDomainStatus        : Synchronized
SendConnectorStatus         : Synchronized
MessageClassificationStatus : Synchronized
RecipientStatus             : NotSynchronized

I don't know if this is a new occurrence or if it has always been the case.

Thanks,
Angie



~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~

Reply via email to