Hi Georg,
>1. Are they errors? > >I found some entries in the log files which looks like errors, but are not >reported as such through pop-up messages or something alike. >Are they errors? > >a) >SYS: "c:\programme\sdb\programs\pgm\regupd" >"c:\programme\sdb\programs\web\config\sapdbxie.reg" "SOFTWARE\SAP\SAP >DBTech\XIE" >SYS: sapdbxie -i: [WARNING] Service registration failed! >SYS: sapdbxie -i: Could not register service at description store: >SYS: sapdbxie -i: Could not open session to registry DB >SYS: sapdbxie -i: [INFO] Service "SAPDBXIE" installed successfully >SYS: sapdbxie -i: Service will use "SOFTWARE\SAP\SAP >DBTech\XIE\SAPDBXIE" This is just a warning. SAPDBXIE tries to register a XML Index Engine with the registry DB. The registry DB is for instance a WebDAV DB. While installing a server, there is no such DB instance. So registration fails. But this is no problem or error. Just as the log states: It is an WARNING. Nothing severe. Once you have a WebDAV DB (once you use WebDAV) and you want to use XML Indexing for WebDAV then you have to register a XML Indexing Engine with the WebDAV DB. How to accomplish that please refer to the documentation: http://www.sapdb.org/7.4/htmhelp/6c/d1813556d46343b8593452e4367752/frameset.htm If you don't use WebDAV or XML Indexing at all you can ignore this warning. If you ask: Well, why does the installation try to register a XML Indexing Engine to a not existing DB instance at all? The answer would be: Suppose you run a WebDAV and you want to add XML Indexing functionallity to it. Then you would install a XML Indexing Engine (there is a separate installation package for it, that is part of the server installation as well) maybe on a different machine that not even has any MaxDB Software on it yet. (Separation could be for performance reasons) Then you could provide the connection parameters for the WebDAV DB (Registry DB) and the installation would register this XML Indexing Engine with the WebDAV DB. You would get no WARNING (well, only if the connect fails and so on ...) Cheers, Daniel -----Original Message----- From: Georg Scheidel [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 10. Dezember 2003 12:46 To: [EMAIL PROTECTED] Subject: MaxDB-7.5.0.5 for Windows - Problems in the Installation Hi, I installed MaxDB 7.5 under Windows 2000 using an user account with administrator rights, but not "Administrator", and I have some comments about the installation process. 1. Are they errors? I found some entries in the log files which looks like errors, but are not reported as such through pop-up messages or something alike. Are they errors? a) SYS: "c:\programme\sdb\programs\pgm\regupd" "c:\programme\sdb\programs\web\config\sapdbxie.reg" "SOFTWARE\SAP\SAP DBTech\XIE" SYS: sapdbxie -i: [WARNING] Service registration failed! SYS: sapdbxie -i: Could not register service at description store: SYS: sapdbxie -i: Could not open session to registry DB SYS: sapdbxie -i: [INFO] Service "SAPDBXIE" installed successfully SYS: sapdbxie -i: Service will use "SOFTWARE\SAP\SAP DBTech\XIE\SAPDBXIE" b) STDOUT: starting installation We, Dec 03, 2003 at 14:07:20 STDOUT: operating system: Windows I386 NT 5.0 Service Pack 4 STDOUT: callers working directory: C:/Scheidel/Databases/MySQL/maxdb-all-win-32bit-i386-7_5_0_5 STDOUT: installer directory: C:/Scheidel/Databases/MySQL/maxdb-all-win-32bit-i386-7_5_0_5 Can't open registry key "HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAP DBTech": No such file or directory STDOUT: STDOUT: existing profiles: c) MSG: no function "verify" in package XML Indexing Engine SYS: sapdbxie -u: [INFO] Service "SAPDBXIE" removed. SYS: sapdbxie -u: [INFO] Un-registration of SAP DB XIE service "SAPDBXIE" successfully d) MSG: write 19 packages MSG: net install registry size = 144365 bytes MSG: wrote install registry (169400 bytes) MSG: no function "register" in package JDBC MSG: no function "unregister" in package JDBC MSG: no function "preuninstall" in package JDBC MSG: no function "postuninstall" in package JDBC MSG: no function "verify" in package JDBC STDOUT: start real extraction of "SDBJDBC.TGZ" e) MSG: no function "verify" in package Database Connectivity STDOUT: skipping package STDOUT: starting preparing phase of package JDBC 7.5.00.02 STDOUT: -------------------------------------------------- WRN: "" is not a valid release format STDOUT: update release check... ok STDOUT: checking interferences to other packages... STDOUT: ok STDOUT: collecting data finished: STDOUT: java driver path: c:/programme/sdb/programs STDOUT: start extraction test run of "SDBJDBC.TGZ" STDOUT: package JDBC successfully checked 2) Treatment of errors If errors are encountered, the user should be prompted to take corrective action! 3) Log files Log files are spread throuout the system in different directories: - the directory where the installation program is started. - the C:\Programme\sdb\... directory There is no severity code such "ERROR" or "FATAL" to search for. 4) Registry entries Under "LOCAL_MACHINE" data is stored in different locations: "SOFTWARE\SAP" "SOFTWARE\SAP AG" 5) Program directories The programs and data are installed in different places: C:\PROGRAMME\SAPDB C:\PROGRAMME\MAXDB Question: What about the messages above - are they errors? How can correct them? Sugestions: 1. Prompt the user when errors are encountered. 2. Clearly mark errors as such in the log files. 3. Use a single place for writing log files. 4. Use a single registry area. 5. Use a common directory for all program components. 6. Provide a documentation section "how to deal with error: XXX?" Mit freundlichen Gr��en, Dipl.-Inf. Georg Scheidel System- und Softwareentwicklung Philotech Buxtehude Germany Tel. 041 61 - 50 20 15 041 61 - 50 20 20 [EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
