Possible Cause: A newer version of the file already exists on the server.

Action: Select Never Overwrite Newer Files.

Possible Cause: Error opening destination file. The file might be in use by another process.

Explanation: Close any other process that might be using the file and retry. If you still get the error, note the name of the file along with the complete path, and skip copying the file.

After installation, search for the file on the product CD and copy it to the destination location.

Possible Cause: Firewall schema extension failed.

Action: Run schext.nlm at server prompt:schext FDN_of_user password . For example, schext.cn=admin.o=novell border12.

Explanation: User should have admin or admin equivalent rights. If Schext shows as already loaded, unload it and run the Schext again. If it cannot be unloaded, restart server and run Schext.

Possible Cause: FILTSRV/BRDCFG is already loaded

Action: Restart the server and run load FILTSRV migrate. (If filtsrv is already loaded, unload filtsrv. After migrating filtsrv, unload filtsrv and, load filtsrv again.)

Explanation: The server was not restarted after a previous installation.

Possible Cause: Unavailability of one or more of the following NMAS™ methods:

Action: Run NMASInst.nlm manually after the install.: NMASInst -addmethod user_DN admin_password config_file_path .

Here the configFilePath is the full path of the file config.txt present in the corresponding NMAS method folder.

These files are copied to the sys:\SYSTEM\nds8temp\products\ nmasmthd folder. For example, if you want to install the CertMutual method, your command will look like: NMASInst -addmethod admin.org mypassword sys:\SYSTEM\nds8temp\ products\nmasmthd\CertMutual\config.txt

Explanation: View the sys:\etc\nmas\nmasinst.log for status and details.

If you find that the files or directories in sys:\SYSTEM\nds8temp\ products\nmasmthd\NMAS_Method are empty, copy them from the product CD from the location Nmas_EE\NmasMethods\Novell\NMAS Method

For more details on NMAS documentation see the NMAS Documentation

Possible Cause: Could be any one of the following:

Action: Run the standalone Cache Volume Creation Utility provided in the Unsupported folder of the product CD, and then write the information to eDirectory.

If writing the Cache Volume Information to eDirectory fails, do the following:

Explanation: If volume creation failed but partition was created, delete the partition using the NSS Management Utility before running the tool. To do this, run nssmu on the server console, select the traditional partition created, then delete it.

Possible Cause: This is skipped if iManager 2.6 is not installed, or if the option is deselected by the user.

For the cause of the failure, see sys :\ni\data\ nioutput.txt under the heading Exception at VPN Plugin Install.

Action: Install the bmacl.npm, bmpxy.npm, bm.npm (for firewall), and vpn.npm (for VPN) modules from iManager. To do this,

Explanation: The bmacl.npm, bmpxy.npm, bm.npm, and vpn.npm modules can be found on the product CD.

Possible Cause: Making the interface public

Action: At the server console, type filtcfg > Select Configure Interface Options > Make the interfaces public or private as you want.

Possible Cause: Setting default filters

Action: Run brdcfg.nlm

Possible Cause: Enabling Packet Filtering

Action: Run INETCFG from the server console, then select Enable TCP/IP filtering support > Reinitialize System. You can configure filters using FILTCFG.

Possible Cause: Adding Filter Exceptions for VPN Services failed during an upgrade. This could happen because of the following conditions:

Action: Run brdcfg.nlm after the install is over and follow the on-screen instructions.

Possible Cause: Any one of the following

Action: Launch NWAdmin to do the configuration.

Double-click the NCP Server Object > Select BorderManager Setup, then configure the parameters.

If NWAdmin crashes on launch, delete the BRDSRVS:xxx attributes on the NCP server object representing the server.

Explanation: The following are some of the attributes of the NCP Server Object added by the Install:

BRDSRVS: Access Control Flag

BRDSRVS: Component Enable Flag

BRDSRVS: Event Logging

BRDSRVS: Gateway Port Number

BRDSRVS: Timestamp

BRDSRVS: private addr list

BRDSRVS: proxy parameters

BRDSRVS: public addr list,fwsAction,fwsExceptionList, FwsFilterList, fwsInterfaceList, fwsStatus.Objects added to eDirectory: NBMRuleContainer, <NCP Server Object> -GW.

Action: Use iManager to install licenses.

Explanation: Novell BorderManager 3.9 services do not work if licenses are not installed. Trial Licenses are obtained at the root of the product CD under l icenses\trial and regular (production) licenses are licenses\regular.