Global Addressbook error

[joejoe]

Hello,

in SWA i cannot get the global Adress Book.
Every time I want to select a Adresse the following Erroro occours:

"An error has occoured. Contact your System Administrator if the problem persists. #AS020"

In Outlook ist the Addressbook available.
Version:

Scalix Web Access
Version 11.2.0.52
Platform Version 11.2.0.52
Server Version 11.2.0.11121

Anybody knows how to fix this?
Tanks, Jochen

[Obi]

Hi joejoe,
we have a similar error on a customer system. Did we have the same configuration?

CentOS5
Scalix 11.2.0.52 SBS with AD integration

The addressbook works with the outlook connector but in swa we have the same error.

If you do not have AD integration we dont have to look at this way... did you have found a solution for this issue?

[f.plow]

Hi,

we have the same problem... same error message in the address book view in SWA! In Outlook all addresses are shown. No AD involved here.

Anything new on this topic?

Thanks
f.plow

[bguerreiro]

Hi,

we have the same problem... same error message in the address book view in SWA! In Outlook all addresses are shown. No AD involved here.

Anything new on this topic?

Thanks
f.plow

HI,
I've run into this issue also.
Have you tried disabling authentication in /var/opt/scalix/sn/webmail/swa.properties ?
by changing

Code: Select all

swa.ldap.1.authType=simple

to

Code: Select all

swa.ldap.1.authType=none

BRGDS.
BG

[dwerthmu]

This setting didn't work for us.
Scalix purchased licensed version 11.2, on RHEL 5 with Ldap integration for logins.

Whats up with this addressbook via webmail? It worked on version11.1 and 11.0
Granted we have 7500 entries in the directory but this is 1 user on a big server so timeout shouldn't be an issue.

[dwerthmu]

The address book does work but only for directed searches.
a search for staff brings up the staff email list and anyone with staff as part of their name or part of the email address.

But a blank search to browse the list brings up the message posted above.

Also the work searching is listed in the results even when the search is finished.

[lordzik]

I've got the same problem. It happens when:
- create new user in AD
- create Scalix mailbox for him using option 'Use server generated e-mail address (Recommended)'
- synchronize Scalix with AD (omldapsync -u xxxx)
- on AD, go to properties of that user and switch from 'Use server generated e-mail address (Recommended)' to 'Specify email address manually' and create new e-mail address for him.
- synchronize Scalix with AD (omldapsync -u xxxx)

That's it - "An error has occoured. Contact your System Administrator if the problem persists" shows when you go to address book in webmail.
After click on 'Search' popup with error message appears:
Line: 2
Char: 274570
Error: No such interface supported
Code: 0
URL: http://10.0.0.100/webmail/dlg_AddressSe ... cale=en_US

Any fix for that?

[f.plow]

HI,
I've run into this issue also.
Have you tried disabling authentication in /var/opt/scalix/sn/webmail/swa.properties ?
by changing

Code: Select all

swa.ldap.1.authType=simple

to

Code: Select all

swa.ldap.1.authType=none

BRGDS.
BG

Works for us, thank you!

[dwerthmu]

This ended up working for us to:
Solved this problem:
viewtopic.php?t=9973&highlight=

What are the security ramifications of making this change?

[deyjvu]

Just adding a 'me too' to this posting as we have been experiencing this problem at a site that does not do omldapsync but does point to a second ldap directory from within swa.properties.

At first it was only one user, who when he opened a new message and clicked on TO: he would get the error message AS020 etc.

Now it is happening to almost every user on the system. Will check if the simple has been changed to none.

[kdarker]

these forums are great! this solved my problem too, thanks.

[DaryleTilroe]

So I have a similar problem, the authentication hack more or less "fixed" it but I think it may be a bandaid. I am running:

SWA
Version 11.3.9.97
Platform 11.3.0.77
Server 11.2.0.11339

I had this issue when opening the webmail address lookup as SWA tries to build a list of all addresses. It seemed to bog down 'omslapdeng', ie. it took up an inordinate amount of CPU time, and the slapd.debug log looked like this (before auth hack):

Apr 15 18:00:57 odin omslapd[18461]: conn=416 fd=71 connection from unknown (172.16.0.7)
Apr 15 18:00:57 odin omslapd[18461]: conn=416 op=0 BIND dn="mail=d****@micralyne.com" method=128
Apr 15 18:00:57 odin omslapd[18461]: conn=416 op=0 RESULT err=0 tag=97 nentries=0
Apr 15 18:00:57 odin omslapd[18461]: conn=416 op=1 SRCH base="o=scalix" scope=1 filter="(&(mail=h****@micralyne.com)(objectclass=person))"
Apr 15 18:00:57 odin omslapd[18461]: conn=416 op=1 RESULT err=0 tag=101 nentries=0
Apr 15 18:00:57 odin omslapd[18461]: conn=417 fd=72 connection from unknown (172.16.0.7)
Apr 15 18:00:57 odin omslapd[18461]: conn=417 op=0 BIND dn="mail=d****@micralyne.com" method=128
Apr 15 18:00:58 odin omslapd[18461]: conn=417 op=0 RESULT err=0 tag=97 nentries=0
Apr 15 18:00:58 odin omslapd[18461]: conn=417 op=1 SRCH base="o=scalix" scope=1 filter="(&(mail=h2****@micralyne.com)(objectclass=person))"
Apr 15 18:00:58 odin omslapd[18461]: conn=417 op=1 RESULT err=0 tag=101 nentries=0

with pauses on each connection.

After the auth hack is similar but it runs through quite quickly with the blank BIND:

Apr 15 19:54:38 odin omslapd[20552]: conn=1183 fd=231 connection from unknown (172.16.0.7)
Apr 15 19:54:38 odin omslapd[20552]: conn=1183 op=0 BIND dn="" method=128
Apr 15 19:54:38 odin omslapd[20552]: conn=1183 op=0 RESULT err=0 tag=97 nentries=0
Apr 15 19:54:38 odin omslapd[20552]: conn=1183 op=1 SRCH base="o=scalix" scope=1 filter="(&(mail=j******@micralyne.com)(objectclass=person))"

Apr 15 19:54:38 odin omslapd[20552]: conn=1183 op=1 RESULT err=0 tag=101 nentries=0
Apr 15 19:54:38 odin omslapd[20552]: conn=1184 fd=232 connection from unknown (172.16.0.7)
Apr 15 19:54:38 odin omslapd[20552]: conn=1184 op=0 BIND dn="" method=128
Apr 15 19:54:38 odin omslapd[20552]: conn=1184 op=0 RESULT err=0 tag=97 nentries=0
Apr 15 19:54:38 odin omslapd[20552]: conn=1184 op=1 SRCH base="o=scalix" scope=1 filter="(&(mail=j******@micralyne.com)(objectclass=person))"
Apr 15 19:54:38 odin omslapd[20552]: conn=1184 op=1 RESULT err=0 tag=101 nentries=0

Now I don't know quite what SWA is doing to make this very strange and ineffcient query. The log for a similar ldap search from Tbird:

Apr 15 19:11:58 odin omslapd[20552]: conn=432 fd=40 connection from unknown (172.16.4.1)
Apr 15 19:11:58 odin omslapd[20552]: conn=432 op=0 BIND dn="" method=128
Apr 15 19:11:58 odin omslapd[20552]: conn=432 op=0 RESULT err=0 tag=97 nentries=0
Apr 15 19:11:58 odin omslapd[20552]: conn=432 op=1 SRCH base="o=Scalix" scope=2 filter="(|(mail=*)(cn=*)(givenname=*)(sn=*))"
Apr 15 19:11:59 odin omslapd[20552]: conn=432 op=1 RESULT err=4 tag=101 nentries=0

I guess the main questions are:

-why is SWA opening a new connection for each address,
-how to change this behaviour to something more efficient,
-and if fiddling with the filter string in swa.properties can achieve that somehow?

[mclark2112]

Has this error been addressed? I get this as well, and the fix in here did not work.

I have Scalix Enterprise 11.4.5
CentOS 5.4
Active Directory with Kerberos Auto Login

Only my AD added accounts have this directory search error.

This would seem to be a major bug?

[mclark2112]

Was this issue addressed in the newest release?