Microsoft Office 2010 corruption and inability to re-install

A client called this morning with a may-day... Microsoft Office 2010 Home and Business edition is unable to run.
As usual, tried the repair, even tried uninstall and re-install - hey, I have an adventurous client here! - but it did not resolve the problem.

To make things worse, the Ms Office is now unable to be installed with an error stating that there's error 2086. 
(I have already stopped the antivirus, run as administrator and saved the entire CD to my D drive...)

Went online, do my usual ritual of google-ing for things... 

1st link: doesn't help as i have given administrative rights to install and even tried turning off the antivirus (trend micro wfbs corporate)

2nd link: gave me more info on the nature of the problem. rooted to .net frame work installation that is required.

Decided to try doing a Windows update, and to my horror, .net framework 4.0 update failed with another error!

Windows update returned error 643, and upon searching for answers, found this link. 

Looked at both solutions, tried the Microsoft Fix-It first, duh- so easy... But it didn't resolve the problem.
Went on to the second solution to repair the .Net frame work client profile.... then restarted the machine.
After the machine restart, I proceed with the .Net framework 4.0 update again (which is successful). I do know that without this update, there is high possibility that I will not be able to install the MS Office 2010.

Aha! that solved the problem and Ms Office 2010 is successfully installed. Proceeding with Ms Office Service Packs and updates!!!

Mac OS X (all ver) has issues with DNS resolution IPv6 with SBS-2008

Some time back, the SBS-2008 my client has in their office is causing some DNS resolution issues with IPv6 reverse lookup. As such, some times the MAC OS X'es are unable to resolve DNS entries to get connected to the mail server.

A work-around my colleague gave was to set-up VPN connection as PPTP VPN using RAS gives out a separate IPv4 address, and is able to resolve IPv4 DNS requests without using the IPv6. 

While this is an easy work-around, the easier method is to simply set-up hosts file to perform the mapping.

Unfortunately for him, he was unable to locate the hosts file to edit in the mac os X. I did some search in the web and encounter this blog post... (here) I don't wish to re-invent the wheel, but I thought I'll post it here anyway, with some pictures to guide my readers and my team how to make the changes.

Follow my print-screens below. It should be self-explanatory.

just press CTRL+o (Omega) to save.

press Enter to save the changes.

You are good to go! 

Now for the biggie.. the server needs to be fixed with the IPv6 issue.

This is the issue:

I ensured that all settings are right:

 

After hunting through different blogs, i found one here and I realize this guy faced the similar problem and fixed the issue!

the mistake i made was to create 8.c.2.f.0 where I should have done it like this:

 

 Once added with an AAA record, the PTR can be added.

  

Resolution now works.. but the problem still persists!

Shucks! 

 

:

 

 

 

Adobe Reader does not show printer and Windows 7 is unable to change default printer

Client called today to report of problems related to printing.


She's generally able to print to her new Ricoh MFP C5000 Copier machine, but was unable to see this printer driver in Adobe Reader X. Strange as it may seem, this happened because I've set the printer up on a different domain user profile.

I repaired Adobe reader, ran all the updates, but to no avail. Even tried changing printer name to something shorter... Nope, it doesn't work. Gave user the change permission on the printer properties...nope!

Finally, as I was trying to set the printer as a default, I encountered an error:  

Unable to setup Default Printer, error message: 0x00000709

As I was looking through the net for similar issues, I encountered this forum post here.


I had to read through the entire 4-page long document and I finally figured that I could simply change the permission on the registry to allow EVERYONE full access to this registry key:

Found out that I didn't have the right permission to access the registry key here:

 HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows

All I needed was to give myself the full access permission and everything was fine after the reboot.

The thing I couldn't figure was, why is it only Adobe Reader X having this issue with not being able to detect the printer. Hmm...