Wlst deploy via ant fails with NameNotFoundException

All,
I am trying to setup a deployment of a simple ear application to Weblogic using wlst via ant.
The deployment keeps failing with a NameNotFoundException.
####<Sep 20, 2012 4:41:35 PM CDT> <Error> <Deployer> <osb2-dev-1> <WLS_APPMGD1> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1348177295661> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1348177287862' for task '131'. Error is: 'javax.naming.NameNotFoundException: Unable to resolve 'ejb.xxxxServiceSLSBLocalHome'. Resolved 'ejb'; remaining name 'xxxxServiceSLSBLocalHome''
javax.naming.NameNotFoundException: Unable to resolve 'ejb.xxxxServiceSLSBLocalHome'. Resolved 'ejb'; remaining name 'xxxxServiceSLSBLocalHome'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
Note that I struck out the actual service name with xxxx. Here is output from ant:
wl-deploy-only:
[wldeploy] weblogic.Deployer -verbose -upload -noexit -name xxxx -source artifacts\xxxx.ear -targets APPMGD_Cluster -adminurl t3://soaadmin-dev-1:7003 -user weblogic -password ******** -deploy -appversion anthill-2240
[wldeploy] weblogic.Deployer invoked with options: -verbose -upload -noexit -name xxxx -source artifacts\xxxx.ear -targets APPMGD_Cluster -adminurl t3://soaadmin-dev-1:7003 -user weblogic -deploy -appversion anthill-2240
[wldeploy] <Sep 20, 2012 4:01:34 PM CDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, xxxx [archive: artifacts\xxxx.ear], to APPMGD_Cluster .>
[wldeploy] Task 129 initiated: [Deployer:149026]deploy application xxxx [Version=anthill-2240] on APPMGD_Cluster.
[wldeploy] Task 129 failed: [Deployer:149026]deploy application xxxx [Version=anthill-2240] on APPMGD_Cluster.
[wldeploy] Target state: deploy failed on Cluster APPMGD_Cluster
[wldeploy] java.lang.Exception: [DeploymentService:290069]Commit failed message received for id: '1,348,174,902,597' . But exception details cannot be transported. Please look at target server log file for more details.
[wldeploy]
[wldeploy] java.lang.Exception: [DeploymentService:290069]Commit failed message received for id: '1,348,174,902,597' . But exception details cannot be transported. Please look at target server log file for more details.
[wldeploy]
[wldeploy]
[wldeploy] Target Assignments:
[wldeploy] + xxxx APPMGD_Cluster
BUILD FAILED
weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 129 failed: [Deployer:149026]deploy application xxxx [Version=anthill-2240] on APPMGD_Cluster.
Target state: deploy failed on Cluster APPMGD_Cluster
java.lang.Exception: [DeploymentService:290069]Commit failed message received for id: '1,348,174,902,597' . But exception details cannot be transported. Please look at target server log file for more details.
java.lang.Exception: [DeploymentService:290069]Commit failed message received for id: '1,348,174,902,597' . But exception details cannot be transported. Please look at target server log file for more details.
at weblogic.Deployer.run(Deployer.java:72)
at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:420)
at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1307)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1191)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:218)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 129 failed: [Deployer:149026]deploy application xxxx [Version=anthill-2240] on APPMGD_Cluster.
Target state: deploy failed on Cluster APPMGD_Cluster
java.lang.Exception: [DeploymentService:290069]Commit failed message received for id: '1,348,174,902,597' . But exception details cannot be transported. Please look at target server log file for more details.
java.lang.Exception: [DeploymentService:290069]Commit failed message received for id: '1,348,174,902,597' . But exception details cannot be transported. Please look at target server log file for more details.
at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:542)
at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.Deployer.run(Deployer.java:70)
at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
... 2 more
Total time: 25 seconds
I tried redeploy instead of undeploy, but is still fails. Is there anything I am missing?
Thanks.
Edited by: 960582 on Sep 21, 2012 7:18 AM

Kal, that parameter did not solve the problem. I added it under JAVA_OPTIONS in:
${oracle.home}\user_projects\domains\osb_domain\bin\startWebLogic.cmd
I am still getting an exception. The new deployment only gets picked up after the managed servers are bounced. Any idea what could be going on?

Similar Messages

SSM BIOS Deployment Ends Sometimes Fails With Error 0x642

Good morning,
I am currently trying to use the SSM software to deploy a BIOS update to my 300 HP Folio 9470m and am running into an intermittent problem. The problem I am seeing is that sometimes the deployment will fail with a 0x642 dependency error. I have not been able to determine a reason for the failure, and the same package deployment will work on a different laptop.
The only consistency I have been able to reproduce is that if the install fails the first time, it will fail every other time on that particular laptop.
I have included log files from a successful and unsuccessful deployment. I have confirmed that it does not appear to be an issue with using the incorrect BIOS password, because I can set the password to the one specified when I created the deployment database and it will still sometimes fail.
Let me know if I can provide any additional information. Any help would be greatly appreciated. I really would like to be able to use this software as it would make my job managing these laptops a whole lot easier.
Thanks,
Raymond Northcott
Log file from successful deployment: https://drive.google.com/file/d/0By0fDHxxVEc6SHhZb0VDRVRMRWc/edit?usp=sharing
Log file from unsuccessful deployment: https://drive.google.com/file/d/0By0fDHxxVEc6NXdEOTV6bnJ3TGc/edit?usp=sharing
This question was solved.
View Solution.

I know it is late but I have only seen this post today.
The team responsible for SSM does not monitor this forum.
According to the logs you have posted, you are using SSM version 2.14 A8.
Your version pre-dates the design and production of the 9470 folio by approximately 3 years.
There have been many changes to SSM since 2.14.
Please update to the latest version.
You can ask questions about SSM and other client management tools in the HP PC Client Management Community forum.
      HP PC Client Management Community forum
The pc client management discussion board is focused on the following topics but is not exclusive to them:
HP Client Catalog
                The HP Client Catalog for Microsoft System Center Configuration Manager products is used in the deployment of HP software updates (SoftPaqs) to HP commercial PCs in a Microsoft System Center environment.
HP Driver Packs
                HP Driver Packs contain the necessary Microsoft Windows drivers required
to support HP hardware platform(s) listed in each of the driver pack’s release notes.
HP Client Integration Kit
The HP Client Integration Kit ( HP CIK ) is a plug-in for Microsoft System Center Configuration Manager.
HP BIOS Configuration Utility
The HP BIOS Configuration Utility ( HP BCU ) provides the ability to manage BIOS settings on HP supported desktop, workstation and notebook computers.
HP System Software Manager
The HP System Software Manager ( HP SSM ) is a utility for updating BIOS and device drivers on your networked PCs.
These tools and more can be found at www.hp.com/go/clientmanagement
Look in the Resources menu for items such as the HP CMS Download Library, HP CMS Whitepapers or HP Driver Packs.
The HP CMS Download Library contains the latest release version of SSM.
      HP CMS Download Library
If you have questions about SSM or any of the other utilities listed, this is the best forum to find answers.
thanks,
Richard
I work for HP but am not a company spokesperson. Participation in the community forums is voluntary.

Thinkpad T440s BIOS update via PXE fails with "invalid system disk"

Hi,
I'm trying to boot via PXE to the BIOS 2.24 update ISO image because the T440s comes without a DVD drive. The Thinkpads are running RHEL 6.5 workstation installed. I'm using syslinux 6.02 and the following menu entry:
label lenovo_t440s
    menu label Lenovo Thinkpad T440s BIOS 2.24 Update
    kernel memdisk
    append initrd=lenovo/t440s/gjuj11us.iso iso
The ISO gets loaded via TFTP and seems to boot, but then an error message appears:
Loading boot sector... booting...
Lenovo Group Limited
Invalid system disk
Replace the disk, and then press any key.
The Thinkpads come with the following SSD drive: SAMSUNG MZ7TD256HAFV-000L9.
Anyone had luck with updating BIOS via PXE boot?
We also have Thinkpads T430s. There the BIOS update ISO image loads, displays the menu, but when one presses "update firmware" then it freezes.
Regards,
Bernd

Same behaviour when I try without PXE and load memdisk and ISO file directly via GRUB using this entry in /boot/grub/grub.conf:
title ThinkPad BIOS Update
root (hd0,1)
kernel /memdisk iso
initrd /gjuj11us.iso

Problems deploying ear file created with ant build script

Hi All,
I'm using Jdeveloper 11G and Weblogic 10.3. When I build my application and run it within Jdeveloper, it works fine. However, we have a requirement to run ANT build script and create a deployable .ear file that can be manually deployed to any Weblogic Server.
I created my ant build script and it compiles/builds fine - the .ear file looks good. However, when I attempt to deploy it, it fails with
javax.faces.webapp.FacesServlet for servlet Faces Servlet could not be loaded because the requested class was not found in the classpath .
java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet.
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
     Truncated. see log file for complete stacktrace
>
<Nov 2, 2011 2:43:43 PM MDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1320266599219' for task '3'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "Faces Servlet" failed to preload on startup in Web application: "###"
I am not sure how to tell weblogic where to find the classes needed. I have a pretty huge classpath used when compiling - should I be putting the classpath in the manifest (?) - I don't think I should need to include the .jar files manually in the .ear file - since all the libraries should already be available in weblogic - or is that a misconception?
Please help!!

I answered my own question -
I had to manually add the following to the WEB-INF/lib to get the error to go away:
${ORACLE_HOME}/modules/javax.jsf_1.1.0.0_1-2.jar and
${ORACLE_HOME}/oracle_common/modules/oracle.jsf_1.2.9/glassfish.jsf_1.0.0.0_1-2-15.jar and
${ORACLE_HOME}/oracle_common/modules/oracle.jsf_1.2.9/glassfish.jstl_1.2.0.1.jar
that solved my problem. However, I think it'd be great if I could somehow just specify (in the weblogic-application.xml maybe?) that my application is using the above modules without having to copy the jar files into my WEB-INF/lib - any suggestions?
Thanks

SharePoint 2007 Content deployment Error: 'A folder with the name already exists.

Hi, In SharePoint 2007 one Content deployment job is failed with below error:
Content deployment job 'Remote import job for job with sourceID = some id' failed.The exception thrown was 'Microsoft.SharePoint.SPException' : 'A folder with the name PublishingImages/AEI-2014/Blue already exists.'
From last 3 days I am getting this error and previously this Job was running without any Error.
In Import Log file getting message: "FatalError: A folder with the name PublishingImages/sg-2015/yellow already exists."
Please tell me how to resolve the issue.

Hello,
It seems same folder exist in destination server that's why job is failing. You need to check destination server and remove the same name/GUID from site then try again.
See this technet for more info: (see "Conflicting content on source and destination" section)
http://technet.microsoft.com/en-us/library/dd795107%28v=office.12%29.aspx
Hemendra:Yesterday is just a memory,Tomorrow we may never see<br/> Please remember to mark the replies as answers if they help and unmark them if they provide no help

IE11 installation fails with error code 4007 (USER_ERROR_MISSING_REQUIRED_PREREQUISITE)

Hello there
I'm having troubles with the installation of IE11 on Win7 over software deployment: Some clients fail with the error code 4007:
USER_ERROR_MISSING_REQUIRED_PREREQUISITE
All prerequired updates for IE11 (http://support.microsoft.com/kb/2847882/en)
are approved for installation:
2729094
2731771
2533623
2670838
2786081
2834140
However, KB2731771 will not install on the clients with the status: Not applicable. I think, this might cause the problem and I'm wondering, why this update will not install.
Thank you for your ideas and advise.
Cheers,
Simon

Hi,
For Windows update 2731771, please make sure that you've approved the right version for your clients, x86 package or x64 package.
The error indicates that the failed IE installation is caused by the failed prerequisite, so as
Alex_zz mentioned, we can refer to the ie 11 main log to find more detailed information, you can also locate to
%windir%\logs\cbs
%windir%\Windowsupdate.log
to find the detailed information of the failed update.
Yolanda Zhu
TechNet Community Support

SCCM 2012 - Project 2010 Standard deployment failed with error 1603

Hi everyone,
I’m in the progress to roll out a software deployment via SCCM 2012, it’s to remove the current Project 2010 Professional we installed and reinstall the Standard version. We got a task sequence for the job, which is Reboot>Un-install Project 2010 Pro>Reboot>Install
Project 2010 Std.
The Un-installation process uses this command: setup.exe /uninstall PrjPro /config "PrjPro.WW\uninstall.xml"
The Installation process uses this command: setup.exe /adminfile project_silent_install.MSP
But the deployment result is quite random, some of the PCs would succeed without any issue, some of them with fail at the installation process with 1708/1603 error. As far as I know we use standard Win 7 64bits SOE across the environment, so everyone should
have same system baseline.
I reviewed some of the failed Project 2010 Standard installation logs as it shows the following:
Executing chained package: PrjStdWW
05/09/2014 20:16:14 Installing chained package: PrjStdWW
PERF: TickCount=530512 Name=Verify MSI local install source Description=Begin function
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
LIS: wait for package "{90140000-003A-0000-0000-0000000FF1CE}" to complete caching
LIS: package "{90140000-003A-0000-0000-0000000FF1CE}" caching completed
PERF: TickCount=530528 Name=Completed verify local install source Description=End function
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Use Shell UI transform : LIS\{90140000-0115-0409-0000-0000000FF1CE}\ShellUI.MST
Current transform is at path: LIS\{90140000-0115-0409-0000-0000000FF1CE}\ShellUI.MST
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
Using transform at path: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\ShellUI.MST
Catalyst Package Install...
Package: PrjStdWW
File: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi
Command Line: PATCH="\\SCCM2012\SMSPKGE$\PC100139\project_silent_install.MSP" ADDLOCAL=C.35347883.0E64.45B4.88A0.1881DE05E259,OSpp_Core,Project_PIA,SetupExeArpEntry,Office10Fix1,ProductFiles,InternationalSupportFiles_JPN,AceFiles,IMNFiles,OfficeIntlRDC,AceOdbc,OArt_DocTheme,OSetupController,WISPFiles,TCDRegistration,SetLanguageFiles,TCWorks7Files,ClviewFiles,VBAFiles,OfficeAppSupport,TextConverters,ProductNonBootFiles,dummy_Office_PIA,CAGOffice10,VSCommonPIAHidden,WebDiscussFiles,CAGCat10,CAGCat10Clips,MsoInstalledPackagesScoped,WxpFiles,SetupControllerFiles,Forms_PIA,dummy_MSCOMCTL_PIA,AlwaysInstalled,Gimme_OnDemandData,AceRepl,OISFiles,OfficeOLESupport,OfficeMSProof6,CAGFiles,InternationalSupportFiles_ArialUni,OSpp,Ace_PIA,GraphicsFiltersFile,WebDriveFiles,PROJECTFiles,ProductFiles_B2TR,SetupXmlFiles,OfficePostBoot,DocumentImagingUtils,VSTOCLR35,CAGCategoryFiles,ProjectCommon,VSTO,ProofingParent,MsoCommonShellHandler,OfficeDigitalSFiles,CARegistryFeature,OfficeCoreRDC,SetupExeAddRegistry,NonC2R_ProductFiles,MSSOAP3,TranslationCore,CAGOffice10Clips REMOVE=WISPHidden ARPENTRY_NOMODIFY="#0" ARPENTRY_MODIFYPATH="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe"" /modify PRJSTD /dll OSETUP.DLL" INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" SLD_OEMPIDKEY="0" ARPENTRY_NOELEVATEONMODIFY="#0" SETUP_REBOOT="never" COMPANYNAME=" " ARPENTRY_SKUCOMPONENTS="[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Proofing.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Project.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office64.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\PRJSTD\setup.xml[~]" ARPENTRY_HELPLINK="" ARPENTRY_DISPLAYICON="C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\OSETUP.DLL,1" ARPENTRY_DISPLAYNAME="Microsoft Project Standard 2010" ACCEPTEDEULA="1" ARPENTRY_DISPLAYVERSION="14.0.4763.1000" BRANDING_XML="C:\Windows\TEMP\Setup00001048\BRANDING.XML" SLD_SUPPORTSBYPASS="0" SLD_ACID="5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE" SLD_TRIALTYPE="0" ARPENTRY_PACKAGEREFS="[~]OfficeMUISet.en-us[~]OfficeMUI.en-us[~]Proofing.en-us[~]Proof.en-us[~]Proof.es-es[~]Office64MUISet.en-us[~]PrjStdWW[~]Office64WW[~]Office64MUI.en-us[~]ProjectMUI.en-us[~]Proof.fr-fr[~]" SLD_DPID="#xF804000004000000380032003500300033002D00300030003000390038002D003000300031002D003000300030003000310030002D00300033002D0031003000330033002D0037003600300031002E0030003000300030002D0031003200390032003000310034000000000000000000000000000000000000000000000000000000000000000000350064006300370062006600360031002D0035006500630039002D0034003900390036002D0039006300630062002D00640066003800300036006100320064003000650066006500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500072006F006A0065006300740053007400640056004C00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000A09E4657B64703B2F32E339838F004006FE4EEC0394DE6AB2D77DCABCBC8F1C3B8B617EF54ACB52805F38EE560D0B738230977F4AB92430B37CBF02B49DB7636DCF15CE7E175CCF354E009C7A02432315800310036002D0030003800300035003100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000056006F006C0075006D0065003A00470056004C004B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006C0074004B004D00530000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" REMOVESAMEVERSION="" SLD_LICENSETYPE="6" SETUPEXEINSTALLUICULTURE="en-US" ARPENTRY_SHELLUITRANSFORMLANGUAGE="en-US" USERNAME=" " ARPENTRY_CONTACT="" ARPENTRY_HELPTELEPHONE="" ARPENTRY_PRODUCTCODES="[~]{90140000-00B4-0409-0000-0000000FF1CE}[~]{90140000-002C-0409-0000-0000000FF1CE}[~]{90140000-003A-0000-0000-0000000FF1CE}[~]{90140000-002A-0000-1000-0000000FF1CE}[~]{90140000-001F-0C0A-0000-0000000FF1CE}[~]{90140000-001F-0409-0000-0000000FF1CE}[~]{90140000-001F-040C-0000-0000000FF1CE}[~]{90140000-0115-0409-0000-0000000FF1CE}[~]{90140000-006E-0409-0000-0000000FF1CE}[~]{90140000-002A-0409-1000-0000000FF1CE}[~]{90140000-0116-0409-1000-0000000FF1CE}[~]" ARPENTRY_INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" SETUPEXE_DOARPWRITE="1" ACIDS="11B39439-6B93-4642-9570-F2EB81BE2238;5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE;B6E9FAE1-1A0E-4C61-99D0-4AF068915378" ARPENTRY_SPPSKUID="[~]5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE[~]" ARPENTRY_NOREMOVE="#0" SLD_PKU="0" SLD_PID="82503-001-0000106-49615" LICTYPE="ltKMS" ARPENTRY_UNINSTALLSTRING="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe"" /uninstall PRJSTD /dll OSETUP.DLL" ARPENTRY_NOREPAIR="#1" ARPENTRY_URLUPDATEINFO="" ARPENTRY_URLINFOABOUT="" REMOVEPREVIOUS="" ARPENTRY_CACHELOCATION="C:\MSOCache\All Users" REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\" ARPSYSTEMCOMPONENT=1 TRANSFORMS="C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\ShellUI.MST" ALLUSERS="1"
PERF: TickCount=530543 Name=MsiPackage::Install Description=Calling OMsiInstaller::InstallProduct for package file "C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Error: Failed to install product: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi ErrorCode: 1603(0x643).
Log level changed from: Standard to: Verbose
Rolling back chain
05/09/2014 20:18:47 Rolling back package: PrjStdWW
There appears to be no rollback work to do for package: PrjStdWW path: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi
05/09/2014 20:18:47 Rolling back package: Office64WW
Package Office64WW was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64WW
File: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\Office64WW.msi
Command Line: ADDLOCAL=AcePiaReg64,VSTO64,WordXmlEditVerb64,ExcelXmlEditVerb64,GrooveShellIntegration64,Project64Files,OSpp64_Core,ExcelPiaReg64,GraphPiaReg64,FormsPiaReg64,SmartTagPiaReg64,PPTXmlEditVerb64,MsoInstalledPackagesScoped,OfficeExample64bitFilesA,WAC_XmlEditVerb64SPD,SetupXmlFiles,WordPiaReg64,Outlook64Files,AlwaysInstalled64,VBEPiaReg64,VisioPiaReg64,Outlook64SearchShellReg,OneNote64Files,SetupControllerFiles,ProjectPiaReg64,SearchFilters64Files,OutlookPiaReg64,Gimme_OnDemandData,Visio64ShapeSearch,WAC_PIARegSPD64,ProductNonBootFiles64,XDocsPiaReg64,PublisherPiaReg64,OneNotePIAReg64,ProductFiles64,OfficeExample64bitFilesB,OfficePiaReg64,Visio64Files,TCDRegistration64,OSpp64,XDOCSFiles64,XDocsXmlEditVerb64,MsoCommonShellHandler64bit,AccessPiaReg64,PowerPointPiaReg64 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64WW ProductCode:{90140000-002A-0000-1000-0000000FF1CE}
05/09/2014 20:18:56 Rolling back package: ProjectMUI.en-us
Package ProjectMUI.en-us was installed in the chain... uninstalling as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Install Rollback (uninstall)...
Package: ProjectMUI.en-us
Product Code: {90140000-00B4-0409-0000-0000000FF1CE}
Command Line: REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back install of package: ProjectMUI.en-us path:C:\MSOCache\All Users\{90140000-00B4-0409-0000-0000000FF1CE}-C\ProjectMUI.msi
05/09/2014 20:19:00 Rolling back package: Proofing.en-us
Package Proofing.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proofing.en-us
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proofing.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proofing.en-us ProductCode:{90140000-002C-0409-0000-0000000FF1CE}
05/09/2014 20:19:04 Rolling back package: Proof.en-us
Package Proof.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.en-us
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.en\Proof.msi
Command Line: ADDLOCAL=FindAllWordFormsFiles_1033,Gimme_OnDemandData,SpellingAndGrammarFiles_1033,ThesaurusFiles_1033,MsoInstalledPackagesScopedIntl_1033,HyphenationFiles_1033,OCR_1033,SetupControllerFiles,SetupXmlFiles REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.en-us ProductCode:{90140000-001F-0409-0000-0000000FF1CE}
05/09/2014 20:19:05 Rolling back package: Proof.fr-fr
Package Proof.fr-fr was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.fr-fr
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.fr\Proof.msi
Command Line: ADDLOCAL=MsoInstalledPackagesScopedIntl_1036,Gimme_OnDemandData,SpellingAndGrammarFiles_1036,SetupControllerFiles,FindAllWordFormsFiles_1036,TranslationFiles_1036,ThesaurusFiles_1036,HyphenationFiles_1036,SetupXmlFiles,OCR_1036 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.fr-fr ProductCode:{90140000-001F-040C-0000-0000000FF1CE}
05/09/2014 20:19:11 Rolling back package: Proof.es-es
Package Proof.es-es was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.es-es
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.es\Proof.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SpellingAndGrammarFiles_3082,OCR_3082,FindAllWordFormsFiles_3082,HyphenationFiles_3082,ThesaurusFiles_3082,MsoInstalledPackagesScopedIntl_3082,SetupControllerFiles,SetupXmlFiles,TranslationFiles_3082 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.es-es ProductCode:{90140000-001F-0C0A-0000-0000000FF1CE}
05/09/2014 20:19:12 Rolling back package: Office64MUISet.en-us
Package Office64MUISet.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64MUISet.en-us
File: C:\MSOCache\All Users\{90140000-0116-0409-1000-0000000FF1CE}-C\Office64MUISet.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64MUISet.en-us ProductCode:{90140000-0116-0409-1000-0000000FF1CE}
05/09/2014 20:19:19 Rolling back package: Office64MUI.en-us
Package Office64MUI.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64MUI.en-us
File: C:\MSOCache\All Users\{90140000-0116-0409-1000-0000000FF1CE}-C\Office64MUI.msi
Command Line: ADDLOCAL=OfficeExample64bitFilesBIntl_1033,OfficeExample64bitFilesAIntl_1033,Gimme_OnDemandData,Outlook64SearchShellRegIntl_1033,ProductFilesIntl64_1033,MsoInstalledPackagesScopedIntl_1033,OneNoteToLinkedNotesIEAddin64Intl_1033,GrooveFiles64Intl_1033,SetupControllerFiles,SetupXmlFiles REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64MUI.en-us ProductCode:{90140000-002A-0409-1000-0000000FF1CE}
05/09/2014 20:19:20 Rolling back package: OfficeMUISet.en-us
Package OfficeMUISet.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: OfficeMUISet.en-us
File: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\OfficeMUISet.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: OfficeMUISet.en-us ProductCode:{90140000-0115-0409-0000-0000000FF1CE}
05/09/2014 20:19:20 Rolling back package: OfficeMUI.en-us
Package OfficeMUI.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: OfficeMUI.en-us
File: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\OfficeMUI.msi
Command Line: ADDLOCAL=MetricConverterIntl_1033,AlwaysInstalledIntl_1033,MSTagPluginStockFilesIntl_1033,WebDiscussFilesIntl_1033,GraphicsFiltersPNGFilesIntl_1033,EquationEditorFilesIntl_1033,GraphicsFiltersEPSFilesIntl_1033,MSTagPluginNamesFilesIntl_1033,TCWP5FilesIntl_1033,CAGOffice10Intl_1033,OISFilesIntl_1033,WxpFilesIntl_1033,XDOCSEditorFilesIntl_1033,CAGFilesIntl_1033,WISPHiddenIntl_1033,CAGCat10Intl_1033,SetLanguageFilesIntl_1033,OSetupControllerIntl_1033,MsoInstalledPackagesScopedIntl_1033,TCRecoverFilesIntl_1033,SetupControllerFiles,ClviewFilesIntl_1033,GraphHelpFilesIntl_1033,ProductNonBootFilesIntl_1033,MSTagPluginPlacesFiles_1033,VisioPreviewerIntl_1033,ProductFilesIntl_1033,AceReplIntl_1033,GraphicsFiltersCGMFilesIntl_1033,GraphicsFiltersWPGFilesIntl_1033,Gimme_OnDemandData,TCWP6FilesIntl_1033,GraphicsFiltersGIFFilesIntl_1033,GRAPHFilesIntl_1033,MSTagPluginDateFilesIntl_1033,WebDriveFilesIntl_1033,LOBiFilesIntl_1033,LISTFilesIntl_1033,UICaptionsCompanionIntl_1033,SetupXmlFiles,AceFilesIntl_1033,TOOLSFilesIntl_1033,MSSOAP3Intl_1033,VBAHelpFilesIntl_1033,GraphicsFiltersPICTFilesIntl_1033,OfficeDigitalSFilesIntl_1033,VBAFilesIntl_1033,GraphicsFiltersJPEGFilesIntl_1033,QueryFilesIntl_1033,SetLanguageHelpFilesIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: OfficeMUI.en-us ProductCode:{90140000-006E-0409-0000-0000000FF1CE}
Error attaching to OSE, error 0x00000000
Stopping running ose
LIS: start uncaching for download "{90140000-002C-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-002C-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-003A-0000-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-003A-0000-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-00B4-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-00B4-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-0115-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-0115-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-0116-0409-1000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-0116-0409-1000-0000000FF1CE}-C"
Error attaching to OSE, error 0x00000000
Stopping running ose
SystemRestore : Attempting to cancelling System-Restore-Point for Product [Microsoft Project Standard 2010] (with RestorePointType [0, Installed]).
SystemRestore : Successfully cancelled System-Restore-Point for Product [Microsoft Project Standard 2010] (with RestorePointType [0, Installed]).
Not showing completion dialog because it was not requested.
Catalyst execution finished: 05/09/2014 20:19:25. Return code: 1603.
PERF: TickCount=722128 Name=RunSetup Description=End function
Can onyone enlighten me what's went wrong, and why did I get this inconsitent installation behaviour?
Thank you very much!!!

1603 means there is a fatal error during installation process.
Take a look at the article below. It may help on finding cause.
Hi Juke,
I did do fair a bit of Googling before I started the post. I have increased the logging level on one of the machines failed on the installation. Apparently Project installation log doesn't throw the "return value 3", I think it's pointing to a particular
updating item, anyone knows what is it?
Microsoft Office Project Standard 2010 - Update '{35347883-0E64-45B4-88A0-1881DE05E259}' could not be installed.
The following is the detailed installation log.
MSI (s) (8C:B4) [20:31:33:122]: Executing op: SetTargetFolder()
MSI (s) (8C:B4) [20:31:33:122]: Executing op: FontRegister(Title=Arial Unicode MS (TrueType),File=ARIALUNI.TTF)
MSI (s) (8C:B4) [20:31:33:122]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\Fonts
MSI (s) (8C:B4) [20:31:33:122]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (8C:B4) [20:31:33:122]: Error in rollback skipped. Return: 5
MSI (s) (8C:B4) [20:31:33:746]: Entering MsiProvideAssembly. AssemblyName: Policy.12.0.Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:746]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:777]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:777]: Entering MsiProvideAssembly. AssemblyName: Policy.11.0.Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:777]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:808]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:808]: Entering MsiProvideAssembly. AssemblyName: Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:808]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:840]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:840]: Note: 1: 2318 2:
MSI (s) (8C:B4) [20:31:33:840]: No System Restore sequence number for this installation.
MSI (s) (8C:B4) [20:31:33:840]: Unlocking Server
MSI (s) (8C:B4) [20:31:33:980]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (8C:B4) [20:31:34:011]: Product: Microsoft Office Project Standard 2010 - Update '{35347883-0E64-45B4-88A0-1881DE05E259}' could not be installed. Error code 1603. Additional information is available in the log file C:\WINDOWS\TEMP\MSI1f79e.LOG.
MSI (s) (8C:B4) [20:31:34:011]: Windows Installer installed an update. Product Name: Microsoft Office Project Standard 2010. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Update Name: {35347883-0E64-45B4-88A0-1881DE05E259}. Installation success or error status: 1603.
MSI (s) (8C:B4) [20:31:34:011]: Note: 1: 1708
MSI (s) (8C:B4) [20:31:34:011]: Product: Microsoft Office Project Standard 2010 -- Installation operation failed.
MSI (s) (8C:B4) [20:31:34:011]: Windows Installer installed the product. Product Name: Microsoft Office Project Standard 2010. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202cf.msp
MSI (s) (8C:B4) [20:31:34:011]: Unable to delete the file. LastError = 32
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202d0.mst
MSI (s) (8C:B4) [20:31:34:011]: Unable to delete the file. LastError = 32
MSI (s) (8C:B4) [20:31:34:011]: Deferring clean up of packages/files, if any exist
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202cf.msp
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202d0.mst
MSI (s) (8C:B4) [20:31:34:011]: MainEngineThread is returning 1603
MSI (s) (8C:24) [20:31:34:011]: No System Restore sequence number for this installation.
MSI (s) (8C:24) [20:31:34:011]: User policy value 'DisableRollback' is 0
MSI (s) (8C:24) [20:31:34:011]: Machine policy value 'DisableRollback' is 0
MSI (s) (8C:24) [20:31:34:011]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (8C:24) [20:31:34:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:24) [20:31:34:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:24) [20:31:34:027]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (8C:24) [20:31:34:027]: Restoring environment variables
MSI (s) (8C:24) [20:31:34:027]: Destroying RemoteAPI object.
MSI (s) (8C:48) [20:31:34:027]: Custom Action Manager thread ending.
MSI (c) (F4:1C) [20:31:34:027]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F4:1C) [20:31:34:027]: MainEngineThread is returning 1603
=== Verbose logging stopped: 7/05/2014 20:31:34 ===

VMM 2012 R2 Template creation fails with sysprep error via the gui, but works in powershell?

I'm in the process of trying to convert an existing gen1 VM (Win Server 2012 R2) to a VM template using VMM 2012 R2 with rollup 1. The creation keeps failing with the following error :-
"Error
(2901)The operation did not complete successfully because of a parameter or call sequence
that is not valid.Recommended ActionEnsure
that the parameters are valid, and then try the operation again."
I've checked that the local administrator account for the machine being converted to a template and it is blank as expected and in an attempt to troubleshoot I've output the template creation script via the VMM GUI and executed the commands in order which appears
to have resolved the problem, well the template finishes creation, i'm yet to deploy a machine via it?
# Create VM Template Wizard Script
# Script generated on Thursday, April 3, 2014 12:52:15 PM by Virtual Machine Manager
# For additional help on cmdlet usage, type get-help <cmdlet name>
$VM = Get-SCVirtualMachine -VMMServer localhost -Name "MyTemplate_Template" -ID "98299447-83e1-4d98-a558-a96ebafcf9b5"
| where {$_.VMHost.Name -eq "myhost.mydomain.com"}
$LibraryServer = Get-SCLibraryServer -VMMServer localhost | where {$_.Name -eq "my.library.com"}
$GuestOSProfile = Get-SCGuestOSProfile -VMMServer localhost | where {$_.Name -eq "Windows Server 2012
R2"}
$OperatingSystem = Get-SCOperatingSystem -VMMServer localhost -ID "50b66974-c64a-4a06-b05a-7e6610c579a2"
| where {$_.Name -eq "Windows Server 2012 R2 Standard"}
$template = New-SCVMTemplate -Name "My Template" -RunAsynchronously -VM $VM -LibraryServer $LibraryServer
-SharePath "\\mylibrary.mydomain.com\SCVMM Library\Templates\mytemplatedestination" -GuestOSProfile $GuestOSProfile -JobGroup d2f2f539-85da-4091-ab08-abe739fc4761 -ComputerName "*" -TimeZone 85 -FullName "Administrator"
-OrganizationName "My Organisation" -Workgroup "WORKGROUP" -AnswerFile $null -OperatingSystem $OperatingSystem
Now the only fields that weren't populated when I ran through the gui were FullName and Organization? Before I changed the script these two fields were just set to ""? Is that what has potentially caused the issue are they both required fields?

Your not the only one who can reproduce this. Did you ever find out what it was? I saw your post and tried your same work-around and it also worked for me via Powershell.

How to deploy ADF-BC (SDO) with ANT

I have an ADF-BC exposed as an webserivce. I can deploy it via JDeveloper, but how do I deploy it with ANT. Does anyone has an ANT script example, based on ADF-BC
Marc
http://orasoa.blogspot.com

I am using JDev 11g (ps1). The link you mentioned, is about deploying artifacts to the MDS. I want to deploy and ADFBC exposed as an webservice , (aka SDO object) to the server via ANT.
Marc

HSS "Deployment Metadata" export (partly) fails with 4 error messages:

The "Deployment Metadata"-export fails.
It fails both on HSS user interface or via the LCM utility on the foundation server and on a non foundation machine.
Perhaps its due to the fact that we have 3 essbase servers with a couple of essbase application/ database with the same names. But if thats the case this should not happen I guess.
(ApplicationX.DatabaseY exists both on Essbase serverA and essbase serverB)
Any help will be great.
kind regards,
Detlev
Error in migrating artifact, "/Shared Services Registry/Essbase/Cluster - inform.acc@inform/Properties".
EPMREG-10003: An unexpected error occurred during storing the artifact Properties. Detailed message is /Shared Services Registry/Essbase/Cluster - inform.acc@inform
Error in migrating artifact, "/Shared Services Registry/Essbase/Cluster - inform.check@inform/Properties".
EPMREG-10003: An unexpected error occurred during storing the artifact Properties. Detailed message is /Shared Services Registry/Essbase/Cluster - inform.check@inform
Warning in migrating artifact, "/Shared Services Registry/Essbase/ITC - EssbaseServer@inform/Properties".
EPMLCM-35003: Application artifact listing metadata contains duplicate resource information for /Shared Services Registry/Essbase/ITC - EssbaseServer@inform/Properties.
Warning in migrating artifact, "/Shared Services Registry/Foundation Services/Shared Services/ITC - Foundation@inform/Properties".
EPMLCM-35003: Application artifact listing metadata contains duplicate resource information for /Shared Services Registry/Foundation Services/Shared Services/ITC - Foundation@inform/Properties.
Warning in migrating artifact, "/Shared Services Registry/Interactive Reporting/Agent Module@ServerX_6814,6815/RAService - DataAccess@serverX/Das Dsn@ServerY/Properties".
EPMLCM-35003: Application artifact listing metadata contains duplicate resource information for /Shared Services Registry/Interactive Reporting/Agent Module@ServerX_6814,6815/RAService - DataAccess@ServerX/Das Dsn@ServerY/Properties
Edited by: Detlev on Apr 8, 2013 4:46 PM

Could you try to use adt to package the AIR file?
There might be some error messages that doesn't get caught by Flash Builder.
Have you modified the Application Descriptor since last succeful packaging?

LDAP Broken Pipe exception when deploying processes via ant task

Hi,
Has anyone experienced this and can offer a fix? We are publishing/deploying our processes using the fuego:publish task in Fuego 5.7 (we are migrating our system from 5.1) and one of the publish tasks for a large project always fails with the following exception:
Caused by: fuego.directory.CommunicationException: Cannot connect to the Directory Service at: [iplanet://zion:28899/o=nexagent.com].
Detail:The Directory Service could not be reached. Either the Directory Service is down, the host where it resides is unavailable, a network problem exists, or there is no Directory Service at the specified location.
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:465)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:489)
at fuego.directory.provider.ldap.LDAPProjectAccessor.createCatalogJar(LDAPProjectAccessor.java:160)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:257)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:46)
at fuego.mami.CatalogPublisher.store(CatalogPublisher.java:369)
at fuego.mami.ProjectPublisher.storeCatalog(ProjectPublisher.java:1631)
at fuego.mami.ProjectPublisher.storeProject(ProjectPublisher.java:1653)
at fuego.mami.ProjectPublisher.publish(ProjectPublisher.java:854)
at fuego.tools.ant.enterprise.impl.PublishProjectTaskImpl.execute(PublishProjectTaskImpl.java:377)
... 23 more
Caused by: javax.naming.CommunicationException: Broken pipe [Root exception is java.net.SocketException: Broken pipe]; remaining name 'cn=catalogJar-3,cn=fuego-dirCatalogJars,cn=fuego-directoryRoot'
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:803)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:178)
at fuego.jndi.FaultTolerantDirContext.createSubcontext(FaultTolerantDirContext.java:413)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createNestedEntry(LDAPPersistenceManager.java:1744)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:455)
... 32 more
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:389)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:364)
at com.sun.jndi.ldap.LdapClient.add(LdapClient.java:1007)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:766)
... 39 more
Looking at the LDAP access log the error code is B1 which means that the client closed the connection without sending an unbind request or it could also mean that the client sent a malformed request to the server. The project being deployed is quite big and fails when storing the catalog, could the size have something to do with it (this worked in v5.1) is this a bug in 5.7?
Any help would be greatly appreciated!
regards,
Mike

Hi,
Has anyone experienced this and can offer a fix? We are publishing/deploying our processes using the fuego:publish task in Fuego 5.7 (we are migrating our system from 5.1) and one of the publish tasks for a large project always fails with the following exception:
Caused by: fuego.directory.CommunicationException: Cannot connect to the Directory Service at: [iplanet://zion:28899/o=nexagent.com].
Detail:The Directory Service could not be reached. Either the Directory Service is down, the host where it resides is unavailable, a network problem exists, or there is no Directory Service at the specified location.
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:465)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:489)
at fuego.directory.provider.ldap.LDAPProjectAccessor.createCatalogJar(LDAPProjectAccessor.java:160)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:257)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:46)
at fuego.mami.CatalogPublisher.store(CatalogPublisher.java:369)
at fuego.mami.ProjectPublisher.storeCatalog(ProjectPublisher.java:1631)
at fuego.mami.ProjectPublisher.storeProject(ProjectPublisher.java:1653)
at fuego.mami.ProjectPublisher.publish(ProjectPublisher.java:854)
at fuego.tools.ant.enterprise.impl.PublishProjectTaskImpl.execute(PublishProjectTaskImpl.java:377)
... 23 more
Caused by: javax.naming.CommunicationException: Broken pipe [Root exception is java.net.SocketException: Broken pipe]; remaining name 'cn=catalogJar-3,cn=fuego-dirCatalogJars,cn=fuego-directoryRoot'
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:803)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:178)
at fuego.jndi.FaultTolerantDirContext.createSubcontext(FaultTolerantDirContext.java:413)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createNestedEntry(LDAPPersistenceManager.java:1744)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:455)
... 32 more
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:389)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:364)
at com.sun.jndi.ldap.LdapClient.add(LdapClient.java:1007)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:766)
... 39 more
Looking at the LDAP access log the error code is B1 which means that the client closed the connection without sending an unbind request or it could also mean that the client sent a malformed request to the server. The project being deployed is quite big and fails when storing the catalog, could the size have something to do with it (this worked in v5.1) is this a bug in 5.7?
Any help would be greatly appreciated!
regards,
Mike

SAP Strategy Management 7.0 SSM Component Deployment failed with JSPM

Dear experts,
i have installed a SAP Netweaver CE 7.1 on Windows Server 2003 Enterprise x64 with MS SQL and i wish to install now SAP Strategy Management 7.0 with JSPM Tool.
I have copied the CPMSTRMGMAPC00_0.SCA file on the usr\sap\trans\EPS\in\ directory and the deployment precessus failed with error before the AS JAVA has been restarted.
How can i manage this problem? Any suggestion is welcomed.
Thank you very much.
Best regards,
Pascal.

Any ideas?
Here is the F:\usr\sap\PI7\J71\j2ee\JSPM\log\log_2009_06_15_12_51_48\deploy_2009-06-15_14-56-58.log
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.7.1006]/>
<!NAME[F:\usr\sap\PI7\J71\j2ee\JSPM\log\log_2009_06_15_12_51_48\deploy_2009-06-15_13-07-03.log]/>
<!PATTERN[deploy_2009-06-15_13-07-03.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%6s]:%m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jun 15, 2009 1:07:03 PM [Info ]:DC API is trying to connect to 'sap-pi7:57104'
Jun 15, 2009 1:07:03 PM [Info ]:DC API has Connected to 'sap-pi7:57104'
Jun 15, 2009 1:07:03 PM [Path ]:+++++ Starting V A L I D A T E action +++++[ deployerId=2 ]. timerId=7
Jun 15, 2009 1:07:03 PM [Path ]:Selected archives for validation. [ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Path ]:
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca
Jun 15, 2009 1:07:03 PM [Debug ]:Got full sdu path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
Jun 15, 2009 1:07:03 PM [Path ]:component version handling rule is UpdateLowerVersionsOnly.[ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Path ]:deployment workflow strategy is safety deploy strategy.[ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Path ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Path ]:Error strategies[ deployerId=2 ]:
Jun 15, 2009 1:07:03 PM [Path ]:error action 'DeploymentAction' is 'OnErrorStop'
Jun 15, 2009 1:07:03 PM [Path ]:error action 'PrerequisitesCheckAction' is 'OnErrorSkipDepending'
Jun 15, 2009 1:07:03 PM [Debug ]:deployer initialized successfully:[id:#8, elapsed: 0 ms.].[ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Debug ]:Total time:[#8: 0.0 sec].[ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Info ]:Start validating.[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:Validating completed. Preparing the validation result.
Jun 15, 2009 1:07:06 PM [Path ]:
Sorted Items -
     1. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca --> xappscpmsm~strategymanagement.sda'
     Sdu info :name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]
          Deploy status is 'Admitted'
     2. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
     Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
          Deploy status is 'Admitted'
Deployment Items -
     1. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
     Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
          Deploy status is 'Admitted'
          Time statistics:
          Contained DCs:
          1.1:name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]
                    Deploy status is 'Admitted'
          1.2:name 'xappscpmsm~strategymanagementactions', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465041', software type ('J2EE', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465041'.
          1.3:name 'xappscpmsm~strategymanagementdoc', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465046', software type ('J2EE', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465046'.
          1.4:name 'xappscpmsm~strategymanagementdic', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465042', software type ('JDDSCHEMA', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465042'.
Jun 15, 2009 1:07:06 PM [Info ]:+++ Validation finished with status 'Success' +++[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:+++++ End V A L I D A T E action +++++[ deployerId=2 ]. Total time:[#7: 3.016 sec]
Jun 15, 2009 1:07:06 PM [Path ]:+++++ Starting D E P L O Y action +++++ [ deployerId=2 ] [ timerId=9]
Jun 15, 2009 1:07:06 PM [Path ]:Selected archives for deployment. [ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca
Jun 15, 2009 1:07:06 PM [Debug ]:Got full sdu path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
Jun 15, 2009 1:07:06 PM [Path ]:component version handling rule is UpdateLowerVersionsOnly.[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:deployment workflow strategy is safety deploy strategy.[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:Error strategies[ deployerId=2 ]:
Jun 15, 2009 1:07:06 PM [Path ]:error action 'DeploymentAction' is 'OnErrorStop'
Jun 15, 2009 1:07:06 PM [Path ]:error action 'PrerequisitesCheckAction' is 'OnErrorStop'
Jun 15, 2009 1:07:06 PM [Debug ]:deployer initialized successfully:[id:#11, elapsed: 15 ms.].[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Debug ]:Total time:[#11: 0.015 sec].[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:Starting deployment.[ deployerId=2 ]
Jun 15, 2009 1:07:17 PM [Debug ]:clusterRestartTriggered for transactionId:223, clusterEventAction:cluster restart triggered
Jun 15, 2009 1:07:17 PM [Debug ]:Mark transaction '223' as offline phase.
Jun 15, 2009 1:07:17 PM [Info ]:+++ Performing offline deployment. Server is being restarted +++.The timeout for the operation is: 86400 sec.
Jun 15, 2009 1:07:17 PM [Path ]:+++ Wait for server response +++. Elapsed: 0 ms.
Jun 15, 2009 1:07:47 PM [Path ]:+++ Wait for server response +++. Elapsed: 484 ms.
Jun 15, 2009 1:08:19 PM [Path ]:+++ Wait for server response +++. Elapsed: 30484 ms.
Jun 15, 2009 1:08:49 PM [Path ]:+++ Wait for server response +++. Elapsed: 62140 ms.
Jun 15, 2009 1:09:19 PM [Path ]:+++ Wait for server response +++. Elapsed: 92156 ms.
Jun 15, 2009 1:09:49 PM [Path ]:+++ Wait for server response +++. Elapsed: 122171 ms.
Jun 15, 2009 1:10:19 PM [Path ]:+++ Wait for server response +++. Elapsed: 152171 ms.
Jun 15, 2009 1:10:49 PM [Path ]:+++ Wait for server response +++. Elapsed: 182296 ms.
Jun 15, 2009 1:11:20 PM [Path ]:+++ Wait for server response +++. Elapsed: 212905 ms.
Jun 15, 2009 1:12:22 PM [Info ]:Engine is up and running. Wait for engine deployment result.
Jun 15, 2009 1:12:22 PM [Debug ]:DC API will create new CM
Jun 15, 2009 1:12:52 PM [Path ]:+++ Wait for server response +++. Elapsed: 305686 ms.
Jun 15, 2009 1:13:22 PM [Path ]:+++ Wait for server response +++. Elapsed: 335685 ms.
Jun 15, 2009 1:13:53 PM [Path ]:+++ Wait for server response +++. Elapsed: 365701 ms.
Jun 15, 2009 1:14:23 PM [Path ]:+++ Wait for server response +++. Elapsed: 395701 ms.
Jun 15, 2009 1:14:53 PM [Path ]:+++ Wait for server response +++. Elapsed: 425763 ms.
Jun 15, 2009 1:15:24 PM [Path ]:+++ Wait for server response +++. Elapsed: 456856 ms.
Jun 15, 2009 1:15:54 PM [Path ]:+++ Wait for server response +++. Elapsed: 487012 ms.
Jun 15, 2009 1:15:57 PM [Info ]:Engine is up and running. Wait for engine deployment result.
Jun 15, 2009 1:15:57 PM [Info ]:server is online, time:[id:#10, elapsed: 520059 ms.]
Jun 15, 2009 1:15:57 PM [Path ]:Deployment completed. Preparing the deployment result.[ deployerId=2 ]
Jun 15, 2009 1:15:57 PM [Path ]:
Sorted Items -
     1. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca --> xappscpmsm~strategymanagement.sda'
     Sdu info :name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]
          Deploy status is 'Aborted'
          Description:'1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
           -> class java.lang.NullPointerException'.
     2. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
     Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
          Deploy status is 'Aborted'
          Description:'1. Contains Aborted deployment component:
sdu id: sap.com_xappscpmsm~strategymanagement
sdu file path: F:\usr\sap\PI7\J71\j2ee\cluster\server0\.\temp\tcbldeploy_controller\archives\223\CPMSTRMGMAPC00_0_sca1245064026979\DEPLOYARCHIVES\xappscpmsm~strategymanagement.sda
version status: NEW
deployment status: Aborted
description: 1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
           -> class java.lang.NullPointerException'.
Deployment Items -
     1. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
     Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
          Deploy status is 'Aborted'
          Description:'1. Contains Aborted deployment component:
sdu id: sap.com_xappscpmsm~strategymanagement
sdu file path: F:\usr\sap\PI7\J71\j2ee\cluster\server0\.\temp\tcbldeploy_controller\archives\223\CPMSTRMGMAPC00_0_sca1245064026979\DEPLOYARCHIVES\xappscpmsm~strategymanagement.sda
version status: NEW
deployment status: Aborted
description: 1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
           -> class java.lang.NullPointerException'.
          Time statistics:
          Contained DCs:
          1.1:name 'xappscpmsm~strategymanagementdic', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465042'.
          1.2:name 'xappscpmsm~strategymanagementdoc', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465046'.
          1.3:name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]
                    Deploy status is 'Aborted'
          Time statistics( ms ):
               1.deployment : 34906
                    1.1.Notify:Event triggered : 157
                    1.2.Disable LCM deployment : 34656
                         1.2.1.Perform delivery : 34656
                              1.2.1.1.Application Deployer : 34656
                    1.3.Notify Observers : 15
                         1.3.1.Persist in storage : 15
                    1.4.Notify:Event performed : 78
               2.Persist in storage : 16
                    Description:'1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
           -> class java.lang.NullPointerException'.
          1.4:name 'xappscpmsm~strategymanagementactions', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465041'.
Jun 15, 2009 1:15:57 PM [Info ]:
Deploy Result Description: Deployment exception occurred during deploy online data. Reason :An error occurred while deploying the deployment item 'sap.com_xappscpmsm~strategymanagement'.; nested exception is:
     com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of sap.com_xappscpmsm~strategymanagement. Cannot deploy it.
[ deployerId=2 ]
Jun 15, 2009 1:15:57 PM [Info ]:+++ Deployment finished with status 'Error' +++.[ deployerId=2 ][#10: 530.465 sec]
Jun 15, 2009 1:15:57 PM [Path ]:+++++ End D E P L O Y action +++++[ deployerId=2 ]. Total time:[#9: 530.465 sec]
Jun 15, 2009 1:15:57 PM [Debug ]:Incorrect client ID. The stub is not connected yet.
Jun 15, 2009 1:15:57 PM [Debug ]:Incorrect client ID. The stub is not connected yet.

Error when deploying EAR file: Operation failed with error: java:/app/jdbc/

I created application using JDeveloper 11g, and have the deploy file EAR read to deploy to oracle application server 10g, but I am encouting the error of Operation failed with error: java:/app/jdbc/jdbc/HRConnDS not found
Below is the log. What did i do wrong? I have created the datasource of HRConnDS, and it shows in EM.
Nov 6, 2009 10:06:12 AM] Application Deployer for hra1 STARTS.
[Nov 6, 2009 10:06:12 AM] Copy the archive to /u01/OraHome_app1/j2ee/home/applications/hra1.ear
[Nov 6, 2009 10:06:12 AM] Initialize /u01/OraHome_app1/j2ee/home/applications/hra1.ear begins...
[Nov 6, 2009 10:06:12 AM] Unpacking hra1.ear
[Nov 6, 2009 10:06:12 AM] Done unpacking hra1.ear
[Nov 6, 2009 10:06:12 AM] Unpacking webapp2.war
[Nov 6, 2009 10:06:12 AM] Done unpacking webapp2.war
[Nov 6, 2009 10:06:12 AM] Initialize /u01/OraHome_app1/j2ee/home/applications/hra1.ear ends...
[Nov 6, 2009 10:06:12 AM] Starting application : hra1
[Nov 6, 2009 10:06:12 AM] Initializing ClassLoader(s)
[Nov 6, 2009 10:06:12 AM] Initializing EJB container
[Nov 6, 2009 10:06:12 AM] Loading connector(s)
[Nov 6, 2009 10:06:12 AM] Starting up resource adapters
[Nov 6, 2009 10:06:12 AM] application : hra1 is in failed state
[Nov 6, 2009 10:06:12 AM] Operation failed with error: java:/app/jdbc/jdbc/HRConnDS not found
Thank you very much for your help.

How did you create your datasource, can you post the content, without passwords of course.
Greetings.

My IPOD Touch initially had a white screen. I tried correcting this by restoring default settings via ITunes. The Restore Failed with error 1602 and now the IPOD touch is completely dead. It will not power on or respond when I plug it into my PC via USB

My IPOD Touch initially had a white screen. I tried correcting this by restoring default settings via ITunes. The Restore Failed with error 1602 and now the IPOD touch is completely dead. It will not power on or respond when I plug it into my PC via USB. I get an error on my PC stating that device attached to USB port is not recognizable. Can anyone help?

Error 1602: Try the following steps to resolve this error:
Ensure proper USB isolation troubleshooting has been performed, and test with a known-good cable.
Follow the steps listed for Error 1604.
This error may be resolved by disabling, deactivating, or uninstalling third-party security, antivirus, and firewall software. See steps in this article for details on troubleshooting security software.
Above from:
http://support.apple.com/kb/TS3694

Hi, I've been trying for days to download Windows support software via Bootcamp assistant, but it always failed with message 'Can't install Windows Support Software because it is not currently available from the Software update server.' Any advice welcome

Hi,
I've been trying for days to download Windows support software via Bootcamp assistant but it always fails with message 'Can't install windows software because it is not currently available from the software update server.'
Anyone else had problems or success with this?
Thanks in advance.

9thdoc wrote:
I'm getting a similar but distinct error message in snow leopard: Download could not continue. "The windows support software is not available" and have no original snow leopard instal disc with me.
Your issue is completely different. You are running Snow Leopard. There is no download for Windows Support software for Snow Leopard, hence the error you see. Snow Leopard Windows Support software is on the Snow Leopard installation disk.
You need the Snow Leopard installation disk or a replacement for it.

Wlst deploy via ant fails with NameNotFoundException

Similar Messages

Maybe you are looking for