What is CSCONFIGDOTMACCERT? How do I stop it?

Question

Level 1

0 points

What is CSCONFIGDOTMACCERT? How do I stop it?

For what ever reason this CSCONFIGDOTMACCERT is running the processor at a 100%. It just started today and I thing the only thing new is the update to the iwork programs. Help

MacBookPro5,3, Mac OS X (10.6.4)

Posted on Sep 1, 2010 4:11 PM

Reply

Answer 1

rkaufmann87

Level 10

140,682 points

Sep 1, 2010 4:40 PM in response to jqkern

Have you restarted the computer?

Reply

Answer 2

jqkern Author

Level 1

0 points

Sep 1, 2010 4:54 PM in response to rkaufmann87

Yes several times it always goes back to running that process.

Reply

Answer 3

rkaufmann87

Level 10

140,682 points

Sep 1, 2010 5:01 PM in response to jqkern

I just Googled CSCONFIGDOTMACCERT, it appears it's something to do with MobileMe. Do you have a MobileMe account?

The things I'd try are a SMC reset and PRAM reset, they're pretty simple to do just go to these advice letters:

http://support.apple.com/kb/HT3964

http://support.apple.com/kb/HT1379

Reply

Answer 4

jqkern Author

Level 1

0 points

Sep 1, 2010 7:12 PM in response to rkaufmann87

Tried both of those. Did not work.

Reply

Answer 5

rkaufmann87

Level 10

140,682 points

Sep 1, 2010 7:26 PM in response to jqkern

Do you have a MobileMe account?

Reply

Answer 6

jqkern Author

Level 1

0 points

Sep 1, 2010 8:41 PM in response to rkaufmann87

Yes I do have a mobile me account.

Reply

Answer 7

jqkern Author

Level 1

0 points

Sep 1, 2010 9:17 PM in response to jqkern

So I turned off MobileMe and I rebooted. Problem solved. Guess i'll look around the MobileMe forum to fix it.

Thankks!

Reply

Answer 8

rkaufmann87

Level 10

140,682 points

Sep 1, 2010 9:36 PM in response to jqkern

Your welcome.

We've narrowed it down, try this look in your ~/Library/Preferences folder for a .plist file with MobileMe in it.I suspect the file will be called com.apple.MobileMe.plist but I'm not positive because I don't use MobileMe. Once you have found it drag it to your desktop and then restart MobileMe and see if that fully takes care of the problem.

Reply