General discussion

Locked

NDPS broker trouble

By dpaff ·
Runnings NW6 with SP2. Have created broker & print manager using iManager. The broker appears to load properly from the server console but will not load from iManager under Manager Broker. When attempting to load broker from iManager I get the following error.

Exception saving broker information.

Yet I can load the broker from the server console. If I do I get the following errors when trying to manage the broker in iManager.

Under broker control I get:
Exception reading broker information
ccode=35073 (0x8901)

Under resource management I get:

Exception reading resource banners configuration
ccode=35073 (0x8901)

Exception reading resource print drivers configuration
ccode=35073 (0x8901)

Have tried uninstalling &reinstalling NDPS, deleting broker & print manager objects and creating new ones, restoreing the ndps directory on vol sys, deleting it and creating new directory when reinstalling ndps, nothing seems to work so I can't add drivers to the broker resource management. In NWAdmin32 I can add drivers from the system, but not from a file.

Help would be greatly appreciated.

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

NDPS broker trouble

by BudTheGrey In reply to NDPS broker trouble

I can't help much with iManager, but you might want to look at TIDs 10075015, 10078722 at http://support.novell.com/search

There were a couple issues with NDPS and NWADMN32.EXE (such as adding drivers) that go away if you make a short cut to NWADMN32, then modify it to add "/disabletls" (sans quotes) to the command line.

hth

Collapse -

NDPS broker trouble

by dpaff In reply to NDPS broker trouble

The question was auto-closed by TechRepublic

Collapse -

NDPS broker trouble

by matjaz.demsar In reply to NDPS broker trouble

Hello!
Maybe you should check if everything is ok with Tomcat server, which is used for iManager. sometimes this server performs "strangely" and needs to be restarted. I've seen this happen before and it was also connected with iPrint. All it needsis a restart...

Collapse -

NDPS broker trouble

by dpaff In reply to NDPS broker trouble

The question was auto-closed by TechRepublic

Collapse -

NDPS broker trouble

by dpaff In reply to NDPS broker trouble

This question was auto closed due to inactivity

Back to Networks Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums