Error starting wiki server in Mac Mini server with Mountain Lion 10.8.3

Hi, i've got a problem with my wiki server.
The service doesn't start!
It does an error while i try to start the wiki!
The service can't read the service impostation!
How can i solve it??
Anyone with the same problem??
Thanks!

here the /var/log/apache2/error_log
[Fri Jun 28 10:35:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:35:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:35:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:28 2013] [notice] caught SIGTERM, shutting down
httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
[Fri Jun 28 10:36:31 2013] [notice] FastCGI: process manager initialized (pid 145)
[Fri Jun 28 10:36:31 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
[Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 10:36:36 2013] [notice] caught SIGTERM, shutting down
httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
[Fri Jun 28 10:36:39 2013] [notice] FastCGI: process manager initialized (pid 196)
[Fri Jun 28 10:36:39 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
[Fri Jun 28 10:37:25 2013] [notice] caught SIGTERM, shutting down
[Fri Jun 28 10:37:38 2013] [crit] (17)File exists: mod_rewrite: Parent could not create RewriteLock file /var/log/apache2/rewrite.lock
Configuration Failed
httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
[Fri Jun 28 10:37:48 2013] [notice] FastCGI: process manager initialized (pid 432)
[Fri Jun 28 10:37:48 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
[Fri Jun 28 16:28:22 2013] [notice] caught SIGTERM, shutting down
httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
[Fri Jun 28 16:28:26 2013] [notice] FastCGI: process manager initialized (pid 31415)
[Fri Jun 28 16:28:26 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
[Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:28:30 2013] [notice] caught SIGTERM, shutting down
httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
[Fri Jun 28 16:28:33 2013] [notice] FastCGI: process manager initialized (pid 31466)
[Fri Jun 28 16:28:33 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
[Fri Jun 28 16:43:46 2013] [notice] caught SIGTERM, shutting down
httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
[Fri Jun 28 16:43:49 2013] [notice] FastCGI: process manager initialized (pid 33283)
[Fri Jun 28 16:43:49 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
[Fri Jun 28 16:43:51 2013] [notice] caught SIGTERM, shutting down
httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
[Fri Jun 28 16:43:55 2013] [notice] FastCGI: process manager initialized (pid 33322)
[Fri Jun 28 16:43:55 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
[Fri Jun 28 16:44:41 2013] [notice] caught SIGTERM, shutting down
httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
[Fri Jun 28 16:44:44 2013] [notice] FastCGI: process manager initialized (pid 33499)
[Fri Jun 28 16:44:44 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
[Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
[Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
[Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
[Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
[Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Jun 28 16:44:49 2013] [notice] caught SIGTERM, shutting down
httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
[Fri Jun 28 16:44:52 2013] [notice] FastCGI: process manager initialized (pid 33579)
[Fri Jun 28 16:44:52 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations

Similar Messages

  • Sharing iTunes with a Mac Mini OS X Mountain Lion Server

    I'm adding a Mac Mini OS X Mountain Lion Server to my home network. What options do I have to inetgrate iTunes into the server? Currently my master iTunes library is housed on a RAID on a Mac Pro, home sharing is on, and it interfaces over the network just fine into Apple TV (3rd gen). For instance, with Server can all devices on the network have access to that library?  Could the library stream to the Apple TV in the living room, an iMac in the office, an iPhone in another room all simultaenously? Also, can any Server member order iTunes Store content and cause it it to be placed into the master library on the Ser

    Maybe this discussion will interest you?
    https://discussions.apple.com/thread/3097703

  • If I purchase a mac mini now - will Mountain Lion be avilable free?

    If I purchase a mac mini now - Will Mountain Lion be available free - or should I wait to purchase the mac mini?

    No. It will come with Lion installed. A free upgrade to Mountain Lion would only occur when Apple announces such an option, and only to those who purchase the computer within some period of time after ML is released.
    If saving $30 or so to upgrade to ML is your goal, then wait until it is released and Apple initiates an Up-To-Date program.

  • I have mac mini os x mountain lion can i put snow leopard on the partition

    I have a mac mini os x mountain lion can i put snow leopard on the partition

    on the same partition?  no.  you'll need to create another partition if you want to dual boot, and install SL there.

  • Trouble receiving FaceTime calls on my Mac Mini using OSX Mountain Lion

    I have a Mac Mini using OSX Mountain Lion, an iPad 2, and an iPhone 4.  I tried to receive  a FaceTime call on my Mac but it was telling the caller that it was busy.  I was however able to call her iPhone from FaceTime on my Mac and we connected that way.  After our video conversation I tried testing this by calling my Mac from my iPhone.  I also received the message that it was busy.  I should also add that when I first received the call I had my iPad FaceTime turned on.  The iPad was ringing but not the Mac.  So I turned off FaceTime on my iPad and had her call me back again using my email address.  As noted it said it was busy.  Please help!

    Do you have different FT addresses on your Mini, iPhone and iPad?
    Using FaceTime http://support.apple.com/kb/ht4319
    Troubleshooting FaceTime http://support.apple.com/kb/TS3367
    The Complete Guide to FaceTime + iMessage: Setup, Use, and Troubleshooting
    http://tinyurl.com/a7odey8
    Troubleshooting FaceTime and iMessage activation
    http://support.apple.com/kb/TS4268
    iOS: FaceTime is 'Unable to verify email because it is in use'
    http://support.apple.com/kb/TS3510
    Using FaceTime and iMessage behind a firewall
    http://support.apple.com/kb/HT4245
    iOS: About Messages
    http://support.apple.com/kb/HT3529
    Set up iMessage
    http://www.apple.com/ca/ios/messages/
    iOS 6 and OS X Mountain Lion: Link your phone number and Apple ID for use with FaceTime and iMessage
    http://support.apple.com/kb/HT5538
    How to Set Up & Use iMessage on iPhone, iPad, & iPod touch with iOS
    http://osxdaily.com/2011/10/18/set-up-imessage-on-iphone-ipad-ipod-touch-with-io s-5/
    Troubleshooting Messages
    http://support.apple.com/kb/TS2755
    Troubleshooting iMessage Issues: Some Useful Tips You Should Try
    http://www.igeeksblog.com/troubleshooting-imessage-issues/
    Setting Up Multiple iOS Devices for iMessage and Facetime
    http://macmost.com/setting-up-multiple-ios-devices-for-messages-and-facetime.htm l
    FaceTime and iMessage not accepting Apple ID password
    http://www.ilounge.com/index.php/articles/comments/facetime-and-imessage-not-acc epting-apple-id-password/
    FaceTime, Game Center, Messages: Troubleshooting sign in issues
    http://support.apple.com/kb/TS3970
    Unable to use FaceTime and iMessage with my apple ID
    https://discussions.apple.com/thread/4649373?tstart=90
    How to Block Someone on FaceTime
    http://www.ehow.com/how_10033185_block-someone-facetime.html
    My Facetime Doesn't Ring
    https://discussions.apple.com/message/19087457
    To send messages to non-Apple devices, check out the TextFree app https://itunes.apple.com/us/app/text-free-textfree-sms-real/id399355755?mt=8
    How to Send SMS from iPad
    http://www.iskysoft.com/apple-ipad/send-sms-from-ipad.html
    You can check the status of the FaceTime/iMessage servers at this link.
    http://www.apple.com/support/systemstatus/
     Cheers, Tom

  • Is my mac pro compatible with mountain lion?

    Is my mac pro compatible with mountain lion/ 2 x 2.66 Ghz Dual core processors?
    Any help would be appreciated. Thanks
    William

    And FBDIMMs which use to cost $300+ for 8GB can now be had for... 2 x $34.
    I paid $300 2 x 512MB August 2006,, then 2 x 1GB $400 March '07
    So as long as you only need 16GB you are safe, it is when you need 4GB, or the rare 8GB FBDIMM and 32GB or more, that yes, time to part ways and get a system that supports cheaper DDR3.
    Except, right now, 10.8.2 'broke' support for more than 64GB and there were people depending on and using 96GB.  Or that more than 48GB also 'broke' the Apple Pro RAID card; a card that still does not support 3TB drives. 10.8.2 does though provide support for more current Nvidia cards (10.7.4 also showed support just not for GTX 6xx series). 3rd party graphic support has always been a weakness, until now.
    Apple Mac Pro is a workstation. Except when it is not. It is still not clear how they missed these things.
    What 32-bit EFI won't get you is 64-bit kernel mode and abilty to fully use more powerful graphic cards or memory addresses for a single process beyond 4GB or graphic card support with more than 2GB (and 2GB use to always fail in OS X in the past).

  • Do I get a free upgrade to Mountain lion on my MacBookPro if I just purchased a new Mac Book Air with Mountain Lion installed?

    Do I get a free upgrade to Mountain lion on my MacBookPro if I just purchased a new Mac Book Air with Mountain Lion installed?

    Sorry, no.

  • Error starting managed server with JRockit VM

    I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
    option on. The OS is NT. Any clues , please ?
    exception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    D:\i252\services>runtxnserver
    JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
    Garbage Collector, started.
    [JRockit] Starting Management Server on port 7090
    Starting WebLogic Server ....
    Connecting to http://ocncat2:7991...
    <May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on fd:
    4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
    java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
    35c4a
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    >
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
    tected attempting to connect to admin server at http://ocncat2:7991 during i
    alization of managed server ( null:7551 ). The reported error was: < java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) > This condition generally results when the managed and
    n servers are using the same listen address and port.>
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize th
    rver: 'Fatal initialization exception
    Throwable: weblogic.management.configuration.ConfigurationException: java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    '>
    The WebLogic Server did not start up properly.
    Exception raised: weblogic.management.configuration.ConfigurationException:
    .io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace

    I found the solution . The reason for this is that JRockit's High Performance Thread
    System uses asynchrounous I/O "under the hood". Weblogic's Native I/O is also asynchronous.
    The two asynchronous I/O systems clash and the result is the error you see.
    There are two ways around this problem. Either disable JRockit's High Performance
    Thread System (or thinthreads) by using the -Xnativethreads command line flag, or
    disable Weblogic's Native I/O.
    For Weblogic 6.0 and higher, edit the config.xml file. Find the line saying NativeIOEnabled="true"
    and change this to NativeIOEnabled="false".
    For Weblogic 5.1 you edit the file weblogic.properties and change the line weblogic.system.nativeIO.enable=true
    to
    weblogic.system.nativeIO.enable=false
    "Manoj jayadevan" <[email protected]> wrote:
    >
    I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
    option on. The OS is NT. Any clues , please ?
    exception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    D:\i252\services>runtxnserver
    JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
    Garbage Collector, started.
    [JRockit] Starting Management Server on port 7090
    Starting WebLogic Server ....
    Connecting to http://ocncat2:7991...
    <May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on
    fd:
    4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
    java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
    35c4a
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
    C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
    Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    >
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
    tected attempting to connect to admin server at http://ocncat2:7991 during
    i
    alization of managed server ( null:7551 ). The reported error was: < java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) > This condition generally results when the managed
    and
    n servers are using the same listen address and port.>
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize
    th
    rver: 'Fatal initialization exception
    Throwable: weblogic.management.configuration.ConfigurationException: java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
    C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
    Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    '>
    The WebLogic Server did not start up properly.
    Exception raised: weblogic.management.configuration.ConfigurationException:
    .io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
    C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
    Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace

  • Mac Mini mid 2011 Mountain Lion sleep and don't wake after +/- 6h of sleep

    Hello all.
    I Have a Mac Mini mid 2011 with Mountain Lion 10.8.5. connected to Wi-Fi network with Time Capsule, with back to Mymac enabled as well as ssh.
    The power save is set as default to wake up on lan, put to sleep the disks as nedeed.
    It works fine , and i can wake him up by back to mymac or just ssh to until +/- 6 hours of inactivity, after I Can't wake him up unless by bluetooth or with the power button.
    I had made a fresh install but it works realy the same.
    Before update to Mountain Lion , it was working fine.
    Can someone help me
    Thanks in advance.
    PC

    You don't need an expensive USB keyboard, a £10 Logitech UK - Keyboard K120 will work just fine for booting into the Recovery Partition to Repair or Reinstall OS X.
    Also see > OS X: About OS X Recovery

  • Gestures won't work after waking my mac from sleep with mountain lion. can anyone resolve this issue?

    is seems like quite a few mac users with mountain lion installed have this issue.  can someone help me out?

    Error "The serial number is not valid for this product" | Creative Suite

  • Mac Mini 2011 and Mountain Lion ERROR?

    Hello! I have a Mac Mini 2011 that came with Lion, since I uprgade to Mountain Lion, my Mac Mini stops working (Mouse Freezes) and a GRAY SCREEN APPEARS!! and says that the computer have to RESTART! Any Ideas?
    Thanks

    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the page that opens.
    Select the most recent panic log under System Diagnostic Reports. Post the contents — the text, please, not a screenshot. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header and body of the report, if it’s present (it may not be.) Please don't post shutdownStall, spin, or hang reports.

  • Lion Server with mountain lion computers?

    Hello,
    So i am running a mac pro 1.1 with Lion server because it won't run mountain lion, I am thinking about upgrading my other computers to mountain lion are there any issues or features that aren't availible or will be problematic?
    Thanks

    The difference between case 1 and cases 2-4 are that in 1 the client is letting the server expand the group membership, and in 2-4 it's the client doing that expansion.  The group members returned by the server when it expands the group are "guaranteed" to work because the server definitely knows about them (and providing them to the client).  In the cases where it's the client adding the attendees, I suppose there must be some mismatch sometimes, although I don't know what that could be if the email addresses are the same between the users you've created via Contacts.app and the users you've created via Server.app.
    I actually tried this setup and it was working fine.  What caused you to want to duplicate the users and groups that you have in Server.app into Contacts.app?

  • Can't acces lion server with Mountain Lion

    I upgraded to to Mountain Lion and now its telling me I cannot access Lion Server on this Mac? I was able to access it before the upgrade.

    Did you upgrade to the Server version of Mountain Lion? If  you did not that explains why you cannot access it. However if you did please repost in the correct forum which is:
    https://discussions.apple.com/community/mac_os/os_x_mountain_lion

  • Mac mini wont run mountain Lion

    I have just purchased a 2nd hand 2009 mini mac, and have updated the snow leopard osx.
    I checked the spec to be able to run mountain Lion and my machine just meets it...core 2 duo 1.83ghz,upgraded to 2gb ram.
    I have purchased Mountain Lion for £14 from apple, and got a download link. Right at the start of the download stage, a warning pops up that my machine isn't able to run it.
    I have adequate hard drive space,and realise I am close to edge of compatability,  is it because "apple" is recognising my machine as originally having less than 2gb, thus says it is unable to run it?
    other questions are, as I ordered the download, but then it failed will I still be charged?
    also, if available could I purchase a physical disk and install either on top of my existing OS or even on a new HD.....
    I am a new convert having previously done many many windows upgrades etc, so I am learning a bit...Any help would be great, my reason for wanting to upgrade is I wan't to down load Mac Apps, which you have to have mt Lion to do?
    many thanks

    Yes, thxs for that, my current os is defo 10.6.8, i've run an update, and it says the software is up to date....
    My current o/s is I guess snow leopard, and i wan't to get to at least Lion or mountain Lion...
    I realise Mavericks is a free upgrade, but i really dont think my machine would run that, but my first issue is getting Mt Lion installed, i understand you can't buy Lion on its own so i purchased Mt Lion...
    but like i said, i am unsure if my machine meets the required spec for even that as the ram is just upgraded to 2 gb...
    is there a way around the install checking what spec the machine is that it is being installed on to?, although i am unsure if i am even near to that stage as it won't even start the down load...
    i will try again!!!
    thanks again, has anyone else got any advice...
    sorry one last thing, will it be anything linked to my serial number?, it isn't listed under "about my mac", i suspect as it may well have been effected when the ram was expanded to 2gb, would that cause an issue, I have the serial number on the original box, can i re establish that with the mac if that is the cause?

  • Mac Mini/Xcode/OS Mountain Lion issue

    Hi everyone,
    I'm a complete newbie to macs and I'm having a tough time figuring a couple of things out. I basically bought a mac mini so I can use Xcode. I went to try and download it but when it finishes and I open the Xcode file I get a message that says "Xcode Not Supported On This Archtecture". I hit software upgrade but it stays stuck on version 10.5.8. Then I see that you can pay $20 bucks for the newest Mountain Lion update.
    Do I need to get Mountain Lion in order for Xcode to work on my Mac Mini?
    For further info, I signed up as a developer and I have the 3 gig version of the Mac Mini. I've heard kind of confusing things regarding Xcode with people saying it's free but others saying you have to pay an annual fee. At the moment I haven't paid for anything relating to Xcode.
    Basically my main question is, how do I get Xcode up and running?
    Sorry if this is all super rookie bush league but I'm brand new to the mac world.
    Thanks for all your help.

    Xcode is free. A basic login to the developer site is free. For $99 you get full membership in the developer program and the ability to release software either in the App Store (depending on either iOS or Mac program). If you are in the Mac developer program you can release software with a Developer ID. You also get access to different versions of the operating system for testing.
    The problem is that your Mac Mini is from 2007 at best. It will not run Mountain Lion. You can call Apple (yes - telephone only - no online sales) and purchase either Snow Leopard or Lion. In the developer site you can download an older version of Xcode appropriate for whatever operating system you want to run. That will be enough to learn on. If you ever want to move publishing your apps, you will need a new system.

Maybe you are looking for

  • Correlation and Async/Sync Communication using JMS adapter without BPM

    Hello 1. Pls explain with simple example docs/links --- Correlation 2. Async/Sync Communication using JMS adapter without BPM    If i see blog --- If I go with blog --- /people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-w

  • Having problem getting my mac book air to set up

    I need help setting up my computer? I am stuck on there intetact with desktop content is empty

  • Changing the default currency of an entity after it has data stored

    We would like to setup some new entities that are not incorporated for our Actuals collection yet and submit data to our Forecast scenario for them. The issue is the entities currency may change by the time it is incorporated at which point we would

  • Interactive image not working

    I insert the interactive widget. I bring in an image and create the labels. I Set View. I click on Show Interactive Tools. But when I go to the iPad it shows the images with the labels but the photo is out of focus, the labels are out of focus, and t

  • IMac - gray screen after OSX 10.9.4 upgrade

    iMAC 21.5-inch, Late 2009 Processor  3.33 GHz Intel Core 2 Duo Memory  16 GB 1067 MHz DDR3 Graphics  ATI Radeon HD 4670 256 MB Software  OS X 10.9.4 (13E28) After being gone for 2 weeks we returned home and initially the iMAC booted fine and my wife