Cannot Define System – Primary Domain On Linux

[tjackson]

I’m not sure if this is an A2Go v2 problem but after removing 1.5 and installing 2.0, I cannot seem to use Enterprise mode because I am unable to define a system. On XP, the application hangs when clicking on the “Define” link. On Windows 7 after I browse to the domain path (Samba share), I get an error message with a lot of output. The first line mentions that “there were problems while trying to use Creator, Please check the following error messages.” Looking through the output, the thing that stands out to me is is a COMException – eDirectory Tree could not be set error.

The primary domain directory is shared via Samba and I am logged in as a user with full rights.

Thanks,
Tim

Topic

[Support 1]

Thanks for reporting these problems.

>On XP, the application hangs when clicking on the “Define” link.

Unfortunately I am not sure what might cause this. Which version of the Microsoft Framework for .NET is installed on the workstation?

I believe that the problem with setting the domain path is most probably caused by the sharing configuration from Linux to Windows. You are likely to see the same behavior with versions 1.5 and 2.0. Another customer wrote the following:

quote:

---

Here is my environment.
– Only one NDS tree and Only one GroupWise server
– Netware client 4.91 sp5 installed
– GroupWise Client 7.03 is installed
– Groupwise 7.03 server is running on Linux OES1
– Mail is shared by Samba to Windows 2003 server for running Archive To Go.
– User account have read/write permission on this share and the domain directory

---

This customer was unable to create a GroupWise system definition with Archive To Go Creator. Here is how the customer resolved the problem:

quote:

---

I need to move gwdomain folder to the NSS volume and create a symbolic link. (Before I moved to NSS, Gwdomain was located in linux partition and created a samba share) Novell client causes Windows to lookup the UNC path on NCP share first, then samba.

The samba share does not work in OES.

We don’t have this problem if GroupWise is installed SLES9 or SLES10.

---

I hope this helps you. Please let me know how you go.

Regards,
Advansys Support

[This message was edited by Support 1 on June 03, 2010 at 05:21 PM.]

[tjackson]

Although similar, I don’t think our problem is the same. Come to find out, defining the system in XP just took awhile for the new window to open. Once opened, it received the same error after defining the path to the domain as I did on Windows 7.

To rule out any Novell client interference, I have A2Go installed on Windows XP SP2 with only GW Client v8, .net 2.0. It has a mapped drive to the Primary Domain (SLES11 no OES) shared via Samba. The logged in user has full rights to the domain directory.

I no longer get the error message described earlier, however now when I browse to the domain folder it says “This is not a primary domain path”.

Has A2GO been tested against a Samba share on Linux?

[Support 1]

Thanks for the additional information.

>To rule out any Novell client interference

Could you elaborate on what you mean by the above? You do need the Novell Client installed for the GroupWise Admin API (that Archive To Go uses) to operate correctly.

>The logged in user has full rights to the domain directory.

From a quick look at the Novell Communities, this post indicates that incorrect Samba group Read and Write permissions can result in administration issues.

I have confirmed that the error ‘This is not a primary domain path.’ was reported by the customer mentioned previously. No other error was reported. I think it’s very likely this is due to the Samba share on Linux. Unfortunately we cannot offer specific advice on how to reconfigure this share; we have not tested Archive To Go in this environment. Archive To Go is a GroupWise Windows client based solution which uses the GroupWise client Object and Admin APIs to access the GroupWise server. Apart from any difference in potential rights allocation and folder access methods between the different operating environments for administering GroupWise, Archive To Go’s operation is independent of the GroupWise server’s operating system.

For reference, if your GroupWise system consists of several eDirectory Trees, you will need to log into all trees before attempting system discovery. Archive To Go Creator uses system discovery to list the GroupWise Post Office objects to help you create a system definition. Not logging into all Trees is a known cause of error ‘eDirectory Tree could not be set’. In this circumstance, in the Novell Client Connections dialog, it is also recommended that you set the GroupWise system to be the Primary system connection.

If the problem persists, testing your environment may be a little quicker by using our stand-alone GroupWise System Discovery utility, which attempts an administrative GroupWise system login and discovery of all domain and post office objects. If there is a rights issue or folder access problem, the utility will still log a similar error because it uses the same technique as Archive To Go. The utility is available from:

http://support.advansyscorp.com/utilities/groupwise-system-discovery.zip

After downloading, double-click the MSI file to install GroupWise System Discovery. Operation should be straightforward. Given the appropriate connection information and access rights, it will attempt to connect to your GroupWise system and identify the Domain and Post Office objects. It will not attempt to list or access User objects. It should create a log file which you can return to us via email (click the “Create email…” button and use support@advansyscorp.com).

Regards,
Advansys Support

[This message was edited by Support 2 on June 06, 2010 at 08:11 PM.]

[tjackson]

Thanks for your help. One of my post offices is in a separate tree. Once I logged in to that one as well, it allowed me to define the system and all is working well. It seems that A2GO needs access to all of the servers in the system at the time of system definition, not just the primary domain.

[Support 2]

Thank you for the update and good news. It appears to confirm that successful system discovery in a distributed system topology requires access to all GroupWise system components.

Thanks again for letting us know. We will review this scenario again at our next engineering meeting and see if there is another approach which could better assist users experiencing this problem.

Regards,

Advansys Support

[clement]

Hi Support,

After reading this thread I have discovered that this is the reason that I can no longer define the system using ver. 2.0. We have approx. 170 domains in different e-dir trees all over the world. Some of them are in very remote hard to communicate with locations. Simultaneous connection to each domain/tree is not practical let alone entirely possible.
Is there another way that I would be able to define my system?

TIA,
Sue

[Support 2]

While we will double-check with our project engineers, we are not aware that the authentication mechanism has changed in 2.0. Normally the discovery process of the GroupWise system is handled by the GroupWise Admin API and Novell Client services we call from the Archive To Go code.

Can you confirm that you able to define a new system using Archive To Go 1.5?

Has anything else potentially relevant changed in your environment, such as GroupWise client version, Operating System etc, apart from the upgrade to Archive To Go 2.0?

Thanks in advance for the additional information.

Kind Regards,

Advansys Support

[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.

[Support 1]

Thanks for reporting this.

Please provide a description of your eDirectory topology, eg. total Trees, total Domains, total external Domains. Are any Domains distributed across multiple Trees? If you prefer, send your response to support@advansyscorp.com.

After successful creation of a system definition, Archive To Go Creator caches the definition. This is important because it avoids the need to do system discovery every time you use Creator. Both versions 1.5 and 2.0 will cache any system definitions.

Please follow the directions below, for doing a ‘clean’ test with Creator 1.5.

• Use Windows File Explorer to navigate to the folder below:

  C:Documents and Settings[Windows User Name]Application DataAdvansysArchive To Go

• If this folder contains the file ‘systems.xml’, rename it as something else, eg. ‘systems.bak’.
• If 2.0 is installed, uninstall it. Install Archive To Go 1.5.
• Run Archive To Go Creator 1.5. You should see that no system is defined. Try to create a new system definition. What results do you
  get?
• If you do not wish to retain the test system definition created at step 4, delete ‘systems.xml’ and restore the original name of ‘systems.bak’ (steps 1 and 2). Otherwise, you may delete ‘systems.bak’.

I look forward to your reply.

Regards,
Advansys Support

[This message was edited by Support 1 on June 29, 2010 at 07:18 PM.]

[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.

[Support 1]

Tedd,

Many thanks for your detailed description; this is very helpful. Our engineers are now investigating this behavior with A2G v2.0.

In the meantime, please test your environment by using our stand-alone GroupWise System Discovery utility, which attempts an administrative GroupWise system login and discovery of all domain and post office objects. If there is a rights issue or folder access problem, the utility should still log a similar error because it uses the same technique as Archive To Go. Like A2G v1.x, the utility was built for .NET 1.1; if the utility fails to reproduce the problem we may need to provide you with a .NET 2.0 build for comparison.

The utility is available from:

http://support.advansyscorp.com/utilities/groupwise-system-discovery.zip

After downloading, double-click the MSI file to install. Operation should be straightforward. Given the appropriate connection information and access rights, it will attempt to connect to your GroupWise system and identify the Domain and Post Office objects. It will not attempt to list or access User objects. It should create a log file which you can return to us via email (click the “Create email…” button and use support@advansyscorp.com).

In addition, you may be able to get v2.0 to use the system defined with v1.5, as follows:

• Ensure that ‘systems.xml’ is available and not renamed to something else. This is the cache file for system definitions created by Creator 1.x.
• Navigate to the folder below:

  C:Documents and SettingsAll UsersApplication DataAdvansysArchive To Go

• If this folder contains the file ‘a2go‑config.bin’, rename it as something else, eg. ‘a2go‑config.bak’.
• If Archive To Go 2.0 is installed, re‑run the installer for it and choose the Repair option. If it is not installed, run it as a normal installation.

  This should replace ‘a2go‑config.bin’ by a copy with the default settings.

• Run Archive To Go Creator 2.0, which should migrate the settings in your ‘systems.xml’ and ‘settings.xml’ files. You should see the system defined using Creator 1.5. Try to archive one or multiple accounts. What results do you get?

Regards,
Advansys Support

[This message was edited by Support 1 on June 30, 2010 at 08:44 PM.]

[chapindad]

I had the same problem. I had to login into both my trees before I was able to access my system.

This was not a problem under 1.5.

[Support 1]

Thanks for letting us know.

We have confirmed this is caused by a defect in Creator 2.0. For the moment the available workarounds are:

– Log into all eDirectory Trees.
– Migrate the system definition created with Creator 1.5 as described in my post on June 30th.

We are in the final stage of testing an update that fixes this defect; the update will be available within a few days.

Regards,
Advansys Support

[Author]

Replies