Application failed to return status record to ALE layer after Idoc procesed

Hi,
I am loading a full load to Product category (hierarchies) through process chain.
One of the load failed with the following error. The Idoc has status 51 in BW.
Can some suggest me the process for correcting this.
Thanks
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.

Hi
If this is standard code then you will have to write code to populate the status message in exit. But in case of custom code, the above mentioned solution is best (if coding logic is correct). I have given this solution to many queries and all worked.
Thanks
Anuraag

Similar Messages

Application document not psted status 51 in ALE/IDOC

Hi Gurus/Experts;
Status number : 51 Application document not psted.
I have configured ALE for distributing material master data. On the outbound side the status of every Idoc is sucess. But on the inbound side some of them are red stating error.
Outbound Side :
we05 t-code.
03 success.
Inbound Side:
we02 t-code.
51 Error.
when I execute the we02 t-code and
Expand Status Record 51
am getting error like : Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT
Please Give me some suggestion on this..
Thanks;
Ravi.

HI jayanth;
thanks for your replay.
we are almost 1 step ahead i think ...
plz suggest me the same...
those steps are very usefull and its cleard the step status type 51 error
now am getting error on inbound side when we execute we02 t-code.
status Error number 29.
Could not determine recipients for message type MATFET
Message no. B1003
Diagnosis
An IDoc of message type MATFET was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message type or deactivate distribution for these message types.
Thanks;
Ravi.

Application failed to return a video frame

This is no problem to me anymore, but if someone have this error appearing ir rendering process, I can share my solutions. I had to spent some week before I finalize my current project in Premiere Pro CS3. I manage to test all solutions, what people provide in different forums about this error message. I cannot say, that something of this is nuts, maybe there are different problems under this one error message.
1) first they say, that there should not be any gaps between you videos or sequences in timeline – not a single black frame
2) your audio should not be longer than video on timeline. same – not longer than a single frame
3) when you render, you should close all sequences ir timeline palette (they will not be deleted, just closed)
4) and this ir most important – you have to boot your system in 32bit, not 64! I'm working on MacOSX Snow Leo x64, and did render my movie only after I boot in 32bit. It could be solution for Win users, too. I have no idea about CS4 and CS5, bet my CS3 is not 64bit application.
Good luck!

Welcome to the forum, and thank you for posting your observations, and experiences.
I did this ARTICLE for the most likely cause of "Failure to Return Frame" error.
You also make an important note of the Duration of the Audio vs the Video. As the Video takes center-stage, having even a few Audio Units extra, means there is a gap in the Video. To keep this from happening, and to also address some other potential issues, I always end each Timeline with about 02 sec. of Black Video, and always end the Audio within that.
What I find odd, however, is that I have seen Timelines with many gaps, and they Transcode fine, yet have seen Timelines with one 1-Frame gap, that would yield the "Failure to Return Frame." Why the gaps are not 100% universal in shutting down Transcoding, is still a mystery.
Appreciated, and good luck,
Hunt

How to troubleshoot why some valid query values fail to return records

Post Author: Chas1048
CA Forum: General
I have an existing crystal 10 report that reports on an Oracle DB. Some of the valid prompt entries return a report others fail to return any records.
Does Crystal log errors anywhere? I have checked the table linking.

Forms 6i is an antique ... write your code to run on the server.
Multiple examples of how to loop through an array loaded with bulk collect can be found here.
http://www.morganslibrary.org/reference/array_processing.html
The main library page is:
http://www.morganslibrary.org/library.html

Return Status

Hi. Does anybody know where can I find what a Return Status means? I'm getting "Command Failed. Return Status = 1030100" while running an Esscmd.Thanks a lot. Diego.

##1030100 Cannot open file: [%s]look for message.txt in your Hyperion directory. (essbase/api/include)orhttp://www-3.ibm.com/software/data/db2/db2olap/v81docs/errmsgs/erhelp.htmwith hints on how to solve error.or if not listed then you can get an idea of the error category by errors range:http://www.essbase.com/doc/essbase-62/dbag/dtrbl.htm#14640Eric BelmonPartake [email protected]

Relation of ALE , EDI and idoc

HI
     what is relation of these ALE, EDI, IDOC , i know the definition of these , i want know ( while the transfer of sap to sap ALE tool is used ,) where this idoc is used ,
regards
shivaji

Hi Shivaji,
What is EDI?
Electronic Data Interchange
     The computer-to-computer electronic exchange of machine processable business documents in a standard format
     An electronic alternative to paper, fax, and phone-based transactions used by companies to communicate with one another
Purpose:
     Allows for better time management and relieves the entering of duplicate information while cutting down on discrepancies and human intervention.
     The Electronic Data Interchange component in Sales and Distribution consists of an Intermediate Document (IDoc) [Ext.] interface. You can use this interface to
     send messages (outbound processing) such as an order confirmation through Electronic Data Interchange (EDI)
     receive messages (inbound processing) such as a sales order through EDI
EDI:
     What?
     The technology of transmitting documents electronically
     Why?
     For Electronic Data Interchange between a company and trading partners
     How?
     By means of an electronic document - the IDoc
From the SAP side, the EDI interface is based on IDoc technology, which is independent of
EDI standards. All data is transferred in files between the R/3 System and the EDI subsystem.
Synchronous Remote Function Call (RFC) is implemented to define the time of transfer for a
file between the two systems. The following data can be transferred using the EDI interface:
Outbound Idocs: IDocs are transferred from the R/3 System to the EDI subsystem.
Inbound Idocs: IDocs are transferred from the EDI subsystem to the R/3 System.
Status report: The EDI subsystem sends a status report to the R/3 System on the progress of
the processing of the outbound Idoc.
Contents of IDOC
The data in every IDoc is exchanged between the SAP system and a subsystem in the following three record types, irrespective of the IDoc type:
     Control record (Table: EDIDC): Contains information about Sender and Receiver. There is only one control record per IDoc. It consists of
IDoc Number
Sender and Receiver information
IDoc Message Type* / Port.
IDoc Type / Direction / Current status / Partner No / Partner Type (Vendor/customer)
     Data record (Table: EDIDD): Contains the message to be exchanged between Sender and Receiver. An IDoc can contain multiple data records, as defined by the IDoc structure. Data records store application data such as purchase order / sales order header information, sales order details like sales doc #, Material / Qty and other relevant information.
     Status record (Table: EDIDS): Contains Status of IDoc at various stages, during the transmission of IDoc between Sender and Receiver. Multiple status records are usually attached to an IDoc. Status records are attached to an IDoc throughout the process like status code, date and time at every stage
Know Me
Basic Type: The form of IDOC type that is originally created in the system. Like ORDERS01 is a basic type IDOC for order messages. It is using the basic types only you would be able to enhance them to suit new requirements within the same IDOC structure. Any enhancement to the basic type IDOC will produce an Extension IDOC that would be more or less similar to the basic type with some new additions (of segments or fields). Here, I would go on to say that IDOC type and Basic type is the same thing that would be referred to interchangeably.
Message type: Again, obvious from the name, its the message that is being conveyed. A message type is assigned to the Basic type. Here, logical messages are assigned to the basic type to reflect a business message being transacted. For example, ORDERS is the message type for a purchase order sent by buyer to vendor. The use of which Basic type in this message will differ from buyer to vendor. Basic types used for ORDERS are ORDERS01/02/ etc...Also, one may come up with a custom built IDOC type (or basic type as you can say)...But it is essential to associate a message type with a basic type IDOC. This feature will enable the same IDOC type to be used for a related message. For example : ORDERS01 can be used for message ORDERS for posting a order, the same IDOC can be associated with message ORDCHG to indicate that the message is an order change and so the processing of this IDOC will change accordingly.
IDoc Type:
     Defines the structure of data records
      IDoc Type is used to understand the message in string form available in the data records.
      IDoc type is version dependent i.e an Idoc type can be used only in versions in and above the version in which IDoc is released.
      Transaction WE30 is used to define and release IDoc Types
      Newly created Idoc is a BASIC IDoc and modifications
             (Additions of segments) to IDoc after it has been released can be done by creation of extension      of IDoc.
      IDoc type can be defined by structuring Segments
Function Module: The most important player in the IDOC processing. This is nothing but an ABAP program to process the IDOC. SAP has supplied function modules to process all standard basic IDOCs and messages. A function module is determined based on the Basic IDOC type and the message type (also message code). So from the above descriptions about basic and message type, the combination of two would primarily determine which IDOC will process this idoc. As an instance, ORDERS01 with message ORDERS is configured to be processed by FM IDOC_INPUT_ORDERS. Similarly, ORDERS01 + ORDCHG will be processed by IDOC_INPUT_ORDCHG. Likewise, you can see all associations in WE57 for inbound. For out bounds, you would refer to process codes (WE41).
Segments: The idenfiers in the IDOC structure which indicates the data, their level, state of occurrence....You can take them as records in the IDOC. Each individual segment will come to you as a record in the IDOC. (Go to EDID4, provide an IDOC # and it will list all included segments as records.) Segments are logically nested to indicate various levels of data (header, item etc).
Qualifiers: Inside the segments, there are fields that can carry actual data often signified by use of qualifiers. A qualifier for a segment field would provide the exact meaning of the data. For example, E1EDK03 segment is configured for dates related data. Segment field IDDAT qualifies the date type and the DATUM field gives out the actual date. So you may see a date qualified as 002, which can be interpreted as requested delivery date. Likewise you can see all qualifiers and their meanings in the associated segment fields in SE12. Give the segment name and go to the domain the ranges for the ID fields.
How EDI Works
Sending Data
     Computer system serves as a data repository.
     EDI extracts information from existing computer applications.
     Transmits paperless, computer-readable documents via telephone lines.
Receiving Data
     Fed directly into a computer system.
     Automatically processed and interfaced with internal applications.
Processing Time
     Accomplished in minutes.
     No re-keying.
     No paper shuffling.
     No attendant costs of manual document processing and delivery.
What is the difference between ALE, EDI, IDocs and BAPI?
The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
ALE/EDI - Purpose
Electronic Data Interchange (EDI) and Application Link Enabling (ALE) are used for exchanging business data between different systems.
For both these forms of communication, you require the IDoc Interface. The IDoc interface is made up of the definition of a data structure and the processing logic of this data structure. The data structure is the IDoc. The IDoc is the general exchange format of the communicating systems. IDocs can be sent using different methods (for example, RFC or as a file).
Application Link Enabling (ALE)
You distribute data using ALE if you want to communicate from one system to one or more other (mostly internal) systems. ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
1.     ALE enables the integration of business processes across several SAP or non-SAP systems.
Electronic Data Interchange (EDI)
You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor). The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12). This enables communication with non-SAP systems.
1.     By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message.
IDoc Interface/ALE
Purpose
The IDoc interface exchanges business data with an external system.
The IDoc interface consists of the definition of a data structure, along with processing logic for this data structure.
The data structure is the IDoc. The IDoc is the exchange format common to all the communicating systems. You can specify exception handling in the SAP Business Workflow, with IDocs, without the data already having to exist as SAP application documents.
You need the IDoc interface in the following scenarios:
Electronic data exchange (EDI)
Connect other business application systems (e.g. PC applications, external Workflow tools) by IDoc
Application Link Enabling (ALE).
Application Link Enabling (ALE) is a technology to create and run distributed applications
Hope this would help you.
Reward points if helpful.
Vamsi.

Issue while readnig child records of Advanced Table after show/hide event.

Hi All,
As suggested in OAF dev guide, I used below piece of code to get control on Child items for selected Parent
-- code Starts
// get a handle to inner table
OATableBean innerTable =
(OATableBean)webBean.findChildRecursive("InnerTableBean");
// create an enumerator
OAInnerDataObjectEnumerator enum =
new OAInnerDataObjectEnumerator(pageContext, innerTable);
while (enum.hasMoreElements())
RowSet innerRowSet = (RowSet) enum.nextElement();
// get all rows
Row []rowsInRange = innerRowSet.getAllRowsInRange();
for (int i = 0; i < rowsInRange.length; i++)
Row nextRow = (Row) rowsInRange;
-- code Ends
The above piece of code works when I don’t select show/hide link of Adv table and select custom ‘Update Parent/Child’ button that is placed at header(parent) level,
upon btn event it returns all the rows of parent and works fine. But when I select show/hide link and then select ‘Update Parent/Child’ button then only it return no of Child rows displayed (fetched) on page...
For example, If I have 100 child records of a set and only 10 child rows are displayed at a time on child region , then above code only returns 10 records,
Ideally it suppose to return all 100 values.
Can someone please help on this to understand why it only return 10 records not all 100 after selecting Hide show region ? and how can I fix this issue.
Thanks
Anand

Hi,
Use the VO attached to the inner table and use VO.fetchedRowCount instead of rowsInRange.length in the for loop.
int rowcount = vo.fetchedRowCount();
i.e. for (int i = 0; i < rowcount ; i++)
Thanks,
Kumar

How workflow work in ale layer.

hi guruj,
If an error occurs in the ALE layer, the IDoc containing the error is stored and a workflow is created.
how that works.
can u suggest some site or forwrd some material on it on([email protected]).
thankyou .

HI
see the links
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6702507d11d18ee90000e8366fc2/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/17/eb18c879ebd54798921ecbd2268a8e/content.htm
download docs.
http://www.erpgenie.com/sapgenie/docs/application_link_enabling_whitepaper.doc
http://www.erpgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://hosteddocs.ittoolbox.com/KW122906.pdf
http://65.13.3.56/Misc/Processing%20in%20the%20ALE%20Layer.pdf
http://www.dataxstream.com/doclib/ALEOptimization.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6a90d6aa-0b01-0010-8a83-cf0e6c70dcce
<b><REMOVED BY MODERATOR></b>
VIVEKANAND
Message was edited by:
Alvaro Tejada Galindo

Status 51:No status record was passed to ALE by the application

Hi All,
my scenario is file->XI->IDOC.
data is reaching r/3 system, but i see below error in WE02
status 51: Application document not posted
No status record was passed to ALE by the application
registering the function module, linking FM with basic type with direction equal to 2, assigning FM to process code and inbound parameters of partner profiles are configured well.
Plz let me know if i missed any steps.
Thanks,
Goutham

use similar thread
Inbound IDOC
In WE19, Give the IDOC number & execute ... then put the cursor on the idoc control record . then click on the Standard Inbound push button on the application tool bar.it will show show all the details like partner no,type , message type , process code & function module name ...
now put a break point in the function module .. & debug .
if u r using customised inbound function module , then click on inbound function module .. there u will get a pop screen with FM name & debugging option in both background & foreground mode...
Edited by: Dharamveer Gaur on Sep 19, 2008 2:17 PM

No status record was passed to ALE by the application

Hi Experts,
My requirement is something like this: The middleware (XI) is triggering an IDOC which is Inbound to SAP-ECC. This IDOC is used for posting of Financial documents (Invoice and Credit memos).
I am processing the IDOC by writing a FM. Inside the FM I am reading data from IDOC and using a BAPI to post the documents. Then I am updating the status of the IDOC based on successful or unsuccessful posting.
Issue: When XI triggers the IDOC, the IDOC is resulting in status "No status record was passed to ALE by the application". This is not the status that I am populating inside my FM. This means that the control is not entering the FM at all (please correct if I am wrong).
My findings: When I re-process the same IDOC which resulted in error previously using WE19, the control goes inside my FM (obviously as I give my FM name in WE19 ) and the status gets populated according to my code.
Problem that I am facing is only when I am trying to do an Intergration testing.
I have searched SDN for same issue and found out that I need to clear/refresh all the necessary variables. I am doing that (and double checked it too).
Please help me with this problem as I am running out of ways to find the solution (and time also ).
Many thanks,
Daljeet.

Hi Daljeet,
Please check SM58 logs.
Thanks,
Best regards,
Prashant

IDocStatus Application document not posted, No status record passed to ALE

Hi,
I am sending CREMAS04 IDOC to receiver system.The receiver system should create vendor entry in master table by using IDOC data.
IDOC is getting posted successfully in R/3,but while calling inbound function module i.e process code CRE1 I am getting following status records :
51 Application document not posted
No status record was passed to ALE by application.
62 IDOC passed to application
Direct call started.
64 IDOC ready to be transfered to application
No filters , No conversion , No version change .
50 IDoc added
Please help me to resolve this problem.

Shweta,
The IDOC has been posted by XI to the R3 system. It is the funtional module that is not able to handle the IDOC and only your Functional Team can tell you why the IDOC is not being processed properly by the R3 system.
It can be because of multiple reasons including invalid data, etc . For instance we once faced an issue once when the User ID used to post the IDOC did not have the authorizations to do financial manipulations and it was our functional team that was able to pin point the reason to us.
Regards,
Bhavesh

Record center - submit file soap call throwing The request failed with http status 401: Unauthorized" exception

Hi, I am trying to implement custom hold order / send to in sharepoint 2010 to send files in to holds / record center.
I am at the last step where I am trying submit the metadata using soap call- submit file
[SoapDocumentMethod("http://schemas.microsoft.com/sharepoint/soap/recordsrepository/SubmitFile", RequestNamespace = "http://schemas.microsoft.com/sharepoint/soap/recordsrepository/", ResponseNamespace = "http://schemas.microsoft.com/sharepoint/soap/recordsrepository/", Use = SoapBindingUse.Literal, ParameterStyle = SoapParameterStyle.Wrapped)]
public string SubmitFile([XmlElement(DataType = "base64Binary")] byte[] fileToSubmit, [XmlArrayItem(IsNullable = false)] Microsoft.SharePoint.RecordsRepositoryProperty[] properties, string recordRouting, string sourceUrl, string userName)
return (string)base.Invoke("SubmitFile", new object[] { fileToSubmit, properties, recordRouting, sourceUrl, userName })[0];
I am getting an error "The request failed with http status 401: Unauthorized".
Actual file was transferred successfully but while transferring the properties (metadata) I am getting this exception.
ganesh

Hi ganesh,
Please try to disable the loop back check, compare the result:
In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value.
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1, and then click OK.
Quit Registry Editor, and then restart your computer.
In addition, please check if these links are useful:
http://www.sharepointpills.com/2011/10/send-sharepoint-2010-document-to.html
http://www.codeproject.com/Articles/497729/UploadingplusDocumentsplusProgramaticallyplustoplu
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

IDoc Control Record and Status Record Code, where is it!!!

Hi,
Where can i see the code for generation of control record and status record of IDoc.
   Thanks in advance for your answers

hi ,
1.first create an segment with the fields u want tcode we31 relase it .
2. create an idoc and assign segment to it tcode we30.
3.crate a message type tcode we81
4.assign that message to idoc tcode we 82.
do the ale configarations .
now u can write the code in our sender system
*1.     Create parameters/select-options for input data. i.e., message type, logical system.
parameters : p_mestyp like edmsg-msgtyp default 'ZKKUMSG',
             p_logsys like tbdlst-logsys obligatory.
*2.     Create Data objects for control record, data record and database table.
data : c_segment like edidd-segnam value 'ZKKUSEG',        "Data record (IDoc)-Segment type
       c_idoctp like edidc-idoctp value 'ZKKUIDOC'.            "Control record (IDoc)-Basic type
data : begin of i_tab occurs 0,
          ZKSNO   like ZKSTD-ZKSNO,
          ZKSNAME like ZKSTD-ZKSNAME,
       end of i_tab.
data : w_itab like i_tab.
data : s_segment like ZKKUSEG.
data : i_edidd like edidd occurs 0 with header line.
data : i_control_record like edidc.
data : i_comm_idoc like edidc occurs 0 with header line.
*3.     Select the data from responding tables into internal table for a defined condition.
here you have take ur internal table
*select single zsno zsname from zkiran into corresponding fields of itab where zsno = p_sno.
*4.     create control record into internal table.
i_control_record-mestyp = p_mestyp.         "Message Type
i_control_record-idoctp = c_idoctp.         "Basic type
i_control_record-rcvprt = 'LS'.             "Partner Type of Receiver
i_control_record-rcvprn = p_logsys.         "Partner Number of Recipient
*5.     create data record into internal table.
*i_edidd-segnam =   c_segment.
loop at i_tab into w_itab.
s_segment-zksno    = w_itab-ZKSNO.                     "Application Data
s_segment-zksname = w_itab-ZKSNAME.
i_edidd-sdata     = s_segment.
i_edidd-segnam    = c_segment.
clear w_itab.
append i_edidd.
endloop.
*6.     Process ALE Service Layer using the function module MASTER_IDOC_DISTRIBUTE. It returns the corresponding IDoc No.s.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
    master_idoc_control            = i_control_record
tables
    communication_idoc_control     = i_comm_idoc
    master_idoc_data               = i_edidd
exceptions
    error_in_idoc_control          = 1
    error_writing_idoc_status      = 2
    error_in_idoc_data             = 3
    sending_logical_system_unknown = 4
    others                         = 5.
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
          with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*7.     Display Communication IDocs.
loop at i_comm_idoc.
write : / 'Communication IDoc No. is : ', i_comm_idoc-docnum.
endloop.
*8.     Commit Work.
commit work.
i hope this sample code help u .
thanks

Problems connecting to SSRS using IReportServerCredentials, the request failed with http status 401: unauthorized

We have a hosted SSRS server and we access it's reports using the reportviewer in an ASP.net application.
We are getting the error: The request failed with HTTP status 401: Unauthorized. When trying to run one of the reports. I have confirmed that the login details work when logging into the report manager page directly.
I have implemented an instance of IReportServerCredentials in a separate class (below) and I call it from the page before it tries to access the report. I'm not sure if this is all I need but can't seem to find any other info.
I have managed to gain access connecting to the external server from my PC and accessed the report, but when I promote the code to production and run it from there on my local PC I get the unauthorized message again: the request failed with http status
401: unauthorized
The class:
[Serializable]
public sealed class MyReportServerCredentials :
IReportServerCredentials
public WindowsIdentity ImpersonationUser
get
// Use the default Windows user. Credentials will be
// provided by the NetworkCredentials property.
return null;
public ICredentials NetworkCredentials
get
// Read the user information from the Web.config file.
// By reading the information on demand instead of
// storing it, the credentials will not be stored in
// session, reducing the vulnerable surface area to the
// Web.config file, which can be secured with an ACL.
// User name
string userName =
ConfigurationManager.AppSettings
["MyReportViewerUser"];
if (string.IsNullOrEmpty(userName))
throw new Exception(
"Missing user name from web.config file");
// Password
string password =
ConfigurationManager.AppSettings
["MyReportViewerPassword"];
if (string.IsNullOrEmpty(password))
throw new Exception(
"Missing password from web.config file");
// Domain
string domain =
ConfigurationManager.AppSettings
["MyReportViewerDomain"];
return new NetworkCredential(userName, password);
public bool GetFormsCredentials(out Cookie authCookie,
out string userName, out string password,
out string authority)
authCookie = null;
userName = null;
password = null;
authority = null;
// Not using form credentials
return false;
The call to the class, just before the report is run:
if (GetConnection.GetConnectionString().ToString().Contains("IP of external server removed"))
invoiceviewer.ServerReport.ReportServerCredentials = new MyReportServerCredentials();
We have tried so many things here, we don't even care whether the server authenticates or not but it appears to be as standard. Our hosting company has also drawn a blank and changed so many settings to no ava

Hi Nasa1999,
According to your description, you are getting the error: The request failed with HTTP status 401: Unauthorized when you access the report using the ReportViewer in an ASP.net application.
Regarding the 401 error, it could cause by the Service Principal Name(SPN) for the account the Reporting Services is running under hasn’t been registered when the Reporting Services is configured to use Kerberos authentication. So in your scenario,
please check if you are using Kerberos authentication. If that is a case, please make sure SPN is configured correctly. For more information, please refer to the similar thread:
The request failed with HTTP status 401: Unauthorized. in SSRS.
If issue persists, please check the Reporting Service error log (default location: %programfiles%\Microsoft SQL Server\<SQL Server Instance>\Reporting Services\LogFiles) around the time that the error message thrown out.
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

OSD Install application fails.

Hi, i hope someone can help :)
Single install application step is failing after 4 hours waiting. The installation and discovery of the application was correct, return code 0, but the task sequence doesnt continue, its stops there for hours and then fails.
If i boot windows the aplication is correctly installed and working.
Im using SCCM2012 SP1.
Error on Status Messages:
The task sequence execution engine failed executing the action (Install MS Office 2010 Pro Plus) in the group (Install Applications) with the error code 2278556181Action output: ... ssage Setting URL = ***********, Ports = 80,443, CRL = false Setting Server Certificates. Setting Authenticator.Set authenticator in transport Setting Media Certificate.Sending StatusMessageSetting message signatures.Setting the authenticator.CLibSMSMessageWinHttpTransport::Send: URL: ***********:80 CCM_POST /ccm_system/requestRequest was succesful.hrInstallation, HRESULT=87d00215 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,808)pInstall->InstallApplications(saAppNames, sContinueOnError), HRESULT=87d00215 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\main.cpp,277)Failed to Reconnect to existing job, hr=0x87d00215Reconnect Job request failed, hr=0x87d00215Install application action failed: 'Microsoft Office 2010 Pro Plus'. Error Code 0x87d00215Install application action cannot continue. ContinueOnErrorFlag is set to false.Install Static Applications failed, hr=0x87d00215. The operating system reported error 1: Incorrect function.
No errors on AppEnforce.log:
Prepared working directory: C:\Windows\ccmcache\1
Prepared command line: "C:\Windows\ccmcache\1\setup.exe" /adminfile office2010.MSP
Executing Command line: "C:\Windows\ccmcache\1\setup.exe" /adminfile office2010.MSP with system context
Working directory C:\Windows\ccmcache\1
Post install behavior is BasedOnExitCode
Waiting for process 3516 to finish. Timeout = 120 minutes.
Process 3516 terminated with exitcode: 0
Looking for exit code 0 in exit codes table...
Matched exit code 0 to a Success entry in exit codes table.
Performing detection of app deployment type Microsoft Office 2010 Pro
Plus(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d,
revision 4) for system.
+++ Discovered application [AppDT Id:
ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d,
Revision: 4]
++++++ App enforcement completed (964
seconds) for App DT "Microsoft Office 2010 Pro Plus"
[ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d],
Revision: 4, User SID: ] ++++++
Regards,
Daniel B

Btw, we have published 2 applications on the OSD TS and noticed the error is happening to both applications, it was working before.
Aplication installation fails after some hours, but its installed ...
smsts.log
Invoking App Management SDK to evaluate app polices InstallApplication 17/09/2013 16:09:34 2924 (0x0B6C)
CAppMgmtSDK::EvaluateAppPolicy ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.(null) DCMAgent 17/09/2013 16:09:34 2924 (0x0B6C)
App policy evaluation for application 'ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6' has started. Please refer to DCMAgent.log for the details on this job. JobID='{E5009A8E-63F4-4234-BF7A-FC99FD15167F}' InstallApplication 17/09/2013 16:09:34 2924 (0x0B6C)
Setting TSEnv variable 'SMSTSAppPolicyEvaluationJobID__ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/Application_f9c9997b-8d3a-459e-accd-57ed8ac79bf6'='{E5009A8E-63F4-4234-BF7A-FC99FD15167F}' InstallApplication 17/09/2013 16:09:34 2924 (0x0B6C)
Waiting for installation job to complete.. InstallApplication 17/09/2013 16:09:34 2924 (0x0B6C)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:34 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:34 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:34 1996 (0x07CC)
spCIStateStore->GetCIState( pszAppPolicyId, csPolicyRevision, (sUserSID.length()>0) ? sUserSID.c_str() : 0, &spPolicyState, 1), HRESULT=87d00215 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,2088) DCMAgent 17/09/2013 16:09:34 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState - ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 Not found in CI state store. Marking CIs state as EvaluationFailed DCMAgent 17/09/2013 16:09:34 1996 (0x07CC)
NotifyProgress received: 16 (Application failed to evaluate ) InstallApplication 17/09/2013 16:09:34 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:34 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:34 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:34 1996 (0x07CC)
spCIStateStore->GetCIState( pszAppPolicyId, csPolicyRevision, (sUserSID.length()>0) ? sUserSID.c_str() : 0, &spPolicyState, 1), HRESULT=87d00215 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,2088) DCMAgent 17/09/2013 16:09:34 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState - ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 Not found in CI state store. Marking CIs state as EvaluationFailed DCMAgent 17/09/2013 16:09:34 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:43 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:43 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:43 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = Unknown DCMAgent 17/09/2013 16:09:43 1996 (0x07CC)
NotifyProgress received: 0 (No application state information is available ) InstallApplication 17/09/2013 16:09:43 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:44 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:44 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:44 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = Unknown DCMAgent 17/09/2013 16:09:44 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
NotifyProgress received: 3 (Application is available for installation ) InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
NotifyComplete received InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
NotifyComplete processed InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
Received job completion notification from DCM Agent InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
Policy evaluation for App successful InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
Setting TSEnv variable 'SMSTSAppPolicyEvaluationJobID__ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/Application_f9c9997b-8d3a-459e-accd-57ed8ac79bf6'='' InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
EvaluationJob complete InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
Checking if the active request handle: {BE78A9F9-F9BC-409E-9AF9-0B1F8CE0CFAF} is valid. InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
CoCreateInstance succeeded InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
Active request handle: {BE78A9F9-F9BC-409E-9AF9-0B1F8CE0CFAF} is valid. InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
Invoking App Management SDK to install application InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
CAppMgmtSDK::EnforceAppPolicy ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.(null) DCMAgent 17/09/2013 16:09:45 2924 (0x0B6C)
Installing application 'ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6' has started. Please refer to DCMAgent.log for the details on this job. JobID='{42FB35A9-CCB5-4C30-91DA-B251B6893FF4}' InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
Setting TSEnv variable 'SMSTSInstallApplicationJobID__ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/Application_f9c9997b-8d3a-459e-accd-57ed8ac79bf6'='{42FB35A9-CCB5-4C30-91DA-B251B6893FF4}' InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
Waiting for installation job to complete.. InstallApplication 17/09/2013 16:09:45 2924 (0x0B6C)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Passed in version 17 for ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
CAppMgmtSDK::GetEvaluationState ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 = AvailableForEnforcement DCMAgent 17/09/2013 16:09:45 1996 (0x07CC)
Waiting for job status notification... InstallApplication 17/09/2013 22:09:45 2924 (0x0B6C)
AppMgmtSDK handler is invalid. Trying to reconnect... InstallApplication 17/09/2013 22:09:45 2924 (0x0B6C)
GetAppMgmtSDKInterface successful InstallApplication 17/09/2013 22:09:45 2924 (0x0B6C)
Reconnecting to existing jobID '{42FB35A9-CCB5-4C30-91DA-B251B6893FF4}'.. InstallApplication 17/09/2013 22:09:45 2924 (0x0B6C)
spAgent->GetJob(jobId, &spAgentJob), HRESULT=87d00215 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,1756) DCMAgent 17/09/2013 22:09:46 2924 (0x0B6C)
spAppMgmtSDK->SetEvaluationCallback( guidJobID, spNotifyCompPtr ), HRESULT=87d00215 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,404) InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Failed to Reconnect to existing job, hr=0x87d00215 InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Reconnect Job request failed, hr=0x87d00215 InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
ReconnectJob(spAppMgmtSDK, spCallback, guidJobID), HRESULT=87d00215 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,1152) InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
WaitforJobCompletion(spAppMgmtSDK, m_guidAppInstallJobID, ulAppInstallTimeout, nAppInstallRetryAttempts), HRESULT=87d00215 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,1041) InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Step 2 out of 2 complete InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Install application action failed: 'Microsoft Office 2010 Pro Plus'. Error Code 0x87d00215 InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Sending error status message InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Setting URL = http://*****, Ports = 80,443, CRL = false InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Setting Server Certificates. InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Setting Authenticator. InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Set authenticator in transport InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Setting Media Certificate. InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Sending StatusMessage InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Setting message signatures. InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Setting the authenticator. InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
CLibSMSMessageWinHttpTransport::Send: URL: *****:80 CCM_POST /ccm_system/request InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Request was succesful. InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Install application action cannot continue. ContinueOnErrorFlag is set to false. InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
hrInstallation, HRESULT=87d00215 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,808) InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
pInstall->InstallApplications(saAppNames, sContinueOnError), HRESULT=87d00215 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\main.cpp,277) InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Install Static Applications failed, hr=0x87d00215 InstallApplication 17/09/2013 22:09:46 2924 (0x0B6C)
Process completed with exit code 2278556181 TSManager 17/09/2013 22:09:46 928 (0x03A0)
!--------------------------------------------------------------------------------------------! TSManager 17/09/2013 22:09:46 928 (0x03A0)
Failed to run the action: Microsoft Office 2010 SP1.
Item not found (Error: 87D00215; Source: CCM) TSManager 17/09/2013 22:09:46 928 (0x03A0)
MP server http://****. Ports 80,443. CRL=false. TSManager 17/09/2013 22:09:46 928 (0x03A0)
Setting authenticator TSManager 17/09/2013 22:09:46 928 (0x03A0)
Set authenticator in transport TSManager 17/09/2013 22:09:46 928 (0x03A0)
Sending StatusMessage TSManager 17/09/2013 22:09:46 928 (0x03A0)
Setting message signatures. TSManager 17/09/2013 22:09:46 928 (0x03A0)
Setting the authenticator. TSManager 17/09/2013 22:09:46 928 (0x03A0)
CLibSMSMessageWinHttpTransport::Send: URL: ****:80 CCM_POST /ccm_system/request TSManager 17/09/2013 22:09:46 928 (0x03A0)
Request was succesful. TSManager 17/09/2013 22:09:46 928 (0x03A0)
Set a global environment variable _SMSTSLastActionRetCode=-2016411115 TSManager 17/09/2013 22:09:46 928 (0x03A0)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 17/09/2013 22:09:46 928 (0x03A0)
Clear local default environment TSManager 17/09/2013 22:09:46 928 (0x03A0)
The execution engine ignored the failure of the action (Microsoft Office 2010 SP1) and continues execution TSManager 17/09/2013 22:09:46 928 (0x03A0)
CIAgent.log
CAgent::Initialize succeeded. CIAgent 17/09/2013 16:04:58 3100 (0x0C1C)
CI Agent successfully started up. CIAgent 17/09/2013 16:04:58 3100 (0x0C1C)
CAgent::CreateJob - Creating new CI Agent Job for machine CIAgent 17/09/2013 16:09:34 3052 (0x0BEC)
CAgent::EvaluateCIs CIAgent 17/09/2013 16:09:34 3104 (0x0C20)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 17/09/2013 16:09:34 3052 (0x0BEC)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::HandleEvent(Event=Transition, CurrentState=Init) CIAgent 17/09/2013 16:09:34 3104 (0x0C20)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): Client requesting CIAgentJob context info for key: StateMessagePriority CIAgent 17/09/2013 16:09:34 3104 (0x0C20)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): TransitionState(From=Init, To=WaitingForAssignedCI) for Event=Transition CIAgent 17/09/2013 16:09:34 3104 (0x0C20)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 17/09/2013 16:09:34 3104 (0x0C20)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:34 3104 (0x0C20)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::HandleEvent(Event=Transition, CurrentState=WaitingForAssignedCI) CIAgent 17/09/2013 16:09:34 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore DownloadCIs CIAgent 17/09/2013 16:09:34 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:34 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::HandleEvent(Event=DownloadCIs, CurrentState=WaitingForAssignedCI) CIAgent 17/09/2013 16:09:34 4076 (0x0FEC)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): TransitionState(From=WaitingForAssignedCI, To=DownloadingCIs) for Event=Transition CIAgent 17/09/2013 16:09:34 4076 (0x0FEC)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 17/09/2013 16:09:34 4076 (0x0FEC)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:34 4076 (0x0FEC)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::HandleEvent(Event=Transition, CurrentState=DownloadingCIs) CIAgent 17/09/2013 16:09:34 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): Client requesting CIAgentJob context info for key: PostRebootDetect CIAgent 17/09/2013 16:09:34 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): Started CIDownloadJob({5468E99C-9DBA-4463-9587-29D881EA38E3}) CIAgent 17/09/2013 16:09:35 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:35 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore PersistCIs CIAgent 17/09/2013 16:09:43 4036 (0x0FC4)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::HandleEvent(Event=PersistCIs, CurrentState=DownloadingCIs) CIAgent 17/09/2013 16:09:43 4036 (0x0FC4)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): TransitionState(From=DownloadingCIs, To=PersistingCIModels) for Event=Transition CIAgent 17/09/2013 16:09:43 4036 (0x0FC4)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::Execute [GlobalSemaphore] Trying to aquire global semaphore CIAgent 17/09/2013 16:09:43 4036 (0x0FC4)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::Execute [GlobalSemaphore] Queued for global semaphore acquisition. CIAgent 17/09/2013 16:09:43 4036 (0x0FC4)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): GlobalJobEvent() called [GlobalSemaphore] CIAgent 17/09/2013 16:09:43 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::Execute [GlobalSemaphore] Acquired global semaphore. CIAgent 17/09/2013 16:09:43 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::HandleEvent(Event=Transition, CurrentState=PersistingCIModels) CIAgent 17/09/2013 16:09:43 4080 (0x0FF0)
CAgent::CreateJob - Creating new CI Agent Job for machine CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CAgent::EvaluateCIs CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::HandleEvent(Event=Transition, CurrentState=Init) CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): Client requesting CIAgentJob context info for key: StateMessagePriority CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): TransitionState(From=Init, To=WaitingForAssignedCI) for Event=Transition CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::HandleEvent(Event=Transition, CurrentState=WaitingForAssignedCI) CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore DownloadCIs CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::HandleEvent(Event=DownloadCIs, CurrentState=WaitingForAssignedCI) CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): TransitionState(From=WaitingForAssignedCI, To=DownloadingCIs) for Event=Transition CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::HandleEvent(Event=Transition, CurrentState=DownloadingCIs) CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): Client requesting CIAgentJob context info for key: PostRebootDetect CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/Application_f9c9997b-8d3a-459e-accd-57ed8ac79bf6:17 (Office 2010 Pro Plus) targeted to (Dependant of policy CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6:17) is in scope for evaluation. CIAgent 17/09/2013 16:09:44 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d:13 (Microsoft Office 2010 Pro Plus) targeted to (Dependant of policy CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6:17) is in scope for evaluation. CIAgent 17/09/2013 16:09:44 4080 (0x0FF0)
Failed to get the display name of the CI. Status messages will be based on the CI ID. CIAgent 17/09/2013 16:09:44 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6:17 () targeted to (Dependant of policy CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6:17) is in scope for evaluation. CIAgent 17/09/2013 16:09:44 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): TransitionState(From=PersistingCIModels, To=InvokingSdmMethod) for Event=Transition CIAgent 17/09/2013 16:09:44 4080 (0x0FF0)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): Started CIDownloadJob({5305BEEB-DDA8-4E92-98AC-76B14B9213B6}) CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 17/09/2013 16:09:44 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:44 4080 (0x0FF0)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::HandleEvent(Event=Transition, CurrentState=InvokingSdmMethod) CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): StartEnactment - CI - ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6 CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): StartEnactment - Attempting to invoke Policy Platform Client CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
Acquiring lock CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
DCM::LanternUtils::CreateBindingInstance - Creating binding document for Policy: ScopeId_A1EAE2D5_4D36_4E8F_BBB7_EF7ADC272A5E_Application_f9c9997b_8d3a_459e_accd_57ed8ac79bf6_17_Platform_PolicyDocument, Revision: 17. CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
DCM::LanternUtils::ScopeAndBindPolicies - [ScopedPolicies] ScopeId_A1EAE2D5_4D36_4E8F_BBB7_EF7ADC272A5E_Application_f9c9997b_8d3a_459e_accd_57ed8ac79bf6_17_Platform_PolicyDocument CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
DCM::LanternUtils::CreateBindingInstance - Creating binding document for Policy: ScopeId_A1EAE2D5_4D36_4E8F_BBB7_EF7ADC272A5E_Application_f9c9997b_8d3a_459e_accd_57ed8ac79bf6_17_Configuration_PolicyDocument, Revision: 17. CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
DCM::LanternUtils::ScopeAndBindPolicies - [ScopedPolicies] ScopeId_A1EAE2D5_4D36_4E8F_BBB7_EF7ADC272A5E_Application_f9c9997b_8d3a_459e_accd_57ed8ac79bf6_17_Configuration_PolicyDocument CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
DCM::LanternUtils::CreateBindingInstance - Creating binding document for Policy: ScopeId_A1EAE2D5_4D36_4E8F_BBB7_EF7ADC272A5E_DeploymentType_3bdc07d5_1d0b_4c3f_a17b_4f6dc45b0c4d_13_Discovery_PolicyDocument, Revision: 13. CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
DCM::LanternUtils::ScopeAndBindPolicies - [ScopedPolicies] ScopeId_A1EAE2D5_4D36_4E8F_BBB7_EF7ADC272A5E_DeploymentType_3bdc07d5_1d0b_4c3f_a17b_4f6dc45b0c4d_13_Discovery_PolicyDocument CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
DCM::LanternUtils::CreateBindingInstance - Creating binding document for Policy: ScopeId_A1EAE2D5_4D36_4E8F_BBB7_EF7ADC272A5E_DeploymentType_3bdc07d5_1d0b_4c3f_a17b_4f6dc45b0c4d_13_Requirements_PolicyDocument, Revision: 13. CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
DCM::LanternUtils::ScopeAndBindPolicies - [ScopedPolicies] ScopeId_A1EAE2D5_4D36_4E8F_BBB7_EF7ADC272A5E_DeploymentType_3bdc07d5_1d0b_4c3f_a17b_4f6dc45b0c4d_13_Requirements_PolicyDocument CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore PersistCIs CIAgent 17/09/2013 16:09:44 1404 (0x057C)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::HandleEvent(Event=PersistCIs, CurrentState=DownloadingCIs) CIAgent 17/09/2013 16:09:44 4080 (0x0FF0)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): TransitionState(From=DownloadingCIs, To=PersistingCIModels) for Event=Transition CIAgent 17/09/2013 16:09:44 4080 (0x0FF0)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::Execute [GlobalSemaphore] Trying to aquire global semaphore CIAgent 17/09/2013 16:09:44 4080 (0x0FF0)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::Execute [GlobalSemaphore] Queued for global semaphore acquisition. CIAgent 17/09/2013 16:09:44 4080 (0x0FF0)
Lantern job:F9CAD339-56FE-477B-8C5B-215F67BE3AB1 succeeded. CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
Releasing lock CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): Invocation succeeded for policy platform job F9CAD339-56FE-477B-8C5B-215F67BE3AB1 CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:44 4036 (0x0FC4)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): ReportMethodInvocation :: Enactment succeeded CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): ReportMethodInvocation :: Obtained lantern reports CIAgent 17/09/2013 16:09:44 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}):State - Reporting (scan):: AppModel - ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/Application_f9c9997b-8d3a-459e-accd-57ed8ac79bf6:17 - State = NotInstalled ResolvedState = Available Applicability = Applicable ConfigureState= NotNeeded CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}):State - Reporting (scan):: Deployment Type - ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d:13 - State = NotInstalled ResolvedState = Available Applicability = Applicable ConfigureState= NotNeeded CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}):State - Reporting (scan):: Install Policy Type - ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6:17 - State = NonCompliant ResolvedState = Compliant Applicability = Applicable ConfigureState= NotNeeded CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::ReleaseGlobalSemaphore [GlobalSemaphore] Released global download semaphore CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): GlobalJobEvent() called [GlobalSemaphore] CIAgent 17/09/2013 16:09:45 4036 (0x0FC4)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::Execute [GlobalSemaphore] Acquired global semaphore. CIAgent 17/09/2013 16:09:45 4036 (0x0FC4)
CIAgentJob({8251BDAA-A7B6-4EC8-8807-E0EEA1650EF8}): CAgentJob::HandleEvent(Event=Transition, CurrentState=PersistingCIModels) CIAgent 17/09/2013 16:09:45 4036 (0x0FC4)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore NotifyComplete CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::HandleEvent(Event=NotifyComplete, CurrentState=InvokingSdmMethod) CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): TransitionState(From=InvokingSdmMethod, To=CompletedSdmMethodInvocation) for Event=Transition CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::HandleEvent(Event=Transition, CurrentState=CompletedSdmMethodInvocation) CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): TransitionState(From=CompletedSdmMethodInvocation, To=StateDownloadingContents) for Event=Transition CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): QueueDebug - Executing Event. CIAgent 17/09/2013 16:09:45 3132 (0x0C3C)
CIAgentJob({B95D2613-0A5F-4738-B404-3470919D3F6E}): CAgentJob::HandleEvent(Event=Transition, Current
CITaskMgr.log
Initiating task ContentDownload for CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13 (Microsoft Office 2010 Pro Plus) for target: , consumer: {C6E3BB4D-852B-4240-9F36-2871DD7BAAB8} CITaskMgr 17/09/2013 16:09:45 4036 (0x0FC4)
Initiating content download : CITask(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13..Install.ContentDownload) CITaskMgr 17/09/2013 16:09:46 4036 (0x0FC4)
State transition to (InProgress), Param(0) : CITask(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13..Install.ContentDownload) CITaskMgr 17/09/2013 16:09:46 4036 (0x0FC4)
State transition to (InProgress), Param(0) : CTaskConsumer(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13.{6273217C-1E91-44EE-9CF0-97628CD04706}) CITaskMgr 17/09/2013 16:09:46 4036 (0x0FC4)
Successfully initiated contents download request {00C794C9-CA03-4E1B-9440-73E09A1A12F9} : CITask(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13..Install.ContentDownload) CITaskMgr 17/09/2013 16:09:46 4036 (0x0FC4)
Initiating task ContentDownload for CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13 (Microsoft Office 2010 Pro Plus) for target: , consumer: {A6CC1080-139B-4ED0-8DEB-04FBF8E2D613} CITaskMgr 17/09/2013 16:10:43 2168 (0x0878)
State transition to (Success), Param(0) : CITask(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13..Install.ContentDownload) CITaskMgr 17/09/2013 16:13:30 3804 (0x0EDC)
State transition to (Success), Param(0) : CTaskConsumer(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13.{6273217C-1E91-44EE-9CF0-97628CD04706}) CITaskMgr 17/09/2013 16:13:30 3804 (0x0EDC)
Release task ContentDownload for CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13 for target: , consumer {A6CC1080-139B-4ED0-8DEB-04FBF8E2D613} CITaskMgr 17/09/2013 16:13:30 412 (0x019C)
Release task ContentDownload for CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/Application_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 for target: , consumer {988A4382-4757-4C3C-B418-0A2B76B27224} CITaskMgr 17/09/2013 16:13:30 412 (0x019C)
Release task ContentDownload for CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 for target: , consumer {1B8A201C-758A-46DE-8BC3-813BB089180C} CITaskMgr 17/09/2013 16:13:30 412 (0x019C)
Initiating task Enforce for CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13 (Microsoft Office 2010 Pro Plus) for target: , consumer: {9D59DEFA-BF1A-455C-9B07-D5815CA8DE12} CITaskMgr 17/09/2013 16:13:30 3804 (0x0EDC)
Starting Enforcement : CITask(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13..Install.Enforce) CITaskMgr 17/09/2013 16:13:30 3804 (0x0EDC)
Initiated application enforcement. : CITask(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13..Install.Enforce) CITaskMgr 17/09/2013 16:13:30 3804 (0x0EDC)
State transition to (InProgress), Param(0) : CITask(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13..Install.Enforce) CITaskMgr 17/09/2013 16:13:30 3804 (0x0EDC)
State transition to (InProgress), Param(0) : CTaskConsumer(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13.{6273217C-1E91-44EE-9CF0-97628CD04706}) CITaskMgr 17/09/2013 16:13:30 3804 (0x0EDC)
Application enforcement completed : CITask(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13..Install.Enforce) CITaskMgr 17/09/2013 16:28:59 3200 (0x0C80)
Enforcement completion state Success : CITask(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13..Install.Enforce) CITaskMgr 17/09/2013 16:28:59 3200 (0x0C80)
State transition to (Success), Param(0) : CITask(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13..Install.Enforce) CITaskMgr 17/09/2013 16:28:59 3200 (0x0C80)
State transition to (Success), Param(0) : CTaskConsumer(ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13.{6273217C-1E91-44EE-9CF0-97628CD04706}) CITaskMgr 17/09/2013 16:28:59 3200 (0x0C80)
Release task Enforce for CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/DeploymentType_3bdc07d5-1d0b-4c3f-a17b-4f6dc45b0c4d.13 for target: , consumer {9D59DEFA-BF1A-455C-9B07-D5815CA8DE12} CITaskMgr 17/09/2013 16:29:04 2572 (0x0A0C)
Release task Enforce for CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/Application_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 for target: , consumer {E9622739-EAFB-4C44-B582-EB0EECD0EF30} CITaskMgr 17/09/2013 16:29:04 2572 (0x0A0C)
Release task Enforce for CI ScopeId_A1EAE2D5-4D36-4E8F-BBB7-EF7ADC272A5E/RequiredApplication_f9c9997b-8d3a-459e-accd-57ed8ac79bf6.17 for target: , consumer {CD21FEE4-970C-4C68-B7FA-3C31EBF31E3C} CITaskMgr 17/09/2013 16:29:04 2572 (0x0A0C)

Application failed to return status record to ALE layer after Idoc procesed

Similar Messages

Maybe you are looking for