|
HP OpenVMS Systems |
|
HP Advanced Server V7.3B for OpenVMS
|
| Previous | Contents | Index |
Problem:
Occasionally, the server might crash. 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=0000000000000000, PC=0000000000117AF8, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
PWRK$LMSRV SESSSETUP AddExtraSidsToTokenSids
134347 00000000000030B8 0000000000117AF8
PWRK$LMSRV SESSSETUP LogMeIn 132769 00000000000006E8 0000000000115128
PWRK$LMSRV SESSSETUP smbsesssetup 134020 00000000000029E8 0000000000117428
PWRK$LMSRV SMBWORK smbwork 90471 0000000000001B00 00000000000FD540
PWRK$CSSHR_V7 MTS MTS$CONTEXT_SWITCH
6673 0000000000000104 00000000003BC644
PWRK$CSSHR_V7 MTS MTS$MAIN_SCHEDULER
? ?
PWRK$LMSRV MTS$MAIN main 5678 00000000000000D8 0000000000091AB8
PWRK$LMSRV MTS$MAIN __main 0 0000000000000070 0000000000091A50
0 FFFFFFFF8028F63C FFFFFFFF8028F63C
|
Solution:
This problem is resolved in Advanced Server V7.3A-ECO4 for OpenVMS.
This chapter describes problems resolved by software changes made in Advanced Server V7.3B 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 |
|---|---|
| Installation and Configuration Problems | 12.1 |
| Server Problems | 12.2 |
| File/Printer Share Problems | 12.3 |
| Transport Problems | 12.4 |
| Browser Problems | 12.5 |
This section describes installation problems corrected in Advanced
Server V7.3B for OpenVMS.
12.1.1 Problem with RestrictAnonymous Registry Parameter
Problem:
In a domain where Advanced Server V7.3A for OpenVMS or later is configured as Primary Domain Controller (PDC), PATHWORKS V6.1 can be added to that domain, even if Registry parameter RestrictAnonymous is set to 1.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.1.2 pwrk$*_V8 Images Not Installed on OpenVMS V7.* Systems
Problem:
When Advanced Server is installed on OpenVMS V7.* systems, then the PWRK$*_V8 images will not be installed. If you upgrade to OpenVMS V8.* version, either you have to manually extract PWRK$*_V8.* files from the kit and copy them to the respective locations or reinstall the kit.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.2 Server Problems
This section describes the file server problems corrected in Advanced
Server V7.3B for OpenVMS.
12.2.1 Server Hangs on all Nodes in the Cluster
Problem:
The Advanced server running on a four node cluster does not respond to client requests as it hangs on all the nodes in the cluster. On one of the nodes, there were numerous copies of the following error message:
PCSCACHE\Passthru_acquire_lock: unexpected VMS status error! (0x9F0) PCSCACHE\Passthru_acquire_lock: unexpected VMS status error! (0xE0A) PCSCACHE\Passthru_acquire_lock: unexpected VMS status error! (0xE0A) . . . |
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.2.2 PWRK$LMSRV Process Crashes in Module PFS$OPS, Routine PFS_getuser()
Problem:
The PWRK$LMSRV process might crash in strlen(), in the module PFS$OPS, routine PFS_getuser(). 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=0000000000000064, PC=FFFFFFFF811A88E8, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
DECC$SHR_EV56
0 0000000000008E8 FFFFFFFF811A88E8
PWRK$CSSHR_V7 PFS$OPS PFS_getuser
29089 0000000000010610 00000000003E79A0
PWRK$LMSRV SESSSETUP smbsesssetup
134181 0000000000002AD8 0000000000117F68
PWRK$LMSRV SMBWORK smbwork
90497 0000000000001A90 00000000000FE210
PWRK$CSSHR_V7 MTS MTS$CONTEXT_SWITCH
6673 0000000000000104 00000000003BC634
PWRK$CSSHR_V7 MTS MTS$MAIN_SCHEDULER
? ?
|
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.2.3 Server Crashes When ADMINISTER Command is Executed to Close the Session
Problem:
When ADMINISTER command is executed to close the session, in the module TRANS, routine smbtrans, the PWRK$LMSRV process crashes. A traceback similar to the following would be seen in the PWRK$LMSRV log file:
Image module routine line rel pc abs pc
PWRK$CSSHR_V7 LIBCHARSET LIB_ServerCPToClientCP
22565 0000000000003718 000000038EA68
PWRK$LMAPISHR CODESETCONV ServerToClientCodeSetConv
69909 00000000000000E8 000000000055EF68
PWRK$LMSRV SRVLANG SrvExportDownLevelString
63892 0000000000000110 000000000019C620
PWRK$LMSRV TRANSPARSE unwindvwv
73033 0000000000001FE0 00000000001A29A0
PWRK$LMSRV TRANSPARSE outparse
73554 0000000000002EA8 00000000001A3868
PWRK$LMSRV FILEAPI CommonFileGetInfo
78901 000000000000221C 000000000014B26C
PWRK$LMSRV FILEAPI ATTNetFileGetInfo2
79044 000000000000259C 000000000014B5EC
PWRK$LMSRV TRANS dotransapi
92542 0000000000002758 000000000011F0F8
PWRK$LMSRV TRANS smbtrans
91976 0000000000000E88 000000000011D828
PWRK$LMSRV SMBWORK smbwork
90471 0000000000001B00 00000000000FD540
PWRK$CSSHR_V7 MTS MTS$CONTEXT_SWITCH
6673 0000000000000104 00000000003BC644
|
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.2.4 PWRK$LMSRV Crashes in Routine SepSidInToken
Problem:
The PWRK$LMSRV process crashes during session setup in routine SepSidInToken. A traceback similar to the following would be seen in the PWRK$LMSRV log file:
Image module routine line rel pc abs pc
WRK$LMAPISHR ACCESSCK SepSidInToken
88066 00000000000000F8 0000000000655568
PWRK$LMAPISHR ACCESSCK SepAccessCheck
88557 00000000000004E4 0000000000655954
PWRK$LMAPISHR ACCESSCK SeAccessCheck
88752 0000000000000774 0000000000655BE4
PWRK$LMAPISHR SECURITY SampValidateObjectAccess
124629 0000000000000A60 0000000000654CD0
PWRK$LMAPISHR DOMAIN PegSamrOpenDomain
134145 0000000000000214 0000000000614654
PWRK$LMSRV SAMRPC SamrOpenDomain
111461 00000000000003C8 00000000000A1F68
PWRK$LMSRV SAMRPC_S samr_SamrOpenDomain
43460 0000000000001058 00000000000A4F58
PWRK$LMAPISHR RPCCALL rpc__call_put
32676 0000000000000204 00000000006341A4
PWRK$LMAPISHR CNSRV rpc__ncacn_process_request
42142 0000000000001F78 000000000062ED78
PWRK$LMAPISHR CNSRV rpc__ncacn_datawork
42611 0000000000002D20 000000000062FB20
|
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.2.5 Set Password fails With Externally Authenticated User
Problem:
In a domain with Windows 2000 or Windows 2003 as a PDC emulator and Advanced Server configured as Member server, if a user tries to modify the password of an externally authenticated account using DCL SET PASSWORD command, the error messages similar to the following will be displayed:
$ SET PASSWORD Old password: New password: Verification: %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-FAILURE, requested operation has failed |
Solution:
This Problem is resolved in Advanced Server V7.3B for OpenVMS. Note
that if the password is changed by executing the DCL SET PASSWORD
command, then the sessions established through ADMINISTER commands
prior to password modification, will be lost. Users have to re-login
again using the new password.
12.2.6 Delay in the Server Response to Pipe Open Requests
Problem:
If there are simultaneous pipe open requests from clients, there is a delay in the server response.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.2.7 PWRK$LMSRV Crashes in Module TRANSPARSE, Routine unwindvwv
Problem:
The PWRK$LMSRV process might crash in memcpy(), in the module TRANSPARSE, routine unwindvwv. A traceback similar to the following would be seen in PWRK$LMSRV log file:
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
LIBOTS
0 0000000000219D8 FFFFFFFF80CF99D8
PWRK$LMSRV TRANSPARSE unwindvwv
73016 0000000000001E6C 00000000001A328C
PWRK$LMSRV TRANSPARSE outparse
73578 0000000000002EA8 00000000001A42C8
PWRK$LMSRV SHAREAPI ATTRNetShareGetInfo
104883 0000000000002F9C 00000000001335FC
PWRK$LMSRV TRANS dotransapi
92569 0000000000002758 000000000011FB48
PWRK$LMSRV TRANS smbtrans
92003 0000000000000E88 000000000011E278
PWRK$LMSRV SMBWORK smbwork
90497 0000000000001A90 00000000000FE210
|
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.2.8 Advanced Server Does Not Support More than 32 %X86 ACEs
Problem:
When the ACL grows beyond 31 ACE's while adding users to the security mask of the file, the Advanced Server fails to display this file or crashes.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.2.9 PWRK$LMSRV Crashes in Routine FileEnumWorker
Problem:
The PWRK$LMRV process might crash in module ENUMS, routine FileEnumWorker while enumerating files opened on the server. 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=0000000000000000, PC=FFFFFFFF809A88E8, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
DECC$SHR_EV56
0 00000000000008E8 FFFFFFFF809A88E8
PWRK$LMSRV ENUMS FileEnumWorker
117407 0000000000002078 00000000000EC368
PWRK$LMSRV ENUMS realFileEnum
117896 0000000000002A0C 00000000000ECCFC
PWRK$LMSRV ENUMS NetrFileEnum
118037 0000000000002CA0 00000000000ECF90
PWRK$LMSRV SRVSVC_S srvsvc_NetrFileEnum
33935 000000000000196C 00000000000B27DC
PWRK$LMAPISHR RPCCALL rpc__call_put
2677 0000000000000204 0000000000635084
|
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.2.10 OpenVMS System Hangs During Reboot
Problem:
Advanced Server references quadword I/O database mutex, IOC$GQ_MUTEX through long word routines SCH$LOCKREXEC and SCH$UNLOCKEXEC which corrupts the IOC$GQ_MUTEX, causing the OpenVMS system to hang.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.2.11 PWRK$LMSRV Crashes in Routine resume_0
Problem:
The Advanced server might crash in module Thread, routine resume_0. 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=0000000000000030, PC=0000000000417000, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
PWRK$CSSHR_V7 THREAD resume_0
20095 0000000000008070 0000000000417000
PWRK$CSSHR_V7 THREAD threadresumelast
15961 0000000000003C34 0000000000412BC4
PWRK$CSSHR_V7 WORKQ WorkQ_queue_work_safe
11798 0000000000000B30 0000000000419D80
PWRK$CSSHR_V7 WORKQ WorkQ_queue_work
11695 0000000000000944 0000000000419B94
PWRK$LMAPISHR QUEUE queue_put
14017 00000000000000EC 000000000063266C
PWRK$CSSHR_V7 LIBIPC mbreaddoneast
52520 0000000000008420 000000000039D290
|
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.2.12 ADMINISTER SHOW SESSIONS and ADMINISTER SHOW CONNECTION Commands Do Not Display Information for all User Sessions
Problem:
If the number of user sessions exceeds 622, then ADMINISTER SHOW SESSION command will display session information only for 622 users.
If multiple users are connected to the Advanced Server from a Windows 2003 system through CITRIX terminal services client and if ADMINISTER SHOW CONNECTION command is executed on Advanced server, it displays the information only for the last user connected through CITRIX terminal service client and not for other users.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS
12.2.13 Advanced Server Always Establishes Secure Channel Against PDC
Problem:
If Advanced Server is configured as the Member Server in a domain, it always establishes secure channel with the PDC. In a domain where PDC lies across the WAN, if the communication channel is slow, the communication between the Advanced server and the Primary Domain Controller gets disconnected or timed out.
Solution:
This Problem is resolved in Advanced Server V7.3B. Note that if Advanced Server is configured as a Member Server to Windows 2000 or Windows 2003 domain, it can establish secure channel with any domain controller, if the registry parameter "MemberInAD" is set to 1.
The registry parameter can be set by executing the following commands:
$ @SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM |
$ REGUTL SET PARAMETER VMSSERVER MEMBERINAD 1 /CREATE |
Once this registry parameter is created, /create qualifier need not be
used to modify the parameter again. Also, Advanced Server needs to be
restarted everytime the value of this registry parameter changes for
the new value to take effect.
12.2.14 OpenVMS System Crashes in Routine OTS$MOVE_C+004D0
Problem:
The OpenVMS System might crash in routine OTS$MOVE_C+004D0, with the following Bugcheck information:
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Node: BB01 (Cluster) CPU Type: HP AlphaServer ES80 7/1150 VMS Version: V8.2 Current Process: NULL Current Image: Failing PC: FFFFFFFF.80009B50 OTS$MOVE_C+004D0 Failing PS: 10000000.00000804 |
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.3 File/Printer Share Problems
This section describes file access and printing problems corrected in
Advanced Server V7.3B for OpenVMS.
12.3.1 Server-Based Licenses are Lost Whenever a Node in the Cluster Crashes
Problem:
In a cluster environment, all the nodes get the Server-Based licenses from a common license pool. If one of the node in the cluster crashes and one or more clients have Server-Based licenses assigned through that node, sometimes those licenses are lost until the Advanced Server is restarted on one of the node in the cluster.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.3.2 Advanced Server Shared Files Appear Empty When the Data is Requested from a Linux Client
Problem:
After mapping an ASV share from the Linux client, if an user tries to view the files, they appear empty.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.3.3 File Creation on a Linux Client Fails, and touch Command Hangs
Problem:
After mapping an ASV share from the Linux client, if an user tries to create a file using touch command, the command hangs until the Linux client re-establishes the session.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.3.4 Problem Accessing Shared Files from Windows 2003 SP1 Clients
Problem:
When Windows 2003 SP1 clients try to access files on Advanced Server share, they face the following problems:
\\server-name is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if You have access permissions" |
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.3.5 Users are Unable to Connect to Shares on Windows 2000 Member Servers or Workstations in a Domain
Problem:
In a domain with Advanced Server as PDC, the users will not be able to connect to shares on Windows 2000 member servers or workstations using the credentials of user(s) belonging to another domain where Advanced Sever PDC has a trust established.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.3.6 Viewing XML Files on Windows Using Internet Explorer Dislays an Error Message
Problem:
When an user tries to view an XML files generated on OpenVMS using Internet Explorer (IE) on Windows an error message similar to the following is displayed at the bottom of the page:
"The XML page cannot be displayed Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later." |
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.3.7 Unable to Copy or Print a File on Advanced Server Share if the File Size is Greater than the Datacache Size
Problem:
If clients try to copy a file to an Advanced Server share, there is a 3 minute delay if the file size is less than the Advanced Server data cache size. If the file size exceeds the data cache size, the clients time out after 3 minutes. This problem occurs even when client tries to a print a file using an Advanced Server shared printer.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS.
12.4 Transport Problems
This section describes problems related to the use of transport
protocols with the Advanced Server, corrected in Advanced Server V7.3B
for OpenVMS.
12.4.1 Messages are not Logged When WINS Server is Unavailable
Problem:
If the server is not able to register its name with the specified WINS server, messages indicating the unavailability of the WINS server are not logged.
Solution:
This problem is resolved in Advanced Server V7.3B for OpenVMS. Now the following messages will be displayed in the pwrk$knbdaemon_<node name>.log file :
"*Warning*: WINS Server is unavailable (IP Addr: <WINS server ip address>)" |
"Server established contact to WINS Server (IP Addr: <WINS server ip address>)" (IP Addr: <WINS server ip address>)" |
<node name> is the SCSNODE name of the system. |
| Previous | Next | Contents | Index |