Knowledgebase: Scalix
Pim Login Failure in User Stats
Posted by Matt Kuebler on 09 November 2009 01:48 PM

Scalix:

If in User stats you are seeing a PIM login Failure for any of your users the first thing to do is trying to re-type their password in the Admin Console under User Administration ->Edit User.

If the password is correct then try the below steps to make sure NotifyLink and Scalix are communicating properly. Also check the NLPim.log(C:\Program Files>NotifyLink Enterprise Server) for any specific errors.


1. “GenerateScalixProfile aborting”
1. –2147467259

i. OL2000 must be in “corporate/workgroup” mode

2. –2147221233

i. remove / reinstall Scalix Connect for Wireless

ii. reregister cdo.dll (\system32)

iii. ever had GW on machine? No workaround for this

3. Other ideas:

i. Make sure OL is not running. Even if application is not running, check “processes” tab in task manager

2. “unable to verify CDO session”

MAPI_E_USER_CANCEL is usually a superuser problem (a).

MAPI_E_LOGON_FAILED could be any of the things listed below.

MAPI_E_NO_SUPPORT is usually account initialization (b-ii).

1. Check superuser:

i. This should NOT be the full email address

ii. Can login to superuser account through SWA?

1. same username / pwd used in NLES?

iii. Verify privileges from Scalix machine command line, type: omshowu –n

1. look for “Mailbox Admin Capabilities : YES”

2. “User Name” cannot have a space, i.e.

User Name : nospacesname /CN=nospacesname

2. Check NLES user:

i. Username must be full email address (different than superuser)

ii. Must login to user account with Outlook to initialize account. This must be done from machine with Scalix’s Full Outlook Connector and cannot be done from the NLES machine.

3. Check that Scalix mail server has DNS entry. If it does not or you are unsure, you can add the IP and hostname to the hosts file on the NLES machine (located at \system32\drivers\etc\hosts). To find the hostname simply type hostname from the command prompt on the Scalix machine (this may need to be done even if they use the IP itself as the mail server name in NLES).



Other things to remember / check:

1. \system32\cdo.dll should be version 5.5.2653.12

2. Outlook 2000 must be in “corporate / workgroup” mode (NOT “internet” mode)

3. Outlook 2002 (XP) must have SP1+