Microsoft Support Number OR Call Toll-Free @ 1-844-478-2887

Friday, February 3, 2012

Solving a Microsoft Communicator Address Book Syncing Issue

I have a problem with systems that are using Microsoft Communicator 2007, where they are unable to synchronize the address book. This of course makes searching for contacts nearly impossible and is quite annoying. I Googled around and found all sorts of people with similar issues, but it appears the same symptom can be caused by many things. I’m going to describe what I did to fix my particular situation.

A really important detail in my situation, is that this was only affecting users that were on computers that were not part of our Active Directory domain, such as a personal PC at home. They would install Microsoft Communicator and connect up to the VPN, sign in and they would get connected, however there would be a little red exclamation point in the top right of the Communicator GUI that looks like this:

Communicator Error 1
When you select the twisty, you’ll see an error message that says “Cannot Synchronize Address Book”

When you select the menu item Cannot Synchronize Address Book you would get the following error dialog box:

Cannot synchronize with the corporate address book. This may be because the proxy server setting in your web browser does not allow access to the address book. If the problem persists, contact your system administrator.

The issue of course is you can not search for people from the global address book and are forced to add them manually.

For my particular situation, the problem was actually with the SSL certificate. Specifically the problem is the client computer can not get to the CRL (Certificate Revocation List) URL. For whatever reason, I’m still not sure why yet, the default URL for the CRL used HTTP instead of HTTPS. The IIS virtual web on our Microsoft Certificate Authority server listens on port 80 just fine, but then anything your request from it just returns:

The page must be viewed over a secure channel
The page you are trying to access is secured with Secure Sockets Layer (SSL).

Please try the following:

Type https:// at the beginning of the address you are attempting to reach and press ENTER.
HTTP Error 403.4 – Forbidden: SSL is required to view this resource.
Internet Information Services (IIS)
Technical Information (for support personnel)

Go to Microsoft Product Support Services and perform a title search for the words HTTP and 403.
Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled About Security, Secure Sockets Layer (SSL), andAbout Custom Error Messages.
Work around

Ok, I have a solution I will post a bit further down, but for those who don’t have control of the CA IIS configuration, here is a workaround. Now before you complain, what I am suggesting affects things globally on your computer. By default Windows is configured to stop when it can not reach the CRL, so what we need to do is tell it not to. You do this by doing the following from Internet Explorer:

1-Go to Internet Options
2-Select the Advanced Tab
3-Scroll down to the Security section, and then uncheck: “Check for server certificate revocation”.
4-Close IE
5-Exit out of Microsoft Communicator
6-Start Microsoft Communicatior

At this point if your problem is the same one I had, then the red exclamation should go away and you should have downloaded the address book and be able to search contacts by name.

My Solution

What I decided to do was to have the IIS server on the Microsoft Certificate Authority server issue a redirect for all HTTP requests, ie) http://yourcahostname -> https://yourcahostname

In order to do this I located the Default Web Site on the IIS server on our CA, and then changed the non SSL port from 80 to 8888.

Then I created a dummy virtual web site called https redirect and had it listen to port 80. Under the home directory tab I changed the content to “A redirection to a URL” and put in https://yourcahostname  and then checked the “A permanent redirection for this resource”.

Now when your SSL certificate tells the computer to go the HTTP CRL URL it will get a 302 redirect the the HTTPS CRL URL and things should just work.

Microsoft Communicator Mobile 2007 R2 Update

Microsoft Office Communicator Mobile is a versatile Java-based unified communications client for Microsoft Office Communications Server 2007 R2. Communicator Mobile runs on Microsoft Windows Mobile 6.0 or higher which includes Pocket PC and smartphone devices.

It also supports:
Motorola Razr V3xx
Nokia S40 series: Nokia 3120 Classic, Nokia 3600 slide, Nokia 5220/5310/5610 XpressMusic, Nokia 6212 classic, Nokia 6300i, Nokia 6301, Nokia 6500 classic, Nokia 6500 slide, Nokia 6600 fold, Nokia 6600 slide, Nokia 7210/7310/7510/7610 Super Nova, Nokia 7900 Prism, Nokia 8800 Arte.
Nokia S60 series: Nokia E 51/63/66/71, Nokia N95
This month they released an important hotfix update for Communicator Mobile 2007 R2.
What's cool about Communicator Mobile 2007 R2 is that it enables users running the app on their mobile phone to make work calls using their corporate phone system leveraging "Single Number Reach" functionality. This allows you to use a single telephone number on your business card. With Single Number Reach, your desk phone and mobile phone will ring when an incoming call arrives. Importantly, outbound calling on your mobile device also gives the same caller identity regardless of whether you use a desk phone or a mobile phone. Another key advantage in Communicator Mobile R2 is that you can simultaneously sign in to more than one application at the same time and have multiple options for communication. In order to keep presence information up to date, the presence indicator now shows "Mobile" as an option for your availability, enabling people to easily keep track of your status. Apparently they've done some major overhaul to the code from the prior version since Microsoft said they optimized the performance and battery life is now improved by 350 percent.

Using Communicator 2011 on a MacBook

Here’s how to do it.

1. Download Microsoft Communicator for the Mac 2011. I got mine from my MSDN subscription. I don’t think it’s available as a public download. I also don’t know if it’s part of the Microsoft Lync Server download (I’ve not been involved in the setting up of the Lync server).

2. It’s an iso file, so just mount it and install it in the usual way on your Mac. When it asks you for your login details, ignore it and cancel out.

3. Now the fun step. It seems you have to install a certificate as a root certificate on the Mac in order for Communicator to work securely (briefly: the TLS connection needs an X509 certificate to authenticate the server). Azret gave me the URI on our NAS for ours, so I just double-clicked it from within Finder. A Keychain Access dialog came up asking me if I trusted the certificate. I clicked “Always Trust”, and... nothing happened. The certificate wasn’t added. If I tried to login with Communicator (you need your email address, user id, and password), I got this:

Screen shot 2011-01-12 at 7.01.47

Obviously that’s not the way to do it, so I did more searching.

3 bis. This is where it gets squirrely. A lot of the advice out there is for the earlier Leopard version of Mac OS X or is for earlier versions of Messenger for the Mac and talks about having to add the X509Anchors keychain to the list in the Keychain Access utility (although it’s there by default in Leopard) and then adding your company server certificate to that. Sometimes, this advice forgets to add the word “Leopard” making it seem as if it’s valid for all versions of OS X. Since the keychain by default is restricted to writing, you have to issue chmod commands and such to open it up for modification. (See here for an example of such advice, although it does talk about SnowLeopard. Here’s a TechNet article that also sent me down another rabbit hole.)

The answer for SnowLeopard is actually very simple: open Keychain Access (it’s in /Applications/Utilities, although I tend to just use Spotlight to find apps); drag the root certificate to the login keychain; on the dialog that comes up click Always Trust.

4. Start up Communicator for the Mac, type in your email address, user id, and password (I also click the remember password checkbox) and click Sign In. Communicator starts up.

5. (This one’s a bummer.) It seems that Communicator for the Mac does not use Growl for alerts but instead uses its own system. Yah. Boo. Sucks.

Screen shot 2011-01-12 at 7.26.18

As you can see, I set the dock icon bounce to Continuously (the default is Once Only). That way, if I miss someone pinging me immediately, at least I have a better chance of seeing it fairly quickly. I prefer Adium’s bounce once every 5 seconds option though.

How to Integrate Office Communicator 2007 R2 32bit with Microsoft Outlook 2010 64bit Edition

If you find yourself in the situation where you have Microsoft Outlook 2010 64bit Edition Installed together with Communicator 2007 R2 you will find that without the proper Exchange Configuration you will not have access to your Outlook Contacts and your Presence in Communicator will not be synchronized with your Calendar or OOF Events.

In a 1:1 installation, meaning Outlook and Communicator both, 32bit, Communicator relies on Outlook to get the Presence and OOF information as well as Local Contacts. It does this by connecting to the mapi.dll, but more on this in a later chapter.

Here is how to get Presence, OOF and Contact Information synchronized with your 32bit Communicator even if you have Outlook 64bit or no Outlook at all.

Firstly you will need to update Communicator to 3.5.6907.0083 (, you need to do this because an automatic mechanism was added to Communicator to enable it to fall-back on a direct Exchange Connection when it is unable to connect to Outlook.
*Note: You will still get the Outlook Integration Error but you can ignore it as you should have the functionality, the error message is meant to inform you that you are not connecting via Outlook.
In Communicator CU6 3.5.6907.0206 (  the behavior was changed and the Error message does not appear anymore if you fall-back to an Exchange Connection.
Well after you have installed Communicator CU4 or CU6 all the work on the Communicator/OCS side is done; now we need to check your exchange CAS Server and the method you use for autodiscover.
The guys in the Exchange Team took a few moments to explain the workings of the autodiscover process… as it goes we have two options to get the autodiscover XML.
Outlook usually employs the SCP method and gets the CAS Server address buy LDAP Query, when you are in your corporate network. When you are outside the organization and a connection to the DC is not possible, Outlook will try to connect using the Exchange Web Services. In order to identify the Web Services it employs several look up methods, here is a KB Article describing the process in detail:

Coming back to our Problem, Communicator will not be able to identify the SCP in AD so it will always employ the second method and it will use Exchange Web Services. So all you need to do to enable Communicator Integration with your Exchange Server is to create a SRV Record pointing to your Exchange CAS Server or create a DNS Host A record [autodiscover.] pointing to the same CAS Server or HLB.
Now we got the discovery method covered, the next step is to create a certificate and assign it to the IIS Server on the CAS. The certificate has to be created by a CA that your Local Client trusts, no SELF-SIGNED Certificates allowed hereJ.
Request a Certificate from the CA of choice, internally you could potentially get one from your internal CA, but if you are using OWA you will need to assign a Public Certificate for the Servers designated for external connections.
The Certificate will typically have a SN with the Server name and some SAN like mail.,apart from the usual SN and SAN, used by Exchange, you will need to add another SAN to this certificate with the fqdn autodiscover.
Assign this Certificate to your IIS, do an IISRESET if the services are started and you should be up and running.
Communicator should at this stage be able to resolve the autodiscover. and get the XML with the EWS URL that is used to get the Availability (AKA Free-Busy) and OOF information as well as Local Contacts stored in your Outlook Profile.
*NOTE: You will need to set your URL in Exchange to FQDNs that are accessible from any location in and outside your network in order to have overall coverage for your Communicator integration.
More Information on how to How to Configure Exchange Services for the Autodiscover Service can be found under

Thursday, February 2, 2012

Fix Microsoft Security Essentials Install Error Code 0×80070645

Ever since Microsoft has released their Microsoft Security Essentials anti-virus and anti-spyware program, I’ve used it exclusively on all my Windows machines. It does a great job and has a fairly high detection rate as compared to other free anti-virus programs.
However, I recently ran into a strange issue that caused me some grief. Everything was running fine until one day Security Essentials said it was out of date and that I had to upgrade to a newer version. Ok, no problem. After a little while, I got the following error message:

security essentials
MSE Install Error Code 0×80070645
Whoops! It would not install the latest version, so I tried multiple things such as uninstalling Microsoft Security Essentials, downloading the latest version and trying to install that way. However, that didn’t work either. I got the same error message.

I ended up having to talk to Microsoft support and they suggest a couple of things, one of which finally worked. I will mention the different possible solutions and hopefully one of them will fix your problem.
Method 1 – Delete Registry Keys

Sometimes during the upgrade, there are two registry keys that do not get removed that should not be there. Navigate to the following registry key and delete them:
HKEY_CLASSES_ROOT – Installer – UpgradeCodes – 1F69ACF0D1CF2B7418F292F0E05EC20B
You can go ahead and right-click on the 1F69ACF0D1CF2B7418F292F0E05EC20B key and choose Delete.
HKEY_LOCAL_MACHINE – SOFTWARE – Microsoft – Windows – CurrentVersion – Installer – UpgradeCodes – 1F69ACF0D1CF2B7418F292F0E05EC20B
Again, go ahead and right-click on the 1F69ACF0D1CF2B7418F292F0E05EC20B key and choose Delete.
Once you are done, close the registry editor and go ahead and restart the computer. Now try to install Microsoft Security Essentials and see if you get the error or not. If so, continue reading.
Method 2 – Run Cleanup Tools

If you ever had any other security software installed on your PC, you will need to perform a cleanup in case anything was left behind during an uninstall. Secondly, if you still having something else running like an anti-virus or anti-malware program, you should uninstall it otherwise it will cause conflicts with Security Essentials.
You can check out this link below that lists out all the different cleanup programs for software like Norton, Avira, AVG, Kaspersky, McAfee, TrendMicro, ESET, etc.
Once you perform the cleanup, go ahead and restart your computer and try installing Security Essentials again.
Method 3 – Run FixIt

You can also run the Microsoft FixIt solution, which will uninstall Microsoft Security Essentials 1.0. It will remove all remnants of the program so that you can perform a fresh install of the latest version of MSE.
If you’re having problems with version 2.0 of Security Essentials or if you installed one on top of another or something else crazy, you can follow the instructions below to completely remove Security Essentials 2.0.
Method 4 – Use Windows Update

Your last possible solution here is to use the above links to completely remove all versions of Security Essentials that you may have installed and then to go ahead and run Windows Update only our Windows machine and install version 1 of MSE.
Then, once you have MSE 1.0 installed, download the MSE 2.0 installer and go ahead and run it. This has worked for quite a few people, so if you are really having issues, then give this a shot.
Method 5 – Windows Installer

Lastly, you could possibly have an issue with Windows Installer. In that case, one program may be blocking another program from installing properly. You can download the Program Install and Uninstall Troubleshooter from Microsoft, which will fix that problem if it is occurring.
That’s about it! If you are still having issues, you might have to open a case with Microsoft and see if they can help you.

Fix Microsoft Outlook has encountered a problem error

One of Microsoft’s favorite error messages is “Program X has encountered a problem and needs to close”. You’ll get this message from pretty much any Microsoft product, including Microsoft Office, Windows, and Internet Explorer. Previously I wrote about a way to fix Internet Explorer has encountered a problem and needs to close error.

fix this same error for Microsoft Outlook! It may look something like this:

AppName: outlook.exe      AppVer: 11.0.8010.0     AppStamp:232039e
ModName: msmapi32.dll      ModVer: 11.0.8002.0      ModStamp:32949d2
Microsoft outlook has encountered a problem.

These errors, unfortunately, are not easily fixed because there are multiple problems that can give the same error message! So you may see this error in Outlook only when you close the program or you may see it every time you try to check for new mail.
Each of these has be be resolved in a different way! So in this post, I will list out all the possible ways that I know of that you can fix this annoying “Outlook has encountered a problem” error and hopefully one of them works for you.
outlook encountered a problem

Method 1 – Install Windows and Office updates
I’m going to start off with the easier tips before going into more technical solutions. Go ahead and install all the latest Windows updates and the latest Office updates. If you have Outlook with Business Contact Manager, make sure to install the service packs for that also. This probably won’t solve your issue, but it’s worth a shot.
Method 2 – Delete and recreate email account
Sometimes this error may be related to the actual email account setup in Outlook. You can try to delete the email account by going to Tools and then Email Accounts or Account Settings.
tools email accounts

Click on the email account and then choose Remove or Delete.

outlook email accounts

Go ahead and recreate the email account and see if that resolves your issue.
Method 3 – Start Outlook without add-ons
Your problem may also be caused if you recently installed an Outlook add-on, so try to remember if you installed anything recently that would have installed an add-in to Outlook. For example, if you install Adobe Professional, it tries to install a PDF add-on to all Office programs.

If you install some kind of Outlook connector add-on, uninstall that and see if the problem goes away. Installing an anti-virus program such as AVG, etc may also install an add-on to Outlook. Other add-ons like spam filters (Cloudmark, etc) may also be causing the issue.

You can quickly tell if an add-on is causing the problem by starting Outlook without any add-ons. Basically, you are starting Outlook in Safe Mode.
Go to Start, then Run, and type in the following command in the Open box:
outlook /safe

If your problem goes away, then you know it’s one of the add-ons. In Outlook 2007, you can enable or disable add-ins by going to Tools, Trust Center and then clicking on Add-ins.

outlook add ins

In Outlook 2003, you can disable add-ins by going to Tools, Options, clicking on the Other tab, clicking on Advanced Options, and then clicking on Add-In Manager.
Method 4 – Uninstall any new software
You can also get this error in Outlook by installing some other third party software on your computer. For example, if you recently installed a new toolbar for IE, uninstall it. If you recently updated to a new version of IE, try to revert back to an older version. Sometimes other programs not related to Outlook can cause this error to appear!
Method 5 – Find the corrupt email and delete it
This may sound weird, but one particular email can actually crash the entire Outlook program! Oddly, I have seen this happen before. When you try to read one specific email in your Inbox, all of a sudden Outlook will crash and close without a notice.
You will have to go through your email and try to find the email or emails that cause Outlook to crash. Though this is very rare, it has happened and can be very frustrating to figure out. My suggestion would be to simply click on the first email and just arrow down through emails slowly until you reach the corrupt one.
Method 6 – Replace msmapi32.dll with an older version
Some people have sworn that by replacing this file with a different version, their problem has gone away. However, this is a bit more complicated as their are many versions of this file around and you have to figure out which one will actually work. It’s best to simply copy the one you have currently to a different location and then try out various versions of this file.
You’ll have to do a search on Google for msmapi32.dll to actually find and download the files, but this may work for some people.
Method 7 – Delete or rename auto-complete data file
You can also try to delete the auto-complete history file as that sometimes gets corrupt and can cause this error. First, make sure you can see hidden files and folders by going to Windows Explorer and clicking on Tools, Options, clicking on the View tab and choosing Show Hidden Files and Folders.
Now navigate to the following directory:
C:\Documents and Settings\Username\Application Data\Microsoft\Outlook
Now find the file with a .NK2 extension and either rename the extension to something else or simply delete the file. Outlook will automatically recreate it and hopefully the new version will be error free.
And that’s about it! If your problem still persists, you can always try to completely uninstall Outlook and reinstall it and see if that works. Other than that though, one of the above methods should fix your Outlook error!

Fix Microsoft Word has Stopped Working

I recently installed Office 2010 on a Windows 7 machine and everything worked fine for a few days, but all of a sudden when I open Word, I get the following error message:

It then gives me the option to check online for a solution or to close the program.
word has stopped working

After this, I could not even open Word 2010 anymore! It would simply close down the program. How annoying! Anyway, after doing some research, I finally got the problem fixed. Depending on your situation, the solution may be different. I will try to post all of them here and hopefully one will work for you.
Method 1 – Repair Office 2010/Office 2007

To perform a repair of Office 2010/2007, go to Start, then Control Panel and click on Programs and Features. Click on the Office 2010/2007 program and click Change.

word not working

Click Repair and then click Continue. Let the repair finish, which could take a while, and then restart your computer.
word stopped working

If you continue to get the “Word has stopped working” message, then keep reading for more possible solutions!
Method 2 – Disable All Add-ins

Sometimes an add-in that gets installed automatically by another program (such as Adobe, etc), might cause Word to crash. In this case, you can start Word in Safe Mode, which does not load any add-ins.
Simply click on Start and then Run or if you’re using Windows 7, just type the following command into the search box:

winword.exe /a
Now click on the Office button and click on Word Options.
word error
Click on Add-Ins and then disable all add-ins and try to load Word again normally.

disable word addins

Method 3 – Install Latest Updates

If that didn’t work for you either, then you should try to download and install the latest updates for your version of Office. Sometimes it’s a glitch that is fixed when you install the latest patches and fixes.
In Windows 7, you can go to Automatic Updates from the Control Panel and find the latest updates. You can also visit the Office download center and download service packs for Office 2007, etc:
Method 4 – Delete the Word Data Registry Key

There is a key in the registry that stores frequently used options in Word. If you delete the key, Word rebuilds it the next time you start Word by using the default settings.
You can delete the Word data key by going to the following location in the registry depending on your version of Word:
Word 2002:HKEY_CURRENT_USER\Software\Microsoft \Office\10.0\Word\Data
Word 2003:HKEY_CURRENT_USER\Software\Microsoft\ Office\11.0\Word\Data
Word 2007:HKEY_CURRENT_USER\Software\Microsoft\ Office\12.0\Word\Data
Word 2010:HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Word\Data

delete word data key

Simply right click on the Data key and choose Delete. Now restart Word and see if the problem has gone away or not.
Method 5 – Remove Older Printer Drivers

Oddly enough, this ended up being the cause of my problem. I had an older print driver installed on my Windows 7 machine and once I removed that driver, Word started working without any problems!
You can delete individual printer drivers by going into the registry. Note that simply going to Printers and Faxes and deleting a printer there does not delete the printer driver.
Follow Step 3 in my previous post about a printer error to remove the printer drivers:
Method 6 – Uninstall Recent Software

At this point, you have also think about any software or plugins that you may have installed on your computer. Annoyingly, this problem with Word can be caused by a program that is completely unrelated to Word!
Did you recently install some new hardware? A printer, scanner, label machine, web cam, tablet, etc? Have you installed any software? If so, uninstall it and see if the problem goes away.
Method 7 – Completely Uninstall and Reinstall Office

If nothing has worked yet, there are not many options left! You can try to perform a full uninstall and then reinstall to see if the problem is fixed.
Go to this link first and download the Fix It solution for your version of Office:
Once you run that, go ahead and restart the computer and reinstall your version of Office.

Wednesday, February 1, 2012

Microsoft Communicator error ” Cannot Synchronize Address Book “

A common issue we see is clients getting an error stating “Cannot Synchronize Address Book”.  It looks like this:



This is an action that the OCS installation doesn’t take care of automatically so it happens pretty regularly.  To resolve it, select the Directory Security tab and click on the Server Certificate Button


After you click on the Server Certificate button, follow the Wizard, select Assign an Existing Certificate and assign the certificate used by your OCS Server for client logins.  Once you’ve assigned the certificate the SSL port on the Web Site tab should be filled in with port 443.

Sign your clients out of Communicator and then back in and the Address Book should be downloaded successfully

How to remove partially installed Office 2010 for installing it again?

In certain situations the installation process of Office 2010 freezes before completion, you cannot rollback it or uninstall it as there is no entry for this installation in the Add/Remove list. Moreover it’s also impossible to install any other version of Office (such as Office 2007).

You can try to manually uninstall Office 2010 by the steps below as suggested by Microsoft:

1. Download and install the Windows Installer Cleanup Utility.

2. After you install the Windows Installer CleanUp Utility, click Start -> All Programs -> Windows Install Clean Up.

3. Highlight Microsoft Office 2010 entry in the list and then click Remove. Quit the Utility.

Note: If you have got any other old or redundant office entries such as Office 2007 or other Office stand alone products such as Visio in the list, please remove them together.

4. Close all applications.

5. Click Start, in the Search box, type “regedit” (without the quotation marks) and press Enter.

6. Expand the registry tree on the left pane and locate the following two registry subkeys:

HKEY_CURRENT_USER – Software – Microsoft – Office
HKEY_LOCAL_MACHINE – Software – Microsoft – Office

7. Right-click on this registry subkey and click Delete to delete those keys.
8. Open Windows Explorer, and then browse to the “C:Program Files” folder

If it exists, rename the “Microsoft Office” to “Microsoft Office OLD”
If it exists, rename “OfficeUpdate” to “OfficeUpdateOLD”
If it exists, rename “OfficeUpdate14″ to “OfficeUpdate14OLD”

9. Click Start, in the Search box, type “%Temp%” (without the quotation marks) and press Enter.

10. Empty the Temp folder.

Note: If some files can’t be deleted, please skip them, which don’t influence the result of the troubleshooting.

11. Empty the Recycle Bin.

12. Restart your computer. Try to install Office 2010 again.

Remove Microsoft Office 2010 from your PC

If you got an error message that saying “this product installation has been corrupted. when trying to uninstall Office 2010 (beta), the tips that I found on Techgeekmore may help you.

There are two methods: Most probably the error is caused by a missing xml file from the Grove portion of the Office installation. However, if you haven’t installed Groove, there are other reasons also.

First method with Groove installed: To solve this issue, you will need a copy of your installation source / CD.

1 – Locate the Grove Folder on your installation Source / CD

2 – Copy the setup.xml from the groove folder, and paste it in C:Program Files – Common Files – Microsoft Shared – OFFICE14 – Office Setup Controller – Groove.en-us –

3 – Try to uninstall Office again

Second method without Grove Installed or without the Office Installation Source

Go to the Microsoft Support Page at Using the Microsoft Fix It function, you can solve your problem. The process helps you remove Office 2010 (also 2007) from your PC.

Microsoft Office 2010 Language DLL error

Problem-When I receive excel docs via outlook 2010 I receive the following error when
trying to open it up from an email. But once I hit Ok, it opens up the
excel 2010 sheet.
The language DLL 'VBE7INTL.DLL' could not be found.


If you find errors related to. Dll files that are preventing entering Windows, start your computer in safe mode to solve the problem. First try to restore your computer to an earlier date (if you have Windows XP or Vista). This form of solution is a quick and easy recommendation that solves many of the problems that may have Microsoft Windows.

Use SFC command from Windows XP to scan and repair Windows files. To run this command, follow these steps.
Click on start > run
In the run box type - sfc / scannow and press Enter.

How To Fix The Microsoft Office 2010 Error 1935

Step 1 - Repair The .NET 2.0 Framework Installation
The .NET framework is a type of computer application designed to help your system run various programs that have been coded in the .NET language. This is a very common type of Framework for most computers, but is constantly being damaged. To fix this, you should “repair” the framework with the steps below:

Click Start, select Control Panel, click Add/Remove Programs.
In the currently installed programs list, click Microsoft .NET Framework 2.0 then click Change/Remove.
Click Repair, then click Next.
Step 2 - Install A Fresh Copy Of The .NET 2.0 Framework
If repairing the installation of the .NET framework does not fix the problem, then you should look at installing a new copy, or reinstalling your current copy. To do this, just download the framework from the site below and install it – it will guide you through the rest of the process:

If a version of the .NET Framework is not installed on your computer, then install the .NET Framework version 2.0. To do this follow this link
Step 3 - Clean Out The Registry
Download this registry cleaner
Another way to fix this error is to use a ‘registry cleaner’ application to repair the various damaged settings the right might have. The registry is a database inside the Windows system which stores important settings & options for your PC. Unfortunately, this database is continually being damaged, preventing the installation of Microsoft Office 2010 from being able to use it correctly. To fix this problem, it’s highly recommended you use a “registry cleaner” program to fix any of the damaged settings that are inside this database. Not many people realize it, but this could be the reason why the 1935 error is appearing.

Windows XP Shows Error Message: Installation of Microsoft Office 2010 Requires MSXML Version 6.10.1129.0

When you try to install Microsoft Office 2010 in Windows XP, you might get following error message:

Setup is unable to proceed due to the following error(s):

The installation of Microsoft Office 2010 requires that MSXML version 6.10.1129.0 should be installed on your computer. Install the component and re-run the setup. Correct the issue(s) and re-run the setup.

To fix the issue, you can follow any of following solutions:

Solution 1:

Download and install Windows XP SP3 from here. SP3 contains MSXML, so it'll fix your problem.

Solution 2:

If you can't download and install SP3, you can manually download and install MSXML using this link.

Solution 3:

If the above solutions don't work for you, do as following:

1. Type regedit in RUN or start menu search box and press Enter. It'll open Registry Editor.

2. Now go to following key:


3. Right-click on win32 key and select Permissions.

4. Now select your username and provide Full Control to it.

5. After that in right-side pane, change value of (Default) to following:


NOTE: Here C: is system drive where Windows is installed in your system. If you have installed Windows in any other drive, change C: to that drive letter.

ERROR 1935 while installing Microsoft office 2010 on windows 7

Problem- Installing Office 2010 student not on Windows 7 64 bit, error 1935. Error 1935 during installation of assembly component (63E949F6-03BC-5C40-A01F-C8B3B9A1E18E). HRESULT: 0x800736FD. Online support orient myself to a problem of micrsoft.NET framework to repair or re-install, but on my computer windows 7 64 bit I have Microsoft Sync Framework and the updates tell me that everything is in order. The program windows installer appears to hang when launching some applications. An update is she to do? Windows update should do it automatically? Another error message noted that I did not have permission to execute the program / update, "contact your system administrator" when I'm the only profile and the only administrator on my computer. Any related reply for this ERROR 1935 while installing Microsoft office 2010 on windows 7 will be appreciated.

Start by disabling the UAC (user access control) completely before uninstalling Office 2010 completely and start your installation. To completely uninstall: 1) always safe: creating a restore point 2) you make a copy of your file C: \ Users \ [tonprofil] \ AppData \ Roaming \ Microsoft that contains your templates, dictionaries. (to adapt because you're on XP) If you use Outlook, also make a copy of your pst file that contains your mails in case you'd have left in the default folder for installation. 4) You download from MS Windows Install Clean Up and save the file offered on the Windows desktop. When the download is complete, double-click the file msicuu2.exe and follow the installation instructions. You will be able to solve the problem.