In very rare cases, after installing our PDF printer, users receive an error message when calling the 7-PDF Printer Options dialog box with the following message
Error 429: Error creating object: pdf7.PdfUtil or similar.
The error occurs when important .NET assemblies of the PDF printer (.NET type libraries) could not be properly registered via the .NET registration tool
regasm.exe when the setup was executed. The following error message appears in the Setup Log of the PDF printer:
Process exit code: 100 when trying to register the corresponding .NET libraries of the PDF printer such as pdf7.PDFWriter.dll, pdf7.PdfWriter.Lib.dll, pdf7.PdfWriter.Upload.dll, pdf7.PdfWriter.Mail.dll, pdf7.PdfWriter.XpsInternal.dll etc.
The components are usually located under
C:\Program Files\Common Files\7-PDF\System\Framework\v4.0\ and are registered from there by InnoSetup (installer) when the PDF printer setup is executed. In the case of a Windows 10 with a properly installed .NET Framework installation, this error usually does not occur at all. However, if the patch status or the installation of the current Windows 10 system is unclean for any reason, the registration of the necessary components may fail.
In the event that this is the case with you, you should try to get your .NET Framework back into a clean state with all existing Windows updates and a corresponding installation of the same. Only then should you reinstall 7-PDF Printer and the error 429 should then no longer occur.
Should there be further problems with your .NET Framework, you could try to register the individual .NET components manually. However, this would only be recommended for professionals among them. For example, a batch file with the following commands was successfully executed under Build Level Windows 10 64bit 20H2 (Build 19042.685) and properly registered the .NET components using a command prompt previously executed as an administrator:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\regasm.exe /codebase "C:\Program Files\Common Files\7-PDF\PDF Printer\API\Microsoft.NET\Framework\v4.0\pdf7.PDFWriter.dll" /tlb
C:\Windows\Microsoft.NET\Framework\v4.0.30319\regasm.exe /codebase "C:\Program Files\Common Files\7-PDF\System\Framework\v4.0\pdf7.PdfWriter.Lib.dll" /tlb
C:\Windows\Microsoft.NET\Framework\v4.0.30319\regasm.exe /codebase "C:\Program Files\Common Files\7-PDF\System\Framework\v4.0\pdf7.PdfWriter.Upload.dll" /tlb
C:\Windows\Microsoft.NET\Framework\v4.0.30319\regasm.exe /codebase "C:\Program Files\Common Files\7-PDF\System\Framework\v4.0\pdf7.PdfWriter.Mail.dll" /tlb
C:\Windows\Microsoft.NET\Framework\v4.0.30319\regasm.exe /codebase "C:\Program Files\Common Files\7-PDF\System\Framework\v4.0\pdf7.PdfWriter.XpsInternal.dll" /tlb
After the manual registration of the .NET components, the error message:
Error 429: Error creating object: pdf7.PdfUtil
Either way you can say that an inconsistent .NET framework or a 7-PDF printer setup that was not executed as an admin leads to the above. Error pattern can result. Antivirus programs or malware tools could also prevent the required .NET components from being installed properly. Anyway...in a current and normally functioning Windows 10 system, this error pattern should not actually appear at all.