MarkView Bar Code Server - What diagnostic steps should I follow and what information should I gather when there is an issue with MarkView Bar Code Server?
Summary
Applies To
- ERP System: Oracle, Peoplesoft, SAP
- MarkView Version: All Versions
Behavior
Troubleshooting steps to follow if you encounter an issue with the MarkView Bar Code Server.
Known Causes
MarkView Bar Code Server recognizes and processes bar codes on documents that come through the MarkView suite. Working in conjunction with another application, such as MarkView Fax Server, you can receive bar coded documents and route them through your workflow using MarkView Bar Code Server.
Resolution
Troubleshooting steps for Bar Code Server:
Review log files for errors
- If the Bar Code Server is not functioning correctly then you will want to review the log files for any error messages. See the "Logging" section below for logging information.
Check pre-requisite software
- To check the versions of pre-requisite software please review the following Support Article:
All MarkView Components - Supported versions of third party products
Ensure Kofax configuration is correct
- In order for the Bar Code Server to recognize bar codes the Kofax software needs to be configured with a default source of 'Import from disk with image processing'. For instructions on how to configure the Kofax source you can review the MarkView 6.2 Installation Guide -> CHAPTER 9 'Installing MarkView Bar Code Server' -> 'Bar Code Setup on the Host Computer' (Note that this section of the documentation applies to all versions of MarkView.)
Troubleshooting Poor Recognition Rates
- All MarkView Versions
- Try printing the bar code coverpage in landscape mode instead of portrait. By changing the orientation of the page, streaking and lines that may be caused by the fax machine are less likely to render the barcode unreadable.
- For customers running Oracle Applications you can add instructions to your iExpenses coversheet to have your users print in landscape mode. For MarkView 6.1 and higher instructions for altering the coversheet can be found in the MarkView 6.2 System Administration Guide -> Section 2: Solutions -> Chapter 21 'MarkView Expense Management' -> 'Providing Submission Instructions'. For other versions please refer to the corresponding version of the documentation.
- See if the barcode can be recognized directly in VCDemo
- Retrieve the actual TIF file from the Document Server.
- Run the TIF file through VCDemo following the instructions in the following Support Web Answer. By using VCDemo you can modify some of the settings to see if you can find a successful configuration which recognizes the failed barcode.
- If the barcode recognizes successfully in VCDemo but not in the Bar Code Server please review the following Support Web Answer:
- Retrieve the actual TIF file from the Document Server.
- If you have already tried the suggestion above, and still have a low bar code recognition rate, you do have the option to contact your Kofax MarkView Practice Manager to inquire about purchasing a license for Enhanced Bar Code Recognition.
- If you do choose to purchase a license for Enhanced Bar Code Recognition, after enabling the license for Enhanced Bar Code, you will need to edit the markview.ini file by adding the following two lines, and restarting the Bar Code Server Service. ( The markview.ini file is typically located in the c:\windows directory.)
[Barcode Server Imgp1]
BarAlgorithm=2
- If you do choose to purchase a license for Enhanced Bar Code Recognition, after enabling the license for Enhanced Bar Code, you will need to edit the markview.ini file by adding the following two lines, and restarting the Bar Code Server Service. ( The markview.ini file is typically located in the c:\windows directory.)
- Try printing the bar code coverpage in landscape mode instead of portrait. By changing the orientation of the page, streaking and lines that may be caused by the fax machine are less likely to render the barcode unreadable.
- MarkView Versions 5.x to 5.10x
- If after having your users print in landscape mode you do not see an improvement in the recognition rate of your barcodes, please review Support Article 1339 which contains instructions on how to generate the bar code vertically which may help improve the recognition rate.
Enable Debug Logging
- MarkView Versions 4.x to 5.0
- To run the server in debug mode the following steps can be taken:
- Stop the Bar Code Server
- Add the following line to the [MarkView Bar Code Server] section of the markview.ini file which is located in the c:\windows or c:\winnt directory.
DebugMode_YesNo = Yes - Start the Bar Code Server
- MarkView Versions 5.5 and higher
- On the machine where the Bar Code Server is installed please create the following registry key with a value of "True", where <INSTANCE> should be replaced with the name of the Bar Code Server instance in your environment.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MVBarCodeServer_<INSTANCE>\Parameters\DebugMode - Restart the Bar Code Server Service.
- On the machine where the Bar Code Server is installed please create the following registry key with a value of "True", where <INSTANCE> should be replaced with the name of the Bar Code Server instance in your environment.
Disable Debug Logging
- MarkView Versions 4.x to 5.0
- Stop the Bar Code Server
- To disable debug logging set the
DebugMode_YesNoparameter to No in the [MarkView Bar Code Server] section of the markview.ini file which is located in the c:\windows or c:\winnt directory. - Start the Bar Code Server
- MarkView Versions 5.10.x and higher
- On the machine where the Bar Code Server is installed please set the following registry key to a vlue of "False" where <INSTANCE> should be replaced with the name of the Bar Code Server instance in your environment.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MVBarCodeServer_<INSTANCE>\Parameters\DebugMode - Restart the Bar Code Server Service.
- On the machine where the Bar Code Server is installed please set the following registry key to a vlue of "False" where <INSTANCE> should be replaced with the name of the Bar Code Server instance in your environment.
Log File Location
- MarkView Versions 4.x to 5.0
- Open the MarkView Bar Code Server and choose File -> Preferences then select the Log tab. The 'Log to File' tab contains the location and file name of the Bar Code Server log file.
- MarkView Versions 5.5 and higher
- File Location: All MarkView Components - Log File Locations
- File Name(s): Windows Event Viewer
Impact of debug logging
- MarkView Versions 4.x to 5.0
- With debug logging enabled the log file will grow at a rate of 2KB per document page that goes through the Bar Code Server for recognition.
- MarkView Versions 5.5 and higher
- There is no debug logging available for MarkView 5.5 and higher.
Known Issues
- MarkView Versions 4.x to 5.0
- Bad Filename: processing halted on Bar Code Server
- MarkView Versions 5.5 and higher
- Bad Filename: processing halted on Bar Code Server
If the following error is encountered when configuring MarkView Barcode Server, ensure your host machine has met the requirements for ODAC for the Windows version and bitness per the Technical Specification document:
DEFAULT_BARCODE_SERVER is not a valid server name
If using Windows 2016, then ODAC 12 is required.
If you install ODAC 11 on the server, note that the ODAC 11 installer doesn't remove the key from the registry. That means that when you install Barcode Server, the installer checks that key in the registry, finds that and does NOT install oip11.dll which ultimately results in this connection error. So, you have to leave ODAC 11 installed once installed. If you never installed ODAC 11, and just install ODAC 12, that should work.
Keywords: barcode diagnostics gather