Several hot topics emerged this week on the newsgroups involving the install of Office 2008 SP1 Update.
- Office Setup Assistant opens when I try to open an Office 2008 application View fix
- Installer fails with an alert saying "there was nothing to update" View fix
- This problem can also be caused by a modification of the Office files. See details here.
- Installer fails with an alert saying "Version required not found." View fix
- This error can be caused by user error... confusion over 12.1.0 and 12.0.1. View fix
- Entourage fails to start. It crashes immediately. View fix
- When I deploy Office 2008 for Mac SP1, the update is not installed on client computers. View fix
- Office apps not opening some documents correctly when double-clicking them, or when downloading them from a Web site. View fix
Note some links above will not work until you view the extended view. (added 5/20)
Problem: Entourage fails to start. It crashes immediately.
Solution: Move the Microsoft User Data folder to the desktop. Re-install Office 2008 from DVD. Run the SP1 upgrade. Move MUD folder back.
Problem: 'There was nothing to update'
Cause: 'There was nothing to update' was discussed in this workaround. However, this problem can also be caused by a modification of the Office files. See the details in the section Users that have modified, moved or changed Office User reports: I had run a language pack utility to save disk space. This deleted many of the languages that came with Office. This was not allowing me to update.
Solution: Without uninstalling anything, insert the Office installer DVD and run installer. It should now update successfully.
If you continue to have problems....
You might need to download the combo updater from Apple and run it again rather than using Software Update. Doing so overwrites potentially problem-causing files. Several users have reported this fixed some odd problems they were having with Office. Combo updaters will install on the same version as they're applying--no need to roll back or do a clean install.
Leopard:
Mac OS X 10.5.2 Combo Update (This update delivers several improvements for both PowerPC- and Intel-based Macs )
Tiger:
Mac OS X 10.4.11 Combo Update (PPC)
Mac OS X 10.4.11 Combo Update (Intel)
Not directly involving Entourage, but a problem that started with SP1:
Mactopia has published a new topic regarding the issue around Office apps not opening some documents correctly when double-clicking them, or when downloading them from a Web site.
Also on Mactopia:
Comments (11)
If your email address is user@example.com you would get the following error.
"Unable to establish a secure connection to www.example.com because the server name or IP address does not match the name or IP address on the server's certificate. If you continue, the information you view and send will be encrypted, but will not be secure."
We think this is related to the autodiscover service. Users inside the organization see the error but those outside don't. We do have an autodiscover.example.com address setup but it Entourage doesn't seem to work with it. We don't have control over www.example.com to setup autodiscover there. Office 2008 without SP1 doesn't have the problem.
I'll pass this on. I know several users including myself that are experiencing the problem. Thanks!!
After updating to SP1, I was told my Entourage database had to be updated. After it was updated, all e-mail that existed on my Exchange server was pulled off the server even though it still shows up in my inbox.
The problem is all NEW e-mail appears as a Folder_With_Subject.EML folder under my exchange inbox - meaning I can't access the message.
Why is Entourage seeing new e-mail messages (and they do show up as messages through webmail) as inbox folders. :(
SP1 does upgrade the Identity. I warned about this advising users to backup their Identity prior to upgrading in cases of problems. I will see what I can find out about your problem and will contact you if I find anything that will help you.
How/when did you get this notice? “I was told my Entourage database had to be updated?”
How was it updated?
Can you explain “pulled off the server?”
Have you tried rebuilding with the Database Utility?
You may need to flush your cache.
Deleting and recreating the account in Entourage should fix the problem. If not please contact me off list with more info and include screenshots. Your previous email address was a fake.
After SP1 install, I get this error on startup without fail:
"Unable to Establish a secure connection to xxx.xxx.xxx because the server name or IP address does not match the name or IP address on the server's certificate."
We have a Unified communications certificate installed that has 4 domains in it. It doesn't seem to matter which domain I use in Entourage, it errors on all of them. I saw in another blog that a post would be made here when something was found but I'm not seeing anything. Any information anyone could provide would be great.
This is a known bug and there should be a fix shortly. You can continue to use the accounts. Just dismiss the error.
Any news on the new mails appearing as EML-mails after installing Entourage 2008, as described by Bryan? I'm seen exactly the same behavior. Only, it didn't happen immediately after installing SP1, but after having to rebuild my Entourage database a week or two later.
I've tried emptying the cache, but to no avail. The issue must be linked to Exchange-accounts, as I don't have the same problem on the mail received through POP-accounts.
Diane,
Along with this bug though, free/busy search and Delegation appears to have been broken, so merely clicking through the error doesn't really let you work. E-mail works fine, but Free/Busy never retrieves any information. It worked fine in 12.0.1.
Thanks,
John
Hi John!
Are you referring to the certificate message that refers to "domain.com" and not "server.domain.com"? If so, that's still an open issue.
To the best of my knowledge, this is affecting only Exchange Server 2007. Paul Robichaux, an Exchange Server MVP, believes this may be related to the new AutoDiscover feature of Exchange Server 2007 and that an improperly configured or incomplete AutoDiscover DNS setup may be the cause.
I have no idea how this might affect the public folders server.
Although it may be an error message we should be seeing I've found no way to dismiss it by completely trusting certificates. I've been in communication with one of my contacts at Microsoft and asked him to either confirm this is a bug or tell us what we need to do to permanently dismiss the notification. I've provided them details from one of my Exchange accounts that is experiencing this problem. They are still investigating.
I may go ahead and post about this separately just to help folks acknowledge this is an existing issue under investigation. More and more folks are reporting this problem with no fix.
Hi All,
I had this issue right after I installed my UC Cert for users with Entourage. I found a post about the WebDAV Exchange Folder needing to be setup however I don't like messing with default redirects in exchange 2007. The way I fixed this was to add the autodiscover.mydomain.com and point it to my internal ip address of my exchange server in DNS. Since we host our external DNS outside we will add an entry there as well pointing to our public NAT'd address to our email server for roaming users. Hope this helps. (Just in case you are wondering - we do have SP1 on Entourage as well)
Thanks - Robert