Forum Replies Created
-
AuthorReplies
-
December 22, 2010 at 6:39 pm in reply to: Archive To Go Finder has encountered a problem and needs to close. #9766
Thank you for reporting this problem, and sorry for the delay.
I think the errors you get with the Trust an Assembly wizard and .NET Configuration tool (.NET 1.1) are due to them being incompatible with Archive To Go 2.x, because it is based on .NET 2.0. You could use the equivalent utilities for .NET 2.0 but (unlike in .NET 1.1) they are not included with a standard .NET 2.0 installation. They are only available with the .NET 2.0 Software Development Kit which is a 354 MB download.
Alternatively, you could try the following based on the CasPol (code access security policy) utility which is included with a standard .NET 2.0 installation.
- Open a command window: go to the Windows Start menu and press Run… (or press the Windows key + R), then enter ‘cmd’.
- Navigate to the directory of .NET 2.0 utilities: either enter the text below by hand or copy it to the clipboard, right-click on the command window and press Paste.
cd WINDOWSMicrosoft.NETFrameworkv2.0.50727
- Similarly, enter the text below, but change ‘full path to a2gofinder.exe’ to the actual path on your network drive:
caspol -q -m -ag All_Code -strong -file “full path to a2gofinder.exe” -noname -noversion FullTrust -name “Advansys Archive To Go” -description “Advansys Archive To Go for GroupWise suite of applications.”
I hope this helps. Please let me know how you go.
When we have received confirmation that the above suggestion works, we will update the featured topic Running Archive To Go from a Network drive accordingly.
Kind regards,
Advansys SupportWe have received your email, thank you. A reply was sent to you on December 18th.
Regards,
Advansys SupportThanks for reporting this problem.
> Our license is supposed to cover 2 GW systems, but I’m wondering if it’s specific to the one it works on.
Do you mean your GroupWise license or your Archive To Go license?
It seems strange that you get this error with 2.0.0.5, which includes support for system discovery even when you have not authenticated to all Trees in your eDirectory system. This means system objects (eg. Post Offices, Users, Resources) from only the Trees to which you have authenticated will be listed.
You may be able to resolve this problem by authenticating to all Trees in your system, but please review the following before trying this option.
Do you have Read and Write permissions to the primary domain folder?
What platform (eg. NetWare, Linux) is your GroupWise server running on? Please provide details of the platform and server versions.
If your server platform is Linux, what is your setup for connectivity from a Windows client?
Please send the post office discovery log, which you will find in a location similar to the one below:
C:Documents and Settings[Windows User Name]Application DataAdvansysArchive To Go
The file name is based on your GroupWise system name. For a system named ‘GWDEV’, the file name is ‘PO discovery (GWDEV).log’. There may also be an older version of this file, eg. ‘PO discovery (GWDEV)-backup.log’. Please send these files (zipped) to support@advansyscorp.com for us to review.
We always recommend using the latest patch for the GroupWise client. For GroupWise 8.x it is 8.0.2 HP1; you may find the Novell Patch Finder useful for obtaining it.
I look forward to your reply.
Kind regards,
Advansys Support[This message was edited by Support 1 on December 20, 2010 at 03:53 PM.]
Thanks for reporting this problem.
Which Windows product/version are you using?
Which version of the GroupWise client are you using?
Which version of Archive To Go are you using? The current release, 2.0.0.5, fixes several memory errors like AccessViolationException.
Please send the log file shown below to support@advansyscorp.com:
C:Documents and Settings[Windows User Name]Application DataAdvansysArchive To GoSystem discovery (GWDEV).log
In the sample above, ‘GWDEV’ is the GroupWise system name.
Please describe as fully as possible how you used the System view at the time the error occurred. For example, was it immediately after creating a system definition, or when selecting Refresh for the selected item in the tree (Domain, Post Office or User?), or when expanding an item in the tree?
I look forward to your reply.
Kind regards,
Advansys Support[This message was edited by Support 1 on December 16, 2010 at 03:44 PM.]
Thanks for your post.
> Upon completion the log file is full of the a/m W messages.
I think ‘W’ above refers to warning items in the log denoted by ‘[W]’. What do you mean by ‘a/m’?
It may be helpful to send the full log (zipped) to support@advansyscorp.com for us to analyze.
> The archive works but I notice that internal addresses do not display the email address, only the name.
To my knowledge this is similar to the GroupWise client behavior: if a sender/recipient is internal (ie. represented in the system address book), only the name will be displayed in the item list (eg. ‘From’ column) and message header area.
Is there a further limitation that you have noticed?
Is this behavior new in 2.0.0.5 or do you see it in previous versions too?
Regards,
Advansys SupportThanks for your question.
> Can anyone confirm if Archive2Go can capture emails w/GWDMS attachments?
It sounds like you are referring to GroupWise Document Reference messages. These are messages which are like shortcuts to documents stored in GroupWise DMS. Archive To Go supports Document Reference messages and exports them with their documents as file attachments.
> I downloaded the demo and tried to create my archive, but I am getting the following error.
>
> 2010-11-29 10:42:26.865-06:00 [E] Creator general exception:Unfortunately we need more information in order to help you. Please send the full export log (zipped) to support@advansyscorp.com for us to analyze.
Regards,
Advansys SupportThanks for the clarification.
Regards,
Advansys SupportThat’s great news – thanks for letting us know.
By the way, just so we’re clear on this: what is ‘DEP’?
Regards,
Advansys SupportThank you for the additional information.
Please send the Formativ configuration from an affected workstation to support@advansyscorp.com. You can obtain the configuration by selecting Help | About Formativ… from the GroupWise main menu. When the About Formativ dialog appears, go to the Configuration tab and click the button Copy to clipboard. Then paste the text into your email (or save it to a plain-text file and include it as an attachment).
Regards,
Advansys SupportThanks for the clarification. Unfortunately I’m not sure what causes these errors.
Do you see the same errors on a machine where Windows XP is installed?
Do you see the same errors on a machine where Windows Vista or Windows 7 is installed?
> When any applet opens a form I get a grpwise.exe error – Access Violation at etc.
Are the applets involved custom applets that were developed by your organization? If so, which operating system/s were the affected forms developed on? If any applet was developed on different machines (with different operating systems – XP/Vista/7/2003/2008), please list the operating systems involved.
I look forward to your reply.
Regards,
Advansys SupportThanks for reporting these errors.
Are all the machines where you have installed Formativ 64-bit machines?
>I have installed the clients on non TS 2003 servers and received the same errors.
Could you list the operating systems installed on these machines, please? Are these 64-bit machines?
Please note that Formativ does not officially support Windows Terminal Services. A number of our customers are using Formativ successfully on Terminal Services. I have not seen feedback on customers’ experience with 64-bit machines.
Regards,
Advansys SupportThat’s great news – thanks for letting me know.
Regards,
Advansys SupportThanks for reporting this problem.
When you attempted to create the GroupWise system definition, were you logged in as Administrator (or equivalent)?
Is eDirectory set to allow creation of a trusted application for this GroupWise system?
Please send a screen shot of your System Properties dialog (Archive To Go Creator) to support@advanyscorp.com.
I look forward to your reply.
Regards,
Advansys SupportSeptember 7, 2010 at 6:59 pm in reply to: enterprise access – shared mailboxes not listed – how do I export them? #9751Thank you for the additional information.
I have added an item about this issue to the Archive To Go enhancements list. To assist our engineers in improving the product, please provide the following details about the External Entity objects:
- How many do you need to export?
- Do they belong to an external Post Office?
- Do they belong to an external Domain?
- Do they belong to a foreign (non-GroupWise) Domain?
I look forward to your reply.
Regards,
Advansys SupportSeptember 6, 2010 at 6:14 pm in reply to: enterprise access – shared mailboxes not listed – how do I export them? #9749Thank you for the clarification.
This is very interesting news about External Entity objects, because as far as I know Archive To Go fails with them in some way. Perhaps something has changed in GroupWise since the last review of these objects.
Could you verify the data exported from your External Entity objects, please? This would involve the following:
- Review the export log in the archive folder. Start with the summary, at the end, to check for any data access failures.
- Start the Viewer and browse a sample of messages (check plain-text and HTML formats, attachments) and contacts, if any.
Archive To Go excludes the following objects from the System view by default:
- External Entity
- External User
- External Post Office
- External Domain
- Non-GroupWise Domain
From your report it seems that we may need to review this default behavior. At present there is no way to make the System view list these objects.
Which version of the GroupWise client are you using? On the server side, which version of the Post Office Agent serves these objects?
For background, could you describe the business/technical reasons why you use External Entity objects as shared mailboxes, please?
If you prefer, you may reply to support@advansyscorp.com.
Regards,
Advansys Support[This message was edited by Support 1 on September 06, 2010 at 06:24 PM.]
-
AuthorReplies