Environment
Novell iPrint
Microsoft Windows XP Professional embedded
Microsoft Windows XP Professional embedded
Situation
Error: The specified module could not be found
Error Group: Windows
Error code: 126
Error Group: Windows
Error code: 126
Unable to install iPrint printers to the Windows XP Thin or Embedded client
During the iPrint client install you may see errors like this on screen:
Error: iPrint Driver Install - Unknown installation error (995).
Error: iPrint Driver Install - Unknown installation error (1223).
The log in the C:\NDPS\ipperrs.txt may have messages like this:
Possible Solution: Add c:\windows\system32\drivers to your path environment variable
?x0009;Possible Solution: Add c:\windows\system32\wbem to your path environment variable
?x0009;Possible Solution: Make sure c:\windows\system32\wbem ramedyn.dll exists and is not corrupt
?x0009;Possible Solution: Make sure c:\windows\system32\srclient.dll exists
Resolution
Add srclient.dll to the Windows\System32 directory and reboot the workstation.
Additional Information
The version of Windows XP installed on this type of "thin client" wants to create a system restore point before a printer driver is installed, but a required Windows file for that process is missing: srclient.dll
Additional information:
iPrint client version 4.18 has additional code to log 126 errors to the c:\NDPS\ipperrs.txt file. This error log will indicate possible resolutions to the problem, such as: srclient.dll must be added and wbem and drivers must be added to the Windows Path Environment.
Additional information:
iPrint client version 4.18 has additional code to log 126 errors to the c:\NDPS\ipperrs.txt file. This error log will indicate possible resolutions to the problem, such as: srclient.dll must be added and wbem and drivers must be added to the Windows Path Environment.
1) Make sure c:\windows\system32\wbem and c:\windows\system32\drivers are in the Windows Environment Variable Path.
a. Right-click My Computer -> Properties
b. Advanced tab -> Environment Variables button
c. Double-click Path (under System variables) and add the path strings listed above. Use semi-colons to separate statements.
d. Click OK and OK.
2) Make sure c:\windows\system32\wbem\framedyn.dll is available and not corrupt.
Formerly known as TID# 10095288