Adagio print error

Posted by: JohnDilworth

Adagio print error - 06/14/17 10:59 AM

I get the following error when trying to print in Adagio. I tried rebooting, then re-installing Adagio and still get the same error. Any ideas what to do?

Logon failed.
Details: [Database vendor code 160]
Error in file .......
Unable to connect: incorrect log on parameters
Details: [Database vendor code 160]
Posted by: Retired_Guy

Re: Adagio print error - 06/14/17 11:19 AM

Adagio module? Version? Report?
Posted by: JohnDilworth

Re: Adagio print error - 06/14/17 11:24 AM

It's happening with all modules and all reports.
I'm using AP 9.2B, GL 9.2 B, etc.
Posted by: Softrak Support

Re: Adagio print error - 06/14/17 11:43 AM

Hi John,

The 'error 160' indicates that the Crystal Runtime is not able to make an ODBC connection. Adagio programs at version 9.2A or later use these components for reporting, rather than a different report table process in Adagio versions older than 9.2A.

One specific report - the User Preferences listing - does not use an ODBC connection, so if you can preview/print this report with no error, that means the Crystal Runtime install is OK, and the issue is with the ODBC part.

Some versions of Windows do not pre-install ODBC files MSVCR110.DLL and MSVCP110.DLL in the C:\Windows\SYSWOW64 directory. Recent versions of Adagio will install these, just in case Windows doesn't have them, and also save a copy to the \Softrak\System\Win32 and \sys64 directories in case you need to copy them in manually - say if the install user didn't have the correct rights.

In the \Softrak\System directory is also a utility OCSTEST.EXE to test the ODBC Connection String, with a help document ConnectionTesterInfo.PDF to describe how this works.
Posted by: JohnDilworth

Re: Adagio print error - 06/14/17 12:36 PM

Sorry but I haven't been able to solve the problem yet.

The User Preferences listing runs OK
so that means the Crystal Runtime install is OK, and the issue is with the ODBC part.

I checked that the ODBC files MSVCR110.DLL and MSVCP110.DLL are in the C:\Windows\SYSWOW64 directory.

I ran OCSTEST.EXE to test the ODBC Connection String, using a sample string as described in the help document. I get the message: Unable to create connection!

FYI, here is the actual connection string that I tested it with:

DRIVER=AdagioDataSourceDriver;
DBQ=C:\SOFTRAK\Receivables\SAMDATA SAM;
DESCRIPTION=Adagio ODBC v2 Driver;
DBDIRECTORY=C:\SOFTRAK\Receivables\SAMDATA;
COLUMNS=COMMON;
DBFILTER=AR9*;
DBSELELECTOR=SAM;
NAMES=LONG;
TABLESALL=FALSE;
USERID=SYS;
PASSWORD=SYS;
RAWPASSWORD=1;
Posted by: Douglas Dickie

Re: Adagio print error - 06/14/17 01:03 PM

John

Workstation and server o/s?
Posted by: JohnDilworth

Re: Adagio print error - 06/14/17 01:13 PM

I'm running it on my laptop only, using the NFR versions of Adagio. OS is Windows 7 Professional Service Pack 1
Posted by: Patricia B.

Re: Adagio print error - 06/14/17 02:30 PM

I would reinstall Crystal manually. Current version is 13.0.16.1954. Is that the one you have installed?
The installer is System\CR_InstallCommon
Posted by: JohnDilworth

Re: Adagio print error - 06/14/17 02:59 PM

I found the msi file in the folder you mentioned. Tried to reinstall but it said it could not find something. The only option was to quit.
Posted by: Patricia B.

Re: Adagio print error - 06/14/17 03:34 PM

Do you have the User Account Control disabled (bar at the bottom)? Disable it, restart the computer and try again.
Posted by: JohnDilworth

Re: Adagio print error - 06/14/17 04:22 PM

Hi Patricia,
Thanks for your assistance.
I disabled UAC, and then it allowed me to reinstall Crystal Reports per your instructions. However I still get exactly the same error message when I try to run a report in Adagio.
Posted by: JohnDilworth

Re: Adagio print error - 06/14/17 04:57 PM

I disabled the UAC, reinstalled Crystal per your instructions successfully. However the reports still will not run and I get the same error message.

I think it must be the ODBC connection. I tried some diagnostics and I get am message that the specified driver cannot be loaded due to system error 126, although the driver (AdagioODBCv264.dll) is in the folder expected. I googled it (ODBC error 126) and found plenty of entries from application vendors, but absolutely no advice from Microsoft (typical). I found nothing helpful at all on the internet and I have spent several hours on it.
Posted by: Softrak Support

Re: Adagio print error - 06/14/17 05:01 PM

Hi John,

I just emailed you a troubleshooting document. It is a couple of years old but the error messages are still relevant.

Both the error 160 and the system error code 127 could be related to installing Adagio without proper rights. The \Softrak\ODBCv2\AdagioODBCv2.DLL file isn't being located properly - it gets located in the Windows Registry on installing an Adagio program.

I presume that you have not installed the Adagio ODBCv2 program - it is not required to do this to print reports from Adagio; I was just curious.

ODBC connections must be 32-bit for Adagio reporting, not 64-bit.
Posted by: Patricia B.

Re: Adagio print error - 06/14/17 05:08 PM

Since you had issues with installing CR Runtime, perhaps you should do a Workstation setup with the UAC disabled.

I wrote another response and it was lost. Check the ODBCV2 folder. See if you are missing any of the long named .dlls. I had an issue before that ODBC and other .exe files were renamed because the computer didn't accept long names when installing including Adagio .exes.
Posted by: JohnDilworth

Re: Adagio print error - 06/14/17 05:17 PM

The Adagio ODBC driver seems to be linked to the 64 bit DLL on my PC, and not the 32 bit one. Your email has not arrived yet. Do you think my best option would be to uninstall all the Adagio modules then install them again (as a system administrator, even though I am already that on my own PC)?
Posted by: JohnDilworth

Re: Adagio print error - 06/15/17 07:37 AM

Before uninstalling everything I thought I would try to solve it as follows:
I checked my ODBC data source as follows:

Control Panel
Administrative Tools
Data Sources (ODBC)
System DSN tab - I can see Adagio Data Source is linked to Adagio Data Source Driver

If I change to the Drivers tab I can see the Adagio Data Source Driver is version 2.01.08.189 with file ADAGIOODBCV264.DLL dated 2/22/2016

This looks like a 64 bit driver. From an earlier post it appears that I should be using the 32 bit driver ADAGIOODBCV2.DLL
Is this correct, and if so how do I remove the existing driver and install the 32 bit one? The Data Sources (ODBC) help says that I must use an installation program provided by the vendor.
Posted by: JohnDilworth

Re: Adagio print error - 06/15/17 08:02 AM

BTW FYI my laptop is 64 bit Win 7 Professional with Service Pack 1

Perhaps I can fix it by just changing the following keys in the Windows registry to point to the full path for ADAGIOODBCV2.DLL instead of the path for ADAGIOODBCV264.DLL

HKEY_LOCAL_MACHINE
SOFTWARE
ODBC
ODBC.ini
Adagio Data Source
Driver

and

HKEY_LOCAL_MACHINE
SOFTWARE
ODBC
ODBCINST.ini
Adagio Data Source Driver
Driver

and

HKEY_LOCAL_MACHINE
SOFTWARE
ODBC
ODBCINST.ini
Adagio Data Source Driver
Setup

Tech support - please confirm if this might work before I make any changes to my registry!
Posted by: Michael Mulrooney

Re: Adagio print error - 06/15/17 08:53 AM

Do not edit the registry...

use

C:\Windows\system32\odbcad32.exe for 64 bit ODBC Administrator
or
C:\Windows\SysWOW64\odbcad32.exe for 32 bit ODBC Administrator
as needed.
Posted by: Softrak Support

Re: Adagio print error - 06/15/17 09:07 AM

Hi, John,

Please run Softrak\System\ChkSys.exe and, after Proceed, select the System Snapshot button in the upper left corner of the Status of System window. Continue and create the snapshot After, create an email to support@softrak.com, attach the snapshot zip in your Softrak\System folder to the email and send it.

We'll take a look and get back to you.

Thanks.
Posted by: Retired_Guy

Re: Adagio print error - 06/15/17 09:24 AM

Hi John,

As a follow-on to Michael's post, it is very difficult to determine whether Windows has launched the 32-bit or 64-bit version of the ODBC Administrator. If you are using the 64-bit Administrator, it will show you the 64-bit registry entries and 64-bit ODBC Driver. If you launch the 32-bit Administrator, then the 32-bit ODBC driver will be shown.

Adagio installs both 32 and 64 bit ODBC connections. Adagio modules use the 32-bit driver to power the SAP Crystal Reports 2013 Connection. If you launch 64-bit Excel and ask it to connect to an Adagio database (if you have installed the Adagio ODBC module), it will automatically pick up the 64 bit driver.

OCSTEST.EXE in Softrak\System will be using the 32-bit driver (the one used by Crystal). All the ODBC connections require that the module has been run against the database being reported on.

So - can you print a report out of the Sample Data? Have you copied ANY of the files to/from the Softrak\Dict Folder?
Posted by: JohnDilworth

Re: Adagio print error - 06/15/17 09:29 AM

I've emailed the snapshot file.

Please note that what I was trying to do in this exercise was to simulate on my laptop an upgrade scenario for a major customer that has several Adagio modules and three third party modules. At their site we have only one day of the week in which we can upgrade (Sundays) because they have a POS store running 11 hours a day 6 days a week. My plan was to see if we could upgrade quickly and smoothly without any problems. Needless to say, so far my simulation has not ran smoothly! Therefore, I would be very pleased if you can pinpoint exactly where I went wrong so that I can ensure that the same problem can be avoided when we do a live upgrade.
Posted by: JohnDilworth

Re: Adagio print error - 06/15/17 09:37 AM

Hi Andrew

Thank you. Re your questions
So - can you print a report out of the Sample Data? - NO
Have you copied ANY of the files to/from the Softrak\Dict Folder? - NO

Liegh Sandercock has replied that Tech Support has received my snapshot file, so I will await their response.
Posted by: Softrak Support

Re: Adagio print error - 06/15/17 01:43 PM

Hi, John,

Per my earlier email, your w/s was missing some dll's from your Windows folders which I sent a link to for you.

After installing these files, try previewing a Company Profile report. It's a simple report but it also uses the dictionaries and, therefore, ODBC. It should work fine now.