Amyuni Technologies

Our company also has the same problem whereas we cannot generate the SQL Queries to build our reports before calling the Printer Initialisation command, and therefore larger reports on slower machines timeout. :? I have just sent an email to Amyuni Support requesting options to increase the timeout ...

I've been beating my brow over this one - everything I try does nothing to improve the situation. Let me recap. I've effectively uninstalled Amyuni completely (removed all amyuni files, deleted all registry entries, confirmed all printers removed, and restarted the server). I then re-run the install...

Unfortunately no joy. I used the version 2.10i with the same result.

I take it there's not way to force a more detailed logging of exactly what the installer is doing to isolate exactly where it's crashing?

Hi Joan, Yes... unfortunately the same problem. I have domain administrative rights, and have also tried under the local administrator account - same result. I have removed the Amyuni Driver (seems to semi-get installed), restarted the Printer Spooler/ rebooted the server and retried. Still no luck....

Hi, Has anyone seen a problem where the Amyuni Printer driver cannot be installed on a Windows 2000 Server machine, but no error code is generated? The output from the log file is such: Windows 2000/XP Install ------------------------------------------------------------------------------------ Chem ...

Sorry for the confusion... the error message is definitely FDF (not ftf as per the subject line). Some additional information as well: The PDF file does get successfully created (double-clicking it on the server's file-system opens it with no problems) References to similar problems I can find are: ...

I come to this forum on my knees... desperately seeking an explanation for strange occurances. We use Amyuni PDF Convertor 2.10f (have tested up to 2.10i as well) with our Java application to generate dynamic PDF reports and send them client's browsers in PDF format. For the developers interested, t...

I'm having the same issue with one of our products... with the same workaround available (set the default printer to be one that handles printers).

My question is: Is this an Amyuni bug? Or the source application's problem?

Your opinion would be great...
Thanks
Brad

I'm sorry to be a pain... but I'm suffering a serious case of domestic blindness. :shock: I can only see 4 articles in the Technical Newsletters Forum - and none of them seem to cover either Windows 2003 OR the error message I reported. Could you please confirm the posting location... Thanks Brad

For once I'm trying to get a head-start on our clients... looks like that was a wise move. We have the Amyuni PDF Convertor Developer edition embedded in our Delphi product, which works like a charm. In Windows 2003 though, it reports an error message: Error Code: 1930 The printer driver is not comp...