I have a PVA installation that connects with three hardware nodes: - 2 new hardware nodes running PVC 4.6.0 (one of these runs the PVA container) - 1 older hardware node running PVC 4.0.0 All are running CentOS 5. I can view all the hardware nodes in PVA without problems. I can also see the containers listed in the 'Virtual Environment' tab (including status, resource usage, etc.). However for the 2 new nodes, I cannot click the container to see the details - the request just times out. The containers on the older HN can be opened without problems. When I try to open the VE's by clicking multiple times, PVA becomes unresponsive and I have to restart the pvamnd service to regain access. I can't make much of the log file. The only odd messages I see are these: T=11:29:11:156; L=(wrn); PID=13961; TID=2b73e2426bf0; P=VZLFunctionalityCore [insert] EnvCache::insert called for 933a55af-6743-e04f-a16a-97710494b257, returning -1. T=11:29:11:162; L=(udf); PID=13961; TID=2b73e2426bf0; P=VZLServerGroup [doHandleError] Can't start monitoring of client 028b6c77-9e3f-0945-8b2d-799b8af93c8d: can't update env config/status list, envcache unavailable. T=11:45:41:869; L=(err); PID=28396; TID=2b0ff0394bf0; P=VZLCore [throwErrorImpl] Throwing exception from /usr/src/redhat/BUILD/pva-mn-core-4.6/vzl/plugins/VZLPolicySlave/VZLPolicySlLocal.cpp(48): policy id:f1166f7f-99a9-b344-a20f-1359a4aac15a. T=11:45:41:870; L=(err); PID=28396; TID=2b0ff0394bf0; P=VZLCore [processException] Exception is caught. Error code 10401, reason: policy id:f1166f7f-99a9-b344-a20f-1359a4aac15a. T=11:45:41:911; L=(err); PID=28396; TID=2b0ff0394bf0; P=VZLPolicyManager [handleStartup] [policym] can't generate effective policy on CT creation for eid="f1166f7f-99a9-b344-a20f-1359a4aac15a"olicy id:f1166f7f-99a9-b344-a20f-1359a4aac15a Any clue on what's going on or where to look? DNS on the hardware nodes and the PVA server is fine, pinging (from the console) works.