PRO11.MSI DEAR FRIEND WHEN I START IT APPEARS THE FOLLOWING ERRORS RSTRUI.EXE MSCTF.DLL AND AGAIN CTFMON.EXE ERROR. HOW I CORRCT THIS ONE SEND MAIL TO ME PLSE. [email protected]

Hi Ihan,

You are facing terrible problem with that error message.. However we can try to fix it. There are few methods you can do..

Solution 1.

1. Insert the product software CD into the CD-ROM drive on the computer.
2. Right-click Start and then click Explore . Windows Explorer opens.
3. Locate and select the CD-ROM drive that contains the product software CD.
4. Locate and double-click the Setup and then the Scan folders to open them.
5. Double-click Data1.cab or Scan.cab to open the contents of that file.

Extract, rename, and save the filesLocate the following files, right-click them, select Extract , and save them to the Windows Desktop. Leave Windows Explorer open after extracting the files.

• F1922_TWUNK_16.EXE.096CD9AA_35CA_455C_ADCB_36EF6B7F7892After extracting this file to the Desktop, right-click it and rename it to TWUNK_16.EXE .
• F1923_TWUNK_32.EXE.096CD9AA_35CA_455C_ADCB_36EF6B7F7892After extracting this file to the desktop, right-click it and rename it to TWUNK_32.EXE .
• F1928_TWAIN.DLL.096CD9AA_35CA_455C_ADCB_36EF6B7F7892After extracting this file to the desktop, right-click it and rename it to TWAIN.DLL .
• F1939_TWAIN_32.DLL.096CD9AA_35CA_455C_ADCB_36EF6B7F7892After extracting this file to the desktop, right-click it and rename it to TWAIN_32.DLL .

Then you have to copy these files to C:\windows\system32 folder ( this means overwrite the files ) and try to install the software. it should work.

for better understanding check the link below.
MSI.SCAN Solution


Solution 2.

you need to remove all the HP Printer entry from Add/remove or Programs and features under Control panel.

Then download the latest software from HP website by clicking on the link below.

HP PSC 1402 Printer Drivers

Regards,
Suhail

Take a look in Event Viewer I looked in Event Viewer to find out what MSI-file that generated the error message and found:
Log Name: Application
Source: MsiInstaller
Date: 23.09.2010 21:58:26
Event ID: 1040
... ...
Description:
Beginning a Windows Installer transaction: C:\ProgramData\Skype\{D103C4BA-F905-437A-8049-DB24763BBE36}\SkypeToolbars.msi. Client Process Id: 6564.
2. Running MSIEXEC with logging options I started a "Command Promt" and used the command: "cd C:\ProgramData\Skype\{D103C4BA-F905-437A-8049-DB24763BBE36}" to navigate into the folder containing the MSI-file.
Now using the command: "msiexec /i SkypeToolbars.msi /lv log.txt" (msiexec options: /i = Install, /lv = Log + Verbose output).
After clicking away the error message I just wrote "log.txt" in my "Command Promt" to open the log-file. Near the bottom of the log-file I found this line:
DEBUG: Error 2738: Could not access VBScript runtime for custom action
3. DEBUG: Error 2738 After a quick search at Google I found out this error indicates that the VBScript engine is not registered on the computer.

The solution for a Windows Vista or Windows 7 32bit:
- Click Start -> All Programs -> Accessories
- Right click "Command Promt" and click on "Run as administrator"
- Write "cd %windir%\system32" and hit Enter
- Write "regsvr32.exe vbscript.dll" and hit Enter
- You should now get a message that says: "DllRegisterServer in vbscript.dll succeeded."
- Click "OK"
The solution for a Windows Vista or Windows 7 64bit:
- Click Start -> All Programs -> Accessories
- Right click "Command Promt" and click on "Run as administrator"
- Write "cd %windir%\syswow64" and hit Enter
- Write "regsvr32.exe vbscript.dll" and hit Enter
- You should now get a message that says: "DllRegisterServer in vbscript.dll succeeded."
- Click "OK"
4. Try again... Now I tried once more to run "msiexec /i SkypeToolbars.msi /lv log.txt" (I kept the /lv log.txt option to look for changes if the installer would fail again).
If you still get the same Error than continue to step 5.
5. Cleanup registry first, then re-reg My installation still gave me the same error, so after some more searching and reading on Google I found a solution that explained what I tried before (with the regsvr32.exe) and also an alternative step if that one should fail. The alternative step was to remove the Registry Key pointing to vbscript.dll.
The alternative solution for a Windows Vista or Windows 7 32bit is then:
- Click Start -> All Programs -> Accessories
- Right click "Command Promt" and click on "Run as administrator"
- Write "reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f" and hit Enter
- Write "cd %windir%\system32" and hit Enter
- Write "regsvr32.exe vbscript.dll" and hit Enter
- You should now get a message that says: "DllRegisterServer in vbscript.dll succeeded."
- Click "OK"
The alternative solution for a Windows Vista or Windows 7 64bit:
- Click Start -> All Programs -> Accessories
- Right click "Command Promt" and click on "Run as administrator"
- Write "reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f" and hit Enter
- Write "cd %windir%\ syswow64" and hit Enter
- Write "regsvr32.exe vbscript.dll" and hit Enter
- You should now get a message that says: "DllRegisterServer in vbscript.dll succeeded."
- Click "OK"
Now using the command "msiexec /i SkypeToolbars.msi /lv log.txt" the installer started perfectly, ran all the way thru and Finished.
Conclusion This message indicates that VBScript engine is not currently registered on the Computer running the installer.
Vbscript.dll must get registered to solve the problem.

Ref: http://community.spiceworks.com/how_to/show/1577

This is a posible solution, boot your windows in safe mode with command prompt (by pressing 'f8' as the windows splash screen appears a menu will by prompted with this option), enter this:

C:\windows\system32\restore\rstrui.exe

in the command prompt and follow the instructions to restore the system.

If this doesn't work the problem may be a faulty hard disk, contact again if your problem persists.

uninstall all SQL components from the list of Programs installed

______________________________________________________

Catastrophic failure (0x8000ffff)
Cause
Any of the following could contribute to this issue:

An application is interfering with System Restore.
One or more of the core System Restore files are missing and/or corrupted.
The Volume Shadow Copy Service (VSS) has been disabled. System Restore depends on VSS volume snapshots being created via Shared Protection Points (SPP). System Restore cannot function if snapshot creation via SPP breaks or is disabled or if VSS is disabled.
Resolution
To resolve such issues, use these steps:

Try to use System Restore from WinRE, Safe Mode, or Windows Vista in a clean boot state. If that fails, proceed with the next steps.
Check for the following files in the %windir%\system32 directory:
Srrstr.dll
Srclient.dll
Srcore.dll
Rstrui.exe
Follow the "Restoring Core Files" section later in this document. You might want to follow the instructions in that section to reregister Srcore.dll. Keep in mind that you are not able reregister Srrstr.dll, Srclient.dll, and Rstrui.exe as doing so produces an error message.
Check that Volume Shadow Copy Service (VSS) is not disabled.
Check for either of the following registry keys:
HKLM\Software\Policies\Microsoft\WindowsNT\CurrentVersion\SystemRestore
HKLM\Software\Microsoft\WindowsNT\CurrentVersion\SystemRestore
If you find a DisableConfig DWORD set to 1 in either of these keys, export the key and delete it.
Try System Restore again.

Take my notes as a guide and hopefully this will work for you.

1. Start > Run > msconfig > “Start Up” tab > Disable All
2. “Services” tab > Check box “Hide Microsoft Services” > Disable All
2.5 Exit out, but don't reboot yet
3. Start > Right-click “My Computer” > “Properties” > “System Restore” > Check box “Turn off restore on Hard disks”
4. Start > Run > type %temp% > Edit Select All > Shift-Delete
Reboot machine
1. Combofix.exe. This program will run on its own. Also, it will likely wish to reboot the machine. Let it complete.
http://download.bleepingcomputer.com/sUBs/ComboFix.exe
2. WinSockFix.exe. This will fix any issues with the network connection.

3. SuperAntispyware.exe. This will remove all remaining spyware, tracking cookies, and browser hijackers.
Check to see that your favorite internet browser is working. Install or re-enable your favorite antivirus that failed to catch this in the first place.

Stop WinAntiVirus2008 Processes:
mav_startupmon.exe
uwa7pcw.exe
rtasks.exe
WinAv.exe
wa7pinst.exe
Remove WinAntiVirus2008 Registry Values:
2178F3FB-2560-458f-BDEE-631E2FE0DFE4
6F520BE0-9B54-4558-816F-224E67997DF3
459F4226-1AAB-43B6-9DC1-B6313EF83749
1AC5C88A-DEA7-462b-A232-04AF5CA42E7E
723D54C7-7483-4EB8-8EED-CE5B2AEA534D

Find and Delete these WinAntiVirus2008 Files:
WinAntiVirus Pro
WinAv.exe
uwa7pcw.exe
mav_startupmon
mav_startupmon.exe
rtasks
rtasks.exe
wa7pinst.exe
IH.exe
WinAntiVirus Pro.lnk
Reinstall or Uninstall WinAntiVirus Pro.lnk
WinAntiVirus Pro Manual.lnk
WapCHK.dll
rpt.dll
awvtr.dll
yayyvsp.dll
fcyxx.dll
gebxyax.dll
asmngr.dll
fopnl.dll
IEFWBHO.dll
Scnkrnl.dll
settings.dll
sqlite3.dll
WAV6COM.dll
winpgi.dll
BORLNDMM.dll
SCANADWR.dll
SCANBCDR.dll
SCANLDR.DLL
SCANDOS1.dll
SCANEMUL.dll
SCANFUNC.dll
SCANMCRL.dll
SCANOTHR.dll
SCANSCR.dll
SCANTOOL.dll
SCANTROJ.dll
SCANWIN1.dll
UNACPU.dll
UNADBX.dll
unamscan.dll
UNMIME.dll
UNPACK.dll
UNPACKS.dll
UNPACKS2.dll
UNPEPACK.dll

Vista

Stop WinAntivirus2008 Processes:
(Learn how to do this)
WinAntivirus2008.exe
mav_startupmon.exe
uwa7pcw.exe
rtasks.exe
WinAv.exe
wa7pinst.exe
Find and Delete these WinAntivirus2008 Files:
(Learn how to do this)
%UserProfile%\Desktop\Viruses.bdt
%UserProfile%\Desktop\WinAntivirus2008.lnk
c:\Program Files\WinAntivirus2008
c:\Program Files\WinAntivirus2008\Viruses.bdt
c:\Program Files\WinAntivirus2008\VRM2008.exe
c:\Documents and Settings\All Users\Start Menu\Programs\WinAntivirus2008
c:\Documents and Settings\All Users\Start Menu\Programs\WinAntivirus2008\WinAntivirus2008.lnk
%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\WinAntivirus2008.lnk
%UserProfile%\Application Data\Mozilla\Firefox\Profiles\s1jqw0bz.default\cookies.sqlite
WinAv.exe
uwa7pcw.exe
mav_startupmon
mav_startupmon.exe
rtasks
rtasks.exe
wa7pinst.exe
IH.exe
WinAntiVirus Pro.lnk
Reinstall or Uninstall WinAntiVirus Pro.lnk
WinAntiVirus Pro Manual.lnk
WapCHK.dll
rpt.dll
awvtr.dll
yayyvsp.dll
fcyxx.dll
gebxyax.dll
asmngr.dll
fopnl.dll
IEFWBHO.dll
Scnkrnl.dll
settings.dll
sqlite3.dll
WAV6COM.dll
winpgi.dll
BORLNDMM.dll
SCANADWR.dll
SCANBCDR.dll
SCANLDR.DLL
SCANDOS1.dll
SCANEMUL.dll
SCANFUNC.dll
SCANMCRL.dll
SCANOTHR.dll
SCANSCR.dll
SCANTOOL.dll
SCANTROJ.dll
SCANWIN1.dll
UNACPU.dll
UNADBX.dll
unamscan.dll
UNMIME.dll
UNPACK.dll
UNPACKS.dll
UNPACKS2.dll
UNPEPACK.dll
Remove WinAntivirus2008 Registry Values:
(Learn how to do this)
5222008A-DD62-49c7-A735-7BD18ECC7350
HKEY_CURRENT_USER\Software\WinAntivirus2008
2178F3FB-2560-458f-BDEE-631E2FE0DFE4
6F520BE0-9B54-4558-816F-224E67997DF3
459F4226-1AAB-43B6-9DC1-B6313EF83749
1AC5C88A-DEA7-462b-A232-04AF5CA42E7E
723D54C7-7483-4EB8-8EED-CE5B2AEA534D
WinAntivirus 2009

# 1. Find and Remove the following Antivirus 2009 Processes:
* av2009.exe
# 2. Find and Remove the following Antivirus 2009 files and folders:
* C:\Program Files\Antivirus 2009
* C:\Program Files\Antivirus 2009\av2009.exe
* c:\WINDOWS\system32\scui.cpl
* c:\WINDOWS\system32\winsrc.dll
# 3. Find and Remove the following Antivirus 2009 files and folders:
* HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\ CurrentVersion\Run\15358943642955870504508370025739

Download:Windows Vista Service Pack 1

I tried personally in WIN-XP worked same applies to Vista.

Error Message:
Error 1719. The Windows Installer Service could not be accessed. You may be running in safe mode or Windows Installer may not be correctly installed. Translation:
This message might appear when you’re trying to add or remove a program that installs via a Windows Installer MSI (Microsoft Software Installation) package file. The Windows Installer Service is the standard method for installing and uninstalling software on Windows XP. It keeps track of all of the components that need to be installed for a particular program to run and ensures that any files that are shared by programs are not removed when one of those programs is uninstalled. The Error 1719 is an indication that some Windows Installer Service files are missing or have become damaged. Solution:
The first thing to try is re-registering Windows Installer in the Windows registry. Make sure that no other programs are running and then click Start, Run, type msiexec /unregister in the Open field, and click OK. Next, click Start, Run, type misexec /regserver in the Open field, and click OK. Restart your computer and try installing or uninstalling again.

If you’re still getting the error message, the next step is to try reinstalling the Windows Installer files. In order to do this, you’ll first need to rename the existing files.

First, click Start, Run, and type msiexec /unregister in the Open field, and click OK.

In My Computer, click Search and locate the following three files: msi.dll, msiexec.exe, and msihnd.dll. They are hidden files so you’ll need to select Search Hidden Files And Folders under More Advanced Options. When you’ve found the files, rename them, by removing the .dll and .exe extensions and replacing them with an .old extension(for example msi.dll becomes msi.old).

Once you’ve renamed the files, WinXP will automatically replace them with a new copy from the dllcache (a hidden folder where copies of important system files are kept in case you mistakenly delete or rename critical system files). Restart your computer and try to install or uninstall the program again.

Finally, if neither of the above processes corrects the problem, boot into Safe Mode, and go through the above steps again, first re-registering and then reinstalling.

or

Go through the following links:

http://www.vistax64.com/vista-general/45784-windows-vista-error-1719-help-3.html

Hope this will be helpfull

Please rate me...

Thanks & Regards.
Nandu

My Scenario:

OS: MS Windows XP SP3 [Version 5.1.2600]
Printer: HP LaserJet 3390 (AiO) (Firmware datecode: 20070331)
Printer Connection: Connected via Ethernet with a static IP address
HP Driver Version: v4.0 (hp_LJ3050-3052-3055-3390-3392_Full_Solution_AMWE.exe)

Ran into same error that everyone else is experiencing. (see below)

Now Launching=X:\hpzmsi01.exe -m dot4msi -l XXX -f X:\DIVins??.DAT
Error message received: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753.
X:\HPZBDI32.msi failed with return code 1603
MSIInstall() failed with 1603
Exit code=1603

After debugging HP's installation scripts for 2 days, here is the cause & solution I identified to this specific install error. Once I got passed this error, everything installed without error and all functionality was working properly (including scanning!).


BACKGROUND:

Microsoft Installer (MSI) error 1603 is simply a generic "A fatal error occurred during installation" -- see http://msdn.microsoft.com/en-us/library/aa368542(VS.85).aspx. This is basically MSI telling you that something very bad has happened during the installation. In order to get more details, you can turn on MSI debug logging by following this MS Knowledge Base article (http://support.microsoft.com/kb/223300).

The MSI error code 2753 is the code for "The File '<file name>' is not marked for installation.". This error can be triggered by many scenarios, but usually, it has to do with the actual installation script not properly checking for the existence/non-existence of an installation file and then not marking it for either installation/removal. I know this sounds confusing, and it is. If your curious about all the possible causes, just Google for "msi 2753 not marked for installation" and you'll see lots of results which you can peruse for your own enjoyment.

In order to identify what was causing these 2 errors, I enabled debugging for MSI via the aforementioned MS KB article

CAUSE:

Certain HP services (and associated DLL files) were somehow partially/improperly installed. (Possibly, from a previous failed install?)

The Windows services (files) were:

Pml Driver HPZ12 (C:\Windows\System32\HPZipm12.dll)
Net Driver HPZ12 (C:\Windows\System32\HPZinw12.dll)

The existence of these 2 files in the System32 directory was causing this error in my situation. Somehow, the installation script was not identifying that these files were already installed (or improperly installed) and failing to properly set them to be installed again.

SOLUTION:

Steps:

1) Check to make sure that the 2 Windows services above are not running (or not installed).
2) Rename/delete the 2 associated service DLL files (this will only be possible once the services are stopped)
3) Run the installation again.

If all goes well, the install should now run without any issues.


Hope this helps since many people (including myself) have spent a lot of time (and HP Support chats) trying to find a workaround for this issue.

If you find this solution helped you out, please feel free to make a small donation to my PayPal ;)

Please try the following:

Click Start >> Run >>
Type the follow command in the Open box.
"net.exe stop wuauserv" (w/o quotes)
Press Ok

Repeat the same for the following commands:

regsvr32.exe wuapi.dll
regsvr32.exe wups.dll
regsvr32.exe wuaueng.dll
regsvr32.exe wucltui.dll
regsvr32.exe MSXML3.dll
regsvr32.exe qmgr.dll
regsvr32.exe qmgrprxy.dll
net.exe start wuauserv

Restart the machine and try again.

Click on the start button, click run
at the run window type the following:

sfc /scannow

now your windows system files will be checked for changed, if they are changed a fresh copy of the files will be copyed from the windows cd.

Note: you must have the original windows installation cd in the cd/dvd drive.

OK, here is my debugged/tested solution.

I know your error refers to a different installer MSI file (CIOUM32.msi) but the installation component in your log file (ipm12.A4B24390_80AD_4BAF_B8FD_C670FE0DB586) is identical to the one that was giving me trouble as well (i.e. points to the same service/file). So it is definitely worth a shot to try this solution out as it will only take a few minutes.

My Scenario:

OS: MS Windows XP SP3 [Version 5.1.2600]
Printer: HP LaserJet 3390 (AiO) (Firmware datecode: 20070331)
Printer Connection: Connected via Ethernet with a static IP address
HP Driver Version: v4.0 (hp_LJ3050-3052-3055-3390-3392_Full_Solution_AMWE.exe)

Ran into same error that everyone else is experiencing. (see below)

Now Launching=X:\hpzmsi01.exe -m dot4msi -l XXX -f X:\DIVins??.DAT
Error message received: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753.
X:\HPZBDI32.msi failed with return code 1603
MSIInstall() failed with 1603
Exit code=1603

After debugging HP's installation scripts for 2 days, here is the cause & solution I identified to this specific install error. Once I got passed this error, everything installed without error and all functionality was working properly (including scanning!).


BACKGROUND:

Microsoft Installer (MSI) error 1603 is simply a generic "A fatal error occurred during installation" -- see http://msdn.microsoft.com/en-us/library/aa368542(VS.85).aspx. This is basically MSI telling you that something very bad has happened during the installation. In order to get more details, you can turn on MSI debug logging by following this MS Knowledge Base article (http://support.microsoft.com/kb/223300).

The MSI error code 2753 is the code for "The File '<file name>' is not marked for installation.". This error can be triggered by many scenarios, but usually, it has to do with the actual installation script not properly checking for the existence/non-existence of an installation file and then not marking it for either installation/removal. I know this sounds confusing, and it is. If your curious about all the possible causes, just Google for "msi 2753 not marked for installation" and you'll see lots of results which you can peruse for your own enjoyment.

In order to identify what was causing these 2 errors, I enabled debugging for MSI via the aforementioned MS KB article

CAUSE:

Certain HP services (and associated DLL files) were somehow partially/improperly installed. (Possibly, from a previous failed install?)

The Windows services (files) were:

Pml Driver HPZ12 (C:\Windows\System32\HPZipm12.dll)
Net Driver HPZ12 (C:\Windows\System32\HPZinw12.dll)

The existence of these 2 files in the System32 directory was causing this error in my situation. Somehow, the installation script was not identifying that these files were already installed (or improperly installed) and failing to properly set them to be installed again.

SOLUTION:

Steps:

1) Check to make sure that the 2 Windows services above are not running (or not installed).
2) Rename/delete the 2 associated service DLL files (this will only be possible once the services are stopped)
3) Run the installation again.

If all goes well, the install should now run without any issues.


Hope this helps since many people (including myself) have spent a lot of time (and HP Support chats) trying to find a workaround for this issue.

If you find this solution helped you out, please feel free to make a small donation to my PayPal ;)