Admin install failure.

This seems to be a common problem, but nothing has worked so far... when ever I try to install adobe air installer. exe I get the error message: An error occurred while installing Adobe AIR. Installation may not be allowed by your administrator. Please contact your administrator. I AM the system admin... im running Vista and here is the .airinstall.log :
Performing runtime install
UI SWF load is complete
UI initialized
starting user confirmation
Version of this installer: 1.5.2.8870
Installation type: new
starting elevated install
Launching elevated sub-installer failed
runtime install entering error state: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="Launching elevated sub-installer failed" errorID=5100]
begin quitting
Hope some one could direct me in the right way- thannks
P.S. I have never had any previous version of AA.

Finaly after much fooling around with the file I got it to work. I compressed the installer exe into a .rar file then viewed files(In win .rar program) this showed 3 files: application, windows installer package,and file sfw. I just ran the "windows installer package". it configured AIR and installed with out any problem. I dont know why this worked but, one win goes to randomly clicking buttons. Hope this Helps some of you other little buddies out there.

Similar Messages

Remote Install Failure on AIA3.0

Hi,
Remote Install Failure on AIA 3.0:
AIA 3.0 installations on Windows XP-Pro is failing in Step 4 of 11 with the Error
"Node manager is down or the username and password entered is incorrect"
Details on the installation are as follows:
1) Installation is done on a Windows-XP 32 bit SP2, RAM - 4 GB.
2) SOA Suite 11gR1 PS1 and Weblogic 10.3.2 successfully installed.
3) SOA managed server, Admin server and node manager are running successfully on remote server.
4) The status of Node manager is reachable and has been confirmed through the admin console.
5) When installing AIA 3.0 use Remote Install option, the 4th step is failing after providing the node manager credentials of remote server.
Error message is "Node manager is down or the username and password entered is incorrect".
6) We given remote server configuration on 4th step (Host Name, Admin Port, Domain name, user/pass).
7) The Remote WLS Server is reachable.
8) Installer is always looking local node manager is not looking for Remote node manager which one is running on remote machine.
Error Log
Adding C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM for deletion.
Adding to classpath:file:/C:/WINNT/TEMP/OraInstall2010-04-29_04-25-49PM/ext/jlib/soawl.jar
Adding to classpath:file:/C:/WINNT/TEMP/OraInstall2010-04-29_04-25-49PM/ext/jlib/template.jar
null
configFileName:C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\footprint.xml
osName:Windows XP
Inside startPreReqOperation...prereq
osName:Windows XP
diskSpaceRequirements from engine:Home id =SoftwareOnlyOraclehome name=Oracle home variable=%AIA_HOME_PATH% fixedSpace=2048 unit=MB condition=null totalSpaceRequired=0 isConditionSatisfiedfalse
entryPoint: entryPoint = oracle.installType.all condition = null className = null
contextFile:C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\prereq\oui\agent_prereq_context.xml
The entry point is: oracle.installType.all
Check Name:CertifiedVersions
Check Description:This is a prerequisite condition to test whether the Oracle software is certified on the current O/S or not.
Expected result: One of 5.1,5.2,6.0,6.1
Actual Result: 5.1
Check complete. The overall result of this check is: Passed
Check Name:ServicePackChecks
Check Description:This is a prerequisite condition to test whether the Service Pack level recommended for installing the product is available on the system.
Expected result: 2
Actual Result: 2
Check complete. The overall result of this check is: Passed
Check Name:TotalMemory
Check Description:This is a prerequisite condition to test whether the system has sufficient physical memory.
Expected result: 1024MB
Actual Result: 3191MB
Check complete. The overall result of this check is: Passed
Property File location: D:\AIA3.1\New Folder\cd\Disk1\install\win32\aiaoneclick.properties
Item State: javax.swing.JComboBox[,170,52,262x18,invalid,layout=com.jgoodies.looks.plastic.PlasticComboBoxUI$PlasticComboBoxLayoutManager,alignmentX=0.0,alignmentY=0.0,border=,flags=4194632,maximumSize=,minimumSize=,preferredSize=,isEditable=true,lightWeightPopupEnabled=true,maximumRowCount=8,selectedItemReminder=AIA3]
Path: D:\Oracle11GPS\Oracle\Middleware_new\AIA3
Item State: javax.swing.JComboBox[,170,81,262x18,invalid,layout=com.jgoodies.looks.plastic.PlasticComboBoxUI$PlasticComboBoxLayoutManager,alignmentX=0.0,alignmentY=0.0,border=,flags=4194632,maximumSize=,minimumSize=,preferredSize=,isEditable=true,lightWeightPopupEnabled=true,maximumRowCount=8,selectedItemReminder=D:\Oracle11GPS\Oracle\Middleware_new\AIA3]
Home: AIA3
In processFieldStringAIA Home
In processFieldStringJAVA HOME
In processFieldStringAIA Home Path
In processFieldStringAIA Instance Name Contains invalid characters
getting root directory
D:\oracle11GPS\Middleware\user_projects\domains\dev_domain
truevalue for type of install
D:\Oracle11GPS\Oracle\Middleware_new\jdeveloper
D:\Oracle11GPS\Oracle\Middleware_new
*****Web Logic Home: D:\Oracle11GPS\Oracle\Middleware_new\wlserver_10.3
CLASSPATH: D:\Oracle11GPS\Oracle\Middleware_new\wlserver_10.3\server\lib\weblogic.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM;;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\adapters.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\adf-config.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\aqapi.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\bpelImport.log;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\ccrQueries.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\com.bea.cie.comdev_6.1.0.0.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\com.bea.cie.config_6.0.0.0.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\com.bea.core.common.security.api_1.0.0.0_5-1-0-0.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\com.bea.core.nodemanager.plugin_1.3.0.0.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\commonutils.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\connections.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\dms.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\emocmutl.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\encrypt.bat;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\encrypt.sh;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\engine.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\enginehelp.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\footprint.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\glassfish.jaxb.xjc_1.0.0.0_2-1-7.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\glassfish.jaxb_1.0.0.0_2-1-7.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvest-tasks.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvest.bat;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvest.sh;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvester-10.3.1.0.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvester-ant.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvesterSettings.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\install.properties;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\jython-modules.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\log-config.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\log4fl.properties;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\message.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\ojdbc5.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\ojdl-log4j.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\ojdl.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\ojdl2.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\oneclick.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\oneofftool.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\runant.bat;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\runant.sh;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\setenv.bat;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\setenv.sh;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\soainstallhelp.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\soawl.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\SysInfo.dll;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\template.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\tools.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\tools11g.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\types.properties;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\wlcipher.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\wlfullclient.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\wtinstallhelp.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\xml.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\xmlparserv2.jar;;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\OraInstaller.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\oneclick.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\xmlparserv2.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\share.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\OraInstallerNet.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\emocmutl.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\emCfg.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\OraPrereq.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\jsch.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\ssh.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\remoteinterfaces.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\http_client.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\OPatch\jlib\opatch.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\OPatch\jlib\opatchactions.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\OPatch\jlib\opatchprereq.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\OPatch\jlib\opatchutil.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstImages.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_de.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_es.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_fr.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_it.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_ja.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_ko.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_pt_BR.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_zh_CN.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_zh_TW.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\oracle_ice.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\help4.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\help4-nls.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\ewt3.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\ewt3-swingaccess.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\ewt3-nls.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\swingaccess.jar;\;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\jewt4.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\jewt4-nls.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\orai18n-collation.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\orai18n-mapping.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\ojmisc.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\xml.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\srvm.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\classes12.jar
1
localhost
LocalMachine
Connecting to Node Manager ...
<Apr 29, 2010 4:31:11 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Either the password and username entered are incorrect or the node manager is down
Traceback (innermost last):
File "<string>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 618, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : I/O error while reading domain directory
Use dumpStack() to view the full stacktrace
Anyone knows how to install AIA Remote Install on the remote SOA server?

Hi,
may be you enter the wrong username or password? Or there is a problem with certificate? The look file describe a wrong user name or password or nm is not reachable. Is it possible to start managed server via Admin Console? Please check nm log files.
Regards,
Marcel

11g Install Failure, Listener Error.

11g Install Failure, Listener.
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor.
I am attempting to install 11g, 11.1.0 onto a stand alone box which has Windows XP SP2 as the OS.
The box is at present not networked and as is not on a domain. The computer name is homedb.
I have installed the loopback adapter on 10.10.10.10 and updated my hosts file, the computer can resolve this to the computer name and vice versa.
Upon installing 11g and the starter database, the install continues normally, succeeding with the Oracle Net Configuration Assistant. However when the Oracle Database Configuration Assistant is run, 89% of the way through an error is thrown as follows:
Enterprise manager configuration failed due to the following error -
Listener is not up. Start the listener and run EM configuration again.
Refer to the log file at C:\Oracle\cfgtoollogs\dbca\emConfig. Log for more details.
You can retry configuring this database with Enterprise Manager later by manually running C:\Oracle\product\11.1.0\db_1\bin\emca script.
When I click ok on the error message the install completes as normal.
I can TNSPING orcl which results in the following:
TNS Ping Utility for 32-bit Windows: Version 11.1.0.6.0 - Production on 20-JAN-2
008 12:36:33
Copyright (c) 1997, 2007, Oracle. All rights reserved.
Used parameter files:
C:\oracle\product\11.1.0\db_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = homedb)(
PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl)))
OK (20 msec)
I can connect to the database using sqlplus sys/password as sysdba but when I try to connect using
sqlplus sys@orcl and typing in the password I get the following error:
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor.
This is also the error I get when using sql developer to connect to the db.
The extract from the log file mentioned above is as follows:
20-Jan-2008 12:14:09 oracle.sysman.emcp.util.GeneralUtil initSQLEngine
CONFIG: SQLEngine created successfully and connected
20-Jan-2008 12:14:09 oracle.sysman.emcp.ParamsManager checkListenerStatusForDBControl
CONFIG: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
     at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeImpl(SQLEngine.java:1530)
     at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeSql(SQLEngine.java:1771)
     at oracle.sysman.emcp.ParamsManager.checkListenerStatusForDBControl(ParamsManager.java:2708)
     at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:368)
     at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:147)
     at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:222)
     at oracle.sysman.assistants.util.em.EMConfiguration.run(EMConfiguration.java:460)
     at java.lang.Thread.run(Thread.java:595)
20-Jan-2008 12:14:09 oracle.sysman.emcp.EMConfig perform
SEVERE: Listener is not up. Start the Listener and run EM Configuration Assistant again .
Refer to the log file at C:\oracle\cfgtoollogs\dbca\orcl\emConfig.log for more details.
20-Jan-2008 12:14:09 oracle.sysman.emcp.EMConfig perform
CONFIG: Stack Trace:
oracle.sysman.emcp.exception.EMConfigException: Listener is not up. Start the Listener and run EM Configuration Assistant again .
     at oracle.sysman.emcp.ParamsManager.checkListenerStatusForDBControl(ParamsManager.java:2715)
     at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:368)
     at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:147)
     at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:222)
     at oracle.sysman.assistants.util.em.EMConfiguration.run(EMConfiguration.java:460)
     at java.lang.Thread.run(Thread.java:595)
20-Jan-2008 12:14:09 oracle.sysman.emcp.EMConfig restoreOuiLoc
CONFIG: Restoring oracle.installer.oui_loc to C:\oracle\product\11.1.0\db_1\oui
My listener, tnsnames and sqlnet are as follows:
listener.ora:
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = homedb)(PORT = 1521))
sqlnet.ora:
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
tnsnames.ora:
ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = homedb)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl)
When logged into the database a SHOW PARAMETER SERVICE results in a service of orcl
Running the command: lsnrctl service, results in the following:
LSNRCTL for 32-bit Windows: Version 11.1.0.6.0 - Production on 20-JAN-2008 12:46
:52
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
The listener supports no services
The command completed successfully.
Running lsnrctl status results in the following:
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 11.1.0.6.0 - Produ
ction
Start Date 20-JAN-2008 12:09:10
Uptime 0 days 0 hr. 40 min. 9 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File C:\oracle\product\11.1.0\db_1\network\admin\listener.o
ra
Listener Log File c:\oracle\diag\tnslsnr\homedb\listener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=homedb)(PORT=1521)))
The listener supports no services
The command completed successfully
I have re run the db configuration again but it would not start because apparently there was no listener, running the Net Configuration Assistant makes no difference.
All firewalls and anti virus software have been disabled for the purposes of this install.
Do I need to manually register the listener with the database, if so how do I go about doing this?
I have installed 10g on a standalone box before with no trouble, what have I missed here?, any help greatly appreciated.

To answer my own question I fixed this by issuing the command
netsh winsocks reset
Winsocks deals with windows networking and can become corrupt through installs of software, virus cleaning, etc.
Hope that helps,
Adam

Error 1308.Source file not found with 9.4.2 Admin Install point

I'm including as much information in this post as possible to help narrow down my problem, so if it's too wordy I appologize.
I've created an Admin install point for Acrobat 9 patching it up to Acrobat 9.4.2 using the following commands in a batch file:
D:
cd \Adobe\Acrobat\AcrobatPro9
md \Adobe\Acrobat\AcrobatPro9AIP
start /wait msiexec /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP /Liv D:\Adobe\Acrobat\AcrobatPro9AIP\install900.log /qn
cd \Adobe\Acrobat\AcrobatPro9AIP
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcroProStdUpd910_T1T2_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install910.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd912_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install912.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd920_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install920.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd930_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install930.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd932_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install932.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd933_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install933.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd940_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install940.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd941_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install941.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd942_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install942.log /qn
I rename the folder "AcrobatPro9AIP" to reflect the current version (e.g. "Acrobat9.4.2"), copy the folder to my DFS, create an MST with the Customization Wizard, and then deploy with Group Policy.
Before I deploy I always run a few test installations on two Windows XP 32-bit machines, and two Windows 7 64-bit workstations. I've been using this method to build my install point for the last 5 Adobe patches without a problem, but suddenly with version 9.4.2 my test workstations pop up with the following error during the installation via the standard installation method "msiexec /i acropro.msi TRANSFORMS=acropro.mst":
I built my installation package for acrobat9.4.1, 9.4.0 and 9.3.3 exactly the same way and the installations did not have this error. The file in question "Adobe.Acrobat.Dependencies.manifest" does not exist in my 9.4.1, or 9.4.0 package folders, nor does it exist in the 9.4.2 folder. Any suggestions?

I am having the same problem, all the relevant info was already covered in the "thewaker" post above.   I too have made a script to make a Admin install with patches up to 9.4.2. The script worked for 9.3.3 but when I remade the AdobeAIP for 9.4.2, I too got this error when installing it, even manually. (Error 1308.Source file not found. Adobe.Acrobat.Dependencies.manifest ) Running on Windows 7 32bit.
Here is my Script.
C:
cd\AcroBatPro9
md \AcrobatPro9AIP
start /wait msiexec /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP /Liv c:\AcrobatPro9AIP\install900.log /qn
cd \AcrobatPro9AIP
start /wait msiexec /p c:\AcrobatPro9\AcroProStdUpd910_T1T2_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install910.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd912_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install912.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd920_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install920.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd930_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install930.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd932_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install932.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd933_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install933.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd940_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install940.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd942_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install942.log /qn
I did notice though that the "thewaker" has added AcrobatUpd941_all_incr.msp to his script, which is a security update. Which may be "a" problem, but I don’t think this is related to the problem we are having.
Administrative deployment
Administration Installation Point (AIP) deployments must not apply a quarterly update AIP in which a security update was the most recently applied update. Because a quarterly update includes the changes implemented in all recent security updates, the quarterly update forcibly bypasses those updates entirely. To deploy a quarterly update from an AIP, create a AIP which includes only quarterly updates as follows:
    Acceptable:      Acrobat 9.0.0 -> 9.1.0 (Quarterly) -> 9.1.2 (Quarterly) -> 9.2.0 (Quarterly) -> 9.3.0 (Quarterly) -> 9.3.2 (Quarterly) -> 9.3.3 (Quarterly) -> 9.4.0 (Quarterly) -> 9.4.1 (Security)
    Acceptable:      Acrobat 9.0.0 -> 9.1.0 (Quarterly) -> 9.1.2 (Quarterly) -> 9.2.0 (Quarterly) -> 9.3.0 (Quarterly) -> 9.3.2 (Quarterly) -> 9.3.3 (Quarterly) -> 9.4.0 (Quarterly) -> 9.4.2 (Quarterly)
    Unacceptable: Acrobat 9.0.0 -> 9.1.0 (Quarterly) -> 9.1.2 (Quarterly) -> 9.2.0 (Quarterly) -> 9.3.0 (Quarterly) -> 9.3.2 (Quarterly) -> 9.3.3 (Quarterly) -> 9.4.0 (Quarterly) -> 9.4.1 (Security) -> 9.4.2 (Quarterly)
Anyway.. Any help with this would be helpful as I would like to deploy it soon.
Thanks.

How to change number of retries and delay before retrying after software install failure

I deploy a software to client, but the installation is fail, so it will retry. but How to change the number of retries and delay before retrying after software install failure?
I find "Retry Settings" in "Software Distribution Component Properties". But I think it work for Distribution, not the installation. am I right?

First, are you referring to packages or applications because the behavior is different.
Also, why do you want it to retry a failure? It failed for a reason so you need to fix the cause of the failure first. If it failed the first, it will likely fail the next time for the same reason. In general, ConfigMgr will only retry on transient type
errors.
Jason | http://blog.configmgrftw.com

Photoshop Elements 10 Mac Ongoing Install Failure - Exit Code 7

Photoshop Elements 10 Mac Ongoing Install Failure - Exit Code 7
I downloaded Photoshop Elements 10 for Mac (not trial, with valid serial #)
Mac OSX 10.7.2, 3.6 GHz Intel Core i5, 16 GB RAM
I know the install package is valid because I installed it on my backup laptop (same Max OSX version) after I was having problems with my primary desktop and it installed fine. I have followed all the instructions on the install package including "restarting my system and installing again," and the install keeps failing with the same message:
Exit Code: 7
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 18 error(s), 3 warning(s)
WARNING: DS013: Payload {298CF0B0-8B47-46DF-B726-8E4BFAD5432E} AdobeHelp 1.0.0.0 is already installed and the session payload {EB3A47AA-B4E2-4857-A69C-92A6E097F24C} AdobeHelp 3.5.0.0 has no upgrade/conflict relationship with it.
WARNING: DS013: Payload {75063C76-E858-455B-9C26-89E55D26F276} AdobeHelp 3.2.0.0 is already installed and the session payload {EB3A47AA-B4E2-4857-A69C-92A6E097F24C} AdobeHelp 3.5.0.0 has no upgrade/conflict relationship with it.
ERROR: DS013: Verifying payload integrity : Failed with code 1
----------- Payload: {60CB5C6D-5B99-45D3-BAB5-E7728182101E} Adobe Photoshop Elements 10 10.0.0.0 -----------
ERROR: DF024: Unable to preserve original file at "/Library/Fonts/BickhamScriptPro-Regular.otf" Error 0(Seq 1519)
ERROR: DW063: Command ARKDeleteFileCommand failed.(Seq 1519)
ERROR: DF023: Unable to delete file "/Applications/Adobe Photoshop Elements 10/Support Files/Adobe Photoshop Elements Editor.app/Contents/Info.plist". Error 0(Seq 2)
ERROR: DW063: Error rolling back command ARKCopyFileCommand(Seq 2)
ERROR: DF001: Unable to get permissions of "/Applications/Adobe Photoshop Elements 10/Support Files/Adobe Photoshop Elements Editor.app/Contents"(Seq 2)
ERROR: DW063: Error rolling back command ARKCreateDirectoryCommand(Seq 2)
ERROR: DF001: Unable to get permissions of "/Applications/Adobe Photoshop Elements 10/Support Files/Adobe Photoshop Elements Editor.app"(Seq 2)
ERROR: DW063: Error rolling back command ARKCreateDirectoryCommand(Seq 2)
ERROR: DF001: Unable to get permissions of "/Applications/Adobe Photoshop Elements 10/Support Files"(Seq 2)
ERROR: DW063: Error rolling back command ARKCreateDirectoryCommand(Seq 2)
ERROR: DF015: Unable to delete symlink "/Applications/Adobe Photoshop Elements 10/Adobe Photoshop Elements 10"(Seq 1)
ERROR: DW063: Error rolling back command ARKCopySymlinkCommand(Seq 1)
ERROR: DF001: Unable to get permissions of "/Applications/Adobe Photoshop Elements 10"(Seq 1)
ERROR: DW063: Error rolling back command ARKCreateDirectoryCommand(Seq 1)
WARNING: DW036: Payload cannot be installed due to dependent operation failure
ERROR: DW050: The following payload errors were found during install:
ERROR: DW050: - Adobe Photoshop Elements 10: Failed due to Language Pack installation failure
ERROR: DW050: - Adobe Photoshop Elements 10_AdobePhotoshopElements10_en_US: Install failed
Suggestions? thanks.

Issue resolved with the help of Adobe Support (Mercer). My problem had been seen in another machine, there were empty folders in the Fonts Folder (Hard Drive>Library>Fonts) that the installer could not reconcile or delete, that was hanging up the Installer.
My fix was to delete the following empty folders from the Fonts Folder:
AdobeMingStd-Light.otf
BickhamScriptPro-Regular.otf
KozMinPro-Regular.otf
MyriadPro-BoldCond.otf
TektonPro-BoldCond.otf
And then re-run the installer (be sure to empty the trash).
My advice would be to first read the installer log and look for names of font folders that could not be resolved, then dump those. Another way would be to dump any empty folders in the Fonts Folder, empty the trash, then re-sun the installer.

Applying 9.1.2 to existing admin install point

I am trying to patch my existing admin install point of Adobe Reader 9.1.1 to 9.1.2 but get this error:
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on yoru computer and that you have the correct upgrade patch.
I get the same error on my PC when I double click the msp file
This is the msi log from when I tried to patch the existing admin install of 9.1.1:
MSI (c) (00:58) [16:18:02:876]: Final Patch Application Order:
MSI (c) (00:58) [16:18:02:876]: Other Patches:
MSI (c) (00:58) [16:18:02:876]: Unknown\Absent: {AC76BA86-7AD7-0000-2550-7A8C40000912} - C:\CustomInstalls\AdobeReader\patches\adobe912.msp
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
d that you have the correct upgrade patch.
C:\CustomInstalls\AdobeReader\acroread.msi
MSI (c) (00:58) [16:18:02:876]: Product: Adobe Reader 9.1.1 - Update '{AC76BA86-7AD7-0000-2550-7A8C40000912}' could not be installed. Error code 1642. Additional information is available in the log file c:\adobe.log.
MSI (c) (00:58) [16:18:02:923]: Product: Adobe Reader 9.1.1 -- Installation failed.
Any help is greatly appreciated.

I don't even know why I continue to use adobe products. Adobe software development is a joke. So are their UIs.
First, this forum crashed my FireFox 3.0.10 browser, twice. The second time, I figured out it was Adobe's fault. Why doesn't Adobe learn to script AJAX properly so it doesn't crash browsers? So here I am in IE8 typing a reply.
All of you guys were beating around the bush in regards to the "solution" to this problem. I have found a way to apply the patch and use an MST generated by the Adobe Customization Wizard. Granted, it would be much better if Adobe would just generate their patches correctly to begin with.
As you all have found out, you cannot create an MST using the ACW (Adobe Customization Wizard) and then use the following command
msiexec /i AcroRead.msi /p AdbeRdrUpd912_all_incr.msp /t
This will cause the aforementioned problem. Below is the proper sequence of events:
Make a backup copy of the 9.1.0 AcroRead.msi (just in case).
Run the following command: msiexec /a AcroRead.msi /p AdbeRdrUpd912_all_incr.msp This command will create an Administrative Install Point (AIP) in the directory you choose. I will place it in a directory called Patched The AcroRead.msi file will be rewritten and will be version 9.1.2 (check the Property table with ORCA and look at the value ProductVersion). In addition, the files that were in Data1.cab will be expanded and patched and are in the Patched folder I specified above. At this point, we no longer need the Data1.cab file. If you know how, you could compress all the files back into a cab and insert them back into the media table, but that is overly complicated and I forget how to do it successfully. In any event, the major benefit would be some space savings. If you had a lot of apps like this, it would be beneficial; but for one, not so much so.
Open AcroRead.msi with ACW. Make any changes you want for your installation. However, the following changes must be made or browser integration will be broken (per an earlier post in this thread):
Go to the Registry item in the left-hand menu.
Under the Destination Computer section, navigate to the following key: HKEY_CLASSES_ROOT\acrobat\DefaultIcon.
Modify the (Default) value to the following: [READER]AcroRd32.exe. NOTE: This only applies if you are installing Adobe Reader. If you are installing Acrobat, this may not apply, but I am not sure. YMMV.
This step was updated 10 July 2009 11:30:00 EST (GMT-05:00). If your are performing application virtualization, you will want to make te following changes to the MSI (via ORCA or ACW). I'm making these changes from ACW. The installer will fail during application sequencing during the installation of the Adobe Updater Manager (AUM). For virtualized applications, this component is unnecessary and should not be installed. Other sites lead you through a lengthy, risky process to eliminate the installation of the AUM. This step will eliminate the installation of AUM with two simple changes to the MSI.
In ACW, select the Direct Editor node from the left hand side.
Select the Feature table.
On the right side, locate the features named AUM and Updater. Note that the Level field for both features are 1. Change the Level field for both fields to be 200. Actually, any number greater than 100 will do, but 200 is a nice round number. Since the installer defaults to INSTALLLEVEL=100 (see the Property table), any feature with a Level value of 100 or less will be installed. Since we have now given these features an install level of 200, these features will not be installed. Generally, this tactic can be used on any component you wish not to have installed (for Adobe Reader and some other applcations with simple installers), such as AIR and Acrobat.com. Those are the only two changes that need to be made to not have AUM installed.
To make sure your users don't encounter an error while running Adobe Reader, make sure, in ACW, to uncheck the box Disable all updates under the Online and Acrobat.com Features section.
Save the package (in ACW, File->Save Package). This modifies the setup.ini file so that it will use the changes you just made (saved by default in AcroRead.mst).
I left my original instructions below, but marked as deleted. Please see step 5 below these deleted instructions. This is a new step. If you are performing application virtualization, you want to make the following changes to the MSI (via ORCA or ACW). I'm making these changes via ACW. The installer will fail during application squencing due to not being able to create to two certain registry keys. This is the easiest way that I can think of to get this to work.
Start your sequencing machine (in my case, a VM).
Install Adobe Reader 9.1.x (do not sequence, simply install).
Once installation completes, open the Registry Editor (assuming Windows Vista; if using WinXP or below, try RegEdt32.exe).
Browse to HKEY_CLASSES_ROOT\Installer\Win32Assemblies\Global
Double click the following entry (make sure you get the right one, there are two similar entries!): Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762", processorArchitecture="x86".
Copy the value of the entry (on Vista, the value is already highlighted,simply right-click and choose Copy. Otherwise, right-click and choose Select All and then right-click again and choose Copy.).
Paste this value into Notepad. Save the file, making sure to select the Unicode encoding type from the Encoding drop-down list. Save it with the name Microsoft.VC80.CRT.txt
Back in the registry editor, double-click the following entry: policy.8.0.Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32-policy",versio n="8.0.50727.762",processorArchitecture="x86".
Copy the value of the entry (on Vista, the value is already highlighted,simply right-click and choose Copy. Otherwise, right-click and choose Select All and then right-click again and choose Copy.).
Paste this value into Notepad. Save the file, making sure to select the Unicode encoding type from the Encoding drop-down list. Save it with the name policy.8.0.Microsoft.VC80.CRT.txt
Close the registry editor.
Reset your VM so it is clean for the sequencing (i.e. revert to a snapshot).
Back in the ACW, at the Registry portion, navigate to HKEY_CLASSES_ROOT.
Right-click HKEY_CLASSES_ROOT and selet New->Key. Name the new key Installer.
Right-click the Installer key and select New->Key again. Name the key Win32Assemblies.
Create a new key in Win32Assemblies called Global.
Select the Global key you just created.
On the right-side of the editor, right-click and choose New->Multi-String Value. Name the new value: Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762", processorArchitecture="x86".
Right-click the new value and select Modify
Open the text file Microsoft.VC80.CRT.txt you created aboe.
Press CTRL+A or Edit->Select All (in Notepad) and then press CTRL+C (or Edit->Copy).
Back in ACW, paste the value from the clipboard and click OK.
Now right-click the editor and choose New->Multi-String Value again. Name it policy.8.0.Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32-policy",versio n="8.0.50727.762",processorArchitecture="x86".
Open the policy.8.0.Microsoft.VC80.CRT.txt file created above.
Copy the file contents as the value of the new entry in the ACW.
Save the package. You should now be ready to install Adobe Reader via Setup.exe for sequencing.
Updated 10 July 2009 12:00:00 EST (GMT-05:00). We have one more step to perform just to clean things up bit. I'm going to create another AIP using the patched MSI and our newly created MST. However, this does not work quite as one would expect.
Run the following command: msiexec /a AcroRead.msi /t <Your_transform.mst>. I created this AIP in a folder called PatchedTransformed.
The above step created another AIP in the PatchedTransformed folder. What's different about this AIP compared to the one made at the beginning of this procedure is that the MSI file was copied to the PatchedTransformed folder as well. However, the MSI is not merged with the changes from the MST as I expected. There are two things you can do:
Modify the setup.ini file and add the following line to the [Product] section: CmdLine=TRANSFORMS="<Your_Transform.mst>", or
Use ORCA. Open your patched MSI in ORCA. Choose Transform->Apply Transform... and select the transform generated by the ACW. Then choose File->Save Transformed As... and give the transformed MSI a new name, e.g. Custom-AdobeReader-9.1.2.msi.
That's it. You now have a fully patched and modified Adobe Reader installer ready for installation or application virtualization.
At this point, you should have an MSI and MST. If you want, you can use ORCA to merge the MST into the MSI. If you're using Setup.exe, you're going to have to change th Setup.ini file.
To test that everything works, you can copy the files to a test directory and perform the following command: msiexec /a <AdobeReader.msi> [/t <Your_transform.mst>] Replace with the name of your MSI file and optionally, pass in your transform (definitely do this if you made a separate MST!). If all goes well, the installation should go well, too. During sequencing, you will still get an MSI installer error (actually, 2), number 1406, about not being able to write to two registry keys. These were the registry keys we added in the steps above. This does not happen on normal installatons.
Please also note that I don't know whether the roaming user profile problem menioned in http://kb2.adobe.com/cps/404/kb404597.html is fixed in version 9.1.2. It was not fixed as of 9.1.0.163. This is all posted AS-IS. YMMV.
UPDATE:
In case you don't know, I will share a bit of enlightenment I had with my procedure above. This specifically relates to application virtualization and sequencing Adobe Reader for MS App-V.
In step 4, I had you install Adobe Reader on a clean machine and obtain some registry information because otherwise, the installation may not be successful for virtualization. These steps are unneccessary. Here's why: you cannot "patch/upgrade" vitualized applications within the application itself. To patch/upgrade a virtual application, you have to use (in the case of MS App-V) the Application Virtualization Sequencing MMC to load the virtualized app, then run the upgrade/patch so that MS App-V can detect the changes and properly update the package. So what does this mean? Two things. First, whenever I use the ACW, under the Online and Acrobat.com Features section I always uncheck <b>Disable all updates</b>. However, checking this does not necessarily mean Adobe Reader does not install the Adobe Update Manager (AUM); in fact, it does install AUM, which is the feature that contains the component that attempts to write those registry entries and therefore, which is causing the error.
Therefore, the solution (and what should be step 4) is to disable the installation of AUM. Now some have posted at various sites how to disable the installation of AUM by deleting a whole bunch of stuff in the MSI. This is not necessary. The steps are outlined in the new step 4 above. This should resolve sequencing issues.
UPDATE 10 July 2009 12:00:00 EST (GMT-05:00) - Pertains to virtualizing Adobe Reader only.
This doesn't work for virtualizing the application. When importing the application into MS App-V Server Management Console, the application version is still 9.1.0.163 even though the splash screen says 9.1.2. I think that my assessment is correct because of two reasons: 1) I still got the MS VC++ Runtime error when using a normal user with a roaming profile which Adobe said the latest 9.1.1 release fixed (and hence 9.1.2) (the AppData folder included) and for which Adobe's solution is a joke; 2) When I installed my "patched" Reader (as a normal install) with AUM and proceeded to go to Help->Check for Updates, the 9.1.2 update appeared in the list of updates (again, even though the splash screen said it was version 9.1.2). Adobe has got to get their patchng correct!!!
For application virtualization, I'm going to recommend that you sequence the 9.1.0 version through to completion. Then, save the sequence and close it. Then re-open the sequence project for upgrade and applythe 9.1.2 patch. Whether you can use an ACW transform on the 9.1.0 installation and then patch, that's debatable. I sure hope so. If not, perhaps there's a way I can fudge it, namely, create an MST via ACW. Then, manually create an MST with the pertinent settings via ORCA and see if that works, instead.
Having said all that, I seriously doubt this works at all even for GPSI deployment. Sorry all. Will post again when I finally get this application to sequence. Hopefully, the same principles will apply to GPSI deployment.
Message was edited by: TTEConline on 10 July 2009 12:00:00 EST (GMT-05:00)

German Admin Install ACROPRO.MSI

Hi,
i have a multilanguage Installation Disc of Acrobat Pro 9.0
Unfortunately only the SETUP.EXE allows me to install in german.
I have to create an admin install of the MSI to integrate the hotfixes to 9.3.2.
If I do so i get an english version. How can I get the german one?
Cheers
Carsten

Hi,
You can install AcroPro in German using the following steps:
1. Create an AIP for Acrobat 9x using the command: msiexec /a <Path of AcroPro.msi> /p <Path of patch_file>
2. Copy the "1031.mst" from the installation disc to the machine
3. Run the installation using the following command:
msiexec /i <path of Acroat 9 msi present inside the AIP> TRANSFORMS="<path of .mst file>"
Thanks,
Vinod

ZCM Reporting install failure: Wrong OS

Hi, I have downloaded the ZCM_Reporting_10.1.0.iso and would install the server on my ZCM server what is installed on a SLES 10.2 x64 with ZCM 10.1.1 x64. But I got the install message: Not supported OS. Is it true ?

I was also "bitten" by this same problem...ZCM 10.1.1 on a 64-bit SLES 10 SP2 server and when I tried to install the ZCM Reporting Server I got the same message.
It was only when I reviewed the fine print, and I do mean fine print, in the software requirements did I realize that NO 64-bit OS was going to be suitable for the ZCM Reporting Server.
Usually you would not expect to run into trouble installing a 32-bit application on a 64-bit OS but they do crop up occasionally but I was not too concerned in the case of ZCM 10.1 on a 64-bit OS about whether or not the ZCM Reporting Server would install OK. Hey, isn't this stuff supposed to work together? What happened to making IT work as one?
This does need to get "fixed" by Novell and BO because it is a problem that should not exist in the ZCM 10 world to begin with. Shame on them for being so lazy about it.
Novell should have pointed this out IN LARGE TYPE THAT THE ZCM 10.1 REPORTING SERVER CANNOT BE INSTALLED ON ANY 64-BIT OS. Instead they kind of tucked it away in the fine print where it waited to bite us.
Tim Wessels
Originally Posted by Craig Wilson
At this point in time, BOE is only supported on a 32-Bit OS.
Novell is working with Business Objects to get support for 64-Bit Platforms.
Craig Wilson - MCNE, MCSE, CCNA
Novell Support Forums Volunteer Sysop
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
"deban0" <[email protected]> wrote in message
news:[email protected]...
>
> Hi, I have downloaded the ZCM_Reporting_10.1.0.iso and would install the
> server on my ZCM server what is installed on a SLES 10.2 x64 with ZCM
> 10.1.1 x64. But I got the install message: Not supported OS. Is it true
> ?
>
>
> --
> deban0
> ------------------------------------------------------------------------
> deban0's Profile: NOVELL FORUMS - View Profile: deban0
> View this thread: ZCM Reporting install failure: Wrong OS - NOVELL FORUMS
>

Applying Reader 11.0.5 update to admin install

The 11.0.5 patch for adobe reader won't install on my admin install. I've been able to update 11.0.xx up to 11.0.4 by applying a the patch from a command line.

The answer is that I somehow got into the Acrobat updates rather than the Reader updates. The Acrobat update was not able to update the Reader install - duh! on me.
It will work with my script to install updates to the Reader MSI file. All is well in the world when you pay attention!
Solved.

Premiere Elements 10 install failure on Mac osx 10

I have a copy of Adobe Premiere Elements 10, the five disk set, and keep having the same failure trying to install it on my Mac. I have gone through all the product requirements and made sure that my computer satisfies them, but I still find an install failure at 51%, Exit code 7, each time.
What can I do?

I had the exact same problem installing Premiere Elements 10 on a Mac from DVD. Exit code 7 when it reached 51% installation. I followed the link to "updated installation instructions" provided in this forum by Adobe Employee Jeff Wright. It works.
The instructions in a nutshell: DON'T USE THE DVD. Instead, download a trial version. When you install use the serial number provided with your DVD.
I find this to be extremely aggravating. I spent a lot of time trying using the Adobe Support Advisor application trying to sort through the error codes. Then I spent time trying to get through to Adobe Support (never did get through). Finally I tried the forum and found the answer here.
I find Adobe to be grossly inadequate in two ways. First, they put out a product that just wasn't tested. The DVD won't install on a Mac. It is as if they did not test their product. Second, their support is awful. This is a known problem with a known solution. When the fault occurs, the Adobe Support Advisor application should point the customer to the "updated installation instructions". Instead it points to faults that are unrelated so the customer is led on a wild goose chase.
I hope the product will be better than my experience so far.

Photoshop CS5 Install failure, but on just one instance of SL (the one I

HI, I know this is a strange place to post this, but Adobe Support suggests talking to Apple, as I have an install failure of Photoshop CS5, the install app won't even initialize, and it's just on one instance of SL. I can install fine on other machines, and other bootable drives, but not on the one inside an imac (late 2008 vintage). Baffling, as the problem must be tied to this one instance...my production one. I tried other users on the machine, but no luck...same problem. I checked permissions, ran Disk Warrior, all of that, still no luck. Anyone have any other suggestions besides using Gimp:) thx,
coocoo

I can see what's going on with the installer... first it's supposed to create a temp application dir in the user account, Adobe/OOBE/blabla... then kick off the activation and then the installer. Before it get's to the activation part, it blows and deletes the dir it started. As I successfully can install on another boot drive, I tried to cobble together the installation that way, by just copying files over, and got there - pretty much. I just can't activate with my serial number as I am supposed to be able to do...probably intentionally made so - but PS is running in trial mode on my production machine, and full mode on a test machine - ha! If I could just reverse the situation I would be golden. Anyway, I have another call in to Adobe...

RE: Install Failure

We have successfully installed the Forte 2.F.2.0 version on the NT
server 4.0. We have less number of services runnning on the NT server
and the NT server should be BDC instead of PDC for the better
performance. The installation on the NT server 4.0 has few other bugs
like, in the process of installation it will through a error message
saying that 'No program manager found' and it won't configure the
program icons properly.
Thanks
Raju
(630)-271-3357
[email protected]
-----Original Message-----
From: Todd Foster [SMTP:[email protected]]
Sent: Monday, June 02, 1997 11:26 AM
To: [email protected]
Subject: Install Failure
Has anyone else had a problem with installations?
I have an NT4 Server (service pack2).
I launch the setup.exe and the splash screen comes up,
a temp directory is decompressed, and then it's all over.
No Forte.
I've successfully installed on other NT station machines,
it seems InstallShield is getting some sort of 'red light'.
Any feedback would be greatly appreciated.
Thanks

Hi Matthew,
firrst of all: WELCOME TO THE DISCUSSIONS!
unfortunately you do not give us any information about your system. Please fill in your system's details in "My public profile" in the right sidebar of this page. We need to know as much as possible about your system in order to help (especially: exact type of Mac you use, current system version, RAM, 3rd-party cards)!
Before you start please confirm you have the retail full install DVD! You cannot use hardware specific disks that shipped with another computer.
Repair permissions cannot do it's duty without a bootable system installed. Therefore an empty partition is always grayed out.
Did you upgrade your firmware before you reformated: Mac OS X: Chart of Available Firmware Updates?
Make sure you format your disk as "Apple Extended (Journalled)".

INF Install failure for Windows 7

While tring to do Disc Cleanup I continue to get this error:
Error unregistering the OCS C:Windows\system32\20-20Technologies\3D Viewer\v5.0.94.0\2020Player_WEB_5_0_94_o.dllINF Install failure. Reason: Access is denied
I am using Windows 7 32 bit system. I cannot find anyone else with Windows 7 having this issue. Below are some of the thinkgs I have tried, but did not work. Any suggestions would be appreciated.
After click on start, run, open, msiexec/unreg I get this message (Windows cannot find 'msiexec/unreg'. )
I typed services.msc in the run box to see if Windows Installer is disabled. (If it is set it to manual). Mine is set for manual.
I tried downloading and installing this: support.microsoft.com/kb94228
Downloaded Windows Installer 4.5: go.microsoft.com/fwlink/?LinkId=120486
Got error: The requested operation requires elevation
I am at a complete lose to get this taken care of. Please help!!!

I was surfing the 'inter-web' on this issue [grin]
On the Major Geeks forum it said that COMBO Fix was the solution..
[quote]
Step
3:
Now we
need to use ComboFix to remove a bunch of malware files.
Make sure that combofix.exe that you downloaded while doing the READ &
RUN ME is on your Desktop but Do not run it!
If it is not on your Desktop, the below will not work.
Open Notepad and copy/paste the text in the below quote box into it:
Quote:
KILLALL::
DirLook::
C:\WINDOWS\system32\20-20
Technologies
FileLook::
C:\WINDOWS\inf\2020Player.PNF
Folder::
c:\windows\system32\512686
[Quote]
hth
pvm
PVM

Admin install of reader 9.4.1 doesn't update authplay.dll

I made an admin install of adobe reader 9.4.1
I went to ftp://ftp.adobe.com/pub/adobe/reader/win/9.x/ and downloaded 9.4.0 msi and the 9.4.1 patch
I opened a cmd prompt as an admin and ran msiexec /a 9.4.0.msi /p 9.4.1.msp
that gives me an .msi that installs 9.4.1, but one of the files doesn't change.
C:\Program Files\Adobe\Reader 9.0\Reader\authplay.dll stays as the older version
When I run 9.4.0.msi and then patch the install later the file changes to the correct version.
I have tried to package this on vista 32 and 64 and win 7 32 and 64.
any suggestions?

I made an admin install of adobe reader 9.4.1
I went to ftp://ftp.adobe.com/pub/adobe/reader/win/9.x/ and downloaded 9.4.0 msi and the 9.4.1 patch
I opened a cmd prompt as an admin and ran msiexec /a 9.4.0.msi /p 9.4.1.msp
that gives me an .msi that installs 9.4.1, but one of the files doesn't change.
C:\Program Files\Adobe\Reader 9.0\Reader\authplay.dll stays as the older version
When I run 9.4.0.msi and then patch the install later the file changes to the correct version.
I have tried to package this on vista 32 and 64 and win 7 32 and 64.
any suggestions?

Admin install failure.

Similar Messages

Maybe you are looking for