Basically, as soon as I created the public folder DB on the single Ex2007 SP1 mailbox server and replicated the hierarchy viewing the public folders from OWA while logged onto an Ex2007 mailbox worked. If I dismount the Ex2007 SP1 (hierarchy only) public folder database i can not see the public folders via OWA. So the question was what really fixed it? The fact that the public folder database is available on that mailbox server or the fact that it is an Ex2007 public folder database, meaning when i have 10 Ex2007 SP1 mailbox servers I only need to have one Ex2007 public folder db which maintains a copy of the hierarchy? (i confuse myself typing it, can't imagine it'll makes sense to anyone)
On Thu, Feb 21, 2008 at 5:41 AM, Miller Bonnie L. < [EMAIL PROTECTED]> wrote: > Alex—can you clarify what the question is in your first paragraph? We > have one E2k7, now SP1, all roles, and I migrated the PFs from E2k3 last > summer. I did notice that clients on the E2k7 server from Outlook were only > seeing the PFs that had replicated to the E2k7 server (as we waited and > waited for replication to complete), but I don't remember working with it > while only having PFs homed on E2k3. Because OWA doesn't use the same > connection mechanism as Outlook, I guess your error message makes sense to > me if you didn't have any PFs on E2k7. > > > > -Bonnie > > > > *From:* Alex Fontana [mailto:[EMAIL PROTECTED] > *Sent:* Wednesday, February 20, 2008 1:58 PM > *To:* MS-Exchange Admin Issues > *Subject:* Re: Accessing Ex2003 Public Folders using Ex2007 SP1 OWA > > > > Update... > > It appears that first bullet is not exactly true, CAS and HT on the same > box is not the culprit. I found the problem to be the lack of a Public > Folder Database....this is where I'm going to ask if anyone knows...on the > mailbox server where the Ex2007 mailbox is homed or on any Ex2007 mailbox > server? > > I currently only have a single Ex2007 SP1 mailbox server in both prod and > test so "where the mailbox is homed" and "any Ex2007 mailbox server" are one > in the same for me. Anyway, created a PF db on the Ex2007 SP1 mbx server, > mounted it, I have stopped getting the pop-up error. Now just waiting for > the Hierarchy to replicate... > > -alex > > On Tue, Feb 19, 2008 at 8:17 PM, Alex Fontana <[EMAIL PROTECTED]> > wrote: > > Hopefully someone's run into this... Log into an Ex2007 SP1 mailbox via > Ex2007 SP1 CAS (which also runs the HT role), click on the Public Folder > link and get the error: "Outlook Web Access is unable to open public > folders. If the problem continues contact technical support for your > organization." The public folders are located on an Ex2003 box which is the > default PF store for the Ex2007 Sp1 database where this mailbox is located. > > Found the following at: > http://technet.microsoft.com/en-us/library/bb430795(EXCHG.80).aspx<http://technet.microsoft.com/en-us/library/bb430795%28EXCHG.80%29.aspx> > > Exchange 2003 public folders will be available to Exchange 2007 mailboxes > only if the following conditions are true: > > - The server that is hosting the Client Access server role must not > be hosting any other Exchange 2007 server roles. > - The /public and /owa virtual directories must have the same SSL > setting. > - The /public virtual directory has not been renamed. > - SSL is disabled on the home public folder server that is assigned > to the user's mailbox. > > That first bullet of "...must not be hosting any other exchange 2007 > server roles." certainly sounds like the culprit, but I've only heard/read > of issues when the mbx and cas are on the same box. Can anyone confirm? > Everything else checks out. > > Thanks! > -alex > > > > > > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
