unable to start LPD CLIENT

[EdgarZamora]

Jan,

Does this apply to you (especially the last part): (You might want to check your TCCPIP$LPD_SYSTARTUP file)

2.6.3.1 Preserving LPD Behavior (Alpha Systems)
When you install TCP/IP Services over an earlier version of the product, follow
the instructions displayed on your screen to preserve your edits in the LPD
startup and shutdown command procedures.
The following shows a sample screen display.
The following product will be installed to destination:
DEC AXPVMS TCPIP V5.1-9 DISK$ALPHASYS:[VMS$COMMON.]
UCX product already installed.
***********************************************************************
Another version of TCP/IP is installed. You must execute the following
three commands before continuing with this installation:
$ BACKUP SYS$COMMON:[SYSMGR]UCX$LPD_STARTUP.COM; -
SYS$COMMON:[SYSMGR]TCPIP$LPD_STARTUP.COM;
$ BACKUP SYS$COMMON:[SYSMGR]UCX$LPD_SHUTDOWN.COM; -
SYS$COMMON:[SYSMGR]TCPIP$LPD_SHUTDOWN.COM;
$ PRODUCT REMOVE UCX
***********************************************************************
2â 4 Installation, Configuration, and Startup Notes
Installation, Configuration, and Startup Notes
2.6 Removing Prior Versions of this Product
After you follow these instructions and complete the installation of TCP/IP
Services, your site-specific edits to the LPD startup and shutdown files are found
in:
SYS$COMMON:[SYSMGR]TCPIP$LPD_STARTUP.COM_OLD
SYS$COMMON:[SYSMGR]TCPIP$LPD_SHUTDOWN.COM_OLD
Now merge your site-specific edits into:
SYS$COMMON:[SYSMGR]TCPIP$LPD_SYSTARTUP.COM
SYS$COMMON:[SYSMGR]TCPIP$LPD_SYSHUTDOWN.COM
2.6.3.3 Merging Edits (Alpha and VAX Systems)
When you merge edits, do not include the commands to start and stop the queue
UCX$LPD_QUEUE. This queue has been replaced with TCPIP$LPD_QUEUE.
The commands for starting and stopping TCPIP$LPD_QUEUE are in the LPD
startup and shutdown command procedure files.
After you merge the edits, modify the value of the /PROCESSOR qualifier in the
LPD client queue startup commands that you have just appended, replacing
TCPIP$LPD_SMB with UCX$LPD_SMB. For example, enter the following
command:
LSE Command> SUBSTITUTE/ALL "ucx$lpd_smb" "tcpip$lpd_smb"

[Volker Halle]

Jan,

do you find the string 'LPD_CLIENT' or at least '_CLIENT' or 'CLIENT' in either:

SYS$SYSTEM:tcpip$lpd_utilities.exe
SYS$SHARE:TCPIP$LPD_SHR.EXE

in a context, which might be used as a parameter for the STARTFAIL or NOSERVREC error message ?

What does TCPIP SHOW VERS/ALL report for those 2 files ?

When did that system last get booted successfully (i.e. with correctly starting LPD queues) before 2-DEC-2007 ? What happenend since then ?

Volker.

[Wim Van den Wyngaert]

TCP 5.3 eco 2.
TCPIP$CONFIG.COM still has references to LPD_CLIENT.
But the service is not in our ena servi list. I tried to add it and it was accepted. I tried to enable the service and it failed (is not in the services list).

BTW : what a syntax. ucx set conf ena NOservi lpd_client

fwiw

Wim

[Volker Halle]

Jan,

in this thread, you have given 2 error messages:

%TCPIP-E-STARTFAIL, failed to start LPD_CLIENT
%TCPIP-E-NOSERVREC cannot find LPD_CLIENT service database record.

and later

Message number 07648312
= %TCPIP-E-FACNOTSTART, attempt made to run a TCPIP image before starting the facility

I'm assuming that the 2nd message is issued by TCPIP$LPD_UTILITIES, right ? If so, which image/procedure emits the first error message, the one explicitly referencing LPD_CLIENT ?

Volker.

[Jan van den Ende]

Volker,

The STARTFAIL and the NOSERVREC messages are right after one another in executing TCPITP$LPD_STARTUP

>>>
Message number 07648312
= %TCPIP-E-FACNOTSTART, attempt made to run a TCPIP image before starting the facility
<<<

is issued by START/QUEUEU

Proost.

Have one on me.

jpe

[Volker Halle]

Jan,

TCPIP$LPD_STARTUP.COM includes quite a couple of commands. Exactly which one is giving the STARTFAIL/NOSERVREC error ? Which image and which shareabale libraries are used by that image reporting the error ?

I would assume, that the string 'LPD_CLIENT' should somehow be stored in that image. The string 'LPD_CLIENT' must certainly be a parameter for these 2 error messages. Any piece of TCPIP V5.4 ECO 4 software, which would still be using the string 'LPD_CLIENT' would be very suspect.

There are still a couple of un-answered questions, please re-read my previous posts.

As nobody seems to yet have seen this error, the problem solution mainly depends on the quality of the information you're supplying.

Volker.

[Walter Miller_1]

Maybe it would be worthwhile running sys$manager:tcpip$config.com. When you select LPR/LPD configuration under the "Server Components" menu the procedure runs several checks including to be sure the service defined in SYSUAF, TCPIP$SERVICE database and that the application proxy is enabled.

You might want to disable then enable the service through the menu and let it do all the necessary checks.

[Jan van den Ende]

AAAARRGH!!!

Sea my original post:
>>>
I am sure that it will be too trivial to enter into a manual, but we are at a loss right now.
<<<

As trivial as removing PRINTCAP.

Generate a new one.

_NOW_ the service start up, just re-enter all wanted data.

So,

-- STARTING the service does some (which?) checks on structure of or syntax in PRINTCAP, and refuses to start of failure. Does not seem to do ANYTHING with that data.
-- START/QUEUE READs and USES the data, obviously without, or with much less stricct, caring about structre and/or syntax.

I would expect such inconsystencies in m$ware, and to a lesser extent in U*x, but where is the logic in that? Seen trough VMS-tinted glasses?

Anyway,
thanks all that have contributed. You were all as mis-guided as I was.

Proost.

Have one on me.

jpe

[Jan van den Ende]

See above.

Proost.

Have one on me.

jpe

[Jan van den Ende]

Re my post of 10:10:59 GMT

What clumsy typing!

I spotted so many errors, but I think (hope) you can get the meaning nonetheless.

I DO intend to spend some more effort in proof-reading in the future (but that is still no guarantee).

Proost.

Have one on me.

jpe