XFOR: API Gateway Logs Unknown Keyword Errors on Exchange Free Busy Search (222538)

SYMPTOMS

The Outlook client will fail to obtain free-busy data for the GroupWise custom recipients by means of the Calendar Connector.

The Novell GroupWise API Gateway may log the following to its logfile:

03-15-99 14:38:51 Unknown keyword: WPPO
03-15-99 14:38:51 Unknown keyword: WPU
03-15-99 14:38:51 Unknown keyword: CDBA
03-15-99 14:38:51 Unknown keyword: 
03-15-99 14:38:51 Unknown keyword: WPPO
03-15-99 14:38:51 Unknown keyword: WPU
03-15-99 14:38:51 Unknown keyword: CDBA
03-15-99 14:38:51 Unknown keyword: 
...
03-15-99 14:38:51 Unknown destination in address string: WPD= GWDOMAIN
...
03-15-99 14:38:51 Error building the GroupWise message

The API Gateway will place the .API file in the API\GWPROB directory. The file will look similar to the following:

WPC-API= 1.2;
MSG-TYPE= Search;
Msg-ID= AALHJNKA:1999.3.15.14.38:1999.3.22.14.38:1999.3.15.19.38.45;
From= 
    WPD= GWDOMAIN; 
    WPPO= API; 
    WPU= BRIANCL001-SA; 
    CDBA= GWDOMAIN.API.BRIANCL001-SA; ; 
To= 
    WPD= GWDOMAIN; 
    WPPO= GWPO; 
    WPU= GWUser2; 
    CDBA= GWDOMAIN.GWPO.GWUser2; ; 
Begin-Time= 15/3/1999 14:38 +0;
End-Time= 22/3/1999 14:38 +0;
-END-

Line 006 Unknown keyword: WPPO
Line 007 Unknown keyword: WPU
Line 008 Unknown keyword: CDBA
Line 008 Unknown keyword: 
Line 011 Unknown keyword: WPPO
Line 012 Unknown keyword: WPU
Line 013 Unknown keyword: CDBA
Line 013 Unknown keyword:

RESOLUTION

For GroupWise 5.x

Start NetWare Administrator.
Double-click on the API Gateway object.
Click Required Parameters.
Change the Addressing Format from GroupWise to Component.
Click OK.
Stop the API Gateway.
Restart the ADA (in GroupWise 5.5, the message transfer agent [MTA]).
Start the API Gateway.

For GroupWise 4.x

Start the Ad.exe program within a command prompt.
Tab over to the System window.
Highlight the API Gateway object.
From the menu, select Actions, then Edit.
Tab over to the Specific option, or press the S key.
Change the Addressing Format from GroupWise to Component
Stop the API Gateway.
Restart the Message Server.
Start the API Gateway.