How to solve Exchange SMTP server error ’5.7.1 Unable to Relay’?

While using Outlook with Exchange server a user can have to face several kinds of errors. Most common among them are the SMTP errors.

Common SMTP errors are 550 5.7.1 'Unable to Relay', error code 5.0.0, 5.7.1, or 5.7.3 etc. 501 5.7.1 is another error code that can occur if there are problems while relaying email through Exchange. Just like 550 5.7.1 it also indicates that the user email client failed to authenticate on the mail server.

These error codes basically indicate Non-delivery report of a mail or email relay issues. It can happen if the recipient doesn’t allow relay, then the sender will not be able to reach or that the receiver domain is restricting the sender domain from relaying the message.

Symptoms that indicate email relay issues: 

• The Email delivery fails with error code  5.0.0, 5.7.1, or 5.7.3
• If the number of domains increases then You starts facing troubles while sending mail
• Your Exchange computer starts sending unsolicited commercial emails that appears in your mail queues. Also you can receive information from a remote domain that your Exchange computer sent an unsolicited commercial email to it.

'550 5.7.1 Unable to Relay' code error:

550 5.7.1 Unable to Relay’ code error generally occurs when the user tries to send emails outside his domain.

Causes for the error:

• The outgoing mail server could not identify the sender.
• There are some issues while authenticating the sender on the server and thus restricting them to send emails.
• The receiver domain’s recipient policy has imposed restrictions on the sender’s domain / department. The Exchange Database is corrupt.

Fix Exchange Errors & Restore All Mailboxes with Microsoft Exchange Recovery Software

How to resolve the error '550 5.7.1 Unable to Relay'

For Exchange 2003: If you have been using any CRM application such as SharePoint or Dynamics and facing the above error: "550 5.7.1 Unable to relay". In such case, you need to relay off the Exchange server 2007 by allowing application servers. You have to implement some relay restrictions on the virtual server. The application event log stores the error list that occurs in the Exchange environment. You can view the event log; go through the error causing aspect and then find its solution accordingly.

In order to resolve the problem in Exchange 2003, you need to implement a few restrictions on the SMTP virtual server.

• Start Exchange Server Manager.
• Go to the Administrative Groups
• Select Administrative Group Name -> Server -> Server Name -> Protocols -> SMTP.
• Right click Default SMTP Virtual Server and open Properties.
• Go to Access tab > Relay > ‘only the list below‘.

This will open a window where you can add the IPs to be relayed and your domain.

• Select the checkbox ‘Allow all computers which successfully authenticate to relay, regardless of the list above‘.

For Exchange 2007: You need to configure the Exchange server so that it can accept and relay email from the hosts (the host authentication is implemented by default).

The permissions to submit and relay are set within the ‘Permissions Group’. The authenticated users can be granted following permissions:

NT AUTHORITY\Authenticated Users {ms-Exch-SMTP-Submit}
NT AUTHORITY\Authenticated Users {ms-Exch-Accept-Headers-Routing}
NT AUTHORITY\Authenticated Users {ms-Exch-Bypass-Anti-Spam}
NT AUTHORITY\Authenticated Users {ms-Exch-SMTP-Accept-Any-Recipient}

"Only the list below (specify IP address)", you need to use this option for those users that aren't authenticated with Exchange server, one such situation is when you are using an application server that relays messages through Exchange.

Steps to create a new SMTP Virtual Server:

• First create a new SMTP receive connector.
• Specify the remote IP Address(es) in the "Remote Network settings". Only the specified IP Address will be allowed to submit a mail rest else will not be permitted to relay.
• Open the properties of the connector. Now you will get two options: the first option is: "Make your new scoped connector an Externally Secured connector" and the second option is "Grant the relay permission to Anonymous on your new scoped connector".
• Choose the first option if the submitted mails are intended for internal users as well as outside world. First open the CRM application properties. Select the check-box Exchange servers to the enable the Exchange Servers permission group. Click OK. Now go to the authentication tab and specify the security mechanisms which are available for incoming connections.
• Using the second option you can specify who is allowed to connect to this receive connector. First select the checkbox 'Anonymous users' to add the 'Anonymous users' Permissions Group to the connector.

You need to go to the Exchange shell for granting the relay permission

Get-ReceiveConnector "CRM Application" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"

You can have to face several issues while relaying an SMTP Receive Connector for Exchange. I am especially taking the JIRA install into consideration. Such common problems faced by user while setting up a SMTP relay in JIRA install are: The user name will be removed from the ‘From’ field, Emails will be still submitted to external domain addresses or the user's name will stay intact in the ‘From’ address field   but the emails couldn’t be submitted to outside domains.

Follow the given steps to setup SMTP relay in Exchange 2007 for JIRA:

• Go to Exchange MMC > Server Configuration > Hub Transport.
• Select the desired Hub Transport server.
• Then, select the "New Receive Connector" to open the "New SMTP Receive Connector" wizard.

• Enter the relay name & select the suitable option from the dropdown list "Select the intended use for this Receive connector"
• Go to the ‘Local Network settings’ tab and enter your Exchange Hub Transport server’s address under the option "Specify an IP address". Before Entering the FQDN first remove default "All available IPv4 addresses". Then click ‘Next’. 

• Go to the ‘Remote Network settings’ tab>Add. Fill the IP address of the JIRA server in the IP address field. Click OK 

• First Delete the default filled values and proceed further by clicking Next
• Click Finish, once the process is completed.

Now, the newly created for connecter will be shown in the list where others have been already listed. To recheck and verify its attributes, simply double click to open properties. Go to general tab and check whether FQDN is correct or not. Go to network tab and check for the details you have entered in the IP addresses. Now go to Authentication tab and ensure that only ‘Transport Layer Security (TLS)’ is selected there.

• Go to the ‘Permission Groups tab’ and select the checkbox ‘Anonymous Users’.
• Go to Exchange Management Shell and run the command
• Get-ReceiveConnector "JiraTest" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"
• Here, JiraTest is name of the connector that was just created.
• Once this all is done, you can now relay JIRA's emails via Exchange.

The Exchange error code 5.7.1 can also occur due to edb database corruption. In such case you need to repair the corrupt database using utility Eseutil. If it fails to recover your data then you need some powerful Exchange recovery software.

Read more

10 Useful Tips For Troubleshooting Some Common MS Outlook Errors

When MS Outlook halts, output and critical business interactions take a big hit. These troubleshooting actions will aid you fix issues swiftly.

Outlook is presently the side aspect standard email client in the corporate world. Normally speaking, it works like a champion. But at many times, Outlook goes down in a ball of flames. When that occurs and if you are not having a mass of tricks to pullout of your bag, you might discover yourself in a world of pain.

But troubleshooting MS Outlook doesn't have to be a terrifying. In fact, you can more or less script out the troubleshooting practice with these ten helpful tips.

1: Scan PST

PST files will unavoidably build up errors. When they do the same, they can stop Outlook from working accurately. When Outlook is starting to fuss, one of the primary things you should carry out is to run scanpst.exe against each PST file used in Outlook. But be informed: PST file scanning can take some time to run. The scanning process should  take a backup of  your data file, scan for inaccuracies. If the file is quite large, this scan procedure can take a fairly good amount of time. To run Scan PST, you will be required to find the scanpst.exe executable.

2: Rename OST

If users take benefit of a locally cached data file, occasionally re-naming their present OST file is adequate to fix ample of problems. Just close Outlook, open the folder that houses their data files, make sure you can see extension names, and change the .ost extension to something like .old. The next time Outlook opens, it will rebuild that .ost file and Outlook work as it has been installed today itself

3: Archive

Though not actually a troubleshooting tips works , there are times when a PST file will get out-sized which creates troubles with MS Outlook. Instead of allowing that PST keep on to get unmanageable, it is best to set up archiving. When the data file has reached the excess of users' allocated space, I always encourage them to archive by year. This technique makes sure that they will be archiving the biggest amount of data to their local directory which clears up some space on the server. This will also reduce the size of the PST and lessens problems connected with a too-large PST files. Once you are done with this, you are recommended to run Scan PST.

4: Disable add-ons

The more add-ons that connected to Outlook, the slower it becomes. If you have any doubt, start Outlook in safe mode (issue the command outlook.exe /safe) and see how much faster (and smoother) Outlook runs. If you find this to be the case, go into the Trust center, disable suspect add-ons, and restart Outlook normally. You'll know when you've found the culprit, as Outlook should run normally. This is a tedious exercise, but one that will generally bear fruit.

5: Delete/rebuild profile

When all else be unsuccessful (and don’t want to uninstall/reinstall), remove the Outlook profile. Now you have to be careful with this. If Outlook is functioning with a POP account, the present Inbox (and calendars, contacts  etc.) will require to be exported as a data file. If Outlook is connected to either IMAP account or to an Exchange server or this practice is just a matter of removing the profile and re-including it. To perform this, you need to open the Control Panel à Go to Mail à Profiles à Delete the profile.

6: Run in safe mode

As we have talked about earlier, running outlook in safe mode is a good approach for troubleshooting. The one limitation is that some features will not work properly. This clearly means that running in safe mode is not a way out for a trouble, just a technique to assist debug it. Occasionally, just the act of running MS Outlook in safe mode will fix the issue at hand.

7: Disable virus scans

Many antivirus software has an Outlook connector that scans mails as they received and sent out from a machine. In some cases, these antivirus scanning can slow down Outlook to a crawl. If you are not sure where an Outlook problem is branching from, for the time being halt the antivirus Outlook connection to observe whether that resolves the problem. If it does, you might require to update the antivirus software to resolve the issue. Just keep in mind, if you depart that connection wrecked, Outlook will be susceptible.

8: Migrate PSTs from the server

We have noticed this happening so frequently. A user will have oddly big PST files (specially archives) stored on a redirected (or shared) drive on a server. Those files are best served up from the local drive. If you are having more than one PST file required to link to a distant location, probability is Outlook will be bogged down. You need to then move those archives files to the C drive of the local system to enhance efficiency.

9: Run with resetnav

When you give the command outlook.exe /resetnavpane, you reset all customizations to Outlook's navigation panel.  This is essential when users have completed something to the navigation panel  that leads to MS Outlook malfunctioning or the occurrence of some other problems. It is important to note that users will likely to lose some of the customizations made to the navigation panel.

10: Adjust calendar permissions

If somebody sends an invite for others to make use of his or her calendar, but they are not able to create or revise appointments, so you need to alter their permissions. For that,  open the calendar in Outlook, right-click on the shared calendar, click on Properties, and then go to the Permissions tab. There, you can include users to the calendar and give them particular permissions that will permit them to perform anything from owning to reading the calendar.

If you are still unable to fix the above errors, then this problem can damage or corrupt  your OST files. If your OST file gets damaged or corrupt, then in that case, you can stay away from this situation by sustaining backup in the form of PST. You can make use of any third party converter which can convert your important OST files into PST files. We can suggest you one reliable conversion software: "Stellar OST to PST Converter" which efficiently converts your OST files into PST files.

Read more

OST To PST Conversion: A Quick and Effective Way To Repair Corrupt OST Files

Information or Data are the most significant attribute for any industry. In fact it indicates the business progress and its potential. Be it a small or a big enterprise, all of them communicate via emails to exchange data and MS Outlook is one such email client which is being widely used by business to communicate with their clients or customers through emails. User can execute all essential everyday jobs such as email formation, file transfer, sending and receiving emails,  reading existing mails, saving contacts and much more. Outlook is the only mailing application where users can check their emails even when the Internet is unavailable. 

MS Outlook stores files in OST and PST format. OST (Off-line Storage Table) files are usually accessed by the users when Exchange Server is in off-line mode. The synchronization of OST file with Exchange Server is the greatest part of the MS Outlook which enables users to carry on with their work even in the absence of Exchange Server. The user is guaranteed that all the revisions made in the data will be synchronized with the network as soon as the Outlook gets in contact with Exchange server. Where as PST files are the backup files of the Exchange EDB and are saved on the local system's hard drive and can be used whenever needed.

However, MS Outlook is the easiest and simplest to handle email client application but offensive or wrong treatment can result in the malfunctioning of this email client. The hazard of getting data loss is not a newfangled thing as this is happening since the subsistence of the data itself. But the negative effects of data loss are much more relentless in the current situation. From past seven to eight years, nearly every office has got digitalized and each and every important information is stored in the system’s database. In the course of time worth of data has augmented so as the threats related with it. There are several circumstances in which user can experience the damaging or corruption of Outlook files which results in loss of data.

Software Issues:-

1. Virus attack.

2. Unable to synchronize data in a sequential manner. That leaves data useless.

3. Installation of malicious software

4. Finished Outlook data storage memory which varies from version to version of MS Outlook

5. Unusual termination of the Outlook program

6. Removal of Exchange Server log file - edb.log from the Server.

7. Overwriting of garbage data due to bad file system consequences in corruption of OST files.

Hardware Issues:-

1. Bad sectors in hard disk can simply corrupt OST files as the particular folder is stored on it.

2. If the network problem occurs while synchronizing data some which stops the course of action. Then it will result in corruption or damaging of OST files as data is labelled as invalid

3. Power failure is one more issue that can halt the synchronization process which leads to OST files corruption.

Apart from the above talked about aspects, there are many other known/unknown reasons which are responsible for corruption of Outlook data file. By asset of all above listed inaccessibility causes, Outlook offers an integrated utility “Scanost.exe” for repairing corrupt/damaged OST file

  

Simple steps to repair corrupt/damaged OST file using Scanost.exe are as follows:

·         1. Quit Outlook

·         2. Open Scanost.exe, located in “drive:\Program Files\Microsoft Office\OFFICE12”

·         3. Select and Click the profile that include the required OST file.

·         4. Opt for Repair Errors check box.

·         5. Click on “Begin Scan”.

  

But OST Integrity Check utility is not accessible with MS Outlook 2010 and 2013. Also the most important failing with Scanost.exe utility is that occasionally it does not repair the corrupt file. Instead it substitutes the file with new data in rigorously corruption circumstance. In case, if the above integrated utility does not work, you can stay away from this situation by sustaining backup in the form of PST.

Flourishing technology has given birth to superior and efficient OST to PST conversion tools, which delivers supreme outcomes to its users. This tool has become one of the most demanding tools in the present times. Companies which are facing a problem with email data loss can spend into a superior email data recovery tool and get back their important OST files along with its elements. A potent tool converts complete OST data, comprising tasks, journals, contacts, appointments, attachments, notes, and many more.  All the recovered data of OST files gets restored in PST file format. But it is worthwhile to opt the tool sensibly as the bad or incompetent tool will make the circumstances even worse.

We can suggest you one proficient tool which provides extra features to smoothen the process of the conversion. Stellar OST to PSTConverter lets the user to execute conversion competently due to its user- friendly interface and front-end technology. This conversion tool has been developed in a way, which can be effortlessly used by an amateur user as well. Its important features are given below:

1. OST to PST conversion

2. Search & Save mail messages in MSG and EML format                                  

3. Provide a preview of mail objects

4. Repair & convert damaged OST file

5. Save converted file at desired location

6. Safe & risk free conversion

The free demo version of the tool can be downloaded through its website which exhibits entire preview of the tool and enables users to check the compatibility with the situation.

Read more

Most Common Lotus Notes Error Messages and Their Solutions

Lotus Notes email application offers business teamwork functionality which includes sending/receiving emails, instant messaging, contact management, team-rooms, user directories, calendars, file sharing, blogs, micro-blogging, to do lists, and discussion forums. Lotus Notes also provide access and integration with other IBM Domino databases and applications.

Database files of Lotus Notes are prone to corruption due to a number of logical and  physical errors. Error messages are not only frustrations to Lotus Notes administrators and users but they are also call to action to fix the issues. We have assembled some of the most common Lotus Notes/Domino error messages and accompanying solutions and suggestion in this post. If you are also getting error messages when using Lotus Notes database files, migrating to Lotus Notes 8 or errors due to network connectivity, you will find the answers and solutions to fix it here. Check out most common Lotus Notes/Domino error messages along with their solutions below:  

Error 1. 'Your current ID does not specify an Internet certificate for signing'

This error message has caused confusion to end-user for many years, and usually it is generated when a user puts the default setting to sign emails.

In Lotus Notes, this is completed by means of the Public Key Infrastructure of your current Lotus Notes ID. Your client signs the messages to other Lotus Notes recipients with your public key.

To send the mail through Internet, Lotus Notes keys will not work. You need to have X.509 certificate incorporated into your Lotus Notes ID. Though, this is not common because those people who are not in a need, don’t get an access to these keys usually.

When the Lotus Notes client goes to sign the Internet message, it cannot discover a legitimate certificate to make use of, and causes the error. To hold back this, you need to alter the default setting of signing messages. If that is not achievable, then you can accept the dialog box when it comes out.

Error 2. 'Network operation did not complete in a reasonable amount of time'

Tip 1: It is recommended to open the "Replicator" page in your Lotus Notes client and manually trigger/reproduce the line, "Sending outgoing mail" (or a similarly named line).

Tip 2: In your Lotus Notes client, you need to open your existing "Location" and check the "Mail" tab. If the "Mail file location" is "Local," then adjust it to "On Server" to test it. Then, check the "Send outgoing mail" field. If it shows, "directly to Internet," then change it to "through Domino server" and you are done.

Error 3. Lotus Notes error: 'You are not authorized to the database for user's local mail file'

The Lotus Notes StdR7Mail template and 6.5.6 client don't fit in mutually, so you should not make use of R6 client with R7 design template as it is not supported. You should remove the local copy, and then update the server mail file with the help of  R6 mail template from R6 Notes client installation wizard. When you are done with that , replicate this back to the user's system. Many truly unusual problems have been observed from this kind of version incompatibility but It might not essentially be the actual reason, but you should get rid of this prospect prior to trying some other way.

Error 4. 'The object store that is used by this note was not found’. Run the object store COLLECT task on this database.

This error points to Lotus Notes Shared Mail, which is usually not used nowadays, as disk space has turned out to be economical and the exertion required in cleanup of such problems can be expensive and challenging.

Normally this error occurs when a Lotus Notes document that is trying to be read is not available in the Domino object store which leads to the generation of the error. Running “Collect” would clean up the reference, which can resolve the error.

Error 5. Domino server error message:' Entry Not Found in Index'

Earlier, this issue resulted from a locally edited policy. You are advised to try to edit or re-save all described policies straightforwardly on server copy of names.nsf. This will definitely resolve the issue.

Error 6. Database error: 'Database Corrupt -- Cannot Allocate Space'

The most probable reason of this database error is a problem with your Notes client's Desktop.dsk file. Running Nfixup or Compact on the Desktop.dsk file may lessen the problem. In some circumstances, generating a new copy of the corrupted or damaged database will resolve this problem. The copy should be created either at the OS-level or through the Database File in Notes.

If running Nfixup at the server console is not a choice, as in this situation, then you need to remove cache.ndk and rename it as bookmark.nsf.

Error 7. Lotus Notes 8 migration error: 'Database has not been opened yet'

Usually, LotusScript code produces this error when it generates a null database object handle and then attempts to function with this null database object handle. This could happen if the file or server path is incorrect or if the existing machine cannot connect to the end server. Most probably, however, the user does not have a right to access the end database.

If you are still unable to get rid of the above errors, then this problem might corrupt or damage your NSF files. If your Lotus Notes file gets corrupt due to the above physical or logical errors, then in that case, you need to make use of any recovery software which can repair corrupt or damaged files.  These tools have superior features and advanced algorithms that can aid you to repair and recover from serious corruption circumstances and one such reliable tool is "Stellar Phoenix Lotus Notes Recovery Software" which is a great tool to recover and repair your important data.

Read more

How to resolve Internal Error (Code=0000000E) of OST File in Outlook?

The Outlook data files (OST and PST) are the core of Outlook. If there is some issue with these data files ten Outlook cannot work properly. Of you are using Outlook without Exchange then all the Outlook user mailbox data is stored in a PST file that is stored in the user’s local system. It is used for POP3, IMAP, and web-based mail accounts.

In case, the Outlook is being used with Exchange server then an OST file is formed in the user’s local system. Whenever you are using Outlook in Exchange environment, a default OST file will be created. It is the exact replica of the user’s data residing on the Exchange server mailbox.  All Outlook mailbox data such as emails, attachments, calendar items, contacts etc. are stored in the OST file.

The default location for OST file is:

drive:\Users\user\AppData\Local\Microsoft\Outlook (for Windows 7 and Windows Vista)
drive:\Documents and Settings\user\Local Settings\Application Data\Microsoft\Outlook (for Windows XP)

The OST file has a pre defined maximum file size limit for Outlook. This limit varies with version of Outlook used; 2 GB for outlook 2000, 2002, 20 GB for outlook 2003, 2007 and 50 GB for outlook 2010.

When the PST/OST file size starts increasing and reaches the maximum limit then Outlook starts complaining, user starts facing problems while performing daily mail operations such as: sending and receiving mails.

The OST files provide ability to user to work in offline mode and cache exchange server mode. As, the Outlook files are replica of the Exchange database. If some changes all the done in the user mailbox then the same changes are reflected on the Exchange mailbox data as well as the OST file. If due to some reason Exchange isn’t available then at that time user can work in offline mode with the OST file. Once the connection to Exchange is reestablished the changes will be reflected to the user mailbox data present on the Exchange server. Thus, The OST file Provides facility to user to work offline while there is  Slow internet connection, temporary unavailability of Exchange server, sudden Exchange server shutdown or other temporary synchronization issue with Exchange synchronization.

Like other files, the OST files can also get corrupt due to several logical or physical corruption reasons. Some common factors that lead to OST corruption are:

• Virus or Malware attack
• The increasing size of your Outlook data files (OST/PST)
• Sudden outlook termination 
• Any kinds of interruption in the software update process
• Version or other Compatibilities issues with Operating system
• Hardware crash
• Outlook application isn’t handled properly, improper startup or closing of application.
• Improper system shutdown s
• Adds-on incompatibility of MS Outlook
• Abnormal system shutdown

Whenever the OST file gets corrupt or there are some synchronization issues. Then the Outlook complains and various error messages will be flashed on the screen.

Some common OST synchronization errors are:
1) Internal error (code=0000000E)
2) Internal error (code=00000003)
3) Error 8004011D-526-80040115-0
4) Service-specific error 0 (0x0)
5) error code 0x8004103b
6) error-message/c5e20916-9359-43fc-9bd9

In this article, I am going to discuss Outlook Internal error (code=0000000E). Let’s go ahead to know what is Outlook Internal error (code=0000000E), what are the probable causes and ways to resolve the error.

Outlook Internal error (code=0000000E):

While you are working with Outlook and you face the Outlook Internal error (code=0000000E). Then, it’s clear that either your OST file got corrupt or there are some problems while synchronizing OST file with Exchange.

Cause of the error:

• OST corruption
• Improper Synchronization of OST files.

In such situation, you need to correct the OST corruption/synchronization issues using inbox repair utility and OST integrity check tool.

Inbox Repair tool (Scanpst.exe):

Inbox Repair tool is meant to scan your Outlook data files (OST/PST) and check them for file system integrity. The tool only scans the OST file present in your system; it will not scan your mailbox residing on the Exchange server. It supports MS Outlook 97-2002, Microsoft Office Outlook 2003 and Microsoft Office Outlook 2007 data files.

It works in few simple steps, first it scans your Outlook data files, checks them for file structure integrity, if doesn’t find the file system intact then it rebuilds the headers to fix the issue.

To know the step by step repair process by Inbox Repair tool, Read my previous article: ‘http://recover-email.blogspot.in/2012/08/fix-it-unknown-error-has-occurred.html’

There are several situations when Inbox Repair tool fails to resolve your problem. In such case you need to search for more powerful OST recovery method.

First of all let’s see, where does Inbox Repair tool lack?

• It cannot efficiently deal with PST files of large size.
• Sometimes, it scans the corrupted files and shows no error in the result.
• User can also have to face situations when it discovers errors, the user run the repair process, but the recovery process stops in-between Thus, leaving the corrupted file behind. Or it may also cause further loss to your data files. So, don’t forget to backup your data files before starting the repair process.
• It has 2 GB file limitation. Running the tool on the files having size 2 GB or more is totally unusable and waste of time
• It couldn’t recover intentionally or accidentally deleted mail items from your Outlook mailbox.
• The OST repair process is slow. The OST recovery time increases and efficiency decreases with increase in size
• You cannot perform OST/PST recovery using Scanpst.exe, if outlook is not installed properly
• It fails to repair the data if corruption is severe. It only works fine for minor corruptions.
• It can deal only with the file header corruption issues; it fails to recover the data if the corruption is in body part of the data file
• If during repair process, it discovers some unrecognized data then it simply deletes it. Thus, it turns out to be drastic instead to helping as it may cause you to lose some of your important data items.
• It cannot repair the password protected files.

Suppose you are facing some Outlook issues and you can run the inbox repair utility and OST integrity check tools to scan the files, diagnose the errors and then fix them. If you are running the inbox repair utility on OST file of Outlook 2003 or above version. Then there are chances that the Outlook “internal-error-code0000000e” flashes on your screen. 

In such case you require powerful OST recovery software that can efficiently scan the corrupted files and fix the OST corruption or synchronization related issues.  The OST recovery software repairs the corrupted OST file and save the repaired items into PST format. You can import the recovered PST file into Outlook and access the data within it. Different vendors provide various OST recovery software and services. 

You can find the list online along with Demo versions available at their official sites. Run the Demo versions, evaluate their functioning and choose the one that best suit your needs.

To know about other OST synchronization errors, read my upcoming articles.

Read more

How to rebuild Priv.edb and .stm files in Exchange?

About Exchange Information store:

The core elements of Exchange Information store are Extensible Storage Engine and storage files (such as: database file, native content file, transaction logs, checkpoint files, reserved logs and other files).

The Exchange information store consists of transaction logs and storage groups that further consist of mailbox stores, public stores and mailboxes. The default location of Exchange Information Stores is MDBDATA folder. However, the user can also choose to move the data to a custom location of his choice.

Each Mailbox Store contains one Priv1.edb & Priv1.stm file. Similarly, the Public Folder Store contains Pub1.edb & Pub1.stm files. Each edb file has a corresponding stm file. A STM file is the streaming media file that stores multimedia data in MIME format. The amount of data stored in a STM file varies in different cases such as: STM file contains a little amount of data if MAPI Outlook protocol is used. The POP3 or IMAP clients store larger amount of data in STM files. In case of OWA, all the mailbox data is stored in EDB file, the STM file will contain the sent attachments.

The exchange provides Public Folder Replication feature which lets it create, maintain and synchronize the multiple instances of the same public folder on different Exchange servers. This feature increases the fault tolerance and efficiency of Exchange server as it keeps the public folder data replicated and provides access to a local copy of a public folder.  Thus, it provides more security and accessibility for an organization/user to work in a distributed network environment.

Exchange Log files: The Exchange transaction log files record all the information about a transaction that is being committed to the Exchange database.

Exchange database contains three types of log files: current transaction log (E##.log), secondary transaction logs (E#######.log), reserved log files (Res1.log& Res2.log)

The secondary transaction files are numbered sequentially starting with E0000001.log. ## indicates the Storage Group identifier.

The log files can prove to be helpful, if a user requires recovering the database from disaster or crash. If the user doesn’t have a valid recent backup then he can roll back the transactions to reach back to the previous state.

Just like other data files, Exchange database files are also prone to corruption. There can be various software or hardware reasons for the corruption of EDB database.
Such as:

• Conflicting firewall, malware protection, or Antivirus application
• Increased size of EDB database
• Accidental shutdown
• Power failure
• Virus attacks
• Hardware/system crash etc.

You can repair and recover the corrupt Exchange database by running Eseutil and Isinteg commands but there are several cases when these inbuilt repair utilities fail to perform efficient Exchange recovery. If you run eseutil /P command or eseutil /mh for data recovery, it may be possible that you get an error,” .STM file doesn't match the *.EDB file that resides on the server” Or other similar error messages indicating the failure of Eseutil and Isinteg utilities.

Consider the scenario: if the Exchange store has been shut down accidentally, you are not able to load your data from backup, the exchange database has got corrupt and Eseutil & Isinteg utilities both couldn’t recover the data. Then, what would you do in such situation? Your all work will be hampered so, in such situation you can create new edb and stm files so that, the users can continue working with their Exchange mail accounts.

Follow the given steps to rebuild a priv.edb file using log files:

• Ensure that you have all log files from E0000001.log to E00.log.
• Stop all the running Information Stores Services.
• Rename the MDBDATA folder
• Create a new empty MDBDATA folder.
• Restart the Information Stores Services.
• Go to Exchange Administration.
• Right click on the priv1.edb file.
• Click “mount”.
• A message screen will be prompted that says that there is no edb file. Just ignore it and click ok to proceed.
• A fresh PRIV1.edb and PRIV1.stm file will be created and all log files will be replayed now. New empty user mailboxes will be created; the users can now continue mail operations sending & receiving mails.

Note: You should backup your PRIV1 edb, PUB1 edb and stm files before running ESEUTIL for disaster recovery.

Follow the given steps to recreate the STM file:

• Backup you EDB database
• Stop the “Microsoft Exchange System Attendant" services and any antivirus software, if running.
• Run the "Regedit” command by going to "Start" -> "Run”.
• Now you need to modify some of the registry values, First go to:   [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan] and then set the value of "Enable" from 1 to 0.
• Now Run eseutil /mh command as below:

Eseutil /mh “Path of the database”
eseutil /mh "C:\Program Files\Exchsrvr\MDBDATA\priv1.edb"
eseutil /mh "C:\Program Files\Exchsrvr\MDBDATA\pub1.edb"

The command let you know the state of the database .i.e. clean shutdown or dirty shutdown. You can run the – eseutil /ml for checking the health of the log files. If the log files are in healthy state then you can run Eseutil /r for Soft recovery with the command.

• You can create the *.STM file by running eseutil /p /createstm command.

Run:
eseutil /p /createstm "C:\Program Files\Exchsrvr\MDBDATA\priv1.edb" (for private mailbox store *.STM file)
eseutil /p /createstm "C:\Program Files\Exchsrvr\MDBDATA\pub1.edb" (public store *.STM file)

• Again Run the "Regedit" and go to: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan]
• and change the values of "Enable" from 0 to 1.
• Restart "Microsoft Exchange System Attendant" services.
• Go to Exchange "System Manager and open mailbox store/Public store. For each mailbox store, run "mailbox cleanup agent". Then, Select the checkbox "reconnect all mailboxes".
• Open the properties of the mailbox store/Public store. Go to Database" tab and select the checkbox "This database can be overwritten by a restore".
• Finally, mount the mailbox store/Public store; your .STM file has been created. You can now run the antivirus software or other Exchange services.

Note: These steps are valid for Exchange 2000/2003.

Transaction log files play a very important role in rebuilding the Exchange mailbox database. If the edb file gets corrupt then you can roll up the transactions in a new edb. You can easily re-build the Priv1.edb File by using Transaction log files as explained above.

If you are looking for an easy and efficient Exchange database recovery method then, you can find several EDB repair tools in the market. Such software are competently enriched with powerful Exchange recovery features. You can easily repair the corrupt Exchange database files and save the recovered items to a new or existing PST file. The EDB recovery software are en-composed of advanced features and algorithms for performing efficient Exchange database recovery in a small time span.

Different data recovery companies provide different types of Exchange recovery software with varied feature set. However, what you can do is: just do an online search, find the software that seem to suit your needs, evaluate & compare their features, run the Demo and if satisfied with the Demo version, there is no harm in purchasing the full version.

Read more

Simple Steps To Recover Corrupt PRIV, PRIV1, Pub, and Pub1 Exchange Database Files

Most of the people are very much aware of the fact that Exchange database files (.edb) are nothing more than the exact copy of the user’s mailbox on Microsoft Outlook. Furthermore, this MS Exchange Server operates in right collaboration with MS Outlook in the transaction of mails and other important information like contacts, calendars etc. and every particular mail that is received or sent by the user is mainly stored on the server. Now, exchange server principally accumulates these email files as EDB (Exchange Database) files that proves to be very useful in case of several data disaster situations.

 

EDB files are also prone to corruption just like any other data files. There can be various software and hardware issues for the same:

• Installation of malicious software
• Inconsistent firewall or Antivirus software
• Power failure
• Virus attack
• System crash etc.
• Accidental shutdown
• Overwriting of garbage data due to bad file system consequences in corruption of OST files

It is extremely important that you take care of your exchange server well. As an IT admin, you should keep a right check on your data saved and at the same time authenticate its reliability. At present, every storage group on an Exchange server typically comprises one or more than one Public Folder stores and Mailboxes. Throughout the installation process, only single storage group is formed by default. With Exchange Server 2000 and 2003, every Mailbox store comprises a database set which consists two files namely ‘Priv1.edb’ and ‘Priv1.stm’.

The ‘Priv1.edb’ file is a lot similar to a text database file that mainly consists of text attachments, headers and email messages. Additionally, this file also includes ‘Priv.stm’ which is a streaming file that mainly includes media files like images, audio and video and some other internet files that are configured as MIME data. The actual concern with ‘Priv. edb’ file is that its size continues to increase, which eventually makes it prone of getting damaged or corrupt. Moreover, Header and Hard disk corruption are other chief reasons responsible for damaging or corrupting the 'Priv1.edb file. But still, you don’t need to fright , since you can restore the damaged/ corrupt Priv1.edb file with a manual method.

 

1. First of all you need to initiate the Exchange information store and then write down all of the errors.

 

2. Now halt Exchange information store and then from the ‘Bin’ folder , run the commands given below:

C:\exchsrvr\bin>eseutil /mh ..\mdbdata\priv1.edb"   

3. You need to now authenticate the ‘State’ line in the output. Also, make sure that all the files are steady. In case, you discover any of the files incompatible, carry out a soft recovery process. And, to execute such recovery process, you just need to move to the folder where the log files along with the database are placed. After performing this, just make sure to run the subsequent at the command prompt:

C:\Program Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil" /r E00  

4. Once again, it is vital for you to make sure the steadiness of both the public and private information store.

5. If the files are steady, then skip the next step.  

If the databases are found to be inconsistent, then it is significant for you to carry out a hard repair. To perform this, run the commands given below:

C:\Program Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil" /p priv1.edb   

  

C:\Program Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil" /p pub1.edb  

6. From Mbdata folder, eliminate the log files now which is very crucial.

7. Eliminate the 'Temp.edb' file. and '.chk' file.

8.You need to now mount the databases and then, dismount them immediately.  

9. At last, you need to discontinue the ESS(Exchange information store ) and then you should defragment both private and public store DBs. To do the same, run the following commands:

For Pub.edb:
C:\Program Files\exchsrvr\BIN>eseutil /d 
C:\Program Files\exchsrvr\MDBDATA\pub1.edb   

 For Priv.edb: 
C:\Program Files\exchsrvr\BIN>eseutil /d 
C:\Program Files\exchsrvr\MDBDATA\priv1.edb   

10. Now, run the 'Isinteg.exe' utility just to make sure that each database is steady.

C:\Program Files\exchsrvr\BIN>isinteg -s (servername) -fix -test alltests  

11. Lastly, restart the Exchange information store to recover the corrupt PRIV, PRIV1, Pub, and Pub1 Exchange Database Files.
 

On the other hand, after carrying out the manual process if you are still unable to mount the database and access your valuable emails, contacts and other messages, then you don’t need to panic as with the assistance of a competent third party exchange database recovery software like Stellar Phoenix Mailbox Exchange Recovery, you can resolve the problem very efficiently. This software is very much capable in repairing and recovering inaccessible and corrupt Exchange database files, i.e. 'Pub1.edb' and 'Priv1.edb', and can aid you get back the important user mailbox data. Moreover, with the help of this software, you can save the recovered files in PST format which can be easily imported in MS Outlook to access the mailbox items easily.

 

If you are facing any Exchange Server errors, then visit the following posts to get their solutions:

How To Resolve Exchange EVENT Error 9646?   

How To FIX ‘Exchange Server Error CODE 528, 550’?
How To Resolve Exchange Error 4294966746: JET_ERR DATABASE INCONSISTENT?  
How To Resolve Error 0X8004010F IN Exchange 2007?  
How To Deal With Exchange SERVER ErrorS?  
How To Resolve ESE Event ID 467 IN Exchange?

Read more

A brief glimpse at Exchange Extensible Storage Engine (ESE)

Exchange server uses the Extensible Storage Engine (ESE) Indexed Sequential Access Method table manager. This table manger works on the basis of discrete transactions and log files. Active Directory is employed on top of an Indexed Sequential Access Method (ISAM) table manager. ESE handles all the tasks related to maintenance of AD integrity. It possesses full data manipulation language (DML) and data definition language (DDL) capabilities for handling all transaction requests made by DSA; the request may include the addition, modification or deletion of an AD attribute. The Ntds.dit file stores all the data related to each transaction occurring in the domain controller.

The default location for Ntds.dit file is : < drive >\winnt\NTDS\Ntds.dit

ESE keeps track of all Exchange server data in memory, log files, and database stores. Exchange store uses ESE for storing Exchange database records and create indexes. The ESE engine supports JET technology and multi-threading. On the top of ESE database, there lies an Exchange store. Exchange database contains all the records and indexed stored by ESE. Different applications use ESE in different ways for storing and accessing records. ESE has three versions: ESE97 that was used in Exchange Server 5.5, ESE98 that is used in Exchange versions 2000 and 2003; the third version of ESE is ESENT. It uses 10 MB for log files and 8 KB pages but the other versions of ESE implementation uses use five MB log files and four KB page sizes.

How Does ESE Manage Transactions?

Each transaction is an indivisible unit that contains a series of operations that are bundled inside the transaction. ESE keeps track of all operations from the commencement of operation till its completion. When an operation is being performed then the change is not applied permanently to the database, so that if the operations cannot be performed completely then the database can be brought back to its previous state. Once the operation is completed successfully the change is permanently applied to the database. This ESE provides the recovery and roll back facility so that if a crash occurs or transaction couldn’t be completed successfully due to some reason, then the database can be kept synchronized and consistent.

Version Store

It keeps track of the current ongoing ESE transactions and manages an in-memory list of the operations being performed to the database. It supports Rollback, Write-conflict detection, Repeatable reads, deferred before-image logging. These features make it capable of keeping the ESE transaction Isolated and Consistent.

Transaction Rollback

If it is required to roll back a transaction, then version store comes into play. It stores all the list of operations performed within the transaction. The series of operations is performed again in reverse order; from there the database can be restored back to the previous state.

Write-conflict Detection

What will happen if two different sessions are trying to modify the same record, here again Version stores plays a significant role. It keeps track of the sessions going on and if it finds such case then it accepts the first modification and rejects the second one.

Repeatable Reads

Version store helps to avoid the database view conflict that can occur if a session is viewing a record and other sessions modify the records that it is viewing. The version store helps in determining that which version of the database record should be presented in the session for viewing. Thus a session will view the record regardless of modifications made by other clients or sessions. Or we can say that the modifications made by other clients or sessions are isolated from each other.

Deferred Before-Image Logging

This feature helps in optimizing the data of ESE; this helps ESE to keep its data less as compared to other database engines.

ESE Database Pages and ECC Checksum

A ESE database stores the data in B tree structure i.e. parent element at the root and child elements at a node. The database files include edb file, .stm file, and transaction log files. 64 bit Error Correcting Code (ECC) has been introduced in Exchange Server 2003 Service Pack 1 (SP1), the earlier formats used 32 bits. The previous versions of ESE used four-byte checksum, followed by a four-byte page number but ECC starts with an eight-byte checksum.

Database Consistency

ESE helps in maintaining the database consistency. When a page is read then ESE checks its flag and checksum for it. If the checksum is not same as the checksum calculated by ESE then, there is a checksum mismatch error. ESE corrects this error automatically; if the error cannot be corrected then it reports a -1018 error.

ESE manager is based on write-ahead log and a snapshot isolation model. It provides support for de-normalized schemas including tables. ESE has to perform the Database tree balancing function. For a balanced tree there must be the same number of nodes at the root level and at the leaf level. Split and merge operations are performed by the ESE for managing the page’s data. When a page gets full, it keeps the half data and the rest half is shifted to a secondary page. Merge operation is performed when a page is almost empty. In such case the empty page is merged with an adjacent page.

If I recapitulate the summary of the above article, we can easily wrap up the fact that the transactions performed by ESE possess ACID properties (i.e. Atomicity, Consistency, Isolation, and Durability). These properties make ESE supportable for server applications as well as it is lightweight, provides high data performance using caching and concurrent transactions. These properties also make it suitable for auxiliary roles and light structured data storage applications. Read my upcoming article, to know more about ESE, its functioning and related issues.

Read more

How to integrate Outlook with Lotus Domino using DAMO?

Emails are the best way of communication and data dissipation for personal/home users as well as for business domain users. Due to emerging needs and variant user requirements various Emails clients are emerging into the market. Outlook and Lotus Notes are one of such popular Email clients.

Why do users migrate from one email platform to another? There can be various reasons for email migration such as: job change, location change, platform change, technology charges, business needs, cost factors, organizational factors or the user’s personal preferences.

Why do Users Switch From Notes to Outlook?

Some organizations prefer to use Outlook instead of Lotus Notes. Lotus Notes provides better security features than Outlook, but the user friendly and easy to use features of Outlook makes it more preferable for some users.

So, if I consider from the user’s point of view, why they make switch from Lotus Notes to Outlook. Then following major factors comes ahead:

• Easy to use components of Outlook: Even if you are new to outlook, it provides easy to use components that make it easier for the new user to learn and thus reduces the learning curve duration, training cost and efforts.
• Lotus Notes is designed keeping in mind the needs of corporate users, so it’s best suited for their needs. If I consider the home users then it’s tough to use and costs more. So, Outlook is a better choice for home users.
• Lotus Notes requires more installation and maintenance costs as compared to Outlook. So, the cost effectiveness of Outlook makes some users to switch from Notes to Outlook.

Want to make switch from Lotus Domino to Outlook? It may be possible that a user requires making switch from Lotus Notes to Outlook due to business needs or due to personal preferences. In such situation it is necessary for the user to import Lotus Domino to Outlook, so that he can access his previous mail conversations and other mailbox data.

How to Make Switch From Notes to Outlook?

If you are Outlook 2003/2002 user then you can make your Outlook work with Lotus Domino with the help of Microsoft’s Outlook 2003/2002 Add-in: Notes Connector.

IBM provides DAMO (Domino Access for Microsoft Outlook) for integrating Lotus Notes to Outlook. You cannot download it if you aren’t admin as IBM doesn’t provide it as a standalone downloadable product. First get DAMO from your server administrator, then install a copy of the Lotus Domino server.

Follow the given steps for installing Lotus Domino Access for Microsoft Outlook (DAMO) 8.0.2:

Before installing DAMO, checkout your system must match the following specifications:  

• Operating system: Windows XP or Windows Vista.
• Outlook XP with SP3, Outlook 2003 with SP2, or Outlook 2007 with SP1.
• Open Internet Explorer, Go to Tools > Internet Options > Programs and set Outlook as your default Email client.
• Domino server 7.0.1 or higher
• You must have a local copy of Your Notes ID file or stored in your Person document. Also you must know the hierarchical name of your Domino mail server

After ensuring that you have correct system specifications, proceed with the given steps:

1. Run the setup program. The welcome screen will open. Click next to proceed.

2. Click Next after selecting the checkbox ‘accept the terms of the license agreement’

3. Enter your name and organization name in the specified fields.

4. Click Next it will install the software in the default install directory. If you want to change this then click change and enter your desired directory and then click Next. 

5. From the ‘Custom Setup’ window, you can select your desired features to be installed.  

 

6. Choose ‘Lotus Domino Access for Microsoft Outlook’ under the option ’Select the program features you want installed ’ and Click Next.

7. Click Install. The installation progress will be shown by a progress bar.

8.  In the final step of installation, you need to setup the DAMO. 

        
To Do So Follow The Given Steps:

1. On the Setup welcome window, fill the Domino server Network information: your name & your Domino server's hierarchical name. Click Next.

2. You need to enter the server's IP address, if setup couldn't locate the server by name.

3. You need to specify the location of your ID file, if you haven’t attached it to your Person document on Domino server. After that you need to enter the password and click OK. After that Initial Setup window will be opened.  

4. Click Yes in the prompt window to create a cross certificate

5. Click finish.
6. After completion of Setup, exit Outlook application.  

7. Restart Outlook then select your MAPI profile and enter the password in the prompt window. 

8. You will now receive a welcome email form the System Administrator with subject line: "Welcome to IBM Lotus Domino Access for Microsoft Outlook!"

If you aren't prompted to select Domino MAPI profile then, you need to recreate a Domino MAPI profile.

To Do So Follow The Given Steps:

1. Go to Control Panel > Mail> E-mail Accounts. 

2. From there choose your Domino Mail MAPI profile and remove it.

 

3. Re- Run the DAMO setup.
4. Choose the option ‘Modify’ as shown below:

The above steps will recreate your Domino MAPI profile.

Note: If the MAPI Domino profile creation process fails then, the Domino Preferences tab will be missing from the Options under Microsoft Outlook Tools.

After installing the software, go to environmental variables and set the path variable to location: %ProgramFiles%\DominoForOutlook

You can face several issues such as Missing emails .You can get only maximum 200 M of emails from the last days, thus some emails will be missing. To increase the limit Go to Outlook tools -> options -> Domino Preferences > replication section. And from there change the number of days to 365 and the maximum limit to 1600 M. Restart Outlook and let it replicate all the messages, Once it is done go back and set these fields to previous values. You can also have to face the issue that the Messages that get open in Notes, are not opening in Outlook.

If you are looking to make a switch from Lotus Notes to Outlook then, you require integrating your Notes with Outlook by using DAMO. The other alternate option is that you get your Lotus Notes NSF file converted to Outlook Supportable format (PST). To do so, you will require an efficient NSF to PST conversion software. The NSF to PST converter let you export all your NSF mailbox data such as: emails, attachments and contacts etc. to PST file. Later on, you can import the exported PST file into Outlook, access the data within it and work with it.

Read more