Tedd

[Tedd]

Our GroupWise system (Primary and 31 Secondary domains) spans 12 eDirectory trees. We have nine external domains. When I originally installed A2G (in 9/08) we had six or seven more domains/trees but we have been consolidating. If I remember correctly, when I set that up I had to connect to most of these trees before I was able to define a System in A2G v1.x. Since then I only need to be attached to my Primary domain tree and the tree containing the domain of any users I need to archive with A2G.

I did follow your directions but I did not have a systems.xml file to rename because I had removed the system in v2.0 when I was trying to get it to work. While connected to nine of my 12 trees I was able to successfully define a System in v1.5.

I then renamed the systems.xml file and switched back to v2.0 but could not define a system (same error). I restored the systems.xml file and re-ran v2.0; it did not see a system and gives me the same error when I try to define one.

[Tedd]

I’m having a similar issue here with the “eDirectory Tree could not be set” error. I upgraded to 2.0 from my working 1.5 install and immediately received that error. We are in a multiple tree system as well.

I removed my System and have been attempting to recreate but receive the error every time after selecting my primary domain path, even after authenticating to my other domains.

[Tedd]

Renaming settings.xml did the trick. Thank you for the quick response.

Tedd

[Tedd]

Thanks–a reboot fixed this problem for me (Build 1.5.0.4).

Tedd

[Tedd]

I believe 1.5 fixed the issue for me, but it was quite a while ago and I’m not positive.

Another thing that’s helped me with indexing problems in the past is re-running GroupWise database checks (Structure + Index with fix, Contents with fix), then running another capture of the account.

[Tedd]

We are covered by upgrade protection, and I’ve had 1.5 downloaded for a few weeks, but do not have a password for the archive. Our reseller (Concentrico) seems to have disappeared, so I sent an email to your customer support a few days ago and am waiting for a reply.

I completed about ten more archives today, including one 3 GB archive, and Indexing worked fine every time. I will try 1.5 on this problem archive when I get access.

[Tedd]

There is no error, the index window just stops updating. I left it in this state overnight once to give it time to complete, but it was the same in the morning.

There are no error messages. Clicking the Stop button does nothing. I had to stop the process through Windows Task Manager.

The archive size is 7.9 GB. The hard disk has 29.8 GB of free space and is routinely defragmented.

The Indexer version is 1.2.0.0.

Thank you for your assistance!

[Tedd]

Yes, it fails when using both Local and Enterprise mode. When I switch the account to Full License both Local and Enterprise work.

This is a concern for us because we have over 3,500 Limited License accounts–and growing, since they’re quite a bit less expensive.

A Limited License account can be switched to Full License to allow Archive To Go to work, but even though it can be switched back to Limited License afterwards, for auditing purposes it remains a Full License mailbox and is over twice as expensive to license from Novell.

[Tedd]

I just want to be sure, when you say “locked account”, that you’re not referring to an account that is disabled or expired. I’m specifically inquiring about a GroupWise mailbox that is restricted to Limited License and can only be accessed with WebAccess, not with the full Windows GroupWise client. The alternative to Limited License is Full License, allowing access by either WebAccess or the Windows client.

[Author]

Replies