Skip to main content

Microsoft Office 2007 Pro Plus troubleshooting

Microsoft Office 2007 Pro Plus


Microsoft Office 2007 Pro Plus 

Microsoft Office Excel 2007 to analyze your business information, create spreadsheets, and track time, costs, resources, and people
Microsoft Office Word 2007 to create, manage, save, and edit documents
Microsoft Office Publisher 2007 to produce professional publications
Microsoft Office Outlook 2007 to manage tasks, daily appointments, and email
Microsoft Office PowerPoint 2007 to create dynamic sales presentations
Microsoft Access 2007 to create a database and then filter, sort, graph, and visualize business information
InfoPath 2007 to lower the cost of executing business transactions and processes with advanced electronic forms technologies

Trouble shooting section


Issue: Error starting Outlook: "Cannot start Microsoft Office Outlook. Cannot open the Outlook window."

Cause and FIX
This problem can occur when file that maintains the Navigation Pane settings becomes corrupted. This file is called profilename.xml, where profilename is the name of your Outlook profile. This file is stored in the following folder:

•Windows XP

C:\Documents and Settings\username\Application Data\Microsoft\Outlook

•Windows Vista, Windows 7

C:\Users\username\AppData\Roaming\Microsoft\Outlook
A good indication this file is corrupted is when the file size is 0 KB.

To resolve this problem, use the following steps.

1.On the Start menu click Run.
2.In the Run dialog box, type the following command:

Outlook.exe /resetnavpane

Note: There is a space between "Outlook.exe" and "/resetnavpane"

3.Click OK
Issue: Exchange 2003 SP2 and Outlook 2007, mapped mailbox indicates the inbox has one or more unread messages.  However, they are not being displayed in the reading pane.

Connecting directly to the mailbox via wmail reveals the unread messages as well many more read emails that were not present in the mapped mailbox.

Cause and FIX

1 You are able to see all emails when connecting to the mailbox directly (i.e via wmail) but not as a mapped mailbox. The reason is the emails are being sent with a special properties set. The 'sensitivity' setting is defined as 'Private' which mean only the intended recipient user can see the email not users sharing the mailbox.
Issue: Outlook starts with the error message "There is no email program associated to perform the requested action"

Cause and FIX
After clicking on the OK button Outlook appears to respond correctly. Does not relate to missing Plugins or other messages, only when you start Outlook the first time.  Looking at Default file extensions in Windows 7 was not revealing as the current settings mimic another working computer.

After investigation the FIX involved copying [HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Microsoft Outlook] registry from another working computer.  The computer with the error message was missing all of the keys even after re-installing the software.

Issue: If a user has an issue where PowerPoint changes the hyperlink the user inputs from (e.g.) M:\Eng\pdfexample.pdf to ../../root/eng/pdfexample.pdf then please follow the below instructions to fix:

Following stops PowerPoint messing with links on save.

Tools -> Options -> General -> Web Options -> Files -> Update links on save.
Needs to be unchecked.

Comments

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...

Windows 7 Offline files will not go Online when connected to network

Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...