Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AVAYA WORKSPACE CONFIGURATION ON ACCS VER 7.1.1.2

Status
Not open for further replies.

WillardC

Systems Engineer
Jun 7, 2022
8
ZW
Hi team

We recently upgraded one of our clients from 7.1.1.2 from 7.1.1.0. The reason for the upgrade we thought the upgrade would resolve our issue on workspace which never worked from the word go. We did all the required during ignition but we are getting the attached error.

Software configuration has failed.

Failed to configure the Hyper-V environment. Cannot continue.
 
 https://files.engineering.com/getfile.aspx?folder=8ec1d478-f396-499f-b05e-5726e40d2f9e&file=Workspace_error.png
Thanks Megaa

I am failing to understand why then Avaya is telling us to upgrade the version of our ACCS to the latest that support Workspaces. What is the best way forward here?
 
While ACCS may work on Hyper-V it is not supported and Workspaces is deployed via OVA and is Vmware only.
I'm guessing Avaya are assuming a Vmware environment.

From the ACCS docs:
The Avaya Contact Center Select software appliance is supported only with the following
virtualization environments:
• ESXi 6.0
• ESXi 6.5
• ESXi 6.7
Important:
• Avaya Workspaces is supported on ESXi 6.5 and 6.7 only.
• Avaya Contact Center Select on Windows Server 2016 is supported on ESXi 6.5 and 6.7
only.
• VMFS 5.54 or later is required for all supported versions of ESXi.
 
Hi aoh74

Thanks very much , i wanted you to understand that ACCS is deployed on-prem on physical server, i suppose workspace will be running on Hyper-V same as AAMS on the same windows server. so on upgrading to solve the issue, workspace ignition is failing to create the nodes in the Hyper-V. i hope i have clarified .

thank you in advance.
 
It is indeed deployed in Hyper on a physical server, learn something new every day. :)
Check the logfiles in C:\Avaya, it must be failing on prereqs for deployment for some reason.
Also the ACCS version is 7.1.2 correct? And have you installed all subsequent patches/bundles?
 
Hi aoh74

I got these logs from C:\Avaya

VM Network adapter connected to 'AAMS-HV-SWITCH':
2022-06-06 09:06:14 INFO Starting VMs. Please wait...
2022-06-06 09:06:14 INFO - Starting wsk8master
2022-06-06 09:06:14 INFO - Starting wsk8node1
2022-06-06 09:06:14 INFO - Starting wsk8node2
2022-06-06 09:09:14 INFO Waiting for VM wsk8master to start. Please wait...
2022-06-06 09:09:15 INFO - wsk8master not ready. Waiting 0 of 120 seconds
2022-06-06 09:09:16 INFO - wsk8master not ready. Waiting 1 of 120 seconds
2022-06-06 09:09:17 INFO - wsk8master not ready. Waiting 2 of 120 seconds
2022-06-06 09:09:18 INFO - wsk8master not ready. Waiting 3 of 120 seconds
2022-06-06 09:09:19 INFO - wsk8master not ready. Waiting 4 of 120 seconds
2022-06-06 09:09:20 INFO - wsk8master not ready. Waiting 5 of 120 seconds
2022-06-06 09:09:21 INFO - wsk8master not ready. Waiting 6 of 120 seconds
2022-06-06 09:09:22 INFO - wsk8master not ready. Waiting 7 of 120 seconds
2022-06-06 09:09:23 INFO - wsk8master not ready. Waiting 8 of 120 seconds
2022-06-06 09:09:24 INFO - wsk8master not ready. Waiting 9 of 120 seconds
2022-06-06 09:09:25 INFO - wsk8master not ready. Waiting 10 of 120 seconds
2022-06-06 09:09:26 INFO - wsk8master not ready. Waiting 11 of 120 seconds
2022-06-06 09:09:27 INFO - wsk8master not ready. Waiting 12 of 120 seconds
2022-06-06 09:09:28 INFO - wsk8master not ready. Waiting 13 of 120 seconds
2022-06-06 01:54:46 INFO - wsk8master not ready. Waiting 119 of 120 seconds
2022-06-06 01:54:46 ERROR Timeout while waiting for VM wsk8master to start. Cannot continue.
2022-06-06 01:54:46 INFO Updating registry key HKLM:\SOFTWARE\Wow6432Node\Avaya\Contact Center\Product Installation\Workspaces. Adding registry name WS_DeploymentScript_Success with value 0
2022-06-06 01:54:46 INFO Updating registry key HKLM:\SOFTWARE\Wow6432Node\Avaya\Contact Center\Product Installation\Workspaces. Adding registry name ScriptError with value Failed to configure the Hyper-V environment. Cannot continue.
2022-06-06 01:54:46 ERROR Failed to configure the Hyper-V environment. Cannot continue.
2022-06-06 01:54:46 INFO ====================================================================================
2022-06-06 01:54:46 INFO SCRIPT FINISHED: Sun, 05 Jun 2022 23:54:46 GMT
2022-06-06 01:54:46 INFO SCRIPT DURATION (hrs:mins:secs):00:06:27
2022-06-06 01:54:46 INFO ====================================================================================
2022-06-06 09:05:07 INFO ====================================================================================
2022-06-06 09:05:07 INFO SCRIPT STARTED: Mon, 06 Jun 2022 07:05:07 GMT
2022-06-06 09:05:07 INFO Beginning multi-node deployment
2022-06-06 09:05:07 INFO ====================================================================================
2022-06-06 09:05:07 INFO Checking for Administrator privileges:
2022-06-06 09:05:07 INFO - Administrator privileges enabled
2022-06-06 09:05:07 INFO ====================================================================================
2022-06-06 09:05:07 INFO Initializing Script Variables
2022-06-06 09:05:07 INFO ====================================================================================
2022-06-06 09:05:07 INFO m_WS_REG_HIVE value is: HKLM:\SOFTWARE\Wow6432Node\Avaya\Contact Center\Product Installation\Workspaces
2022-06-06 09:05:07 INFO m_WS_REG_DEPLOYMENT_SUCCESS value is: WS_DeploymentScript_Success
2022-06-06 09:05:07 INFO m_REG_SUCCESS_VALUE_1 value is:
2022-06-06 09:05:07 INFO m_REG_FAILURE_VALUE_0 value is: 0
2022-06-06 09:05:07 INFO m_REPAIR_MODE value is: False
2022-06-06 09:05:07 INFO Calling InitializeData_FromRegistry
2022-06-06 09:05:07 INFO Retrieving Registry Data and initializing internal script variables...
2022-06-06 09:05:07 INFO m_NTP_TIMEZONE (Contact Center Timezone) value is: Africa/Harare


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top