User Logon Name length limit on OWA

Hi There,

On my production environment, I am running Exchange 2003 SP2 Back-End
Cluster with Exchange 2003 SP2 Front-End on Windows Server 2003 SP1, and I am
running Windows Server 2003 SP1 native Active Directory.

I found there is a limitation on User logon name on my environment, if a
user logon name is longer or equal than 15 characters, the user received
"HTTP 500, The website cannot be diaplay the page" error when accessing OWA
on the front-end(after entering the username and password through the form
authentication interfrace). It can only be fixed if I reduce the user logon
name length to 14 characters or lower.

However, I can successfully create a user with at least 20 characters in my
test environment with similar setup except the backend Exchange server is
standalone instead of cluster.

Any idea will be greatly appreciated!

Thanks
.

Relevant Pages

  • Re: Pompeii - First Thoughts with Spoilers
    ... Water pistol ... I viewed the story today and thought the modern slang ... but having all your period characters ... enough time to the environment, and the quick-zoom direction was off- ...
    (rec.arts.drwho)
  • Re: Text environment
    ... | standard environment - but the problem is not this but distinguishing ... Control characters are not valid in variable names. ... The parser has to keep track of the current context; ... In most other command processor languages the value of a variable does not ...
    (comp.os.msdos.4dos)
  • Re: problem with java, ASCII and Linux
    ... you have a problem with non-ASCII characters. ... ASCII is US-ASCII, ... Appears that you have some partially utf-8 -based environment. ... to your Java VM which character encoding is used by your terminal ...
    (comp.infosystems.www.servers.unix)
  • Re: SETDOS /X-4-6
    ... The parser has to keep track of the current context; the 0x01 as the first character in GOSUB variable names signals that it is a "very local" variable; the next character in the name is the context. ... As I already wrote, GOSUB and FOR variables in 4DOS are not stored in the environment but temporary stored in memory, and their lifetime is only during the command. ... Nor they are preceded by control characters, with the exception of the single-character FOR variables. ...
    (comp.os.msdos.4dos)
  • Re: allowing an @ sybol in a password
    ... It appears that you have teletype settings. ... characters were just ordinary printing characters, ... will use your current environment. ...
    (comp.unix.admin)