Environment
Novell Client for Windows NT/2000/XP 4.90 Installation
Novell Client for Windows 2000/XP/2003 4.91 Installation
Microsoft Windows Server 2003
Novell Client for Windows 2000/XP/2003 4.91 Installation
Microsoft Windows Server 2003
Situation
Novell Client for Windows installation fails on server with ZENworks 6.x or 7.0 MiddleTier Server installed.
Error: "An unknown error 0x00000001 (1) occurred while installing: Novell Client for Windows" is reported by the Novell Client Installation program (SETUPNW.EXE).
Error: "An unknown error 0x00000001 (1) occurred while installing: Novell Client for Windows" is reported by the Novell Client Installation program (SETUPNW.EXE).
Resolution
Resolved in Novell Client 4.91 SP4 for Windows XP/2003
Install the current version of the Novell Client for Windows XP/2003
Additional Information
The Novell XTier 2.6.x services include an NSNSNT.SYS kernel-mode driver that is installed with a descriptive display name of "Novell Simple Naming Services". The Novell Client for Windows includes a driver, NWSNS.SYS, which is also installed with a display name of "Novell Simple Naming Services".
The manner in which ZENworks MiddleTier Server installation registers its services does not encounter or fail due to this duplication when the Novell Client for Windows is already present on the machine where ZENworks MiddleTier Server is being installed. (And, given that the descriptive display name is not visible even in the Services control panel, no real reason that that it should fail, either. The description text, though duplicated, is largely benign.)
When the Novell Client for Windows is being installed with a ZENworks MiddleTier Server using XTier 2.6.x is already present, the Windows Server 2003 SETUPAPI processing of the Novell Client for Windows' .INF does check for the presence of duplicate service description text and will fail the installation attempt when detected.
The Novell XTier 3.1.4 and later services that implement ZENworks MiddleTier Server 7.0.1 and later do not employ a "NSNSNT" service nor register any service with the display name "Novell Simple Naming Services". Therefore the issue does not occur when installing the Novell Client on a Windows Server that already has ZENworks MiddleTier Server 7.0.1 or later installed.
Note that on Windows 2000 Server, the Windows SETUPAPI processing does not fail the installation due to the presence of duplicate display name descriptions. Also note that on Windows Server 2003, this issue only occurs during the new, first-time installations of the Novell Client for Windows. Subsequent updates of the Novell Client for Windows do not re-experience the issue, unless the Novell Client for Windows is first uninstalled from the Windows Server 2003 machine such that a new installation is being performed again.
The manner in which ZENworks MiddleTier Server installation registers its services does not encounter or fail due to this duplication when the Novell Client for Windows is already present on the machine where ZENworks MiddleTier Server is being installed. (And, given that the descriptive display name is not visible even in the Services control panel, no real reason that that it should fail, either. The description text, though duplicated, is largely benign.)
When the Novell Client for Windows is being installed with a ZENworks MiddleTier Server using XTier 2.6.x is already present, the Windows Server 2003 SETUPAPI processing of the Novell Client for Windows' .INF does check for the presence of duplicate service description text and will fail the installation attempt when detected.
The Novell XTier 3.1.4 and later services that implement ZENworks MiddleTier Server 7.0.1 and later do not employ a "NSNSNT" service nor register any service with the display name "Novell Simple Naming Services". Therefore the issue does not occur when installing the Novell Client on a Windows Server that already has ZENworks MiddleTier Server 7.0.1 or later installed.
Note that on Windows 2000 Server, the Windows SETUPAPI processing does not fail the installation due to the presence of duplicate display name descriptions. Also note that on Windows Server 2003, this issue only occurs during the new, first-time installations of the Novell Client for Windows. Subsequent updates of the Novell Client for Windows do not re-experience the issue, unless the Novell Client for Windows is first uninstalled from the Windows Server 2003 machine such that a new installation is being performed again.