[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference forty2::x500

Title:	X.500 Directory Services
Notice:	Sprt: FORTY2::X500_SUPPORT, Kits: 216.*, try dir/titl=OFFICIAL
Moderator:	FORTY2::PULLEN

Created:	Tue Jan 30 1990
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1016
Total number of notes:	4299

1016.0. "Create DSA problem" by FGTMTS::SYSTEM () Thu Jun 05 1997 19:09

 I'm installing DXDVE03030 on a VAXstation 4000/90A running VMS V7.0

 - The installation is completed with no errors.
 - I created and enable the dsa as :
   NCL>create dsa
   NCL>set  dsa ae title  "/C=FR/O=Digital/CN=EVODSA1"
   NCL>set  dsa  presentation address =
'"DSA"/"DSA"/"DSA"/NS+49002FAA000400FCBE21,CLNS'
   NCL>create dsa naming context "/C=FR/O=DIGITAL"
   NCL>enable dsa
 
   I got no problems during these phases

   I looked at the log file [dxd$server]DXD$DSA_STARTUP_OUTPUT.LOG, 
   the followings are displayed:

$   show time
   5-JUN-1997 15:25:42
$   run sys$system:dxd$dsa_server_main_v7
Copyright Digital Equipment Corporation 1993, 1995. All rights reserved
Version V3.0-38
4:
*** ERROR *** Unhandled exception in DbMonitor.
Exception reported at 678 in DSA
Exception status value = 4227476
11:
*** ERROR *** Unhandled exception in dispi thread top level routine.
Exception reported at 678 in DSA
Exception status value = 4227476
12:


 - I stopped the DXD$DSA_SERVER process and deleted the 

	DSA-INFORMATION-TREE.SNAPID
	DSA-INFORMATION-TREE.SNAPSHOT000000000001
	DSA-INFORMATION-TREE.UPDATES000000000001
 - I restarted the DSA with DXD$COMMON_STARTUP.COM procedure, recreated the DSA
   and I got the same problem
 
Any ideas ?

Many thanks
Marc

T.R Title User Personal
Name Date Lines

1016.1 a-101.tunnel.crl.dec.com::FORTY2::PALKA Andrew Palka Altavista Directory Thu Jun 05 1997 20:12 9

T.R	Title	User	Personal Name	Date	Lines
1016.1		a-101.tunnel.crl.dec.com::FORTY2::PALKA	Andrew Palka Altavista Directory	`Thu Jun 05 1997 20:12`	9
	The unhandled exception errors may be misleading. I think they indicate that some threads were shut down by an alert operation. If you have no other problems then ignore those messages. (There may be other messages that did not get written to the log file if you killed the process). Andrew

The unhandled exception errors may be misleading. I think they
indicate that some threads were shut down by an alert operation.

If you have no other problems then ignore those messages.

(There may be other messages that did not get written to the log
file if you killed the process).

Andrew