How to manually install Muhimbi for eDiscovery
Article ID: 100038456
Updated On:
Description
Description
Technical staff may need to install Muhimbi manually without the aid of the eDiscovery Platform (eDP) installer. This HOWTO describes the steps it takes to install Muhimbi manually and ready it for use with the eDP software.
First make sure there is an independent admin account dedicated to the Muhimbi service that has the admin rights described the eDP installation guide (ie ESADocImager).
Read and understand the following commands. Make substitutions to the arguments based on the pertinent environment.
Muhimbi for eDP version 9.1 and Above:
- Download the Muhimbi Installer Package eDP 9.1_zip.
- Run the MuhimbiSetup.bat and follow the on screen prompts.
- Verify the Muhimbi installation completed successfully via Programs & Features
Muhimbi for eDP version 9.0 and Below:
- Download the Muhimbi Installer Package eDP 9.0 and Below.zip
- Run the MuhimbiSetup.bat and follow the on screen prompts.
- Verify the Muhimbi installation completed successfully via Programs & Features
Caveats:
- If the batch file installation fails with the error "An old version of The Muhimbi Document Converter appears to be installed on this system", make sure that there are no Muhimbi service accounts running, such as EsaImageHelper or DocumentConverterService. If there are, remove them using SC Delete
. - If the installation fails with an Invalid User Name or Password error, check to see if FIPS mode is enabled. Set the following registry key to 0 to disable FIPS mode:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy
Notes
Occasionally it has proved helpful to install Muhimbi and test independent of eDiscovery being installed. This internal portion describes the steps it takes to install Muhimbi manually. If Muhimbi does not work properly using the method below there is almost certainly an environmental issue. Since a standalone Muhimbi can be installed with minimal environmental requirements you can install Muhimbi in and outside any firewall or subnet and further pinpoint the issue. Also this install will automatically use a default Muhimbi eval license so you can determine if there is a license discrepancy.
Requirements:
- Admin account credentials
- Microsoft office with outlook initialized
- Adobe reader
eDiscovery is not a requirement so this technote can be implemented in a wide range of locations.
- Unzip the attached zip file.
- Navigate to the Muhimbi subdir
- Run setup.exe
- Fill in the fields Leave everything as default. Do not enter a license you will get an eval license which is adequate.
- After it is installed navigate to:
- C:\Program Files\Muhimbi Document Converter
- Run Document Converter Diagnostics.exe
- This will pop up a GUI screen
- Choose a source file that you want to convert
- Click the “Convert/Process File” button
Additional information:
For debugging you may want to consider changing the following settings:
Log file location: change the path of the log file name in the appender element to a location of your preference.
Log Level: By default only ‘INFO’ and critical events are logged. To get a better view of what the service is doing, e.g. during a debug session, you may want to consider switching the
In the example below we will switch the logging level to Debug. (Muhimbi.DocumentConverter.Service.exe.config)
Open your Muhimbi Service’s config file (as described here) and change the following from
To
And restart the Muhimbi Service.
Net stop "Muhimbi Document Converter Service"
Net start "Muhimbi Document Converter Service"
http://support.muhimbi.com/entries/21270133-how-do-i-enable-debug-logging
Issue/Introduction
