|
HP OpenVMS Systems |
|
HP Advanced Server V7.3B for OpenVMS
|
| Previous | Contents | Index |
Problem:
This problem is specific to Version 7.3A only. Listing the contents of a directory in an Advanced Server share by specifying the directory's alias file name causes several meaningless entries to be created in the server's common event log.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.21 Unable to Open Event Log on Modern NT Systems
Problem:
Attempts to read or clear the event log on modern NT systems result in an error message: -LM-E-RPC_X_BAD_STUB_, The stub received bad data" (Windows 2000), or -LM-E-ERROR_INVALID_PARAMETER
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.22 Unable to Add PATHWORKS V5.0F ECO2 as a Member Server (or Backup Domain Controller) to Advanced Server V7.03A ECO1 Primary Domain Controller
Problem:
When PATHWORKS V5.0F ECO2 was configured as a member server to Advanced Server V7.03A ECO1, PWRK$LMDMN of PATHWORKS V5.0F ECO2 would ACCVIO at routine updateuser. An error message indicating "authentication failure" or "synchronization failure" would be displayed.
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=0052FD73,
PC=00068B94, PSL=0BC00000
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
00068B94 00068B94
SSILOGON updateuser 46826 000001A5 0002E811
SSILOGON processrec 46946 0000017F 0002EC07
SSILOGON syncdelta 47579 00000779 00030335
NETLOGON dologonsync 48398 000000D8 0002B658
000C2685 000C2685
MTS$MAIN main 2966 0000001B 0002801F
|
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.23 Wrong Behavior If the File is Renamed with an Extension of More Than 39 Characters
Problem:
From a Windows client, if you rename a file residing on an Advanced Server Version 7.3A ODS-2 disk share with an extension of more than 39 characters, the rename operation appears to be successful on the client, but the file becomes unusable until the next synchronization between the client and the server. On ODS-2 disks, the Advanced Server Version 7.3A does not support file names with more than 39 characters in the file extension. Attempts to rename a file in such a way now fails with an error message indicating the failure.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.24 Error in Advanced Server Version 7.3A PWRK$ACME_STARTUP
Problem:
When you move the two VAX external authentication images PWRK$ACME_MODULE_VAX.EXE and PWRK$ACME_STARTUP.COM distributed with the Advanced Server Version 7.3A ECO1 to a VAX node, the following error message displays:
$ original_parse_style = F$GETJPI("", "PARSE_STYLE_PERM")
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
\PARSE_STYLE_PERM\
|
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.25 Server Crashes in BUFIO, Routine lm_force_close
Problem:
In rare circumstances when attempting to remove an entry from the Open File Cache queue, the server might crash in routine lm_force_close.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.26 ADMINISTER Command REMOVE USER/GROUP Confirmation Prompts to Include Domain/Member Server Name
Problem:
When a user executes the ADMINISTER command REMOVE USER, the confirmation prompt does not show the domain name from which the user will be removed.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.27 MCP Ran Out of Pipe Instances
Problem:
While waiting for pipe server to complete a pipe-onen, the pipe threads might stall and sometimes the Advanced Server might hang.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.28 Printing Sometimes Fails with the File Lock Error
Problem:
When a client user attempts to print a document on a print share on the Advanced Server, the operation fails with the following error:
"Unable to write the file because another process has locked a portion of
the file."
|
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.29 Network Problems Cause OPLOCK Timeouts
Problem:
Network problems sometimes lead to OPLOCK timeouts. These timeouts cause threads to hang, which eventually causes the server to hang.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.30 ADMINISTER SET PASSWORD Resulted in ACCVIO
Problem:
Advanced Server access violated on NULL when freeing buffers.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.31 Process Startup Fails Due to Wrong Default Directory
Problem:
PWRK$LICENSE_R erros are seen when creating a process.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.32 MCP Crashes in Module VCDROPPED, Routine mcpvcdropped
Problem:
Processing client requests with service bits other than "00" or "20" resulted in MCP crash.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.33 "Sharedb" File Could Grow to an Unreasonable Size, and Could Not be Shrunk Using "blobadm"
Problem:
When a share is modified, the Advanced Server Version 7.3 creates a new object for that share in the share database file. The old object should be deleted, but a bug in the Version 7.3 code prevents that from happening. The file space occupied by the old object and its key slot become permanently unavailable for re-use. This was fixed in Version 7.3A, but customers that upgraded from Version 7.3 to 7.3A were still affected with an unreasonable size for "Sharedb".
Solution:
A new "blobadm" option (-"E" -u) has been created to recover the inaccessible objects and key slots in a share database file.
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.34 Crashes or Hangs Caused by OPLOFC Threads
Problem:
Design and implementation issues with OPLOCKS and Open File Cache (OFC).
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.35 Avoid Logging Unnecessary Event Types
Problem:
Windows 2000 clients broadcast netlogon packets with a null user name. The Advanced Server logs these packets as security events of event type 529, and fails the logon request. This happens frequently. Because of this, security event logs keep growing.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.36 Browser Service Stays in PENDING State
Problem:
If you have an Advanced Server multi-node cluster PDC, and you hide the servers via the "srvhidden" registry value, then all of the browsers that are not the "active" browser will never leave the "Start Pending" service state. The "active" browser is the one that comes to life first and claims the PWRK$BROWSER lock in EX mode.
Solution:
The problem was fixed in the previous release, but has been
restructured in Version 7.3A-ECO2. Although the Browser starts
correctly on all the cluster nodes, the ADMINISTER SHOW COMPUTER
command might still take some time to display all the servers. This is
normal and intended behavior.
9.37 Excessive Pipes Consumption and File Lock Problems Due to Invalidated Sessions
Problem:
Various symptoms such as clients not being able to access the server's named pipes, files and other resources on the server remaining locked indefinitely although the client is no longer accessing them, etc.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.38 PWRK$LMSRV Crashes in Module APICHECK, Routine ApiAccessCheckAndAudit
Problem:
Server crashed when a NULL primary token was accessed.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.39 Memory Leak When RPC Throws an Exception
Problem:
PWRK$LMBROWSER dies with the following errors and then the process crashes.
t_alloc T_UNITDATA failed: system error - failed to allocate virtual memory t_alloc T_UNITDATA failed: system error - failed to allocate virtual memory t_alloc T_UNITDATA failed: system error - failed to allocate virtual memory %DEBUGBOOT-W-EXQUOTA, process quota exceeded %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000000, PC=000000000034B024, PS=0000001B |
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.40 Session Thrashing
Problem:
This problem can be seen most easily by mapping two shares from a Windows 95 client, one using the server listenname, and one using the cluster alias name. If you do this using a Version 6.1 or 7.3 server, then the client might use both drives simultaneously. In Version 7.3A, only one drive was allowed to be active at a time. The other one was disconnected.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.41 REGUTL Utility Unaware of New Registry Value
Problem:
You cannot modify the time period between password changes for machine accounts.
In the Version 7.3 release of Advanced Server, the registry value that was used for timing changes to machine account passwords was netlogon\ssipasswdage, specified as the number of seconds. Because of the difficulty some users had computing the number of seconds, the Version 7.3A release used the registry value netlogon\MaximumPasswordAge for timing changes to machine account passwords, specified as the number of days. The REGUTL program has been updated to recognize this change.
For more details about the significance of this registry value, refer to Microsoft technet article Q175468
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.42 Missing Out on Open Files/Pipes, Connections and Shares During Enumeration
Problem:
When we try to enumerate the open file(s) / pipe(s), connections using
ADMIN> show open ADMIN> show connections |
and shares using Server Manager in Windows, you may not see the right output. Either the resources do not get displayed at all or they get associated with the wrong user names giving a wrong output.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
The Server Manager and ADMINISTER commands mentioned above now displays
the correct results. If the user associated with a resource is not
found (such as the user has logged off), and the resource is still in
use, the S erver Manager displays the resource with no user name.
9.43 Autoshares Shows Garbled Information in the Description Field and Modification of that Share Creates a New Share
Problem:
Autoshares show garbled information in the description field. Modifying the description of such an autoshare adds a new share (with the name of the autoshare) in the share database file, and this new share cannot be removed. The result is a corrupted database file.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.44 Cannot Establish Trust with Windows 2003 Domain
Problem:
When a Version 7.3A-ECO1 Advanced Server is the PDC of a domain, it is unable to establish a trust with a domain that has a Windows 2003 server as its PDC emulator. The Advanced Server can neither trust nor be trusted by the Windows 2003 domain.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.45 "Access Denied" Error While Accessing Non-stream Files On ODS-2 Disks
Problem:
While accessing non-stream files on ODS-2 disks, Advanced Server fails to convert Meta-pathname into ODS-2 encoded RMS pathname. This could result in "access denied" failures when a user had access.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
9.46 Advanced Server Does Not Bind to the Correct Device on a Multihomed System
Problem:
On a multihomed system, Browsing and Netlogon services always use the IP address associated with the interface that was configured first. If the IP address indicated by PWRK$KNBDAEMON_IPADDR is not the first one in the TCPIP bind order, "Browsing" , "Netlogon" and "Nbshow" commands would fail.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO2 for OpenVMS.
10.1 Server Crashes in Routine FileEnumWorker()
Problem:
The sever might crash with an access violation (ACCVIO) in module ENUMS, routine FileEnumWorker. A traceback similar to the following would be seen in the PWRK$LMSRV log file:
26-JAN-2004 07:27:53.94 20402F29:04CF0498 sso_work: starting task SSOwork 01
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=0000000000000080, PC=00000000000E9058, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
PWRK$LMSRV ENUMS FileEnumWorker
117495 00000000000023C8 000000000E9058
PWRK$LMSRV ENUMS realFileEnum
117822 0000000000002B9C 00000000000E982C
PWRK$LMSRV ENUMS NetrFileEnum
117963 0000000000002E30 00000000000E9AC0
PWRK$LMSRV SRVSVC_S srvsvc_NetrFileEnum
33934 000000000000196C 00000000000AEF1C
PWRK$LMAPISHR RPCCALL rpc__call_put
32676 0000000000000204 0000000000614174
PWRK$LMAPISHR CNSRV rpc__ncacn_process_request
42142 0000000000001F78 000000000060ED48
PWRK$LMAPISHR CNSRV rpc__ncacn_datawork
42611 0000000000002D20 000000000060FAF0
PWRK$LMAPISHR RPCCALL callwork 32751 00000000000004D0
PWRK$CSSHR_V7 MTS MTS$CONTEXT_SWITCH
6673 0000000000000104 000000000039C5E4
PWRK$CSSHR_V7 MTS MTS$MAIN_SCHEDULER ? ?
PWRK$LMSRV MTS$MAIN main 5678 00000000000000D8 0000000000091A68
PWRK$LMSRV MTS$MAIN __main 0 0000000000000070 0000000000091A00
0 FFFFFFFF8028759C FFFFFFFF8028759C
28-JAN-2004 09:01:31.05 20402F29:044B3120 PLM_exit_handler: releasing lock
database resources...
|
Solution:
This problem is resolved in Advanced Server V7.3A-ECO3 for OpenVMS.
10.2 Server Does Not Respond to Any Requests from the Clients
Problem:
The PWRK$LMSRV process becomes unresponsive to clients' requests. The only solution to this problem is to restart the Advanced Server.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO3 for OpenVMS.
10.3 Many Sessions Consumed by 'datagrams on name 00'
Problem:
Often the clients are unable to connect to the server and the ADMINISTER commands fail with the following error message "network path not found".
The PWRK$KNBDAEMON log file reports:
***** No free KNBCB available...You may need to re-configure for more clients! |
The command $NBSHOW KNB shows many sessions allocated/used by "datagrams on name 00":
num state nmcb next accq rname raddr 1. 0000 0 0 0 --datagrams on name 00-- 3. 0000 0 0 0 --datagrams on name 00-- 4. 0000 0 0 0 --datagrams on name 00-- 5. 0000 0 0 0 --datagrams on name 00-- 6. 0000 0 0 0 --datagrams on name 00-- 8. 0000 0 0 0 --datagrams on name 00-- 9. 0000 0 0 0 --datagrams on name 00-- 12. 0000 0 0 0 --datagrams on name 00-- 14. 0000 0 0 0 --datagrams on name 00-- 15. 0009 7 448 0 "CCS001 00" 10.1.5.29 17. 0000 0 0 0 --datagrams on name 00-- |
Solution:
This problem is resolved in Advanced Server V7.3A-ECO3 for OpenVMS.
10.4 ADMINISTER Utility Crashes While Loading the Client Codepage Table
Problem:
ADMINISTER utility crashes with the following footprint, with an additional error message that, it was not able to initialize server character set tables whenever ASV datafiles reside on an ODS-5 disk and the process's case, which executes the ADMINISTER utility, was set to "sensitive".
image module routine line rel PC abs PC
0 FFFFFFFF80888954 FFFFFFFF80888954
PWRK$MGTLIBSHR ML_ERROR ML_Err_Signal
40365 00000000000003F8 00000000002FF278
PWRK$MANAGER MANAGER Manager
56422 0000000000000490 0000000000040490
PWRK$CSSHR_V7 MTS MTS$CONTEXT_SWITCH
6673 0000000000000104 00000000001145E4
PWRK$CSSHR_V7 MTS MTS$MAIN_SCHEDULER ? ?
PWRK$MANAGER MTS$MAIN main 5678 00000000000000D8 000000000005CEE8
PWRK$MANAGER MTS$MAIN __main 0 0000000000000070 000000000005CE80
0 FFFFFFFF8028363C FFFFFFFF8028363C
|
Solution:
This problem is resolved in Advanced Server V7.3A-ECO3 for OpenVMS.
10.5 Problem With Windows NT-style Printing - Settings Done by Administrators are Not Visible to Users That are Members of Domain Users Group
Problem:
Normally when a user, who is only a member of Domain Users group, adds a printer on the PC client, which is served by a Print Server, the client adds a set of registry values in the local PC client at the location:
[HKEY_LOCAL_MACHINE.Software.Microsoft.WindowsNt.CurrentVersion .Print.Providers.LanMan Print Services.Servers.<printserver>. Printers.<printershare>] |
These registry keys store the printer settings particular to that PC client and gets synchronized with the server registry whenever there is any changes in the print server settings.
These registry keys store the printer settings particular to that PC client and gets synchronized with the server registry whenever there is any change in the print server settings.
Since there was a problem in the creation of the proper printer keys at the above mentioned location, synchronization between the client registry and server registry never occurred. This caused a problem whenever Advanced Server was configured as print server.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO3 for OpenVMS. Now all the printer related
keys get created properly in the client and whenever the client uses
the printers served by Advanced Server Print servers, the latest
settings set by Printer Administrator gets reflected on the client side.
10.6 Error While Executing ADMINISTER SHOW HOSTMAP
Problem:
Whenever an explicit hostmapping from lanman user to hostname user reaches certain number, say 1600-1650, the ADMINISTER SHOW HOSTMAP command does not list the hostmappings, instead, the following error message is displayed.
%PWRK-E-ERRGETHOSTMAPS, error getting host mappings
-LM-E-ERROR_MORE_DATA, additional data is available
|
A similar problem was observed with the command ADMINISTER SHOW HOSTMAP/HOSTUSER whenever many (more than 1600-1700) lanman users map to a single hostuser.
Solution:
This problem is resolved in Advanced Server V7.3A-ECO3 for OpenVMS. Now the ADMINISTER command
successfully lists all the explicit hostmappings (including the case
where many lanman user mapping to single host user) even if the number
of hostmap entries exceed 1650.
10.7 PWRK$LMSRV Process Crashes in Module FORCE
Problem:
In Version 7.3A-ECO2 of the Advanced Server for OpenVMS, the server crashes due to an ACCVIO in module Force, routine get_latest_logoff. 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=000000000000
007C, PC=0000000000170008, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
PWRK$LMSRV FORCE get_latest_logoff
120953 0000000000000998 000000000170008
PWRK$LMSRV FORCE force_logoff
120741 0000000000000318 00000000016F988
PWRK$LMAPISHR CALLOUT callout_task
64950 00000000000003E8 000000000053B618
|
Solution:
This problem is resolved in Advanced Server V7.3A-ECO3 for OpenVMS.
| Previous | Next | Contents | Index |