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

Conference bulova::decwindows

Title:DECWINDOWS
Notice:DECwindows Motif V1.2-4 SSB kits: note 5519
Moderator:GRIM::MESSENGER
Created:Wed Nov 28 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5861
Total number of notes:24081

5806.0. "UID file version mismatch - DRMNotValid error" by MUNICH::STEFAN () Mon Mar 17 1997 05:33

Please Help !

   I have a customer who tries to start DATATRIEVE via 
	
	$ DATATRIEVE

	under OpenVMS 6.1

	and gets the following error message:

X Toolkit Warning: DRM: I18NOpenFile: Couldn't open file VAX_DATATRIEVE - UID
file version mismatch - DRMNotValid
X Toolkit Warning: Drm__OpenHierarchy: �� - DRMNotValid


 I let the customer do the following :
	
 1) Removing the file VAX_DATATRIEVE.UID and using a version from a
    another system where he can start DATATRIEVE.
	
  Result: same error message 

 2) Checking if there is a another versions of  VAX_DATATRIEVE.UID
    elsewhere in the system 

    $ DIR/FILE_ID SYS$SYSDEVICE:<000000...>VAX_DATATRIEVE*

  Result : only one FID 
	
 2) Using AUDIT in order to find out which images are used during the 
    startup of DATATRIEVE

$ SET NOON
$ SET AUDIT/SERVER=NEW_LOG
$ SET AUDIT/AUDIT/ENABLE=ACCESS=ALL
$! "execute application"   ( $ RUN x, @ x, ... )  run the application
                                                ! in an environment
                                                ! (account... )
                                                ! where the error
                                                ! occurs and also
                                                ! where it not occurs.
                                                ! Look for differences
$ DATATRIEVE
$ SET AUDIT/AUDIT/DISABLE=ALL
$ SET AUDIT/SERVER=NEW_LOG
$! SET AUDIT/AUDIT/ENABLE=ACCESS=ALL             ! Your default SET AUDIT....
$ EXIT


 Customer sent me this back ( Images witch are requested from DATATRIEVE ) 
 but I can not see what is wrong ? 
 ( $ SET WATCH gave me also no new information. ):
 
==> image name: "CDDEXC"
image file identification: "CDD V5.1-0"
link date/time:  1-JUL-1992 11:01:39.14
linker identification: "05-05"
==> image name: "CDDSHR"
image file identification: "CDD V5.1-3"
link date/time:  4-NOV-1992 16:20:10.62
linker identification: "05-09"
==> image name: "CMA$TIS_SHR"
image file identification: "CMA V2.11-152"
link date/time:  9-MAR-1994 01:31:54.49
linker identification: "05-13"
==> image name: "COBRTL"
image file identification: "COBRTL V5.0-008"
link date/time: 14-MAY-1992 18:08:43.99
linker identification: "05-05"
==> image name: "DECC$SHR"
image file identification: "V06.0-64"
link date/time: 16-MAR-1994 18:19:10.34
linker identification: "05-13"
==> image name: "DECW$DWTLIBSHR"
image file identification: "DW V1.2-4960313"
link date/time: 13-MAR-1996 11:20:39.53
linker identification: "05-05"
==> image name: "DECW$DWTMSG"
image file identification: "DW V1.2-4960311"
link date/time: 11-MAR-1996 17:48:34.43
linker identification: "05-05"
==> image name: "DECW$DWTSHR"
image file identification: "DW V1.2-4960313"
link date/time: 13-MAR-1996 11:29:29.99
linker identification: "05-05"
==> image name: "DECW$TRANSPORTMSG"
image file identification: "DW V6.1-940212"
link date/time: 12-FEB-1994 18:10:44.58
linker identification: "05-05"
==> image name: "DECW$TRANSPORT_COMMON"
image file identification: "DW V6.1-940212"
link date/time: 12-FEB-1994 18:10:13.64
linker identification: "05-05"
==> image name: "DECW$TRANSPORT_DECNET"
image file identification: "DW V6.1-940212"
link date/time: 12-FEB-1994 18:10:27.01
linker identification: "05-05"
==> image name: "DECW$XLIBMSG"
image file identification: "DW V1.2-4960311"
link date/time: 11-MAR-1996 17:48:44.17
linker identification: "05-05"
==> image name: "DECW$XLIBSHR"
image file identification: "DW V1.2-4960823"
link date/time: 27-AUG-1996 16:55:02.58
linker identification: "05-05"
==> image name: "DECW$XTSHR"
image file identification: "DW V1.2-4960313"
link date/time: 13-MAR-1996 11:28:13.49
linker identification: "05-05"
==> image name: "DTR32"
image file identification: "VAX DTR V6.0-0"
link date/time: 27-APR-1993 12:52:12.89
linker identification: "05-13"
==> image name: "DTRMSGS"
image file identification: "DEC DTR T7.1-2"
link date/time: 21-DEC-1995 11:24:57.50
linker identification: "05-13"
==> image name: "DTRSHR"
image file identification: "DEC DTR V7.1"
link date/time:  6-MAR-1997 13:40:30.04
linker identification: "05-13"
==> image name: "FDVMSG"
image file identification: "V2.3-004"
link date/time: 26-JAN-1989 18:22:00.82
linker identification: "05-02"
==> image name: "FDVSHR"
image file identification: "FMS V2.4"
link date/time: 26-JAN-1989 18:22:50.74
linker identification: "05-02"
==> image name: "FORETELL"
image file identification: "VMS V6-002"
link date/time:  9-MAR-1994 01:34:29.24
linker identification: "05-13"
==> image name: "LBRSHR"
image file identification: "X-1"
link date/time:  9-MAR-1994 01:48:11.76
linker identification: "05-13"
==> image name: "LIBRTL"
image file identification: "V06-001"
link date/time:  9-MAR-1994 01:30:02.21
linker identification: "05-13"
==> image name: "LIBRTL"
image file identification: "V05-000"
link date/time:  9-MAR-1994 01:30:24.44
linker identification: "05-13"
==> image name: "NCSSHR"
image file identification: "V52-03-1"
link date/time:  9-MAR-1994 01:50:20.03
linker identification: "05-13"
==> image name: "RDBMSGS"
image file identification: "RDBDISPV4.2-2"
link date/time: 26-JAN-1994 13:44:35.55
linker identification: "05-05"
==> image name: "RDBSHR"
image file identification: "RDBDISPV4.2-2"
link date/time: 26-JAN-1994 13:46:14.15
linker identification: "05-05"
==> image name: "SECRETOR"
image file identification: "X-5"
link date/time:  9-MAR-1994 01:36:38.51
linker identification: "05-13"
==> image name: "SECURESHRP"
image file identification: "X-5"
link date/time:  9-MAR-1994 01:36:27.35
linker identification: "05-13"
==> image name: "SHRIMGMSG"
image file identification: "X-2"
link date/time:  9-MAR-1994 02:26:41.50
linker identification: "05-13"
==> image name: "SMGSHR"
image file identification: "V06-001"
link date/time:  9-MAR-1994 01:34:17.24
linker identification: "05-13"
==> image name: "MTHRTL"
image file identification: "VMS V6-002"
link date/time:  9-MAR-1994 01:32:45.28
linker identification: "05-13"
==> image name: "VAXCMSG"
image file identification: "V6.0-013"
link date/time: 16-MAR-1994 18:27:12.68
linker identification: "05-13"
==> image name: "VAXCRTL"
image file identification: "V06-007"
link date/time:  9-MAR-1994 01:37:39.79
linker identification: "05-13"

Software :

DECwindows ident is			DW V1.2-4960823
DECwindows server ident is		DW V6.1-940212
DECwindows transport ident is		DW V6.1-940212
DECwindows xlib ident is		DW V1.2-4960823
DECwindows OF/Motif Toolkit ident is	DW V1.2-4960823
DECwindows opts ident is		DW V1.2-4960312
DECwindows programming ident is		DW V1.2-4960311


 Any idea what to check ?

	Regards,
		Stefan Geisen
T.RTitleUserPersonal
Name		DateLines
5806.1GRIM::MESSENGERBob MessengerMon Mar 17 1997 11:264
What is the image file identification of the DECW$DWTLIBSHR.EXE image on
the system where the customer can run Datatrieve?

				-- Bob
5806.2Try Reinstalling The Kit...XDELTA::HOFFMANSteve, OpenVMS EngineeringMon Mar 17 1997 16:0116
   Rather than pulling pieces of products around, please first try to
   reinstall the appropriate version of the Datatrieve kit, or install
   the current version of the Datatrieve kit.  (Pulling apart kits and
   copying files around is one of the way folks get _into_ these sorts
   of weird problems -- sometimes, the kit files don't get relocated or
   reprotected correctly, etc.)

   Datatrieve V7.1 is the current release.

   (And -- if this is not a result of a "creative" local system or file
   configuration, you'll want to report this to the Datatrieve folks.)

   Datatrieve conferences:
	IAMOK::DTRDIG
	VARESE::DTR_BUGS
5806.3NETRIX::&quot;[email protected]&quot;Tue Mar 25 1997 05:1628
 Hi,
     Thanks for the replies.
( Sorry for the delay, but the customer was not contactable... )

  1)   What is the image file identification of the DECW$DWTLIBSHR.EXE image
on

        the system where the customer can run DATATRIEVE ?
        ==>     Image name: "DECW$DWTLIBSHR"
                image file identification: "DW V1.2-4960313"
                link date/time: 13-MAR-1996 11:20:39.53
                linker identification: "05-05"

   2)  .. reinstall the appropriate version of the Datatrieve kit..

        Sorry, I did not mention that before the customer replaced the
        UID file ( because sometimes this file can be corrupted ) he had
        already reinstalled DATATRIEVE 7.1

        Installing DATATRIEVE 7.1 again and also making sure that there
        is only  one VAX_DATATRIEVE.UID file produced the same error.

 So, I have no idea what to check. 
 I am going to include this Notes Entry into the IAMOK::DTRDIG notes file

Regards,
        Stefan
[Posted by WWW Notes gateway]
5806.4NNTPD::&quot;[email protected]&quot;Mon May 05 1997 09:336
Solution :
    The customer had under
    SYS$SPECIFIC:[SYSEXE] an old image of DTR32 ( DATATRIEVE )
    from 1993 ;-)
Stefan
[Posted by WWW Notes gateway]