cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
394
Views
6
Helpful
3
Replies

Issue with Server Access on Cisco DevNet Sandbox

poetforcrises
Level 1
Level 1

Hi everyone,

I’m using the Cisco DevNet Sandbox and encountered a couple of issues I need help with.

  1. I connected via VPN and accessed the AW1-A server at IP 10.10.20.21 using Remote Desktop with the following credentials:

    Login User ID: BERLIN\pcceAdmin
    Password: C!sc0DevNet
    The connection to the AW1-A server was successful. However, when I tried accessing the Finesse agent login at https://fin-pub-a-50.berlin.icm:8445/desktop/, I encountered the following error:

    "This Finesse Server is currently out of service. For more information, contact your administrator."

    I’ve encountered this error multiple times.



    image (7).png

  2. I was advised to restart the server by logging into RGR-A (Rogger) at IP 10.10.20.22, but I couldn’t log in using:

    • Username: pcceAdmin
      Password: C!sc0DevNet

    I received an error saying, "logon attempt failed."

    poetforcrises_0-1731053627510.png

     

Could someone help me troubleshoot these issues?

Thanks in advance!

3 Replies 3

@poetforcrises does it help if you end the reservation and start a new one?

Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

ecorban
Cisco Employee
Cisco Employee

hello. please retry the login to the ROgger A with the BERLIN\pcceAdmin login. if that fails restart the finesse service by logging into the finesse server. (information on the ip address and login to finesse server is in the instructions of the sandbox).

once logged into finesse, restart the finesse service first and see if that fixes the issue. use the below as guidance to restart the finesse service:

To restart the Cisco Finesse Notification Service, you must stop and start services in the following order:
  1. Stop the Cisco Finesse Tomcat service.
  2. Stop the Cisco Finesse Notification Service.
  3. Start the Cisco Finesse Notification Service.
  4. Start the Cisco Finesse Tomcat service.

As to validation after the service restart , check  services come up properly and run any acceptance testing you deemed required. For example  login as agent/supervisor to Finesse, make sure you can accept call from queue, etc. If you require additional testing then you can try forwarding, hold, conferencing, etc. typical things agents would do.

If restart the finesse service does NOT fix the issue, then restart the finesse server using the following command:

# utils system restart

Thank you for the solution provided. Following your guidance, I successfully accessed Rogger using the IP 10.10.20.22 with the credentials Username: BERLIN\pcceAdmin and Password: C!sc0DevNet. After establishing the RDP connection, I accessed the Finesse Agent Console through the Chrome browser without any issues.

Given the successful outcome, I plan to follow this exact procedure each time I need to log into the Agent Console. Please confirm if this is an optimal practice or if any additional steps are recommended for stability and security.