|
HP OpenVMS Systemsask the wizard |
|
The Question is:
I have just installed Advanced Server from the OpenVMS 7.2-1 CD on one of our
DS10 Alphas.
The whole installation ran without any problems.
Advanced Server was configures and was set up as a BDC in our NT domain. I
could create an account for the new system ALPHA1.
Advanced Server seems to start up without problems.
After the Alpha was rebooted, the Alpha lost the connection to the NT domain
and I don't seem to be able to get it back. At that time I changed the
security model from Advanced Server only to Advanced Server and OpenVMS
because people could log in under O
penVMS with the other setting.
If I try to give any command in the Administrator, I get a error like this:
ALPHA1$ administrator
GALLUP_DENMARK\\ALPHA1> sh share
%PWRK-E-ERRGETSRV, error getting server information for "ALPHA1"
-LM-E-ERROR_BAD_NETPA, the network path cannot be located
GALLUP_DENMARK\\ALPHA1>
TCPIP is up and running.
ALPHA1$ @sys$update:pwrk$config
Advanced Server V7.2A for OpenVMS Configuration Procedure
Shutting down the currently running server(s)...
The Advanced Server stores and accesses the following
types of data files:
o Configuration parameter files
o License server data files
o Log files
o Printer spool files
o Virtual memory section files
You can specify any existing OpenVMS disk device that has at least
5000 free blocks of disk space to store these data files.
Note: The server frequently accesses the data files stored on the
disk. If these files are stored on the system disk, it can degrade
the performance of both the OpenVMS system and the server. Therefore,
Digital recommends that you specify a disk other than the system disk.
Press RETURN to continue:
If this OpenVMS cluster has multiple system disks, make sure that all
nodes on which you plan to run the Advanced Server:
o Use the same disk device to store and access Advanced Server
data files.
o Share the same SYSUAF.DAT file. In each system disk's startup file,
define a system logical name that points all nodes to the shared
SYSUAF.DAT file. For example:
$ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat
The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM
The Advanced Server directory tree already exists on ALPHA1$DKB600:.
If you specify a different disk device, the Advanced Server directory
tree will be moved to the new device.
Enter disk device name where the Advanced Server data files will be stored
[ALPHA1$DKB600:]:
Checking to see if OpenVMS Registry Services are available...
The OpenVMS Registry server is already started on this node.
Populating OpenVMS Registry with required Advanced Server & NT parameters...
Please wait, this may take one to two minutes to complete ...
Required OpenVMS Registry file server keys and values have been created.
Verifying SAM database files...
Copying client files to Advanced Server directory tree...
Changing the server configuration parameters will allow you to modify
this server's client capacity and select the transports to be used.
ALPHA1 is currently configured to
+ support 30 PC clients
+ use the following transport(s): NetBEUI, TCP/IP
If you want this server to be the primary domain controller, you should
configure it to use all the transports used by any of the backup servers
in the domain.
If you want this server to be a backup domain controller, you should
configure it to have at least one transport in common with the domain's
primary domain controller, otherwise this configuration will fail.
If you do not change the configuration parameters now, you may do so
later by typing ADMIN/CONFIG.
Do you want to change the server configuration parameters now? [YES]:
The OpenVMS Registry server is already started on this node.
Reading current configuration parameters ...
Your Advanced Server for OpenVMS is presently configured to run as follows:
1. Run the license server: YES
2. Enable Timesource service: YES
3. Enable Alerter service: YES
3a. Alert user names: Administrator
4. Enable Netlogon service: YES
5. Advanced Server domain: GALLUP_DENMARK
6. Advanced Server role: BACKUP
7. Advanced Server computer name: ALPHA1
7a. Advanced Server OpenVMS cluster alias: ALPHA1
8. Server announce comment: Advanced Server V7.2A for OpenVMS
Enter item number, or RETURN to use these values [DONE]:
Do you want to start the Advanced Server V7.2A on node ALPHA1 now [YES]:
The file server will use NetBEUI, TCP/IP.
The license server will use DECnet, NetBEUI, TCP/IP.
Advanced Server mail notification will use DECnet.
Process NETBIOS created with identification 204002F9
Process PWRK$NBDAEMON created with identification 204002FB
Process PWRK$KNBDAEMON created with identification 204002FD
Process PWRK$LICENSE_R created with identification 204002FF
Process PWRK$LICENSE_S created with identification 20400301
Checking to see if OpenVMS Registry Services are available...
The OpenVMS Registry server is already started on this node.
The Advanced Server is configured to support 30 PC clients.
Process PWRK$MASTER created with identification 20400304
The master process will now start all other Advanced Server processes.
ALPHA1$
ALPHA1$ sh sys
OpenVMS V7.2-1 on node ALPHA1 26-MAY-2000 16:07:49.07 Uptime 1 07:18:12
Pid Process Name State Pri I/O CPU Page flts Pages
20400201 SWAPPER HIB 16 0 0 00:00:02.08 0 0
20400206 CLUSTER_SERVER HIB 14 39 0 00:00:00.03 58 71
20400207 CONFIGURE HIB 10 19 0 00:00:00.03 39 24
20400208 LANACP HIB 13 85 0 00:00:00.02 117 153
2040020A IPCACP HIB 10 10 0 00:00:00.00 31 43
2040020B ERRFMT HIB 8 3701 0 00:00:00.97 87 101
2040020C CACHE_SERVER HIB 16 3 0 00:00:00.00 25 35
2040020D OPCOM HIB 7 10001 0 00:00:01.77 106 37
2040020E AUDIT_SERVER HIB 10 181 0 00:00:00.06 139 169
2040020F JOB_CONTROL HIB 10 371 0 00:00:00.14 61 83
20400210 SECURITY_SERVER HIB 10 557 0 00:00:00.56 451 282
20400211 DNS$ADVER LEF 5 12355 0 00:00:01.97 723 454
20400212 LES$ACP_V30 HIB 8 128 0 00:00:00.07 74 86
20400213 NET$ACP HIB 4 76 0 00:00:00.04 131 152
20400214 REMACP HIB 8 10 0 00:00:00.00 29 16
20400215 NET$EVD HIB 6 20 0 00:00:34.68 357 208
20400216 DTSS$CLERK LEF 12 2108 0 00:00:00.54 170 150
20400217 NET$MOP HIB 6 34 0 00:00:00.13 253 147
20400218 SMISERVER HIB 9 42 0 00:00:00.02 150 147
20400219 TP_SERVER HIB 10 7616 0 00:00:05.73 74 96
2040021A SMHANDLER HIB 6 50 0 00:00:00.02 158 141
2040021B TNT_SERVER HIB 6 1099 0 00:00:15.87 741 969
2040021C TNT12040021B LEF 2 37 0 00:00:00.04 594 348 S
2040021D TCPIP$INET_ACP HIB 10 364 0 00:00:00.04 258 147
2040021E SMTP_ALPHA1_01 HIB 5 111 0 00:00:00.06 335 81
2040021F TCPIP$PWIP_ACP HIB 10 79 0 00:00:00.01 126 148
20400221 TCPIP$ESNMP LEF 9 11872 0 00:00:00.14 270 204
20400222 TCPIP$OS_MIBS LEF 8 22702 0 00:00:00.56 197 184
20400224 LATACP HIB 14 8 0 00:00:00.00 74 59
20400227 DECW$SERVER_0 HIB 8 847 0 00:00:00.39 854 894
20400228 DTLOGIN LEF 5 147 0 00:00:00.07 398 195
20400229 DTGREET LEF 4 459 0 00:00:00.66 561 420 S
2040022A REGISTRY_SERVER HIB 10 1194 0 00:00:26.45 847 495 M
204002CD KRISTIAN LEF 9 56974 0 00:01:00.78 70356 307
204002E4 JAN LEF 4 2170 0 00:00:00.63 2290 91
204002E6 SYSTEM CUR 4 10066 0 00:00:05.67 23626 147
204002EF UNAN LEF 4 471 0 00:00:00.30 1481 87
204002F9 NETBIOS HIB 5 61 0 00:00:00.02 62 76
204002FB PWRK$NBDAEMON HIB 11 44 0 00:00:00.04 121 145
204002FD PWRK$KNBDAEMON HIB 11 80 0 00:00:00.05 255 288
204002FF PWRK$LICENSE_R HIB 11 169 0 00:00:00.04 447 312
20400301 PWRK$LICENSE_S HIB 6 212 0 00:00:00.16 689 203
20400304 PWRK$MASTER HIB 6 249 0 00:00:00.09 374 102
20400308 PWRK$MONITOR HIB 6 75 0 00:00:00.06 495 132
Thank you.
The Answer is :
Please see this part of the PIPE SHOW SYSTEM | SEARCH SYS$PIPE PWRK$
command display:
204002FB PWRK$NBDAEMON HIB 11 44 0 00:00:00.04 121 145
204002FD PWRK$KNBDAEMON HIB 11 80 0 00:00:00.05 255 288
204002FF PWRK$LICENSE_R HIB 11 169 0 00:00:00.04 447 312
20400301 PWRK$LICENSE_S HIB 6 212 0 00:00:00.16 689 203
20400304 PWRK$MASTER HIB 6 249 0 00:00:00.09 374 102
20400308 PWRK$MONITOR HIB 6 75 0 00:00:00.06 495 132
You are missing the PWRK$LMSRV, PWRK$LMBROWSER, and PWRK$LMMCP processes.
Something is clearly failing, and causing problems for these three
processes. Look in the PWRK$LMLOGS area for the files PWRK$LMSRV_node.log,
PWRK$LMMCP_node.log, one of these files can potentially contain some
interesting information related to the error(s). These messages might
give you a hint as to the cause.
If you are unable to resolve the problem based on the log files, then
please contact the Compaq Customer Support Center directly, as additional
information will be required, Please be sure to preserve the contents
of the failing logs, as this information will likely be required for
resolution.
|