Table of Contents
Advertisement
4.12.1 Plug-In Studio Can't Find the RBS Collection When Trying to Install an Edited
Plug-In.
Plug-In Studio can't find RBS Collections that have special characters in their names, so attempting
to edit a plug-in that has been previously installed into an RBS Collection with special characters in
its name causes the install to fail.
4.12.2 Using Special Characters When Creating a Property Book
Creating a Property Book, and naming it using special characters might cause a DNS Error 603
message. For more information about naming a Property Book, see "Creating a New Property
Book" in the
iManager documentation (http://www.novell.com/documentation/imanager27/
imanager_admin_27/data/bypd8g8.html).
4.12.3 iManager Framework Does Not Support Special Characters in Plug-In IDs.
To create a plug-in ID that includes extended characters, create the plug-in using standard
characters, then use Advanced Properties to change the plug-in display name after it has been
created.
4.13 Two Instances Do Not Maintain Connections to Two
Different Trees
Two instances in Firefox and Internet Explorer 8 tabbed views do not maintain connections to two
different trees. Internet Explorer 6 maintains one session per instance, while Firefox uses the same
session for all instances that use the same profile.
This difference in Web browser behavior gives the appearance that Firefox cannot support two
different sessions and that connection information is crossing over. iManager can maintain a
connection to two different trees at the same time in the Firefox browser, but only if each instance is
using a different profile.
To work different sessions simultaneously, modify your profile using Firefox's
Profile Manager
(http://www.mozilla.org/support/firefox/profile). In Firefox 2.0 and 3.0, you can use the
-no-
option when launching Firefox to run multiple profiles simultaneously.
remote
4.14 javaw.exe Application Error when Closing iManager
Workstation or SDK
When closing iManager Workstation or SDK, you might encounter a
Application Error.
javaw.exe
The error is benign and does not indicate any system problems or instabilities. You can safely close
the error message box and continue working normally.
4.15 Control Characters in Login Script
Using ASCII control characters in a login script might cause an Unhandled Exception Error in
iManager. For this reason, Novell recommends using only the standard ASCII character set when
creating login scripts.
10
iManager 2.7.3 Field Patch (FTF) 4 Readme
Advertisement
Table of Contents
