The following problems have been addressed in the DCE Version 3.1 Kit. This list also includes the problems addressed in DCE Version 3.0 ECO1 and DCE Version 3.0 ECO2 kit.

• The security tickets for SELF-credentials failed to re-authenticate automatically when they expire under a specific condition. "Klist-ef" command displays expired tickets for machines SELF principal.
• DCE CDS Clerk process consumes high CPU time. The looping occurs while cdsclerk was deleting the unused binding handles and marks the inuse handles for future deletion. All these in-used and free (unused) binding handles are part of the dynamically allocated linked list.
• While configuring DCE as a client, the dce$cdsadver process sometimes goes into a hang state on OpenVMS Version 7.3-1.
• The DCE application hangs occasionally with the following error:

  2002-10-01-21:42:32.552-04:00I0.238 PID#541458706 FATAL rpc recv CNRCVR.C;1 563 0x0d563740(rpc__cn_network_receiver) Unexpected exception was raised

• When an illegal state transition detected in CN server call state machine, the DCE/RPC does not report the correct state and event of the state machine.
• When a large number of ACMSxp Processing servers are stopped and started several times in a loop, DCE$CDSADVER process aborted with the following error:

  2002-10-13-23:33:25.440+09:00I----- dce$cdsadver(31600) ERROR cds adver ADVER_SOCKET.C;1 130 0x00a69500 %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000030, PC=FFFFFFFF8118A8E8, PS=0000001B

• XDS header files shipped with DCE replaces the existing X.500 specific files. The DCE install procedure has been modified to copy into [syslib] area only when the common XDS headers (that shipped with both DCE and X.500 kits) are not present.
• Non-privileged VMS user failed to get all the credential files created during dce_login.
• The DCE specific pre-authentication files in DCE$LOCAL:[VAR.SECURITY.PREAUTH] and dtsd.binding file in DCE$LOCAL:[VAR.ADM.TIME] have been assigned with an in-valid file ownership.
• If a VMS DCE RPC application client calls a VMS DCE RPC server and then cancels the thread in which the RPC was started, the server crashes with the following message:

  2003-03-20-16:53:31.137+01:00I4.884 PID#551581762 FATAL rpc cn_state CNSCLSM.C;1 3123 0x02165b40 Illegal state transition detected in CN server call state machine [cur_state: 255, cur_event: 102, call_rep: 1ec9240] %SYSTEM-F-OPCCUS, opcode reserved to customer fault at PC=FFFFFFFF80A3E434, PS=0000001B

• On a DCE Version 3.0 system the SECD process can report the following messages:

  krb5kdc: Unknown code DCE:krb 37 (336760869) pa verify failure krb5kdc: Unknown code DCE:krb 31 (336760863) pa verify failure

  
  One of the causes for the above messages is, mismatch in the passwords stored in the registry database and keytab files for the client and server principals.
  The principal name that is causing "PA verify failure" would be reported in DCE Version 3.1. It is expected the user would take necessary action to correct the password mismatches.

• The "dcecp -c clearinghouse modify <clearinghouse name> -add \{CDS_ UpgradeTo 4.0\}" command reports "Error: Unrecognized argument ’4.0}’".
  The correct usage of the command is:

  $dcecp -c clearinghouse modify <clearinghouse name> -add "{CDS_UpgradeTo 4.0}" (or) dcecp> clearinghouse modify <clearinghouse name> -add {CDS_UpgradeTo 4.0}

• The DCE Security master server ACCVIOs with the following information:

  %SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=00000000000000D8, PC=000000007BBB37EC, PS=0000001B

• When a large number of ACMSxp Processing servers are stopped and re-started several times in a loop, DCE$CDSCLERK process aborted with the following error:

  2003-04-28-15:30:42.052+09:00I----- dce$cdsclerk(20200985) FATAL rpc recv CNRCVR.C;1 566 0x0418b580 (rpc__cn_network_receiver) Unexpected exception was raised %DECthreads bugcheck (version V3.19-059), terminating execution. % Reason: lckMcsLock: deadlock detected, cell = 0x000000000A601580 % Running on OpenVMS V7.3-1() on AlphaServer GS160 6/731, 0Mb; 8 CPUs, pid 538970215 % The bugcheck occurred at 22-APR-2003 04:25:51.12, running image % DSA0:[SYS0.SYSCOMMON.][SYSEXE]DCE$CDSCLERK.EXE;1 in process 20200867 (named "DCE$CDSCLERK"), under username "SYSTEM". AST delivery is enabled for all modes; no ASTs active. Upcalls are disabled. Multiple kernel threads are disabled.

• DCE_SETUP START some times reports the following error.

  Starting sec_client service (please wait) Error: secval service already enabled

• When the bogus parameter was input as the CDS master server name, there was no condition check in the dce$setup.com file to see whether the input parameter is correct or wrong. Because of this missing condition check there was no error reported even when the input parameter was incorrect.
• Bogus error message is reported when the CDS replica is unavailable: Directory Synchronize command of dcecp throws an error "Unable to communicate with any CDS server" even if one of the CDS server (clearinghouses) is not available on which the replica of the directory being skulked resides. The command response now shows the inaccessible clearinghouse names.
  The output would look like below:

  dcecp> directory synch /.: Skulk failure: /.: /.../dce73-cell/ch1_ch inaccessible 1 replica(s) not updated Error: Unable to communicate with any CDS server

• If the time difference on the client system and DCE security server system is not within the permissible time skew value, the DCE startup on client system aborts without reporting any error to the user.
• Some times the rgy_edit command fails due to failure in gethostbyname( ) function.
• The DCE daemon dump files are not created in the daemon specific directories. In DCE Version 3.1, the dump file of the daemon would be created in its result directory.
  For example, the dump of the DCED daemon would be available in the directory DCE$LOCAL:[VAR.DCED]
• During the DCE configuration, when prompted for whether the node should accept time from DECdts servers, entering ’?’ at the prompt, the configuration procedure aborts after displaying the Help as below:

  Should this node accept time from DECdts servers? (YES/NO/?) [N]? ? DCE DTS Time servers can accept time synchronization messages from DECnet DTSS time servers as well as DCE DTS servers. Answering YES to this question will allow this interaction to occur. %DCL-W-USGOTO, target of GOTO not found - check spelling and presence of label \DCE_QUERY_DTS_DECNET\

• The "Add CDS Replica" option in the "Modify Menu" of the DCE setup procedure becomes "Remove CDS Replica" after the operation of adding the CDS Replica fails.
• Some of the error handling sub-routines in DCE Setup command procedure do not report the exact DCE error message on failure of the DCE Commands and instead report a "CLI-W-ABVERB" error, which is not informative enough to troubleshoot the problem.
• The DCE Security Server aborted with the following error information:

  2003-07-08-13:39:36.070+08:00I----- PID#2018 FATAL rpc recv KRBCLT.C;1 296 0x7bbe46f0 (rpc__krb_get_tkt) Unexpected exception was raised %CMA-F-EXCCOP, exception raised; VMS condition code follows -SYSTEM-F-OPCCUS, opcode reserved to customer fault at PC=FFFFFFFF80623E54, PS=0000001B

• When a large number of ACMSxp Processing servers are stopped and re-started several times in a loop for about 2 days, the DCE$DCED process access violated and DCE$DCED.OUT file contains many of the following errors:

  *** CREATE_NET_CHANNLE_W_MBX FAILURE *** 1b4 errors.

• A potential denial of service has been identified on OpenVMS systems that have the DCE products installed or that are using the RPC portion of DCE that ships with the OpenVMS operating system. These OpenVMS systems could be vulnerable to a remote initiated Buffer Overflow, resulting in hang.
• DCE Configuration procedure continues operation even after logging an error message when any of the CDSCP commands fail during the CDS replica configuration.

  ********************** ERROR **************************** *** Could not execute CDSCP command: *** Cdscp create clearinghouse /.:/mr6axp_ch

  
  The DCE$CDSD daemon was terminated and dce$setup.com continued its operation of configuring the CDS Replica server instead of aborting.

• "DCE Config" menu does not show the correct option for Auditing during successive enabling & disabling.
• The PE_SITE file in DCE V3.0 does not have RE permission for the world.
• For each execution of the DCOM application, the receiver thread in DCE was unable to free the credentials due to which the persona was getting piled up for DCOM$RPCSS process and eventually leading to the rundown of DCOM$RPCSS with RMS fatal exception.
• The DCE$CDSD process crashed with SYSTEM-F-STKOVF error in background_activator and back_propogate threads.
• DCECP program access violates when issuing an incomplete DCECP -C ERRTEXT command
• The DCE$RPC_SHUTDOWN.COM did not delete the files in dce$local:[var.dced] directory including EP.DB file. This may result in stale entries in EP.DB file, leading to DCE$DCED daemon crash.
• When Pthread metering is enabled, DCE startup fails while starting up CDSD daemon. The process DCE$CDSD crashes with "%SYSTEM-F-OPCCUS"

  2003-09-29-05:49:26.215+08:00I----- cedar$dka0:[sys0.syscommon.] [sy FATAL cds general SERVER_MAIN.C;3 475 0x7bcd0888 Routine pthread_cond_wait failed : status = -1. %SYSTEM-F-OPCCUS, opcode reserved to customer fault at C=FFFFFFFF80A5ED24, PS=0000001B

• When insufficient command line arguments are provided to DCE$DCED while invoking DCED daemon from command line in "Endpoint Mapper" mode using "-x " option, the process crashes with "%SYSTEM-F-ACCVIO", access violation

  $ dced -x dce73$dka100:[sys0.syscommon.][sysexe]dce$dced.exe;1: option requires an argument -- x %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000000, PC=FFFFFFFF806 68324, PS=0000001B

• In DCE Version 3.0, the DCE$CONFIG_PROTSEQ symbol is used in conjunction with RPC_SUPPORTED_PROTSEQS logical to configure DCE with only TCP as the RPC supported protocol. It is possible that missing DCE$CONFIG_PROTSEQ symbol could create a DCE configuration issues. In DCE Version 3.1, the DCE$CONFIG_PROTSEQ is made redundant and hence user is not required to define the symbol DCE$CONFIG_PROTSEQ.
• The DCECP command program loops infinitely if a wrong option is entered at the DCL prompt.

  $ dcecp -x Error: invalid command name "-X" Error: invalid command name "-X" Error: invalid command name "-X"

• The DCECP program on a OpenVMS VAX produces the following output for a null command input.

  dcecp> Error: invalid command name "]ëÉ"

• When stopping DCE$CDSD process using ’cdscp disable server’ command, CMA-F-ALERT, error reported in the DCE$CDSD.LOG file. Here is the error message.

  %CMA-F-EXCCOPLOS, exception raised; some information lost -CMA-F-ALERTED, thread execution has been canceled

• The DCE$CDSD process hangs with the following error

  2002-10-01-21:42:32.552-04:00I0.238 PID#541458706 FATAL rpc recv CNRCVR.C;1 563 0x0d563740(rpc__cn_network_receiver) Unexpected exception was raised

• While compiling the DCE applications, the C++ Compiler Version 6.5 throws out the following warning with STUBBASE.H header file.

  byte_p_t rpc_ss_mem_alloc ( rpc_ss_mem_handle *, unsigned ) ..........^ %CXX-W-TYPNOLNKFUN, use of a type with no linkage to declare a function at line number 988 in file SYS$COMMON:[DCE$LIBRARY]STUBBASE.H;1

• CDS Checkpoint Migration during the DCE Upgrade to DCE Version 3.1 from Version 1.5:
  When you upgrade the DCE for OpenVMS Version 1.5 to Version 3.1 of DCE, you would need to migrate the CDS checkpoint file that are present in the DCE$LOCAL:[VAR.DIRECTORY.CDS] directory before starting DCE with Version 3.1.
  The CDS checkpoint migration procedure is as below:
  The dce$checkpoint.exe image is delivered through DCE Version 3.1 kit and can be located in SYS$COMMON:[SYSHLP.EXAMPLES.DCE.TOOLS] directory.
  Here are the options available with chkmigrate tool:

  chkmigrate <FileName> [-cmvo] FileName Checkpoint file name -c Check whether the file is proper(default) -m Migrate if file condition is not proper -o Overwrite the existing checkpoint file. Otherwise new file name will be <filename>_MIGRATED -v Verbose

  
  Here are the details regarding DCE$CHKMIGRATE.EXE usage:

  1. $ chkmigrate := = $ <device>:[<directory>]DCE$CHKMIGRATE.EXE
  2. $chkmigrate <checkpoint file name>-m
  3. Migrated file name will be <checkpoint file name>_MIGRATED
  4. Rename the original checkpoint file to <checkpoint file name> _OLD
  5. Rename the migrated file checkpoint file name>_MIGRATED to original filename <checkpoint file name>
  
  Please ensure the version numbers of .TLOG* and .CHECKPOINT* are same as the contents of .VERSION file.
  Here is an example:

  Contents of version file

  $ type DCE$LOCAL:[VAR.DIRECTORY.CDS]MR6AXP-CELL_MIRAGE_CH.VERSION;1 0000000010

  The corresponding .CHECKPOINT and .TLOG would be

  MR6AXP-CELL_MIRAGE_CH.CHECKPOINT0000000010 MR6AXP-CELL_MIRAGE_CH.TLOG0000000010

• SELF principal not a member of cds-server, on an upgraded system:
  After DCE upgrade to Version 3.1 from Version 1.5, following warning messages would be reported whenever the user restarts DCE Version 3.1

  2003-05-07-09:29:58.697-04:00I446.824 cdsclerk(13411) WARNING cds clerk clerk_bind.c 793 0x140043050 CDS server principal hosts/HOSTNAME/self is not a member of group subsys/dce/cds-server.

  
  To eliminate these warning messages, perform the following steps:

  1. Startup DCE.
  2. Log in as cell_admin (dce_login cell_admin)
  3. Execute the following command:

  $dcecp -c group add /.../<cell name>/subsys/dce/cds-server -member /.../<cell name>/hosts/<host name>/self

  
  Performing these steps will add the "hosts/<host name>/self" principal to the "subsys/dce/cds-server" group. Subsequently, when DCE starts up, the startup procedure will not generate warning messages.

• The ‘‘Times Lookup Paths Broken’’ counter denotes the number of lookup failures that happened through CDS server while looking for a directory. This counter may get incremented during the DCE startup, which is expected. However, if the counter keeps on incrementing at regular intervals (the default interval is one hour) then there is a possibility of a child pointer of the directory getting corrupted (or) it’s not present.
  When the counter gets incremented, the directory name of the child pointer is logged in into DCE$CDSD.OUT file. Under this condition, you need to delete and recreate the child pointer of the directory to resolve the lookup failures.
  Here is the command to delete and create the child pointer for the directory.

  dcecp> directory remove <parent_directory_name> \ -member <child_pointer> dcecp> directory add <parent_directory_name> \ -member <child_pointer> \ -clearinghouse <clearing_house_name>

  
  Here is the sample example of the Times_Lookup_Paths_Broken counter incremented:

  dcecp> cds show /.: {Creation_Time 2003-09-24-00:23:22.875+08:00I-----} {Future_Skew_Time 0} {Read_Operations 9538} {Write_Operations 49814} {Skulks_Initiated 14129} {Skulks_Completed 14128} {Times_Lookup_Paths_Broken 12} {Crucial_Replicas 0} {Child_Update_Failures 0} {Security_Failures 0} {Known_Clearinghouses /.../csesup-cell/csesup_ch}

  
  The dce$cdsd.out file would contain the message like

  2003-09-24-01:27:27.242+08:00I-----B_pp_c Dir_name:/.../csesup-cell/dir1, check child_pointer

  
  for this you need to recreate the child pointer using the following command:

  dcecp> directory add /.../csesup-cell -member dir1 \ clearinghouse /.:/csesup_ch

  
  The ‘‘Times Lookup Paths Broken’’ counter may also get incremented if the soft link of the directory is corrupt. In this case, you need to delete the soft link and create it if required.

• When a large number of ACMSxp Processing servers are stopped and re-started several times in a loop, DCE goes into a hang state.
• On cancellation of an RPC-call, the BG devices (Sockets) that were allocated are not released. Several such RPC call cancellations can result in a pileup of BG devices leading to a resource leak.
• Memory leak is encountered in DCE/RPC when DCOM is functional in unauthenticated mode.
• The DCE$DCED process terminates with the following error under load:

  (socket) rpc_socket_disp_select *** FATAL ERROR at SOCKDISPATCH.C;1\3755 *** %CMA-F-EXCCOP, exception raised; VMS condition code follows SYSTEM-F-OPCCUS,opcode reserved to customer fault at PC=00000000007043A8, PS=0 000001B %SYSTEM-F-ABORT, abort

• The login context specific to application processes expires immediately after starting ACMSxp TP system. The TP System makes use of credentials obtained after a dce_login with "acmsxp_svr" as the principal name.

  Klist fails with the following error: No DCE identity available: No currently established network identity for which context exists (dce / sec)

• The DCE$DCED process aborts with SYSTEM-F-ACCVIO when a command procedure containing dce_login and ACMSxp commands is executed in an infinite loop.
• DCE Version 3.0 RPC Only configuration fails on systems with TCPWARE as the IP product. The setup procedure issues UCX commands, which would not work on TCP/IP products other than HPs TCP/IP for OpenVMS. The configuration program terminates abnormally.
• There was a case where a NULL pointer check was not being made in RPC Runtime code because of which the process terminates.
• DCE Client configuration fails in certain cell configurations running HP UNIX DCE Servers. Client configuration aborts with the following error message:

  Attempting to locate security server *** Error: can’t locate security server (exiting) >>> getcellinfo: can’t obtain handle to security server Entry not found (dce / rpc)

• DCE startup fails after a system reboot. The startup procedure fails while starting the CDS Name Service Advertiser daemon. DCE$SETUP reports the following error message:

  "Error Starting CDSADVER"

• Configuration Verification Procedure (CVP) on Version 3.0 fails intermittently with the following error message:

  %CMA-F-EXCCOPLOS, exception raised; some information lost -DCERPC-F-COMMFAILURE, communications failure (dce / rpc) DCE for OpenVMS Alpha V3.0 CVP failed.

• On completion of a CVP run, user was prompted twice to Hit the Return Key for displaying the SETUP menu.

  Press <RETURN> to continue . . . Press <RETURN> to continue . . .

  
  DCE$SETUP now displays the SETUP Menu with the first Carriage Return itself.

• While configuring LDAP Clients into a LDAP Server Cell, the DCE$SETUP program does not report the ’password validation failure’ message when there is a password mismatch.
• DCE Online Help was not properly structured. Having all the Help topics at the top level of Help clutters up the DCL Help. New DCE DCL Help Library fixes the problem.
• When a call to rpc_binding_from_string_binding fails, the subsequent calls to this function hang forever. New RPC Runtime library fixes the bug in "rpc_binding_from_string_binding".
• When running DCOM applications between Windows 2000 and VMS systems, several RPC_CN_CREATE_AUTH_INFO messages are logged into the DCOM$RPCSS.OUT file leading to exhaustion in disk space.
  User will need to define logical "DCE_DISABLE_LOGGING" to 1 either system or process wide for disabling the error messages on DCE 3.1 for OpenVMS.

  $ DEFINE/SYSTEM/EXEC DCE_DISABLE_LOGGING 1 (or) $ DEFINE DCE_DISABLE_LOGGING 1

• Failure to detect or ping an active Windows 2000 Client while running Authenticated DCOM between a Windows 2000 and OpenVMS System would cause the DCOM Server applications to timeout and run down after a period of about 10 minutes.

  Several "RPC_CN_AUTH_VFY_CLIENT_REQ" error messages appear in DCOM$RPCSS.OUT file in intervals of 2 minutes 2001-10-02-17:01:58.468-04:00I0.629 PID#330 ERROR rpc auth CNSASSM.C;1 4654 0x01eb9740 RPC_CN_AUTH_VFY_CLIENT_REQ on server failed: invalid handle (dce /rpc)

• Serviceability logging feature does not log the RPC information into the log files, though it creates the file.
• Enabling Kerberos 5 Services on OpenVMS Alpha Version 7.3 and above aborts with the following error message:

  assert error: expression =context->refcount > 0, in file DECW$DCERESD:[SECURITY.CLIENT.RCA.SRC]INTERNAL_BINDING.C;1 at line 2706 %SYSTEM-F-OPCCUS, opcode reserved to customer fault at PC=FFFFFFFF80A5E7F4, PS=0000001B

• RPC Fatal Exceptions are reported in DCOM$RPCSS.OUT when running DCOM applications from Windows 2000 after a new login. DCOM$RPCSS process reports the following exception in the OUT file.

  2002-04-18-15:04:17.604-04:00I0.113 PID#21370 FATAL rpc recv CNRCVR.C;5 563 0x015a5740 (rpc_cn_network_receiver) Unexpected exception was raised

• When the audit daemon is enabled from the dce_setup command procedure, it fails with the following error message:

  ***Could not execute DCECP command: ***Dcecp -c audfilter create world -at {dce_sec_modify {failure denial}all} ***%CLI-W-ABVERB, ambiguous command verb - supply more characters *** Error: dcecp -c audfilter create world -at {dce_sec_modify {failure denial} all} failed (continuing) Audit daemon configuration failed

• DCE client example programs located in [SYSHLP.EXAMPLES.DCE.RPC] generated using IDL "-trace log_manager" option access violate. The access violation occurs when the symbol RPC_LOG_FILE is defined.

  %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000000, PC=0000000000239F68, PS=0000001B

• DCE Startup Procedure hangs during an upgrade from 1.5 to 3.0 in RPC Only Configuration.
• When an invalid dcecp command is entered, the user is returned to the DCL prompt instead of the dcecp prompt. In the example below, after the error is displayed, the "dcecp>" prompt should be output to allow the user to correct the command and continue.

  $ dcecp dcecp> errtext 2350- Error: The value ’2350-’ is not a valid integer error code. $

• An ACCVIO occurs when configuring Kerberos on pre-V7.2 versions of OpenVMS. The installation should not install MIT Kerberos files on pre- V7.2 Alpha systems and configuration should not ask questions for MIT Kerberos support on systems that do not support the option. Below is a sample of the ACCVIO:

  $ dce_setup configure Configuring Kerberos... %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000001,PC=00000000004D0F50, PS=0000001B

• While converting a DTS local server to a DTS global server, the following error is reported:

  *********************** ERROR *********************** ** An error occurred attempting to log in to DCE with *** principal name "cell_admin" Sorry. Password Validation Failure. - cannot log in with zero-length password (dce / sec)

• DCE processes should be able to produce dumps during abnormal termination. In order to be able to produce dumps, user is granted the option of setting the dump logical ’DCE$DUMP_DAEMONS’. The dump daemons logical can be set using:

  $DEFINE/SYSTEM/EXEC DCE$DUMP_DAEMONS 1

• A DCOM user, running in Unauthenticated mode (no NT security credentials), fails, as follows:

  $ run sserver Server: CoRegisterClassObject: (null)(ee1282ca) Server: Done $ set message sys$message: DCE$RPC_MSG.EXE $ exit %xee1282ca %DCERPC-E-CANTLISTENSOCKE, cannot listen on socket (dce / rpc)

• CNSASSM.C is not checking some memory allocation pointers for NULL.
• According to the OSF documentation when a user defined authorization function returns false, the status value from the user supplied function is to be returned to the client. The RPC runtime always returns status "rpc_s_mgmt_op_disallowed" when the user function returns false.
• ETGET and other DCE tools (like ETDMP, ETFMT, etc) should be, but are not installed by the DCE 3.0 upgrade.
• An attempt to start DCE fails after the start of the DCE$SECD daemon. The error "Dcecp server ping was unsuccessful on all endpoints" is output to the terminal. This error message has been changed to:

  Unable to acquire initial login context: Authentication ticket expired. Please restart DCED Which is more descriptive of the real problem and indicates how to fix the problem, i.e. restart DCED

• The DCE security daemon, DCE$SECD, aborts with an ACCVIO. Analysis using the SYS$MANAGER:JPI.COM tool shows the process is continually leaking page file quota.
• DCED can crash with an ACCVIO at VA=0, PC=2C10E4.The DCE$DCED.OUT file shows:

  Delete DCE$SPECIFIC:[VAR.SECURITY.CREDS]DCECRED_0427F700.NC;1: No ticket 11/06/00 23:29:42 - Starting credentials cleanup 11/07/00 00:29:43 - Starting credentials cleanup 11/07/00 01:29:43 - Starting credentials cleanup Delete DCE$SPECIFIC:[VAR.SECURITY.CREDS]DCECRED_043ACA21.;2: Expired Delete DCE$SPECIFIC:[VAR.SECURITY.CREDS]DCECRED_043ACA65.;1: Old version Delete DCE$SPECIFIC:[VAR.SECURITY.CREDS]DCECRED_043ACA67.;1: Empty Delete DCE$SPECIFIC:[VAR.SECURITY.CREDS]DCECRED_043ACA68.;1: Empty 11/07/00 02:29:47 - Starting credentials cleanup 11/07/00 03:29:47 - Starting credentials cleanup 11/07/00 04:29:47 - Starting credentials cleanup %CMA-F-EXCCOP, exception raised; VMS condition code follows -SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=0000000000000000, PC=00000000002C10E4, PS=0000001B

• A DCE server or client process that needs to maintain a login context crashes with an ACCVIO.For example the DCE$CDSCLERK can fail with the following ACCVIO in the DCE$CDSCLERK.OUT file:

  %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000068, PC=0000000000989D50, PS=0000001B

• Cannot configure and start an RPC only configuration on DCE V3.0. Running uuidgen results in the error:

  $ run sys$system:dce$uuidgen %UUIDGEN-F-RPC_MESSAGE, Received Error Status: "no IEEE 802 hardware address"

• kdestroy does not delete the credential files at DCE$LOCAL:[VAR.SECURITY.CREDS]
• During startup, whenever a client application imports the binding information from the name service database using the rpc call rpc_ns_binding_import_next while having less than 13 free event flags the RPC call fails with the ’name service unavailable’ error.
• After 10 to 12 hours DCE$CDSD and DCE$GDAD will ACCVIO. At that moment it is in a process to refresh the Server Identity. However this refresh activity fails with the error "sec_s_login_handle_invalid".
• While modifying DTS configuration from Local Server to Clerk, the DTS entity representing the DTS server still exists in the lan-profile. The server entry should not exist.

  ---

  Previous

  Contents

  Contents