Http_communication _failure error -reason code 400
Hi All,
I am trying to call a rest based json web service(non sap system) in an abap program by using the CL_HTTP_CLIENT=>CREATE(passing the Host and service details) ,and cl_http_utility=>set_request_uri(with url details), the receive method giving a communication failure error .
The system is a gateway system.
Please let me know the settings Required for this and the methods for parsing the json data to the abap format .
Thank you
Hi Siva,
Thank you for your reply.
We have checked the ports that is concerning SUP it is 2000 we find it is active and open.
We have also checked a subscription monitoring table as suggested in a previous post [/community [original link is broken]
threadID=1978692].
we are getting a HTTP 110 error while debugging the queue of the device.
While checking a monitoring we have found a log saying :
Receive failed: client host = 10.116.158.208: com.sybase.djc.SystemException: HTTP: Post Message - HIOP Version not specified\nProbable cause: unexpected failure or abnormal shutdown of client application or client host
Please suggest to us what might might be the problem.
Thanks,
Krutheeka.
Similar Messages
-
Hello All,
I am trying to create a proxy class from a webservice through a URL.
I get the error:
HTTP error (return code 400, message "ICM_HTTP_CONNECTION_FAILED")
What could be the reason for this. Please help.
Thanks,
SmitaHi Smita
Pls refer the links for this error ICM_HTTP_CONNECTION_FAILED
The specified item was not found.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/changing%252bhttp%252bport%252bof%252bdecentralized%252badapter%252bengine
Http* Errors in XI
Configuring & Publishing Enterprise Services from SAP Business Suite system into NWCE (Netweaver Composition Environment) Services Registry
Publishing ABAP WebServices to an External UDDI Server
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
Regards
Abhishek -
Error: Reason codes with automatic charge-off are not permitted here(F-28)
Hi All
I creted a reason code in obxl t-code and assigned a gl code in OBXL transaction code, But when I am trying to clear a payment with reason code in F-28, System is throwing the following error..Can some one tell me why i am getting this error?
Reason codes with automatic charge-off are not permitted here
Message no. F5605
Diagnosis
The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose. Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
System Response
The reason code entered is not accepted.
Procedure
You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.Hi Venkata,
It seems while entering the payment (partial payment / residual items) ... you are clearing multiple items with differences. (e.g. if the difference amount is $30, then may the difference consists of two invoices underpaid by $15 each). In this scenario, F-28 doesn't know which additional account assignment fields should be picked up ... hence the error.
First of all, to validate that this indeed is the case, try clearing a payment with the same reason code where difference can be attributed to a single invoice. If you still get an error, then there is some other problem.
Then, to take care of a the business scenario where the difference can indeed be due to multiple documents, select "charge off difference" option and create an entry to post the difference as necessary.
HTH,
Manish Patel
Sr. SAP Solutions Consultant -
Error status code 400 with the description Message mapping failed
Hi,
I tried to build RFID outbound scenario using ECC 5.0, XI and AII 2.1.
When I send IDOC message:AIDOPMSG.AIDOP01 from ecc 5.0 to XI(ouput message type is OperationalIn and message mapping is OperationalInTo), i get following error:
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>Message mapping failed</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Message mapping failed</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 400 with the description Message mapping failed Boundary SAP_57D7D47469E09543A1EA0002CBDA0492_END could not be found</SAP:Stack>
I am using standard AUTO-ID 2.1 XI contents. If any of you have encountered such error message, then could you please help me understand the meaning and how to fix it.
thanks in advance,
Ashithi Ashit,
take a look at my weblog on how to test your mapping:
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
maybe with this you'll be able to find out the error
Regards,
michal -
Validation at line item level for F-32 to input Reason code
Hi Gurus,
I would like to write a validation / substitution for F-32 transaction code where in the Reason code field need to be mandatory field (With out input in to this field value the user should not come out of the transaction)
Please guide me how to write validation with out user exit
ThanksHi Suresh,
I guess the idea of MEENAKSH is good, perhaps you have an error in the Tcode, because in table BKPF the Tcode stored is FB1D and not F-32 :
So put the following in GGB0 and check again :
Prerequisite :
BKPF-TCODE = FB1D
Check :
BSEG-RSTGR <> ' '
Message :
Error : Reason code required
in the other hand, you can active a trace in GGB0 (Menu > Extras > Activate trace) to see what's the exactly the error
So it's not a question of screen.
Regards. -
HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED
Hi
when using an https receiver adapter in PI 7.11 I get the error message
"HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED".
The server I am trying to connect to is running and I have activated all services under sap -> xi in SICF.
The ICM log shows this:
WARNING => Connection request from (38/18489/0) to host: https, service: 80 failed (NIEHOST_UNKNOWN)
AP-T38, U18489, 001 ALE_K01, , 15:45:37, M0, W9, , 1/0 [icxxconn.c 2222]
On the PI Integration Server the outbound queue (smq1) is empty.
However, the message seems to be sitting in the inbound tRFC queue (smq2)
Function Module: SXMS_ASYNC_EXEC
Queue Name: XBTO6___0002
Status Text: Transaction Recorded
I also get the error message in the inbound tRFC queue:
"XI Error ATTRIBUTE_CLIENT.PLAINHTTP_ADAPTER: Queue"
It does not help to chose "save LUW" on the erroneous message in the queue.
In the http receiver adapter I entered these values:
Addressing Type: URL Address
Target Host: https://biztalk.lm-gruppen.dk
Service Number: 443
Path: /******/BTSHTTPReceive.dll
What should I do to make it work?
MikaelHi,
In the http receiver adapter I entered these values:
Addressing Type: URL Address
Target Host: https://biztalk.lm-gruppen.dk
Service Number: 443
Path: /******/BTSHTTPReceive.dll
If you want to enable HTTPs, you should use HTTP to RFC destination using SM59 (for the RFC destination) and STRUST (for the SSL authentication). Also, do not specify the http:// or https:// parameter in your target host. The correct parameters should be:
Target Host: biztalk.lm-gruppen.dk
Service Number: 443
Path: /******/BTSHTTPReceive.dll
hope this helps, -
HTTP server code 400 reason Bad Request explanation Bad Request
hello everybody,
i'm working with SAP PI 7.1
I designed my interface IDOC-PI-HTTP.
when i send idoc from R3 i see this message in PI monitor:
HTTP server code 400 reason Bad Request explanation Bad Request
i tried to configure a HTTP port in SM59 and use it in my Communication Channell, but when i test connection i have same error.
I'm using a https address.
have you any suggestion?
thanks
AlexHello,
I already verify with 3 party developer. He confirmed me he is expecting i send data by POST.
Yes, but how does the HTTP Body looks like?See sample webservice below:
http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx?op=GetQuickQuote and scroll down to see how an HTTP POST looks like
Content type is a String
Normally, the content-type for an http post is application/x-www-form-urlencoded. But then, you need to know the prolog and epilog in the http body.
he gave me a url address https://.......
where i need set the parameter HTTPS??
https (http with ssl) is configured in mm59 type G (external server). To enable https, you need to select the SSL folder in which you have installed the CA (certificate authority) certs. Make sure that once you have installed the CA certs, you have performend an ICM Restart.
Hope this helps,
Mark
Edited by: Mark Dihiansan on Jul 25, 2011 11:21 AM -
Incoming payment by F-28: Reason code error while posting
Hello everyone,
I want to post Incoing Payment using F-28 net of TDS. I want the separate GL account to be picked up automatically for the difference when I enter the Reason Code 003.
I did the following customization for the same.
1. Financial Accounting> Accounts Receivable and Accounts Payable> Business Transactions>Incoimng Payments> Incoming Payments Global Settings>Overpayment/Underpayment> Define Reason Codes:- Here I selected the Indicator 'C' for reason code 003 which is for "Indicator: Charge off difference via separate account". The reason code 003 is for TDS Netted
2. Below the Define Reason Code node, I selected the node 'Define Accounts for Payment Differences' . Selected the key ' Rules' and selected the checkbox 'Reason Code'. Then clicked on 'Accounts' and enetered the desired GL account against the reason code '003'.
After doing the above customization I posted the Incoming payment using T code F-28. I entered the difference in the field 'Difference Posting'. Then entered reason code '003' which is for 'TDS netted' in the field 'Reason Code'. Now, I am getting the follwoing error.
Reason codes with automatic charge-off are not permitted here
Message no. F5605
Diagnosis
The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose. Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
System Response
The reason code entered is not accepted.
Procedure
You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.
How can I proceed ahead?
Thanks and Regards,
PradnyaHi Saulo,
Thanks for ur reply.
I had alreay done the config in OBXL and OBBE. Only thing I wanted to know is while posting Incoming Payment by F-28, how to use this reason code.
Ur reply was a gr8 help for me.
Regards,
Pradnya -
Apache Error Log mod_security: Access denied with code 400
Hi
I am seeing the Access denied with code 400 errors in the apache log's after applying CPU Patch updates below into a Dev/TEST environment
RDBMS Patches: 9032412 & 9352191 & post steps below:
@?/rdbms/admin/dbmsaqds.plb
@?/rdbms/admin/prvtaqds.plb
@?/rdbms/admin/prvtaqiu.plb
Java Fix > [ID 1082747.1]
E-Business Suite Patches & post steps below:
9323613 & 9506302
Compiled Forms PLL files using adadmin to solve the known problem below
ORA-04062: signature of package "APPS.FND_HELP" has been changed
ORA-04062: KEY-HELP trigger raised unhandled exception ORA-04062.
the error can be replicated by following the steps below:
Log in to Oracle Apps E-Business Suite (11.5.10.2) select Report Management Information Responsibility and then transaction reports. (Opens Oracle Discoverer 4i Viewer) > select either Period to date or Year to date and then select any department & and any period (date) and then apply parameters:
Error message in browser
This error (HTTP 400 Bad Request) means that Internet Explorer was able to connect to the web server, but the webpage could not be found because of a problem with the address.
For more information about HTTP errors, see Help.
Apache log shows:
error_log shows the following:
[Fri Jul 8 10:52:08 2011] [error] [client 10.180.225.5] mod_security: Access denied with code 400. Pattern match "!^([-_@|#!=A-Za-z0-9/ :.$/(/)]){0,255}([-_@|#!=A-Za-z0-9/ :.$]){0,255}$" at ARGS_NAMES. [hostname "loadbalancer.webdomain"] [uri "/discoverer4i/viewer"] [unique_id ThbTSAq0BRQAABrfK7M]
access_log shows the following:
IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/shadow_bottom02_leading_ltr.gif HTTP/1.1" 200 861 0
IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/seperator.gif HTTP/1.1" 200 42 0
IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/arch_blue_bottom_ltr.gif HTTP/1.1" 200 984 0
10.180.225.5 - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/white.gif HTTP/1.1" 200 37 0
IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/bar_blue_leading_edge_middle_ltr.gif HTTP/1.1" 200 111 0
IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/bar_blue_trailing_edge_middle_ltr.gif HTTP/1.1" 200 129 0
IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/shadow_bottom_leading_edge_ltr.gif HTTP/1.1" 200 862 0
IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/btopshadow.gif HTTP/1.1" 200 44 0
IP ADDRESS- - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/bshadow.gif HTTP/1.1" 200 59 0
IP ADDRESS - - [08/Jul/2011:10:52:08 +0100] "POST /discoverer4i/viewer HTTP/1.1" 400 227 0
I have tried to follow a number of metalink notes but unable to resolve this issue, metalink notes looked at are:
976473.1
389558.1
1313128.1 Patch 10324904 applied
394587.1
389558.1 Patch 5107107 applied
1143882.1
376992.1 Patch 3950067 applied
Any ideas or suggestions most welcome
Thank you
Regards
Arfan
Edited by: user1717313 on 08-Jul-2011 04:59Hi JD
I have tried the steps i.e stop apps tier, run adconfig on apps tiers and then started services on apps tiers and can replicate the error
thanks
Arfan
Hi Helios
I checked note 1080465.1 Patch 9506302 has been applied & Recompile all Forms PLL files using adadmin.
I ran the sql feom the note, output below
SQL> select text from dba_source where name='FND_HELP' and line <3;
TEXT
package Fnd_Help AUTHID CURRENT_USER as
/* $Header: AFMLHLPS.pls 115.22 2009/10/12 12:56:58 nchiring ship $ */
package body FND_HELP as
/* $Header: AFMLHLPB.pls 115.115 2010/03/19 06:45:24 nchiring ship $ */
Thanks
Arfan
Edited by: user1717313 on 08-Jul-2011 05:04 -
Hi experts,
I have a big issue in production server,
the Queues are stuking in smq2 " command to tRFC/qRFC: execute LUW again"
if i am reprocess or press F6 it is going manually.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><html><head><title>Application Server Error</title> <style type="text/css"> body { font-family: arial, sans-serif;} </style> </head> <BODY text="#172972" link="#808080" vlink="#808080" alink="#8e236b" bgcolor=white leftmargin="0" topmargin="0" marginheight="0" marginwidth="0"> <table height="61" width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td background="http://xidist:8000/sap/public/icman/img/bluebar_tile.gif" height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP NetWeaver Application Server </font></td><td width=75% align="right" nowrap><font face=arial size="-1" color="white"><a href="http://help.sap.com/">Help </font></td><td width=5% nowrap></font></td> </tr></table> </td><td rowspan=2 width=122 height=61 valign=top><img src= "http://xidist:8000/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://xidist:8000/sap/public/icman/img/graybar_tile.jpg" height="31"> </td></tr> </table> <br><br> <table width=800> <tr><td width=50 nowrap> </td><td> <H2><b>404 Resource not found</b></H2><br>Partner not reached<br><br><hr> <table border="0"> <tr><td>Error:</td><td>-20</td></tr> <tr><td>Version:</td><td>7000</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Wed May 14 15:50:24 2014 </td></tr> <tr><td>Module:</td><td>icxxconn.c</td></tr> <tr><td>Line:</td><td>2341</td></tr> <tr><td>Server:</td><td>xidist_GXI_00</td></tr> <tr><td>Error Tag:</td><td>{004654a1}</td></tr> <tr><td>Detail:</td><td>Connection request from (110/28816/0) to host: xidist, service: 50000 failed (NIESERV_USED) EX-T110, U28816, 001 PIAFUSER, 10.1.57.50, 15:50:24, M0, W1, , 1/0</td></tr> </table> <p></p> </td></tr></table> <table><tr><td width=50 nowrap></td> <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2009, SAP AG</a></FONT> </td></tr></table> </body></html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Regards,
Kiran polaniDear Sriram Ramani,
in ths case some scenarios are working good. proxy to soap, idoc to soap and jdbc to proxy, proxy to jdbc all are working with out error.
but my problem is in Soap to RFC case..
for all RFC communication channels are working but some time it is throwing RFC_COMMUNICATION_ERROR and messages are stucks in smq2 with retry.
when i check with retry error with in sxmb_moni log showing ICM_HTTP_CONNECTION_FAILED with error code 400.
not for all signals for few signals for some time..
Why it is happening i can't understand.
in repository it is saying Repsitory object hmi failed and address already in use.
is there any problem with loading IR objects.
Please suggest me good suggestion for this type of issue what can do for this to resolve.
Regards,
Kiran Polani -
NPS return Internal Error with Reason Code 1
Hi,
I am having an embedded client which is trying to authenticate using PEAP-MSCHAPv2 using NPS server 2008.
NPS returns this error
Network Policy Server discarded the request for a user.
Contact the Network Policy Server administrator for more information.
User:
Security ID:
SANDBOX\deeps
Account Name:
deeps
Account Domain:
SANDBOX
Fully Qualified Account Name:
SANDBOX\deeps
Client Machine:
Security ID:
NULL SID
Account Name:
Fully Qualified Account Name:
OS-Version:
Called Station Identifier:
Calling Station Identifier:
NAS:
NAS IPv4 Address:
xx.xx.xx.xx
NAS IPv6 Address:
NAS Identifier:
NAS Port-Type:
Wireless - Other
NAS Port:
5
RADIUS Client:
Client Friendly Name:
Deeps_Canopy_AP
Client IP Address:
xx.xx.xx.xx
Authentication Details:
Connection Request Policy Name:
deeps-test
Network Policy Name:
deeps-test
Authentication Provider:
Windows
Authentication Server:
USIL01PMPTST01.sandbox.com
Authentication Type:
EAP
EAP Type:
Account Session Identifier:
Reason Code:
1
Reason:
An internal error occurred. Check the system event log for additional information.
This is not very helpful as it doesn't describe what went wrong and where.
What else logs can I enable to debug further ? Attached are few logs from various components,
Certificate,CRP and Network Policy are fine as they work fine with other standard client.
Please help.
Thanks,
Netlogon logon and it return 0.
4/20 05:31:32 [LOGON] [6480] SANDBOX: SamLogon: Network logon of SANDBOX\deeps from Entered
04/20 05:31:32 [LOGON] [6480] SANDBOX: SamLogon: Network logon of SANDBOX\deeps from Returns 0x0
Logs of NPS IN1504.log
<Event><Timestamp data_type="4">04/20/2015 04:16:16.407</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><User-Name
data_type="1">deeps</User-Name><NAS-IP-Address data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU
data_type="0">1020</Framed-MTU><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 25</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:16.407</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 25</Class><Session-Timeout data_type="0">30</Session-Timeout><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor
data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name
data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name
data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:16.672</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 26</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:16.672</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 26</Class><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Session-Timeout
data_type="0">30</Session-Timeout><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name
data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:16.938</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 27</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:16.938</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 27</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:17.878</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 28</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:17.878</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 28</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:18.141</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 29</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:18.141</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 29</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:18.405</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 30</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:18.405</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 30</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:18.669</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 31</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:18.669</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 31</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:19.629</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 32</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 04:16:19.629</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 32</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:29.898</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><User-Name
data_type="1">deeps</User-Name><NAS-IP-Address data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU
data_type="0">1020</Framed-MTU><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 40</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:29.898</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 40</Class><Session-Timeout data_type="0">30</Session-Timeout><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor
data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name
data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name
data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:30.176</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 41</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:30.176</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 41</Class><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Session-Timeout
data_type="0">30</Session-Timeout><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name
data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:30.441</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 42</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:30.441</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 42</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:31.383</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 43</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:31.383</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 43</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:31.655</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 44</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:31.655</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 44</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:31.920</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 45</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:31.920</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 45</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:32.184</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 46</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:32.184</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 46</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:32.458</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 47</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
<Event><Timestamp data_type="4">04/20/2015 05:31:32.458</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
1 10.120.133.1 04/20/2015 08:26:24 47</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>Hi chitsri,
The log you provided above only contains the successful authentication.
Because standard clients are working fine with NPS, I assume that this issue is caused by the embedded client.
>>What else logs can I enable to debug further ?
We may try to perform a network capture on the NPS server. Then find out what's the difference between the embedded client and standard clients.
To download the the network monitor, please click the link below:
http://www.microsoft.com/en-hk/download/details.aspx?id=4865
If we can't find any hint from the capture data, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
Best Regards.
Steven Lee 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 Support, contact [email protected] -
Proxy issue with SCM - Error code: 400 ICM_HTTP_CONNECTION_FAILED
We have recently added an SCM system to our landscape. I am trying to upload data to BI within SCM. I have set up the method and tested it and it works fine. I am pulling the data in to XI from a flat file and converting it to XML, which works fine, I have tested the payload in the message mapping test tab. When it trys to connect to the SCM system it looks like it hangs forever in sxmb_moni with the error message.
Error when receiving by HTTP (error code: 400,
error text: ICM_HTTP_CONNECTION_FAILED)
I have also created my proxy in SCM, that seems to be fine as well when I test it.
The communication channels are as follows...
Transport Protocol: HTTP 1.0
Message Protocol: XI 3.0
Adapter Engine: Integration Server
Addressing Type: URL Address
Target Host: <hostname>
Service NUmber: 8000
Path: /sap/xi/engine?type=receiver
Auth Type: Use Logon Data for SAP System
SECOND
I cannot see any errors on the Runtime either because my communiation is not showing up... I have saved it and activiated it. The adapter type is XI.
Any help would be appreciated.
Skip FordHi
Error when receiving by HTTP (error code: 400,
error text: ICM_HTTP_CONNECTION_FAILED)
I have also created my proxy in SCM, that seems to be fine as well when I test it.
The communication channels are as follows...
Transport Protocol: HTTP 1.0
Message Protocol: XI 3.0
Adapter Engine: Integration Server
Addressing Type: URL Address
Target Host: <hostname>
Service NUmber: 8000
Path: /sap/xi/engine?type=receiver
Auth Type: Use Logon Data for SAP System
I think the parameter Path for the server proxy should be
/sap/xi/engine?type=entry
Thanks
Gaurav -
Error code: 400, error text: ICM_HTTP_CONNECTION_FAILED
Every now and then we are getting the following error on a synchronous call from XI 3.0.
Error when receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)
Usually it is from XI to R/3 (that's where most of our synch calls take place) but occasionally it happen on a synchronous call to a JDBC comm channel.
It is not just one interface that causes this issue and the same interface will be OK if we re-run it with same data.
I suspect some system parameter is off, or it's just a bug in XI. Any one else run into this ? if so, have you found a fix ? SAP hasn't been much help for us thus far.
Thanks in advance for any help.Hi Tim,
Can you check this thread-
ICM_HTTP_CONNECTION_FAILED
Also check SAP Note 824554,783515,910649,706563.
Cache Refresh~
https://websmp201.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
Hope this helps,
Regards,
Moorthy -
Getting an error code 400..
I have used photoshop elements 10 for over 2 years. now i am getting an error code that says Photoshop.com services are currently not available. Please try again later or contact your network services. Error code 400!
The answer is still the same as it was in your other thread:
http://forums.adobe.com/thread/1282443?tstart=0 -
Attempting to activate WatchABC, get error code 400-1.
I've successfully (according to Charter) activated my AppleTV device but receive error code 400-1 (not authorized). How do I correct this?
Hi JGinLSL,
If you are having issues with the Watch ABC app on your Apple TV, you may find the following page helpful:
Apple TV: Third-party content provider information
http://support.apple.com/kb/HT4799
Regards,
- Brenden
Maybe you are looking for
-
When I download a picture to Desktop it transfers the picture to a folder called Rotated Images no matter which ISP I am using. It also happen if I drop an image /picture onto the desktop: it sits there apx 3 seconds then creates a Rotated Images fol
-
When I import files, the result seems to adhere to the Version Name I enter in the Input Inspector panel. But then, when I'm in Brower Line Mode, I see that the Filename reflects projects I imported a week ago, alongside the correct Version Name. Sho
-
How do i transfer all my old stuff from g4 to my new macbook pro
Hi there, All my itunes songs, gigabytes of pics and all my other info is still on my old g4, it does have ethernet. I want to get all my stuff onto my new mac book pro which will be here in a week or so. obviously without using rw-cds if i can help
-
Can i retrieve deleted photo or video using my icloud account
can i retrieve deleted photo or video using my icloud account
-
I am unable to print main VI due to "image.ccp"
I am abla to print sub VI but when try to print main Vi it says Failure:"image.ccp" line 11326.