Support 1a

[Support 1a]

The Admin API COM server will be registered when the standard GroupWise client is installed using the client setup program supplied by Novell. It may not be registered if you are installing the client using ZEN (or similar), or if you are using a re-packaged installation (for example, an MSI installation you created yourself).

The Admin API is implemented in the client file GWCMB1.DLL (normally found in ‘C:NovellGroupWise’). You could try to manually register the file using something like ‘regsvr32 GWCMB1.DLL’.

When registered, this file will create registry entries like:

HKEY_CLASSES_ROOTNovellGroupWareAdminCLSID
HKEY_CLASSES_ROOTNovellGroupWareAdminCurVer
HKEY_CLASSES_ROOTNovellGroupWareAdminNotInsertable
HKEY_CLASSES_ROOTCLSID{35fc2358-811a-11d0-8a96-00805fc16077}InprocServer32
HKEY_CLASSES_ROOTCLSID{35fc2358-811a-11d0-8a96-00805fc16077}NotInsertable
HKEY_CLASSES_ROOTCLSID{35fc2358-811a-11d0-8a96-00805fc16077}ProgID
HKEY_CLASSES_ROOTCLSID{35fc2358-811a-11d0-8a96-00805fc16077}Programmable
HKEY_CLASSES_ROOTCLSID{35fc2358-811a-11d0-8a96-00805fc16077}TypeLib
HKEY_CLASSES_ROOTCLSID{35fc2358-811a-11d0-8a96-00805fc16077}VersionIndependentProgID

These are incomplete – please don’t try to enter these entries manually.

Advansys Support

[Support 1a]

There is no reason this should normally happen, other than you may have an applet installed that is blocking the send event.

From the main GroupWise menu, select Help | About Formativ. Click on the applets tab, which will display a list of applets (if any) that are installed. I suspect one of these may be the culprit. If you are unsure, select the Configuration tab, then press the ‘copy to clipboard’ button. This will copy the configuration information into the clipboard, which you could then paste into a message back to support@advansyscorp.com and we’ll take a look.

Regards,

Advansys Support

[Support 1a]

You are welcome. We’ll be in contact when we revisit this issue.

Advansys Support

[Support 1a]

You are welcome.

Advansys Support

[Support 1a]

Thanks MA. Depending on the situation, simply supplying a TEXT.htm attachment may not be enough, and creation of a MIME.822 attachment may be required.

Advansys Support

[Support 1a]

‘NovellGroupWareAdmin’ is a service of the Windows 32-bit GroupWise client. I assume you are running the GroupWise Windows client in a native windows session, and Linux on the server?

Assuming so, the problem is due to an incomplete GroupWise client installation. If the NovellGroupWareAdmin object is not registered, the solution cannot create it and hence the message you describe appears.

We have seen this happen when people use incomplete ZEN snapshots to install the client, or have re-packged the installation. I have also seen this happen when the local configuration does not provide the required access to the Windows registry so that object registration entries can be created.

Advansys Support

[Support 1a]

Hold down the CTRL and SHIFT keys, then start the solution while the keys are still held down. release the keys, then run the solution to the point where you see the problem. Exit the solution, at which point a draft email message should be created and a log file attached. Send this draft email to support@advansyscorp.com and we’ll take a look.

Regards,

Advansys Support

[Support 1a]

I note you are using eDirectory to supply configuration information. The settings in eDirectory will override local settings. Check the eDirectory configuration object ‘CN=Corporate Configuration.OU=GroupWise_Macros.O=BBL’ to see if it allows applet recording.

Advansys Support

[Support 1a]

The following code may help. (When recording, you need to use TAB to navigate between fields in order for the recorder to see your actions).

Sub Main(Client, GWEvent)

   call GroupWise.FocusSet(9, "")
   call GroupWise.ItemSetText("X00", itfSubject, " :Secure", true)

End Sub

The key here is the ItemSetText command (you’ll find it documented in the users guide). It appends the text ‘ :Secure’ to the end of the subject of the current message (denoted by the message ID ‘X00’).

I hope this helps.

Advansys Support

[Support 1a]

Dear Perry,

Thank you for your post and suggestion. This is something we have considered, and agree it is a worthy enhancement. We are currently fully committed to delivery our new ‘Archive To Go’ product. Once released, we’ll be in a position to look into some of these issues, including this one.

I’ll make a note of your details in the enhancement database. When we revisit this issue we’ll get in contact directly.

Thank you again for the feedback.

Regards,

Advansys Support

[Support 1a]

Thanks MA.

Advansys Support

[Support 1a]

Hello Sonja,

An example applet is on it’s way via email.

Advansys Support

[Support 1a]

Even though it’s not documented by Novell, I think this is correct. (possibly for reasons of security).

Advansys Support

[Support 1a]

Sorry – the reply was cut directly from the Users Guide. Please refer to the documentation to see the image referred to.

Obtaining the list of users is not related to a successfull login, it simply means the API used by the solution is able to ‘see’ the user list.

Logging into a users account requires a) the Trusted Application to be created and synchronized throught your GroupWise system, and b) Post Office properties to have been correctly defined for each Post office. Problems like the one you describe are generally caused by the later.

Advansys Support

[Support 1a]

The Archive To Go creator option, Include message property information, is far more likely to be affected by problem messages in a GroupWise mailbox. The most common symptom is that during the archive process GroupWise will display D107 (Record not found) and/or D109 (Bad parameter) errors – see the GroupWise Administration Guide for more information.

The problem with these GroupWise errors is that an error message dialog pauses the Archive To Go export process until it is dismissed by the user. This can be most inconvenient when the errors are intermittent and you need to continually check on the export process. Archive To Go cannot suppress these GroupWise error messages. If GroupWise does not have the focus when a D107 or other error occurs, the message dialog can be hidden behind the Archive To Go status dialog and it may appear that the archive process has ‘hung’. You need to dismiss the error dialog before the process can continue. To ensure you can see GroupWise error messages, drag the Archive To Go dialog down to the bottom right of your screen.

The only workaround at this time is to either dismiss the error messages (and the process should continue), or uncheck the ‘Include message property information’ option. We are hoping Novell will remove this annoying message in a furture version on the client. We are also considering a D107 error message dialog box ‘killer’ application that will dismiss these warnings automatically.

Regards,

Advansys Support

[Author]

Replies