Encore 2.0 installation overwrites registry

After loading the Production Suite Premium package over a clean install of Win XP64 (running on a AMD 3400-equipped laptop, 100Gb 7200 rpm HD, 1 Gb RAM) and rebooting, my system "lost" the DVD/CD recorder (HL-DT-ST DVDRW GCA-4080N). Device Manager indicated that all the drivers were present, including PxHlpa64.sys installed by Encore, but returned an error message stating the device could not be found. Uninstalling the device and performing a PNP search/install returned an error message indicating registry corruption.
I wiped the system and redid the clean install, followed by an install of Prod Studio. The DVD was again "lost." I checked the registry and discovered that installing Encore deleted the entry "DeviceName CdRom0" from the hardware registry.
I wiped the system again for a clean OS install, and reinstalled the complete Prod Studio minus Encore. No "lost" DVD now...

Hi Neil,
I just recommended that he export the registry key that contained the device in question. Then after installing Encore, if the device recognition went fruit-shaped again (I love that phrase), he could merge the exported registry key into the registry and see if that solved his problem.
As for insight as to why the device went away in the first place, my head is still sore from all the scratching.
Creative Cow
-Jeff

Similar Messages

ITunes 7.0.1 installation overwrites registry data

iTunes 7.0.1 overwrites registry information in WindowsXP that causes the DVD device driver to be considered corrupted and the DVD device to no longer be recognized. This is for a Dell Inspiron E1505, but I imagine the problem is more universal.
Install at your own risk, but if you do and your DVD is no longer recognized, delete the UpperLimits and LowerLimits within the class for the DVD player and reboot.
When you fix this, note that when you access iTunes, then the iTunes player tells you to reinstall 7.0.1 if you want to import or burn to the DVD player.
This needs to be fixed ASAP by the Apple engineers.

iTunes 7.0.1 overwrites registry information in WindowsXP that causes the DVD device driver to be considered corrupted and the DVD device to no longer be recognized. This is for a Dell Inspiron E1505, but I imagine the problem is more universal.
are you getting a Code 41 error message next to your optical drives in Device Manager? if so, the standard treatment on PCs for that (even in cases where Easy CD Creator has not been installed on the PC) is given here:
(MS) CD-ROM access is missing and messages cite error Code 31, Code 32, Code 19, Code 39, or Code 41 after you remove Easy CD Creator in Windows XP
... but for more advanced and subtle techniques for tracking down the precise device filter conflict on your PC, see:
iTunes for Windows: Troubleshooting CD issues caused by device filters

Encore CS5.5 installation fails

Hi,
I've been trying to reinstall the adobe premiere family cs5.5 from my retail dvd, after many attempts the software will not install. I managed to install premiere pro cs5.5 without including encore in the installation process.
The error I receive is [Error DW050]
Are there any patch fixes to this problem?

Serial number and activation chat support (non-CC) is the only help link I have
http://helpx.adobe.com/x-productkb/global/service1.html

ADK Installation root registry not found?

Hi,
I am trying to image some machines in one location and for some reason we aren't able to. Basically it just PXE boots, finds it in the collection and then it is stopped with a command prompt open "x:\sms\bin\x64>" and doesn't do anything after
that.I checked the SMS log and all I see is the following:
ADK installation root registry value not found.
Loaded C:\Windows\system32\wimgapi.dll
Opening image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
Found Image file: D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
PackageID: LIA0029B
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
Closing image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
Any ideas or anything else I can check? TIA

Yes, see below TIA
<![LOG[Found new image LIA00004]LOG]!><time="13:43:59.968+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:00.046+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:00.077+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00004\boot.LIA00004.wim]LOG]!><time="13:44:00.077+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00004\boot.LIA00004.wim
PackageID: LIA00004
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:00.140+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00004\boot.LIA00004.wim]LOG]!><time="13:44:00.140+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00005]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00005\boot.LIA00005.wim]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00005\boot.LIA00005.wim
PackageID: LIA00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:00.982+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00005\boot.LIA00005.wim]LOG]!><time="13:44:00.982+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00095]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00095\boot.LIA00095.wim]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00095\boot.LIA00095.wim
PackageID: LIA00095
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:02.012+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00095\boot.LIA00095.wim]LOG]!><time="13:44:02.012+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA0016A]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA0016A\boot.LIA0016A.wim]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA0016A\boot.LIA0016A.wim
PackageID: LIA0016A
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA0016A\boot.LIA0016A.wim]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA001F4]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA001F4\boot.LIA001F4.wim]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA001F4\boot.LIA001F4.wim
PackageID: LIA001F4
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:02.963+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA001F4\boot.LIA001F4.wim]LOG]!><time="13:44:02.963+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00231]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00231\boot.LIA00231.wim]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00231\boot.LIA00231.wim
PackageID: LIA00231
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:03.509+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00231\boot.LIA00231.wim]LOG]!><time="13:44:03.509+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00269]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00269\boot.LIA00269.wim]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00269\boot.LIA00269.wim
PackageID: LIA00269
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00269\boot.LIA00269.wim]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00276]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00276\boot.LIA00276.wim]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00276\boot.LIA00276.wim
PackageID: LIA00276
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00276\boot.LIA00276.wim]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00288]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00288\boot.LIA00288.wim]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00288\boot.LIA00288.wim
PackageID: LIA00288
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00288\boot.LIA00288.wim]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA0029B]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
PackageID: LIA0029B
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:05.412+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim]LOG]!><time="13:44:05.412+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Begin validation of Certificate [Thumbprint 5FB5F1C55498CB354607662C58BE4C07D293356E] issued to 'f28c724a-201f-4900-91e0-d2f010b670d1']LOG]!><time="13:44:05.865+300" date="02-03-2015" component="SMSPXE" context=""
type="1" thread="6000" file="ccmcert.cpp:1662">
< ![LOG[Completed validation of Certificate [Thumbprint 5FB5F1C55498CB354607662C58BE4C07D293356E] issued to 'f28c724a-201f-4900-91e0-d2f010b670d1']LOG]!><time="13:44:05.865+300" date="02-03-2015" component="SMSPXE"
context="" type="1" thread="6000" file="ccmcert.cpp:1803">
< ![LOG[PXE Provider finished loading.]LOG]!><time="13:44:05.865+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="smspxe.cpp:184">

Installer Properties -- Registry: delete a key?

I know I can easily add registry keys and values under Windows specifying them in the Installer Properties --> Registry page of LabVIEW 8.2.1.
Is it possible to delete keys and values in the same way? I tried with the '-' character as I can do in a .reg file, but It doesn't work.
Is there a simple way?
Vix
In claris non fit interpretatio
Using LV 2013 SP1 on Win 7 64bit
Using LV 8.2.1 on WinXP SP3
Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

battler. wrote:
Hi,
I'm having trouble writing registry keys in Vista. Access seems to be denied for HKEY_LOCAL_MACHINE and only works for HKEY_CURRENT_USER.
For example, refer to the LV shipped example "write to registry.vi" and try it.
My application needs to write certain values to keys in the registry after installation then read them later. I have been placing these values in the HKEY_LOCAL_MACHINE until now. Is there a work-around to writing at run-time to HKEY_LOCAL_MACHINE? Is there another location in the registry which I can store the values for all users?
Thanks for your help.
Battler.
Sorry, I can't resist. The workaround is not to use Vista! And of course Windows 7.
The longer answer is you need to write code that elevates the impersonation level of the current user which will of course cause a login dialog to appear. And no there are no VIs for that so far, so it's about writing C code.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

SCCM 2012 Installation Directory Registry Key chaning automatically to Old Installation Path

Hi Guys,
I have recently recovered SCCM 2012 SP1 CAS Site from Primary Site by reinstalling CAS site and database was replicating with Primary sites properly after CAS recovery. But we noticed that after approx. 2 hours of CAS site recovery database replication stopped.
After long digging into SCCM log files we found that SCCM installation directory was pointing to old CAS Site Installation Directory (Which was before recovery) instead of NEW Installation Directory so we changed SCCM CAS Site Installation Directory manually
to new installation path in below registry key and everything was running fine again on CAS Site.
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Identification
But again when we restarted SMS_EXEUTIVE Service, SCCM Installation Directory again changed to old installation patch under above registry location and all is bad again. We are unable to figure out what is causing this and even we formatted our HDD before
installation CAS Site.
Can anyone please help to get rid of this issue. Our while CAS site is down due to this issue.
Thanks.

I think that you have to use the same installation directory in a site recovery scenario.
Torsten Meringer | http://www.mssccmfaq.de

App Builder Installer Build Registry Keys no longer created in Vista.

This board has been a great resource for answers...thank you all for your help.
Last week (7/31/09), an automatic MS Windows Vista Home Premium
upgrade was performed on my development PC. After the upgrade, I
used AppBuilder to build the final version of my application, which writes
3 string keys to the Window's registry. The Installer build completed successfully,
however, when I run setup.exe, I received an OS error stating that I don't
have permission to update the registry. I have full admin rights AND
User Account Control (UCS) is OFF. This error notification occurred 3
times, once for each registry addition attempt.
The installation was working correctly prior to this Vista update and still works in XP.
Any help would be greatly appreciated!
Please note that this is VI independent- the registry keys were created through
the AppBuilder 'Installer' tool.
I worry that this problem will manifest itself with all new LV application installations
that have the Vista upgrade.

Does the installation fail only when you try to install on computers that have the Vista update? Or since you have updated your development computer, when you build the installer again the installation will fail on any computer? Have you tried installing it on more than one computer with the Vista update?
Please attach the installer log for when the installation fails.
http://digital.ni.com/public.nsf/allkb/AB597E885DB7D16B86256E92006DB232?OpenDocument
Cheers,
David Goldberg
National Instruments
Software R&D

Encore problem during installation of CS4

Hello there,
We're having problems installing the full CS4 package onto a medical photography PC. New workstations have been bought and the whole app goes on without any problems but on trying to install on one of the older machines we the following errors..
The machine is XP SP3, with CS3 on previously.
Any ideas would be much appreciated!

These are very general suggestions and may play no role in your particular instance. This assumes that you are also installing from the DVD and not from the downloaded version, as there are a few other considerations there:
1.) turn off all anti-virus, pop-up blockers and spyware sweepers first.
2.) install under a full administrator account, not anything else.
3.) install onto the machine's C:\ and not to another HDD, or to a networked drive.
4.) once installed, run as a full administrator
I hope that something there helps you. Please report back, as others will likely have other ideas for you.
Good luck,
Hunt

Installation problems - component installation failed

i really need help in installation of adobe premiere pro cs3. i followed everything this link told me to do:
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402169&sliceId=1
i disabled antivirus, antispyware, windows defender, and start up programs except microsoft products.
i was only able to install adobe onlocation cs3. i have problems with adobe premiere procs3 and adobe encore cs3. the installation starts with system check. it proceeds all the way to progress. when it's about 80% progress, it stops and i get the error message component installation failed. for both these products the only parts of the software that successfully got installed is the third party components.
i have a gateway MT6707 using windows vista home premium 32 bit. it has intel pentium Dual Core and a 2 gb memory and 130 gb hard drive. if the laptop does not meet system requirements, i will get an error message telling me that the computer did not meet the minimum requirements. i know this because i tried installing the software on my desktop but in this case, the laptop met the minimum requirements.
i really do not know what to do. please help!

Ola, funny you had this problem, I experienced the
i exact same
thing last night.
I recently added 2 RAID arrays to my system and shuffled the drives around, and so I decided to format the machine and start fresh to avoid any conflicts.
I began installing software last night and ran into problems with Premiere & Encore but Onlocation installed fine, as you described it. I tried repeated attempts and it failed everytime much to my horror. I unistalled fonts, restarted, ran registry scanners, defragged, and I did most of what you described and nothing worked.
I have installed CS3 3 times prior to this so I know it works. I was getting frustrated and ready to post here. But I disabled my firewall (Comodo) before the installation and it worked!
I
b unistalled
it actually, and then it worked, not sure what the problem is but it worked and I was happy. I have just switched to Comodo after having endless crap with Agnitum Outpost, so I hope Comodo does not do the same.
I have XP Pro 32 bit so I am not sure if Vista would affect it, but I doubt it.
Try uninstalling your firewall...?

Lightroom 4.2 Installation Issue

Leaving this around in case anyone else has the same problem -- Solution found -- Windows installer issues / registry issues -- used the Microsoft Fix it tool (http://support.microsoft.com/kb/2438651#reso3) to correct. 4.2 install ran fine.
I've read through the posts in the Lightroom forum regarding LR 4.2 install issues. I will list here the things I've done to try to get the install to work:
1) Downloaded the installation software twice.
2) Ran the setup program in admin user mode.
3) Ran the install in admin user mode.
4) Get the following error in a Windows Installer window:
The feature you are trying to use is on a network resource that is unavailable.
Click ok to try again, or enter an alternate path to a folder containing the installation package 'Adobe_Lightroom_x64.msi' in the box below.
Use source:
c:\Users\RMJF\AppData\Local\Temp\{...}
What I have found (after displaying hidden AppData folder):
The location where the .msi file resides is different from the one defaulting in the above window.
I select this alternate path, but still cannot complete the installation.
Furthermore, when I cancel the install, I get this error:
Adobe Photoshop Lightroom 4.2 64-bit Installer Info
Error 1714. The older version of Adobe Photoshop Lightoom 4.2 64-bit cannot be removed. Contact your technical support group
I have been running LR since the beginning of time and most recently LR 4.1, so there is no 4.2 installed.
Also, I tried to fix the install of 4.1 via the programs in Control Panel. I cannot repair it and get this error:
The installation source for this product is not available. Verify that the source exists and that you can access it.
All versions (except the 1.0 version) were downloaded and installed from the Adobe LR site.
So, looking for suggestions.
Seems like there are some missing files from the 4.1 version that are hindering the install of 4.2???
All quite frustrating. Hope you can get me to a speedy solution.
(System info: Windows Vista 64-bit Home, SP 2, 20 GB of disk space to spare! Also, I have set the install program to be allowed by the anti-virus program. I have run a registry clean-up, as well. No other apps are running during the install.)
Message was edited by: marzo19

untill now, 3 phones later, and mayby 10 attemps later to install it: notting. the errors that i am gething are the same as above, but nothing helps for me.
even the microsoft fixid diden't help.
So also desperate.

Issues with Shockwave 11.5.2.602 / 11.5.6.606 MSI installer

<UPDATE 8/3/09> Nearly all of the issues mentioned below are still present in the MSI installer for 11.5.6.606 - the only one that Adobe have fixed is the one where the MozillaPlugins 'Version' value is left blank by the MSI by default - this is now created correctly, but all of the other issues remain.
Personally I have given up trying to use this MSI package to deploy Shockwave until Adobe get their act together - instead I am using a wrapper to wrap the Shockwave executable inside an MSI file and deploying it that way, although this is not ideal.
I have created an MST file which will fix the MSI installer for version 11.5.6.606, which I will post to another forum shortly, but I am not planning to keep it updated for future versions as I don't really have the time.
Hi,
I've tried submitting the following via the Adobe Customer Support portal and via the Feature Request/Bug Report form, but the first told me that I needed to 'get in touch with Adobe Enterprise Solutions team for getting help' and that 'to get in touch with them you have to purchase a contract', and the second resulted in a bounced email address saying that '[email protected]' 'does not exist at the organization this message was sent to'.
In short, attempting to contact Adobe to report issues with their installers sucks, and I am posting this here in the vain hope that someone at Adobe might read this message and possibly forward it to the relevant people. Some of the issues have already been reported here on this forum, but some of them are new, and I guess others might be interested in them too.
Hi,
I would like to report some issues with most recent version of the Shockwave installer, available in MSI format from the following location:
http://www.adobe.com/cfusion/entitlement/index.cfm?k=4E6102EB-DA7C-2795-C744826EFDE2A098&l oc=en_us
This is the installer for version 11.5.2.602, with a digital signature dated 06 November 2009 10:52:21
When downloading this version of the installer in Windows Installer (MSI) format, the following issues manifest themselves, most of which are not a problem when using the Full EXE installer available from the same page.
First of all, when installing the MSI file using Group Policy Software Deployment, if you log on to the computer after the MSI file has been deployed and view a web page that contains Shockwave content, you receive the following errors in the Windows event log:
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 16/12/2009
Time: 16:51:23
User: CRGS\DefaultUser
Computer: ITO01
Description:
Detection of product '{7D0F2155-D7D3-42CE-903F-684ADD77FF89}', feature 'Adobe_Shockwave_Player_', component '{E89F323D-7BDB-46E1-A0FD-6227821F94EA}' failed. The resource 'C:\WINDOWS\system32\config\systemprofile\Application Data\Adobe\' does not exist.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 16/12/2009
Time: 16:51:23
User: CRGS\DefaultUser
Computer: ITO01
Description:
Detection of product '{7D0F2155-D7D3-42CE-903F-684ADD77FF89}', feature 'Adobe_Shockwave_Player_' failed during request for component '{3D3697FC-DB90-46D8-9ED4-5D54B4901F62}'
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
If you are logged on as an Administrator, then the computer will immediately attempt to 'repair' the Adobe Shockwave Player installation in order to create the missing folder 'C:\WINDOWS\system32\config\systemprofile\Application Data\Adobe\', which leads to a significant delay in the initialization of the Shockwave content on the web page. If you are logged on as a non-Administrator, the errors will still appear, but the 'repair' operation will fail due to insufficient permissions to create the above folder.
I have done some testing and it seems as if this problem can be easily resolved by removing the code from the installer which tells it to create an empty folder in the 'Application Data' folder called 'Adobe\Shockwave Player 11'. This code seems to be entirely unnecessary, as no files are created inside this folder as part of the installation, and I have removed it successfully from my own copy of the MSI without it causing any issues. I have found some other people who are also experiencing this problem in the following forum post:
http://forums.adobe.com/message/2379350 (post number 8)
and since this 'repair' operation causes all customised registry settings to be reset back to defaults as part of the repair, it would be very helpful if this 'feature' could be removed from future versions.
Secondly, there are a number of registry keys which are created incorrectly by the MSI installer when the above 'repair' operation takes place, which need to be corrected to prevent further issues from occurring:
Under '[HKEY_CLASSES_ROOT\CLSID\{1F3CB77D-D339-49e0-B8E4-FECD6D6F8CB8}\LocalServer32]', the 'default' value is set to the following by the MSI:
C:\WINDOWS\system32\Adobe\SHOCKW~1\SWHELP~1.EXE"
(Please note that there is a double quotation mark at the end of the value, but not at the beginning)
Whereas the executable installer creates the value as follows:
"C:\WINDOWS\system32\Adobe\Shockwave 11\SwHelper_1152602.exe"
According to a forum post (http://forums.adobe.com/message/2379350, post 15), this causes DCOM errors when Shockwave is launched, if the MSI 'repair' has taken place as described above.
The above registry value should be set to the following in the installer's Registry table:
"[INSTALLDIR]Shockwave 11\SwHelper_1152602.exe"
so that the MSI installer works the same as the executable one.
Under '[HKEY_CLASSES_ROOT\TypeLib\{6EF568F4-D437-4466-AA63-A3645136D93E}\1.0\0\win32]', the 'default' value is set to the following by the MSI:
Adobe\SHOCKW~1\SWHELP~1.EXE
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Adobe\Shockwave 11\SwHelper_1152602.exe
Also, under '[HKEY_CLASSES_ROOT\TypeLib\{6EF568F4-D437-4466-AA63-A3645136D93E}\1.0\HELPDIR]', the 'default' value is set to the following by the MSI:
Adobe\SHOCKW~1\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Adobe\Shockwave 11\
Once again, the above registry values should be set to the following in the installer's Registry table to fix the issue:
[SystemFolder]Adobe\Shockwave 11\SwHelper_1152602.exe
[SystemFolder]Adobe\Shockwave 11\
Under '[HKEY_CLASSES_ROOT\CLSID\{166B1BCA-3F9C-11CF-8075-444553540000}]', the 'default' value is NOT SET by the MSI by default:
Whereas the executable installer creates the value as follows:
Shockwave ActiveX Control
This value should be set in the installer's Registry table to fix the issue.
Under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\common]', the 'default' value is set to the following by the MSI:
Macromed\common\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\common\
Also, under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\coreplayer]', the 'default' value is set to the following by the MSI:
Macromed\Shockwave 10\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\Shockwave 10\
Also, under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\coreplayerxtras]', the 'default' value is set to the following by the MSI:
Macromed\Shockwave 10\xtras\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\Shockwave 10\xtras\
The above registry values should be set to the following in the installer's Registry table to fix the issue:
[SystemFolder]Macromed\common\
[SystemFolder]Macromed\Shockwave 10\
[SystemFolder]Macromed\Shockwave 10\xtras\
The MSI installer does not create '[HKEY_CLASSES_ROOT\.dcr]', '[HKEY_CLASSES_ROOT\.dir]', or '[HKEY_CLASSES_ROOT\.dxr]'
Wherease the executable installer creates all three of these keys and populates them all with the following 'default' value:
"Content Type"="application/x-director"
These keys and values should be set in the installer's Registry table to fix the issue.
The MSI installer creates a value under the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OptionalComponets\SwDi r]
However this registry key is obviously misspelt (missing an 'n' in 'OptionalComponets') and should read as follows:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OptionalComponents\SwD ir]
This key name needs to be changed in the installer's Registry table to fix the issue (also pointed out in the following forum post: http://forums.adobe.com/message/2379350 (post number 10)).
Under [HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer], the 'Version' value is left blank by the MSI by default:
Whereas the executable installer creates the value as follows:
1152602
This registry value should be set to the correct version in the installer's Registry table to fix the issue.
Finally, the MSI installer creates a number of registry values under the following path:
[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer\Mime Types]
These values are *in addition* to the values created under the following path:
[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer\MimeTypes]
(Note there is no space between 'Mime' and 'Types' in the second key path)
The executable installer *only* creates registry keys under the 'MimeTypes' key, and it seems as if this is the correct formatting for the key (also pointed out in the following forum post: http://forums.adobe.com/message/2379350 (post number 11)).
The unnecessary 'Mime Types' registry keys and values should be removed from the installer's Registry table to avoid any potential issues.
I am sorry that this is such a long list, but it seems as if a number of things have been changed in the transition from 11.5.1.601 to 11.5.2.602, and it would be very helpful if these changes could be put back to how they were before, so that the MSI and the executable installers function in the same way as much as possible.
Message was edited by Borgquite - added 11.5.6.606 update

Have posted an updated version of the MST to my webspace here:
http://homepage.ntlworld.com/minkus/shockwave/shockwave115606mst2.zip
This new version fixes the following issues (changes to this version in bold):
MsiInstaller repair & errors on first run as non-admin (removes 'AppData' directory entries)
DCOM errors once Shockwave is installed (adds double quotes to the beginnning of LocalServer32 value)
Incorrect TypeLib paths in the registry (fixed to use built-in [SystemFolder] property)
Default CLSID description value missing (set to 'Shockwave ActiveX Control', as per the executable installer)
Incorrect Shockwave 10 paths in the registry (fixed to use built-in [SystemFolder] property)
Misspelt 'OptionalComponets' registry key (renamed to 'OptionalComponents')
Missing .dcr, .dir, .dxr Content Type registry values (included in the executable installer)
Fixed incorrect AppID registry key (set to use installer's [VERSION] variable)
Removed 'Launch SWDNLD.exe' shortcut created in Programs subfolder (people don't want this - see here)
I have tested this on my network and it all seems to work fine. Unfortunately my original plan to use the executable installer didn't work out as it does not include the Shockwave 10 compatibility components described here and here, so it looks like I'll have to keep this MST file up to date with the latest versions until Adobe fix the problems themselves...
If you want to see the changes that I have made, load up Adobe's 11.5.6.606 MSI file in Orca, then use Transform / Apply Transform to apply the MST, and look for the entries in green.
Please post any feedback to this thread, and I will try to respond if I can help!
Chris Hill

Error-33 building installer

I am done with a project and I am trying to build an installer for it. I have not been successful. I have all the files needed inside the project. I tested it and run the main Vis and there's no error. But when Im trying to build the installer, I select my source files and se the Additional installers to automatic selection I get this error each time:
Forgive me if it's too long! can someone explain to me what that means.
CDK_CreateNewWizard_Invoke.vi.ProxyCaller >> CDK_CreateNewWizard_Invoke.vi >> AB_CreateNewWizard_Invoke_CORE.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment information
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error loading source distribution info for product 'NI .NET Framework 2.0 Language Pack x86 Installer' from registry.
Error in MDF:istributionSourceCollection::LoadProductSourceFromNISysInfo
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\DotNet20langpack_x86_Installer\DotNet20x86langpack.msi
Path of part in product: DotNet20x86langpack\DotNet20x86langpack.msi
*** End Error Report
*** WARNING ***
Ignoring 'NI .NET Framework 2.0 Language Pack x86 Installer' because there is an error in this product's installation data. Updating, repairing, or reinstalling the product may resolve this issue.
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error loading source distribution info for product 'NI .NET Framework 2.0 Language Pack x86 Installer' from registry.
Error in MDF:istributionSourceCollection::LoadProductSourceFromNISysInfo
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\DotNet20langpack_x86_Installer\DotNet20x86langpack.msi
Path of part in product: DotNet20x86langpack\DotNet20x86langpack.msi
*** End Error Report
*** WARNING ***
Ignoring 'NI .NET Framework 2.0 Language Pack x86 Installer' because there is an error in this product's installation data. Updating, repairing, or reinstalling the product may resolve this issue.
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error loading source distribution info for product 'NI .NET Framework 2.0 Language Pack x86 Installer' from registry.
Error in MDF:istributionSourceCollection::LoadProductSourceFromNISysInfo
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\DotNet20langpack_x86_Installer\DotNet20x86langpack.msi
Path of part in product: DotNet20x86langpack\DotNet20x86langpack.msi
*** End Error Report
*** WARNING ***
Ignoring 'NI .NET Framework 2.0 Language Pack x86 Installer' because there is an error in this product's installation data. Updating, repairing, or reinstalling the product may resolve this issue.
Adding files to installer
Validating...
Copying files...
Scanning files...
Updating files...
Build complete successfully.
Done adding files
Preparing to build deployment
Copying products from distributions
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem
Error in MDF:istributionSourceCollection::LoadDist
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\LabVIEW_RT_TraceToolkit_Support_90\LabV90\RTETT_LV_90.msi
Path of part in product: LabVIEW_RT_TraceToolkit_Support_90\RTETT_LV_90.msi
*** End Error Report
Done building deployment

In regards to needing to put in the CDs, LabVIEW will ask you to do so unless you actually transfer the installers to your computer. When you install LabVIEW, it uses the installers on the CD to install to your machine. It won't copy the installer files to your computer by default, as this would waste several GBs of space. You would have to physically copy them from the disk or download them from ni.com/donwloads to get them on your desktop. (This is true for any program, which is why you need installation disks to install or build installers unless you have the installer files on your computer.)
In regards to the error, which XML file in the link I posted previously matched yours? Revision A or Revision B? Can you please post the precise error with Revision A replacing your XML file and the precise error with Revision B replacing your XML file? I would expect the file paths listed to be slightly different.
Could you also post the precise path of the "NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml" file on your computer?
Regards,
David R
Applications Engineer
National Instruments

Installation of update KB2977320 results in error code 29569 and 45671

When trying to manually install the update KB2977320 after the automatic installation failed I get the following entries in my log:
2014-11-20 17:10:47 Slp: Sco: Attempting to normalize directory path 'c:\Program Files\Microsoft SQL Server\100\Shared\SqlWtsn.exe.config'
2014-11-20 17:10:47 Slp: Sco: Attempting to check if file 'c:\Program Files\Microsoft SQL Server\100\Shared\SqlWtsn.exe.config' exists
2014-11-20 17:10:47 Slp: App config file c:\Program Files\Microsoft SQL Server\100\Shared\SqlWtsn.exe.config was not found
2014-11-20 17:10:47 Slp: Completed Action: NotifyProgressComplete, returned True
2014-11-20 17:10:47 Slp: ----------------------------------------------------------------------
2014-11-20 17:10:47 Slp: Running Action: FinalizeProgressStatus
2014-11-20 17:10:47 Slp: Completed Action: FinalizeProgressStatus, returned True
2014-11-20 17:10:47 Slp: ----------------------------------------------------------------------
2014-11-20 17:10:47 Slp: Running Action: CloseUI
2014-11-20 17:10:47 Slp: Stop action skipped in UI Mode Quiet
2014-11-20 17:10:47 Slp: Completed Action: CloseUI, returned True
2014-11-20 17:10:49 Slp:
2014-11-20 17:10:49 Slp:
2014-11-20 17:10:49 Slp: ----------------------------------------------------------------------
2014-11-20 17:10:49 Slp:
2014-11-20 17:10:49 Slp: Error result: -2068024447
2014-11-20 17:10:49 Slp: Result facility code: 1212
2014-11-20 17:10:49 Slp: Result error code: 29569
2014-11-20 17:10:49 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-11-20 17:10:49 Slp: Sco: Attempting to open registry subkey
2014-11-20 17:10:49 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2014-11-20 17:10:49 Slp: Sco: Attempting to get registry value DW0200
2014-11-20 17:10:51 Slp: Received request to add the following file to Watson reporting: C:\Users\schmieder\AppData\Local\Temp\tmp87E8.tmp
2014-11-20 17:10:51 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2014-11-20 17:10:51 Slp: Inner exceptions are being indented
2014-11-20 17:10:51 Slp:
2014-11-20 17:10:51 Slp: Exception type: System.IO.IOException
2014-11-20 17:10:51 Slp: Message:
2014-11-20 17:10:51 Slp: Das Verzeichnis ist nicht leer.
2014-11-20 17:10:51 Slp:
2014-11-20 17:10:51 Slp: Stack:
2014-11-20 17:10:51 Slp: bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
2014-11-20 17:10:51 Slp: bei System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive)
2014-11-20 17:10:51 Slp: bei System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive)
2014-11-20 17:10:51 Slp: bei Microsoft.SqlServer.Chainer.Infrastructure.WatsonService.CreateCab(WatsonBucket bucket)
2014-11-20 17:10:51 Slp: bei Microsoft.SqlServer.Chainer.Infrastructure.WatsonService.ReportFailures()
2014-11-20 17:10:51 Slp: bei Microsoft.SqlServer.Chainer.Setup.Setup.Start()
2014-11-20 17:10:51 Slp: bei Microsoft.SqlServer.Chainer.Setup.Setup.Main()
2014-11-20 17:10:51 Slp: Watson Bucket 2
Original Parameter Values
2014-11-20 17:10:51 Slp: Parameter 0 : SQL2008@RTM@KB2977320
2014-11-20 17:10:51 Slp: Parameter 3 : System.IO.IOException@-2147024751
2014-11-20 17:10:51 Slp: Parameter 4 : System.IO.IOException@-2147024751
2014-11-20 17:10:51 Slp:
Final Parameter Values
2014-11-20 17:10:51 Slp: Parameter 0 : SQL2008@RTM@KB2977320
2014-11-20 17:10:51 Slp: Parameter 3 : 0xAE9CC9E3
2014-11-20 17:10:51 Slp: Parameter 4 : 0xAE9CC9E3
2014-11-20 17:10:51 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-11-20 17:10:51 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-11-20 17:10:51 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-11-20 17:10:52 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2014-11-20 17:10:52 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-11-20 17:10:52 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2014-11-20 17:10:53 Slp: Das Verzeichnis ist nicht leer.
2014-11-20 17:10:53 Slp: Watson bucket for exception based failure has been created
2014-11-20 17:10:53 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-11-20 17:10:53 Slp: Sco: Attempting to open registry subkey
2014-11-20 17:10:53 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2014-11-20 17:10:53 Slp: Sco: Attempting to get registry value DW0200
2014-11-20 17:10:54 Slp: Submitted 2 of 2 failures to the Watson data repository
2014-11-20 17:10:54 Slp:
2014-11-20 17:10:54 Slp: ----------------------------------------------------------------------
2014-11-20 17:10:54 Slp:
2014-11-20 17:10:54 Slp: Error result: -1251036569
2014-11-20 17:10:54 Slp: Result facility code: 1390
2014-11-20 17:10:54 Slp: Result error code: 45671
Any help is very appreciated.
Thanks!

Hi Technowizard15,
As your description, you come across an error when you manually install security update(KB2977320). Based on my research, security update(KB2977320) is used for SQL Server 2008 R2 Service Pack 2. So firstly, please check if your SQL Server version is SQL
Server 2008 R2 Service Pack 2 according to Shanky_621's post. If it is not SQL Server 2008 R2 Service Pack 2, you need to install related security update according to your SQL Server version.
However, if the error occurs when you use SQL Server 2008 R2 Service Pack 2, please help to post full error message in Detail.txt(%Program Files%\Microsoft SQL Server\100\Setup Bootstrap\Log\<YYYYMMDD_HHMM>\Detail.txt) for further analysis. For more
information about the process, please refer to the article:
http://support.microsoft.com/kb/955396. Additionally, based on my research, the issue could occur in the cases below.
1. Your account has no access to the following registry key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer. So please check if your account has access to the registry. If it has no access, you could follow the steps below to troubleshoot
your issue.
a. Located HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer in registry.
b. Right click and go to Permission, then you could see user accounts or groups. If your user account is not in the list, you could click Add to add your account there.
c. Select your account and check Full Control. Next, Click OK.
d. Install the update KB2977320 again. Please stop any Antivirus software in the installation process.
2. Installer Package (MSI) is missing. Please check if MSI exists in C:\Windows\Installer. If it doesn’t exist, you could solve this issue by one of the methods. Then install the update KB2977320 again and check if the error still occurs.
a. Use a script.
b. Manually restore the files.
For more information about the process, please refer to the article:
http://support.microsoft.com/kb/969052
Regards,
Michelle Li

Installation error - Oracle Database 10g Express Edition

Hi - I've just tried to install Oracle Database 10g Express Edition from the Oracle website and I'm getting this error.
Error 1327 Invalid Drive: I:\ . I've googled the error but can't find much. It seems that the path is hardcoded into the msi installation package.
Anyone else seen this issue before as I'm at a loss at what to do ?
I'm wondering do I have to create an I:\ drive on my machine but that seems a little unusual
Hope someone can help
Cheers.

This problem may occur if you have used the Disk Administrator utility included in Microsoft Windows to change the drive letter of the hard disk that the operating system is installed on, for example, the C drive.
The problem occurs because the Oracle Universal Installer uses registry keys to determine the locations of certain folders that are required to install Oracle. If the drive letter of the hard disk that contains the operating system has been changed, the registry keys refer to nonexistent folders and Setup fails.
To correct this problem, use the Windows Disk Administrator program to restore the drive letter of the hard disk to its original value:
1. Click Start, point to Programs, point to Administrative Tools, and click Disk Administrator.
2. Right-click the drive whose letter you want to change. On the shortcut menu, click Assign Drive Letter.
3. Select the correct drive letter from the list and click OK.
If you are prompted to quit the Disk Administrator or to restart your computer, do so. Once the computer has restarted, attempt to install again.

I want adobe encore but it not found in the ADOBE CREATIVE CLOUD

the question is if I buy Adobe Premiere Pro
did the encore and the encode included in it ?
thanks

As the above post comments, one gets Encore via having the CC license, then downloading a "Previous Version" through the CC desktop app, choosing Premiere Pro CS6, but then if you only want Encore, in the installation box you say only install Encore.
Adobe has a blog post on how to setup Encore ... as you'll need to both download/install, then download a couple other "libraries" of things for it, unzip & place those in specific directories, THEN Encore is totally available for use. Found at the following link:
Encore CS6 not installed with Creative Cloud
It would also be useful to search here for "encore installing"
Neil

Encore 2.0 installation overwrites registry

Similar Messages

Maybe you are looking for