Jump to content

Recommended Posts

Posted

I've got a problem with eclipse.net, i think we're one of very few schools that uses the self issue system...ever since they did their relatively recent update (earlier this year/late last year?) which changed everything quite significantly, the self issue system hasn't been able to see any of the biometric data. We're using identikit, and when we ring MLS they tell us it should be in a specific file in a specific location on the PC with the finger print reader attached.....well that file either doesn't exist or is empty.

 

As far as i can tell that data is held within the database, not a file on the PCs like they're constantly saying to me. The finger print stuff works fine on circulate for example, just not on self issue.

 

Question is, does anyone here have any idea where the data is actually held for MLS biometrics?

 

The most frustrating thing is that they expect us to know where it's stored.......our answer is "well you made the software, you supplied the kit, you tell me!"

Posted

If you're running a recent server version, the original hardware support plugins provided with the update and linked to in the documentation, won't work any more. Also, MLS doesn't have a link to download the new version on their Downloads page.

Hardware Plugin version 2 is available here: [http://supportfiles.microlib.co.uk/ieplugin.exe]

 

Once installed:

Run [MLS.Biometric.Config.exe] in [Program Files\Micro Librarian Systems\MLS Hardware Support\Bin\]

Click on the [Operation Mode] tab.

Change Mode to [Remote] and fill in the server details.

Click [save]

 

Hope that helps :)

Posted

Thanks, but unfortunately i've done all that.

 

Our librarian has two PCs, hers and her self issue one. She can scan a finger and register it on hers, and reuse it fine, when she moves to the self issue machine it doesn't pickup those finger prints. Both have the same version of the hardware plugin and the same configuration in terms of biometric setup. Which seems as though those finger prints are going into a local .dat file, but they can't be because i've renamed the .dat on her machine and it still continues to work...i've tried opening that .dat in the viewer as well but every time it lists two fingerprints with no name on them and doesn't let me do anyhting with them.

 

Going to reimage the self issue machine now and reinstall it all from scratch to see if that helps (really scraping the barrel for ideas), not going to hold my breath though.

Posted

In the upgrade guide there is this small statement:

 

If you are using a Biometric reader provided by MLS (and one that is not Biostore) thenan essential part of the upgrade process is to convert the biometric data before theupgrade has taken place. See further instructions on doing this, here.

 

the here references page 27 of this guide.

 

In short the old version of eclipse hosted the thumb prints in the database in the new version its in a standalone file, before you upgrade you need to cnvert/ extract the data.

 

Did you take a backup before you did the upgrade?

Posted
In the upgrade guide there is this small statement:

 

 

 

the here references page 27 of this guide.

 

In short the old version of eclipse hosted the thumb prints in the database in the new version its in a standalone file, before you upgrade you need to cnvert/ extract the data.

 

Did you take a backup before you did the upgrade?

 

This is for new biometric data. In typical eclipse support fashion they attempted to convert the existing data for us (we sent them an entire copy of our database) and said it couldn't be done...

 

So we've started from scratch in september, but the self issue software just isn't seeing the biometric data at all.

Posted

Where are you getting your self service version from?

 

There is one of the microlib support site under downloads and there is another that is part of the ieplugin that AXE gave the link for. If your on the latest version you need to be using the selfservice.exe that is in the plugin install directory.

 

By default the biometric data is stored in a .dat file located in C:\Program Files\Micro Librarian Systems\MLS Hardware Support\App_data this is information MLS should have given you TBH.

Posted (edited)
Where are you getting your self service version from?

 

There is one of the microlib support site under downloads and there is another that is part of the ieplugin that AXE gave the link for. If your on the latest version you need to be using the selfservice.exe that is in the plugin install directory.

 

By default the biometric data is stored in a .dat file located in C:\Program Files\Micro Librarian Systems\MLS Hardware Support\App_data this is information MLS should have given you TBH.

 

The new one is an app that looks like it was made by a 5 year old and is the one I'm using (the one that's part of the plugin) it used to be on the old version that you'd get an icon in the tray and right click it to open selfissue (which worked perfectly btw) now you have to run the exe from within the MLS hardware support folder.

 

Nothing at all on either PC within that folder location, and that's the information MLS gave me, it's reading biometric data fine on one PC, but the other one sees nothing.

 

I've just wiped a PC with a completely fresh image, installed the plugin software, enabled idenikit in IE (compatability mode + added to trusted sites, and run the UI tab registry fix) tested a finger and it says no fingers matched, i've then registered my finger on that second PC, which now works fine (important to note, still no .dat file in that folder) i've then opened selfissue and it still doesn't see the same finger i registered on that same machine.

 

I haven't tried going back to the original PC and using my finger i registered on the second pc on that, but i can't see it working anyway seeing as it doesn't work the other way around.

 

Why is something that should be so simple made so complicated >_<

 

To be honest i just want to completely abandon eclipse now, I'm too busy to be messing with something we pay support for that they should be fixing themselves. We seriously need a better company for our library software (although it's my impression from past threads that most library solutions are equally poor)

Edited by mrbios

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...