|
HP OpenVMS Systems Documentation |
|
Compaq PATHWORKS V6.1 for OpenVMS (Advanced
Server)
|
| Previous | Contents |
This section describes problems with the Browser service corrected in
PATHWORKS V6.0C-ECO2 for OpenVMS (Advanced Server) and PATHWORKS V6.0D for OpenVMS (Advanced Server).
5.6.1 Browser Fails to List Entire List of Servers or Domains
Problem:
In large domains, or in networks with many domains, clients using an Advanced Server backup Browser do not receive the complete list of the servers or domains.
Solution:
This problem is resolved in PATHWORKS V6.0C-ECO2 for OpenVMS (Advanced Server) and PATHWORKS V6.0D for OpenVMS (Advanced Server).
This chapter describes problems resolved by software changes made in PATHWORKS V6.1 for OpenVMS (Advanced Server). These software changes will also be included in future ECOs. The problems are described in the sections indicated in the following table:
This section describes the file server problems corrected in
PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.1.1 Files Created by Windows 95 or Windows 98 Clients Have Wrong Timestamp
Problem:
Files created from Windows 95 and Windows 98 clients in shared directories are given incorrect timestamps for their creation date. When viewing file properties, the time displayed for the creation date would be off by one or more hours, depending on the timezone of the server.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.1.2 Advanced Server Hangs and Logs "Server allocating 10 more queue elements" Messages
Problem:
The Advanced Server hangs because it is attempting to process multiple VFC files at the same time. The PWRK$LMSRV log file records several "Server allocating 10 more queue elements" messages and a message indicating that the data cache is saturated and should be increased in size.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.1.3 Server Crashes with ACCVIO in Routine FIDGetCache
Problem:
The server might crash with an access violation (ACCVIO) in module ODS2$FIDCACHE, routine FIDGetCache. Error messages and a traceback similar to the following would be seen in the PWRK$LMSRV log file:
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000010 %TRACE-F-TRACEBACK, symbolic stack dump follows image module routine line rel PC PWRK$FSLIB_ODS2 ODS2$FIDCACHE FIDGetCache 32276 ...01C94 PWRK$FSLIB_ODS2 ODS2$FIDCACHE ODS2GetFIDCache 33962 ...06714 PWRK$FSLIB_ODS2 ODS2$FILE ODS2LookupFile 30532 ...00DC8 PWRK$FSLIB_ODS2 ODS2$FILELIB ODS2GetDirectory 27678 ...00AF4 PWRK$FSLIB_ODS2 ODS2$FILE ODS2LookupPath 30408 ...00AB0 PWRK$FSLIB_ODS2 ODS2$FILE ODS2LookupFile 30506 ...00D2C PWRK$FSLIB_ODS2 ODS2$LIB ODS2Stat 34009 ...02AEC |
In addition, the log file would contain many informational messages from the FID cache and ThreadLock/Unlock routines.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server). The crash and the extraneous
informational messages should no longer occur.
6.1.4 Numerous Locks on a Resource Accumulate, Causing PWRK$LMSRV or the System to Crash
Problem:
The PWRK$LMSRV process might gradually become overloaded with multiple locks on a single resource, causing the system enqueue limit quota (ENQLM) to be exceeded. As a result, either the PWRK$LMSRV process might crash or an OpenVMS lock manager problem might cause the system to crash. The locks have a name beginning with "PWRK$om", such as PWRK$om_0093EA0002000100.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.1.5 PWRK$LMSRV Crashes with ODS2ReadRMS Errors
Problem:
The PWRK$LMSRV process crashes with the following error messages in the PWRK$LMSRV log file previous to the crash:
ODS2ReadRMS: failed to rewind file, status 000000 ODS2ReadRMS: failed to get record, status [various RMS codes] |
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.1.6 PWRK$LMSRV Crashes with Access Violation in Module ODS2$LIB
Problem:
The PWRK$LMSRV process might crash with an access violation in the module ODS2$LIB, in routine ODS2NewASUSecurityAce. Error messages and a traceback similar to the following would be seen in the PWRK$LMSRV log file:
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=0000000006FDC004, PC=FFFFFFFF808BF9A4, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine . . . rel PC abs PC
FFFFFFFF808BF9A4 FFFFFFFF808BF9A4
PWRK$FSLIB_ODS2 ODS2$LIB ODS2NewASUSecurityAce
00000000000026AC 0000000000C2D0DC
PWRK$FSLIB_ODS2 ODS2$LIB ODS2SetASUSecurity
000000000000294C 0000000000C2D37C
PWRK$FSLIB_ODS2 ODS2$OPS ODS2_setsecurity
00000000000117C0 0000000000BF97C0
.
.
.
|
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.1.7 PWRK$Monitor Crashes While Attempting to Output an OpenVMS Error Message (932)
Problem:
The PWRK$MONITOR process might crash in module cmtsvrmonsys while writing out a dump file and attempting to include an OpenVMS error message (status code 932). The log file will include the following information:
29-MAY-2001 13:32:47.73 21200233:00243DD8 PFS_CACHE_IMAGE : PWRK$PCMSHR 1-JUN-2001 11:07:48.17 21200233:002481E8 In module <cmtsvrmonsys>, in function <MonitorServer> 1-JUN-2001 11:07:48.29 21200233:002481E8 Message Text: Error returned from sys$getjpi() 1-JUN-2001 11:07:48.30 21200233:002481E8 Status Code: 932 . . . |
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.1.8 Partial Synchronizations Require Excessive Time to Complete
Problem:
When the Advanced Server is the primary domain controller (PDC), partial synchronizations that require more than one update message to be sent from the PDC to the BDC might take an inordinate amount of time to complete.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.1.9 "release_secure_channel_lock failed" Error in Server Log and 5716 Event in Event Log
Problem:
Multiple users of the secure communication channel that is formed between a BDC and its PDC arbitrate for the channel using an OpenVMS lock. In previous versions of the Advanced Server, the arbitration did not always work successfully, and the channel would break temporarily.
Two side effects of this include:
"release_secure_channel_lock failed, R0 status = 00002124" |
I 11/21/00 02:32:14 PM NETLOGON None 5717 N/A MOLD I 11/21/00 02:32:12 PM NETLOGON None 5715 N/A MOLD W 11/21/00 02:31:09 PM NETLOGON None 5716 N/A MOLD I 11/21/00 02:31:08 PM NETLOGON None 5715 N/A MOLD |
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.2 File Access/Printing Problems
This section describes file access and printing problems corrected in
PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.2.1 Certain Applications Might Fail When Attempting to Display Files on ODS-5 Disk Volumes
Problem:
Certain MS-DOS applications attempting to enumerate files in an Advanced Server share directory residing on an ODS-5 volume will fail if the file names are in lowercase. These same applications work fine on an ODS-2 volume.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.3 ADMINISTER Command Problems
This section describes ADMINISTER command problems corrected in
PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.3.1 The Password of a Newly Created Account Is Not Expired by Default
Problem:
By default, a user account is created with an expired password. The user must enter a new password at first logon. (To remove the need for users to reset their passwords at first logon, use the /FLAGS=(NOPWDEXPIRED) qualifier with the ADD USER command.) However, version V6.0C-ECO1 of the PATHWORKS Advanced Server is not setting the password of a newly created account as expired. Thus, when first logging in, a new user would not have to reset the account password, as expected.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.3.2 ADMIN/ANALYZE Command Loops with Error Messages
Problem:
When a non-privileged user invokes the ADMINISTER/ANALYZE command, an error message will be displayed repeatedly until the user presses [CTRL/C] to cancel the command. The following example shows the repeated error message that might be seen:
$ ADMIN/ANA/SINCE
:::::::::: PATHWORKS Error Log Report ::::::::::
DATE: 21-SEP-2001 16:01:51.33
PCSLVB\acquire_lvb_lock: unexpected VMS status error! (000028F4)
PCSLVB\acquire_lvb_lock: unexpected VMS status error! (000028F4)
PCSLVB\acquire_lvb_lock: unexpected VMS status error! (000028F4)
PCSLVB\acquire_lvb_lock: unexpected VMS status error! (000028F4)
.
.
.
|
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.3.3 Administrator Cannot Take File Ownership
Problem:
Once all permissions are removed from a shared directory, an administrator, using the ADMINISTER TAKE FILE OWNERSHIP command, is not able to take ownership of the directory or of files in the directory. No messages are displayed. However, if the administrator uses the SHOW FILES command, an "insufficient privileges for attempted operation" error message is displayed.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.4 Transport Problems
This section describes problems related to the use of transport
protocols with the Advanced Server, corrected in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.4.1 15-Character Alias Name Truncated in Claimed NETBIOS Name
Problem:
When a user specifies a cluster alias name 15 characters in length, one of the two associated NETBIOS names that get claimed is truncated to 14 characters. This is the name that ends with "\0x00" in the last byte and is used for datagrams.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.5 Event Logging Problems
This section describes problems related to event logging functions of
the server, corrected in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.5.1 Displaying Application Event Log Files Fails to Display Events Data
Problem:
The ADMINISTER command SHOW EVENTS/FULL displays details about events. Both the ADMINISTER command and the NT Event Viewer give you the description of the event (the text associated with an event ID). There is also optional data included with some events that helps with troubleshooting problems. This information is not available from the ADMINISTER command.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.6 Windows 2000 Related Problems
This section describes problems related to the interaction with Windows
2000, corrected in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.6.1 Attempts to Add a User Fails
Problem:
Adding a user in a mixed-mode Windows 2000 domain fails if the PDC's user account policy specifies a minimum password length, even when the password specified is long enough. Messages would be seen as in the following example:
LANDOFOZ\\TINMAN> add user smith/pass="ilikethisstuff" %PWRK-E-ERRADDUSER, error adding user "SMITH" -LM-E-NERR_PASSWORDHI, password too short or found in history list |
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.6.2 Windows 2000 Clients See Blank Date Fields for Shared Files
Problem:
When users of a Windows 2000 client view the properties of a shared file with an unknown file extension, the date fields are blank. In addition, the last four date fields stored in the UNKNOWN=%X80 ACE are all zeros.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.6.3 DCL SET PASSWORD Command Fails in Windows 2000 Mixed-Mode Domain
Problem:
If the host server for authentication is a BDC in a mixed-mode Windows 2000 domain, the DCL SET PASSWORD command fails when attempted by an OpenVMS user marked for external authentication, and the hostmapped server user's password was last updated using the ADMINISTER MODIFY USER/PASSWORD command. The following example shows the error messages returned:
$ SET PASSWORD [Return] Old password: [Return] New password: [Return] Verification: [Return] %SET-I-SNDEXTAUTH, Sending password request to external authenticator %SET-E-EXTPWDERR, Password could not be set by external authenticator -SYSTEM-F-AUTHFAIL, authorization failure -ACME-E-UNSPECIFIED, general error, see secondary status for details |
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.6.4 Roaming User Profiles Cannot Be Saved on the Advanced Server
Problem:
In a Windows 2000 terminal server environment, roaming user profiles cannot be saved on the Advanced Server. When a user logs out from a terminal session, error messages indicate that the file could not be copied or the file could not be found, and that the roaming profile could not be updated.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server). However, for profiles stored
on a PATHWORKS for OpenVMS (Advanced Server) share, bear in mind the limitations of the ODS-2
disk volume structure, which does not support long directory names
(longer than 32 characters). See Section 7.5.2, Restriction on Roaming User Profiles.
6.6.5 Access Denied When Copying a Subfolder of a Directory Tree Using the Windows 2000 Xcopy Command
Problem:
Using the xcopy command on a Windows 2000 client to copy a directory tree to a PATHWORKS share might result in an "Access Denied" error immediately after creating a subdirectory. This problem does not occur on Windows NT or Windows 98 clients.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server).
6.7 Miscellaneous Problems
This section describes miscellaneous problems pertaining to the
PATHWORKS Advanced Server.
6.7.1 Advanced Server Supplies Obsolete Version of File Used by eXcursion
Problem:
The Advanced Server supplies an obsolete version of SYS$COMMON:[SYSEXE]PCX$SERVER.COM. The file is used by eXcursion.
Solution:
This problem is resolved in PATHWORKS V6.1 for OpenVMS (Advanced Server). The current version of the file is correctly installed in SYS$COMMON:[SYSEXE]. You can find the correct version on the PATHWORKS 32 distribution kit as file PCX_SERV.COM, or contact your Compaq customer support center.
This chapter describes restrictions in the PATHWORKS V6.1 for OpenVMS (Advanced Server) software. The restrictions are described in the sections indicated in the following table:
This section describes restrictions in the installation and
configuration of the PATHWORKS Advanced Server software.
7.1.1 PWRK$CONFIG and PWRK$SETINI Command Procedures Fail After Domain Name Change Failure
Problem:
The command procedures PWRK$CONFIG.COM and PWRK$SETINI.COM may fail if there has been a previous failure in trying to change the domain name, and your server is going to be a backup domain controller (BDC) in the new domain.
To change your domain name, you must run either the PWRK$SETINI.COM or PWRK$CONFIG.COM command procedure. If the command procedure that you run fails to communicate with the primary domain controller (PDC), then the next time you run either command procedure, it will fail. The command procedure fails while trying to verify the security accounts (SAM) database files. It fails because the name of the domain in PWRK$LANMAN.INI does not match the name of the SAM account database file. The name in LANMAN.INI will have the new domain name, and the name of the SAM accounts file will have the original name.
Solution:
If the PWRK$CONFIG.COM command procedure fails to communicate with the PDC, then after running either of the command procedures, delete all versions of the file PWRK$LMDATAFILES:PWRK$UPG_DOMAINS.DAT.
Next, make sure the domain name in PWRK$LANMAN.INI is the original name
(the name that existed before you tried to change it). If it is not the
original name, then edit the file, delete the new name, and replace it
with the old name. Make sure you type it in uppercase.
7.1.2 PATHWORKS Advanced Server Cannot Coexist with PATHWORKS V5.0C for OpenVMS (LAN Manager) Server
Problem:
The PATHWORKS Advanced Server cannot share a domain with a server running PATHWORKS (LAN Manager) V5.0C. The V5.0C server incorrectly generates a name conflict when the PATHWORKS Advanced Server claims a group name that is used by both servers.
Solution:
To correct this problem, upgrade the PATHWORKS V5.0C server to
PATHWORKS V5.0C ECO1, or a later version of PATHWORKS V5 for OpenVMS (LAN Manager).
7.1.3 PATHWORKS Advanced Server May Fail at Startup Time If SYLOGIN.COM Executes with Errors
PATHWORKS Advanced Server process startup depends on successful execution of OpenVMS logins and logouts.
If your sites make use of SYLOGIN.COM to achieve cluster-member specific logon setup, and SYLOGIN.COM encounters errors, PATHWORKS Advanced Server startup hangs.
When this problem occurs, process startup either fails to generate log
file messages or fails to complete.
7.1.4 Advanced Server Fails to Start If Any Processes Are Running the ADMININSTER Command Line Interface
Problem:
If you attempt to start the Advanced Server while a process is running the ADMINISTER command line interface, the startup may fail and a message similar to the following is displayed:
%PWRK-F-INSGBLSECTS, system has only 53 free global sections -PWRK-I-REQGBLSECTS, PATHWORKS requires a minimum of 75 The system does not have enough free global sections to use PATHWORKS. Please see the Installation Guide on how to increase the number of global sections by modifying the SYSGEN parameter GBLSECTIONS. |
Solution:
Have any process that is running the ADMINISTER command line interface exit from the program. To determine which processes are running the ADMINISTER command line interface, use the following commands:
$ SHOW DEVICE/FILES SYS$SYSTEM: /OUT=TMP.TMP $ SEARCH TMP.TMP PWRK$MANAGER.EXE |
Problem:
On OpenVMS V7.1 systems, if the PATHWORKS on-disk structure contains directories more than eight levels deep, the PWRK$CONFIG procedure cannot move the on-disk structure to another disk because of an OpenVMS RMS restriction. This restriction does not apply to OpenVMS V7.2 or later systems.
Solution:
Before running the PWRK$CONFIG procedure to move the PATHWORKS on-disk structure, either delete directories that are greater than eight levels deep, or rename them so that the standard OpenVMS BACKUP command invoked by PWRK$CONFIG can move them correctly.
| Previous | Next | Contents |