cancel
Showing results for 
Search instead for 
Did you mean: 

Error -25596 when trying to connect to use the Informix Online Server native data source

Former Member
0 Kudos

Hi All,

We currently use a very old version on crystal (v9) and have recently downloaded the current version (14.1.1.1036) in order to investigate the effort involved in upgrading.

In the past we have always connected to our IBM Informix Server using the native Crystal Reports Informix Online Server data source, but all attempts with the current version of Crystal Reports are failing with error -25596.

The error is reported by Informix and it has this description:

-25596  The INFORMIXSERVER value is not listed in the sqlhosts file or the

Registry.

The default database server name that the INFORMIXSERVER environment

variable specifies must be a valid database server name in the file

$INFORMIXDIR/etc/sqlhosts on UNIX or the registry on Windows. Check

that the specified server is listed in the sqlhosts file or the

registry.

However, I'm of the opinion that the server is known and is configured OK (it's configured using the Informix SetNet32 application and it has resulted in this registry key being populated:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Informix\SqlHosts\prod1_devdb1 (NB: prod1_devdb1 is the name of the server I am trying to connect to).

I can create ODBC datasources on my PC and they work OK.  I can also run our legacy VB6 application (using the Crystal 9 COM objects) and connect using the native drivers to the Informix database.

My PC is running 64 bit Windows 7 Enterprise (fully patched).  Our Informix server is version 11.7 running on a SUSE server.

Any suggestions for where to start looking to solve this?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

This issue has been solved.  I upgraded to the latest version of the IBM Informix SDK (from version 3.70 to version 4.1) and it worked after that.

I'm not 100% sure if it was the upgrade itself, or a change I was forced to do the Path on my PC in order to do the upgrade.  The path change was to add "C:\Windows\SysWOW64" to the start of the Path (it was already in the Path, but not at the start).

Thanks also to Don for his assistance with this issue...

Answers (1)

Answers (1)

0 Kudos

Hi Scott,

I checked the PAM and that version is supported...

As a test if you configure a System ODBC connection does that work? Make sure you use the 32 bit ODBC Admin. And both the 32 and 64 bit ODBC Admin executables are odbcadm32.exe. The one you want to use is located here:

C:\Windows\SysWOW64

CR Designer is a 32 bit application so it means you need to use the 32 bit Client. Typically the Client detects the OS platform and installs the 64 bit version, but in this case you must use the 32 bit client.

If you are using the 32 bit client then try enabling CR DB logging to see if it tells you anything new...

Add these 3 values to the System Environment variables:

LOGGING_DIR = c:\logging

LOGGING_ENABLED_ASSERT = 1

LOGGING_ENABLED_RUNTIME = 30

Create the logging folder of course, and then try to connect. Close CR Designer first.

To turn off logging remove the lines, you can rename crlogger.dll to *.org but if you install a patch that file will get updated and logging will be enabled again. So if you notice slow performance look in the logging folder first...

Don

Former Member
0 Kudos

Hi Don,

Thanks for  the response.

I think I'm running the 32 bit version of Crystal.  It's installed in C:\Program Files (x86)\SAP BusinessObjects and Help-->About--MoreInfo shows lots of the loaded modules live in c\Windows\SysWOW64.

I'll ran the logging, but the logs didn't seem to contain anything significant.  In fact, interestingly enough, once the native Informix login form is displayed, the log isn't updated until the form is closed.  That is, I enter my credentials, click OK, see the -25596 error and acknowledge it, all without the log being updated. 

FYI, all I am doing after starting crystal is going into the File-->Log On of Off Server option (I'm not actually trying to use a report at this stage). 

With in that option, if I select ODBC as my connection method, I can connect OK (e.g. using a data source named "globalstar:prod1_devdb1:devdb1").  I can also see in the logs that the connection was made successfully.

One other interesting point is that I have validated the Informix server. I have successfully tested a native connection to "prod1_devdb1" using the Informix ILogon Demo application (it gets installed when the Informix drivers are installed on a PC).  I also find that if I deliberately mistype the server name (e.g. I enter prod1_devdb1x), I see a -25596 error (as you would expect).


Regards Scott

0 Kudos

Hi Scott,

Correct, that is where CR is installed, it is a 32 bit app.

Is the informix client install in the PATH statement? CR still uses it to find the client.

Did the logs show you logging on with the user name, PW is **** out...?

Can you paste in the info from the log, remove any senisitive info of course... but verify the IP or Server name is absolutely correct.

Don

Former Member
0 Kudos

Hi Don,

My path has a correct reference to Informix Client:

C:\Program Files (x86)\IBM Informix Client SDK\bin

I will post another reply with the contents of the "runtime" log.  The process I followed was:

1. Delete log files

2. Start CR

3. Try to log onto Informix Server

4. Acknowledge error message and the cancel out of logon form

5. Close CR

The entire log file is included in the post below.  The only modifications I've made was to deleted the blank lines...

NB the "assert" log was empty bar for a heading record. 

Former Member
0 Kudos
TIMESTAMPTHREAD_IDFILENAMELINE_NUMBERLOGGED_DATALEVEL
2014-5-1-3-54-3110828..\cserrinf.cpp523Error 14722 (..\csdll.cpp, 117): : C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\crw32_res_xx.dll1
2014-5-1-3-54-5110828.\QESession.cpp445Set Product View Locale: 103320
2014-5-1-3-54-5110828.\QESession.cpp479Set Preferred View Locale: 308120
2014-5-1-3-54-5110828.\QESession.cpp501Set Process Locale: 308120
2014-5-1-3-54-5110828.\qecommon.cpp117This property is currently in a read-only state and cannot be modified. File Name: ".\QEProperty.cpp". Line: 2171
2014-5-1-3-54-5410828.\xml.cpp211Leaving DbInitialize()20
2014-5-1-3-54-5410828.\xml.cpp153In DbInitialize()20
2014-5-1-3-54-5410828.\xml.cpp211Leaving DbInitialize()20
2014-5-1-3-54-5410828.\xml.cpp385In DbFetchDatabaseType()20
2014-5-1-3-54-5410828.\xml.cpp399Leaving DbFetchDatabaseType()20
2014-5-1-3-54-5410828.\xml.cpp4732In DbFreeString()20
2014-5-1-3-54-5410828.\xml.cpp4735Leaving DbFreeString()20
2014-5-1-3-54-5410828.\jdbc.cpp241Leave DbInitialize()20
2014-5-1-3-54-5410828.\jdbc.cpp185Enter DbInitialize()20
2014-5-1-3-54-5410828.\jdbc.cpp241Leave DbInitialize()20
2014-5-1-3-54-5410828.\jdbc.cpp555Enter DbFetchDatabaseType()20
2014-5-1-3-54-5410828.\jdbc.cpp564Leave DbFetchDatabaseType()20
2014-5-1-3-54-5510828.\xml.cpp112Leaving DllMain()20
2014-5-1-3-54-5510828.\jdbc.cpp173Leaving DllMain()20
2014-5-1-3-54-5510828.\xml.cpp112Leaving DllMain()20
2014-5-1-3-54-5510828.\jdbc.cpp173Leaving DllMain()20
2014-5-1-3-54-5710828.\javabeans.cpp194Leaving DbInitialize()20
2014-5-1-3-54-5710828.\javabeans.cpp148In DbInitialize()20
2014-5-1-3-54-5710828.\javabeans.cpp194Leaving DbInitialize()20
2014-5-1-3-54-5710828.\javabeans.cpp317In DbFetchDatabaseType()20
2014-5-1-3-54-5710828.\javabeans.cpp326Leaving DbFetchDatabaseType()20
2014-5-1-3-54-5710828.\javabeans.cpp1858In DbFreeString()20
2014-5-1-3-54-5710828.\javabeans.cpp1861Leaving DbFreeString()20
2014-5-1-3-54-5710828.\javabeans.cpp113In DllMain()20
2014-5-1-3-54-5710828.\javabeans.cpp136Leaving DllMain()20
2014-5-1-3-54-5710828.\jdbc.cpp173Leaving DllMain()20
2014-5-1-3-54-5710828.\xml.cpp112Leaving DllMain()20
2014-5-1-3-55-210828.\crdb_wic.cpp182Leaving DbInitialize()20
2014-5-1-3-55-210828.\crdb_wic.cpp127Enter DbInitialize()20
2014-5-1-3-55-210828.\crdb_wic.cpp182Leaving DbInitialize()20
2014-5-1-3-55-210828.\crdb_wic.cpp381Enter DbFetchDatabaseType()20
2014-5-1-3-55-210828.\crdb_wic.cpp397Leave DbFetchDatabaseType()20
2014-5-1-3-55-210828.\crdb_wic.cpp404In DbFreeString()20
2014-5-1-3-55-210828.\crdb_wic.cpp407Leaving DbFreeString()20
2014-5-1-3-55-910828..\crdb_p2s.cpp570Entering SQLLogOnSQLServerWithExtendableOptions20
2014-5-1-3-55-4510828.\javabeans.cpp113In DllMain()20
2014-5-1-3-55-4510828.\javabeans.cpp136Leaving DllMain()20
2014-5-1-3-55-4510828.\jdbc.cpp173Leaving DllMain()20
2014-5-1-3-55-4510828.\xml.cpp112Leaving DllMain()20
2014-5-1-3-55-4610828..\crdb_p2s.cpp577Leaving SQLLogOnSQLServerWithExtendableOptions20
2014-5-1-3-55-4610828..\serverhandle.cpp356succeeded: serverName=prod1_devdb1,databaseName=globalstar,userID=scottr1
2014-5-1-3-55-4610828..\..\convert.cpp864Error: message=, DbError=2021
2014-5-1-3-55-4610828..\cserrinf.cpp523Error 31816 (..\..\src\data\queryenghelp.cpp, 549): Logon failed.:1
2014-5-1-3-55-5310828.\javabeans.cpp113In DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp136Leaving DllMain()20
2014-5-1-3-55-5310828.\jdbc.cpp173Leaving DllMain()20
2014-5-1-3-55-5310828.\xml.cpp112Leaving DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp113In DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp136Leaving DllMain()20
2014-5-1-3-55-5310828.\jdbc.cpp173Leaving DllMain()20
2014-5-1-3-55-5310828.\xml.cpp112Leaving DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp113In DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp136Leaving DllMain()20
2014-5-1-3-55-5310828.\jdbc.cpp173Leaving DllMain()20
2014-5-1-3-55-5310828.\xml.cpp112Leaving DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp113In DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp136Leaving DllMain()20
2014-5-1-3-55-5310828.\jdbc.cpp173Leaving DllMain()20
2014-5-1-3-55-5310828.\xml.cpp112Leaving DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp113In DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp136Leaving DllMain()20
2014-5-1-3-55-5310828.\jdbc.cpp173Leaving DllMain()20
2014-5-1-3-55-5310828.\xml.cpp112Leaving DllMain()20
2014-5-1-3-55-5310828..\..\src\print\format\imageretriever.cpp905Destroy API called. Image Retriever was not used. No cleanup necessary.20
2014-5-1-3-55-5310828.\xml.cpp219In DbTerminate()20
2014-5-1-3-55-5310828.\xml.cpp271Leaving DbTerminate()20
2014-5-1-3-55-5310828.\jdbc.cpp250Enter DbTerminate()20
2014-5-1-3-55-5310828.\javabeans.cpp203In DbTerminate()20
2014-5-1-3-55-5310828.\javabeans.cpp252Leaving DbTerminate()20
2014-5-1-3-55-5310828.\crdb_wic.cpp190In DbTerminate()20
2014-5-1-3-55-5310828.\crdb_wic.cpp241Leaving DbTerminate()20
2014-5-1-3-55-5310828.\javabeans.cpp203In DbTerminate()20
2014-5-1-3-55-5310828.\javabeans.cpp252Leaving DbTerminate()20
2014-5-1-3-55-5310828.\crdb_wic.cpp190In DbTerminate()20
2014-5-1-3-55-5310828.\crdb_wic.cpp241Leaving DbTerminate()20
2014-5-1-3-55-5310828.\xml.cpp219In DbTerminate()20
2014-5-1-3-55-5310828.\xml.cpp271Leaving DbTerminate()20
2014-5-1-3-55-5310828.\javabeans.cpp113In DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp136Leaving DllMain()20
2014-5-1-3-55-5310828.\xml.cpp112Leaving DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp113In DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp136Leaving DllMain()20
2014-5-1-3-55-5310828.\xml.cpp112Leaving DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp113In DllMain()20
2014-5-1-3-55-5310828.\javabeans.cpp136Leaving DllMain()20
2014-5-1-3-55-5310828.\xml.cpp112Leaving DllMain()20
0 Kudos

Hi Scott,

When you try to log on which Database driver are you selecting?

Current version no longer have a Native Informix driver so you have to select ODBC or OLE DB or possibly JDBC.

when you try to connect which driver are you selecting?

Logs show it's trying to use XML or JDBC.

If that's is the case then hit the F1 key and follow the info on how to configure a JDBC driver.

Don

Former Member
0 Kudos

I'm using the native Informix Online Server option:

0 Kudos

Hi Scott,

In the log the error 202 seems to be the cause. According to informix error codes:

Error Codes from -200 Through -899

Error codes from -200 to -899 indicate problems in the execution of an SQL
statement. These codes are returned to the SQLCA. An ISAM error code accompanies
many of these messages.

This can typically mean the user may not have permissions to the table or there are differences in the clients being used.

Don