Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    "Unable to find id" errors for message.dat in Print Daemon


    • Product: Aleph
    • Product Version: 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care



    When we activate the GUI Print Daemon, printing is interrupted between each slip by the following messages:

      Unable to find id: PrintUtilEnd in file: message.dat
      Unable to find id: PrintRemote ToDir in file: message.dat
      Unable to find id: Print Error Number in file: message.dat


    This occurred because a new message.dat file was distributed as part of version 23.3 (v23 rep_change 003046).

       As described in this article, Version Check hasn't picked it up because it's looking at /exlibris/aleph/a23_1/aleph/pc_exe/sp_exe on the server (rather than /exlibris/aleph/a23_1/aleph/pc_exe/sp_conf).  
       Since you have almost certainly made no local changes to this message.dat file, English-language customers can replace the .\alephcom\tab\eng\message.dat on your PC with the new one ( attached to this Case.  (Rename the existing alephcom message.dat file to message.dat.old and then rename the to message.dat.  Then restart the GUI client and the print daemon.)  


    • Article last edited: 19-Aug-2020
    • Was this article helpful?