Location Autocomplete Failed for appointment location field

[flyerguybham]

Today a couple of my users noticed that when they go to schedule appointments, when they start typing in a location name, they get the "Autocomplete Failed" popup message almost immediately and no locations are returned in the list. This happens from both the QuickAdd dialog and the full appointment wizard in the Location field on the Appointment Details tab. If I go to the Find Locations tab, and then search for locations and add them that way, it works fine.

Autocomplete is working fine for email addresses when composing emails and for attendee email addresses when scheduling appointments. It's only failing for Location autocompletes.

I verified this behavior on Firefox 3 on Linux, Firefox 3 on Windows, and IE7, from multiple user accounts.

I do notice that I get a bunch of these on the JavaScript error console when autocomplete runs:

Warning: The 'charCode' property of a keyup event should not be used. The value is meaningless.

...but I get these for all autocompletes, even ones that work. And, it's a warning, not an error, so maybe not an issue.

Two things have changed recently. On Sunday evening I upgraded from 5.0.16 to 6.0.2. Although I did not personally schedule any appointments Sunday evening or Monday, I should note that no users complained about this during that time.

Then, this morning I updated the SSL certificate on our 6.0.2 server to a commercial one using zmcertmgr. The certificate and the CA chain both validated successfully, it was installed successfully, and after restart browsers are seeing the new certificate successfully. The above buggy behavior is occurring regardless of whether I use http or https to access the web client. However, I wanted to mention it as it was the last thing which changed before users started seeing this bug.

Any thoughts? Where would I start to look in logs to hunt down the error?

[ArcaneMagus]

If you have a firefox install with the firebug addon, can you take a look at any network requests when you do the searches? I would imagine it would be similar to any requests you would see for contact searches if you wanted a reference point as to what it should look like.

[flyerguybham]

Great idea!

Ok, doing a contact autocomplete on the string "to" I see a POST AutoCompleteReq go out:

{"Header":{"context":{"_jsns":"urn:zimbra","userAg ent":{"name":"ZimbraWebClient - FF3.0 (Linux)","version":"6.0.2_GA_1912.RHEL5_64"},"sess ion":{"_content":12441,"id":12441},"account":{"_co ntent":"fran@cis.uab.edu","by":"name"},"authToken" :"0_603cf09757d1ec528e520d83b8e88574272529cf_69643 d33363a35376635343632312d626636392d343031362d62643 1652d3536353761303161393636383b6578703d31333a31323 5383133383838343139383b747970653d363a7a696d6272613 b"}},"Body":{"AutoCompleteRequest":{"_jsns":"urn:z imbraMail","name":{"_content":"to"}}}}

with the response:

{"Header":{"context":{"session":{"id":"12441","_co ntent":"12441"},"change":{"token":1258757},"_jsns" :"urn:zimbra"}},"Body":{"AutoCompleteResponse":{"c anBeCached":true,"match":[{"email":"\"tony XXXXXXX\" \x3CXXXXX@XXXXX.edu\x3E","type":"contact","ranking ":"1","l":"7"}, etc..... in other words, contacts come back just fine.

And doing a location autocomplete on the string "ch" (all of our rooms begin with those letters) I see a POST AutoCompleteReq go out:

{"Header":{"context":{"_jsns":"urn:zimbra","userAg ent":{"name":"ZimbraWebClient - FF3.0 (Linux)","version":"6.0.2_GA_1912.RHEL5_64"},"sess ion":{"_content":12441,"id":12441},"account":{"_co ntent":"fran@cis.uab.edu","by":"name"},"authToken" :"0_603cf29767d1ec528e520d83b8e88574272529cf_69643 d33363a35376635343632312d626636392d343031362d62643 1652d3536353761303161393636383b6578703d31333a31323 5383133383838343139383b747970653d363a7a696d6272613 b"}},"Body":{"AutoCompleteGalRequest":{"_jsns":"ur n:zimbraAccount","limit":20,"name":"ch","type":"re source"}}}

with the response:

{"Header":{"context":{"session":{"id":"12441","_co ntent":"12441"},"change":{"token":1258758},"_jsns" :"urn:zimbra"}},"Body":{"Fault":{"Code":{"Value":" soap:Receiver"},"Reason":{"Text":"system failure: ldap search failed"},"Detail":{"Error":{"Code":"service.FAILUR E","Trace":"btpool0-1176://zimbra/service/soap/AutoCompleteGalRequest:1257978129439:cb981c293c312 575","_jsns":"urn:zimbra"}}}},"_jsns":"urn:zimbraS oap"}

So the ldap query fails for location but works for contacts.

Now, my GAL is configured to query both the internal and an external LDAP, but for locations it would just be querying the internal one. I wonder if there is a connectivity issue with the internal LDAP, or maybe an ACL issue of some sort?

[ArcaneMagus]

Hmmm, well the only difference is the contact search uses "AutoCompleteRequest" whereas the location search uses "AutoCompleteGalRequest", beyond that difference I have no idea... it works perfectly here

I'll see if I can dig up the code for those and see what the difference is, but I have no idea here...

These bugs might be of relevance:
Bug 42317 - Use AutoCompleteRequest instead of AutoCompleteGalRequest
Bug 41000 - Unable to view Resources within the GAL.

[shan]

We upgraded ZCS from 5.0.18 to 5.0.21. We run into same problem. Auto compelte for resources stopped working. Anyone out there has the same problem with releases later than 5.0.18? It was working before 5.0.18.

[flyerguybham]

Unfortunately, we still get the Autocomplete Failed message whenever trying to do Location autocompletes.

Very frustrating. It's confusing the heck out of our front office staff, who keep think they are reserving rooms for events when they really aren't.

[hchan]

This is definitely causing a problem here too. Zimbra Network edition 5.0.21. Client side mostly Firefox 3.5.7/3.6.x. Any new updates or fixes?