>> (Win 2003 server x64). As best I can tell it's some kind of
>> incompatibility with 64-bit Crystal runtimes not talking to 32-bit AR
>> System ODBC driver (I'm at home at the moment and don't have the logs
>> handy, something like "error 193" in the logs).
Actual error is:
4/2/2010 1:48:57 PM
Logon failed.
Details: IM003:Specified driver could not be loaded due to system error 193
(AR System ODBC Driver).
Error in File C:\DOCUME~1\username\LOCALS~1\Temp\6\ARCategorizationHistory
{7CC59A4C-3C60-4442-9E63-10D9949C30CB}.rpt:
Unable to connect: incorrect log on parameters.
4/2/2010 1:50:57 PM
Logon failed.
Details: IM003:Specified driver could not be loaded due to system error 193
(AR System ODBC Driver).
Error in File C:\DOCUME~1\username\LOCALS~1\Temp\6\ARCategorizationHistory
{297C4630-A592-4FF3-8EF3-0823FBDDE455}.rpt:
Unable to connect: incorrect log on parameters.
> Crystal Reports Exporter is a free command line utility that can easily be
> setup to run from a batch file. Here is the URL:
> http://www.rainforestnet.com/crexport-download.htm
This one errors out with:
Unhandled Exception: System.IO.FileNotFoundException: Could not load file or
assembly 'CrystalDecisions.CrystalReports.Engine, Versi
on=9.1.5000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its
dependencies. The system cannot find the file specifi
ed.
File name: 'CrystalDecisions.CrystalReports.Engine, Version=9.1.5000.0,
Culture=neutral, PublicKeyToken=692fbea5521e1304'
at crexport.crexport.Main(String[] args)
Alan
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
