Solved

Error 1304: error writing to MSO.dll file.

Posted on 2007-11-14
3
4,103 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

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

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

Have you ever had the experience that you had to follow 10 steps over and over again every time when you need to nicely forward an important email to your manager? Fear no more! With the help of the Quick Steps feature in Outlook 2010, your old chor…
This article descibes how to create a connection between Excel and SAP and how to move data from Excel to SAP or the other way around.
The view will learn how to download and install SIMTOOLS and FORMLIST into Excel, how to use SIMTOOLS to generate a Monte Carlo simulation of 30 sales calls, and how to calculate the conditional probability based on the results of the Monte Carlo …
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…

895 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

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now