More Snow Leopard issues with old apps, including Office
Wednesday, September 2, 2009
Two readers report older versions of cross-platform software not running in Snow Leopard. Ausilia Corso said that Office 2004 no longers runs after upgrading to Snow Leopard:
I just installed Snow Leopard and now can't open Mac Office 2004 not for love or money. Have gone looking for a fix, both from Microsoft and Mac and no one seems to have one. I have uninstalled and installed Mac Office 2004 to no avail. I'm trying to run a business and frustrated.
William Jackson reports that an older version of CrossOver no longer runs after installing Snow Leopard:
Crossover 7.1 won't run under Snow Leopard. Bounces tries to open, but doesn't. The current version of VMware 2.0.5 runs on Snow Leopard with a Windows XP VM. It connected to the Internet without a hitch.
The current version of Crossover, v8.0, does run in Snow Leopard. CrossOver runs certain Windows programs on Mac OS X without the use of Windows.
On Monday, we reported that Snow Leopard does not run older versions of Parallels Desktop, though it does run the current version without problems.
Suggestions for Snow Leopard Office 2004 problem
Friday, September 11, 2009
Chris Carrier believes that a previous report about Office 2004 not working in Snow Leopard may be because Rosetta isn't installed:
I have not had any problems running Office 2004 after installing Snow Leopard. You just need to manually install Rosetta from the Snow Leopard install disk. It did not automatically install in my case. From memory there is a folder called something like "Other Installations" or something similar on the Snow Leopard installation dialogue box. Click the "package" inside it and select the Rosetta option from the list, then all should be well. Might want to reboot after just to be sure.
Phil Ershler has another suggestion
I'm having no problems whatsoever with 10.6 and MS Office 2004. My only suggestion is to make sure that the version of Office 2004 you are trying to run has all of the current patches applied.
If you've seen this issue and tried these suggestions
Update on Office 2004 compatibility problem with Snow Leopard
Monday, November 30, 2009
Paul Roberts tried a previously reported suggestion to fix a problem running Office 2004 in Snow Leopard, but it didn't help:
I tried the suggestion for reloading Rosetta but my PowerPoint still freezes up my machine when I load it.
If you've seen this problem
Reader reports Snow Leopard Mail problems connecting to Exchange | Top of Page |
Monday, September 21, 2009
Frank Thompson is having problems connecting to Exchange Server from Snow Leopard Mail on several Macs:
Just to let you know that I have had a great deal of problems with Mail under Snow Leopard. I still can't link up to our Exchange Server, even with 10.6.1 except if I use IMAP. And then sending email still doesn't work. My wife has lost her link with her IMAP email as well, despite lengthy support calls to the provider.
Beyond that, Snow Leopard has had three system crashes already when everything freezes solid. It has been years since my Mac crashed like this. There seem to be serious bugs to sort out. In the meantime I now have less of a Mac than I had before the 'upgrade.' I'm very disappointed and hope that 10.6.2 is released fast.
If you've seen this problem
Another report of Snow Leopard Mail errors connecting to Exchange
Wednesday, September 30, 2009
Robbie Thielemans responded to a report about problems connecting to Exchange Server from Snow Leopard Mail:
I have same issues here from the moment I upgraded to Snow Leopard. Whilst connecting to Exchange with Entourage, it constantly loses connection (error, cannot connect to server). Sometimes I need to retry ten times to send the same email. All the settings have remained the same as Leopard. I have no idea what causes this, and professionally this is really not workable.
If you're seeing this problem
Reader thinks Sarari 4.0.4 related to Entourage problem | Top of Page |
Monday, November 16, 2009
Chris Ryan starting having problems with Entourage and Exchange when he upgraded Safari:
It may be coincidental, but on Mac OS X 10.6.2, the Safari 4.0.4 update appears to have broken Exchange support not only in Mail.app and iCal but also in Entourage. I would hold off on this update until this becomes clear. I have our IT department looking into it.
If you've see this issue
Calendar delegation using iCal with Exchange Server | Top of Page |
Monday, December 14, 2009
Paul Koch has a problem with iCal and Exchange Server 2007:
I am having trouble configuring iCal so other Exchange users can view my calendar. I am using iCal in Mac OS X 10.6.2. The company is running Exchange Server 2007. My Exchange e-mail works and Exchange calendar invitations work. Going through iCal > Preferences > Accounts > Delegation > Edit, my password is accepted.
But then I do not see a list of Exchange users to which I can delegate access, and any new names that I try to add are not recognized. Likewise, I can't see the names of anyone whose calendar I might view.
In the Exchange account setup, I note that the internal server and external server names are not the same. When I first set up my Exchange account, outgoing e-mail was not received anywhere until I used an internal server name given by the corporate IT guy. Unlike my experience, calendar sharing seems to be working as expected among company Windows users. This is a small company dominated by Windows/Exchange/Blackberry.
If you've seen this problem or have a suggestion
Reader says Mac OS X 10.6.5 breaks DNS CNAME lookups
Monday, November 29, 2010
Dan Parker reports that the Mac OS X 10.6.5 update breaks CNAME look ups in DNS. He also provides a link to some Apple discussion forums about the problem:
The issue is with CNAMEs to .local addresses are broken. Of course, A records work but CNAME lookups are failing. IP and internal FQDN are fine directly. Also, .local CNAME to .local FQDN are also fine. This isn't a huge problem for most folks but I can imagine it wreaking havoc in the enterprise.
I've opened an incident with AppleCare Education and was told it was "Accepted" to be reviewed by Apple's Engineers and have an incident number. I've also spoken with one of their .edu reps and he confirmed multiple internal and external reports of the issue.
From my understanding, the mDNSresponder is supposed to do XX.local lookups but pass on xx.xx.local or *.xx.local lookups to DNS. Since 10.6.5, this results in an unknown host error. The commands host, nslookup and dig all yield the correct information.
There are a few threads around the Internet referencing this issues with various levels of detail. Here's one. Another referencing mDNSresponder lookups of .local hostnames.
If you've seen this problem
Mac OS X 10.6.5 update wiped out readers' DNS settings
Responding to last week's report "Mac OS X 10.6.5 breaks DNS CNAME lookups," Michael Watts reported a different DNS problem with the update:
My previously reliable wireless connection at work came to an end with the update. I know just enough about networks to go to Prefs, and discovered that the DNS settings for the company's wireless network had vanished. Looking forward to another update.
If you've seen this problem
More on CNAME DNS problem for iOS and Snow Leopard
Wednesday, December 22, 2010
Kevin Parker responded to two reports about DNS problems with CNAME lookups with iPhones ("TIP: DNS fix for iPhone iOS4 error in Exchange inbox") and with Snow Leopard ("Mac OS X 10.6.5 breaks DNS CNAME lookups"). They may be related:
We are experiencing this, but it appears to be a bigger DNS issue with CNAMEs, and in our case, affects Mac OS X 10.6.x, iPhones, and iPads. I added comments to this Apple thread, but also copied them here below:
I am experiencing the same issues re: unable to connect to a server via its CNAME record pointing, a FQDN (server1.ourdomainname.NET), internally to an A record. I can look up the information and see the A record and IP to which this ".net" zone CNAME points, but I can't ping it.
Strangely, we have another CNAME record for "server1.ourdomainname.LOCAL" that points to the CNAME "server1.ourdomainname.NET" (the one I can't reach internally), and THAT one resolves fine. But it doesn't help when it's our mail server and I need to be able to access both on and off site.
THIS IS NOT LIMITED TO MACS. Our iPhones AND iPads are experiencing the exact same behavior. I.E., they can reach the FQDN externally, but not internally. This all happened about the same time. Windows clients are unaffected by this one DNS oddity on our network. Even my Windows 7 VM on my Mac can resolve the FQDN fine internally.
If you've seen this issue
Mac OS X 10.6.6 fixes problem with DNS CNAME lookups
Dan Parker followed up on his previous report that Mac OS X 10.6.5 problem with breaking DNS CNAME to .local address look ups:
Just a follow up. This appears to be fixed in 10.6.6.
Other readers have reported this problem as well. If the Mac OS X 10.6.6 update fixes the problem for you
TIP: Fix for error in Apache web server after 10.6.5 and 10.6.6 upgrades
Jim Ferr alerted us to a bug in Apache, Mac OS X's web server, after upgrading to 10.6.5 or 10.6.6. Fortunately, he also provided the solution, which is to edit the apachectl script by editing this line:
ULIMIT_MAX_FILES="ulimit -S -n `ulimit -H -n`"
and replacing it with this line:
Here is Ferr's report:
There's an error in Apache after 10.6.5 upgrade:
/usr/sbin/apachectl: line 82: ulimit: open files: cannot modify limit: Invalid argument
Here and here are two articles with the solution.
If you've tried this new version of VirtualBox