clariviere
asked on
MS Office 2010 install returns error 1935
When I try and do a fresh install of MS Office 2010 Professional Plus I get the following error.
Microsfot Office Professional Plus 2010 encountered an error during setup.
Error 1935. An error occurred druing the installation of assembly component {7702D6A3-846B-B087-736005
Microsfot Office Professional Plus 2010 encountered an error during setup.
Error 1935. An error occurred druing the installation of assembly component {7702D6A3-846B-B087-736005
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Binh Win
Please run setup /? to find the log file parameter, then run setup.exe with that log file parameter to produce the log file. Then hopefully the log file will tell you what the issue is and you can attach the log file here for me to look at too.
Clariviere,
I am still waiting for the log file, did you ever figured this one out? I think both myself and byundt should get some points for effort. :-)
I am still waiting for the log file, did you ever figured this one out? I think both myself and byundt should get some points for effort. :-)
mismoboy,
We get points not for effort but rather if the suggestion(s) lead to a solution. That's what makes the PAQs so valuable in the Experts Exchange database.
Questions like this one are somewhat akin to throwing darts at a dartboard. Since we can't reproduce the problem at our end, we can't know for sure that we have ever solved it. All we can do is suggest a procedure that may uncover the real problem, or post a few links that may or may not be relevant.
That said, it would be helpful if clariviere posted progress to date. The site works best as a collaboration between Asker and Experts. Even if we didn't hit the bullseye, sometimes a few more clues may let us be more helpful.
byundt
We get points not for effort but rather if the suggestion(s) lead to a solution. That's what makes the PAQs so valuable in the Experts Exchange database.
Questions like this one are somewhat akin to throwing darts at a dartboard. Since we can't reproduce the problem at our end, we can't know for sure that we have ever solved it. All we can do is suggest a procedure that may uncover the real problem, or post a few links that may or may not be relevant.
That said, it would be helpful if clariviere posted progress to date. The site works best as a collaboration between Asker and Experts. Even if we didn't hit the bullseye, sometimes a few more clues may let us be more helpful.
byundt
I guess it's really hard to see my tone of voice or true meaning through forums. My happy face at the end of my comment was meant to be a joke...
ASKER
I re-ran did a thorough unistall of 2007, did all the MS updates and then reinstalled 2010 with no issues. I think it was the .net, sorry for taking so long to get back I was out with pneumonia for about 3 weeks and then I have been playing catch up and finally was able to get back to this issue. Thanks again.