That's my problem, there isn't anywhere else to look. The only thing in
common with those having no access through OWA is the use of outlook. Does
anyone know just how OWA accesses mailboxes? If I new the sequence of events
I might be able to track the process and find the problem that way.

-----Original Message-----
From: Chris Scharff [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 13, 2001 1:04 PM
To: Exchange Discussions
Subject: RE: exchange and OWA (repost)


Most likely nothing. The connection between rebuilding a shortcut bar in
Outlook and an inability to connect via OWA is spurious IMHO. Look elsewhere
for the cause.

Chris
-- 
Chris Scharff
Senior Sales Engineer
MessageOne
If you can't measure, you can't manage! 


> -----Original Message-----
> From: Steve Parks [mailto:[EMAIL PROTECTED]] 
> Sent: Thursday, December 13, 2001 11:08 AM
> To: Exchange Discussions
> Subject: exchange and OWA (repost)
> 
> 
> I rebuilt my information store the following way:
> use exmerge to export all mailboxes
> erase priv.edb
> restart (automatically recreates priv.edb)
> send a message to everyone (recreates the directory structure 
> in info store) use exmerge to import all mailboxes
> 
> Worked like a champ. The first time I connected to the new 
> mailbox with outlook it gave me a message about rebuilding 
> shortcuts and delivery rules, I said ok, and everything is 
> fine except now when I log in to OWA I get "failed to get 
> inbox". This has happened to everyone that uses outlook. My 
> remote users that only use OWA can still use OWA with no 
> problem. So my question is, what is outlook doing to these 
> mailboxes that breaks OWA?

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to