Error Code 126 When Installing (i have read the other posts)

gmcdonald · Post by **gmcdonald** » Tue Nov 16 2004

A client of ours has the following problem when installing amyuni:

Installing printer driver
Error Code: 126
The specified module could not be found
--------------------------------------------------
Installing printer
Error Code: 1797
The printer driver is unknown
--------------------------------------------------
Installing printer
Error Code: 1797
The printer driver is unknown
--------------------------------------------------

After searching your forums i came across some information that suggested this was due to the wbem directory being missing from the system path. Upon checking i discovered that it was still there.

But i did find that the system path had environment variables coded into it (namely %SystemRoot%). After checking the registry i discovered that the type of the Path key was set to REG_SZ. I tried changing this to REG_EXPAND_SZ and rebooting but the machine set the type back to REG_SZ. To work around this i manually expanded all the environment variables and reapplied the path. This didn't work either and the above errors were produced again.

I noticed in other posts that there was mention of an .inf file that may solve the problem. Can you provide me any further information???

Kind Regards,

Grant McDonald
Configuration Manager
InfoComp Pty Ltd, Australia

P.S. Btw, i was wondering if there were command line options to specify a silent install? (side-topic).

Joan · Post by **Joan** » Tue Nov 16 2004

Hello,

The inf file is provided by our Technical Support to help you install the PDF Printer manually. This will avoid you getting the error.

You can get this file by contacting support@amyuni.com

Did you try to copy framedyn.dll to the windows\system32 folder?

Concerning silent install, you can run Install -s to install the printer silently.

Hope this helps.

gmcdonald · Post by **gmcdonald** » Tue Nov 16 2004

I can't see how this should help since it is on the system path. Is there a problem in the installer regarding system paths?

gmcdonald · Post by **gmcdonald** » Tue Nov 16 2004

Some further information:

Amyuni previously worked fine on this computer, but it has undergone a complete reinstall. I have since found out that due to a new version of an in-house product they have developed, an additional PDF converter has been installed prior to Amyuni being reinstalled:

LEADTOOLS ePrint IV (4.5 to be precise)

I was wondering whether you have had any problems with such products co-existing with Amyuni before?

Kind Regards,

Grant McDonald
Configuration Manager
InfoComp Pty Ltd

Joan · Post by **Joan** » Wed Nov 17 2004

Hello,

It is not really that our Installer has a problem with system path.

This issue is explained in our Technical Newsletter 1 http://www.amyuni.com/forum/viewtopic.php?t=180

This error occurs because the windows printer installer looks for the file framedyn.dll in the system path and does not find it. This DLL is supposed to be located under the wbem directory under system32 and the system path is supposed to point to that directory.

We have found that under some installations, the system path contains a space character after the wbem directory, which prevents Windows XP from finding this DLL.
To check if this is the problem, type PATH in a command line window and check for something like:
path=c:\windows;c:\windows\system32;c:\windows\system32\wbem ;
If this is the case, you will need to manually remove the space from the system path, or copy the framedyn.dll file to your application or system32 directories

This is why I advised you to try to copy framedyn.dll to windows\system32, to be on the safe side that this is not a space problem.

We do not have problems with coexisting printer drivers. Maybe Leadtools are using our driver, I am not sure which PDF Converter Leadtools. Please note that two different versions of the PDF Converter (example version 2.0x and 2.1x) can coexists with no problems because these use different drivers.

Hope this helps.

trumpetinc · Post by **trumpetinc** » Wed Jun 08 2005

Has there been any other information regarding this issue?

I have found some workstations with the problem. Changing the system path does NOT fix the problem, but compying the framedyn.dll file into the system32 directory does work.

We are installing using PDFDriverInit.

I'm OK with copying that DLL around, but I have concerns about what happens if Windows upgrades the DLL. Does that library only get used during install of the printer, or is it also required for using the print driver?

Thanks,

- K

Joan · Post by **Joan** » Mon Jun 13 2005

Hello,

Framedyn.dll is used only during the printer installation because it is used by the Windows printer installer, this dlls is not needed when using the printer specially if you are using Cdintf.

trumpetinc · Post by **trumpetinc** » Thu Jun 16 2005

Thanks, Joan.

Along these lines, we've noticed that the printer driver install fails if certain Hewlett Packard system tray applications are running.

Any idea why?

Thanks,

- K

Amyuni Technologies

Error Code 126 When Installing (i have read the other posts)

Error Code 126 When Installing (i have read the other posts)

Other PDF Converters?