- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Simplivity 380 Gen10 Deployment - err_dply_caught_...
-
-
Forums
- Products
- Servers and Operating Systems
- Storage
- Software
- Services
- HPE GreenLake
- Company
- Events
- Webinars
- Partner Solutions and Certifications
- Local Language
- China - 简体中文
- Japan - 日本語
- Korea - 한국어
- Taiwan - 繁體中文
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Blog, Poland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2021 06:41 AM
03-24-2021 06:41 AM
Simplivity 380 Gen10 Deployment - err_dply_caught_exception_configuring_vc: an exception occured whi
I doing the deployment of Simplivity 380 Gen10 and I come accross this error
err_dply_caught_exception_configuring_vc: an exception occured while configuring virtual controller
Any idea please?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2021 08:38 AM
03-24-2021 08:38 AM
Re: Simplivity 380 Gen10 Deployment - err_dply_caught_exception_configuring_vc: an exception occured
Hello @azabram,
It is hard to determine exact cause for the failure from just that snippet of log but typically when we fail at this stage it is related to some problematic hardware component. I would check the Deployment Manager Orchestrator log for more information and a look at the AHS logs on iLO may also be useful.
Regards,
David
I work for HPE

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2021 08:55 AM
03-24-2021 08:55 AM
Re: Simplivity 380 Gen10 Deployment - err_dply_caught_exception_configuring_vc: an exception occured
Thank you very much for your feed back.
There is no error in IML.
Below an extrat of the informations contain in Deployment Manager Orchestrator log.
') to OmniCube at 192.168.0.11 port 9299 failed - exception org.apache.thrift.transport.TTransportException
org.apache.thrift.transport.TTransportException: null
at org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:132)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:86)
at org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:425)
at org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:321)
at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:225)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:77)
at com.simplivity.deploy.dcs.DeployConfigService$Client.recv_setVirtualControllerSizeConfig(DeployConfigService.java:346)
at com.simplivity.deploy.dcs.DeployConfigService$Client.setVirtualControllerSizeConfig(DeployConfigService.java:333)
at com.simplivity.deploy.orchestrator.DeployConfigConnect.lambda$setVirtualControllerSizeConfig$5(DeployConfigConnect.java:216)
at com.simplivity.deploy.orchestrator.DeployConfigConnect.lambda$runWithReconnect$16(DeployConfigConnect.java:465)
at com.simplivity.deploy.orchestrator.DeployConfigConnect.returnWithReconnect(DeployConfigConnect.java:437)
at com.simplivity.deploy.orchestrator.DeployConfigConnect.runWithReconnect(DeployConfigConnect.java:464)
at com.simplivity.deploy.orchestrator.DeployConfigConnect.setVirtualControllerSizeConfig(DeployConfigConnect.java:216)
at com.simplivity.deploy.orchestrator.DeployActions.computeAndSendSvaSizingConfig(DeployActions.java:1977)
at com.simplivity.deploy.orchestrator.CustomerDeploy.lambda$initSteps$5(CustomerDeploy.java:69)
at com.simplivity.deploy.orchestrator.DeployStep.run(DeployStep.java:38)
at com.simplivity.deploy.orchestrator.DeployExecutor.run(DeployExecutor.java:215)
at java.lang.Thread.run(Unknown Source)
2021-03-24 14:34:19,049Z ERROR Omnistack-192.168.0.14 [c.s.d.o.DeployExecutor] setDeployStatus(DeployExecutor.java:94) - DeployStatus(status:ERROR, detail:ERR_DPLY_CAUGHT_EXCEPTION_CONFIGURING_VC, message:Step 30 of 43: ERR_DPLY_CAUGHT_EXCEPTION_CONFIGURING_VC: An exception occurred while configuring the Virtual Controller.)
2021-03-24 14:34:19,049Z ERROR Omnistack-192.168.0.14 [c.s.d.o.DeployExecutor] run(DeployExecutor.java:229) - com.simplivity.deploy.orchestrator.DeployException: ERR_DPLY_CAUGHT_EXCEPTION_CONFIGURING_VC: An exception occurred while configuring the Virtual Controller.
at com.simplivity.deploy.orchestrator.DeployActions.computeAndSendSvaSizingConfig(DeployActions.java:1981)
at com.simplivity.deploy.orchestrator.CustomerDeploy.lambda$initSteps$5(CustomerDeploy.java:69)
at com.simplivity.deploy.orchestrator.DeployStep.run(DeployStep.java:38)
at com.simplivity.deploy.orchestrator.DeployExecutor.run(DeployExecutor.java:215)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.thrift.transport.TTransportException
at org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:132)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:86)
at org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:425)
at org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:321)
at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:225)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:77)
at com.simplivity.deploy.dcs.DeployConfigService$Client.recv_setVirtualControllerSizeConfig(DeployConfigService.java:346)
at com.simplivity.deploy.dcs.DeployConfigService$Client.setVirtualControllerSizeConfig(DeployConfigService.java:333)
at com.simplivity.deploy.orchestrator.DeployConfigConnect.lambda$setVirtualControllerSizeConfig$5(DeployConfigConnect.java:216)
at com.simplivity.deploy.orchestrator.DeployConfigConnect.lambda$runWithReconnect$16(DeployConfigConnect.java:465)
at com.simplivity.deploy.orchestrator.DeployConfigConnect.returnWithReconnect(DeployConfigConnect.java:437)
at com.simplivity.deploy.orchestrator.DeployConfigConnect.runWithReconnect(DeployConfigConnect.java:464)
at com.simplivity.deploy.orchestrator.DeployConfigConnect.setVirtualControllerSizeConfig(DeployConfigConnect.java:216)
at com.simplivity.deploy.orchestrator.DeployActions.computeAndSendSvaSizingConfig(DeployActions.java:1977)
... 4 more
2021-03-24 14:34:19,049Z DEBUG Omnistack-192.168.0.14 [c.s.d.o.DeployStep] LogStats(DeployStep.java:139) - step[ 0] duration | Expected=1,00 | Actual=0,04 | Diff=-96,40%
2021-03-24 14:34:19,050Z DEBUG Omnistack-192.168.0.14 [c.s.d.o.DeployStep] LogStats(DeployStep.java:139) - step[ 1] duration | Expected=1,00 | Actual=18,72 | Diff=1772,30% (large diff!)
2021-03-24 14:34:19,050Z DEBUG Omnistack-192.168.0.14 [c.s.d.o.DeployStep] LogStats(DeployStep.java:139) - step[ 2] duration | Expected=1,00 | Actual=0,11 | Diff=-88,70%
2021-03-24 14:34:19,050Z DEBUG Omnistack-192.168.0.14 [c.s.d.o.DeployStep] LogStats(DeployStep.java:139) - step[ 3] duration | Expected=1,00 | Actual=0,28 | Diff=-71,60%
2021-03-24 14:34:19,051Z DEBUG Omnistack-192.168.0.14 [c.s.d.o.DeployStep] LogStats(DeployStep.java:139) - step[ 4] duration | Expected=1,00 | Actual=0,02 | Diff=-97,50%
2021-03-24 14:34:19,051Z DEBUG Omnistack-192.168.0.14 [c.s.d.o.DeployStep] LogStats(DeployStep.java:139) - step[ 5] duration | Expected=240,00 | Actual=0,00 | Diff=-100,00% (large diff!)
2021-03-24 14:34:19,051Z DEBUG Omnistack-192.168.0.14 [c.s.d.o.DeployStep] LogStats(DeployStep.java:139) - step[ 6] duration | Expected=10,00
Do you have an idea of what is the problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2021 05:26 AM
03-26-2021 05:26 AM
Re: Simplivity 380 Gen10 Deployment - err_dply_caught_exception_configuring_vc: an exception occured
Hello @azabram,
It's still difficult to determine the problem with the provided log. Still, I agree most of the time this is a hardware related problem. You could try the following steps:
1. Shutdown the host
2. Push power button for 10 seconds.
3. Remove power cables for 10 minutes.
4. Make sure all hard drives are properly seated in their slots.
5. Reconnect host and power it on.
6. Factory reset the host again and re-try redeployment.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2021 07:09 AM
04-28-2021 07:09 AM
Re: Simplivity 380 Gen10 Deployment - err_dply_caught_exception_configuring_vc: an exception occured
I ran into the same issue trying to deploy two Simplivity 380 Gen10 Large
Any hints ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2021 06:46 AM
10-05-2021 06:46 AM
Re: Simplivity 380 Gen10 Deployment - err_dply_caught_exception_configuring_vc: an excepti
Same issue, any resolution?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2022 09:31 PM
02-28-2022 09:31 PM
Re: Simplivity 380 Gen10 Deployment - err_dply_caught_exception_configuring_vc: an excepti
Same issue, any resolution?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
a week ago
Re: Simplivity 380 Gen10 Deployment - err_dply_caught_exception_configuring_vc: an excepti
Having te same issue. Anybody resolved this? Please answer
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2022 Hewlett Packard Enterprise Development LP