Transliteration error

[DaNewt]

I saw a reference to an issue applying to CFMX for J2EE under release notes for
ColdFusion Updater release 3. However it said SPECIFICALLY that it did not
apply to CF MX Server. Nevertheless, CF MX7 Server throws the following message
when the homepage starts to load:

Error Executing Database Query.
[Microsoft][SQLServer 2000 Driver for JDBC]Character set 437 not found in
com.microsoft.util.transliteration.properties.

I've tried using the old version of macromedia_drivers.jar, but since we are
not using J2EE, there is no jar program to execute. Anyone have any ideas on
how to fix this?

Dave Newton
NASA MSFC

[PaulH]

have you tried the latest drivers (and other hotfixes) for cf7? you don't
appear to be using the cf supplied datadirect drivers so perhaps that j2ee note
actually applies in your case. maybe swap to the newer cf supplied driver or
perhaps give the jTDS driver a shot [url]http://jtds.sourceforge.net/[/url] we've found it
to be faster than the ms & datadirect (haven't tested the latest version yet)
drivers.

btw jar is part of any good java install, so if everything's in it's place,
you should be able to start it from a command line.

[DaNewt]

I did apply all of the hotfixes that were listed. JAR does not execute. I
have a feeling it's something that I'm unfamiliar with that's causing me not to
be able to update.

Also, the system is behind a firewall and IE has security enabled, so maybe
something did not transfer/execute?

Thanks!

Dave Newton
NASA/MSFC

[PaulH]

and did you try the mm supplied JDBC driver yet?

[DaNewt]

The fix:
Copied the macromedia_drivers.jar file from the server and ran JAR locally (CF
did NOT install JAR on the server) to extract the transliteration.properties
file and add the two lines:

translit.type.437=VM
translit.name.437=Cp437

The exact procedure for this was given in the March 19, 2003 release notes for
CFMX updater release 3.

Once this was done and the properties were inserted back into the jar file, I
stopped the CF services, copied it back to the server, restarted the CF
services. The alternate JDBC data source that was set up did not work, so I
deleted it and created a new datasource connection using the DEFAULT SQL
driver. And it worked.

So now Macromedia doesn't have to document this annoying little bit of tech
support. Annoying because it should have worked out of the box - and no one
should be faced with the choice of either spending many hours researching then
digging into a jar file just to make software work, or paying for tech support
that should be free to the point of troubleshooting normal data connections.
Are you listening, Adobe?

Dave-