#14 Unable to open Servers within the Windows console
Closed: wontfix None Opened 12 years ago by mkosek.

https://bugzilla.redhat.com/show_bug.cgi?id=752536

Description of problem:

I upgraded both my Directory Servers to 8.2.6 and since then I am unable to
connect to the servers using the windows tools

Version-Release number of selected component (if applicable):

Console Framework 1.1.5

How reproducible:

Each time

Steps to Reproduce:
1. Open 389 Console
2. Right click to expand the server
3. Right click to expand the Server Group

Actual results:

Results in a circle continually on the screen

Expected results:

I can open the actual server and administer it

Additional info:


C:\Program Files\389 Management Console>"java" "-Djava.library.path=." -cp
"./js
s4.jar;./ldapjdk.jar;./idm-console-base.jar;./idm-console-mcc.jar;./idm-console
-
mcc_en.jar;./idm-console-nmclf.jar;./idm-console-nmclf_en.jar;./389-console_en.
j
ar" -Djava.util.prefs.systemRoot=/.389-console
-Djava.util.prefs.userRoot=/.389-
console com.netscape.management.client.console.Console
Uncaught error fetching image:
java.lang.NullPointerException
        at java.io.FileInputStream.<init>(Unknown Source)
        at java.io.FileInputStream.<init>(Unknown Source)
        at sun.awt.image.FileImageSource.getDecoder(Unknown Source)
        at sun.awt.image.InputStreamImageSource.doFetch(Unknown Source)
        at sun.awt.image.ImageFetcher.fetchloop(Unknown Source)
        at sun.awt.image.ImageFetcher.run(Unknown Source)

Added initial screened field value.

Metadata Update from @nkinder:
- Issue assigned to rmeggins
- Issue set to the milestone: N/A

7 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/14

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)

3 years ago

Login to comment on this ticket.

Metadata