Eternal Spinning Wait Cursor on editing AnyWord Document (including when opening a fresh wordsession

[Bill_Capehart]

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel Eternal Spinning Wait Cursor on editing Any Word Document (including when opening a fresh word session)

This is a continuation of a trouble request that seems to have closed itself though it was never resolved.

Original Thread:

http://www.officeformac.com/ms/ProductForums/Word/9531

Summary:

Word freezes on entry more-often-than-not. I start typing or any other edit function nothing happens at first (not text or anything), and then I get the spinning wait cursor which continues until I do a "Force Quit."

I cannot predict when or where the hang will occur so I cannot avoid it. I'm at the point where am falling to iWork as a backup - a sub-optimal solution since I work in a MS Office 2007/8 shop and Pages and Word are not 1:1 compatible when using *.doc as a go-between.

I have done the following with *both* 32-bit and 64-bit mode.

In all cases, I've checked all updates for both OSX (now at 10.6.3 (Build 10D573)) and Word (now at 12.2.4, with Entourage for Web services at 13.0.4)

------------

What's been described as the easy fix

1) Validated the Fonts in Font Book

2) Repaired both the Disk Permissions and the Disk (even though it didn't need it)

3) Shutdown & Restart after a few minutes

------------

1) the scorched earth uninstall and install, described by several MPVs and summarized in the thread below.

http://www.officeformac.com/ms/ProductForums/Word/9903/45

(As such my Normal template is the default one with no embellishments at present)

======================================

Sample Error is below.

I went through a bunch of these and have found that they change with each crash. Sometimes, the "co-casher" is airport, sometimes it's the addressbook, vm fusion, activity monitor, etc...

Date/Time: 2010-04-10 18:56:04 -0600
OS Version: 10.6.3 (Build 10D573)
Architecture: x86_64
Report Version: 6

Command: Word
Path: /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
Version: 12.2.4 (12.2.4)
Build Version: 0
Project Name: (null)
Source Version: 100205
Parent: launchd [452]

PID: 3961
Event: hang
Duration: 2.99s (sampling started after 2 seconds)
Steps: 9 (100ms sampling interval)

Pageins: 0
Pageouts: 0

Process: Microsoft Word [3961]
Path: /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
UID: 1261

Process: AirPort Base Station Agent [473]
Path: /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
UID: 1261

Thread d878620 DispatchQueue 1
  User stack:
    9 ??? (in AirPort Base Station Agent + 5692) [0x10000163c]
      9 NSApplicationMain + 364 (in AppKit) [0x7fff84997d7c]
        9 -[NSApplication run] + 395 (in AppKit) [0x7fff8499f05b]
          9 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155 (in AppKit) [0x7fff849d9379]
            9 _DPSNextEvent + 708 (in AppKit) [0x7fff849d9a2a]
              9 BlockUntilNextEventMatchingListInMode + 59 (in HIToolbox) [0x7fff82b74798]
                9 ReceiveNextEventCommon + 310 (in HIToolbox) [0x7fff82b748df]
                  9 RunCurrentEventLoopInMode + 333 (in HIToolbox) [0x7fff82b74ada]
                    9 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff8865f8df]
                      9 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff88660452]
                        9 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff887c675a]
  Kernel stack:
    9 ipc_mqueue_receive_continue + 0 [0xffffff800026e5de]

Thread d9c6000 DispatchQueue 2
  User stack:
    9 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff887e0385]
      9 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff887e04e8]
        9 _dispatch_worker_thread2 + 252 (in l

 

[jaclah]

bill capehart:

same problem here.
you mentioned earlier to "open font book and resolve duplicate" i dont see the line "resolve duplicate", where did you find it? did do the "repair permissions", but did not solve the problem; when i open word it tells me there is a problem with database; I used and repair the database utility to no avail.
this is frustrating, how did you end up solving the problem, or is not solved?
good luck and thanks for the help
jacques
thanks

 

[John McGhie]

Hi Jacques:

Your problem is probably not the same as Bill's.

I don't have your software version and update levels, and it's not safe to
say anything until I get those: please start your own thread so we can keep
advice to you and to Bill separate, and your software update levels are
absolutely critical to solving this issue.

Cheers

bill capehart:

same problem here.
you mentioned earlier to "open font book and resolve duplicate" i dont see the
line "resolve duplicate", where did you find it? did do the "repair
permissions", but did not solve the problem; when i open word it tells me
there is a problem with database; I used and repair the database utility to no
avail.
this is frustrating, how did you end up solving the problem, or is not solved?
good luck and thanks for the help
jacques
thanks

--

The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410 | mailto:[email protected]

 

[John McGhie]

Hi Bill:

OK, looks like it's NOT fonts in your case.

There are several things that can tip Word over in OS 10.6, duplicate fonts
is one, corrupt or incompatible fonts is another.

But an unstable network will also do this, as will corrupt documents.

You have replaced your Normal.dotm, so we can expect that new documents will
be OK for you, but that does not mean that existing documents are clean.

I would like to suggest that the log you posted looks as though Word hung
waiting for a response from the Airport. We're going to have to go hunting
for this one.

What's on the Airport for you? What kind of data do you store there?

Starting up in 64-bit mode is a relatively "brave" move. Word 2008 runs
fine in 64-bit mode on this system, but various "nice-to-haves" such as my
network driver and printer DON'T, so my opportunity to experiment on that
side of the fence have been somewhat limited.

If you disconnect the Airport and reboot, what happens?

There was a problem with Airport firmware that would cause Word network
writes to lock up, but I thought that was fixed with an Airport firmware
upgrade, and that was a long time ago.

Hope this helps

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel
Eternal Spinning Wait Cursor on editing Any Word Document (including when
opening a fresh word session)

This is a continuation of a trouble request that seems to have closed itself
though it was never resolved.

Original Thread:

http://www.officeformac.com/ms/ProductForums/Word/9531

Summary:

Word freezes on entry more-often-than-not. I start typing or any other edit
function nothing happens at first (not text or anything), and then I get the
spinning wait cursor which continues until I do a "Force Quit."

I cannot predict when or where the hang will occur so I cannot avoid it. I'm
at the point where am falling to iWork as a backup - a sub-optimal solution
since I work in a MS Office 2007/8 shop and Pages and Word are not 1:1
compatible when using *.doc as a go-between.

I have done the following with *both* 32-bit and 64-bit mode.

In all cases, I've checked all updates for both OSX (now at 10.6.3 (Build
10D573)) and Word (now at 12.2.4, with Entourage for Web services at 13.0.4)

------------

What's been described as the easy fix

1) Validated the Fonts in Font Book

2) Repaired both the Disk Permissions and the Disk (even though it didn't need
it)

3) Shutdown & Restart after a few minutes

------------

1) the scorched earth uninstall and install, described by several MPVs and
summarized in the thread below.

http://www.officeformac.com/ms/ProductForums/Word/9903/45

(As such my Normal template is the default one with no embellishments at
present)

======================================

Sample Error is below.

I went through a bunch of these and have found that they change with each
crash. Sometimes, the "co-casher" is airport, sometimes it's the addressbook,
vm fusion, activity monitor, etc...

Date/Time: 2010-04-10 18:56:04 -0600
OS Version: 10.6.3 (Build 10D573)
Architecture: x86_64
Report Version: 6

Command: Word
Path: /Applications/Microsoft Office 2008/Microsoft
Word.app/Contents/MacOS/Microsoft Word
Version: 12.2.4 (12.2.4)
Build Version: 0
Project Name: (null)
Source Version: 100205
Parent: launchd [452]

PID: 3961
Event: hang
Duration: 2.99s (sampling started after 2 seconds)
Steps: 9 (100ms sampling interval)

Pageins: 0
Pageouts: 0

Process: Microsoft Word [3961]
Path: /Applications/Microsoft Office 2008/Microsoft
Word.app/Contents/MacOS/Microsoft Word
UID: 1261

Process: AirPort Base Station Agent [473]
Path: /System/Library/CoreServices/AirPort Base Station
Agent.app/Contents/MacOS/AirPort Base Station Agent
UID: 1261

Thread d878620 DispatchQueue 1
User stack:
9 ??? (in AirPort Base Station Agent + 5692) [0x10000163c]
9 NSApplicationMain + 364 (in AppKit) [0x7fff84997d7c]
9 -[NSApplication run] + 395 (in AppKit) [0x7fff8499f05b]
9 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] +
155 (in AppKit) [0x7fff849d9379]
9 _DPSNextEvent + 708 (in AppKit) [0x7fff849d9a2a]
9 BlockUntilNextEventMatchingListInMode + 59 (in HIToolbox)
[0x7fff82b74798]
9 ReceiveNextEventCommon + 310 (in HIToolbox) [0x7fff82b748df]
9 RunCurrentEventLoopInMode + 333 (in HIToolbox)
[0x7fff82b74ada]
9 CFRunLoopRunSpecific + 575 (in CoreFoundation)
[0x7fff8865f8df]
9 __CFRunLoopRun + 1698 (in CoreFoundation)
[0x7fff88660452]
9 mach_msg_trap + 10 (in libSystem.B.dylib)
[0x7fff887c675a]
Kernel stack:
9 ipc_mqueue_receive_continue + 0 [0xffffff800026e5de]

Thread d9c6000 DispatchQueue 2
User stack:
9 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff887e0385]
9 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff887e04e8]
9 _dispatch_worker_thread2 + 252 (in l

--

The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410 | mailto:[email protected]

 

[CyberTaz]

I agree with John that there are external forces at work, but I haven't
ruled out fonts altogether In your reply you indicate that you
*Validated fonts* [#1] but you don't mention having Resolved Duplicates.

On the AirPort issue, there is also a recent update to the software. I
believe it requires the firmware updates so perhaps it will guide you along
when you apply it.

Also, it might be a good idea to retrieve the 10.6.3 COMBO updater for OS X
an apply it over you existing installation.

HTH |:>)
Bob Jones
[MVP] Office:Mac

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel
Eternal Spinning Wait Cursor on editing Any Word Document (including when
opening a fresh word session)

This is a continuation of a trouble request that seems to have closed itself
though it was never resolved.

Original Thread:

http://www.officeformac.com/ms/ProductForums/Word/9531

Summary:

Word freezes on entry more-often-than-not. I start typing or any other edit
function nothing happens at first (not text or anything), and then I get the
spinning wait cursor which continues until I do a "Force Quit."

I cannot predict when or where the hang will occur so I cannot avoid it. I'm
at the point where am falling to iWork as a backup - a sub-optimal solution
since I work in a MS Office 2007/8 shop and Pages and Word are not 1:1
compatible when using *.doc as a go-between.

I have done the following with *both* 32-bit and 64-bit mode.

In all cases, I've checked all updates for both OSX (now at 10.6.3 (Build
10D573)) and Word (now at 12.2.4, with Entourage for Web services at 13.0.4)

------------

What's been described as the easy fix

1) Validated the Fonts in Font Book

2) Repaired both the Disk Permissions and the Disk (even though it didn't need
it)

3) Shutdown & Restart after a few minutes

------------

1) the scorched earth uninstall and install, described by several MPVs and
summarized in the thread below.

http://www.officeformac.com/ms/ProductForums/Word/9903/45

(As such my Normal template is the default one with no embellishments at
present)

======================================

Sample Error is below.

I went through a bunch of these and have found that they change with each
crash. Sometimes, the "co-casher" is airport, sometimes it's the addressbook,
vm fusion, activity monitor, etc...

Date/Time: 2010-04-10 18:56:04 -0600
OS Version: 10.6.3 (Build 10D573)
Architecture: x86_64
Report Version: 6

Command: Word
Path: /Applications/Microsoft Office 2008/Microsoft
Word.app/Contents/MacOS/Microsoft Word
Version: 12.2.4 (12.2.4)
Build Version: 0
Project Name: (null)
Source Version: 100205
Parent: launchd [452]

PID: 3961
Event: hang
Duration: 2.99s (sampling started after 2 seconds)
Steps: 9 (100ms sampling interval)

Pageins: 0
Pageouts: 0

Process: Microsoft Word [3961]
Path: /Applications/Microsoft Office 2008/Microsoft
Word.app/Contents/MacOS/Microsoft Word
UID: 1261

Process: AirPort Base Station Agent [473]
Path: /System/Library/CoreServices/AirPort Base Station
Agent.app/Contents/MacOS/AirPort Base Station Agent
UID: 1261

Thread d878620 DispatchQueue 1
User stack:
9 ??? (in AirPort Base Station Agent + 5692) [0x10000163c]
9 NSApplicationMain + 364 (in AppKit) [0x7fff84997d7c]
9 -[NSApplication run] + 395 (in AppKit) [0x7fff8499f05b]
9 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] +
155 (in AppKit) [0x7fff849d9379]
9 _DPSNextEvent + 708 (in AppKit) [0x7fff849d9a2a]
9 BlockUntilNextEventMatchingListInMode + 59 (in HIToolbox)
[0x7fff82b74798]
9 ReceiveNextEventCommon + 310 (in HIToolbox) [0x7fff82b748df]
9 RunCurrentEventLoopInMode + 333 (in HIToolbox)
[0x7fff82b74ada]
9 CFRunLoopRunSpecific + 575 (in CoreFoundation)
[0x7fff8865f8df]
9 __CFRunLoopRun + 1698 (in CoreFoundation)
[0x7fff88660452]
9 mach_msg_trap + 10 (in libSystem.B.dylib)
[0x7fff887c675a]
Kernel stack:
9 ipc_mqueue_receive_continue + 0 [0xffffff800026e5de]

Thread d9c6000 DispatchQueue 2
User stack:
9 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff887e0385]
9 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff887e04e8]
9 _dispatch_worker_thread2 + 252 (in l

 

[Bill_Capehart]

Hi Bill:

>
> OK, looks like it's NOT fonts in your case.
>
> There are several things that can tip Word over in OS 10.6, duplicate fonts
> is one, corrupt or incompatible fonts is another.
>
> But an unstable network will also do this, as will corrupt documents.
>
> You have replaced your Normal.dotm, so we can expect that new documents will
> be OK for you, but that does not mean that existing documents are clean.
>
> I would like to suggest that the log you posted looks as though Word hung
> waiting for a response from the Airport. We're going to have to go hunting
> for this one.
>
> What's on the Airport for you? What kind of data do you store there?
>
> Starting up in 64-bit mode is a relatively "brave" move. Word 2008 runs
> fine in 64-bit mode on this system, but various "nice-to-haves" such as my
> network driver and printer DON'T, so my opportunity to experiment on that
> side of the fence have been somewhat limited.
>
> If you disconnect the Airport and reboot, what happens?
>
> There was a problem with Airport firmware that would cause Word network
> writes to lock up, but I thought that was fixed with an Airport firmware
> upgrade, and that was a long time ago.
>
> Hope this helps

Thanks but here are couple clarifications:

I don't use Airport base or the TIme machine or any other wireless station. It can happen with I have network on, off, landlined or wireless.

Also, it's happening with the brand-spanking post-scorched earth re-installed Normal.dotx, and as I said in the prologue to the error log dump, the program/process that's co-listed in the log changes.

Plus, as I said before the log-dump, Airport is often the one it does the most but also Addressbook or Activity log (looks like it's doing alphabetical order!) will also be seen. (The one I just got a a second ago and am including below) has the address book as the troublemaker.

Date/Time: 2010-04-11 07:37:45 -0600
OS Version: 10.6.3 (Build 10D573)
Architecture: x86_64
Report Version: 6

Command: Word
Path: /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
Version: 12.2.4 (12.2.4)
Build Version: 0
Project Name: (null)
Source Version: 100205
Parent: launchd [440]

PID: 1994
Event: hang
Duration: 3.04s (sampling started after 2 seconds)
Steps: 10 (100ms sampling interval)

Pageins: 22
Pageouts: 0

Process: Microsoft Word [1994]
Path: /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
UID: 1261

Process: Address Book [1992]
Path: /Applications/Address Book.app/Contents/MacOS/Address Book
UID: 1261

Thread bca7000 DispatchQueue 1
  User stack:
    10 ??? (in Address Book + 7004) [0x100001b5c]
      10 NSApplicationMain + 364 (in AppKit) [0x7fff84997d7c]
        10 -[NSApplication run] + 395 (in AppKit) [0x7fff8499f05b]
          10 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155 (in AppKit) [0x7fff849d9379]
            10 _DPSNextEvent + 708 (in AppKit) [0x7fff849d9a2a]
              10 BlockUntilNextEventMatchingListInMode + 59 (in HIToolbox) [0x7fff82b74798]
                10 ReceiveNextEventCommon + 310 (in HIToolbox) [0x7fff82b748df]
                  10 RunCurrentEventLoopInMode + 333 (in HIToolbox) [0x7fff82b74ada]
                    10 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff8865f8df]
                      10 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff88660452]
                        10 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff887c675a]
  Kernel stack:
    10 ipc_mqueue_receive_continue + 0 [0xffffff800026e5de]

Thread bafe098 DispatchQueue 2
  User stack:
    10 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff887e0385]
      10 _pthread_

 

[Bill_Capehart]

TYPO ERROR!

DOH! Any other wireless station made by APPLE.

My typo, sorry

 

[Bill_Capehart]

Also, it might be a good idea to retrieve the 10.6.3 COMBO updater for OS X

> an apply it over you existing installation.

Bob, the 10.6.3 Combo update did not do the trick... still hanging.

 

[CyberTaz]

OK, let's gather a little more insight...

With no other apps running hold Shift while launching Word. Any improvement?

Log out, then hold Shift while you log in. Any change when you launch Word?

Run Word while logged into a different (preferably newly created) User
Account. Any change in behavior there?

Please reply with the results of each of those three separate processes.

Regards |:>)
Bob Jones
[MVP] Office:Mac

 

[Bill_Capehart]

OK, let's gather a little more insight...

>
> With no other apps running hold Shift while launching Word. Any improvement?

That didn't do it. It froze right away.

I've now started the second test: logging back in with the Shift key down.

 

[Bill_Capehart]

Log out, then hold Shift while you log in. Any change when you launch Word?

I have not gotten a spining wait cursor on this yet after a week of shift-login; however, I have not heavily used Word or Excel (meaning more than 5-10 times in a single log-in session. On login w/o shift-login, it's set to fire up Capsee, MyDay, Microsoft Databaset Daemon, VMWare Fusion Helper, and MyBoingo. I have since disabled myboingo since on review, i don't use it much.

 

[Bill_Capehart]

And as soon as I posted above, it came back (on a shift-login session).

 

[CyberTaz]

Of the login items you mentioned the only one I'm not familiar with is
Capsee. The others shouldn't cause the problem, but that one sounds like it
'could' be the type of thing that might. I read your later post but that
could be coincidental - the timing on a Shift-Login can be touchy.

I'd try logging in normally after disabling Capsee. Let us know if that
makes any difference.

Regards |:>)
Bob Jones
[MVP] Office:Mac

 

[Bill_Capehart]

I'm about to start the process of moving to a new account. And testing from there.

As this error takes a while to happen, I will likely need to

a) port my entourage database over to the new account

b) change over the UUID so I can communicate with our linux network,

(b)'s "easy." I've done it before.. But I haven't done (a) before. How painful is it and how should I do that?

 

[Bill_Capehart]

I'm about to start the process of moving to a new account. And testing from there.

Spun and stalled on the new account as well. :-/

OK now what?

 

[John McGhie]

Hi Bill:

Now: "Damn! It's the System!"

Something, somewhere, on that system is locking up Microsoft Office.

It could be something really strange, such as an incompatibility in the
Linux file system preventing Office from locking or releasing files
correctly on the network. If you have a server in play, in here you need to
say so.

The fastest resolution to your issue is to nuke that box from orbit and
start again (format the System volume and re-install OS X from scratch).
However, you may want to do two more diagnostic steps before you do that.

The first would be to run System Profiler (from Apple>About This Mac...) and
save the result as an XML file. Zip it up and email it to me
([email protected]): I will try to persuade one of the Senior Development
Engineers in Test at the Macintosh Business Unit to run his eye down it and
see if there are any obvious software or hardware conflicts.

The second would be to find someone else's Mac, connect it to your network,
and make sure it does not suffer the same issues. For that purpose, it
should be sufficient to bring your machine up from an external bootable
drive on which you can do a clean install of just Apple OS X and Office.

It is entirely possible that there is something to do with your network
configuration or the routing, firewalling (or even the file formats in use)
that is preventing Office from locking and releasing files such as Temporary
files.

Hope this helps

Spun and stalled on the new account as well. :-/

OK now what?

--

The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410 | mailto:[email protected]

 

[CyberTaz]

I'll leave the network issues to John, but did you ever test to find out
whether that program called "Capsee" might be the culprit? I see no
reference to you having done so in your recent postings. It would not be the
first time that such a utility caused a conflict, especially if there are
version/update issues related to it.

Regards |:>)
Bob Jones
[MVP] Office:Mac

 

[Bill_Capehart]

I'll leave the network issues to John, but did you ever test to find out

> whether that program called "Capsee" might be the culprit? I see no
> reference to you having done so in your recent postings. It would not be the
> first time that such a utility caused a conflict, especially if there are
> version/update issues related to it.

Capsee is no longer started on login so that isn't the issue :-/

 

[Bill_Capehart]

It could be something really strange, such as an incompatibility in the

> Linux file system preventing Office from locking or releasing files
> correctly on the network. If you have a server in play, in here you need to
> say so.

One thing to point out here is that I'll get a Word or Excel stall with or without being on a network (including w/o wireless). It also happens both on the office and home networks (not to mention, once again, when floating free).

The fastest resolution to your issue is to nuke that box from orbit and
> start again (format the System volume and re-install OS X from scratch).
> However, you may want to do two more diagnostic steps before you do that.
>
> The first would be to run System Profiler (from Apple>About This Mac...) and
> save the result as an XML file. Zip it up and email it to me
> ([email protected]): I will try to persuade one of the Senior Development
> Engineers in Test at the Macintosh Business Unit to run his eye down it and
> see if there are any obvious software or hardware conflicts.

I will send you a crash file and system profile for each network environment. It'll take some time for this as each config will need to crash first.

Thanks Much
WJC

 

[Bill_Capehart]

The fastest resolution to your issue is to nuke that box from orbit and

> start again (format the System volume and re-install OS X from scratch).
> However, you may want to do two more diagnostic steps before you
> do that.

For the record I am willing to enable the nuclear option. However, I will need guidance as to how to reimport my Entourage mail archives onto my newly reinstalled OS.