Agent Logs under agent names shows no information in CSD

I have 1 supervisor and that supervisor needs to see the agent logs under each individual agent name but for some reason there is nothing being reported there. If an agent takes a call or makes a call, inbound or outbound will appear under the agent name with data but logs just will not show anything. Is there a setting somewhere i'm missing?          

You may have already checked this and apologize if you did, but have you verified that the supervisor is configured to see the columns under the Logs?
In Supervisor, go to View - Preferences.  In the window that appears, go to Team - Agent - Logs and click on "Configure" on the right side, in the "Columns" field.  Make sure that the columns have a check mark next to them.
If that is ok, have you tried running Supervisor from a different machine to see if that works?

Similar Messages

  • My iphone is stolen .. is there any way to know the numbe of the person going to use in the future .. I have the serial no. and every thing .. and it is registered under my name and my information with iTunes ??

    my iphone is stolen .. is there any way to know the numbe of the person going to use in the future .. I have the serial no. and every thing .. and it is registered under my name and my information with iTunes ??

    If you had find my iphone activated on the iphone itself before it was stolen, then you may be able to track it.
    Otherwise, there is nothing you can do.
    Sorry.
    Report it to the police and your wireless carrier and change your password.

  • Sequence Quiz Using User Defined Variables - Can See Underlying Variable Name On Move

    I have just tested using 1 slide to capture several user defined variables and the next slide to insert those variables as options in a sequence quiz slide.
    This works but as soon as I grab an object to begin sequencing them the underlying variable name shows up alongside the variable content.
    Am wondering if I am attempting something that shouldn't be possible in Captivate and / or if there is a fix?
    Thanks

    Sure, I'm using Captivate 8. On a test project I've created:
    a slide with 2 text entry boxes, their contents are stored in variables
    another slide with a sequence question (using the native captivate question slide)
    The labels on the 2 sliders on the question slide use the variables from the previous slide.
    This works, so if the variables are as follows:
    $$data_sequence1$$ - "blah blah blah"
    $$data_sequence2$$ - "blah"
    The labels on the sliders on the sequence question will be "blah blah blah" and "blah".  as intended.
    The issue is when I click one of the sliders to drag it to sequence the variable name will flash up on screen. So if I touch the slider with the label "blah blah blah" $$data_sequence1$$ will flash up on screen.
    I have other slides on there but these are the two related to this question. I haven't fully published the project I've previewed it.

  • Cisco Supervisor Desktop show "Agent Logs - call" and "Agent Logs - state" in N/A ::: UCCX 8.5.1

    Hi team.
    The Cisco Supervisor Desktop don't show any logs in the "Agent Logs - State" and "Agent Logs - Call" in some agents.
    I restarted the Cisco Desktop Services in CCX Serviceability but the issue continue.
    I appreciate any help respect this case.
    Thanks a lot.
    ErnestoG

    Hi Ernesto,
    Did you click or selct the Specific Agent\Inbound call which is currently being handled by the Agent. From the Screenshot you have attached (first one) doesn't look like the call has been selected.
    Please select or click on that Specific Agent\Inbound call from CSD and check these values.
    Hope this helps.
    Anand
    Please rate helpful posts !!

  • Does Log reader agent use sa in sp_replcmds?

    We have publisher, subscriber, and distributor on separate servers. Replication is Push Transactional with replication agents setup to run under SQL Agent account context. We are in the process of disabling sa from everywhere and I am monitoring sessions
    that use sa to make sure there is no impact.
    I see that log reader agent session sometimes uses sa as login name in its sessions on publisher. In sys.dm_exec_sessions, there are two columns for login: Login_Name and Original_Login_Name. The Login_Name shows sa. Most of the time the SPID of log reader
    agent on publisher shows the SQL agent service account as login name of the session. But sometimes the same SPID shows sa as login name. This always coincides with session running SP_REPLCMDS without any parameters and also messages like "The Log Reader
    Agent is scanning the transaction log for command to be replicated. Approximately...." in Replication Monitor. Normally, the session would run SP_REPLCMDS giving some parameters. When this happens, in sys.dm_exec_sessions, the log reader SPID keeps showing
    Original Login name as that of Distributor agent service account but login_name sa.
    Does sp_replcmds run as sa? If I disable sa on publisher, distributor, and subscriber, will it break replication?

    it all depends on what accounts you have set for log reader agent security, distribution agent security and snapshot agent security etc.. If you have not configured anything to use sa then you can disable and it should not have an issue.
    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

  • Log Reader Agent error "could not execute sp_replcmds' and causes stack dump

    Publisher/Subscriber db:  SQL 2008 R2, 2000 compatability mode
    Distributor database is on separate server.
    (note:  There is another database on this instance that is running replication without error, it is not in compatibility mode)
    After snapshot agent finishes, the log reader agent starts and fails immediately with this error in the Agent Job.
    Then I get a SEV20 error and stack dump in the error logs.
    Date  6/12/2014 3:12:26 PM
    Log  Job History (SERVER\INSTANCE-DBNAME-43)
    Step ID  2
    Server  ######RT02
    Job Name  SERVER\INSTANCE-DBNAME-43
    Step Name  Run agent.
    Duration  00:00:01
    Sql Severity  0
    Sql Message ID  0
    Operator Emailed  
    Operator Net sent  
    Operator Paged  
    Retries Attempted  0
    Message
    2014-06-12 20:12:26.302 Copyright (c) 2008 Microsoft Corporation
    2014-06-12 20:12:26.302 Microsoft SQL Server Replication Agent: logread
    2014-06-12 20:12:26.302
    2014-06-12 20:12:26.302 The timestamps prepended to the output lines are expressed in terms of UTC time.
    2014-06-12 20:12:26.302 User-specified agent parameter values:
       -Publisher SERVER\INSTANCE
       -PublisherDB DBNAME
       -Distributor ######RT02
       -DistributorSecurityMode 1
       -Continuous
       -XJOBID 0x8958DF32810C6849B28A037A8FF8DD92
       -XJOBNAME SERVER\INSTANCE-DBNAME-43
       -XSTEPID 2
       -XSUBSYSTEM LogReader
       -XSERVER SERVER\INSTANCE
       -XCMDLINE 0
       -XCancelEventHandle 0000000000000F98
       -XParentProcessHandle 0000000000000F34
    2014-06-12 20:12:26.459 Parameter values obtained from agent profile:
       -pollinginterval 5000
       -historyverboselevel 1
       -logintimeout 15
       -querytimeout 1800
       -readbatchsize 500
       -readbatchsize 500000
    2014-06-12 20:12:26.493 Status: 4096, code: 20024, text: 'Initializing'.
    2014-06-12 20:12:26.493 The agent is running. Use Replication Monitor to view the details of this agent session.
    2014-06-12 20:12:27.885 Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.'.
    2014-06-12 20:12:27.886 The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.
    2014-06-12 20:12:27.886 Status: 0, code: 21, text: 'Warning: Fatal error 3624 occurred at Jun 12 2014  3:12PM. Note the error and time, and contact your system administrator.'.
    2014-06-12 20:12:27.886 Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.'.
    I've tried removing replication and setting it back up again, restarting SQL, and restarting the server itself.
    Let me know if you need any more information to help troubleshoot.  Thanks.
    Please help, thanks. 

    Hi,
    Enable Verbose logging and check the results.
    Execute following commands: -Output C:\Temp\OUTPUTFILE.txt –Outputverboselevel 2.
    Please refer following KB article for your reference -
    http://support.microsoft.com/kb/q312292/
    Thanks.
    Tracy Cai
    TechNet Community Support

  • This log -------------policy agent 2.1 for iis5.0

    Sun Java System Identity Server Policy Agent 2.1 for Microsoft IIS 5.0
    Sun\Identity_Server\Agents\2.1\debug\C__Inetpub_wwwroot\amAgent
    2004-07-25 18:06:22.156 Warning 1064:00D01120 PolicyAgent: OnPreprocHeaders(): Identity Server Cookie not found.
    2004-07-25 18:06:22.156 Error 1064:00D01120 PolicyAgent: do_redirect() ServerSupportFunction did not succeed: Attempted status = 302 Found
    2004-07-25 18:06:22.156 Warning 1064:00D01120 PolicyAgent: OnPreprocHeaders(): No cookies found.
    2004-07-25 18:06:22.156 Error 1064:00D01120 PolicyAgent: do_redirect() ServerSupportFunction did not succeed: Attempted status = 302 Found
    2004-07-25 18:07:53.921 Error 1064:00D01120 PolicyEngine: am_policy_evaluate: InternalException in Service::getPolicyResult with error message:Policy not found for resource: http://guorui.mygodsun.com:49153/index.asp and code:7
    2004-07-25 18:07:53.921 Warning 1064:00D01120 PolicyAgent: am_web_is_access_allowed(http://guorui.mygodsun.com:49153/index.asp, GET) denying access: status = no policy found (7)
    2004-07-25 18:07:53.937 128 1064:00D01120 RemoteLog: User amAdmin was denied access to http://guorui.mygodsun.com:49153/index.asp.
    2004-07-25 18:07:54.062 Error 1064:00D01120 PolicyAgent: do_redirect(): Error while calling am_web_get_redirect_url(): status = success
    2004-07-25 18:07:54.078 Error 1064:00D01120 PolicyAgent: do_redirect() WriteClient did not succeed: Attempted message = HTTP/1.1 403 Forbidden
    Content-Length: 13
    Content-Type: text/plain
    403 Forbidden
    from that log,help me
    my:
    Sun Java System Identity Server 6.1
    Sun Java System Directory Server 5.2
    Sun Java System Identity Server Policy Agent 2.1 for Microsoft IIS 5.0
    help me for that how config?
    what error ?
    thanks!

    Sorr for so many people faced the sam or similar issues. I just joined this support a short while. If you think any old problem which is still critical to you, please repost. We shall try our best to give you assistance. Jerry
    Here are some of tips for debugging Web agent.
    From the AMAgent.properties, are both IIS and AM are in the same domain? If they are not, then you need to use CDSSO. Also please check in AM, under "Service Configuration-> Platform -> Cookie Domains" , whether cookie is set for the entire domain which includes AM and IIS ("test.com") or just the AM machine name.
    Also check whether correct value for "Agent-Identity Server Shared Secret" is entered. This should be your internal ldap password (amldapuser). In the AMAgent.properties for the below property the password will be encrypted and assigned: "com.sun.am.policy.am.password".
    Could you also check if the Identity servver and the IIS web server are time synchronized. The problem may be that agent requests policy decisions and the response from server may be timed out due to non-syncrhonized clock.
    Don't forget to restart the whole IIS service using internet
    management console after making agent changes.
    Some of the common error codes:
    20: Application authentication failed. This occurs when Agent cannot sucessfully authenticate with Identity Server. This is mainly due to incorrect password for agent entered during agent installation. Please refer to another faq describing how to change password.
    7: Policy not found. This error occurs typically if there are no policies defined on Identity server for the given web server URL. Otherwise, there may be time skew between Identity Server and Agent. So, polices fetched from Identity Server is instantly flushed by Agent and attempted to refetch over and over again. This can be solved by running rdate or similar command to synchronize time between the two machines. It is recommended to run NNTP server syncrhonize times between your Identity systems.

  • The process could not execute 'sp_repldone/sp_replcounters' error for Log Reader Agent and SQL Server Assertion 17066 & 3624 errors in SQL Logs

    One of our SQL Server started creating SQLDUMP file and and on investigation I found the error longs are filled with Errors 3624 & 17066. There is transnational replication configured on one of the databases is the LogReader Agent is failing error "The
    process could not execute 'sp_repldone/sp_replcounters' on XXXXX". 
    Not sure if both these Assertion & Logreader Agent errors are related. Before I remove and put the replication, I wanted to check if anyone has experienced the same issues or aware of what the cause. 
    ***********Error messages from SQL Logs******
    **Dump thread - spid = 0, EC = 0x0000000111534460
    Message
    A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to
    Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
    Error: 3624, Severity: 20, State: 1.
    SQL Server Assertion: File: <logscan.cpp>, line=2123 Failed Assertion = 'UtilDbccIsInsideDbcc () || (m_ProxyLogMgr->GetPru ()->GetStartupState () < RecoveryUnit::Recovered)'. This error may be timing-related. If the error persists after rerunning
    the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
    Error: 17066, Severity: 16, State: 1.
    External dump process return code 0x20000001.
    External dump process returned no errors.
    Thank you in advance.

    You need to determine if this error is a transient one or a show stopper one.
    It sounds like your log reader agent has crashed and can't continue.
    If so your best bet is to call Microsoft CSS and open a support incident.
    It also sounds like DBCC CHECKDB was running while the log reader agent crashed.
    If you need to get up and running again run sp_replrestart, but then you might find that replicated commands are not picked up. You will need to run a validation to determine if you need to reinitialize the entire publication or a single article.
    I have run into errors like this, but they tend to be transient, ie the log reader agent crashes, and on restart it works fine.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • Ctios - agent log in error

               Any solution for this issue.
    Agent not able to log in agent desktop,
    error returns
    [agent.5001.6251]::Login()
    08/01/13 08:16:36.082  6768  CTIOSSoftphone  Thd(00000900)  [agent.5001.6251]::SetAgentState()
    08/01/13 08:16:36.082  6768  CTIOSSoftphone  Thd(00000900)  CCtiOsSession::MakeRequest(eSetAgentStateRequest)
    08/01/13 08:16:36.348  6768  CTIOSSoftphone  Thd(00004084)  [agent.5001.6251]::OnQueryAgentStateConf()
    08/01/13 08:17:36.692  6768  CTIOSSoftphone  Thd(00004084)  [agent.5001.6251] eControlFailureConf : (PeripheralID:5001 FailureCode:78
      PeripheralErrorCode:0 AgentID:6251 UniqueObjectID:agent.5001.6251
      MessageID:eControlFailureConf MessageType:eSetAgentStateRequest
      ErrorMessage:The request failed because a timeout limit was exceeded.
    But able to log in other device with the same agent login credentials.
    Tried,
    Restarted the computer
    Restart \ Reset the IP Phone
    Disassociate \ associate the device in pg user in call manager
    Reconfigured the device profile \ Line configuration
    Reconfigured the Agent profile \ device target in ICM
    Restarted the cti manager services in call manager.
    The issue still exists, any thaughts or resolution steps or advices will be acceptable...

    Thanks you all for the response & sorry for the belated response.
    As mentioned, deleted the phone profile / recreated / then added in pguser, but it didn't resolved.
    Work arround done- Restarted the ctimanager service (off hours), after that disassociate  / associate the phone under pg user in call manager,  this resolved the issue.
    But restart of ctimanager service for 1 user is not proper solution.....
    Thanks,
    Thanveer

  • CSA MC Events Log and Agent Panel Events Corrolation

    I have recently install CSA MC 6.0.0.201 and the agent on a Win2003 server. I have a question of events showing up in the agent panel and not showing up in the MC events log.
    I see a number of events in the agent 'panel' event viewer. At the end of the event is a number in brackets like [176].
    When I look at the MC event viewer but those events are not being reported.
    My query is:
    #1 I believe the example [176} is the rule being triggered. So if the event is not showing up in the event viewer how to I find that rule in the policies? I finally did stumble across the rule and I see that logging is disabled for that rule, but finding that rule was a needle in the haystack search. Is there an easier way to find rules?
    #2 Maybe I do not understand this part but in the MC I placed this server (the one with the MC) into 'Audit Mode' in hopes that would get the events from the agent to show up in the MC event log. No good. Is there a way to get all events - even if the rule says to not log the event - so show up in the MC log so I can creat an exception?
    Thanks
    Larry

    Tom,
    I think I may have made some progress. Yes I'm in advanced mode. I went into Systems | Groups and first selected the 'Servers' and turned on logging. Still most the events in the agent event viewer were not making it to the MC event log.
    So I went back in to the Systems | Groups and found there was a group called 'Servers - CSA Management Center' and turned on logging there and that got the events to start flowing into the MC events.
    Maybe this will help me get going.
    Larry

  • Cisco Supervisor user isnt under Agent's Team Summary

                       I am using Cisco Supervisor and Agent Robin Dean is under Agent Team State but she is not under Agent-Team Summary. Does anyone know how to get her in there? We are using UCCX 8.0.2.

    There have been quite a few bugs over the years with agents not showing or disappearing from the supervisors desktop.
    Make sure you have the latest SU installed, I think SU4 for 8.0(2)
    Graham

  • UCCX RTMT and CAD Agent Logs

    I have a CAD agent (version 7.0(1)) which uses the IPCC extension to make outbound calls.  My issue is with the RTMT showing these calls as Contacts Presented and Contacts Handled.  When the agent logs into the client to start their shift, they are showing 17 Contacts Presented and 27 Contacts Handled even though they have not received any calls of yet.
    I have tried to reset all stats in the RTMT, all stats clear for all other agents except this agent.
    Is there a way to clear the call log from the CAD?  This is effecting reports supervisors are gathering for call log data.
    Any advice would be appreciated.

    Certainly something to try, but I don't see why that would make a difference in an inability to log out.  I have many customers who only use the default workflow and haven't seen any of them with this issue previously.
    Are you guessing here, or have you actually seen that resolve similar problems?

  • UCCX 9.02 script checking for agents logged into a queue

    I'm needing change my current script so that it will check the queue before it sends a call to the skill to make sure that there are agents logged into it.  If there arent any agents logged into that skill then I need to send them to another predefined skill.  I'm sure it can be done I'm just drawing a blank at the moment, anyone willing to point me in the right direction would be greatly appreciated.
    Thanks,  Mark

    Before arriving at the Select Resource Step you should Assign the csqId and you should have an int type and call it something like iRsrcLoggedIn (it's initial value will be set to 0). Once that is done, use a Get Reporting Statistic Step (from the ACD folder) to check for Logged In Agents for that CSQ you defined after that use if logic..IF iRsrcLoggedIn == 0 then change the csqId value to the other CSQ/Skill..do a check there if you want and then drop the call into Queue. Let me know if I should show a Screen Capture of this..

  • Logging in Agents

    What criterion determines which CTI Sever (7.1.2) a CTI OS agent logs into for a duplexed system?  I have done a ton of tests and can report with 100% certainty that it is not round robin and does not balance out perfectly even.  If there is a formula or a test the desktop runs while logging in could someone please share it with me?

    As a follow up I've found some evidence that suggests if the last octet of the client IP address was odd then it would log into CTI OS A and if even it would log into CTI OS B on first attempts. This does not explain why after logging in and out on multiple occasions the system chooses to switch sides. 
    Please, if anyone has any information, feel free to share.

  • Log Reader Agent: transaction log file scan and failure to construct a replicated command

    I encountered the following error message related to Log Reader job generated as part of transactional replication setup on publisher. As a result of this error, none of the transactions propagated from publisher to any of its subscribers.
    Error Message
    2008-02-12 13:06:57.765 Status: 4, code: 22043, text: 'The Log Reader Agent is scanning the transaction log for commands to be replicated. Approximately 24500000 log records have been scanned in pass # 1, 68847 of which were marked for replication, elapsed time 66018 (ms).'.
    2008-02-12 13:06:57.843 Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on ServerName.'.
    2008-02-12 13:06:57.843 Status: 0, code: 18805, text: 'The Log Reader Agent failed to construct a replicated command from log sequence number (LSN) {00065e22:0002e3d0:0006}. Back up the publication database and contact Customer Support Services.'.
    2008-02-12 13:06:57.843 Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'ServerName'.'.
    Replication agent job kept trying after specified intervals and kept failing with that message.
    Investigation
    I could clearly see there were transactions waiting to be delilvered to subscribers from the followings:
    SELECT * FROM dbo.MSrepl_transactions -- 1162
    SELECT * FROM dbo.MSrepl_commands -- 821922
    The following steps were taken to further investigate the problem. They further confirmed how transactions were in queue waiting to be delivered to distribution database
    -- Returns the commands for transactions marked for replication
    EXEC sp_replcmds
    -- Returns a result set of all the transactions in the publication database transaction log that are marked for replication but have not been marked as distributed.
    EXEC sp_repltrans
    -- Returns the commands for transactions marked for replication in readable format
    EXEC sp_replshowcmds
    Resolution
    Taking a backup as suggested in message wouldn't resolve the issue. None of the commands retrieved from sp_browserreplcmds with mentioned LSN in message had no syntactic problems either.
    exec sp_browsereplcmds @xact_seqno_start = '0x00065e220002e3d00006'
    In a desperate attempt to resolve the problem, I decided to drop all subscriptions. To my surprise Log Reader kept failing with same error again. I thought having no subscription for publications log reader agent would have no reason to scan publisher's transaction log. But obviously I was wrong. Even adding new log reader using sp_addLogreader_agent after deleting the old one would not be any help. Restart of server couldn't do much good either.
    EXEC sp_addlogreader_agent
    @job_login = 'LoginName',
    @job_password = 'Password',
    @publisher_security_mode = 1;
    When nothing else worked for me, I decided to give it a try to the following procedures reserved for troubleshooting replication
    --Updates the record that identifies the last distributed transaction of the server
    EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
    -- Flushes the article cache
    EXEC sp_replflush
    Bingo !
    Log reader agent managed to start successfully this time. I wish if I could have used both commands before I decided to drop subscriptions. It would have saved me considerable effort and time spent re-doing subscriptions.
    Question
    Even though I managed to resolve the error and have replication funtioning again but I think there might have been some better solution and I would appreciate if you could provide me some feedback and propose your approach to resolve the problem.

    Hi Hilary,
    Will the below truncate the log file marked for replication, is there any data loss, when we execute this command, can you please help me understand, the internal working of this command.
    EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1

Maybe you are looking for