General configuration and how-to articles for SimpleIndex.
Fixes for Service not Correctly Running
Please refer to the Wiki Documentation for the complete Index & Batch Logging reference.
If the Service stops and isn’t running properly there can be a variety of different causes for this. You can follow the procedures below to fix this in most cases.
Check Event Log, which is here:
Administrative Tools>Event Viewer>Windows Logs>Application
Then select “Filter Current Log…” on the right
and in the “Event sources:” field drop down pick these: SimpleIndex, SimpleIndex Service & SimpleIndexService (and anything else that says SimpleIndex)
Look at the errors, which will tell you why it’s not working.
Find the Temp folder for SimpleIndex and delete any batches that are there after stopping the Service in the SimpleIndex Service Control and Options Panel
Clear Registry of the Temp Files
HKEY_USERS\(User ID for the User Running the Service)\Software\SimpleIndex\
Then delete the folders for the names of the Configurations that are not starting in the Service Control Panel
Skip to Blank Index on Save Index
Please refer to the Wiki Documentation for the complete Index & Batch Logging reference.
If you would like to have SimpleIndex automatically go to the next page with a blank field and highlight that field when the Save Index button or Enter a change to the XML text of the Job Configuration is needed. This can be useful to quickly move to the next document that has a blank Index field.
Instructions to set Skip to Blank index on Save Index:
- Right click on the Job Configuration file that you would like to suppress the prompt on and select Open With>Notepad
- Search the XML settings text open in Notepad for this term:
<SKIP_TO_NEXT_BLANK> - Set the value between from “False” to “True”
<SKIP_TO_NEXT_BLANK>True</SKIP_TO_NEXT_BLANK> - Save and close the file.
Stop Autorun When Double Clicking Configuration
Please refer to the Wiki Documentation for the complete Settings Wizard reference.
SimpleIndex jobs can be launched from an icon, just like opening a Word document saved on your desktop. However when you do this the default behavior is to automatically run the job file once it opens in SimpleIndex. If you just want to open the job without running it, follow these instructions:
1. Create a shortcut to the configuration by right clicking on the configuration file and selecting “Create shortcut”
2. Right click on the Shortcut that was just created and saved and select “Properties”
3. In the “Target” field put the following:
“C:\Program Files (x86)\SimpleIndex\SimpleIndex.exe” /c:”<Full Path to Configuration file>” /m
Example:
“C:\Program Files (x86)\SimpleIndex\SimpleIndex.exe” /c:”C:\Images\test.sic” /m
Workstation Activation in the Concurrent Serial Number Field
Please refer to the Wiki Documentation for the Licensing & Activation reference.
If you are getting really weird activations errors where it says the license has already been activated the client has probably put the Workstation serial code in the Concurrent spot that is in the Wizard.
To fix this go to the registry (regedit) here:
HLM\Software\Wow6432Node\SimpleIndex\Registration
Then delete the key called Serial
Sharing Violation – Anti-Virus
If you get Sharing Violations during the processing, usually with the Temp folder, and you can’t figure out why it is probably the Anti-Virus software. Turn off the real time virus scan and it should fix it.
Continue with Post Process Command Line if Input Folder is Empty
Please refer to the Wiki Documentation for the complete command line interface reference.
When running multiple jobs in a row or chain with the Post Process Command Line it is possible that an earlier Job in the process won’t have any files. This will stop the Job before reaching the Post Process step and cause later jobs not to run.
This can be corrected by adding an option directly to the XML text of the Job Configuration. This will tell it to keep going to the Post Process step even if there are no files to process in the Job.
Instructions:
- Right click on the Job Configuration file (.sic file format) and select Open With..
- Select Notepad or some other text file opening software.
- Search for this in the text of the file: <POSTPROCEMPTY>false</POSTPROCEMPTY>
- Change the word “false” to the word “true” in that section.
- false = Stop immediately if there are no files to process.
- true = Run the Post Process Command Line even if there are no files to process
- Save the file and close it.
Overlap of SimpleView Viewer in SimpleIndex Display
Please refer to the Wiki Documentation for the SimpleView interface reference.
Occasionally on certain Windows displays the SimpleView viewer sub-window in SimpleIndex will extend over the Index fields causing the user to not be able to interact with them or click Save All/Save Index or use the Mouse Actions. This seems to happen more with ultra-high resolution monitors like a 4K monitors or the Surface Pro. You will see something like this:
The fix for this is relatively simple by using the High DPI Scaling in Windows. You can find the instructions for this below.
Windows 10 Instructions:
- Open Windows File Explorer and go to this folder: C:\Program Files (x86)\SimpleIndex
- Find the SimpleIndex.exe
- Right click on the SimpleIndex.exe and then select Properties
- Go to the Compatibility tab
- Click the button called “Change high DPI settings”
- Check the boxes labelled “Use this setting to fix scaling problems for this program instead of the one in Settings” and “Override high DPI scaling behavior. Scaling performed by:”
Windows 7 Instructions:
- Open Windows File Explorer and go to this folder: C:\Program Files (x86)\SimpleIndex
- Find the SimpleIndex.exe
- Right click on the SimpleIndex.exe and then select Properties
- Go to the Compatibility tab
- Check “Disable display scaling on high DPI settings”
Once you make this change reopen SimpleIndex and you display will be correct.
Notes: After enabling this setting there might some oddities with the toolbars and navigation buttons, but they are all readable and working, and the menus work. The old job settings has several issues with this, but it has been replaced with the wizard which does not.
Sort Lists Error – HexUniControl Module
Please refer to the Wiki Documentation for the complete Job File reference.
If you have an error when manually changing the values in a List type index field that says “HexUniControl” then it’s an issue with the way SimpleIndex sorts the values in the list that the drop down is accessing. This sorting needs to be turned off to avoid this error. The instructions to turn this list sorting off are below. Instructions:
1. Right click on the configuration file and select Open With>Note Pad or Open With>Word Pad or any text editor.
2. Search for this term: SORT_LISTS
3. Find the entry, which should look like this: <SORT_LISTS>true</SORT_LISTS>
4. Set the true value to false.
Troubleshooting SharePoint Permissions Issues
Please refer to the Wiki Documentation for the complete SharePoint reference.
The problem was being caused by the fact that the root site on the server did not grant the users read access.
For example, imagine they are trying to upload to:
” http://server/sites/mysite/test.pdf ”
The user has full permissions on mysite, but if they try to access http://server/ they get permission denied. Even though the user can upload to mysite, they cannot upload with SimpleIndex because the client objects require permission on the root site.
Granting the users at least read access to the root site at http://server/ resolves the issue.
SharePoint Managed Metadata
Please refer to the Wiki Documentation for the complete SharePoint reference.
If a SharePoint user has a Managed Metadata column that they need to set the value for in SimpleIndex, the value they must use is the unique ID for that metadata value, not the value itself.
SharePoint 2010
To find the unique ID, go to a document library that uses the managed metadata column and view the documents in Datasheet view. The unique ID is the part before the semicolon in that column. In the example below, the ERM Classification of “Electric Deal Tickets” has an actual value of “1”.
You will need to have a document with each possible value in order to get all the values this way. If there are a great number of possible values, it is possible to use a script to download them or to pull them directly from the SharePoint database.
SharePoint 2013 & Office365
For SharePoint 2013 and Office365 you need to use the GUID identifier for the taxonomy term. To get the actual value for a managed metadata term, you can use the Unique Identifier that is displayed when you edit the terms in Term Store Management.
In order to get the full list of unique ID values, follow the steps on this here. Use this list to create an autofill table that will replace the text value with the unique ID and map that field to your column in the database.
Users may have access to other tables and views that aren’t in their schema. When connecting to the database these tables will show up in the list, but when you try to get the list of fields you get an “Invalid object reference” error.
To reference these tables, use [Schema].[Table] for the table name to explicitly reference the table.
You can also change the user’s default schema on the server to the one matching the table.
A third option is to create a view under the user’s default schema that selects the necessary records.
At the present time you cannot enter [Schema].[Table] in the wizard, so if you need to use this workaround configure the job in the wizard and modify the table name in the old job options screen.
Using alternate database schemas
Please refer to the Wiki Documentation for the complete Database reference.
In SQL Server, Oracle and MySQL (among others) user logons are associated with a default “schema” that determines which tables and views they can see.
Users may have access to other tables and views that aren’t in their schema. When connecting to the database these tables will show up in the list, but when you try to get the list of fields you get an “Invalid object reference” error.
To reference these tables, use [Schema].[Table] for the table name to explicitly reference the table.
You can also change the user’s default schema on the server to the one matching the table.
A third option is to create a view under the user’s default schema that selects the necessary records.
At the present time you cannot enter [Schema].[Table] in the wizard, so if you need to use this workaround configure the job in the wizard and modify the table name in the old job options screen.
Multiple Sort Fields on Search
Please refer to the Wiki Documentation for the complete Search reference.
If you have a Search/Retrieval configuration that you want to have Sort by more than one column do the following.
1. Open the configuration pad in Notepad.
2. Search for the option value <SORT_FIELD>
3. Normally there is one value in the section that looks like this: <SORT_FIELD>FIELD1</SORT_FIELD>
4. Add the fields that you want to search by as the database columns like this: <SORT_FIELD>[FIELD1],[FIELD2]</SORT_FIELD>
Service Configuration Paths
Please refer to the Wiki Documentation for the complete Job File reference.
The paths to the configuration files that are stored in the list in the Service Control and Options panel is located in the registry here:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SimpleIndexService\Jobs
Forward Blank Index Fields
Please refer to the Wiki Documentation for the complete Index Fields reference.
To turn on the carry Forward when you blank out an index field do the following:
1. Right click on the configuration file and open with Notepad or another text editor.
2. Search for this XML value: FORWARD_BLANK
3. Set the value to true
Do Not Combine Pages to 1 Bookmark
Please refer to the Wiki Documentation for the complete PDF Bookmarking reference.
If you want to keep pages in bookmarks separate instead of combining them into a single bookmark when the same bookmark value is found in several interspersed images in the batch do the following:
1. Open the Job Configuration file in Notepad.
2. Search for this value: <BOOKMARK_PDF1>
3. Enter this directly above the line that has <BOOKMARK_PDF1> if its not already there: <BOOKMARK_UNIQUE_LEVELS>-1</BOOKMARK_UNIQUE_LEVELS>
4. -1 is the default value and that means that no pages should be combined into one bookmark unless they fall in order. 0 means that the first bookmark level should be combined into one bookmark value and the rest should not. 1 means that the first and second bookmark levels should be combined and the rest should not be. ETC.