[an error occurred while processing this directive]

HP OpenVMS Systems

Content starts here

HP Advanced Server V7.3B for OpenVMS
Release Notes


Previous Contents Index


Chapter 5
Problems Corrected in Advanced Server V7.3-ECO1 for OpenVMS

This chapter describes problems resolved by software changes made in Advanced Server V7.3-ECO1 for OpenVMS. These software changes will also be included in future ECOs. The problems are described in the sections indicated in the following table:

Problem Type Section Number
Server Problems 5.1
File Access/Printing Problems 5.2
User Interface Command Problems 5.3
Windows 2000 Related Problems 5.4
Transport Problems 5.5
Cluster-Related Problems 5.6
Miscellaneous Problems 5.7

5.1 Server Problems

This section describes the file server problems corrected in Advanced Server V7.3-ECO1 for OpenVMS.

5.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 Advanced Server V7.3-ECO1 for OpenVMS.

5.1.2 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 Advanced Server V7.3-ECO1 for OpenVMS.

5.1.3 PWRK$Monitor Crashes While Attempting to Output an OpenVMS Error Message (932)

Problem:

The PWRK$MONITOR process might crash in module cmtsvrmonsys while attempting to write out a system error message (possibly the OpenVMS error message with status code 932: "%SYSTEM-F-SUSPENDED, process is suspended"). 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 Advanced Server V7.3-ECO1 for OpenVMS.

5.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 Advanced Server V7.3-ECO1 for OpenVMS.

5.1.5 PWRK$LMSRV Process Crashes in Module THREAD

Problem:

The Advanced Server might crash with the following error messages and traceback in the PWRK$LMSRV log file:


%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=0000000000000030, PC=000000000041B560, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image           module  routine          line   rel PC ...
PWRK$CSSHR_V7   THREAD  resume_0         16861 0000000000008520
PWRK$CSSHR_V7   THREAD  threadresumelast
                                         12759 0000000000003E0C
PWRK$CSSHR_V7   WORKQ   WorkQ_queue_work_safe
                                          9556 0000000000000DC8
PWRK$CSSHR_V7   WORKQ   WorkQ_queue_work
                                          9453 0000000000000B0C
PWRK$LMTASKSHR  QUEUE   queue_put        14706 00000000000000E4
PWRK$CSSHR_V7   LIBIPC  mbreaddoneast
                                         32735 0000000000008EC4

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.1.6 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 Advanced Server V7.3-ECO1 for OpenVMS.

5.1.7 Server Crashes in Module SERTL, Routine RtlValidSid

Problem:

With COM for OpenVMS in use, the server might crash with the following error messages and traceback in the PWRK$LMSRV log file:


%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=0000000000000002, PC=0000000000310584, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image    module    routine       line    rel PC   ...
PWRK$LMAPISHR  SERTL  RtlValidSid 47830  0000000000000024
PWRK$LMSRV  ELF  AdtReportEvent   77822  0000000000000818
PWRK$LMSRV  EVENTDISP  ProcessReportEvent
                                  77673  00000000000003D8
PWRK$LMSRV  SSIGNON_PROC  process_acme_message_3
                                 108409  00000000000033A4
PWRK$LMSRV  SSIGNON_COM  receive_comp_handler
                                  51101  0000000000000BEC
PWRK$LMSRV  SSIGNON_COM  ssignon_work
                                  51599  0000000000001A10
PWRK$CSSHR_V7  MTS  MTS$CONTEXT_SWITCH
                                   6693  0000000000000104
PWRK$CSSHR_V7  MTS  MTS$MAIN_SCHEDULER
   .
   .
   .

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.1.8 Server Stops Responding to Logon Requests

Problem:

The server might suddenly stop validating logon requests (NetLogon hangs). For example, when running a user script that adds user accounts (ADMINISTER ADD USER), the server might hang. Similarly, when issuing a command that requires access to the PDC, the server might not respond. A message might indicate that the PDC cannot be found.

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.1.9 Authentication Fails for Domain User Names Exceeding 14 Characters in Length

Problem:

Attempts to log on to an OpenVMS account for which external authentication is enabled are denied if the user enters a user name exceeding 14 characters in length. The server should be able to authenticate user names with a maximum of 20 characters in length.

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.1.10 PWRK$LMSRV Crashes in Module PFS$OPS, Routine PFS_setextattr

Problem:

Under some circumstances, when the file server is attempting to create ACEs (access control entries) for a file or directory, the server crashes due to an ACCVIO in the PFS$OPS module, routine PFS_setextattr. 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=0000000000000003, PC=0000000000438EE8, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
  image    module    routine    line     rel PC          abs PC
PWRK$CSSHR_V7  PFS$OPS  PFS_setextattr
                              25208  0000000000011708 0000000000438EE8
PWRK$CSSHR_V7  PFS$OPS  PFS_copyfile
                              20033  00000000000044C8 000000000042BCA8
PWRK$LMSRV  MVCP  treecopy    56336  0000000000000624 000000000012E8B4
 .
 .
 .

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.1.11 PWRK$LMSRV Crashes When Viewing Printer Properties

Problem:

When attempting to view printer properties with Windows NT printer management enabled, the server might crash in routine T_RegQueryValueEx, with the following error messages and traceback in the PWRK$LMSRV log file:


%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=0000000000000000, PC=FFFFFFFF804BFBE0, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
  image    module    routine             line      rel PC ...
                                            0 0000000000000000
 PWRK$LMAPISHR  TREGWRAP  T_RegQueryValueEx
                                        75355 00000000000016A8
 PWRK$LMSRV  PRNDATA  SplGetPrinterData
                                       102246 0000000000000468
 PWRK$LMSRV  RPCSPOOL  RpcGetPrinterData
                                       112589 00000000000026FC
 PWRK$LMSRV  NTSPL_S  winspool_RpcGetPrinterData
                                        28048 0000000000006498
 PWRK$LMRPCSHR  RPCCALL  rpc__call_put  28446 0000000000000240
   .
   .
   .

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.2 File Access/Printing Problems

This section describes file access and printing problems corrected in Advanced Server V7.3-ECO1 for OpenVMS.

5.2.1 Files Remain Open

Problem:

When a user with less than Full Control Access to a file views the security on that file, the file might be left in an "open" state. Subsequent attempts to delete or rename the file would fail.

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.2.2 Directory Enumeration Incorrect If a File Named ".;1" Exists in the Directory

Problem:

When a client attempts to display the contents of a directory that contains a file named ".;1", the display will be incorrect. For example, the directory might appear empty although it contains files.

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.2.3 Client Application Might Fail When Attempting to Create a Directory on a Share

Problem:

A client application might fail when attempting to create a directory on the Advanced Server. Before creating the directory, the client first queries the server to determine if the directory already exists. The server would return the "NO_MORE_FILES" error message, implying that the directory already exists. As a result, the client would then terminate its attempt to create the directory.

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.3 User Interface Command Problems

This section describes user interface command problems corrected in Advanced Server V7.3-ECO1 for OpenVMS.

5.3.1 PWVER Command Problems

Problem:

Any of several problems with the PWVER command might arise:

  • The PWVER ALL command might produce incorrect results. The display includes messages indicating that information about certain images could not be obtained.
  • Pressing [CTRL/Y] fails to interrupt the PWVER command display.
  • PWVER with a wildcard (*) terminates before displaying all the images that should be listed.

Solution:

These problems are resolved in Advanced Server V7.3-ECO1 for OpenVMS. The PWVER command is not needed for normal operation of the server. It is most often used by HP Customer Support to help solve problems at a customer's site.

5.3.2 Unable to Add Permissions to Local Share

Problem:

If a user uses the ADMINISTER command line interface to log in to a member server's local database and attempts to add permissions to a share in that database, the user might be prompted for the global domain password. This could happen if the member server's local domain (database) does not exist in the global domain, or the password for the local domain differs. In any case, the user should be able to modify permissions without providing the global domain's password.

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.4 Windows 2000 Related Problems

This section describes problems related to the interaction with Windows 2000, corrected in Advanced Server V7.3-ECO1 for OpenVMS.

5.4.1 Attempt to Add or Copy a User Account 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 Advanced Server V7.3-ECO1 for OpenVMS.

5.4.2 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 Advanced Server V7.3-ECO1 for OpenVMS.

5.4.3 Roaming User Profiles Cannot Be Saved on the Advanced Server

Problem:

In a Windows 2000 environment, roaming user profiles might not be saved on the Advanced Server. When a user logs out, 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 Advanced Server V7.3-ECO1 for OpenVMS. For a restriction pertaining to roaming profiles, see Section 13.4.18, Restriction on Roaming User Profiles.

5.4.4 Read-Only Attribute Is Removed When the File is Copied Over Itself

Problem:

If a read-only file on an Advanced Server share was copied over itself, the file's read-only file attribute would be removed.

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.4.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 an Advanced Server 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 Advanced Server V7.3-ECO1 for OpenVMS.

5.4.6 Attempts to Add File Permissions from Windows 2000 Client Fails with "Object Picker Cannot Open" Message

Problem:

Attempts to add permissions to a file from a Windows 2000 client fail. The following message is displayed:


Object Picker cannot open because it cannot determine whether
node-name is joined to a domain.

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.5 Transport Problems

This section describes problems related to the use of transport protocols with the Advanced Server, corrected in Advanced Server V7.3-ECO1 for OpenVMS.

5.5.1 System Hangs or Crashes with a Spinwait Bugcheck

Problem:

An Advanced Server running on a multi-CPU system might cause the OpenVMS system to hang or crash in PWRK$STREAMSOS with a CPU spinwait bugcheck.

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.6 Cluster-Related Problems

This section describes problems relating to servers participating in OpenVMS Clusters. These problems have been corrected in Advanced Server V7.3-ECO1 for OpenVMS.

5.6.1 Server Hangs with One Server Cluster Member in the LEF State, Another Server Member with Multiple Copies of a "deadlock detected" Message

Problem:

When the Advanced Server in an OpenVMS Cluster is the PDC in a domain that includes several BDCs, it might hang. On one node, the server will be in the local event flag wait (LEF) state. On another node, the server log file will contain numerous copies of the following messages:


<timestamp> PCSCACHE\acquire_lock: deadlock detected -- retry
<timestamp> occured during conversion to PWMODE lock

Solution:

This problem is resolved in Advanced Server V7.3-ECO1 for OpenVMS.

5.7 Miscellaneous Problems

This section describes miscellaneous problems pertaining to the Advanced Server for OpenVMS.

5.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 Advanced Server V7.3-ECO1 for OpenVMS. 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 HP customer support center.


Previous Next Contents Index