Fix Office 2010 Activation Error 0x8007001

Problem :

I am running Windows XP Professional 2002 SP3 on a desktop workstation connected to a corporate network. I downloaded the Office 2010 Professional Plus beta. I elected to do a custom installation and install only Publisher 2010. The installation completed successfully. I have been unable to activate the software. When I attempt to do so, I get the following message: "An unspecified error has occurred. Your request cannot be processed at this time. Please try again later. (0x8007001)." I have tried repeatedly. I have de-installed and re-installed. I was able to install and activate the product on my laptop.


Solution :

1.) Start menu --> Run... --> regedit
2.) Search for this registry key (you might want to right click HKEY_LOCAL_MACHINE --> Find..., and type 4D36E967-E325-11CE-BFC1-08002BE10318 into the box):

HKLM\SYSTEM\CURRENTCONTROLSET\CONTROL\CLASS\{4D36E967-E325-11CE-BFC1-08002BE10318}

3.) Look for UpperFilters, which is of type REG_MULTI_SZ
4.) Double-click on it, and under Value data, add "PartMgr" to the top of the list. Click OK.
5.) Restart your computer.
6.) Start Word (or any Office application), and follow the prompts to activate.

Fix Office 2007 Communicator Crashing

Problem :

We have implemented numerous OCS infrastructures. But with one customer we have a strange problem. On all the windows XP laptops (different brands) the communicator crashes after using the options with the right mouse button. For example starting a Live Meeting session. The laptops are up to date regarding the microsoft updates. On the Windows 7 laptops, no problem. The only differents is the way the communicator has been installed on the laptops. We have done this in the kix32 login script. Does anyone have the same problem or know a solution?


Solution :

The xp's version(sp2/sp3), the OC's version, whcih vender of the laptop
You also can check some log to find the causes, Such as: some event log in the application, the oc log. It may be also need to use the ADPlus to get some information regarding to your issue. Can refer to below about how to use http://support.microsoft.com/?kbid=286350

Some other inormation: ensure you have update the latest kb for OS and OC client.

reinstall the conferenceing add-in for the outlook refer to below

http://office.microsoft.com/en-us/help/HA102368901033.aspx

Does all the xp client(laptop and desktop box) have the same issue , please test both; I found a case looked the same as yours, it caused by the laptop momory problem(discovered by checking the dump log).
Does the xp sp3 client works well? you can test it.

Fix Outlook 2010 With Communicator 2007 R2 Error

Problem :

I use Windows 7 Enterprise (x64) with Outlook 2010 (x64) and Communicator 2007 R2 . I get Outlook Integration error in Office Communicator and could not update status information.
"Communicator could not determine the location of your Exchange Web services"


Solution :


What is in the latest released update for OC 2007 R2 for Exchange Connectivity:

· 64-bit MAPI is not supported for OC 2007 R2 in any configuration.

· In the event that MAPI is not available (Outlook not installed, or only 64bit MAPI is available) OC 2007 R2 falls back to EWS.

· In order for OC to discover Exchange and EWS, auto-discovery for Exchange to be enabled via the Exchange auto-discovery URLs.



Connectivity to Exchange Online:

· For customers that are using ExOnline where no auto-discovery is provisioned by BPOS, they should use 32 bit Office instead of 64 bit Office.

o BPOS uses local configuration files via the Single-Sign On Service Agent to configure Outlook to connect to ExO. OC relies solely on Exchange auto-discovery which is not configured for ExOnline.

o This will allow OC 2007 R2 to leverage 32bit MAPI to access Exchange Online via Outlook’s local configuration file that BPOS SSO/Service Agent drops.



Outlook Integration Error with 64bit Office 2010:

· For customers that are seeing an issue with on-premise Exchange deployments where auto-discovery is setup and enabled as described above , OC 2007 R2 CU4 should be able to connect to Exchange. These customers will still see an Outlook integration error in OC (since we couldn’t integrate with Outlook x64).

o For example, free/busy and out-of-office information should still be available in OC via EWS.

Hope this helps clarify the questions here.

Fix Outlook 2010 Error 30023

Problem :

Has anyone been playing with the outlook 2010 deployment scripts yet? We're testing outlook before the full package.
We seem to have run into an odd error that doesn't appear online when running the default script provided by MS.

C:\>start /wait \\srv1\pathToOutlookFolder\setup.exe /config \\srv1\pathToOutlookFolder\Outlook.WW\config.xml
C:\>echo Fri 06/25/2010 16:46:33.03 Setup ended with error code 30023. 1>> c:\\error.txt


Solution :

Error 30023 typically means there is a problem with your installation source. My recommendation would be to save your config.xml and your Office Customization Tool MSP file, delete your entire Office 2010 source folder, and then re-built it from unaltered, original source. Add your config.xml and setup msp to the new source and run setup.exe.

Your command line example syntax is good. If these steps don't resolve your issue you should enable verbose setup logging to help determine root cause. To enable logging, change this line in your config.xml:



to this:

Fix Outlook 2010 Emails Disappearing Error

Problem :

A few days ago i installed Office 2010 on my Windows 7 laptop, replacing Office 2007. All seemed well and Outlook retrieved emails from my pair of Pop mail servers.
Then i noticed an email appear in my Inbox, only disappear a second later. This has since happened 3 or 4 more times that i have observed. I've searched within Outlook (junk and deleted included) without success. I now have retain on server enabled so that i can use webmail and see the emails - they do not download again.


Solution :

There are 3 common scenarios in which this could happen.

To change or reset your view use;

Change view; tab View-> button Change View-> Compact (and optionally set the Arrangement to Date)

Reset view; tab View-> button Reset View

To verify/change your default delivery location;

File-> section Info-> button Accounts Settings-> Account Settings…-> tab Data Files-> select the Exchange mailbox-> button Set As Default

Additionally, on the E-mail tab, select the Exchange account and verify that your delivery location is set to the correct mailbox.

Third party add-ins

If you have such an add-in installed, you should check their settings to see what they do with the emails; move it to another folder, delete it directly or move it to some storage/quarantine location of their own. You can consult the vendor of the add-in which options are available to you.

Fix Visio 2007 SP2 Crashes Error

Problem :

Have Visio 2007 SP2, Windows 7 Enterprise. Whenever I open Visio and attempt a copy and paste operation it fails. The copied object could be anything - image or visio shapes.


Solution :



Try to disable all add-ins in Visio 2007 to test this issue.

1. In Visio 2007, click Trust Center on the Tools menu.
2. Click Add-ins.
3. In the Manage list, click COM Add-ins, and then click Go.
4. In the COM Add-Ins dialog box, click to clear the check boxes for all the add-ins in the Add-Ins available list.
5. Click OK.

Fix Office 2010 Slow Printing Error From Network Printer

Problem :

The title says it all. It takes 2 to 4 minutes for anything printed from an Office document to a networked Canon iR2870 copier. It doesn't matter if it's a doc or docx, xls or xlsx, etc. If it's open in Office 2010, it takes for ever to print. If it's printed from Office 2007, it prints in under 30 seconds. Any suggestions?


Solution :


1. Go to Start, Control Panel and Administrative Tools. Double click on Services icon.


2. Scroll down to the Print Spooler service and right click on it and select Stop. In order to do this, you need to be logged in as Administrator. At this point, no one will be able to print anything on any of the printers that are being hosted on this server.


3. Next you need to go to the following directory: C:\WINDOWS\System32\spool\PRINTERS. Delete all the files in this folder. This will clear all print queues (it’s a good idea to first make sure there are no other print jobs being processed on any of the other printers on the server because doing this step will delete those jobs also)


4. Now you can go back to the Services console and right-click and choose Start for the Print Spooler service!