Through my infinite wisdom, I blew out the Queue, Printer Server, and
Printer objects of the original problem queue in NWADMIN and attempted to
recreate the stack with the quick setup wizard. I get an error message of
"The new object could not be created" with an error number of '104:-319'.
The Queue and Printer can be created fine manually, and now I cannot create
any print server. I run the printer OU with minimal licenses so I
transferred a 5 pack over and still am having issues.
Searching with Novell, Google, etc, I have turned up nothing. At some
point this year, I am making the move to iPrint/NDPS, but it needs to wait.
Any suggestions on the printer server issue, I plan on another reboot this
evening as a desperation move. Also, is there a way to reload print queues
without rebooting. I have search for loaded modules and pconsole does not
show up.
Any assitance is greatly appreciate.
Regards,
Matt Rigor
It is actually the PS that serves the queue :) Now, what kind of server are we
talking about? PSERVER.NLM or a jet-direct type server?
> Through my infinite wisdom, I blew out the Queue, Printer Server, and
> Printer objects of the original problem queue in NWADMIN and attempted to
> recreate the stack with the quick setup wizard. I get an error message of
> "The new object could not be created" with an error number of '104:-319'.
> The Queue and Printer can be created fine manually, and now I cannot create
> any print server. I run the printer OU with minimal licenses so I
> transferred a 5 pack over and still am having issues.
What happens when you try creating a Print server object?
> Searching with Novell, Google, etc, I have turned up nothing. At some
> point this year, I am making the move to iPrint/NDPS, but it needs to wait.
>
> Any suggestions on the printer server issue, I plan on another reboot this
> evening as a desperation move. Also, is there a way to reload print queues
> without rebooting. I have search for loaded modules and pconsole does not
> show up.
>
- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)
Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement
Using VA 5.51 build 315 on Windows 2000 build 2600
I believe it would be jet-direct, but how would I know for sure?
What happens when you try creating a Print server object?
It fails with the error message of
"The new object could not be created" with an error number of '104:-319'.
That is with selecting to create only the print server or using the quick
setup wizard.
How is the printer connected? Is PSERVER.NLM loaded?
> What happens when you try creating a Print server object?
>
> It fails with the error message of
> "The new object could not be created" with an error number of '104:-319'.
> That is with selecting to create only the print server or using the quick
> setup wizard.
rror: 319 -319 0xFFFFFEC1 = ERR_SYSTEM_ERROR
Not very helpful. I suggest running a full DS Health check as per:
http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=10060600&sliceId=&dialogID=28887592&stateId=1%200%201178552
If using Pserver, you can unload/load that separately without rebooting
the server.
If you have Jetdirect cards, do you have latest firmware on them?
-sk
> quick setup wizard
Suggest you give HP's JetAdmin/WebAdmin a try instead ..
--
Peter
eDirectory Rules!
(ssAegis powering up to 65% ...)
With that said, I can still not print to the printer specified via the
queue. I can print directly to the IP address, and newtare is enabled with
all frame types and the appropriate NDS information on the printer. To
test further, I deleted/created the same queue information and also created
a new queue stack with a different name, same results. The printer is an
IBM Infoprint, it and 2 other IBM Infoprints have been working fine for
years. For some reason, in the middle of a business day it just quit
printing from the queue. I have checked the Printer, Print Server, and
Queue configuration inside NWAdmin, being mindful of the Operator and Users
tabs and checking the configuration with the other queues that are known to
be working.
I access the print server via pserver on the console and it says the
printer status is 'not connected', but other print servers that are working
say the same thing.
I appreciate your assistance.
Regards,
Matt Rigor