Application returned an unexpected return code 1632 - MDT 2012

Hi,
I am getting the following error while installing Adobe reader, office 2010 only in few PC's.
applicatio adobe reader x1 returned an unexpected return code 1632
applicatio MS office 2010 returned an unexpected return code 1632
can any help on this.
Please note that the above mentioned problem comes only in some PC's.
D. Sendil Kumar

http://support.microsoft.com/kb/290158/en-us
ERROR_INSTALL_TEMP_
UNWRITABLE              1632   The temp folder is either full or
                                inaccessible. Verify that the temp folder
                                exists and that you can write to it.
Check the MSI installation logs. Whenever I install *.msi packages in MDT I turn on logging:
Msiexec.exe /qb- /l*vx %LogPath%\<file>.log REBOOT=ReallySuppress UILevel=67 ALLUSERS=2 /i <File>.msi
http://keithga.wordpress.com/2013/09/04/application-installation-and-packaging-via-mdt-and-sccm/
Keith Garner - keithga.wordpress.com

Similar Messages

Couldn't verify 'C:\Windows\ccmsetup\ccmsetup.cab' authenticode signature. Return code 0x80096001 - SCCM 2012 R2 Client Deployment

Hi All,
I installed SCCM 2012 R2 one primary site from one of our customer & using SQL 2012 SP1 DB at the back-end.
Facing Issues while deploying agent from one of our client machine - OS - window 7 Professional Sp1:
==========[ ccmsetup started in process 3828 ]==========
ccmsetup 25-02-2014 02:20:37 PM
284 (0x011C)
Running on platform X86 ccmsetup
25-02-2014 02:20:37 PM 284 (0x011C)
Updated security on object C:\Windows\ccmsetup\cache\.
ccmsetup 25-02-2014 02:20:37 PM
284 (0x011C)
Launch from folder C:\Windows\ccmsetup\ ccmsetup
25-02-2014 02:20:37 PM 284 (0x011C)
CcmSetup version: 5.0.7958.1000 ccmsetup
25-02-2014 02:20:37 PM 284 (0x011C)
Successfully started the ccmsetup service ccmsetup
25-02-2014 02:20:37 PM 332 (0x014C)
In ServiceMain ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist.
ccmsetup 25-02-2014 02:20:37 PM
332 (0x014C)
CcmSetup is exiting with return code 0 ccmsetup
25-02-2014 02:20:37 PM 332 (0x014C)
Running on 'Microsoft Windows 7 Professional ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice "/config:C:\Windows\ccmsetup\MobileClientUnicode.tcf" "/RetryWinTask:1"
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required.
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice "/config:C:\Windows\ccmsetup\MobileClientUnicode.tcf" "/RetryWinTask:1"
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
SslState value: 224 ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
CCMHTTPPORT: 80 ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
CCMHTTPSPORT: 443 ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
CCMHTTPSSTATE: 480 ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
CCMHTTPSCERTNAME: ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
FSP: SCCM.MYDOMAIN.COM ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
CCMCERTISSUERS: CN=MYDOMAIN-CA-CA; DC=MYDOMAIN; DC=COM
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
CCMFIRSTCERT: 1 ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
Config file: C:\Windows\ccmsetup\MobileClientUnicode.tcf
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Retry time: 10 minute(s)
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
MSI log file: C:\Windows\ccmsetup\Logs\client.msi.log
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
MSI properties: INSTALL="ALL" SMSSITECODE="PRI" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="480" FSP="SCCM.MYDOMAIN.COM" CCMCERTISSUERS="CN=MYDOMAIN-CA-CA; DC=MYDOMAIN; DC=COM"
CCMFIRSTCERT="1" ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
Source List: ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
\\SCCM.MYDOMAIN.COM\SMSClient
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
\\SCCMDMZ.MYDOMAIN.COM\SMSClient
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
\\SCCM.MYDOMAIN.COM\SMSClient
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
\\SCCMDMZ.MYDOMAIN.COM\SMSClient
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
MPs: ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
SCCM.MYDOMAIN.COM
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
No version of the client is currently detected.
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist.
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Attempting #1 retry. Max 5 retries. ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
Updated security on object C:\Windows\ccmsetup\.
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Sending Fallback Status Point message to 'SCCM.MYDOMAIN.COM', STATEID='100'.
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Failed to get client version for sending messages to FSP. Error 0x8004100e
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Params to send FSP message '5.0.7958.1000 Deployment '
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Request failed: 500 Internal Server Error
FSPStateMessage
25-02-2014 02:20:37 PM 1480 (0x05C8)
Running as user "SYSTEM" ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
Detected 69650 MB free disk space on system drive.
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Checking Write Filter Status. ccmsetup
25-02-2014 02:20:37 PM 1480 (0x05C8)
This is not a supported write filter device. We are not in a write filter maintenance mode.
ccmsetup 25-02-2014 02:20:37 PM
1480 (0x05C8)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=PRI))'
ccmsetup 25-02-2014 02:20:38 PM
1480 (0x05C8)
OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=MYDOMAIN-CA-CA;
DC=MYDOMAIN; DC=COM</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F2308201DAA00302010202105F02416299E5D1BC44A2DBB2F1CFDE39300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3134303130363037333732365A180F32313133313231343037333732365A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100B82EF14C5EEB69D726A3E24B3A2248ACC67667E2D4A4021792169437C5C2A03A35649F0FA3D01DC7FF3BB8668C30662B322A73562FA54EE19DF6A0533EBE895F0CA833E375CA2B8298C59C2372B05A61AF1F41360ED700508678AE2A4321F99DCE7C42139E9690009017A69568D59D2480E45EE724EF902757B66ACE24A8C1705B6628863F7C6DD9140B466F36FCB8FA891AF9F01BC1C94093EDE814D711ACB13F7067F69AD970DAF03AA58E1E5C943582B4B5D0B49BB99E7C1E51D76661BE0A4DEBA2FDF6121C7211A33E8E3092F9CFBECCD0EB9BDE2E1E83EB98F57DD905226B1693D1EEFDE826593D5538902C5292B119303CA02D41B11E762BCC1AF118630203010001A33A303830200603551D110419301782155343434D2E68656C70616765696E6469612E6F726730140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100839328B4017E3317BD05E6D35022AFC1C0AA91E7B1EA838143B257BDAF9780B3C582547891FE4361E5D789B269C4E49CFDAA2E38E85AE7252980F392EC7378F482001909E92F752A6292AFF0FE9E9634B915A70CF3E5DECE35B272630B6CAF5A73FFF4928F847B63A35DF05E2B41F05AAD7C436B166AF6C157789FAA084BB5A38E0592F65F5C6D29588DF6B79B6A51AB6D6D2985FDB346FA88FDD36EE0DAF53603F2036371F7D6866F49A96AB9BE3ED757743033C7C3F97FDF772F699F38DB52775BD0B0090381F89B3D8AD2A49DC653991BCE031517F6BA61FCED45E23139CA01E32F61E865DBA2F5FF0E30403BFC7FEDE1892EE890B765C38FE2F06448FC58</SiteSigningCert></SecurityConfiguration><RootSiteCode>PRI</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=PRI</CommandLine> </CCM><FSP> <FSPServer>SCCM.MYDOMAIN.COM</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain
Value="MYDOMAIN.COM" /><Forest Value="MYDOMAIN.COM" /></ClientOperationalSettings>'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown.
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
The MP name retrieved is 'SCCM.MYDOMAIN.COM' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
MP 'SCCM.MYDOMAIN.COM' is compatible ccmsetup
25-02-2014 02:20:39 PM 1480 (0x05C8)
Retrieved 1 MP records from AD for site 'PRI'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Retrived site version '5.00.7958.1000' from AD for site 'PRI'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
SiteCode: PRI ccmsetup
25-02-2014 02:20:39 PM 1480 (0x05C8)
SiteVersion: 5.00.7958.1000
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again.
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Only one MP SCCM.MYDOMAIN.COM is specified. Use it.
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Searching for DP locations from MP(s)... ccmsetup
25-02-2014 02:20:39 PM 1480 (0x05C8)
Current AD site of machine is Default-First-Site
LocationServices 25-02-2014 02:20:39 PM
1480 (0x05C8)
Local Machine is joined to an AD domain LocationServices
25-02-2014 02:20:39 PM 1480 (0x05C8)
Current AD forest name is MYDOMAIN.COM, domain name is MYDOMAIN.COM
LocationServices 25-02-2014 02:20:39 PM
1480 (0x05C8)
DhcpGetOriginalSubnetMask entry point is supported.
LocationServices 25-02-2014 02:20:39 PM
1480 (0x05C8)
Begin checking Alternate Network Configuration
LocationServices 25-02-2014 02:20:39 PM
1480 (0x05C8)
Finished checking Alternate Network Configuration
LocationServices 25-02-2014 02:20:39 PM
1480 (0x05C8)
Adapter {95A6D3CE-4F28-4E55-A29A-FF3F1A317C61} is DHCP enabled. Checking quarantine status.
LocationServices 25-02-2014 02:20:39 PM
1480 (0x05C8)
Adapter {6024AB68-EB5E-4370-BD9E-8B2CEFE261A8} is DHCP enabled. Checking quarantine status.
LocationServices 25-02-2014 02:20:39 PM
1480 (0x05C8)
Sending message body '<ContentLocationRequest SchemaVersion="1.00">
<AssignedSite SiteCode="PRI"/>
<ClientPackage/>
<ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0"
UseInternetDP="0">
<ADSite Name="Default-First-Site"/>
<Forest Name="MYDOMAIN.COM"/>
<Domain Name="MYDOMAIN.COM"/>
<IPAddresses>
<IPAddress SubnetAddress="10.0.0.0" Address="10.10.10.192"/>
</IPAddresses>
</ClientLocationInfo>
</ContentLocationRequest>
' ccmsetup
25-02-2014 02:20:39 PM 1480 (0x05C8)
Sending message header '<Msg SchemaVersion="1.1"><ID>{F6331322-941A-4E44-974F-A755B1B016A4}</ID><SourceHost>POOJASETHI</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:POOJASETHI:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>SCCM.MYDOMAIN.COM</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2014-02-25T08:50:39Z</SentTime><Body
Type="ByteRange" Offset="0" Length="1126"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
CCM_POST 'HTTP://SCCM.MYDOMAIN.COM/ccm_system/request'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Content boundary is '--aAbBcCdDv1234567890VxXyYzZ'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Received header '<Msg SchemaVersion="1.1">
<ID>{14ADB6F1-95C1-4EEF-B8BA-16CD020ACFCF}</ID>
<SourceID>GUID:526CE573-6351-407E-AC2A-2C3927979AD9</SourceID>
<SourceHost>SCCM</SourceHost>
<TargetAddress>direct:POOJASETHI:LS_ReplyLocations</TargetAddress>
<ReplyTo>MP_LocationManager</ReplyTo>
<CorrelationID>{00000000-0000-0000-0000-000000000000}</CorrelationID>
<Priority>3</Priority>
<Timeout>600</Timeout>
<Capabilities><Property Name="SSL" Version="1"/></Capabilities><ReplyCapabilities><AllowRegistrationReset>direct:SCCM:ClientRegistration</AllowRegistrationReset></ReplyCapabilities><TargetHost>POOJASETHI</TargetHost><TargetEndpoint>LS_ReplyLocations</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>https</Protocol><SentTime>2014-02-25T08:50:39Z</SentTime><Body
Type="ByteRange" Offset="0" Length="3494"/><Hooks><Hook3 Name="zlib-compress"/><Hook Name="authenticate"><Property Name="Signature">3082018C06092A864886F70D010702A082017D30820179020101310B300906052B0E03021A0500300B06092A864886F70D01070131820158308201540201013031301D310D300B060355040313045343434D310C300A06035504031303534D530210165D06FED03B9DB94FE763D9360D9AC5300906052B0E03021A0500300D06092A864886F70D010101050004820100501708FC116FFF030AF508AA81D93086786D1E088F8729906DBFC42B6239C511CF34CB5AA9008B4356FA2D314EF43E85D8555A7D185888870EDC7A3D3700AA974B5246D59D9CC72614845768082F3AB463F2F92025D4505C1E8CBF243F6245E224EAE31091A18C9B0ADE6DEF3500DC599B04BDCE176EA49159D2947C84328F7BD2F0F6C93271F72F5826ED6717C19B5C36CDA9E1B02F9810F1D6B91659E9FD5DB25AFE155ECF86A3535A28ADE0B53505C20E69FB4A6406904299D60098B9756180BA3B6D742E3483F9FE0A45A8EC1611565377D8E6788E51057F7082339BF67771BAFC985C56784CE756BCB39C59E77071BCEE7352500B961D4509FC3EFE3828</Property><Property
Name="AuthSenderMachine">SCCM;SCCM.MYDOMAIN.COM;</Property><Property Name="MPSiteCode">PRI</Property></Hook></Hooks><Payload Type="inline"/></Msg>'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="16777216"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="PRI" MasterSiteCode="PRI"
SiteLocality="LOCAL" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><URL Name="http://SCCM.MYDOMAIN.COM/SMS_DP_SMSPKG$/PRI00003" Signature="http://SCCM.MYDOMAIN.COM/SMS_DP_SMSSIG$/PRI00003"/><ADSite
Name="Default-First-Site"/><IPSubnets><IPSubnet Address="10.0.0.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>7958</Version><Capabilities SchemaVersion="1.0"><Property
Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>SCCM.MYDOMAIN.COM</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="1"/><Locality>LOCAL</Locality></LocationRecord><LocationRecord><URL
Name="http://SCCMDMZ.MYDOMAIN.COM/SMS_DP_SMSPKG$/PRI00003" Signature="http://SCCMDMZ.MYDOMAIN.COM/SMS_DP_SMSSIG$/PRI00003"/><ADSite Name="Default-First-Site"/><IPSubnets><IPSubnet Address="172.16.10.0"/><IPSubnet
Address=""/></IPSubnets><Metric Value=""/><Version>7958</Version><Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>SCCMDMZ.MYDOMAIN.COM</ServerRemoteName><DPType>SERVER</DPType><Windows
Trust="1"/><Locality>FALLBACK</Locality></LocationRecord></LocationRecords></Site></Sites><ClientPackage FullPackageID="PRI00003" FullPackageVersion="1" FullPackageHash="BFC11E099E8F451107B43E0DBEFD93B01DB2D6453DA74F8A2CB94B73D676C1CD"
MinimumClientVersion="5.00.7958.1000" RandomizeMaxDays="7" ProgramEnabled="false" LastModifiedTime="30354761;897103744" SiteVersionMatch="true" SiteVersion="5.00.7958.1000" EnablePeerCache="true"/><RelatedContentIDs/></ContentLocationReply>'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Found local location 'http://SCCM.MYDOMAIN.COM/SMS_DP_SMSPKG$/PRI00003'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Found remote location 'http://SCCMDMZ.MYDOMAIN.COM/SMS_DP_SMSPKG$/PRI00003'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Discovered 1 local DP locations. ccmsetup
25-02-2014 02:20:39 PM 1480 (0x05C8)
PROPFIND 'http://SCCM.MYDOMAIN.COM/SMS_DP_SMSPKG$/PRI00003'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Using DP location http://SCCM.MYDOMAIN.COM/SMS_DP_SMSPKG$/PRI00003
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
GET 'http://SCCM.MYDOMAIN.COM/SMS_DP_SMSPKG$/PRI00003/ccmsetup.cab'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Couldn't verify 'C:\Windows\ccmsetup\ccmsetup.cab' authenticode signature. Return code 0x80096001
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Sending Fallback Status Point message to 'SCCM.MYDOMAIN.COM', STATEID='316'.
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Failed to get client version for sending messages to FSP. Error 0x8004100e
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Params to send FSP message '5.0.7958.1000 Deployment Error 0x80004005. Pre-req file name: C:\Windows\ccmsetup\ccmsetup.cab'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Request failed: 500 Internal Server Error
FSPStateMessage
25-02-2014 02:20:39 PM
1480 (0x05C8)
Failed to extract manifest cab file with error 0x80004005. Try next location.
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Enumerated all 1 local DP locations but none of them is good. Fallback to MP.
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
GET 'HTTP://SCCM.MYDOMAIN.COM/CCM_Client/ccmsetup.cab'
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
Couldn't verify 'C:\Windows\ccmsetup\ccmsetup.cab' authenticode signature. Return code 0x80096001
ccmsetup 25-02-2014 02:20:39 PM
1480 (0x05C8)
CcmSetup failed with error code 0x80004005
ccmsetup 25-02-2014 02:20:39 PM
284 (0x011C)
Please let me know any solution or workaround for this
Thanks Rahul$

Hi,
The client cannot verify the signature of ccmsetup.cab. I suggest you check the Trusted Root Certification Authorities in certificate store on the client to see whether a certificate is missing.
Try to enable verbose logging for SCCM client installation. Then check the log to see whether there are some useful information.(http://technet.microsoft.com/en-us/library/gg699356.aspx)
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Return code meanings of livecache applications

Hello,
Can somebody please let me know where can I find the docs. containing livecache application return codes (which can be seen as ( /n/sapapo/om01 ).
As far as I know we can see them via /sapapo/om10
But which user action is required is not mentioned there
Can somebody throw light on this.
Best Regards,
Prashant

Hello Prashant,
-> As SAP customer you have the option to create the OSS ticket, therefore we could
     logon to your system via OSS and take a look closer on the reported issue.
-> Using the /n/sapapo/om01 you could display LCA Trace File.
     The LCA trace file is written for the LCA developers and LCA development
     support to help with the analysis of the liveCache application issues.
     Therefore some of the LCA/liveCache errors need the LCA/liveCache development/support
     involved . And the user < customer action > has to be : open the OSS ticket to the component
    'BC-DB-LCA', provide the application scenario to reproduce the issue if you can,
     let the LCA support to logon and check your systems & logs.
-> What errors did you see in the LCA trace? What LCA routine failed?
      Did you see the LCA RC in the application log?
      As you already know to display Meaning of Return Code of the LCA routine => use the
      transaction /SAPAPO/OM10.
-> If the LCA application checked the LCA routine RC after the LCA routine run and the LCA routine
     code is critical => you could see the message of the 'Message class' /sapapo/om* < it's dependent of what application you are running >. For example, class /SAPAPO/OM_TS is for Messages for OM
    Management of Time Series Objects. You could run /nse91 transaction & display the message by
    the 'Message class' and known number, or you could display all message by the 'Message class' .
    Some messages are 'self-explained' < The short text describes the problem sufficiently > and another
    messages have the long text, which you could display & check the 'Procedure' section.
-> You could review the documented often asked LCA < COM > RCs at Wiki :
         https://www.sdn.sap.com/irj/sdn/wiki < All >
                         -> Supply Chain Management -> FAQ -> COM Error FAQ
    Thank you and best regards, Natalia Khlopina

MDT application install returns unexpected return code: 16

Hi, I'm using MDT 2013 (Version: 6.2.5019.0) and deploying Server 2012 R2 Standard.
The deployment runs fine, but an application install fails. Here is the relevant content from the BDD.LOG file:
Run Command: \\MDT\Share$\Tools\X64\bddrun.exe robocopy \\MDT\Share$\BuildFiles "C:" /MIR /W:5 /R:3 /LOG \\MDT\Share$\LOGS
ZTI installing application
About to run command: \\MDT\Share$\Tools\X64\bddrun.exe robocopy \\MDT\Share$\BuildFiles "C:" /MIR /W:5 /R:3 /LOG \\MDT\Share$\LOGS
Command has been started (process ID 2896)
Return code from command = 16
Application Copy Files 1.0 returned an unexpected return code: 16
Property InstalledApplications001 is now = {9d0ba76d-96f9-4f4f-a6b8-4b1d0ffd2007}
ZTIApplications processing completed successfully.
I've searched for the error code 16 but can't find any results. What does it mean?
Cheers.

I think that I may have found the solution. On different site I've found the robocopy exit codes and 16 is listed there as "Robocopy
did not copy any files. Check the command line parameters and verify that Robocopy has enough rights to write to the destination folder."
I guess that I need to alter the destination folder to something other than the root of C:\
I'll respond with the result later.
UPDATE: Yep, that was the problem.

MDT capture warning: Unexpected return code while re-arming office 2010, RC= -1073425657

Greetings,
I have a base image I have created with an MDT task sequence, than I am then immediately capturing with another MDT task sequence (the capture sequence is basically the default). After capture, I get 0 errors, 1 warning: "Unexpected return code
while re-arming office 2010, RC= -1073425657".
I am capturing immedaitely after the base image build, and even more strangely, even with Office 2010 removed from my base build, I STILL get this warning! Office isn't even on there anymore (I verified before capture just to double check).
Not sure how or why this is happening - or more importantly, should I care? I've deployed a couple of machines using this image, and both Office and Windows show as activated. Can this safely be ignored, or if not... what is the fix?
Thanks in advance!

Freddie,
Please read your own post again, can you tie the knots together, because your phrasing is going crazy!?!
However, if using the sysprep step from within a MDT task sequence, please scroll through the ZTISysprep.wsf to find that not only the machine will be sysprepped, but also Office 2010 will be automatically re-armed, this is provided in the script already,
so no need to run it on your own.
Ok how do i undo that because thatswhy the message appears to many rearms...
If a machine is domain joined, it will not sysprep and capture. Also I wouldn't sysprep and capture an already sysprepped and captured image again (based on gut feeling) and as always check your logfiles, they can reveal what is going on here.
The machine is not domain joined in the Vm. And i do not sysprep and capture twice.Which logfiles exactly to see?
If this post is helpful please click "Mark for answer", thanks! Kind regards
freddie

Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)

Hi all,
I have TFS2012 and run several projects.
We encounterwed with such an error while using Build server.
Overall Build Process
Initial Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
00:00
Get the Build
00:00
Update Build Number
Initial Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Final Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Result = Ephone_DIT_Deploy_20150424.1
01:56
Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
Initial Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
00:00
Get the Build Directory
Initial Property Values
Result = d:\temp\217\CTI\Ephone_DIT_Deploy
01:53
If Not String.IsNullOrEmpty(ConfigurationFolderPath)
Initial Property Values
Condition = True
01:53
Run TfsBuild for Configuration Folder
Initial Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp"
00:08
Getting sources
00:02
Labeling sources
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.
00:19
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:10
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
MSBuild Log File
00:08
Generating list of changesets
00:20
Built Skins\SkinEPhone.cs for default targets.
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
00:03
Creating work item
Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Final Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
Final Property Values
Condition = True
Final Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
Final Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
Please have a look and guide where to find a problem
Thanks ahead

Hi Hooi,
I'd like to know whether you can build successfully in your local machine with MSBuild. You have to build succeed with MSBuild beore you can build with TFS Build since TFS build use MSBuild as its default compiler.
From the error message, you might build with wrong platform for your project. Please check if the build platfrom is proper. If you have customization of your build process template, it would be better to elaborate the reproduce steps and customization details.
Best regards,

Error while calling COM routines via application prog(return code 1028533-)

Hello Expert,
In Interactive Demand Planning ( /SAPAPO/SDP94 ), when I'm trying to load data in a planning book , error
'Error while calling COM routines via application program (return code 1028533-)' is encountered.
In my selection id, i have only two locations....there is no material selection.
When I select the 1st location and load the data its getting loaded properly.....but when i select the 2nd location and try loading data ...the above error is coming.
I did run /SAPAPO/TS_LCM_CONS_CHECK but the problem persist.
Any advise to fix this issue would be much appreciated.
Thanks.
Tom

Hi Tom,
Please see if below exiting threads help you.
COM error 40134 in Interactive Planning on SCM 5.0 Support Pack SAPKY50011
Error for COM Routine application program (return code 40028)
Thukral

MDT 2012 Litetocuh Deployment Failed, Return Code = -2147467259 0x0004005

Here is what I have tried. I have tried recreating the DeploymentShare. Moved my Deployment Test Share to the standard 2008 Server running MDT 2012. I have setup a Win7 x64 box as the Deployment Manager. I am still getting the following error:
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Copy OEM files.
Incorrect function, (Error: 00000001; Source: Windows)
The execution of the group (Install has failed and the execution has been aborted. An action failed.
Operation abourted (Error: 80004004; Source Windows)
Failed to run the last action: Copy OEM files, Execution of task sequence failed.
Incorrect funtion. (Error: 00000001; Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Recreated the Image, Task Sequences, CS.ini and Boot.ini) Incorporated all OOB Drivers, Packages. Using
a USB 16Gb flash drive with LiteTouchx86.
List last time we tried to create a separate deployment share. Copy all the preexisting data from a working known good deployment share with images, task
sequence, cs.ini and all image files. Still getting the same issue.
Finally checked some of the Google, technet and forums for any assistance but non seem to do the trick.
I'm new to the process but have been working with a fellow tech who has been working with MDT for six months and he can not find the issue either.
Thanks for all your help up front.

Can you post your log files?
IT Support " Scripting Noob "

Error while calling COM routines via application program (return code 40028

Hi ,
When i am doing these steps i am getting the following error.
1.from SAP menu...Demand Planning>Planning>Interactive Demand planning
       2.after the transaction gets loaded...click on the 2nd button that is selection window from the left ALV menu..on the top.
        3.type the below
show - Material
APO Planning Version - K01
Material - 12345
4.Material 12345 will be loaded
5.Double click and i am getting ''error Error while calling COM routines via application program (return code 40028)''
Note : Observed that this is not happening everytime, but happening alternatively.
Can any one say what is the problem for Error.
Thanks
Gerard

Hello Gerard, Hello Krishna,
-> The liveCache application failed with COM error::
                               40028 Illegal timestamp in rough timegrid
More details about COM error 40028 you will see in TA /n/sapapo/om10
     -> Return code: 40028 -> execute ::
Invalid time stamp in the time buckets profile relation
( om_ts_tgrelinvalidstamp )
   < click on '?' mark >
-> Open an OSS message in accordance with SAP note 167280 if further help
     needed to solve the issue on your system.
Thank you and best regards, Natalia Khlopina

"Error for COM routine using application program (return code 40,020)"

Dear All,
Working on 4.1
We are getting the below error while loading the Data into planning book...
"Time Series has to be updated"
After this we updated the storage bucket profile and the fiscal year varient calender.
And after this we are trying to initialize the planning area..but getting the below error...
"Error for COM routine using application program (return code 40,020)"
So then we try to run the LCM CON check , but here also we are getting the below log...
"Inconsistent time series initialization horizons"
We teasted all the above in TEST system , but we are not facing any issue.
Plz plz help us to resolve the same.
Regards,
Rajesh Patil

Hello Rajesh,
COM error 40,020 generally indicates that no Time Series exists for
the characteristic combination that is being loaded or saved.
In certain cases it could be related to missing Time Series for aggregates.
Therefore, performing a consistency check for the relevant planning area by running the program
/SAPAPO/TS_LCM_CONS_CHECK is usually the first option. You could also check the relevant planning
object structure and any aggregates using the programs /SAPAPO/TS_PSTRU_TOOL and /SAPAPO/TS_PSTRU_CONS_CHECK.
Additionally, please make sure that the time series exists for the horizon for which data is to be loaded. Should all these not resolve the issue, the problem will be resolved by deinitializing & reinitializing the time series.
Please note that deinitializing of the the planning area will lead to data loss, so please take the backup of your data before you
deinitialize the planning area.
Hope this helps.
Regards,
Ade

Error for COM Routine application program (return code 40028)

Hi,
When we loading data in Planning Book ,we are getting below error
Error for COM Routine application program (return code 40028)

Hi,
Did you try checking your COM build? The COM communicates between your database and Livecache and fetches the data requested. The last time we had this, SAP recommended COM upgrade.

SCCM 2012 application run Powershell script and return codes

Hi,
I created an new application (imported as MSI) in SCCM 2012R2. After import I changed the deployment type installation program to run a Powershell script: powershell.exe -ExecutionPolicy Unrestricted -File "Install FactSet 2013 5I.ps1
My goal is to close some processes before installing the MSI. This works. But on a failure the application program also return code 0 (AppEnforce.log). Is it possible to pass the MSI return codes to SCCM.
Maybe anyone had the same or idea's to solve this? Thanks in advance.
Regards,
Peter
Powershell script code:
$ExitCode=0
Function
Stop-RunningApplication{
Param(
[parameter(Mandatory
=$true)]
[string]$ProcessName#
Specify process names separated by commas
# Split multiple processes on a comma and join with the regex operator '|' to perform "or" match against
multiple applications
$processName=$processName-split(",")
-join("|")
$process=Get-Process|Where{
$_.ProcessName
-match$processName}
|Stop-Process-Force
#Stop running processes
Stop-RunningApplication
-ProcessName"excel,outlook,fdsw32,marquee,POWERPNT,WINWORD"
#Install FactSet 2013 5I
$ExitCode
=(Start-Process".\FactSet_Setup_2013_5I_x644.msi"'/qn
FACTSET_CLOSE_PROCESSES=1 /l*v C:\Temp\InstFac20135I.log'-Wait-Passthru).ExitCode
Environment]::Exit($ExitCode)
Peter vd Bosch

It's really hard to tell from the code above because of the way it's listed, but are sure that even executes? I see at least one stray curly brace and a stray square bracket.
For the Start-Process cmdlet, have you tried without the -passthru parameter?
Also, using the actual parameters will make the code much more readable instead of relying on position.
Jason | http://blog.configmgrftw.com | @jasonsandys

Pass return code from Java application to a .bat file.

I have a .bat file which will execute a Java application. I want to pass the return code from the java application to the ".bat" file.
Could you please let me know, how can I accomplish this.

I tried that, but it doesn't return the value...
In my Java app, I had System.exit(returnCode) and in the '.bat' file
I have
@echo off
java <myApp>
set returnCd=%?%
echo %returnCd
and it didn't return any value. What should I specify in set returnCd=%?% instead of ?

Error for COM routine using application program (return code 40069)

Hi,
In our planning book, sometimes, when we change a value and save, we are getting a pop up with the message "Error for COM routine using application program (return code 40069)". When we click ok, the value in that cell is reset to the previous value.
I initially thought this is due to duplicate CVCs and ran the consistency checks, /SAPAPO/TS_LCM_CONS_CHECK and /SAPAPO/TS_PSTRU_CONS_CHECK. I found few and corrected them. Now even after correcting them, I am still getting this COM error.
I could not find any SAP notes on this.
I switched on the SQL trace in ST05 and executed the same operation to get the COM error.
I noticed this part of the trace that is unusual and I am guessing that is what the system is doing when I get the error.
Can somebody please explain me the meaning of this attached trace?
http://spreadsheets.google.com/pub?key=pMjKR_3qLaxblBDDPfRt6cw
what does the SIM_SIMSESSION_CONTROL do?
Does CALL USER.SAPTS_AGGMULT_TIMESERIES mean there are duplicate time series?
Thanks.

I may not be technical person but may be the following thread on SIMSESSION may help.
SIM Session
ST05 trace only gives DB level traces. It would not give you traces of things happening in Live Cache since there are stored DB procedures that are called for LC activity.
Did you do OSS search on "return code 40069" ? CHeck OSS note 863244. See if it is applicable.

"Error for COM routine using application program (return code 1028514-)"

Hello Experts,
We have one issue in SAP SAP SCM 5.10.
When we are accessing the SNP Planing book, Now a days every often we are getting kicked out of the Planning book
with the error message "Error for COM routine using application program (return code 1028514-)"
How to rectify this,..Please advice /suggest
Regards,
Ramesh

Sorry, I copy the content as below:
Error -28514
Version Not Found
You attempted to access an OMS version, the liveCache infrastructure to store a Simulation Version, which does not exist (any longer).
On a productive system this error should only occur in exceptional situations because liveCache checks whether the simulation exists beforehand and returns an Error 17831 if this is not the case.
Reasons (=exceptional situation) for an error -28514 are:
a transactional simulation (Simulation Version) is older than liveCache parameter MaxRetentionTime (default: 8 hours). In this case, the OMS version (more precisely: the corresponding consistent view) can be deleted (asynchronously) by liveCache and an error -28514 will occur if the application tries to use the transactional simulation again.
a transactional simulation (Simulation Version) is older than liveCache parameter MinRetentionTime (default: 1 hour) and the data area usage exceeds 90%. In this case, the OMS version (more precisely: the corresponding consistent view) can be deleted (asynchronously) by liveCache and an error -28514 will occur if the application tries to use the simulation again.
If liveCache deletes an OMS version due to one of the reasons above, a corresponding notice can be found in liveCache's knlmsg file (cyclically overwritten!).
Error -28833
Error -28833 ("Consistent view has been cancelled") occurs instead of an error -28514, if the an OMS version is deleted while a parallel liveCache call is still using this OMS version.
Malfunction Test
If this error occurs during LCAPPS internal malfunction tests, it indicates that the preceeding provoked exception has not been handled correctly. During the handling of the provoked exception the OMS version is dropped automatically. As the malfunction test program catches the exception which would normally lead to a shortdump, it either has to recreate the current simulation in liveCache or to ensure that it is not used any more.
Error 17831 does not occur in this situation, because the keyed object representing the simulation (OMS version) is not deleted along with the version and can therefore still be accessed.
Best Regards,
Ada

Application returned an unexpected return code 1632 - MDT 2012

Similar Messages

Maybe you are looking for