Rwcli60 terminate with errors

Hi reports gurus,
When run rwcli60 like this:
rwcli60 userid=user/pass@db server=repser report=test.rdf destype=file desformat=PDF desname=test.pdf
i receive the following errors:
REP-0177: Error while running in remote server
REP-0110: Unable to open file '/export/home1/orion/mod/rpt60/test.rdf'.
REP-1070: Error while opening or saving a document.
REP-0110: Unable to open file '/export/home1/orion/mod/rpt60/test.rdf'.
I think that it isn't a problem of REPORT_PATH, because the REPORT_PATH variable contain already directory of test.rdf file.
It seem strange for me. Any idea plz help.
NB: I'm using reports 6i on sun solaris 9.Thx

I don't that it's a problem of ORACLE_HOME.
Can somone already receive this error and fix it.
PLZ show me the way to fix this problem, it's very important.

Similar Messages

Adobe Application Manager terminates with Error Code A12E1

After downloading the new AAM from the Creative Cloud website and running it I get the following Error:
The last lines of the log file look like this:
Fri May 11 10:01:00 2012
[INFO] OPM - Build Version - 6.0.309.0
Fri May 11 10:01:00 2012
[INFO] OPM - Logging Level verbosity Set to 4
Fri May 11 10:01:00 2012
[INFO] OPM - Schema version and schema compatibility version are same or greater than current
Fri May 11 10:01:00 2012
[INFO] OPM - No Record found for the input fields
Fri May 11 10:01:00 2012
[INFO] OPM - Released OPM refrence successfully
Fri May 11 10:01:25 2012
[INFO] Setup - Build Version - 6.1.76.0
Fri May 11 10:01:25 2012
[INFO] Setup - Logging Level verbosity Set to 4
Fri May 11 10:01:25 2012
[INFO] Setup - TimeLog: Bootstrapper Start
Fri May 11 10:01:25 2012
[INFO] Setup - Launch Path set to /Volumes/ASU
Fri May 11 10:01:25 2012
[INFO] Setup - Found 7 packages in setup manifest
Fri May 11 10:01:55 2012
[FATAL] Native-Utils - Error Failed to close all Non Deployment Workflows ...
Fri May 11 10:01:55 2012
[FATAL] Setup - Error closing notification workflows. Cannot Install.
Fri May 11 10:01:55 2012
[INFO] Setup - ================= Exiting Installer with Code: -3 =================
I have killed all AAM* processes but always get the same error. Also downloaded multi times ... same effect.

"5.saurabhGupta1403,
May 11, 2012 9:32 PM in reply to Michael Carvin
Report
Try using the cleaner tool : http://www.adobe.com/support/contact/cscleanertool.html
Clean only AAM from the system. It should solve the problem."
This is what worked for me!

Import terminates with error Memory fault(coredump)

Hello All,
I am trying to import the data from 9.2.0.8 to 10.2.0.4 on HP UX 11i.
After some times i get error
Memory fault(coredump)
and import job gets disconnected. There are no other logs/ errors reported even at the db level nor at import job.
Request to help if some body knows about the cause.
Thank you,
Anil

Hi,
I'm also experiencing this error.
Some info on my databases
[EXP]
Version: 9.2.0.5.0 - 64bit Production
Character Set: US7ASCII
National Character Set: AL16UTF16
[IMP]
Version: 9.2.0.5.0 - 64bit Production
Character Set: US7ASCII
National Character Set: AL16UTF16
[Common]
Machine Type: HP-UX B.11.11
The import job terminates and leave a file named core which is sized to the amount i placed in the buffer. How do i proceed on this one? Thanks.

Hierarchy from flat file loading with errors - duplicate node names

Hello experts,
I am loading a product hierarchy from a flat file into a custom hierarchy
object. The issue is that it errors out saying I am loading
duplicates within nodes, however all node IDs within a level are unique.
It seems to be looking at the node name to determine uniqueness and I know
we have some duplication within the text there especially when you factor
in the 32 character limitation for the node name. Does anyone have an idea
as to whether it is possible to have it only consider the node ID instead
of the node name to determine uniqueness?
A colleague suggested using the link ID to fix this problem but I don't know how that field works or how to populate it.
I'm working in a BI 7.0 environment (I don't know if that makes a difference since you still have to use the 3.x objects to extract the hierarchy).
Any help would be appreciated.
Nancy

Hi Nancy,
You may wish to check this OSS Note 1026749 - Hierarchies: Consistency check for duplicate nodes and 912115 (old one)
Symptom -
When you load or activate a hierarchy it terminates with error message RH 109 or RH 211. The hierarchy contains duplicate nodes and this is not allowed. The long texts of messages RH 109 or RH 211 do not describe the reason for the problem sufficiently or they are partially incorrect.
There is uncertainty about in which cases duplicate nodes exist in a hierarchy and in which cases duplicate nodes are allowed.
Hope this helps,
Bye...
Naga Timmaraju

Update statistics ends with error

Hi Techies
Few months back our BI system got crashed then ,we re-install the system & restore the database,Now the issue is whenever we are running the update statistics it gives the following error & terminates with error.
BR0301E SQL error -20000 at location stats_ind_collect-2, SQL statement:
'BEGIN DBMS_STATS.GATHER_INDEX_STATS (OWNNAME => '"SAPSR3"', INDNAME => '"/BIC/B0000598000KE"', ESTIMATE_PERCENT => NULL, DEGREE => NULL,
ORA-20000: index "SAPSR3"."/BIC/B0000598000KE" or partition of such index is in unusable state
ORA-06512: at "SYS.DBMS_STATS", line 10613
ORA-06512: at "SYS.DBMS_STATS", line 10648
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for index SAPSR3./BIC/B0000598000KE
BR0301E SQL error -20000 at location stats_tab_collect-18, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BIC/B0000598000"', ESTIMATE_PERCENT => 30, METHOD_OPT => 'FOR A
ORA-20000: index "SAPSR3"."/BIC/B0000598000KE" or partition of such index is in unusable state
ORA-06512: at "SYS.DBMS_STATS", line 13159
ORA-06512: at "SYS.DBMS_STATS", line 13179
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for table SAPSR3./BIC/B0000598000
Environment Details
OS-AIX 5.3
DB-Oracle 10.2.0.2.0
SAP-SAP Netweaver 2004s
BI-SAP Netweaver BI 7.0
Quick response appreciated
Thanks
Vijay

Hi,
ORA-20000: index "SAPSR3"."/BIC/B0000598000KE" or partition of such index is in unusable state
rebuild the index using BRTOOLS.
Run brtools
select 3 --> SEGMENT MANGEMENT --> 2 - Rebuild indexes --> 7 ~ Index names (index)
provide your index name here SAPSR3"."/BIC/B0000598000KE
and rebuild the index
after running rebuild index , start again Update Statistics.
it will run succesful
Thanks
Anil

OPatch failed with error code 73

Friends,
We are getting below error message while firing $ORACLE_HOME/OPatch/opatch lsinventory.Please suggest me whether what could be the reason for this.Appricate your help.
Inventory load failed... OPatch cannot load inventory for the given Oracle Home.
Locker::release()
OUISessionManager::unRegister()
Un-Registering the caller : OPatch
LsInventory::getInstance() returns
LsInventorySession failed: Unable to create patchObject
Cleaning up the directory : "/oracle/rdbms/10.2.0.4/.patch_storage/patch_unzip"...
OPatch failed with error code 73
Regards,
Vinay

Following these instructions solved the problem for me, maybe they will help you.
Issue 3: On Linux AMD x86-64 on RHEL4 systems, if you run OPatch in -report mode, it detects the incorrect platform and then terminates with errors similar to the following:
Apply Session failed: ApplySession failed to prepare the system.
OPatch failed with error code 73
Workaround: Set the OPATCH_PLATFORM_ID environment variable to point to the AMD64 Linux platform, whose ID is 226. For example:
export OPATCH_PLATFORM_ID=226
Then re-run OPatch in -report mode, for example:
opatch apply -report
Or
opatch rollback -report

Time Machine will not complete a system backup and terminates with "Unable to complete backup. An error occurred while copying files to the backup volume. This follows a problem when Time machne terminated when the volume was almost full.

On 11/1/2011, Time Machine (TM) terminated with an error message I did not record. I noted that the drive was full and decided to do a separate complete bootable system backup using Carbon Copy Clone (CCC), before clearing the TM volume and trying to start it over clean. Part way through the full system backup CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". That was about the time that TM malfunctioned, so I assumed they were related. After starting CCC over a couple of times, and getting the same error message, I let it go through to completion of the backup, which took three or four hours. I then ran tests using Disk Utility and verified that there was nothing physically wrong with both the internal hard drive and the TM volume. I also erased and reformatted the TM volume. However, every time I started Time Machine, it would record a few GB and terminate with "Unable to complete backup. An error occurred while copying files to the backup volume". I restarted the computer with no change in results. Note that prior to starting the CCC backup, I "Repaired Permissions", "zapped the PRAM" and "re-set the SMC", hoping to have a clean bootable system on the backup. I ran Techtool and no problems were found.
I'm running this on an Intel iMac under 10.5.8 and recording to a 500GB My Passport drive. My hard drive is only about half full at 246 GB. My assessment is that something happened at 16-28-16 on 11/1/2001 to screwup the Backup Directory in the file at "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". My question is, how do I fix it?
I had just completed writing everything above here, explaining the problems I had been encountering for the past 24 hours. I had the Time Machine window standing open on the desktop where I could see it, having recentlycleared it after the last termination. As I was proofing what I had written, I looked at the window and noted that the clock had started a new run for a full back up, since all prior efforts had failed and the TM volume was empty. As I watched and waited for it to fail again, as it had been doing at about 13 GB, it kept going and going until it just finished a complete backup, about 4.5 hours later, with my having done nothing. Now my question would have to be - what could possiibly have happened to make it perform this way? It will be interesting to see if it continue to operate normally, or if the problem will return, in a later backup run.

jcm21 wrote:
CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16"
You should not keep those files for long, and probably shouldn't back them up (if you need them at all -- since you do regular backups, I'm doubtful just how worthwhile that feature is).
"Unable to complete backup. An error occurred while copying files to the backup volume".
One of Apple's maddeningly incomplete messages. Most likely, there's a problem with a file (quite possibly the one CCC didn't like). See #C3 in Time Machine - Troubleshooting for details and instructions on finding and fixing it.
If you continue running the Directory Protection app, be sure to exclude your Time Machine drive from it (as it will just take up lots of room, and won't help repair your backups if there's a problem); and exclude the folders it creates from being backed-up by Time Machine (as they'll create large backups, and you probably can't use the backed-up folders anyway), per #10 in Time Machine - Frequently Asked Questions.

Can not install this update for kb2667402 windows 7 professional. I tried various fix-it but it did not help Update KB2667402 failed with error 80004005

I'm not sure where to turn now and am soooooooooo frustrated! I have been trying to get security update KB2667402 with error code 80004005 to install for a couple months without any success.
So, I finally turned to microsoft tech support... Case# 1186572463
On Fri. Oct. 26 I was on the phone with a microsoft tech for over 3 hours. The tech that took remote access of my computer said she did not know how to fix my problem and that my case would have to be escalated to a higher level and that I would
receive a call back on Mon. Oct. 29th. However, I never got a return call.
Yesterday - Tues. Oct. 30th I called in again and was on the phone for 4.5 hrs with a microsoft tech and he also took remote access of my computer but was not able to fix the problem. I asked to speak to someone at a higher tech level and was told to call
back into the microsoft helpline.
The 3rd call - Although I had been told during the prior 2 calls that I was still covered under my warrenty I was now told that I needed to pay for the support call. It took a while to get that straighteded out and to give all my information again to
the call center but I finally worked with a 3rd tech for over 2 hrs. but had to terminate the call for a conference call I had with a client. The person I worked with said he would call me back between 7-8pmEST so he could continue helping me but I never
got a return call.
I have already invested over 10 hrs in the last few days regarding this issue and fear that if I call back in I will once again start over completely with no success which is why I am reaching out here. Is there anyone that has the knowledge of how to fix
the problem?

I've been having the same problem and today did some searching and found something that worked. Check that the download hasn't already been installed - look in the Installed Updates listing for an entry. If it exists there, uninstall it, and
then force a Check For Updates and retry the install. This worked for me and I hope it helps.
Good day, Chuck.

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 ===

Transport control program tp ended with error code 0211

Dear Experts,
I have a problem in doing the import after the client export was successfully done.
I am actaully tring to do a client import/export from the PRD server to DEV server.
On PRD the client is 900 and on the DEV the client is 240.
I have manually copied the transport requests created into the
/usr/sap/trans/cofiles and /usr/sap/trans/data folders to the same on the DEV server.
After coping them,
I have tried to add these transport requests to the DEV server queue, i get the following error message
Transport control program tp ended with error code 0211
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: ADDTOBUFFER RT2KT00014 RT1 pf=/usr/sap/trans/bin/T
Return code: 0211
Error text: no info about transport request found
Request: RT2KT00014
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.
After this I have tried to add the transports to the buffer at the OS level using the command
./tp pf=TPPARAM addtobuffer "RT2KT00014" RT1 U18 by going to the folder
/usr/sap/trans/bin
But it says that the tp is not found.
I have also checked the permissions for the TRANS folder, it has full access i.e 777
This is where i am struck, and the client has to be imported asap as the requirement for the SUPPORT TEAM is very urgent.
We are on AIX, Oracle 10G and ECC6
Thanks and regards
Harry

Dear Imtiaz,
Thanks for your quick fire reply...
The link helped me but it could not resolve my issue..
Infact i found it my self that the transport requests had to be given full FILE PERMISSIONS at the OS level
I logged in as ROOT
and changed directory to /usr/sap/trans/cofile and gave the command
chmod 777 RT00014.RT2 and
chmod 777 RX00014.RT2
and then went to STMS>SYSTEMS>Import View>Extras>Other requests--> Add ..
Here i added the request nos and then it added up in the queue and then i started the import.
Anyway thank you very for your reply..
Awareded points to you.
Thanks and regards
Harry...

Transport control program tp ended with error code 0203

when i import queue and transport queue from dev to prd ,error show:
Transport control program tp ended with error code 0203
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: IMPORT DEVK900298 P01 clientP01 U0 pf=/usr/sap/tra
Return code: 0203
Error text: wrong syntax in tp call
Request: DEVK900298
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.

Dear Allen,
The transport control program tp collects all return codes that occur when a tp command is executed. From all of these single return codes, a combined return code is calculated that tp outputs as a result at the end the command. During an import, for example, all return codes for individual import steps are handled. If a special return code does not occur, then the combined return code at the end is the maximum of individual return codes that occur. In addition to the value of the return code, tp also gives a short description of this return code. You can display this short description using the command explainrc.
Normally, all return codes that occur originate from individual transport steps. Since these individual return codes can only have the following values 0, 4, 6, 8, 12, 13, 14, 16, the combined return code also has one of these values. However, if a general error occurs, a single return code over 200 is generated. For example, this could arise if tp cannot establish a connection to the database. The maximum return code for all single transport steps is output in a separate message before specifying the combined returned code. In this case, the combined return code is always the return code of the general error message.
<b>tp Commands:</b>
tp addtobuffer <request> <sapsid>
As of Release 4.6A, an explicit addtobuffer command leaves the position of the entry unchanged, if the relevant transport request is already in the buffer. Only the status of the entry is changed:
Unconditional modes appearing in the command line are added to the unconditional modes in the buffer.
All the steps of the entry are re-initialized.
If the entry found is not an initial entry, the import step for the command file is set to *4000 .
Before you call this command and its options, consider the effects of changing the import sequence.
tp cleanbuffer <sapsid>
This deletes successfully imported change requests from the list of requests that are marked for import into the SAP System <SAPSID>. This function is contained in the commands tp import all <sapsid> and tp put <sapsid> .
tp delfrombuffer <request> <sapsid>
If the specified request is marked for import into the specified SAP System, this flag is deleted from the import list.
Before you call this command, consider the effects of changing the import sequence.
As of Release 4.6A: If a transport request was only partially imported, you can delete this type of transport request from the buffer. However, if a deleted transport request is placed in the buffer (without having been initially or completely imported), the attributes of the old entry are reactivated. This means the return codes, the unconditional modes and tags of the deleted entry appear in the new entry.
tp delstopmark <sapsid>
If the list of requests marked for import into the specified SAP System contains a STOP mark, the mark is deleted.
tp export <request>
This exports the complete request from the source system. This command starts the export of a request from the operating system level. Only use this command in exceptional cases. The SAP System uses the command expwbo to release requests from CTS transactions.
tp reformatbuffer <sapsid> [options]
This automatically reformats the entire buffer.
As of Release 4.5A, there are 2 different formats for buffer entries. (As of Release 4.5A, tp can work with both formats, and with a puffer containing heterogeneous entries. As of Release 4.6A, tp can work with 3 formats.)
However, in certain cases entries with the old formatting have to be reformatted during the normal run of tp . In this case, the entire buffer is automatically reformatted.
If you use the options downtorelease and Iagree for command reformatbuffer , you can format the buffer so that its formatting is compatible with an older release:
Option downtorelease <Release>
The command reformatbuffer with this option formats the buffer so that the formatting corresponds to the one used in an old release. This is necessary if tp writes buffer entries to the buffer of another system, but uses a buffer format that the transport control programs does not understand in this system.
Since older formats cannot store the same amount of information as the newer ones, some information contained in the original buffer may not be stored in the unformatted buffer. This may lead to data loss.
To avoid data loss, the original buffer is stored. In addition, you have the following functions:
Displaying the unformatted buffer (using showbuffer <SID> )
Displaying the original buffer (using showbuffer buffer=<SID>SAV )
Accepting the unformatted buffer (using reformatbuffer and the option Iagree yes )
Resetting the changes (using reformatpuffer and the option Iagree no )
If you call reformatpuffer using downtorelease , tp displays in detail if information was lost by reformatting, and what that information was. tp also names the commands that is has to execute to accept or reject the changes.
If you use the option downtorelease , you must also specify the option Iagree with yes or no . You cannot use the transport system until you decide to accept or reject the changes.
Option Iagree
Here are the following values for this option:
yes ( true )
Accept the change made by tp reformatbuffer <SID> downtorelease <rel>
In this case, tp deleted the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
no ( false )
Reject the change made by tp reformatbuffer <SID> downtorelease <rel> In this case, tp copies the backup of the original buffer back and deletes the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
tp setstopmark <sapsid>
A special STOP mark is added to the list of requests registered for import into the specified SAP System. The commands tp import all <sapsid> and tp put <sapsid> only process the requests in front of this stop mark.
If there is no stop mark, it is automatically generated by the commands
tp import all <sapsid> and tp put <sapsid> .
When all the requests in front of the stop mark have been imported successfully, at the end of all the calls the related marks and the mark itself are deleted.
A STOP mark can only be placed at the end of the change requests that have already been marked. In addition, it can only be set if no other mark of the same kind already exists.
tp showparams <sapsid>
This tp function displays which values the individual parameters of the transport profile have for the current SAP System.
tp verse <request>
This creates versions of the objects in the specified request. This transport step is contained in command export .
As of Release 4.5A, more actions that prepare the export are performed in this step.
Thanks and Regards,
Naveen.

Tp ended with error code 0247 - addtobuffer has problems with data- and/or

Hello Experts,
If you give some idea, it will be greatly appreciated.
This transported issue started coming after power outage, sap system went hard shutdown.
Then we brought up the system. Before that , we do not have this transport issue.
our TMS landscape is
DEV QA-PRD
SED-SEQSEP
DEV is having the TMS domain controller.
FYI:
*At OS level, when we do scp command using root user, it is fine for any TR.
In STMS, while adding TR in SEQ(QA system), we are getting error like this.
Error:
Transport control program tp ended with error code 0247
     Message no. XT200
Diagnosis
     An error occurred when executing a tp command.
       Command:        ADDTOBUFFER SEDK906339 SEQ client010 pf=/us
       Return code:    0247
       Error text:     addtobuffer has problems with data- and/or
       Request:        SEDK906339
System Response
     The function terminates.
Procedure
     Correct the error and execute the command again if necessary.
This is tp version 372.04.71 (release 700, unicode enabled)
Addtobuffer failed for SEDK906339.
Neither datafile nor cofile exist (cofile may also be corrupted).
standard output from tp and from tools called by tp:
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0247

when we do scp using sm69,
SEDADM@DEVSYS:/usr/sap/trans/cofiles/K906339.SED SEQADM@QASYS:/usr/sap/trans/cofiles/.
it throws the error like below,
Host key verification failed.
                                                                                External program terminated with exit code 1
Thanks
Praba

CC app manager update failed with error code 50 after reaching about 35%

Trying to update the CC app manager. The update is always very slow (I have ATT DSL, lowest level) and I usually terminate it after an hour or so. Today I let it run and it failed with error code 50 after reaching about 35%. Any ideas?

Update to my original post. I read through some of the suggestions that I found in other threads for fixing this problem, and it appears that this has been an ongoing issue. Numerous fixes have been suggested, some very convoluted, difficult, and involved, including those that came from the customer support folks. I passed on those as this should be something simple. How Adobe manages to let updating of their own software turn into an ongoing problem is beyond me and sort of defeats the purpose of subscribing. I then noticed that a simple fix had been suggested a few times, so I tried that.
The user suggested fix that worked for me was:
1) Restarted computer (Asus Windows 7 i3 machine for me) in Safe Mode with Networking. Logged into my separate Admin account just in case.
2) Started the creative cloud desktop app.
3) The app said it needed to be updated. I hit the update button.
4) Update started and proceeded slowly as it had in many previous failed attempts (I have ATT DSL at the slowest level, but it is not dial-up). Within about 30 min, the update succeeded.
5) Restarted computer in normal mode.
6) The creative cloud desktop app now did not say it needs to be updated, and I can update my other apps normally. Have not updated LR or PS yet, but plan to try. If that fails, I may try doing it in the Safe Mode with Networking.
So, that was relatively painless and much much simpler than many of the other suggestions I saw. Do not know if it will work for everyone, but I wanted to post the fix that worked for me. Thank you very much to the 2 or 3 users who had suggested this fix earlier (sorry, I did not write down your IDs, but the threads can be found by searching for creative cloud desktop update fail error code 50). Hope this saves some people a lot of time.

Windows.Launch contract failed with error: The app didn't start..

We have installed windows 8 Prof X64 Edition; none of the Metro apps are not getting launched; the system is added in domain, the event viewer has the below information for one of the app.
Event Under: Applications
App microsoft.windowscommunicationsapps_8wekyb3d8bbwe!Microsoft.WindowsLive.Chat did not launch within its allotted time.
Event Under: AppHost
The App Host has encountered an unexpected error and will terminate. The error is 0x8007000E.
Event Under: Microsoft-Windows-TWinUI/Operational
Activation of the app microsoft.windowscommunicationsapps_8wekyb3d8bbwe!Microsoft.WindowsLive.Chat for the Windows.Launch contract failed with error: The app didn't start..
Regards Ajinkya Ghare MCITP-Server Administrator | MCTS

Hi,
Try to put a machine disjoin the domain to see if the same issue occurs.
Sometimes the Windows 8 machines cannot use metro app once join the domain, you can try this method:
1- Open "Local Group Policy Editor"
2-Navigate to "Computer Configuration - Administrative Templates - Network Isolation"
3- Open "Internet Proxy Servers for Metro Style Apps" and set the value to your proxy server address like 172.16.0.1:8080.
Regards,
Leo
Huang
Leo Huang
TechNet Community Support

Job RDDEXECL terminated with error.

Hi!
I am facing with hanging SPAM error in phase IMPORT_PROPER (patch of SAPKB70013 - SAPKB70016).
The SPAM patch terminates after a few sec. in DDIC activation action.
I have looked into log file and founded folllowing:
The job RDDEXECL terminated with error.
The reason seems to be sysntax error in program "CL_PROXY_SERVICE=======CP".
Futhermore I could detect that table SI_WD_FIRST_MAIN_SCREEN cannot be activated.
Can some one help me to solve this problem?
Of great interest was the following:
rescedule possibilities of job RDDEEXECL in order to contibue patch
start of SPAM or tp-commando by ignoring this error
Any helpful information will be very appreciated!
Holger

What do you mean with reimport?
I tried for almost 100 times to restart the import.

Rwcli60 terminate with errors

Similar Messages

Maybe you are looking for