MS OFFICE ERRORS

nullI understand that when you tried to open Outlook 2010 beta on the Windows 7 computer, you encountered the following error:
null
"Either there is not default mail client of the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client."
You tried to repair Office, but the problem persists.
Before we go further, I would like to confirm if you tried Ben’s suggestions to start Outlook in the safe mode. If we can start Outlook in the safe mode, the issue is caused by some third party add-ins in the Outlook program. We can try to disable them.
However, if the problem persists when trying to start Outlook in the safe mode, let’s continue.

First, let’s try to manually set Outlook 2010 as the default e-mail client on Windows 7:

Click Start.

Type "default programs" in the Start Search box.

Click Default Programs under Programs in the search results.

Now click Set your default programs.

Highlight Microsoft Office Outlook or Microsoft Outlook on the left.

Click Set this program as default.

Click OK.

Check the issue again. If the problem persists, this issue may occur when the Outlook registry is corrupted. Let’s try to remove the related registry and try to repair Office again.

===============

Click Start, in the Search box, type regedit, and then press ENTER.

In Registry Editor, locate the following subkey in the registry: HKEY_LOCAL_MACHINE\Software\Clients\Mail\Microsoft Outlook

Select the subkey, and then press DELETE.

Click Yes.

Quit Registry Editor.

Click Start, then click Control Panel.

Click Programs and Features.

Click the Office 2010 program that you want to repair, then click Change.

Click Repair, then click Continue. You might need to restart your computer after the repair is complete.

Can we open Outlook after this? If the problem persists, we might need to reinstall the Office program to resolve the issue.

PROCEDURE 2
An administrator can monitor the performance of their Outlook application by shutting down all other applications and then running the performance monitoring tool from the Task Manager which will show the CPU utilization and memory usage on the Performance tab. If the Task Manager is not available to an end user then get an administrator to follow these steps:

1.Press the Ctrl-Alt-Delete key sequence simultaneously.
2.Choose Task Manager.
3.Select the Performance tab.
You can also select the Processes tab to view all CPU and memory usages per process running on the system. Selecting the CPU or Memory headings from within the Process tab will allow an administrator to monitor the usages from high to low or from low to high based on the needs of the administrator.

An administrator might want to try opening Outlook in safe mode by using the following command with the forward slash safe argument:

C:Program FilesMicrosoft OfficeOFFICE11Outlook.exe / safe

In safe mode the add-ins are not running which is at least a workaround to allow your users to run their email application while preventing the potential issue of memory leaks. One way of determining if the add-ins are causing trouble is to start Outlook normally and then disable the add-ins one-by-one. An administrator can start Outlook, disable an add-in, restart Outlook and then monitor the memory for memory leaks. If no leaks are occurring then repeat the same procedure until an add-in has been identified. Once identified then remove that add-in permanently, install the previous add-ins and then report the problem to the respective author of the add-in.

Another diagnostic procedure to take would be to run all spyware applications and check for something out of the ordinary. This is why routine and regular maintenance of all software applications on the client is strongly recommended to prevent problems before they happen.

A less desirable approach is to completely uninstall Outlook and then re-install it so that they are operating with a clean application.

If your client is running an earlier version of Outlook such as Outlook 2000 then there was a patch (service pack 3 – SP3) which existed that fixed this memory leak problem. You can check the Microsoft Knowledge database for the following article: http://support.microsoft.com/?kbid=811167.