Vani Nathan: April 2009

Thursday, April 30, 2009

Process Tracking Log tool for Exchange Server 2007

There are many scenarios in Exchange 2007 Server which requires parsing, monitoring, and analyzing Message Tracking logs. For example, in transaction log file and / or Database growth scenarios, Server got hit with spam messages, Looping message scenario, Transport queue backup scenarios, and Server performance scenarios, and many other administrative, monitoring, and troubleshooting scenarios - it absolutely becomes necessary to review and analyze Message Tracking Logs. The amount of fields and tremendous amount of data present in message tracking logs, and the amount of extremely high messaging traffic that Exchange servers process these days ( i.e. the sheer size of message tracking log files ) makes it extremely difficult, if not impossible, to analyze these message tracking logs manually. The task is further complicated when you have to review message tracing logs from multiple servers, and especially on a pretty regular basis.
Process Tracking Log tool simplifies these tasks by automating the parsing and analysis of Message tracking logs, and then reporting it back by producing xls or txt output files with meaningful data, which is extremely useful in a lot of Administration, troubleshooting, and monitoring scenarios in Exchange 2007, as discussed above. Besides rich useful data regarding monitoring, administration, and troubleshooting, the tool also provides critical data on End-To-End Delivery Latency Distribution for all Messages Delivered, Server Latency Distribution for all Messages Processed and Server Latency Distribution for all Individual Deliveries.

USAGE:
cscript ProcessTrackingLog.vbs [ today yesterday ]

Wednesday, April 29, 2009

Exchange Server 2007 Service Pack 1

Anywhere Access
• Integrated Exchange Unified Messaging functionality with Microsoft Office Communicator 2007 and Microsoft Office Communications Server 2007.
• Outlook Web Access additions, including public folder access, S/MIME support, personal distribution lists, and mailbox rules editor.
• Webready document viewer supports Microsoft Office 2007 documents in addition to Microsoft Office 2003 documents.
• Extended language support in Outlook Web Access with Arabic and Korean spell checking.
Operational Efficiency
• Support for Windows Server 2008 deployments, including benefits in flexible clustering, advanced networking, and simplified management.
• Additional tools in the Exchange Management Console, including public folder management and configuration options for clustering and POP/IMAP access.
• Improvements to the Exchange Management Shell syntax and import-export PST in the move-mailbox command.
• Wider variety of web services for application development, including public folder access, delegate management, and folder level permissions.
Built-in Protection
• Addition of Standby Continuous Replication (SCR) for site resilient high availability deployments.
• Extended Exchange ActiveSync policies for mobile policy enforcement.
• Information rights management pre-licensing by the Hub Transport role.
• Secure Real Time Protocol (SRTP) support in the Unified Messaging role.
• Support for IPv6 when using Windows Server 2008
Standby Continuous Replication (SCR) feature.

SCR joins the other three HA solutions that Exchange 2007 SP1 provides, and is built on the "continuous replication" concept. This is where the database and the transaction logs are copied over to a secondary location -- whether that location is a disk, as in the case of Local Continuous Replication (LCR), or a passive node to a cluster, as in the case of Cluster Continuous Replication (CCR) -- and then replayed into the database.
SCR allows you to replicate your data to a different server or servers because it can accommodate multiple targets. It allows admins to establish a lag time to prevent a corrupt set of files from replicating before they can stop it. It also allows admins to replicate the passive side to a CCR or Single Copy Cluster (SCC), the fourth solution of HA that is offered by Exchange 2007.
The only downside is that SP1 doesn't include a way to accomplish SCR through the Exchange Management Console. It requires the use of the Exchange Management Shell (EMS) with PowerShell commands.

Monday, April 27, 2009

User get a Error 0x8004010F " the operation failed.An object could not be found " while doing a Send/Receive.

Resolution:

check for problems running the Offline Address Book Integrity Checker

rebuild the offline address book

Store.exe process uses almost 100 percent of CPU resources

Cause:
problem occurs because the index is not available when the Microsoft Exchange Information Store service tries to create an index-based view. It takes lots of CPU resource to create such views. Additionally, such views require lots of temporary table space. The space requirement causes the database to increase.

Resolution:
Apply update rollup 1 for exchange server 2007 service pack 1

Workaround :

Move public folders to a server that is running Microsoft Exchange Server 2003.
Turn off the Microsoft Search Service in Exchange Server 2007.
Use an address list instead of sharing contacts in public folders.

Tuesday, April 21, 2009

Microsoft Forefront

Microsoft Forefront delivers end-to-end security and access to information through an integrated line of protection, access and identity management products.

Forefront Security products deliver protection, access, and management solutions, built around user identity and integrated with a highly secure, interoperable platform.
Microsoft is working to achieve the goal of business ready security based on 3 fundamental tenets:
Integrate and Extend Across the Enterprise

· Deeply integrates with the identity infrastructure and across the stack

· Support for heterogeneous environments

· On-premises and hosted solutions for seamless connectivity

· Open standards and protocols based identity and security platform
Help Protect Everywhere, Access Anywhere

· Defense in depth across multiple layers to help protect across endpoints, servers, and network · Secure identity-based access products help connect the mobile workforce virtually anywhere

· Identity-aware protection help organizations secure information and enable policy-based access
Simplify the Experience, Manage Compliance

· Enable centralized management of the environment and gain critical visibility into the state of the infrastructure

· Help improve security and compliance through identity tracking and enforcement throughout the enterprise

· Provide policy management features and reporting to enable auditing and compliance

Saturday, April 4, 2009

Exchange Store Won't Mount

Information Store
Is the Microsoft Exchange Information Store (MSExchangeIS) service running?
Can you successfully start the Information Store service if it is stopped?
If you cannot start the Information Store service, is the Microsoft Exchange System Attendant (MSExchangeSA) service started?
System Attendant
Is the Microsoft Exchange System Attendant service started?
Can you successfully start the System Attendant service if it is stopped?
If you successfully start the System Attendant service, make sure to start the Information Store service as well.
refer :http://go.microsoft.com/fwlink/?linkid=3052&kbid=245024).
Anti-virus software comes in two flavors as far as Exchange is concerned: generic and Exchange-aware. If you are using generic anti-virus software (that is, software that is not Exchange-aware), make sure that you are not scanning your Exchange data directories.
try disabling your anti-virus software and then restart your Exchange server

Mount a Blank Database (Enterprise Edition Only)
If you are trying to isolate the problem and are not sure if the problem is with a particular database, you can try to mount a blank database. If you can successfully mount a blank database, you know that your existing database has a problem. When mounting a blank database, do not move your current database files, simply create a new database. If you have used all 20 of your allowed databases, you can create a database in a recovery storage group to do the test. If you are using a recovery storage group to test mounting a blank database, either restart the IIS Admin Service (IISADMIN) or wait 15 minutes before attempting to mount the new database so that the Active Directory® directory service caches are refreshed.

Problems with the Database
Are you running Exchange Server Standard Edition? If so, has the server reached the 16-GB store limit? If you are running Exchange Standard Edition, your mailbox stores will dismount when you reach the 16-GB size limit.

http://go.microsoft.com/fwlink/?linkid=3052&kbid=828070

Is there a -1018 or -1022 error in the application log indicating a problem with your physical storage? See Knowledge Base article 314917

Verify that the database was shut down in a clean (consistent) state. Use ESEUTIL /MH. If the database is shutdown in a dirty (inconsistent) state, you cannot mount it and you must replay at least one transaction log file to bring it to a clean state.

If you receive the following errors, here are some things to investigate.
C1041724
Error c1041724 is "An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both." For general information about this error, see Knowledge Base article 294318, "C1041724 Error Occurs When You Try to Mount a Database" (http://support.microsoft.com/?id=294318).
Check permissions on the folder that the TMP variable points to. Exchange needs full control permissions for the root of the drive with the transaction log files and database files and all subfolders between the root of the drive and these files. See Knowledge Base article 307242, "Information store does not mount with 0xfffff745 and -2235 errors" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=307242).
Check the application log for MSExchangeIS Event ID 9519. See Knowledge Base article 312873, "Mailbox Store or a Public Store May Not Mount with Error -344" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=312873).
Check the application log for MSExchangeIS Event ID 1088. See Knowledge Base article 280652, "XADM: "Event ID 1088" Is Logged and Store Fails to Mount" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=280652).
Check to ensure that the store you are trying to mount has the Allow inheritable permissions to propagate to this object check box selected. See Knowledge Base article 827283, "You receive a c1041724 or c1041722 error message when you try to mount an Exchange 2000 Server mailbox store" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=827283).
If you receive this error when trying to mount a store that has just been restored from backup, make sure hard recovery has completed. See Knowledge Base article 253931, "Mounting a Database After Restore Fails with Error Message c1041724" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=253931).
Check to see if a second SystemMailbox object exists for the store you are trying to mount. See Knowledge Base article 274534, "XADM: Event ID 9175, 9546, 9519 Messages Occur When Mailbox Store Fails to Mount" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=274534).
Check to make sure another copy of the same database is not running. See Knowledge Base article 280753, "XADM: Event ID 9175, 9546, 9519 Messages Occur When Mailbox Store Fails to Mount" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=280753).
Check the log file drive to ensure that it has adequate space. You may see MSExchangeIS Event 9519 and 9559 in the application log. It is important that you do not simply delete transaction log files to make more space. These files are part of your Exchange database. For information on moving log files, see Knowledge Base article 821915, "How to Move Exchange Databases and Logs in Exchange Server 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=821915).
Check to make sure your E00.log file has the correct signature. See Knowledge Base article 294367, "You Cannot Mount the Database, and Receive Events 9518 and 455" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=294367).
Check to see if the MDBDATA folder that contains the files for the store you are trying to mount has the proper permissions set on it. See Knowledge Base article 823022, " 'ID No: c1041724' Error Message and Event ID 491 When You Try to Mount the Mailbox or the Public Store" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=823022).
C1041722
Error c1041722 is "The Microsoft Exchange Information Store service could not find the specified object."
Try restarting IISADMIN and Windows Management Instrumentation (WMI) to clear the directory cache. If you have created the database recently, wait a few minutes for Active Directory replication.
Check to see if the Everyone group has been assigned explicit Deny permissions on the root of the Public Folder hierarchy in Exchange System Manager. See Knowledge Base article 823017, "Event ID 9519 When You Try to Mount a Public Folder Store" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=823017).
Check to ensure that the store you are trying to mount has the Allow inheritable permissions to propagate to this object check box selected. See Knowledge Base article 827283, "You receive a c1041724 or c1041722 error message when you try to mount an Exchange 2000 Server mailbox store" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=827283).
Check to see if the Exchange Domain Servers group has Full Control permissions on the Server objects in Active Directory. See Knowledge Base article 313865, "XADM: Public Folder Store Cannot Mount with Error c1041722" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=313865).
Check to see if the Exchange Enterprise Servers group has the Manage Auditing and Security Logs permission set. See Knowledge Base articles 281537, "XADM: Description of the Policytest.exe Utility" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=281537) and 290189, "XADM: C1041722 Error Message Occurs When You Attempt to Mount Databases" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=290189).
C1041737
Error c1041737 is " The name of one of the database files in this store is invalid."
This error may occur if there are problems with your storage media. The application log may show MSExchangeIS Event IDs 9518 and 9519. An ESE Event ID 470 may also be logged. See Knowledge Base article 300608, "XADM: A "C1041737" Error and an Event ID 470 Message May Be Displayed When You Attempt to Mount Databases" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=300608).
Check to see if the Everyone group has Full Control permissions on the drive. Not having this permission may sometimes cause this error.

Vani Nathan

Thursday, April 30, 2009

Process Tracking Log tool for Exchange Server 2007

Wednesday, April 29, 2009

Exchange Server 2007 Service Pack 1

Monday, April 27, 2009

User get a Error 0x8004010F " the operation failed.An object could not be found " while doing a Send/Receive.

Store.exe process uses almost 100 percent of CPU resources

Tuesday, April 21, 2009

Microsoft Forefront

Reading

Exchange 2010 Beta is available

Reading

Saturday, April 4, 2009

Exchange Store Won't Mount

About Me

Blog Archive

Blogs

Favourites

Tips