Support 1a

[Support 1a]

To read/write proxy access information, Enterprise Proxy must be able to log into any user in your GroupWise system. To access each account, Enterprise Proxy may need to know the connection settings used by the POA serving each user.

In many environments such settings are unnecessary. However, if you experience problems logging into user accounts, you may need to specify POA connection settings for each of the Post Offices in your GroupWise system.

1. Run Enterprise Proxy.

2. Select the Post Office object in the tree that requires connection settings to be specified.

3. Click the PO Settings… option on the left side of the dialog. The POA Settings dialog appears.

4. Specify either the IP address and port number of the POA, or the full path to the Post office.

5. Click OK to save your changes.

Once POA settings have been associated with a Post Office it is shown with a red icon in the system tree view. For example, in the figure below two Post Office objects are visible. The Post Office object labelled 1 (GWDEVPO) does not have any settings associated with it. The Post Office labelled 2 (GWDEVPO2) is shown with a red icon, indicating connection settings have been applied.

Note that specifying the direct path to the post office can result in significantly faster performance compared to specifying an IP address and port number.

Advansys Support

[Support 1a]

The MS DOM doesn’t like spaces. I suspect you may need to replace the spaces in the URL with HTML encoded spaces, ‘%20’ from memory, before you copy the data to the clipboard.

Regards,

Advansys Support

[Support 1a]

We’ve just tested this and unfortunately it would appear Novell have not fixed the defect in the 9/29/2005 GW release. Feel free to lobby Novell to have this issue resolved – the more voices the better.

Advansys Support

[Support 1a]

This was reported to Novell as a bug prior to GW7. I recall they had difficulty reproducing it in the GW7 client, so it may have been resolved. We have not yet confirmed if this is resolved in the FTF version of the GW7 client just released.

[Support 1a]

Does your client meet the minimum requirements?

• Novell GroupWise 32-bit Windows Client, Version 6.5.3 or later.
• Microsoft .NET Framework 1.1.
• Windows Installer.

The Microsoft .NET Framework 1.1 Redistributable has the following requirements:

• Windows XP Professional.
• Windows XP Home Edition.
• Windows 2000.
• Windows Millennium Edition (Windows Me).
• Windows 98.
• 32 megabytes (MB) of RAM, 96 MB or higher recommended.
• 110 MB of hard disk space required, 40 MB additional hard disk space required for installation (150 MB total).
• 800 x 600 or higher-resolution display with 256 colors.
• Microsoft Internet Explorer 5.01 or later.

Advansys Support

[Support 1a]

Thanks for the update. Are any of the domains external?

I look forward to hearing how you procced with Enterprise Proxy.

Advansys Support

[Support 1a]

Could you please detail the exact steps you are performing to test this, including how/when you copy data to the clipboard? We’ll be able to fix it if we can reproduce it.

Advansys Support

[Support 1a]

You would populate the combo, not the AB control. I’ve sent an example to your email address.

Advansys Support

[Support 1a]

Thanks MA.

Advansys Support

[Support 1a]

Marc/LP – thanks for the input.

Advansys Support

[Support 1a]

You require 6.5.3 or higher on the client. You should be OK with a 6.5.1 backend. I would not expect you would have any problems running 6.5.3 against a 6.5.1 agent, though it is a good idea to keep them in sync.

Advansys Support

[Support 1a]

I doubt this has anything to do with the Trusted Application component of the solution. The tree view is populated with users based on information returned using the Admin API. This is what appears to be failing.

Reasons why this might happen could include:

– You have an incomplete/faulty GroupWise client installation. The Admin API is a component of the Windows client. You may wish to try re-installing the GroupWise client to see if this resolves the issue.

– Your GroupWise topology is stopping the Admin API from ‘seeing’ your system. I know this can happen if you using using foreign Domains, for example. Is your GroupWise system ‘unusal’ in any way? Do you have a firewall between you and any of the GroupWise agents?

You may wish to try installing a trial version of our Enterprise Proxy solution. It also uses the Admin API to populate a tree with system components. It would be interesting to see if you are able to see users, etc, with that solution.

Please let me know how you proceed.

Advansys Support

[Support 1a]

Unfortunately Novell’s name completion control appears to be read-only. We were unable to preset it with data. I suspect you may have to re-work the way the recipient management will work in your application. You may be able to use a standard Edit control in conjunction with the Address Book control.

Advansys Support

[Support 1a]

Unfortunately we were unable to reproduce the problem. We tried with the latest version of stationery available from the downloads page. Could you please try installing the latest version and see if the problem persists?

Advansys Support

[Support 1a]

Here’s some sample code that checks the ‘To’ field to ensure it doesn’t contain more than 3 recipients. (The number can be changed by changing the value of the constant). The applet would need to be integrated with the OnSend event.

Please note this technique doesn’t check to see if any of the recipients are in groups. This requires a more complex solution.

I hope this helps.

Advansys Support

' This sample code will check the number of addresses in the TO field and stop
' sending the message if the addresses exceed the limit.  The applet must be
' integrated to fire in response to the OnSend event.

const IDS_EXCEED_LIMIT = 3


'-------------------------------------------------------------------------------
' Main line processing
'-------------------------------------------------------------------------------
sub Main(Client, GWEvent)

  ' Stop the send if the number of recipients exceeds IDS_EXCEED_LIMIT.
  if (GetTotalAddresses(groupwise.ItemGetText("X00", itfTo)) > IDS_EXCEED_LIMIT) then
    call msgbox("", vbExclamation, "Advansys Formativ")
    groupwise.CancelGroupWiseEvent = true
  end if

End Sub


'-------------------------------------------------------------------------------
' Get total number of addresses in the field.
'-------------------------------------------------------------------------------
function GetTotalAddresses(addresses)

  if (len(addresses) = 0) then
    GetTotalAddresses = 0
    exit function
  end if

  if (instr(1, addresses, ";", vbTextCompare) > 0) then
     GetTotalAddresses = ubound(Split(addresses, ";", -1, vbTextCompare)) + 1
  elseif (instr(1, addresses, ",", vbTextCompare) > 0) then
     GetTotalAddresses = ubound(Split(addresses, ",", -1, vbTextCompare)) + 1
  else
     GetTotalAddresses = 1
  end if

end function

[Author]

Replies