Scalix Forums

Hi,
My helpdesk went and change a number of users display names and the "email display name". This created all kinds of problems. No one can log into the SWA. I've checked all the authentication IDs and changed a number of passwords. But I continue to get the incorrect login and password. I've verified the auth id from the command line. I've read similar posts that recommend stoping and killing the IMAP process which also hasn't worked. My own login doesn't work but I can login to Outlook and SAC no problem.
This also caused outbound internet email to appears as from Surname@fqdn rather than givenname.surname@domain.com. I fixed this when changing the display names back to their original. I've restarted tomcat and the box has been rebooted since then but I still can't get into the SWA.
Why is changing the display name so problematic? I know this will happen in the future and would like to prevent any problems with email delivery, access, and logins.

I'm still running version 10.0.0.175, but I'm planning to upgrade to 10.0.1 and then 10.0.2 before this weekend.
TIA
chrisj

I just noticed that the CDA server was in an aborted state. I had a .lock file on the system from a power failure. I've removed the lock file, started the CDA process, run the omexeccda command, changed my password again, restarted tomcat, as well as restarting IMAP.
I still can't login.
What am I missing?

Hi Chris,

The IMAP server is likely caching the names from people's previous logins. Try this:

omoff -d0 -w rci imap
omon rci imap

Now, try logging in via SWA and see what happens.

Thanks,
Rachel

Rachel,
That didn't work. I'm not able to login the SWA. I can, however log into SAC with the same username and password.
thx,
chrisj

Hi Chris,

Two more things you may need to do. First, restart tomcat and second, clear your browser cache. If that doesn't work, please do an omshowu for that user, then do an "omsearch -e cn=USER-CN -m @all-attr@ -v" where USER-CN is the user's CN and post the output along with the exact name you're sending as.

Thanks,
Rachel

I'll mail the output to support. There's some info I'd rather not have sitting on the forum.

Hi
Did you solved this problem?
I have the same problem with one user and SWA.
THX
Erich

This may be a hanging IMAP process. Do an omshowu username -f, this will show you the User-ID which relates to the process ID the IMAP satellite would be running under. Do a ps -ef | grep PID on it and if it appears to be old, kill it. Then, try again.

Sascha.