Answer This Question for a Date with Britney Spears - We know she puts out.
Since I got no response with my first title, I thought this might get everyone's attention.
Our Outlook 2003 users can invite attendees to meetings, however they are unable to access free/busy information for the attendees. When they attempt to do this, they get "No free/busy information could be retrieved." Outlook 2007 users have no problems.
There is an error in the server:
Source: MSExchangeFBPublish Category: General EventID: 8207 Type: Error
"Error updating public folder with free/busy information on virtual machine SERVER1. The error number is 0x80004005."
When I click on the MS link in the event, it basically tells me to check my Public Folder store to make sure it's mounted, which it is.
Any help with this would be greatly appreciated.
Thanks!
<-=+=->
BACKGROUND INFO:
Active Directory Information:
Three sites, single domain in single forest. All DCs are running Windows Server 2003 R2 Standard 32-bit. GCS in each site. DNS server in each site. Domain is raised to highest functional level.
Exchange Information:
Single-server environment. Exchange 2007 on Windows Server 2003 R2 Standard 64-bit. Dual Quad-Core Xeons, 8GB RAM. 1.5TB HDD space. Single Public Folder database. Single Mailbox database. Each in its own Storage Group. (Pretty much the default config).
Upgrade Procedure:
We had a single-server Exchange 2003 organization. Exchange 2007 was added on a new server, upgrading the organization. All mailboxes were moved to the 2007 server. All public folders (including the Schedule+ Free/Busy) were moved to the 2007 server. All AL, OAB, RUS and other roles were moved to 2007 server. 2003 was then uninstalled cleanly from the old server and the old server was joined to a workgroup, thus was removed from the domain cleanly. The old server was reinstalled and is now being used in a different role.
Our Outlook 2003 users can invite attendees to meetings, however they are unable to access free/busy information for the attendees. When they attempt to do this, they get "No free/busy information could be retrieved." Outlook 2007 users have no problems.
There is an error in the server:
Source: MSExchangeFBPublish Category: General EventID: 8207 Type: Error
"Error updating public folder with free/busy information on virtual machine SERVER1. The error number is 0x80004005."
When I click on the MS link in the event, it basically tells me to check my Public Folder store to make sure it's mounted, which it is.
Any help with this would be greatly appreciated.
Thanks!
<-=+=->
BACKGROUND INFO:
Active Directory Information:
Three sites, single domain in single forest. All DCs are running Windows Server 2003 R2 Standard 32-bit. GCS in each site. DNS server in each site. Domain is raised to highest functional level.
Exchange Information:
Single-server environment. Exchange 2007 on Windows Server 2003 R2 Standard 64-bit. Dual Quad-Core Xeons, 8GB RAM. 1.5TB HDD space. Single Public Folder database. Single Mailbox database. Each in its own Storage Group. (Pretty much the default config).
Upgrade Procedure:
We had a single-server Exchange 2003 organization. Exchange 2007 was added on a new server, upgrading the organization. All mailboxes were moved to the 2007 server. All public folders (including the Schedule+ Free/Busy) were moved to the 2007 server. All AL, OAB, RUS and other roles were moved to 2007 server. 2003 was then uninstalled cleanly from the old server and the old server was joined to a workgroup, thus was removed from the domain cleanly. The old server was reinstalled and is now being used in a different role.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Matthew Millers
How is this going?
ASKER
Actually, what we ended up doing was recreating the Schedule+ Free/Busy Replica via a different KB article. What is really strange is that I dd this the day before we posted the question to no effect. A different guy who was also involved with troubleshooting the problem did the exact same thing about a day later and it worked.
Weird.
We're also having fits with certificates. I gotta be honest, I've been working with (and am certified on) Exchange since 5.0; so far, I am not at all impressed with 2007.
<-=+=->
Weird.
We're also having fits with certificates. I gotta be honest, I've been working with (and am certified on) Exchange since 5.0; so far, I am not at all impressed with 2007.
<-=+=->
ASKER
We actually found a different solution, but thank you for your time!