Novell GroupWise 2012
Novell GroupWise Free Busy Service
When checking availability of GroupWise recipients in a Scheduling Assistant of Outlook 2010 client (EWS), there were no booked appointments showing. Displayed results showed like if GroupWise data was available but no appointments were displayed.
When doing exactly the same from Exchange WebAccess (OWA), then you received correct data, i.e. booked appointments of GroupWise recipients were displayed as expected. A redirector log file (EWA) showed following information:
2013-04-23 17:18:26,431  DEBUG - Enter Application_BeginRequest
2013-04-23 17:18:26,431  DEBUG - No GroupWise users found
This was a specific problem of the Exchange configuration of one customer. There were attempts to make Free Busy Search working between existing GroupWise and Exchange system in a past. There was a test to get it working similarly like Exchange system does via Public Folders and there was also an address space assigned "mygroupwise.company.com" (here just example of GroupWise default iDomain name). That was the same iDomain of GroupWise system that was used later also in a Free Busy Service configuration tool. That Public Folder part of the Exchange configuration was forgotten. It caused Exchange system to check for GroupWise users data in own Public Folders area instead of contacting GroupWise system via the SOAP protocol of the POA.
After removing this old, obsolete configuration, Exchange system (EWS part) started to pass such requests to a GroupWise system and was able to present correct results.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.