Office v.X "unexpected error...Framework X"

[russkle]

Everytime I launch any of the Office v.X apps besides Entourage, I get the following error:

An unexpected error occured while trying to load the Microsoft Framework X library.

I have reinstalled, blew away the prefs, blew away the prefs and reinstalled... all to no avail. I remember there being some problem when the database daemon doesn't load adn the app tries to do its copyright protection checking; however, it seems to be runing just fine. At least is is in the Login apps. (Anyone know what it shows up as in Processes?) Anyways... it is driving me insane. The only other culprit I can think of is the Palm beta. Anyone else out there experiencing this problem or have any ideas?

Russell
russkle@mmcable.com

[xchanyazy]

In Process Viewer, the Daemon shows up as LaunchCFM App, along with a bunch of other programs. In top, it shows up as "Microsoft ", as do the office apps and IE. However, if you quit any of those apps and a Microsoft is still listed in top, you will know that it is running.

[russkle]

Yup, then the database daemon is definately running. I uninstalled the Palm beta. I also resinstalled the Entourage Hotmail fix... it installs a new Microsoft Framework X. Still I'm having the same problem. This is driving me crazy. Nothing shows up in console either. Could this be the "check for piracy" network action failing? How do I tell? I'm using a Linksys Cable/Modem router and their is a remote, bery remote possibility that this began when I ugraded its firmware.... Surely someone has had this problem before. I've searched all the major Mac sites and google to no avail.

helllllppppp....

[mervTormel]

% ps axww | grep microsoft
  406  ??  S      1:07.20 /Volumes/xapps/Microsoft Office X/Office/Microsoft Database Daemon \
/Volumes/xapps/Microsoft Office X/Office/Microsoft Database Daemon -psn_0_3014657
 3369  ??  S      1:01.90 /Volumes/xapps/Microsoft Office X/Microsoft Entourage \
/Volumes/xapps/Microsoft Office X/Microsoft Entourage -psn_0_18743297
 6850 std  R+     0:00.01 grep -i microsoft

now then, are there any messages in /var/log/system.log about the framework errors?

have you messed around with any permissions?

if you create a new user and give them access to the apps, do the same exceptions occur?

reinstalled hotmail fix? do you use hotmail? prolly not the 'check for piracy', but, is there another node on the net running ms product?


let us know. more info, better.

[russkle]

Well I have found some more information. According to a thread on MacFixIt (http://www.macfixitforums.com/php/sh...=&view=&sb=&o=) , this is a problem with a Entourage Profile database that has been "locked". Not neccessarily locked in the file system, more likely some internal flag that sets this status. The fix for it is creating a new Indentity and copying all your data over. Yikes! I have over 3000 messages, I don't think I want to do this. I've done the basic database repair (hold OPTION while starting Entourage) to no avail. I'm doing advanced now. I'm hoping to avoid a complete rebuild just for this.

This most likely occured when I had a power outage a few weeks ago and I was logged into Entourage. For the new Imac that I hope gets shipped doon, I've bought a UPS to avoid these problems.

I'll let everyone know what the final result is....

[mervTormel]

russkle,

often, a technique for implementing a lock mechanism in UNIXland is creating a file, sometimes named indicating it is the locking mechanism.

these may be fleeting files that other MS v.X users won't see even while running the apps. perhaps yours was created and you crashed during that fleeting moment.

so search for a file with lock in the name

% find <path> -name "*[L-l]ock*" -print

where path could be obvious MS data, like your $HOME or the MS Office app dir

then again, the locking mechanism may be internal to a db file. but the search is prudent.

let us know.

[russkle]

Thanks for your help. I did search for the lock files and only found the default .FBSLockFolders files. I did what the macFixIt Forum said and created a new Intetity and the problem is now resolved. I think M$ should definately come up with a better way of fixing this.