Support Blues

Friday, July 8, 2011

Fix For: Unable to add the domain - An Unexpected Error of type - 14090 (eDSAuthFailed) occurred

Error Message:
Unable to add the domain - An Unexpected Error of type - 14090 (eDSAuthFailed) occurred.

Screens:

Platforms:
Mac OS X 10.6.x
Mac OS X 10.5.x

Scenario:
Active Directory account credentials were not recognized by the machine. Directory users were unable to log in to the machine using their network log in credentials. Local OS X accounts works fine. trying to unbind the machine from the Active Directory may fail and require us to do a force unbind. Then, when we go and try to rebind the machines to the directory , above mentioned message will appear.

Reason:

File "Kerberos:EXAMPLE.COM.AU.plist" located in /var/db/dslocal/nodes/Default/config/ may be corrupted or invalid.

Sample content of the file /var/db/dslocal/nodes/Default/config/Kerberos:EXAMPLE.COM.AU.plist is shown below

Use the Terminal command:

sudo cat /var/db/dslocal/nodes/Default/config/Kerberos:EXAMPLE.COM.AU.plist

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>OSBuild</key>

<key>appDurations</key>

<dict>

<key>["com.Adobe.ESD.AdobeUpdaterApplication"] [6.2.0.1474] [Adobe Updater 6.2.0.1474]</key>

<key>[Microsoft/com.microsoft.AlertsDaemon] [12.2.5] [12.2.5]</key>

<key>[Microsoft/com.microsoft.AlertsDaemon] [12.2.6] [12.2.6]</key>

<key>[Microsoft/com.microsoft.AlertsDaemon] [12.2.7] [12.2.7]</key>

<key>[com.adobe.Acrobat.Pro] [9.0.0] [9.0.0]</key>

<key>[com.adobe.Installers.Setup] [2.1.51.0] [COMPUTER_NAME:nodes]

Solution:

Remove the Kerberos:EXAMPLE.COM.AU.plist file and attempt to bind the machine to the domain again.

Use the terminal command:

sudo rm /var/db/dslocal/nodes/Default/config/Kerberos:EXAMPLE.COM.AU.plist

More Information:

Thursday, May 26, 2011

Resetting the System Management Controller (SMC) And Parameter Random Access Memory (PRAM) in MacBook Pro

Problem:
MacBook Pro does not charge its internal battery. Laptop works till it is connected to the main power supply. But as soon as we take out the power code laptop dies as no power is left in the battery.

Screens:
In the following screen you can see that the internal battery is not getting charged even though the unit is connected to the mains supply.

Platform:
Hardware: MacBook Pro 8,1 i7/4GB RAM /500GB HDD
Software: Mac OS X 10.6.7

Reason:
Corrupted System Management Controller (SMC) and/or Parameter Random Access Memory (PRAM) is responsible for this.

Solution:
Reset System Management Controller to factory defaults.

Note: Portable computers that have a battery you should not remove on your own include MacBook Pro (Early 2009) and later, all models of MacBook Air, and MacBook (Late 2009).

Shut down the computer.
Plug in the MagSafe power adapter to a power source, connecting it to the Mac if its not already connected.
On the built-in keyboard, press the (left side) Shift-Control-Option keys and the power button at the same time.
Release all the keys and the power button at the same time.
Press the power button to turn on the computer.

Note: The LED on the MagSafe power adapter may change states or temporarily turn off when you reset the SMC.

Reset PRAM and NVRAM

Shut down the computer.
Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously.
Turn on the computer.
Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.

Apple knowledge base Links:

Friday, March 25, 2011

Fix For : A virtual CPU has entered the shutdown state. This would have caused a physical machine to restart.

Error Message:

"A virtual CPU has entered the shutdown state. This would have caused a physical machine to restart. This can be caused by an incorrect configuration of the virtual machine, a bug in the operating system or a problem in the VMware Fusion software.

Screens:

Platforms:

Host: Mac OS X 10.6.7

Guest: Mac OS X server 10.6.2

Hardware: Mac Book Pro, 2.3 GHz Intel Core i5 CPU

Software: VMware Fusion 3.1.2

Scenario:

Was trying to install Mac OS X Snow leopard server as a VMware virtual guest on a new (Released Feb 2011) Mac Book pro. This resulted in above mentioned error.

Reason:

The universal Mac OS X Server 10.6.2 / 10.6.3 (build 10d573) operating system does not work inside a virtual machine on the physical MacBook Pro models with Core i5/ i7 processors. These physical machines were released after Mac OS X Server 10.6.2 / 10.6.3 (build 10d573) was released, and they have a processor that Mac OS X Server 10.6.2 / 10.6.3 (build 10d573) does not support.

Solution:

If you start with a 10.6.4 or greater version installation media, it should work.

There is a workaround as newfoundglory suggest.

Install Snow Leopard Server 10.6.3 inside VMware Fusion on an old Intel core 2 duo based machine. Then update it by running apple software updates to bring it to the latest version. Then copy over the virtual machine file to Mac Pro with i5/i7 CPU and try booting it.

More Information: