Support 1

[Support 1]

The preliminary results of our tests indicate that for message properties to be accessible, the relevant account must be logged-in. For a native archive, this means having your GroupWise client switched to the archive prior to starting the export.

With Archive To Go 1.2 and above you can export a native archive without the corresponding main mailbox. If you switch your client to the relevant archive before exporting, this should avoid the errors you have seen.

Thus to export a native archive with message properties included, you will need to export it separately from the main account.

We will look into whether Archive To Go can automate this workaround by reliably switching between GroupWise message databases. In the meantime we have asked Novell to enhance the GroupWise API in order to address this issue.

Note: It appears that this issue also applies to incoming shared folders. That is, the message properties are not accessible for group (non-personal) items in an incoming shared folder. However in this case we are not aware of a workaround.

Regards,
Advansys Support

[This message was edited by Support 1 on November 05, 2007 at 10:05 PM.]

[Support 1]

This inquiry has been handled by direct email.

Regards,
Advansys Support

[Support 1]

Thank you for your inquiry.

This error is likely to be caused by running Finder from a network drive without reconfiguring the .NET permissions. Have you tried following the directions in this featured post?

Regards,
Advansys Support

[Support 1]

We are not sure what might cause this behavior, and are doing various tests in the hope of finding a pattern.

In the meantime I suggest you upgrade your GroupWise client and try again. We always recommend upgrading to the latest update for a given client version. In the case of 6.5, the appropriate update is 6.5.6 Update 1, also known as 6.5.7. (Note: 6.5.6 Update 2 will not work unless you also upgrade your server.) You can download this update (free) from the Novell website, on this page.

Regards,
Advansys Support

[Support 1]

I have generally found that it’s hard to write code that works with human-readable date/time values. When it’s necessary to record a date/time as a string, the UTC format is simple and easy to build or parse.

Why do you need to write code to work with the date/time in string form (human-readable or otherwise)? The reason I ask is for context; because there might be another way to solve the problem.

Regards,
Advansys Support

[Support 1]

I don’t think it’s possible to assign a value like “10/31/3007” to DateTimePicker.Date, which is really a floating point number.

Have you tried using the VBScript functions DateSerial(year, month, day) and TimeSerial(hour, minute, second)? You could use them to do something like:

  DateTimePicker.DateTime = DateSerial(2007, 10, 31) + TimeSerial(11, 54, 0)

Regards,
Advansys Support

[Support 1]

Some time ago we requested support for this in the GroupWise API. We are hopeful that it will be available in the next major version, codenamed “Bonsai”, which is due for release sometime during 2008.

Regards,
Advansys Support

[Support 1]

Thank you for your inquiry. The Viewer’s request to load media-01 is a generic request used if media-01 is not loaded or an expected file is not found on media-01.

It may be that one or more files were not copied (or were renamed) by your DVD-writing software. This could happen because a filename contains characters which are not allowed by the DVD file system, or because of some other file system limitation. Is there a log you can review for the DVD writing process?

In order to identify the missing file(s) we need to analyze some data in the archive. Please zip the “_metadata” sub-folder and send it to support@advansyscorp.com. This folder contains only:

• The folder names in a GroupWise account.
• For each exported message, its sender, recipients, subject, date.
• For each exported contact, its display name (if available), email address.

We look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for this report.

Which version of GroupWise are you running?

If you run the Viewer on this export, what text is displayed under the Properties tab for any of these messages?

You wrote here of using both versions 1.2 and 1.5 with your test account and its native archive. Do you get similar results with 1.2, i.e. when you review the Properties tab for each message – as well as the process log?

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

That’s great news. Thanks for the update.

Regards,
Advansys Support

[Support 1]

Thank you for your report.

Could you send the process log file (zipped if possible) to support@advansyscorp.com, please?

Could include samples of these problem messages in your email? It would be helpful if we could look at the original GroupWise message and the corresponding FML file (Advansys Portable Message) exported by Archive To Go. You can locate the FML file for a given message using the Viewer: go to the Properties tab and scroll to the end of the text where you fill find the full path to the file.

Regards,
Advansys Support

[Support 1]

>if I try .StartDate = DateTime1 (and .EndDate = DateTime2) then
>the result isn’t in the right format (and the applet errs out)

This will not work because the data type of DateTime1 and DateTime2 is DateTimePicker, whereas the data type of StartDate/EndDate is Date. See the Formativ Language Guide section on DateTimePicker and the GroupWise Object API documentation on Appointment.

Assuming iTimePeriodBegin and iTimePeriodEnd are updated to match the values set by the user in the dialog box, it looks like your appointment’s times are only partially set. The Formativ Language Guide section on DateTimePicker indicates that its properties include Date as well as Time. From your code excerpt it is not clear that the value of Date is included in iTimePeriodBegin/iTimePeriodEnd. To combine the values of Date and Time, simply add them:

  with DateTime1
    iTimePeriodBegin = .Date + .Time
  end with

I hope this helps.

Regards,
Advansys Support

[Support 1]

That’s great news, and thank you for the detailed update.

Regards,
Advansys Support

[Support 1]

We have received your email, and yes that way will be more convenient to discuss this matter.

Regards,
Advansys Support

[Support 1]

Thank you for reporting this issue.

Could you send the process log from one of the attempts to support@advansyscorp.com, please? If the log file is larger than 100KB then please zip it before attaching to your email. You will find the log file in the archive directory, e.g. a directory named “bsmith Archive” will contain the file “bsmith.log”.

Regards,
Advansys Support

[Author]

Replies