Reason Code Log History
Hi, I need to see the Log History of Reason codes that was available in work list. Is there any table or place where can i check the Reason code log history?
Thanks
yadayya
Good Morning!
<b>Reversal Reason code</b> has the following uses in SAP!
1- A document is entered & posted Incorrectly. It must be reversed & re-entered correctly. When you reverse the document, you have to enter reversal reason code that explain the reversal. The reversal reason code also control whether the revrsal date is allowed to be different to the original posting date.
2-there are two types to reverse the document ( 1-Normal Reverse Postinf, 2-Negative Posting). For " Negative posting" the reversal reason code must ve defined for negative reversal in Configuration.
3-Reason code is also user for Accural/ Deferrel
<b>Payment Difference Reason code</b> has the following uses in SAP!
we define reason codes, per company code, for handling payment differences in the form of ,Residual items,Partial payments,Postings on account.
2-Control of the type of Pyment Notice that is sent to Costomer
3-Control the account where a residual item is posted.
4-Automatic posting of residual item to a specfied GL Account.
5-Exclusion of residual item from Customer credit limit check because it is disputed item.
Please reward me point as way of Thanks
Similar Messages
-
Agent logged out suddenly, reason code:50003
Hi,
We have icm 8.0(3) and cad 8.
Sometimes, an agent (each time a different one) is logged out suddenly and he get the reason code: 50003
Please find attached a logout status report that is showing the agent using extension “7459” has been logged out at 13:48:50 and reason code “50003”
I am attaching the CM-pim, opc and ctios logs as well
did anyone have been faced by a simalar issue?
Thanks in advance
GeorgesReason code 50003 says
50003 - Device Failure log out. Call Manager reported that the device is out of service.
From the below trace you can see that PIM has recieved an outofservice event from jgw and we dont have jgw logs but jgw is simply passing the events it received from callmanager.
Line 9: 13:44:46:595 PG1B-pim1 Trace: RecvAddressOutOfService: Couldn't find client stack for device target device string 800
Line 12: 13:44:47:939 PG1B-pim1 Trace: RecvAddressOutOfService: Couldn't find client stack for device target device string 7459
Line 18: 13:46:12:784 PG1B-pim1 Trace: RecvAddressOutOfService: Couldn't find client stack for device target device string 800
Line 19: 13:46:20:065 PG1B-pim1 Trace: RecvAddressOutOfService: Couldn't find client stack for device target device string 7459
Line 43: 13:48:51:021 PG1B-pim1 Trace: RecvAddressOutOfService: Couldn't find client stack for device target device string 800
so you need to investigate why callmanager is reporting out of service event for these phones, if you are using extension mobility and when the user logs out you could see similar messages in the jgw/pim logs
From the PG side you could
-check the connectivity with callmanager,
- check the switch port setting are as per BOM (auto/auto if using gigi interfaces)
- check that the TCP chimney has been disabled on the PG
https://supportforums.cisco.com/docs/DOC-9222
- check PG eventvwr logs to see if you get any clues
If it doesnt help, collect the callmanager SDI/SDL and CTIManager SDI/SDL logs at Detailed level and open a TAC case with CUCM team to investigate why phones are reported as outof service to PG
Thanks,
Shirish -
Security Audit Log Reason Codes
Hello there,
We have an logon failed entry in our Security Audit Log and i am trying to find out what the reason code is. I think it is to do with a failed RFC connection of one of our users. Is there a list somewhere that shows all these failed logon reason codes?
Logon Failed (Reason = 53, Type = H)
Cheers!
Bernard.That would be a failed logon of type HTTP(s) due to the user ID's password being locked from failed logon attempts (USR02-UFLAG = 128 in the ABAP world).
See SAP Note 320991.
Cheers,
Julius -
Security Audit Log Failed Logon Reason Codes
Hi all,
Deos anyone know where i can get a list of the failed logon reason codes and types. For example:
RFC/CPIC Logon Failed, Reason = 53, Type = S
Thanks,,,Hi John,
Check out note 320991
53 = Password lock active (too many failed logons)
S = RFC system call (SRFC) -
Siebel CRM Reason Code Commands
We are needing to enable some commands on the Cisco CTIOS Siebel connector and just not sure where they are enabled or edited at.
We are using connecter provided by CISCO for CTI between Siebel and CISCO. Connector provides the enabled command to Siebel that siebel can send as device command like "DeviceCommand = "ChangeNotReadyState"" using communication configuration DEF file.
Currently we have business requirement:
CTI agents can set their state to NOT READY on a click of button with reason code selected by the agents irrespective of there current state.
We configured the button, but the button is enabled only when the device command "ChangeNotReadyState" is enabled. Can it be possible to enable this button always and we can are able to change agents state at CTIOS level(CISCO)? Can we send "ChangeNotReadyState" command to CISCO irrespective of agents current state
Here is what we have done so far:
We configured DEF according to ORACLE support recommendation (ID 543337.1 listed below in this mail)
RELEVANT PARTIAL DEF FILE:
[Command:DSC_NOTREADY_POP_EXE]
SubCommand_1 = "DSC_NOTREADY_NOPOPUP"
SubCommand_2 = "DSC_NOTREADY_POPUP"
SubCommand_3 = "CleanDashBoard"
Comment = "YQ8279: Add for Direct not ready Button Aug2012"
Description = "Not Ready"
ExecuteAll = "TRUE"
Hidden = "TRUE"
[Command:DSC_NOTREADY_NOPOPUP]
Comment = "YQ8279: Add for Direct not ready Button Aug2012"
Description = "Not Ready"
DeviceCommand = "ChangeNotReadyState"
FilterSpec = "[$GetCommandStatus(ChangeNotReadyState)]= 'Enabled'"
Hidden = "TRUE"
[Command:DSC_NOTREADY_POPUP]
Comment = "YQ8279: Add for Direct not ready Button Aug2012"
Description = "Not Ready"
DeviceCommand = "ChangeNotReadyState"
FilterSpec = "[$GetCommandStatus(ChangeNotReadyState)]= 'Enabled'"
Hidden = "TRUE"
CmdData = "PopupforReason"
[CmdData:PopupforReason]
Comment = "YQ8279: Add for Direct not ready Button Aug2012"
Param.ReasonCode = "[Name]"
SelectApplet = "Transfer Multiple LOV Popup Applet"
SelectBusComp = "List Of Values"
SelectBusObj = "List Of Values"
SelectParam = "TRUE"
SelectQuerySpec = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
SelectTitle = "Please select the reason for changing status to Not-Ready"
So with above configuration suggested by oracle support we are sending "ChangeNotReadyState" device command twice in a manner so that it will be processed one after the other. But it is not happing, second command is not going through as its not enabled after Siebel issued it once. Please see below logs and highlights.
SCOMM LOG: <In Time Context >
ChangeNotReadyState Command is enabled (status = 16)
see image 1 on attached doc
Now user applied the command once :
See Image 2 on attached doc
Now "ChangeNotReadyState" device command is disabled .
Can we make it "ChangeNotReadyState" enabled via connecter always by making some registry setting or some setup.
See image 3 on attached doc
Oracle Support Suggestion:
Not able to select Not Ready Reason Code [ID 543337.1]
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=485718774714219&type=DOCUMENT&id=881215.1&displayIndex=4&_afrWindowMode=0&_adf.ctrl-state=dhq5nrae7_147
Symptoms
In the current production we are having some CTI agents facing problem with picking the AUX Codes (Reason Codes) when trying to change status for Not Ready.
Some of the agents reported that they can NOT pick the reason codes ( probably the icon is disabled for some reason at some point of time). I tried to reproduce the problem, but not happened.
Our objective is to not receive the call and make the agent click the AUX Code (Not Ready Reason Code).
Cause
Users were not able to pick the auxiliary code (reason code) at Siebel web client under using Genesys Gplus 7.0.000.1. Agent objective was to not receive the call and be able to click the AUX Code.
During the operation of selecting an auxiliary code (aux code dialog open or not ready reason code applet) an incoming call reaches the agent before he decide which aux code to user not allowing selecting the reason code.
The GPlus driver at this point did not receive the not ready command and is in ready state for this agent allowing new calls.
Solution
Suggestion was to define first the not ready state for the GPlus with the default reason code = -1. Now agent is on a not ready state allowing enough time for agent to perform the selection.
Then we can call another communications command that starts the popup for the LOV of aux codes.
Here the agent will have enough time to pick the code with no more inbound calls.
The device commands for the command group are as follow:
[Command:NotReadyForGVoiceGroup]
SubCommand_1 = "NotReadyForGVoiceStd"
SubCommand_2 = "NotReadyForGVoiceAuxCode"
SubCommand_99 = "NotReadyForGVoiceEnabler"
Description = "Set not redy for voice"
Hidden = "TRUE"
ExecuteAll = "TRUE"
[Command:NotReadyForGVoiceStd]
Description = "Set not ready for voice"
DeviceCommand = "NotReady"
Hidden = "True"
Title = "Voice not Ready"
CmdData = "NotReadyAuxCode"
[CmdData:NotReadyAuxCode]
Param.ReasonCode = "-1" ; Check manual Gplus Adapter for Siebel 7—Deployment Guide page 241 for the value.
[Command:NotReadyForGVoiceAuxCode]
Description = "Seçect Reason Code for Voice"
DeviceCommand = "NotReady"
FilterSpec = "[$GetCommandStatus(NotReady)] = 'Enabled'"
Hidden = "True"
HotKey = "Alt+A"
Title = "Aux Mode"
Profile = "Gplus Voice1"
CmdData = "ReasonCodePopup"
[CmdData:ReasonCodePopup]
Param.ReasonCode = "[Name]"
Param.ReasonValue = "[Value]"
Param.StringAttributeExtensions = "ReasonCode,ReasonValue"
SelectApplet = "Value Type Pick Applet"
SelectBusComp = "List Of Values"
SelectBusObj = "List Of Values"
SelectParam = "TRUE"
SelectQuerySpec = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
SelectTitle = "Please select the reason for changing status to Not-Ready"Thanks for your response Cherilynn,
You are correct for a vanilla agetn desktop. However, if the agent has to become available to move from one aux reason to another, the agent may get a call in that process. With customiization, we can allow changing from one aux code to another without having to make the agent ready. Oracle suggested a solution but to do this, we need to enable and modify certain parameters within Cisco. What we are trying to find out is where are these parameters set, ex: AgentWorkMode and AgentWorkMode2, ChangeNotReadyState...
ORACLE SUPPORT SR
Not able to select Not Ready Reason Code [ID 543337.1]
SymptomsIn the current production we are having some CTI agents facing problem with picking the AUX Codes (Reason Codes) when trying to change status for Not Ready.
Some of the agents reported that they can NOT pick the reason codes ( probably the icon is disabled for some reason at some point of time). I tried to reproduce the problem, but not happened.
Our objective is to not receive the call and make the agent click the AUX Code (Not Ready Reason Code).
CauseUsers were not able to pick the auxiliary code (reason code) at Siebel web client under using Genesys Gplus 7.0.000.1. Agent objective was to not receive the call and be able to click the AUX Code.
During the operation of selecting an auxiliary code (aux code dialog open or not ready reason code applet) an incoming call reaches the agent before he decide which aux code to user not allowing selecting the reason code.
The GPlus driver at this point did not receive the not ready command and is in ready state for this agent allowing new calls.
SolutionSuggestion was to define first the not ready state for the GPlus with the default reason code = -1. Now agent is on a not ready state allowing enough time for agent to perform the selection.
Then we can call another communications command that starts the popup for the LOV of aux codes.
Here the agent will have enough time to pick the code with no more inbound calls.
The device commands for the command group are as follow:
[Command:NotReadyForGVoiceGroup]
SubCommand_1 = "NotReadyForGVoiceStd"
SubCommand_2 = "NotReadyForGVoiceAuxCode"
SubCommand_99 = "NotReadyForGVoiceEnabler"
Description = "Set not redy for voice"
Hidden = "TRUE"
ExecuteAll = "TRUE"
[Command:NotReadyForGVoiceStd]
Description = "Set not ready for voice"
DeviceCommand = "NotReady"
Hidden = "True"
Title = "Voice not Ready"
CmdData = "NotReadyAuxCode"
[CmdData:NotReadyAuxCode]
Param.ReasonCode = "-1" ; Check manual Gplus Adapter for Siebel 7—Deployment Guide page 241 for the value.
[Command:NotReadyForGVoiceAuxCode]
Description = "Seçect Reason Code for Voice"
DeviceCommand = "NotReady"
FilterSpec = "[$GetCommandStatus(NotReady)] = 'Enabled'"
Hidden = "True"
HotKey = "Alt+A"
Title = "Aux Mode"
Profile = "Gplus Voice1"
CmdData = "ReasonCodePopup"
[CmdData:ReasonCodePopup]
Param.ReasonCode = "[Name]"
Param.ReasonValue = "[Value]"
Param.StringAttributeExtensions = "ReasonCode,ReasonValue"
SelectApplet = "Value Type Pick Applet"
SelectBusComp = "List Of Values"
SelectBusObj = "List Of Values"
SelectParam = "TRUE"
SelectQuerySpec = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
SelectTitle = "Please select the reason for changing status to Not-Ready"
Regards,
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=485718774714219&type=DOCUMENT&id=881215.1&displayIndex=4&_afrWindowMode=0&_adf.ctrl-state=dhq5nrae7_147 -
Agent going to not ready after call hangup, Siebel CRM Connector, reason code 50002
Hi Everyone,
We have Contact Center Enterprise UCCE 8.5.2 with CTOS integrated Siebel CRM 8.1.1 using
Cisco Unified CRM connector
On daily basis we are receiving about 100 incidents that Agents goes to not ready after
talking to customer. and the reporting gives the reason code 50002.
As per Cisco its because of CTI server Failure/Agent desktop closed/network Problem. But
In real there is no network issue, Agent not closing the Agent desktop. Also if this is
the case agent should be logged out but in pratical its stays logged in but moved to
not-ready state(Reason 50002)
It could be miss communication between UCCE and Siebal CRM connector.
One more thing its not happening with one customer only it happening in many deployment on
Version 8. Especially the one integrated with Siebel.
If anyone face the same issue please share the experience and the solution if found any!
Regards,
Atif TanveerAtif,
If memory serves me right, CTI events are controlled and communicated by Siebel connector. So when your users close Siebel or any other CTI controlling connector this will be same as closing CTIOS or CAD without proper logoff. This will keep the phone out of synch and keep the user automatically into not ready to prevent any callers going to this device.
Simple answer you have to train users and make sure they close Close applications properly.
Thanks,
Baseer. -
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] -
Reason Code - several questions
Hi all
I have checked FAQ, discussions, help etc, but I could not find any reply to the following questions:
1) If I am in excel changing a value and get my popup with the reason codes assigned to the roles,
the order of the reason codes seem to be complete random, at least it is neither alphabetical for the technical name nor the description.
HOW is the order? How can I influence display order?
Business Case is that depending on the process, one user has different subset of reason codes
2) Evaluation of reason codes:
Currenty with JAM, you can not evaluate Reason Codes systematically, it is just a series of feeds, wich does not meet our requirements
With Change History, you have more possibilities for evaluation in URL-UI
Is there any possibility / workaround / development planned that we can have these reason codes in Excel already?
Business Case is that if the planner works on a material, he wants to see the reason codes in excel directly,
so he knows while planning on one view all reason codes given.
3) Is there any chance that we can set up thresholds for reason codes? Any workaround? Any development planned?
Business Case is that we dont want to have reason code if we just make a minor change, but e.g. only when the change is higher than 5%
This is a repeating question we get from different persons / roles from customer
Thanks
IrmiHi Irmi,
#1. We faced this issue in my previous project but could not determine the sorting order of the reason codes. They appear to be random. We checked to see if it's in the order they were created but that did not seem to be it either.
#2. Can you select by the hash tag? such as #upside? Try to do that in Feed and you should be able to display only the ones that your searched for.
#3. If reason codes are set up for your user, they will pop up no matter the change. One way to do this is to create a RC saying <5% change and just ignor those feeds.
thank you -
Kamala -
Since we upgraded our WCS system to V6.0.196.0 we are receiving a lot of the following error messages and I haven't figured out why.
Client 'c0:cb:38:3f:a1:0d (anonymous, 0.0.0.0)' which was associated with interface '802.11a/n' of AP 'ACAA01-00.P04-G2C2.1' is excluded. The reason code is '4(802.1X Authentication failed 3 times.)'. - Controller Name: 205-dg20-bb3-4/2Check you ACS (Radius) logs under failures. You will see why its failing. Sounds like a AD account went bad
or someone is entering the wrong logon ... But check your radius log it will point you in the right direction. -
Calls Getting disconnected with reason code 26
Hi,
Few of my calls are getting disconnected with reason code 26. on agent screen it just flash and disconnect.as per RCD its showing Error code 0( fine) and finally its ending at Skill Group Node. talk time is 1 or 2 seconds. agents having auto answer setting as well as IP Phone set auto ans with headset.
my setup is IPIVR based UCCE setup.
Please help
Regards-
PKHi PK,
CD 26 normally indicates Resource Not available in CUCM side. please check the Jtapi gateway process logs for the failed calls. you should be able to see something similar to below
19:08:37:896 PG1A-jgw1 Trace: ConnFailedEv CID: 27224748 Addr: 80002985 CiscoCause: CAUSE_RESOURCESNAVAIL Cause: CAUSE_RESOURCES_NOT_AVAILABLE.
if that is the case , please check from CUCM perspective as well.
Regards,
Sasikumar. -
NPS SQL missing reason-code in Server 2012 R2
Hi
It seems like several SQL fields in the 2012 R2 version of NPS logging has been removed.
Amongst others the Reason-Code field.
Most people only refer to log files to see why someone can't connect to the vpn server.
In previous versions we had a web front end for an sql view that gave you the reason why the server denied access so that we do not need to give helpdesk personnel access to the log files and we also filter which operations vpn sessions they can see (via
multiple vpn nps policies and then filter the sql view based on their permissions).
Is there any way to restore the logging of this field to SQL as well as logging the source IP address of the request (our investors requires this and we get audited on it) with the issued IP (non DHCP). We are not allowed to run DHCP on this server since
it is situated in the 3rd party datacenter.
Regards
JohanAnd this is what Server 2008R2 had parsed in the default stored procedure:
FROM
OPENXML(@idoc,
'/Event')
WITH
Computer_Name
nvarchar(255)
'./Computer-Name',
Packet_Type
int
'./Packet-Type',
[User_Name]
nvarchar(255)
'./User-Name',
F_Q_User_Name
nvarchar(255)
'./Fully-Qualifed-User-Name',
Called_Station_Id
nvarchar(255)
'./Called-Station-Id',
Calling_Station_Id
nvarchar(255)
'./Calling-Station-Id',
Callback_Number
nvarchar(255)
'./Callback-Number',
Framed_IP_Address
nvarchar(15)
'./Framed-IP-Address',
NAS_Identifier
nvarchar(255)
'./NAS-Identifier',
NAS_IP_Address
nvarchar(15)
'./NAS-IP-Address',
NAS_Port
int
'./NAS-Port',
Client_Vendor
int
'./Client-Vendor',
Client_IP_Address
nvarchar(15)
'./Client-IP-Address',
Client_Friendly_Name
nvarchar(255)
'./Client-Friendly-Name',
Event_Timestamp
datetime
'./Event-Timestamp',
Port_Limit
int
'./Port-Limit',
NAS_Port_Type
int
'./NAS-Port-Type',
Connect_Info
nvarchar(255)
'./Connect-Info',
Framed_Protocol
int
'./Framed-Protocol',
Service_Type
int
'./Service-Type',
Authentication_Type
int
'./Authentication-Type',
NP_Policy_Name
nvarchar(255)
'./NP-Policy-Name',
Reason_Code
int
'./Reason-Code',
Class
nvarchar(255)
'./Class',
Session_Timeout
int
'./Session-Timeout',
Idle_Timeout
int
'./Idle-Timeout',
Termination_Action
int
'./Termination-Action',
EAP_Friendly_Name
nvarchar(255)
'./EAP-Friendly-Name',
Acct_Status_Type
int
'./Acct-Status-Type',
Acct_Delay_Time
int
'./Acct-Delay-Time',
Acct_Input_Octets
int
'./Acct-Input-Octets',
Acct_Output_Octets
int
'./Acct-Output-Octets',
Acct_Session_Id
nvarchar(255)
'./Acct-Session-Id',
Acct_Authentic
int
'./Acct-Authentic',
Acct_Session_Time
int
'./Acct-Session-Time',
Acct_Input_Packets
int
'./Acct-Input-Packets',
Acct_Output_Packets
int
'./Acct-Output-Packets',
Acct_Terminate_Cause
int
'./Acct-Terminate-Cause',
Acct_Multi_Session_Id
nvarchar(255)
'./Acct-Multi-Session-Id',
Acct_Link_Count
int
'./Acct-Link-Count',
Acct_Interim_Interval
int
'./Acct-Interim-Interval',
Tunnel_Type
int
'./Tunnel-Type',
Tunnel_Medium_Type
int
'./Tunnel-Medium-Type',
Tunnel_Client_Endpoint
nvarchar(255)
'./Tunnel-Client-Endpt',
Tunnel_Server_Endpoint
nvarchar(255)
'./Tunnel-Server-Endpt',
Acct_Tunnel_Connection
nvarchar(255)
'./Acct-Tunnel-Connection',
Tunnel_Pvt_Group_Id
nvarchar(255)
'./Tunnel-Pvt-Group-Id',
Tunnel_Assignment_Id
nvarchar(255)
'./Tunnel-Assignment-Id',
Tunnel_Preference
int
'./Tunnel-Preference',
MS_Acct_Auth_Type
int
'./MS-Acct-Auth-Type',
MS_Acct_EAP_Type
int
'./MS-Acct-EAP-Type',
MS_RAS_Version
nvarchar(255)
'./MS-RAS-Version',
MS_RAS_Vendor
int
'./MS-RAS-Vendor',
MS_CHAP_Error
nvarchar(255)
'./MS-CHAP-Error',
MS_CHAP_Domain
nvarchar(255)
'./MS-CHAP-Domain',
MS_MPPE_Encryption_Types
int
'./MS-MPPE-Encryption-Types',
MS_MPPE_Encryption_Policy
int
'./MS-MPPE-Encryption-Policy',
Proxy_Policy_Name
nvarchar(255)
'./Proxy-Policy-Name',
Provider_Type
int
'./Provider-Type',
Provider_Name
nvarchar(255)
'./Provider-Name',
Remote_Server_Address
nvarchar(15)
'./Remote-Server-Address',
MS_RAS_Client_Name
nvarchar(255)
'./MS-RAS-Client-Name',
MS_RAS_Client_Version
nvarchar(255)
'./MS-RAS-Client-Version',
NAP-specific information, available from NPS starting with Windows Server 2008. -
Background: I am new to SAP GRC. We are in the process of upgrading from 4.0 to 5.2. I am focusing on FF and CC.
My question pertains to FF.
When logging in as a firefighter in 4.0, it is a free-form to enter your reason and activity.
When logging in as a firefighter in 5.2, it has been changed to choosing from a list of mandatory "reason codes".
Is there a way to revert back to the old method in entering free-form text as opposed to choosing from a list of reason codes? The user/config guide does not specify.
Thanks in advance!
- Jes BehrensHello Jes,
As Ankur just mentioned that you have to maintain reason codes in advance but the reason text field is a free text for sure. That's right, and this should be the best practice as well. Now the reports are much more efficient. There is a new dedicated report called Reason / Activity Report
This report can be generated by Reason Code, Firefighter ID, Firefighter ID Owner, or by Session Date. So it would be great if you discuss this with Business process Owners and decide what reason codes would be appropriate.
Suppose you have a reason code for basis activities, and later on your management want's to see what were the activities performed by basis team in over a month or more, in this case you can simply go to Reason/Activity report and select an appropriate reason code and wow here what do you have?
the whole list of basis activities. wow, don't you think it is an amazing functional addition on FF 5.2 well my company love this feature.
Best Regards,
Amol Bharti -
Reason code 105 for LastOutOfServiceInformation
Hello,
I have one client with CUCM 8.6.2.21900-5 with 79XX IP phones running this firmware:
SCCPXX.9-2-3S.
The IP Phones are loosing the register with CUCM, on the RTMT i see these logs:
ccm: 524188: CUCM01.localdomain: Jan 20 2014 13:16:34.385 UTC : %UC_-3-LastOutOfServiceInformation: %[DeviceName=SEPf0f75584db02][DeviceIPv4Address=192.168.4.238/23][IPv4DefaultGateway=192.168.5.254][DeviceIPv6Address=][IPv6DefaultGateway=][ModelNumber=CP-6921][NeighborIPv6Address=][NeighborIPv4Address=192.168.0.219][NeighborDeviceID=SW01][UNKNOWN_PARAMNAME:NeighborIPortID=GigabitEthernet1/0/19][DHCPv4Status=1][DHCPv6Status=1][TFTPCfgStatus=1][UNKNOWN_PARAMNAME:DNSStatusCUCM1=4][VoiceVLAN=4][UNKNOWN_PARAMNAME:CUCMIPAddress=192.168.4.10][LocalPort=35315][TimeStamp=3182386][ReasonForOutOfService=105][LastProtocolEventSent=0x1][LastProtocolEventReceived=0x9d][ClusterID=StandAloneCluster][NodeID=CUCM01]: Information related to the last out-of-service event
On this doc (https://supportforums.cisco.com/docs/DOC-27668) i see what means this reason code:
105 - The device closed the TCP connection due to a restart triggered internally by the device because device failed to download the configuration or dial plan file.
What can i do for solve this issue?
Regards
Leonardo SantanaSomeone?
-
Can someone please point me to a complete list with explanations of the wake reason codes seen in the Console system log.
Various posters have stated this or that code means one thing or another, but no one has said where they got the information or posted a complete list. Thanks.We pick up information from other users, from reading books about OS X, from using the knowledge base in the Apple support site, from joining the Developers site and searching their knowledge base, searching Google, etc.
Did you have specific console messages in mind? Yu can post questions about such information in the developer forums rather than in these forums. -
UCCE Agent_Logout table reason code 0
Hi all,
It is a UCCE system 9.0
we faced an issue last saturday, all the agents got logged_out from their cisco phones and then they were able to log in again.
when checking the reason code at that time in the agent_logout table I noticed that its value was 0.
has anyone encountered a similar issue? and what does the reason code 0 mean?
Thank you in advance
LaraLara,
could you please post a few rows from the Agent_Event_Detail (or if it's enabled, the Agent_State_Trace) database views? I would like to see the Not Ready reason code for the event that preceeded the Logout event.
Reasons may be plenty. For instance, agent phone lost connection to the CUCM and reset.
G.
Maybe you are looking for
-
Is there a way to take my video recorded at regular speed and create a slow motion effect with it? Thanks!
-
There are 2 users on our computer; I am the administrator. On the 2nd user's page, the AVG Secure Search page comes up despite changing the home page, deleting AVG Anti Virus, and it is not listed where one manages the search engines (we use Ixquick)
-
ITunes store-bought Digital Booklet won't open
I downloaded Avenged Sevenfold's Hail to the King Deluxe Version and the .pdf file Digital Booklet won't open. Adobe Reader says the file is damaged, is there any way to get around that?
-
I can't reinstall creative cloud after uninstalling everything due to updating errors. Please help
I uninstalled creative cloud because my apps continued to fail updating. So I uninstalled all of my apps and creative cloud it self to try again with a clean slate. Now I can't even download the CC desktop. Please help I'm running OSX 10.9.4
-
Stop importing contacts from email account
New iphone 4 imported ALL emails address sent to into my contacts. How do i stop this?