New users creating get page cannot be displayed when accessing OWA

  • Thread starter Rollinwest
  • Start date Views 3,747
Status
Not open for further replies.
R

Rollinwest

Hello all,

I have just noticed that any new user that i create cannot access owa.

I get a page cannot be displayed. I am not sure that the problem is.

I have checked the user properties and OWA access is enabled. I do not

see any events in the event viewer so i am confused.

Any help would be great!

Thanks,

Rollinwest!
 
L

Lee Derbyshire [MVP]

"Rollinwest" <RollinWest@gmail.com> wrote in message

news:7bda50d5-7383-4af5-9fd0-bcdb9683e02b@v38g2000yqb.googlegroups.com...
> Hello all,

> I have just noticed that any new user that i create cannot access owa.
> I get a page cannot be displayed. I am not sure that the problem is.

> I have checked the user properties and OWA access is enabled. I do not
> see any events in the event viewer so i am confused.

> Any help would be great!

> Thanks,
> Rollinwest!


Which version of Exchange? Make sure that they are getting an SMTP address

in the same domain as everyone else.

Lee.

 
K

Karl Mitschke

Hello Rollinwest,


> Hello all,

> I have just noticed that any new user that i create cannot access owa.
> I get a page cannot be displayed. I am not sure that the problem is.

> I have checked the user properties and OWA access is enabled. I do not
> see any events in the event viewer so i am confused.

> Any help would be great!

> Thanks,
> Rollinwest!


Are you running Exchange 2007?

If so, are you using the old ADUC integrated tools (or any Exchange 1000/2003

tools) to create the mailboxes?

If so, try this in the EMS:

Set-Mailbox -Identity <user> -ApplyMandatoryProperties

If you don't see the following, it means the mandatory properties were not

present. Try OWA again :)

"WARNING: The command completed successfully but no settings of 'user fqdn'

have been modified." would indicate that the AD object already had the mandatory

properties.

As an aside, and as far as I recall, these properties are:

msExchRecipientDisplayType: 1073741824

msExchRecipientTypeDetails: 1

msExchVersion: 4535486012416
 
R

Rollinwest

Re: New users creating get page cannot be displayed when accessingOWA

On Mar 24, 10:08 am, Karl Mitschke <karlmitsc...@somestate.gov> wrote:
> Hello Rollinwest,
>
> > Hello all,

>
> > I have just noticed that any newuserthat i createcannotaccessowa.
> > I get a pagecannotbe displayed. I am not sure that the problem is.

>
> > I have checked theuserproperties andOWAaccessis enabled. I do not
> > see any events in the event viewer so i am confused.

>
> > Any help would be great!

>
> > Thanks,
> > Rollinwest!


> Are you running Exchange 2007?

> If so, are you using the old ADUC integrated tools (or any Exchange 1000/2003
> tools) to create the mailboxes?

> If so, try this in the EMS:

> Set-Mailbox -Identity <user> -ApplyMandatoryProperties

> If you don't see the following, it means the mandatory properties were not
> present. TryOWAagain :)

> "WARNING: The command completed successfully but no settings of 'userfqdn'
> have been modified." would indicate that the AD object already had the mandatory
> properties.

> As an aside, and as far as I recall, these properties are:
> msExchRecipientDisplayType: 1073741824
> msExchRecipientTypeDetails:1
> msExchVersion: 4535486012416


Hello there,

i am running exchange 2003. so with that said should i try the other

items in your email? Thanks!
 
K

Karl Mitschke

Hello Rollinwest,


> On Mar 24, 10:08 am, Karl Mitschke <karlmitsc...@somestate.gov> wrote:
>
> > Hello Rollinwest,
> >
> >> Hello all,
> >
>>> I have just noticed that any newuserthat i createcannotaccessowa. I
> >> get a pagecannotbe displayed. I am not sure that the problem is.
> >
>>> I have checked theuserproperties andOWAaccessis enabled. I do not
> >> see any events in the event viewer so i am confused.
> >
>>> Any help would be great!
> >
>>> Thanks,
> >> Rollinwest!

> > Are you running Exchange 2007?
>

>> If so, are you using the old ADUC integrated tools (or any Exchange
> > 1000/2003 tools) to create the mailboxes?
>

>> If so, try this in the EMS:
>

>> Set-Mailbox -Identity <user> -ApplyMandatoryProperties
>

>> If you don't see the following, it means the mandatory properties
> > were not present. TryOWAagain :)
>

>> "WARNING: The command completed successfully but no settings of
> > 'userfqdn'
> > have been modified." would indicate that the AD object already had
> > the mandatory
> > properties.
> > As an aside, and as far as I recall, these properties are:
> > msExchRecipientDisplayType: 1073741824
> > msExchRecipientTypeDetails:1
> > msExchVersion: 4535486012416

> Hello there,

> i am running exchange 2003. so with that said should i try the other
> items in your email? Thanks!


Nope, the items in my email are specific to Exchange 2007 - Unless you have

prepared your schema for 2007 those AD attributes shouldn't even exist.

Now that we have the Exchange version;

Can these users access OWA internally?

Have a user try to connect to the server via the IP address instead of the

URL - does that work?

The "page cannot be displayed." page should have SOME information on it?

Karl
 
R

Rollinwest

Re: New users creating get page cannot be displayed when accessingOWA

On Mar 24, 12:35 pm, Karl Mitschke <karlmitsc...@somestate.gov> wrote:
> Hello Rollinwest,

>
> > On Mar 24, 10:08 am, Karl Mitschke <karlmitsc...@somestate.gov> wrote:

>
> >> Hello Rollinwest,

>
> >>> Hello all,

>
> >>> I have just noticed that any newuserthat i createcannotaccessowa. I
> >>> get a pagecannotbe displayed. I am not sure that the problem is.

>
> >>> I have checked theuserproperties andOWAaccessis enabled. I do not
> >>> see any events in the event viewer so i am confused.

>
> >>> Any help would be great!

>
> >>> Thanks,
> >>> Rollinwest!
> >> Are you running Exchange 2007?

>
> >> If so, are you using the old ADUC integrated tools (or any Exchange
> >> 1000/2003 tools) to create the mailboxes?

>
> >> If so, try this in the EMS:

>
> >> Set-Mailbox -Identity <user> -ApplyMandatoryProperties

>
> >> If you don't see the following, it means the mandatory properties
> >> were not present. TryOWAagain :)

>
> >> "WARNING: The command completed successfully but no settings of
> >> 'userfqdn'
> >> have been modified." would indicate that the AD object already had
> >> the mandatory
> >> properties.
> >> As an aside, and as far as I recall, these properties are:
> >> msExchRecipientDisplayType: 1073741824
> >> msExchRecipientTypeDetails:1
> >> msExchVersion: 4535486012416

> > Hello there,

>
> > i am running exchange 2003. so with that said should i try the other
> > items in your email? Thanks!


> Nope, the items in my email are specific to Exchange 2007 - Unless you have
> prepared your schema for 2007 those AD attributes shouldn't even exist.

> Now that we have the Exchange version;

> Can these usersaccessOWAinternally?

> Have ausertry to connect to the server via the IP address instead of the
> URL - does that work?

> The "pagecannotbe displayed." page should have SOME information on it?

> Karl-



Hi karl,

Thanks for your help to answer your questions

OWA is only used internally or through a VPN session.

Sorry the page error states the page cannot be found. Here is what's

listed below.

The page cannot be found

The page you are looking for might have been removed, had its name

changed, or is temporarily unavailable.

------------------------------------------------Please try the following:

Make sure that the Web site address displayed in the address bar of

your browser is spelled and formatted correctly.

If you reached this page by clicking a link, contact the Web site

administrator to alert them that the link is incorrectly formatted.

Click the Back button to try another link.

HTTP Error 404 - File or directory not found.

Internet Information Services (IIS)

------------------------------------------------Technical Information (for support personnel)

Go to Microsoft Product Support Services and perform a title search

for the words HTTP and 404.

Open IIS Help, which is accessible in IIS Manager (inetmgr), and

search for topics titled Web Site Setup, Common Administrative Tasks,

and About Custom Error Messages.
 
R

Rollinwest

Re: New users creating get page cannot be displayed when accessingOWA

On Mar 24, 1:19 pm, Rollinwest <RollinW...@gmail.com> wrote:
> On Mar 24, 12:35 pm, Karl Mitschke <karlmitsc...@somestate.gov> wrote:

>
> > Hello Rollinwest,

>
> > > On Mar 24, 10:08 am, Karl Mitschke <karlmitsc...@somestate.gov> wrote:

>
> > >> Hello Rollinwest,

>
> > >>> Hello all,

>
> > >>> I have just noticed that any newuserthat i createcannotaccessowa. I
> > >>> get a pagecannotbe displayed. I am not sure that the problem is.

>
> > >>> I have checked theuserproperties andOWAaccessis enabled. I do not
> > >>> see any events in the event viewer so i am confused.

>
> > >>> Any help would be great!

>
> > >>> Thanks,
> > >>> Rollinwest!
> > >> Are you running Exchange 2007?

>
> > >> If so, are you using the old ADUC integrated tools (or any Exchange
> > >> 1000/2003 tools) to create the mailboxes?

>
> > >> If so, try this in the EMS:

>
> > >> Set-Mailbox -Identity <user> -ApplyMandatoryProperties

>
> > >> If you don't see the following, it means the mandatory properties
> > >> were not present. TryOWAagain :)

>
> > >> "WARNING: The command completed successfully but no settings of
> > >> 'userfqdn'
> > >> have been modified." would indicate that the AD object already had
> > >> the mandatory
> > >> properties.
> > >> As an aside, and as far as I recall, these properties are:
> > >> msExchRecipientDisplayType: 1073741824
> > >> msExchRecipientTypeDetails:1
> > >> msExchVersion: 4535486012416
> > > Hello there,

>
> > > i am running exchange 2003. so with that said should i try the other
> > > items in your email? Thanks!

>
> > Nope, the items in my email are specific to Exchange 2007 - Unless you have
> > prepared your schema for 2007 those AD attributes shouldn't even exist.

>
> > Now that we have the Exchange version;

>
> > Can these usersaccessOWAinternally?

>
> > Have ausertry to connect to the server via the IP address instead of the
> > URL - does that work?

>
> > The "pagecannotbe displayed." page should have SOME information on it?

>
> > Karl-

>
>


> Hi karl,

> Thanks for your help to answer your questions

> OWAis only used internally or through a VPN session.

> Sorry the page error states the pagecannotbe found. Here is what's
> listed below.

> The pagecannotbe found
> The page you are looking for might have been removed, had its name
> changed, or is temporarily unavailable.
> ---------------------------------------------------------------------------­---
> Please try the following:

> Make sure that the Web site address displayed in the address bar of
> your browser is spelled and formatted correctly.
> If you reached this page by clicking a link, contact the Web site
> administrator to alert them that the link is incorrectly formatted.
> Click the Back button to try another link.
> HTTP Error 404 - File or directory not found.
> Internet Information Services (IIS)

> ---------------------------------------------------------------------------­---
> Technical Information (for support personnel)

> Go to Microsoft Product Support Services and perform a title search
> for the words HTTP and 404.
> Open IIS Help, which is accessible in IIS Manager (inetmgr), and
> search for topics titled Web Site Setup, Common Administrative Tasks,
> and About Custom Error Messages.-



Thank you for your help. i believe i have found the problem. However

hopefully you can explain how to completly resolve. The issue has to

do changing our email format. we had a recepient policy that you give

the user firstinitialastname@xxx.com and firstname.lastname@xx.com

We have set the policy to make firstname.lastname primary and removed

firstinitialastname.

So when I manually created the firstinitiallastname email address for

the user it's working. how can that be corrected. I hope it makes

sense.

thanks!
 
K

Karl Mitschke

Hello Rollinwest,


> On Mar 24, 1:19 pm, Rollinwest <RollinW...@gmail.com> wrote:
>
> > On Mar 24, 12:35 pm, Karl Mitschke <karlmitsc...@somestate.gov
>> wrote:
> >
> >> Hello Rollinwest,
> >
>>>> On Mar 24, 10:08 am, Karl Mitschke <karlmitsc...@somestate.gov
>>>> wrote:
> >>
>>>>> Hello Rollinwest,
> >>>
>>>>>> Hello all,
> >>>>
>>>>>> I have just noticed that any newuserthat i createcannotaccessowa.
> >>>>> I get a pagecannotbe displayed. I am not sure that the problem
> >>>>> is.
> >>>>
>>>>>> I have checked theuserproperties andOWAaccessis enabled. I do not
> >>>>> see any events in the event viewer so i am confused.
> >>>>
>>>>>> Any help would be great!
> >>>>
>>>>>> Thanks,
> >>>>> Rollinwest!
> >>>> Are you running Exchange 2007?
> >>>
>>>>> If so, are you using the old ADUC integrated tools (or any
> >>>> Exchange 1000/2003 tools) to create the mailboxes?
> >>>
>>>>> If so, try this in the EMS:
> >>>
>>>>> Set-Mailbox -Identity <user> -ApplyMandatoryProperties
> >>>
>>>>> If you don't see the following, it means the mandatory properties
> >>>> were not present. TryOWAagain :)
> >>>
>>>>> "WARNING: The command completed successfully but no settings of
> >>>> 'userfqdn'
> >>>> have been modified." would indicate that the AD object already had
> >>>> the mandatory
> >>>> properties.
> >>>> As an aside, and as far as I recall, these properties are:
> >>>> msExchRecipientDisplayType: 1073741824
> >>>> msExchRecipientTypeDetails:1
> >>>> msExchVersion: 4535486012416
> >>> Hello there,
> >>
>>>> i am running exchange 2003. so with that said should i try the
> >>> other items in your email? Thanks!
> >>
>>> Nope, the items in my email are specific to Exchange 2007 - Unless
> >> you have prepared your schema for 2007 those AD attributes shouldn't
> >> even exist.
> >
>>> Now that we have the Exchange version;
> >
>>> Can these usersaccessOWAinternally?
> >
>>> Have ausertry to connect to the server via the IP address instead of
> >> the URL - does that work?
> >
>>> The "pagecannotbe displayed." page should have SOME information on
> >> it?
> >
>>> Karl-

> >
>>
> >>

> > Hi karl,
>

>> Thanks for your help to answer your questions
>

>> OWAis only used internally or through a VPN session.
>

>> Sorry the page error states the pagecannotbe found. Here is what's
> > listed below.
>

>> The pagecannotbe found
> > The page you are looking for might have been removed, had its name
> > changed, or is temporarily unavailable.
> > -------------------------------------------------------------------> > ------­---> > Please try the following:
>

>> Make sure that the Web site address displayed in the address bar of
> > your browser is spelled and formatted correctly.
> > If you reached this page by clicking a link, contact the Web site
> > administrator to alert them that the link is incorrectly formatted.
> > Click the Back button to try another link.
> > HTTP Error 404 - File or directory not found.
> > Internet Information Services (IIS)
> > -------------------------------------------------------------------> > ------­--->

>> Technical Information (for support personnel)
>

>> Go to Microsoft Product Support Services and perform a title search
> > for the words HTTP and 404.
> > Open IIS Help, which is accessible in IIS Manager (inetmgr), and
> > search for topics titled Web Site Setup, Common Administrative Tasks,
> > and About Custom Error Messages.-

>

> >

> Thank you for your help. i believe i have found the problem. However
> hopefully you can explain how to completly resolve. The issue has to
> do changing our email format. we had a recepient policy that you give
> the user firstinitialastname@xxx.com and firstname.lastname@xx.com

> We have set the policy to make firstname.lastname primary and removed
> firstinitialastname.

> So when I manually created the firstinitiallastname email address for
> the user it's working. how can that be corrected. I hope it makes
> sense.

> thanks!


Do you have OWA setup to use domain\username for the login?
 
R

Rollinwest

Re: New users creating get page cannot be displayed when accessingOWA

On Mar 24, 2:32 pm, Karl Mitschke <karlmitsc...@somestate.gov> wrote:
> Hello Rollinwest,

>
> > On Mar 24,1:19 pm, Rollinwest <RollinW...@gmail.com> wrote:

>
> >> On Mar 24, 12:35 pm, Karl Mitschke <karlmitsc...@somestate.gov
> >> wrote:

>
> >>> Hello Rollinwest,

>
> >>>> On Mar 24, 10:08 am, Karl Mitschke <karlmitsc...@somestate.gov
> >>>> wrote:

>
> >>>>> Hello Rollinwest,

>
> >>>>>> Hello all,

>
> >>>>>> I have just noticed that any newuserthat i createcannotaccessowa.
> >>>>>> I get a pagecannotbe displayed. I am not sure that the problem
> >>>>>> is.

>
> >>>>>> I have checked theuserproperties andOWAaccessis enabled. I do not
> >>>>>> see any events in the event viewer so i am confused.

>
> >>>>>> Any help would be great!

>
> >>>>>> Thanks,
> >>>>>> Rollinwest!
> >>>>> Are you running Exchange 2007?

>
> >>>>> If so, are you using the old ADUC integrated tools (or any
> >>>>> Exchange 1000/2003 tools) to create the mailboxes?

>
> >>>>> If so, try this in the EMS:

>
> >>>>> Set-Mailbox -Identity <user> -ApplyMandatoryProperties

>
> >>>>> If you don't see the following, it means the mandatory properties
> >>>>> were not present. TryOWAagain :)

>
> >>>>> "WARNING: The command completed successfully but no settings of
> >>>>> 'userfqdn'
> >>>>> have been modified." would indicate that the AD object already had
> >>>>> the mandatory
> >>>>> properties.
> >>>>> As an aside, and as far as I recall, these properties are:
> >>>>> msExchRecipientDisplayType: 1073741824
> >>>>> msExchRecipientTypeDetails:1
> >>>>> msExchVersion: 4535486012416
> >>>> Hello there,

>
> >>>> i am running exchange 2003. so with that said should i try the
> >>>> other items in your email? Thanks!

>
> >>> Nope, the items in my email are specific to Exchange 2007 - Unless
> >>> you have prepared your schema for 2007 those AD attributes shouldn't
> >>> even exist.

>
> >>> Now that we have the Exchange version;

>
> >>> Can these usersaccessOWAinternally?

>
> >>> Have ausertry to connect to the server via the IP address instead of
> >>> the URL - does that work?

>
> >>> The "pagecannotbe displayed." page should have SOME information on
> >>> it?

>
> >>> Karl-

>
> >>

>
> >> Hi karl,

>
> >> Thanks for your help to answer your questions

>
> >> OWAis only used internally or through a VPN session.

>
> >> Sorry the page error states the pagecannotbe found. Here is what's
> >> listed below.

>
> >> The pagecannotbe found
> >> The page you are looking for might have been removed, had its name
> >> changed, or is temporarily unavailable.
> >> -------------------------------------------------------------------> >> ------­---> >> Please try the following:

>
> >> Make sure that the Web site address displayed in the address bar of
> >> your browser is spelled and formatted correctly.
> >> If you reached this page by clicking a link, contact the Web site
> >> administrator to alert them that the link is incorrectly formatted.
> >> Click the Back button to try another link.
> >> HTTP Error 404 - File or directory not found.
> >> Internet Information Services (IIS)
> >> -------------------------------------------------------------------> >> ------­-----

>
> >> Technical Information (for support personnel)

>
> >> Go to Microsoft Product Support Services and perform a title search
> >> for the words HTTP and 404.
> >> Open IIS Help, which is accessible in IIS Manager (inetmgr), and
> >> search for topics titled Web Site Setup, Common Administrative Tasks,
> >> and About Custom Error Messages.-

> >

>
> > Thank you for your help. i believe i have found the problem. However
> > hopefully you can explain how to completly resolve. The issue has to
> > do changing our email format. we had a recepient policy that you give
> > theuserfirstinitialastn...@xxx.com and firstname.lastn...@xx.com

>
> > We have set the policy to make firstname.lastname primary and removed
> > firstinitialastname.

>
> > So when I manually created the firstinitiallastname email address for
> > theuserit's working. how can that be corrected. I hope it makes
> > sense.

>
> > thanks!


> Do you haveOWAsetup to use domain\username for the login?-



Yes which i really dont like i wanted to use form bases authentication

but i am having a lot of problems with that. Do you know how i can

resolve?
 
K

Karl Mitschke

Hello Rollinwest,


> On Mar 24, 2:32 pm, Karl Mitschke <karlmitsc...@somestate.gov> wrote:
>
> > Hello Rollinwest,
> >
> >> On Mar 24,1:19 pm, Rollinwest <RollinW...@gmail.com> wrote:
> >
>>>> On Mar 24, 12:35 pm, Karl Mitschke <karlmitsc...@somestate.gov
>>>> wrote:
> >>
>>>>> Hello Rollinwest,
> >>>
>>>>>> On Mar 24, 10:08 am, Karl Mitschke <karlmitsc...@somestate.gov
>>>>>> wrote:
> >>>>
>>>>>>> Hello Rollinwest,
> >>>>>
>>>>>>>> Hello all,
> >>>>>>
>>>>>>>> I have just noticed that any newuserthat i
> >>>>>>> createcannotaccessowa. I get a pagecannotbe displayed. I am not
> >>>>>>> sure that the problem is.
> >>>>>>
>>>>>>>> I have checked theuserproperties andOWAaccessis enabled. I do
> >>>>>>> not see any events in the event viewer so i am confused.
> >>>>>>
>>>>>>>> Any help would be great!
> >>>>>>
>>>>>>>> Thanks,
> >>>>>>> Rollinwest!
> >>>>>> Are you running Exchange 2007?
> >>>>>
>>>>>>> If so, are you using the old ADUC integrated tools (or any
> >>>>>> Exchange 1000/2003 tools) to create the mailboxes?
> >>>>>
>>>>>>> If so, try this in the EMS:
> >>>>>
>>>>>>> Set-Mailbox -Identity <user> -ApplyMandatoryProperties
> >>>>>
>>>>>>> If you don't see the following, it means the mandatory
> >>>>>> properties were not present. TryOWAagain :)
> >>>>>
>>>>>>> "WARNING: The command completed successfully but no settings of
> >>>>>> 'userfqdn'
> >>>>>> have been modified." would indicate that the AD object already
> >>>>>> had
> >>>>>> the mandatory
> >>>>>> properties.
> >>>>>> As an aside, and as far as I recall, these properties are:
> >>>>>> msExchRecipientDisplayType: 1073741824
> >>>>>> msExchRecipientTypeDetails:1
> >>>>>> msExchVersion: 4535486012416
> >>>>> Hello there,
> >>>>
>>>>>> i am running exchange 2003. so with that said should i try the
> >>>>> other items in your email? Thanks!
> >>>>
>>>>> Nope, the items in my email are specific to Exchange 2007 - Unless
> >>>> you have prepared your schema for 2007 those AD attributes
> >>>> shouldn't even exist.
> >>>
>>>>> Now that we have the Exchange version;
> >>>
>>>>> Can these usersaccessOWAinternally?
> >>>
>>>>> Have ausertry to connect to the server via the IP address instead
> >>>> of the URL - does that work?
> >>>
>>>>> The "pagecannotbe displayed." page should have SOME information on
> >>>> it?
> >>>
>>>>> Karl-

> >>>
>>>>
> >>>
>>>> Hi karl,
> >>
>>>> Thanks for your help to answer your questions
> >>
>>>> OWAis only used internally or through a VPN session.
> >>
>>>> Sorry the page error states the pagecannotbe found. Here is what's
> >>> listed below.
> >>
>>>> The pagecannotbe found
> >>> The page you are looking for might have been removed, had its name
> >>> changed, or is temporarily unavailable.
> >>> -----------------------------------------------------------------> >>> > >>> ------­---> >>> Please try the following:
> >>> Make sure that the Web site address displayed in the address bar of
> >>> your browser is spelled and formatted correctly.
> >>> If you reached this page by clicking a link, contact the Web site
> >>> administrator to alert them that the link is incorrectly formatted.
> >>> Click the Back button to try another link.
> >>> HTTP Error 404 - File or directory not found.
> >>> Internet Information Services (IIS)
> >>> -----------------------------------------------------------------> >>> > >>> ------­---> >>> Technical Information (for support personnel)
> >>
>>>> Go to Microsoft Product Support Services and perform a title search
> >>> for the words HTTP and 404.
> >>> Open IIS Help, which is accessible in IIS Manager (inetmgr), and
> >>> search for topics titled Web Site Setup, Common Administrative
> >>> Tasks,
> >>> and About Custom Error Messages.-

> >>
> >> Thank you for your help. i believe i have found the problem. However
> >> hopefully you can explain how to completly resolve. The issue has to
> >> do changing our email format. we had a recepient policy that you
> >> give theuserfirstinitialastn...@xxx.com and
> >> firstname.lastn...@xx.com
> >
>>> We have set the policy to make firstname.lastname primary and
> >> removed firstinitialastname.
> >
>>> So when I manually created the firstinitiallastname email address
> >> for theuserit's working. how can that be corrected. I hope it makes
> >> sense.
> >
>>> thanks!
> >>

> > Do you haveOWAsetup to use domain\username for the login?- Hide
> > quoted text -
>

>
> >

> Yes which i really dont like i wanted to use form bases authentication
> but i am having a lot of problems with that. Do you know how i can
> resolve?


Like I mentioned before, I don't have any brain cells dedicated to Exchange

2000/2003 anymore ;)

So, everything I come up with is a SWAG.

Have you read through this?

http://www.msexchange.org/tutorials/OWA_Exchange_Server_2003.html

Karl
 
L

Lee Derbyshire [MVP]

"Rollinwest" <RollinWest@gmail.com> wrote in message

news:b3eeb12c-ff68-454e-8b8c-9edc75fb3467@o11g2000yql.googlegroups.com...

On Mar 24, 10:08 am, Karl Mitschke <karlmitsc...@somestate.gov> wrote:
> Hello Rollinwest,
>
> > Hello all,

>
> > I have just noticed that any newuserthat i createcannotaccessowa.
> > I get a pagecannotbe displayed. I am not sure that the problem is.

>
> > I have checked theuserproperties andOWAaccessis enabled. I do not
> > see any events in the event viewer so i am confused.

>
> > Any help would be great!

>
> > Thanks,
> > Rollinwest!


> Are you running Exchange 2007?

> If so, are you using the old ADUC integrated tools (or any Exchange
> 1000/2003
> tools) to create the mailboxes?

> If so, try this in the EMS:

> Set-Mailbox -Identity <user> -ApplyMandatoryProperties

> If you don't see the following, it means the mandatory properties were not
> present. TryOWAagain :)

> "WARNING: The command completed successfully but no settings of 'userfqdn'
> have been modified." would indicate that the AD object already had the
> mandatory
> properties.

> As an aside, and as far as I recall, these properties are:
> msExchRecipientDisplayType: 1073741824
> msExchRecipientTypeDetails:1
> msExchVersion: 4535486012416


Hello there,

i am running exchange 2003. so with that said should i try the other

items in your email? Thanks!

--------
Check that the problem users have an email address in the same SMTP domain

as the other users that don't see the problem. The Default OWA directory

can only server users that have email addresses in the primary SMTP domain

that is defined in your Default Recipient Policy. Your new users may not

authomatically be getting the same domain's SMTP addresses assigned to them.

Lee.

 
K

Karl Mitschke

Hello Lee Derbyshire [MVP]" email leederbyshire d.0.t c.0.m,


> "Rollinwest" <RollinWest@gmail.com> wrote in message
> news:b3eeb12c-ff68-454e-8b8c-9edc75fb3467@o11g2000yql.googlegroups.com
> ... On Mar 24, 10:08 am, Karl Mitschke <karlmitsc...@somestate.gov
> wrote:
>
> > Hello Rollinwest,
> >
> >> Hello all,
> >
>>> I have just noticed that any newuserthat i createcannotaccessowa. I
> >> get a pagecannotbe displayed. I am not sure that the problem is.
> >
>>> I have checked theuserproperties andOWAaccessis enabled. I do not
> >> see any events in the event viewer so i am confused.
> >
>>> Any help would be great!
> >
>>> Thanks,
> >> Rollinwest!

> > Are you running Exchange 2007?
>

>> If so, are you using the old ADUC integrated tools (or any Exchange
> > 1000/2003
> > tools) to create the mailboxes?
> > If so, try this in the EMS:
>

>> Set-Mailbox -Identity <user> -ApplyMandatoryProperties
>

>> If you don't see the following, it means the mandatory properties
> > were not present. TryOWAagain :)
>

>> "WARNING: The command completed successfully but no settings of
> > 'userfqdn'
> > have been modified." would indicate that the AD object already had
> > the
> > mandatory
> > properties.
> > As an aside, and as far as I recall, these properties are:
> > msExchRecipientDisplayType: 1073741824
> > msExchRecipientTypeDetails:1
> > msExchVersion: 4535486012416

> Hello there,

> i am running exchange 2003. so with that said should i try the other
> items in your email? Thanks!

> --------
> Check that the problem users have an email address in the same SMTP
> domain as the other users that don't see the problem. The Default OWA
> directory can only server users that have email addresses in the
> primary SMTP domain that is defined in your Default Recipient Policy.
> Your new users may not authomatically be getting the same domain's
> SMTP addresses assigned to them.

> Lee.

>

> >

>


There's a reason you're the MVP :)

He specifically said " i believe i have found the problem. However hopefully

you can explain how to completly resolve. The issue has to do changing our

email format. we had a recepient policy that you give theuserfirstinitialastn...@xxx.com

and firstname.lastn...@xx.com"

I didn't count the x's in the domain name, as I assumed he just hit the x

once too many times - BUT, it could be that his new recipient policy has

a different domain!

Karl
 
L

Lee Derbyshire [MVP]

"Karl Mitschke" <karlmitschke@somestate.gov> wrote in message

news:d66cd4c2778f8cb7b36afd997ee@msnews.microsoft.com...
> Hello Lee Derbyshire [MVP]" email leederbyshire d.0.t c.0.m,
>
> > "Rollinwest" <RollinWest@gmail.com> wrote in message
> > news:b3eeb12c-ff68-454e-8b8c-9edc75fb3467@o11g2000yql.googlegroups.com
> > ... On Mar 24, 10:08 am, Karl Mitschke <karlmitsc...@somestate.gov
>> wrote:
> >
> >> Hello Rollinwest,
> >
>>>> Hello all,
> >>
>>>> I have just noticed that any newuserthat i createcannotaccessowa. I
> >>> get a pagecannotbe displayed. I am not sure that the problem is.
> >>
>>>> I have checked theuserproperties andOWAaccessis enabled. I do not
> >>> see any events in the event viewer so i am confused.
> >>
>>>> Any help would be great!
> >>
>>>> Thanks,
> >>> Rollinwest!
> >> Are you running Exchange 2007?
> >
>>> If so, are you using the old ADUC integrated tools (or any Exchange
> >> 1000/2003
> >> tools) to create the mailboxes?
> >> If so, try this in the EMS:
> >
>>> Set-Mailbox -Identity <user> -ApplyMandatoryProperties
> >
>>> If you don't see the following, it means the mandatory properties
> >> were not present. TryOWAagain :)
> >
>>> "WARNING: The command completed successfully but no settings of
> >> 'userfqdn'
> >> have been modified." would indicate that the AD object already had
> >> the
> >> mandatory
> >> properties.
> >> As an aside, and as far as I recall, these properties are:
> >> msExchRecipientDisplayType: 1073741824
> >> msExchRecipientTypeDetails:1
> >> msExchVersion: 4535486012416

> > Hello there,
>

>> i am running exchange 2003. so with that said should i try the other
> > items in your email? Thanks!
>

>> -------->

>> Check that the problem users have an email address in the same SMTP
> > domain as the other users that don't see the problem. The Default OWA
> > directory can only server users that have email addresses in the
> > primary SMTP domain that is defined in your Default Recipient Policy.
> > Your new users may not authomatically be getting the same domain's
> > SMTP addresses assigned to them.
>

>> Lee.
>

>>

> > > >

> >


> There's a reason you're the MVP :)

> He specifically said " i believe i have found the problem. However
> hopefully you can explain how to completly resolve. The issue has to do
> changing our email format. we had a recepient policy that you give
> theuserfirstinitialastn...@xxx.com and firstname.lastn...@xx.com"

> I didn't count the x's in the domain name, as I assumed he just hit the x
> once too many times - BUT, it could be that his new recipient policy has a
> different domain!

> Karl


You will need to check which is the Primary domain in the Default Recipient

Policy, then make sure that each user has an email address in that domain.

It doesn't have to be their Default SMTP Address, but it does have to be in

the list of their addresses if they want to use OWA 2003. Or, you can

create a new Exchange VDir in ESM, and make the 'Exchange Path' property

equal to the other domain; but I think that's a more confusing solution for

your users, since the new users must now use a different URL.

Lee.
 
R

Rollinwest

Re: New users creating get page cannot be displayed when accessingOWA

On Mar 25, 7:55 am, "Lee Derbyshire [MVP]" <email a@t leederbyshire d.

0.t c.0.m> wrote:
> "Karl Mitschke" <karlmitsc...@somestate.gov> wrote in message

> news:d66cd4c2778f8cb7b36afd997ee@msnews.microsoft.com...

>
> > Hello Lee Derbyshire [MVP]" email leederbyshire d.0.t c.0.m,

>
> >> "Rollinwest" <RollinW...@gmail.com> wrote in message
> >>news:b3eeb12c-ff68-454e-8b8c-9edc75fb3467@o11g2000yql.googlegroups.com
> >> ... On Mar 24, 10:08 am, Karl Mitschke <karlmitsc...@somestate.gov
> >> wrote:

>
> >>> Hello Rollinwest,

>
> >>>> Hello all,

>
> >>>> I have just noticed that any newuserthat i createcannotaccessowa. I
> >>>> get a pagecannotbe displayed. I am not sure that the problem is.

>
> >>>> I have checked theuserproperties andOWAaccessis enabled. I do not
> >>>> see any events in the event viewer so i am confused.

>
> >>>> Any help would be great!

>
> >>>> Thanks,
> >>>> Rollinwest!
> >>> Are you running Exchange 2007?

>
> >>> If so, are you using the old ADUC integrated tools (or any Exchange
> >>> 1000/2003
> >>> tools) to create the mailboxes?
> >>> If so, try this in the EMS:

>
> >>> Set-Mailbox -Identity <user> -ApplyMandatoryProperties

>
> >>> If you don't see the following, it means the mandatory properties
> >>> were not present. TryOWAagain :)

>
> >>> "WARNING: The command completed successfully but no settings of
> >>> 'userfqdn'
> >>> have been modified." would indicate that the AD object already had
> >>> the
> >>> mandatory
> >>> properties.
> >>> As an aside, and as far as I recall, these properties are:
> >>> msExchRecipientDisplayType: 1073741824
> >>> msExchRecipientTypeDetails:1
> >>> msExchVersion: 4535486012416
> >> Hello there,

>
> >> i am running exchange 2003. so with that said should i try the other
> >> items in your email? Thanks!

>
> >> ----------

>
> >> Check that the problem users have an email address in the same SMTP
> >> domain as the other users that don't see the problem.  The Default OWA
> >> directory can only server users that have email addresses in the
> >> primary SMTP domain that is defined in your Default Recipient Policy.
> >> Your new users may not authomatically be getting the same domain's
> >> SMTP addresses assigned to them.

>
> >> Lee.

>
> >>

> >>> >>

> >>

>
> > There's a reason you're the MVP :)

>
> > He specifically said " i believe i have found the problem. However
> > hopefully you can explain how to completly resolve. The issue has to do
> > changing our email format. we had a recepient policy that you give
> > theuserfirstinitialastn...@xxx.com and firstname.lastn...@xx.com"

>
> > I didn't count the x's in the domain name, as I assumed he just hit thex
> > once too many times - BUT, it could be that his new recipient policy has a
> > different domain!

>
> > Karl


> You will need to check which is the Primary domain in the Default Recipient
> Policy, then make sure that each user has an email address in that domain..
> It doesn't have to be their Default SMTP Address, but it does have to be in
> the list of their addresses if they want to use OWA 2003.  Or, you can
> create a new Exchange VDir in ESM, and make the 'Exchange Path' property
> equal to the other domain; but I think that's a more confusing solution for
> your users, since the new users must now use a different URL.

> Lee.-



Thanks Lee,

however management wants to delete all old email addresses so i

believe i will need to find a solution to correct this.
 
K

Karl Mitschke

Hello Rollinwest,


> On Mar 25, 7:55 am, "Lee Derbyshire [MVP]" <email a@t leederbyshire d.
> 0.t c.0.m> wrote:
>
> > "Karl Mitschke" <karlmitsc...@somestate.gov> wrote in message
>

>> news:d66cd4c2778f8cb7b36afd997ee@msnews.microsoft.com...
> >
> >> Hello Lee Derbyshire [MVP]" email leederbyshire d.0.t c.0.m,
> >
>>>> "Rollinwest" <RollinW...@gmail.com> wrote in message
> >>> news:b3eeb12c-ff68-454e-8b8c-9edc75fb3467@o11g2000yql.googlegroups.
> >>> com ... On Mar 24, 10:08 am, Karl Mitschke
> >>> <karlmitsc...@somestate.gov> wrote:
> >>
>>>>> Hello Rollinwest,
> >>>
>>>>>> Hello all,
> >>>>
>>>>>> I have just noticed that any newuserthat i createcannotaccessowa.
> >>>>> I get a pagecannotbe displayed. I am not sure that the problem
> >>>>> is.
> >>>>
>>>>>> I have checked theuserproperties andOWAaccessis enabled. I do not
> >>>>> see any events in the event viewer so i am confused.
> >>>>
>>>>>> Any help would be great!
> >>>>
>>>>>> Thanks,
> >>>>> Rollinwest!
> >>>> Are you running Exchange 2007?
> >>>
>>>>> If so, are you using the old ADUC integrated tools (or any
> >>>> Exchange
> >>>> 1000/2003
> >>>> tools) to create the mailboxes?
> >>>> If so, try this in the EMS:
> >>>> Set-Mailbox -Identity <user> -ApplyMandatoryProperties
> >>>
>>>>> If you don't see the following, it means the mandatory properties
> >>>> were not present. TryOWAagain :)
> >>>
>>>>> "WARNING: The command completed successfully but no settings of
> >>>> 'userfqdn'
> >>>> have been modified." would indicate that the AD object already had
> >>>> the
> >>>> mandatory
> >>>> properties.
> >>>> As an aside, and as far as I recall, these properties are:
> >>>> msExchRecipientDisplayType: 1073741824
> >>>> msExchRecipientTypeDetails:1
> >>>> msExchVersion: 4535486012416
> >>> Hello there,
> >>
>>>> i am running exchange 2003. so with that said should i try the
> >>> other items in your email? Thanks!
> >>
>>>> --------> >>
>>>> Check that the problem users have an email address in the same SMTP
> >>> domain as the other users that don't see the problem. The Default
> >>> OWA directory can only server users that have email addresses in
> >>> the primary SMTP domain that is defined in your Default Recipient
> >>> Policy. Your new users may not authomatically be getting the same
> >>> domain's SMTP addresses assigned to them.
> >>
>>>> Lee.
> >>
>>>>

> >>> > >>>

> >>>

> >> There's a reason you're the MVP :)
> >
>>> He specifically said " i believe i have found the problem. However
> >> hopefully you can explain how to completly resolve. The issue has to
> >> do changing our email format. we had a recepient policy that you
> >> give theuserfirstinitialastn...@xxx.com and
> >> firstname.lastn...@xx.com"
> >
>>> I didn't count the x's in the domain name, as I assumed he just hit
> >> the x once too many times - BUT, it could be that his new recipient
> >> policy has a different domain!
> >
>>> Karl
> >>

> > You will need to check which is the Primary domain in the Default
> > Recipient Policy, then make sure that each user has an email address
> > in that domain. It doesn't have to be their Default SMTP Address, but
> > it does have to be in the list of their addresses if they want to use
> > OWA 2003. Or, you can create a new Exchange VDir in ESM, and make
> > the 'Exchange Path' property equal to the other domain; but I think
> > that's a more confusing solution for your users, since the new users
> > must now use a different URL.
>

>> Lee.-

>

>
> >

> Thanks Lee,

> however management wants to delete all old email addresses so i
> believe i will need to find a solution to correct this.
>


I beleive Lee gave you the soloution.

You have a Default Recipient Policy. All your users need an email address

in that domain.

If you are changing the default domain, you need to change it in the default

recipient policy, or add email addresses to the recipients that match that

domain.

So, if the default recipient policy shows a domain name of foobar.com and

you are changing to barfoo.com, you need to either change the default recipient

policy, or add email addresses to the new users so they also have foobar.com

addresses.

If you are doing this in stages, they way I would do it is create a new policy

for the new users listing the primary SMTP address @barfoo.com and a secondary

SMTP address @foobar.com

You can then transition the rest of the users at your leisure.

At somer point, you could change your default policy to be @barfoo.com and

remove all refernces to @foobar.com from your policies, and if in fact the

policies are now the same, delete the new policy.

Karl
 
L

Lee Derbyshire [MVP]

"Karl Mitschke" <karlmitschke@somestate.gov> wrote in message

news:d66cd4c2782e8cb7b6991eb61e9@msnews.microsoft.com...
> Hello Rollinwest,
>
> > On Mar 25, 7:55 am, "Lee Derbyshire [MVP]" <email a@t leederbyshire d.
> > 0.t c.0.m> wrote:
> >
> >> "Karl Mitschke" <karlmitsc...@somestate.gov> wrote in message
> >
>>> news:d66cd4c2778f8cb7b36afd997ee@msnews.microsoft.com...
> >
>>>> Hello Lee Derbyshire [MVP]" email leederbyshire d.0.t c.0.m,
> >>
>>>>> "Rollinwest" <RollinW...@gmail.com> wrote in message
> >>>> news:b3eeb12c-ff68-454e-8b8c-9edc75fb3467@o11g2000yql.googlegroups.
> >>>> com ... On Mar 24, 10:08 am, Karl Mitschke
> >>>> <karlmitsc...@somestate.gov> wrote:
> >>>
>>>>>> Hello Rollinwest,
> >>>>
>>>>>>> Hello all,
> >>>>>
>>>>>>> I have just noticed that any newuserthat i createcannotaccessowa.
> >>>>>> I get a pagecannotbe displayed. I am not sure that the problem
> >>>>>> is.
> >>>>>
>>>>>>> I have checked theuserproperties andOWAaccessis enabled. I do not
> >>>>>> see any events in the event viewer so i am confused.
> >>>>>
>>>>>>> Any help would be great!
> >>>>>
>>>>>>> Thanks,
> >>>>>> Rollinwest!
> >>>>> Are you running Exchange 2007?
> >>>>
>>>>>> If so, are you using the old ADUC integrated tools (or any
> >>>>> Exchange
> >>>>> 1000/2003
> >>>>> tools) to create the mailboxes?
> >>>>> If so, try this in the EMS:
> >>>>> Set-Mailbox -Identity <user> -ApplyMandatoryProperties
> >>>>
>>>>>> If you don't see the following, it means the mandatory properties
> >>>>> were not present. TryOWAagain :)
> >>>>
>>>>>> "WARNING: The command completed successfully but no settings of
> >>>>> 'userfqdn'
> >>>>> have been modified." would indicate that the AD object already had
> >>>>> the
> >>>>> mandatory
> >>>>> properties.
> >>>>> As an aside, and as far as I recall, these properties are:
> >>>>> msExchRecipientDisplayType: 1073741824
> >>>>> msExchRecipientTypeDetails:1
> >>>>> msExchVersion: 4535486012416
> >>>> Hello there,
> >>>
>>>>> i am running exchange 2003. so with that said should i try the
> >>>> other items in your email? Thanks!
> >>>
>>>>> --------> >>>
>>>>> Check that the problem users have an email address in the same SMTP
> >>>> domain as the other users that don't see the problem. The Default
> >>>> OWA directory can only server users that have email addresses in
> >>>> the primary SMTP domain that is defined in your Default Recipient
> >>>> Policy. Your new users may not authomatically be getting the same
> >>>> domain's SMTP addresses assigned to them.
> >>>
>>>>> Lee.
> >>>
>>>>>

> >>>> > >>>>

> >>>>

> >>> There's a reason you're the MVP :)
> >>
>>>> He specifically said " i believe i have found the problem. However
> >>> hopefully you can explain how to completly resolve. The issue has to
> >>> do changing our email format. we had a recepient policy that you
> >>> give theuserfirstinitialastn...@xxx.com and
> >>> firstname.lastn...@xx.com"
> >>
>>>> I didn't count the x's in the domain name, as I assumed he just hit
> >>> the x once too many times - BUT, it could be that his new recipient
> >>> policy has a different domain!
> >>
>>>> Karl
> >>
>>> You will need to check which is the Primary domain in the Default
> >> Recipient Policy, then make sure that each user has an email address
> >> in that domain. It doesn't have to be their Default SMTP Address, but
> >> it does have to be in the list of their addresses if they want to use
> >> OWA 2003. Or, you can create a new Exchange VDir in ESM, and make
> >> the 'Exchange Path' property equal to the other domain; but I think
> >> that's a more confusing solution for your users, since the new users
> >> must now use a different URL.
> >
>>> Lee.-

> >
>>
> >>

> > Thanks Lee,
>

>> however management wants to delete all old email addresses so i
> > believe i will need to find a solution to correct this.
> >


> I beleive Lee gave you the soloution.
> You have a Default Recipient Policy. All your users need an email address
> in that domain.

> If you are changing the default domain, you need to change it in the
> default recipient policy, or add email addresses to the recipients that
> match that domain.

> So, if the default recipient policy shows a domain name of foobar.com and
> you are changing to barfoo.com, you need to either change the default
> recipient policy, or add email addresses to the new users so they also
> have foobar.com addresses.

> If you are doing this in stages, they way I would do it is create a new
> policy for the new users listing the primary SMTP address @barfoo.com and
> a secondary SMTP address @foobar.com

> You can then transition the rest of the users at your leisure.

> At somer point, you could change your default policy to be @barfoo.com and
> remove all refernces to @foobar.com from your policies, and if in fact the
> policies are now the same, delete the new policy.

> Karl


Correct. You can leave the old domain name in the Default Recipient Policy

(so that you can still accept email for it, if you want to), but make the

new domain the default domain.

Lee.

 

gapostolou

Member
Outlook version
Outlook 2007
Email Account
Exchange Server
Just wanted to add that the the above resolution worked for me too. I have looking for a way of resloving this for ages and finally found the solution.

I had also deleted/amended the primary smtp address that is applied by the recipient policy and could not access OWA. Once I added this back in manually OWA worked perfectly.....woohoo
 
Status
Not open for further replies.
Top