Error Code -10810

Question

Level 1

5 points

Error Code -10810

Very frequently my mac using leopard just refuese to do anything, open applications, open finder window etc.

the box the shows up just has -10810 in it.

What the heck is this and how do I repair it?

MacBook Pro, Mac OS X (10.5.1), -10810

Posted on Dec 27, 2007 11:47 AM

Reply

Answer 1

baltwo

Level 9

62,386 points

Dec 27, 2007 12:56 PM in response to Aristocat

Google reveals http://forums.whirlpool.net.au/forum-replies-archive.cfm/573675.html with a link to a possible solution. I've never seen the problem, but searching is a good way to find answers.

Reply

Answer 2

Aristocat Author

Level 1

5 points

Dec 27, 2007 1:36 PM in response to baltwo

I have googled it, this link does reference -10801 but is on MacOSX Server. I am running just a Mac Pro laptop with leopard.

Besides you would have to be a PC weenie to understand the lingo needed to address the issue.

Reply

Answer 3

baltwo

Level 9

62,386 points

Dec 27, 2007 3:23 PM in response to Aristocat

Then, it's off to geek school. Many items WRT to Server apply to client machines. I suspect something associated with Samba is causing the problem.

Reply

Answer 4

Aristocat Author

Level 1

5 points

Dec 28, 2007 8:00 AM in response to baltwo

I bought a Mac to avoid "geek school". Thats VISTA.

Samba sounds like a dance, is this the PC guy ?

Where is the useful help?

Reply

Answer 5

baltwo

Level 9

62,386 points

Dec 28, 2007 2:30 PM in response to Aristocat

Then, google *error 10810* and review the results. http://monkeyfilter.com/link.php/11144 seems promising. Additioinally, see http://www.thexlab.com/faqs/multipleappsquit.html I've run out ideas. Good luck.

Reply

Answer 6

Dec 28, 2007 2:43 PM in response to Aristocat

Hi Aristocat,

I also had this Error after installing Leopard. The cause in my case was one of the programmes which was running at startup was incompatible with Leopard. (It was a hangover from my Tiger install.)

If you go to System Preferences, Accounts, Login Items, you may find something in there is responsible.

Good luck!

Frank

Reply

Answer 7

Aristocat Author

Level 1

5 points

Dec 29, 2007 7:25 AM in response to Frank Hand

First my apologies to everyone, I get grumpy with computers (no people), I want to thank all of you for your assistance.

Called Apple, they are familiar with this error occurrence ( although somewhat tight lipped) They had me rebuild permissions, (no help) then disk verify (it was fine) and then turn off my airport disk sharing thingy (no help), there last instruction was to reinstall Leopard (archive option) have not done this.

On my own observation (copious notes) I have narrowed it down to the screensaver, or something that occurs after the screensaver is turned off by awakening the Mac. I have turned off the screensaver and so far no further problems.

Actually my Macbook is noticeably more zippier in performance.

I had one of Iphoto albums as a screensaver.

Hope this helps someone else. If it occurs again I will post, otherwise Ciao

Reply

Answer 8

baltwo

Level 9

62,386 points

Dec 29, 2007 12:15 PM in response to Aristocat

Thanks for the feedback. Good computing.

Reply

Answer 9

Jan 12, 2008 9:58 AM in response to Aristocat

Have you tried checking your system.log? I found helpful errors about what my program was doing. Fortunately for me, the program which was failing with this error also echoed a more descriptive error message to the system.log error file. You might give that a try and see if you can discover what exact programs are doing what wrong that is causing the failure. I have seen a few people narrow down and find a way of solving the issue by doing this.

You can get to the system.log file by opening the Console.app utility found in the Utilities folder. Click the “Show Log List” icon in the icon bar, and that should show you a list of your log files, with system.log and others. Search in there or browse to see what you find.

Reply

Answer 10

Aristocat Author

Level 1

5 points

Jan 18, 2008 8:33 AM in response to Aristocat

Well, to date no more -10810 errors, although now when rebuilding my ppermissions I get errors about suids being changed and the item is not updated.

I tried the system log thing, I could never find anything in the system log. Although I am now using this approach when things get skanky.

I discovered by looking in the system log a whole bunch of things that were still trying to run even after I trashed the original appplication.

I hunted them down and trashed em. Things run quicker. I thought the MAC was supposed to be smarter than than average PC, however in these log files you many things that you probably should not know about. A lot of errors and weird messages about things trying to happen but they fail.

Oh well, it has been a trip so far.:]

Reply

Answer 11

Jan 27, 2008 1:24 PM in response to Aristocat

In my machine, I have traced the problem to a bug in Microsoft IntelliPoint Mouse Driver Software Version 6.0 (v.147).

The problem manifests itself when the wireless mouse battery is running low. When this happens, the Mouse Driver causes a dialog box to appear on the screen letting you know that your mouse is critically low. It has a way of dismissing the alert or postponing it until later.

The problem is that neither of these function properly. If I postpone or dismiss, the Driver software immediately spawns a new dialog, over and over and over.

I like to run my batteries down completely, so I moved the alert into the background. This is when things started to act up and I started to get the 10810 messages.

When I replaced my batteries in the mouse, the dialog boxes stoppped and the error 10810 stopped.

Reply