AD Manager Plus

Outlook issues after applying kb2412171 update : outlook 2007 prompt for password

After applying KB2412171 update , outlook started prompting for user name and password. Even if you provide the credentials it will again give the same error. Finally I had to uninstall the update KB2412171 to resolve the issue.

The update was released on December 14, 2010 and was revised on January 11, 2011. Some other issue arises after the update are :

  • Loss of the Archive and AutoArchive feature.
    They are missing the option File-> Archive… and the AutoArchive section under Tools-> Options…-> tab Other as well as the AutoArchive tab in the Properties dialog of a folder.
  • Outlook is slow to respond when switching folders.
  • Accounts requiring Secure Password Authentication (SPA) may have issues to connect.
  • Exchange Accounts that have been configured to connect via Outlook Anywhere with NTLM authentication may be reset to Basic Authentication and now requests for the password.
  • IMAP accounts and accounts connecting via SSL may give send/receive errors. Gmail is for instance reporting error 0x800CCC78 and cannot send the message. Another common error is 0x800CCC1A.

How to uninstall  KB2412171 update on Windows 7 or Windows Vista:

  1. Click Start-->Control Panel.
  2. Click Programs, then under Programs and Features, click on View installed updates.
    KB2412171 issue with outlook
  3. Look for installed updates and select KB2412171 update  from the list.
  4. Click Uninstall
  5. Reboot after the uninstall

How to uninstall KB2412171 on Windows XP:

  1. Click Start -->Control Panel.
  2. Click Add or Remove Programs, click on Show Updates check box isshow that you are able to see all installed updates.
  3. Look for installed updates and select KB2412171 update  from the list.
  4. Click Remove.
  5. Reboot after the uninstall.

Microsoft is aware about the issue and posted this on their blog:

Windows Activation error: Code 0x8007232b

I was trying to activate Windows Server 2008 and got this error:
“Activation Error: Code 0x8007232b .DNS Name does not exist”

Actually Windows was looking for KMS server for the activation . and when it did not find that , it threw error 0x8007232b.

Microsoft has a KB article for resolving the issue:

I used following method to resolve the issueThe solution worked for me was:

1. Cick All Programs, click Accessories, and then right-click Command Prompt.
2. Click Run as administrator.
3. At the command prompt, type the following command, and then press ENTER:
            slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Note: In this command, the xxxxx-xxxxx-xxxxx-xxxxx-xxxxx placeholder represents your MAK product key.

4. Now try to activate the Windows online, you will succeed.

What is MAPI(Messaging Application Programming Interface)

Messaging Application Programming Interface (MAPI) is a messaging architecture and a Component Object Model based API for Microsoft Windows. MAPI allows client programs to become (e-mail) messaging-enabled, -aware, or -based by calling MAPI subsystem routines that interface with certain messaging servers. While MAPI is designed to be independent of the protocol, it is usually used with MAPI/RPC, the proprietary protocol that Microsoft Outlook uses to communicate with Microsoft Exchange.

More on Wikipedia :

How to Migrate/move SharePoint Databases from One SQL Server to Another

Following are the major steps to be taken to migrate/move sharepoint database from one SQL server to another SQL server:

1.Log into administration site (http://sharepointserver/default.aspx)
2.Click on the Operations tab and select perform a backup.
3.Select farm level backup and hit continue.
4.Enter destination of backup files and wait until finished backup.
5.Log onto the SharePoint server hosting the central administration.
6.Go to Start > Microsoft Office Server > SharePoint Product and Technologies Configuration Wizard.
7.Disconnect the server from the farm.
8.Repeat this step for the other web servers in the server farm if any.
9.Return to the first server and run the configuration wizard again, this time creating a new farm.
10.Enter data for the new database server (DBSERVER\Sharepoint) and create the farm.
11.Go to remaining web servers and join an existing farm using (DBSERVER\Sharepoint) for database.
12.Connect to administration site (http://sharepointserver/default.aspx)
13.Go to operations tab and select services on server.
14.Enable Office SharePoint Server Search
15.Enable Windows SharePoint Services Search Service (Leave default database information).
16.Go to Operations tab and perform a restore.
17.Select location of backup file and choose to restore the entire farm.

SCCM client push installation not working

When an SCCM client push installation is not working......we need to look at root cause of the issue. Here are some pointers may be helpful to you:

Troubleshooting SCCM Client Push Installation issues

Troubleshooting SCCM Client Push Installation issues

We come across many issues with SCCM client push installation and sometimes it takes lot of time to find a clue about the causes of the issues. Microsoft has recently releases a KB article which covers all possible solutions related to SCCM client push installation.

Here is the URL:;EN-US;925282

The ConfigMgr Advanced Client rejected the site server signing certificate

Error messgae “The ConfigMgr Advanced Client rejected the site server signing certificate to a trust-related failure (0x800b0109)” is showing up on few clients which are failing to install the certificate from the enterprise root CA.

Solution :
Compare the following registry values between a working and a failing client. If the values are different, replace the values on the bad machine with those from the good machine and re-install the client:

X64 – HKLM\Software\WOW6432Node\Microsoft\CCM\Security
X86 – HKLM\Software\Microsoft\CCM\Security
Keys - AllowedRootCAHashCode, Signing Certificate.

This may be helpful as well:  Renewing or Changing the Site Server Signing Certificate

This posting is provided “AS IS” with no warranties and confers no rights.

How to use SBMERGE command to update a Thinapp package

Here are the simple steps for using SBMERGE command on a ThinApp Project...
SBMERGE Process:
  1. Make a copy of the original ThinApp Project WITH the BIN folder and it's contents (EXEs/Data Container).
  2. Clear the SANDBOX within the %APPDATA%\THINSTALL folder.
  3. Run the virtual application in the project to be updated.
  4. Update the application with plugins, settings, updates, modifications. Close the app.
  5. Re-launch the app and test the updates exist and work.
  6. Close the app.
  7. Open CMD and change to the directory where virtual application is stored.
    Example: C:\Thinapp\packages\Firefox
    NOTE: If successful, the ThinApp Sandbox for this packaged app will have been removed from %APPDATA%\Thinstall.
  9. Execute BUILD.BAT within the project just updated by SBMERGE.
  10. Run new version of ThinApp packaged app to test updates/mods.
  11. Deploy via AppSync, Side-by-Side, MSI (via ESD), etc.
Source: VMware
More on updating ThiApp packages:

Popular Posts