Discussion Locked

GroupWise 5.5 - Internal Error

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

For a while now, we have been experiencing an error in GroupWise 5.5. Even though we get this error, the program seems to be functioning fine. However, the error concerns me and I am unable to find a way to get rid of it. The error is the following:

*Internal Error* - The version of the address book 'Extension A' API used by the application calling into the address book DLLs does not match the version the address book DLLs were built for (address book DLL version: 0x00020012, version received from the calling application: 0x00020011). Do you want to run anyway?

Choices Given: Yes No

Upon clicking yes, this error is immediately followed by:

Running the address book API version numbers do not match may lead to unexpected results. Proceed at your own risk.

Choice Given: OK

Does anyone know how to fix this?

2 replies

by jcparkerconsulting

Your Clients and Server versions are out of sync. Download and install server and client patches from Novell. Perform / Schedule an autoupdate of newer files from the server. (I would suggest that you let yor users know as this will pause the screen for a few minutes).

What as happened is that you have gotten a later version of the address book .dll files from an upgrade (read patch) on your server. The calling application (Client Software either GroupWise Client or Outlook) has the older version of the api (older .dll version)

The Address Book is generated from a combination of NDS (Global Address Book) and user entry to form the resulting .dll file used at the workstations.

Hope this is of some assistance.

by mcintyrem

This is a matter of further research when it comes to updating the service. However, another person gave me a response that triggered my testing of the installation procedures. Instead of installing the program directly from the server, I used theCD and the Standard Installation option. By going this route (no others were successful), I was able to install the client on a workstation and totally eliminate the error. No other errors have ocurred since then. Thanks for your advice; it may prove to be very handy when I choose to update the program.

This discussion is closed to new replies.