Solved

Error 1304: error writing to MSO.dll file.

Posted on 2007-11-14
3
4,106 Views
Last Modified: 2008-02-01
Hello,

Getting the above error when I attempt to remove the office 2007 installation. I am repairing because when I start to run any of the office 2007 software, windows installer dialog box appears. Nothing happens for a very long time so I click on the cancel button.

When I do Office 2007 repair, after a while the error msg is ...Error 1304:Error writing to c:\program files\common files\microsoft shared\office12\mso.dll. Verify that you have access to the directory. The mso.dll file is located in the directory. This error only started happening from this morning. Everything was fine yesterday.

Don't want to uninstall then reinstall Office 2007.

many thanks.
0
Comment
Question by:m4nd4li4
  • 2
3 Comments
 
LVL 7

Expert Comment

by:ottobock
ID: 20282282
Hello,
It sounds like the local installation cache may be corrupted.

Are you working with full admin rights on the computer?  Limited rights will give problems when editing anything in program files.

Is this XP or Vista?  How was 2007 installed to begin with (DVD, preloaded, something else)?  If it was through DVD, just reinstall without uninstalling.  
Good luck!
0
 
LVL 3

Author Comment

by:m4nd4li4
ID: 20288118
Hello,
Thanks for the reply. It was full rights on the computer. OS is WinXP Pro SP2. Office 2007 Pro was originally installed from the CD. I was upgrading from Office 2002 to 2007.
I tried reinstalling without uninstalling, but this did not work. Still got Error 1304. So I uninstalled Office 2007 and reinstalled it. Everything works fine now. Still do not understand what went wrong.

Rdgs,
m4nd4li4
0
 
LVL 7

Accepted Solution

by:
ottobock earned 125 total points
ID: 20298950
It's tough to say exactly what went wrong exactly.

Office 2007 changed a lot of installation routines and processes.  I think the 2007 suite is still new enough that solutions are not readily available online.  
Chances are sometime during your upgrade from XP, a file was not properly copied or created, and therefore, this corrupted the local installation cache which Office uses for feature adding/removing and Detect&Repair.  Just a guess..
Glad you got it working!

Glad you have it working!
0

Featured Post

3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction It seems that at least a couple of times per month, I answer a question that requires automating Outlook from another Microsoft Office application, usually (although not always) to send one or more email messages.  For example: …
This article will show you how to use shortcut menus in the Access run-time environment.
This video walks the viewer through the process of creating Hyperlinks for the web and other documents. Select the "Insert" tab: Click "Hyperlink":  Type "http://" followed by a web address to reference a website or navigate to a document to ref…
Learn how to make your own table of contents in Microsoft Word using paragraph styles and the automatic table of contents tool. We'll be using the paragraph styles in Word’s Home toolbar to help you create a table of contents. Type out your initial …

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question