Archive to go fails immediately when started.

[jneureut]

After entering the paramaters for the archive of a groupwise 8.02 mailbox using archive to go 2.0.0.5, it fails imemdiately with the error in the log file. I have run various GWchecks and they come up clean. I can also archive other users from the same po just fine. Not sure what the error listed below is making reference to:

[E] Unable to get property by reflection: “RootFolder”:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Runtime.InteropServices.COMException (0x80020009): Could not find the folder object
— End of inner exception stack trace —
at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at xe01358da1a7cb0fa.x7927126fe5cc7aa8.x4ff37084a5d7d57f(Type x43163d22e8cd5a71, Object x6ed4ed9ed59eb694, String x46710263f0fedd95, Object xc6e85c82d0d89508, Object& xde5a5bc74acf4615)

2011-01-10 12:57:46.007-05:00 ______________________________________________________________________
2011-01-10 12:57:46.007-05:00 Folders archived: 0 (0 found)
2011-01-10 12:57:46.007-05:00 Messages archived: 0 (0 found)
2011-01-10 12:57:46.007-05:00 Contacts archived: 0 (0 found)
2011-01-10 12:57:46.007-05:00
2011-01-10 12:57:46.007-05:00 Completion: Warnings (check detail log entries marked as exception [E] or warning [W], [Warning])

Topic

[Support 3]

Thanks for your post.

Considering you can archive other accounts from same Post Office so the issue more likely account specific.

We had few reports about this issue and most case it was resolved by following one or more tasks listed in this feature topic: Troubleshooting Export Problems

The error shows it unable to access the ‘RootFolder’, we suggest you to use following feature topic suggestions:

• Create a new folder and move potential problem messages: Part of the GroupWise data store may become corrupted. Experience has shown that moving potential problem messages from one folder to a newly created folder can force a rewrite of the data store, which may rectify the access problem. If you are not sure about the problemetic messages in that folder then create a new folder and move few messages from that folder.
• Folders which contain more than 5,000 messages: If the folder contains more then 5000 messages then create a new folder and move few messages from that folder.

• Use folder filtering: If you know which folder is causing the problem and need to find a quick resolution, if the folder is not critical to your needs, use the Archive To Go folder filtering feature, which enables selective folder export

See the feature topic for more information. After making the above changes, please do a thorough GWCheck (Fix Structure and Contents) before retrying the export.

Hope this helps. If the problem persists then please send the Archive To Go and GWCheck log file (zipped) to Support (support@advansyscorp.com).

Regards,
Advansys Support

[jneureut]

It appears that there might be a limit of the number of folders the user has. This user was overly organized and had over a 1000 folders and subfolders.
I was also using an older 7.03 groupwise client so I upgraded it to 8.02 hp1 client (same version as this users Post Office) and it now works.

Thank you

[Support 3]

Great news, thanks for letting us know and glad it was of assistance.

Regards,
Advansys Support

[Author]

Replies