Solaris ODBC into NT MS SQL Server 1

[stevenmidlands]

Dear All,

We have a Solaris box running CF 4.5. On the same network, and totally visible, is an NT box running SQL Server version 7.
We need to be able to use the Solaris Cold Fusion to inteogate a database on the NT box. Although the ‘ODBC’ link verifies correctly we get this error every time we try run a query, no matter how simple it may be.

Has anyone any ideas where we are going wrong?

Many thanks in advance
Dr S Lancer.
____________________________________________________

Error Diagnostic Information
ODBC Error Code = S1000 (General error)
[MERANT][ODBC SQL Server Driver]Unicode conversion failed
The error occurred while processing an element with a general identifier of (CFQUERY), occupying document position (9:1) to (9:62).
Date/Time: Thu Nov 16 18:48:29 2000
Browser: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
Remote Address: 10.1.1.102
HTTP Referer:

http://sun1/

_________________________________________________________

 

[programmher]

Did you EVER get a response to your question? I am encountering the same message...

 

[stevenmidlands]

No. Sorry to say.

Nor on the Allaire forums or anywhere.
It seems it is beyond the wit of mankind at the moment!

 

[programmher]

Calamity and woe!!! I REALLY need to resolve this!

Normally, removing the ANSI paddings and warning within the DSN corrects this problem...

I will update you (if you like) when I resolve this issue.

 

[programmher]

Here are some questions another member asked me. Perhaps they will be of some insight or assistance to you:I see... now I have some questions...

Has there been a change to the sort order, character set, or the unicode collation settings on the server?

How did the data in the table originally get populated?

Are you running the query on your machine that has SQL Server installed on it where the data resides on another server?

Has this worked before or did this just start happening?

Has there been a recent restore of any databases on your
server? The master database?

I'll also be checking around technical sources for this...


TechNet also indicates:


Unicode conversion failed. The code page of the SQL server must be installed on the client system.

The server code page must exist on the client for proper operation. Either clear the Auto Translate check box for the DSN or install the code page of the server on the client. The server code page can be determined by running EXEC sp_server_info 18.


Hope this helps!

 

[programmher]

Steve,

Please go here:

http://www.allaire.com/Handlers/index.cfm?ID=15781&Method=Full

This directly addresses the error I'm encountering! If you can't view the document, I've included a portion of it below:


Merant has released two new Linux ODBC drivers for MS SQL Server and MySQL. These drivers will be included in CF 4.5.1 sp2.

Merant has made the following fixes:

Microsoft SQL Server 7 ODBC Driver:
Several issues concerning the direct execution of a Remote Procedure Call have been corrected. The issues that have been corrected are:


The driver was erroneously detecting an Invalid Cursor State.
The driver was not detecting certain expected error conditions.
Unicode conversion failures.
The SQL_DIAG_ functionality was not working properly for error diagnostics
May 25, 2000: A more recent version of this driver has fixed a problem with erronous display of numeric data using MS SQL Server 7.0 SP2 and is available at the link below. This version of the driver includes the fixes detailed above.
Sept 5, 2000: When querying a 'money' field from a SQL Server database from CF on Linux incorrect values are returned
Sept 5, 2000: Unable to connect to SQL Server 6.5 from Linux
Sept 21, 2000: This build has the same fixes as the build done on Sept 5, 2000 except this build is a "release" build from Merant which means the file is smaller (optimized) and therefore runs faster.

Hopefully, installing this SP will resolve the issue. I just don't understand why it is intermittent...

 

[programmher]

Steve-

One last bit of info (as I await SP installation).

If I modified the lengths of my smaller fields (SQL Server side), I no longer got the error message.

Also, here are better directions to the Allaire White Page:

http://www.allaire.com/support/index.cfm

- New ODBC Drivers for Linux OS (the third white paper down).

Happy coding!