Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 686
  • Last Modified:

Docrecord unable to populate fields

Hello,

I currently support a client that is running Docrecord software by Prism which they use to manage their scanned documents.  They also have an old proprietary system running on linux which stores all their old customer information.  Bascially the process is they scan an invoice into Docrecord.  Once in docrecord, it then reads the invoice number from the scanned document.  This can also be manually typed in if it doesnt read properly.  They are then able to hit the "populate" button which connects to the old linux systems database and pulls in fields such as Customer Name, Invoice Date, Work Order Numbers, ETC.  Everything was working fine until we had to re-IP the old linux box.  I was able to locate an ODBC connector on the Docrecord server and repoint it to the new IP.  Connections test fine however we are still unable to "Populate" the fields from the old linux system to docrecord.  

This is the error we get:
Auto-Populate failed.
Unable to connect to the Auto-Popluate source.
Auto-Populate failed.
0
NENS24
Asked:
NENS24
  • 6
  • 5
1 Solution
 
Chris HInfrastructure ManagerCommented:
Look at these registry keys:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms714818(v=vs.85).aspx

On older programs like this, there was always a network utility or tool to set up TCP/ip or name pipes and then enter an IP address for the host DB server.  I'm assuming you've set everything up correctly except for a .ini file in the clients program directory.

Also, is there a map drive that may need to get repointed?  Run your login script on a broken computer with now @echo off and see if you see any errors mapping drives.
0
 
NENS24Author Commented:
Hello Choward,
Thanks for getting back so quickly.  I took a look at the link above.  The odbc.ini contains all the connectors i was able to successfully repoint and test.  The odbcinst.ini doesn't seem to contain anything that needs to be changed.  I reviewed these settings on both the docrecord server and the terminal server.  I'm guessing all the changes that need to be made will be directly on the docrecord server as the clients do not have an ODBC connector setup.  The ODBC connectors were only changed on the docrecord server as those were the only ones previously setup.  Also, to help clarify things, the docrecord server didn't have an IP change so the mapped drives to that server are still the same.  The only server that had an IP change is the linux server which we are having issues populating the docrecord fields from. This function is broken for all computers and terminal server users

Thanks,
John
0
 
Chris HInfrastructure ManagerCommented:
I can only assume there is an ini file (search) on that mapped rive.  And in that ini file is an IP address of where to point the database server.  Let me know if I'm wrong.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Chris HInfrastructure ManagerCommented:
PS.  this has nothing to do with the ODBC ini...  this is an ini file docrecord may use.  I stress may as their documentation is under lock and key and only available for those with a subscription.
0
 
NENS24Author Commented:
That was my original thought however I was unable to locate such an INI which referenced the previous IP of the linux server.  I can tell you that when i setup the clients for docrecord, i do not point them to a mapped drive.  I point them to the docrecord database and a custom port of 1500.  That's not to say it's still not an INI file, just not one that I can find.  Anything within SQL i should be checking?
0
 
Chris HInfrastructure ManagerCommented:
Can you validate port 1500 is open on the linux machine?  If you know a username, you could connect and test to see if the linux machines mysql database is excepting incoming sql connections.

Install MYSQL client:
http://www.mysql.com/downloads/mysql/


C:\www\mysql\bin> mysql --port=1500 -u root -p

http://stackoverflow.com/questions/3246482/mysql-command-line-client-for-windows
0
 
NENS24Author Commented:
The docrecord connection seems to be working fine. The information above was just to explain how the clients connect to the docrecord server which is done through port 1500 to the docrecord database.  The part that I am not too sure about is how docrecord connects to the linux server.  I would guess that it's done on the server end as the clients, as long as they have rights within docrecord, are able to "populate" the fields while in docrecord no matter which computer they are working at.  The only information that i was given is they appeared to configure the SQL server (docrecord) to connect to the linux server.  It's fustrating to know it's going to be a small IP Address change to correct the issue. I just don't know where that configuration is.
0
 
Chris HInfrastructure ManagerCommented:
Can you do a search through the registry and file contents under the docrecords program files directory for the old ip address?
0
 
Chris HInfrastructure ManagerCommented:
There is literally ZERO documentation on how this program works.  Can you get your hands on any of the installation documentation?  Maybe a CD with a setup guide?  That would be invaluable.
0
 
NENS24Author Commented:
hello Choward,

That was my exact problem, no documentation.  We ended up having to spend the money for support to get it resolved.  The fix was literally having them browse to a System DSN I had already modified within ODBC prior to contacting them and apply it to the Auto Poplulate fields.  For some reason even after making the changes in ODBC, the changes don't reflect automatically within docrecord even though the software is referencing the same DSN!

I appreciate the effort though.

Thanks
John
0
 
NENS24Author Commented:
Issue was resolved through vendor support
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now