Error: 80040154 no registration problems, 80040154 no registration
This is actually a problem where the COM component is not registered. Although it has been handled before, it is clear that the COM component needs to be registered, if you do not know, are unfamiliar, or forget it, you can try this method.
The problem occurs when the business system migrates from the old server to the new server. The system has a logon verification interaction interface with other manufacturers. The interface has a history of years, some COM components that need to be registered are also normal. Therefore, when this problem occurs during system deployment:
The first reaction is to register the components provided by the manufacturer under the system32 directory of the system disk, for example, regsvr32 dsccrypt. dll, but after all the registered DLL files have been registered, this error is still reported.
Alas, suddenly kindly. Fortunately, in the above error message, the clsid value of the unregistered DLL component is provided, and there seems to be a glimmer of hope. Copy the clsid value to the registry on the old server where the system runs normally:
See? Actually, the physical path of this DLL exists in InprocServer32. What! It turns out to be placed in a humble directory that is useless.
Then copy the DLL file to the new server. If the file has been copied during migration, find the file under the path and re-register it: regsvr32 WebPro. dll, the problem is solved...
In addition, to register a 32-bit COM component for a 64-bit operating system, go to the C: \ windows \ sysWOW64 \ regsvr32.exe directory, because the default C: \ windows \ system32 \ regsvr32.exe is a 64-bit version.