VMware Horizon Community
DanielVC
Contributor
Contributor
‎02-14-2011 10:26 AM

VMView - Enabling View Composer

Greetings,

I am attempting to evaluate VMView for our student labs.  I am having a problem with enabling “View Composer” from the View admin console.  It always says “No View Composer server found”.  The View Composer service is running on the vCenter console on port 18443.  I have successfully telnet’ed into the port from the VMView server. Our vCenter console runs on port 8443.  I can add our vCenter server from the VMView admin console it just will not allow me to “check” the Composer check box.  I turned on debugging for the VMView admin console and found that it is trying to connect to our vCenter console on the wrong port.  Windows Event view is also stating the same problem "connection to the vCenter Server "https://vcenter.ourdomain.edu:443/sdk failed".

It is trying to access https://vcenter.ourdomain.edu:443/sdk instead of https://vcenter.ourdomain.edu:8443/sdk. I have dumped the ADAM (VMwareVDMDS) ldap server and cannot find any references to port 443 for our vCenter console.  Anyone have an idea why VMView is trying to connect to 443/sdk instead of 8443/sdk?

0 Kudos
16 Replies
AndreTheGiant
Immortal
Immortal
‎02-14-2011 10:50 AM

Which version of View are you using?

Which version of OS is on vCenter and View Connection Server?

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
DanielVC
Contributor
Contributor
‎02-14-2011 12:09 PM

Sorry Andre I should have included that info.

VMWiew 4.5 on OS Win 2008R2 standard

vCenter 4.1 on OS  Win 2008R2 standard using port 8443

Here is a snippet of the VDM debug Log:

2011-02-14 10:03:25,019 INFO  <2772> [ws_TomcatService] Log for VMware View Connection Broker, version=4.5.0 build-293049
10:03:25,019 INFO  <2772> [ws_TomcatService] hostname=VM-VIEW.student.victoriacollege.edu
2011-02-14 10:03:25,018 DEBUG <ConfigureAgentVPs-1297697243799> [ConfigureVPsFederatedTask] VP policies: licensed=true, desktops=0, pools=0, machines=0, skipped=0, noVP=0, matched=0, toupdate=0
2011-02-14 10:03:30,388 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2011-02-14 10:03:30,401 DEBUG <Thread-18> [SimpleAJPService] (Request33) SimpleAJPService request: /admin/messagebroker/amfsecure
2011-02-14 10:03:30,461 DEBUG <TP-Processor3> [ViewFlexFactory] com.vmware.vdi.admin.ui.bean.VCServerBean.getServerById 30 ms
2011-02-14 10:03:30,499 DEBUG <TP-Processor3> [ViewFlexFactory] com.vmware.vdi.admin.ui.bean.VCServerBean.getServerById 38 ms
2011-02-14 10:03:31,703 DEBUG <Thread-17> [SimpleAJPService] (Request34) SimpleAJPService request: /admin/messagebroker/amfsecure
2011-02-14 10:03:31,711 DEBUG <TP-Processor2> [Connection] Using default service timeout: 2000ms
2011-02-14 10:03:32,742 ERROR <TP-Processor2> [Connection] Connection to the vCenter Server https://vcenter.victoriacollege.edu:443/sdk failed.
2011-02-14 10:03:32,743 DEBUG <TP-Processor2> [Connection] [EXCEPTION] Connection to the vCenter Server https://vcenter.victoriacollege.edu:443/sdk failed.
2011-02-14 10:03:32,743 DEBUG <TP-Processor2> [Connection] [EXCEPTION] java.net.ConnectException: Connection refused: connect
2011-02-14 10:03:32,759 DEBUG <TP-Processor2> [Connection] [EXCEPTION] com.vmware.vdi.admin.be.common.Util.reportException(SourceFile:87)
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection refused: connect
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Connection refused: connect
0 Kudos
AndreTheGiant
Immortal
Immortal
‎02-14-2011 09:09 PM


vCenter 4.1 on OS  Win 2008R2 standard using port 8443


Why are you using a different port?

I suppose the this is the problem.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
DanielVC
Contributor
Contributor
‎02-15-2011 06:19 AM

Thanks for the reply Andre.  Our vCenter has been running on port 8443 since ESX 3.5 about three years now.  I don't understand since I can connect to our vCenter through View admin console on port 8443 why I can't enable composer on the same port it doesn't make any sense.

0 Kudos
npeter
Expert
Expert
‎02-16-2011 05:04 AM

Hi Daniel,

This is a known issue. There is a service request filed to fix this.

Thanks

Noble

-nObLe
DanielVC
Contributor
Contributor
‎02-16-2011 01:58 PM

After talking to VMware tech support for two hours they finally recommended that I use the default ports in vCenter.

Thanks for all the input.

0 Kudos
ukfatboy
Contributor
Contributor
‎02-23-2011 07:51 PM

I am having a similar issue with vmview composer, view manager 4.5 will not connect to the composer element of the vcentre server. We have a virtual 2003 x64 server running vcentre server 4.1 with composer 2.5 installed on it. Oddly though, everytime i have installed composer onto this virtual machine at the end of the install it cuts off my remote desktop connection and i cannot reconnect until i reboot the vm using the vsphere client at which point i see an error stating "Windows firewall cannot run because another program or service is running that might use the networks address translation component ipnat.sys" so it would seem vmview composer essentially kills ipnat.sys!   NICE   as of yet having tried everything thinkable vmview composer does NOT work, 3 DAYS work on it installing/uninstalling removing sql/rebuilding sql even starting EVERYTHING over from scratch several times over still NOTHING, everything else is fine just this damed useless composer!

0 Kudos
npeter
Expert
Expert
‎02-23-2011 08:15 PM

Hi,

I think the problem you are facing is different from the one discussed on original post.

Can you tell me what flavour of windows you are running? Do you have any NAT or routing enabled on this VM?

>view manager 4.5 will not connect to the composer element of the vcentre  server. We have a virtual 2003 x64 server running vcentre server 4.1  with composer 2.5 installed on it

What error message do you get when trying to enable view composer from View manager?

-noble

-nObLe
0 Kudos
ukfatboy
Contributor
Contributor
‎02-24-2011 01:28 AM

Hi Peter, okay when i go ahead and place the tick in the box to connect the vmview manager to the view composer it pops up saying basically not found or incorrect port, as i said before the install seems to have an issue. The x64 2003 has just the one virtual NIC in it so no there is no routing or remote access used just basic RDP, there is no firewall in use as windows firewall is deactivated, we use an Untangle system at our gateway for firewalling ect, really i cannot see good reason for this to not be working but it seems to be the way it is. When i try to Telnet locally or remotely to the port i specify it seems to connect though i get no interaction, by this i mean when i attempt to connect to the ip with the wrong port it tells me no connection but when i use the corrcect port it sits there an says connecting.....asin it doesnt NOT connect, usually i expect some response or info from a Telnet connection but with composer it appears to do nothing...

///////////////////////Composer log///////////////////////////////////

------------Sim Web Service Log End-------------
------------Sim Web Service Log Start-----------
Build: 291081
Os Type: win64-x64
API Version: 2.1
Product Version: 2.5.0.3913
2011-02-24 03:12:14,765 | 6             | INFO  | Sim.WebService.SimServer - SVI service is starting.
2011-02-24 03:12:25,406 | 7             | INFO  | CommonLib.UfaSubsystem.UfaSubsystem - UfaSubsystem: contructed with threads: 5, retry no: 1, timeout: 1200000
2011-02-24 03:12:25,531 | 7             | INFO  | Sim.ServiceCore.SimServiceApiImpl - PerformInitialCleanup: start performing initial cleanup.
2011-02-24 03:12:25,625 | 7             | INFO  | Sim.ServiceCore.SimServiceApiImpl - PerformInitialCleanup: no incomplete task needs to be cleaned up.
2011-02-24 03:12:25,734 | 6             | INFO  | Sim.WebService.SimServer - SVI service started successfully.

//////////////////////////////Vcentre log////////////////////////////////

[2011-02-24 09:16:45.411 01948 info 'App' opID=b057650] [VpxLRO] -- FINISH task-internal-368 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:17:18.090 02840 error 'App'] [HttpUtil::ExecuteRequest] Error in sending request - No connection could be made because the target machine actively refused it.
[2011-02-24 09:17:18.090 02840 error 'App'] [ServerAccess] Exception while invoking remote login: vim.fault.HttpFault
[2011-02-24 09:17:18.090 02840 error 'App'] [VpxdHealthServiceMonitor::LoginToHealthService] Unable to login into HealthService. Error is vmodl.fault.HostCommunication
[2011-02-24 09:17:45.564 01948 info 'App' opID=e273bc10] [VpxLRO] -- BEGIN task-internal-369 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:17:45.564 01948 info 'App' opID=e273bc10] [VpxLRO] -- FINISH task-internal-369 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:18:45.725 01948 info 'App' opID=f89f1ca] [VpxLRO] -- BEGIN task-internal-370 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:18:45.725 01948 info 'App' opID=f89f1ca] [VpxLRO] -- FINISH task-internal-370 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:19:18.099 01948 info 'App'] [LicMgr] No vm-based licenses. So skipping collection.
[2011-02-24 09:19:45.780 01948 info 'App' opID=a7cec970] [VpxLRO] -- BEGIN task-internal-371 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:19:45.780 01948 info 'App' opID=a7cec970] [VpxLRO] -- FINISH task-internal-371 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:20:18.089 01700 error 'App'] [HttpUtil::ExecuteRequest] Error in sending request - No connection could be made because the target machine actively refused it.
[2011-02-24 09:20:18.089 01700 error 'App'] [ServerAccess] Exception while invoking remote login: vim.fault.HttpFault
[2011-02-24 09:20:18.105 01700 error 'App'] [VpxdHealthServiceMonitor::LoginToHealthService] Unable to login into HealthService. Error is vmodl.fault.HostCommunication
[2011-02-24 09:20:45.982 01948 info 'App' opID=d1cfbd01] [VpxLRO] -- BEGIN task-internal-372 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:20:45.982 01948 info 'App' opID=d1cfbd01] [VpxLRO] -- FINISH task-internal-372 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:21:46.161 01948 info 'App' opID=92194f9e] [VpxLRO] -- BEGIN task-internal-373 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:21:46.161 01948 info 'App' opID=92194f9e] [VpxLRO] -- FINISH task-internal-373 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:22:46.312 01948 info 'App' opID=878a0336] [VpxLRO] -- BEGIN task-internal-374 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:22:46.312 01948 info 'App' opID=878a0336] [VpxLRO] -- FINISH task-internal-374 --  -- vmodl.query.PropertyCollector.retrieveContents -- 013CC97E-BD0D-4D59-9DED-3EC264EDA084(C8C8B26F-0106-45DA-9908-7F335779839E)
[2011-02-24 09:23:18.097 01252 error 'App'] [HttpUtil::ExecuteRequest] Error in sending request - No connection could be made because the target machine actively refused it.
[2011-02-24 09:23:18.097 01252 error 'App'] [ServerAccess] Exception while invoking remote login: vim.fault.HttpFault
[2011-02-24 09:23:18.097 01252 error 'App'] [VpxdHealthServiceMonitor::LoginToHealthService] Unable to login into HealthService. Error is vmodl.fault.HostCommunication

Interestingly the vcentre logs refer to a connection being actively refused, i would expect this if a system detects an incoming connection on a port it dosn't have an allow entry specificaly set for it though the logs lack any real detail as far as what originating ip and/or port address, i have set my vmview composer to use port 18447 as its original port was conflicting with another service already running within Tomcat, yes i have tried to use ALL of the default ports but again that only causes conflicts with other services running locally.

I believe the issues i am facing all stems from the fact that the vmview composer locks up the entire server at the end of its install to the point where my RDP connection cannot reconnect and my ONLY option is to use the vsphere client to reboot the server after which i can them RDP back onto it, so something towards the end of the composer install deeply affects networking/firewalling/ipnat.sys ect, i am currently trying to roll out 25 vmview desktops using HP thin clients, we need this to work!

So, in conclusion.......the trial continues...

0 Kudos
ukfatboy
Contributor
Contributor
‎02-24-2011 02:21 AM

Okay i figured out the issue.....if you attempt to install vmview composer onto a server that has the firewall disabled it goes into meltdown at the end of the install, if you activate windows firewall it does not.....FANTASTIC! but still the vmview composer will not connect, the vcentre logs have a new error message though...

[2011-02-24 10:07:56.425 02840 warning 'Libs'] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

* The host certificate chain is not complete.
[2011-02-24 10:07:56.488 02840 info 'App' opID=748357de] [VpxLRO] -- BEGIN task-internal-497 --  -- vim.SessionManager.loginExtensionByCertificate --

E8C7BD87-884F-4FDD-A4F4-D38137759A95
[2011-02-24 10:07:56.503 02840 info 'App' opID=748357de] [VpxLRO] -- FINISH task-internal-497 --  -- vim.SessionManager.loginExtensionByCertificate -- E8C7BD87-884F-4FDD-A4F4-D38137759A95(D4BC0B7B-3929-46F6-8ACC-9974B2B75B30)
[2011-02-24 10:07:56.581 02840 warning 'Libs'] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

* The host certificate chain is not complete.
[2011-02-24 10:07:56.581 02840 warning 'Libs'] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

* The host certificate chain is not complete.
[2011-02-24 10:07:56.581 02840 warning 'Libs'] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

* The host certificate chain is not complete.
[2011-02-24 10:07:56.628 02840 info 'App' opID=f2e9ed83] [VpxLRO] -- BEGIN task-internal-498 --  -- vmodl.query.PropertyCollector.retrieveContents --

Back to Google.......

0 Kudos
npeter
Expert
Expert
‎02-24-2011 03:15 AM

Hi,

Are you using non-default port for VC?  Can you post the Connection server debug logs? @time when you try to enable view composer.

-noble

-nObLe
0 Kudos
ukfatboy
Contributor
Contributor
‎02-24-2011 03:28 AM

The vcentre port is set to 5443, here is a section from the logs you asked for, interestingly it refers to the broker keys having an error, i have seen this before with vmview and dns issues.....

VC_OUTAGE:Url:https://192.168.16.39:5443/sdk
10:57:54,728 WARN  <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [ServiceConnection25] VirtualCenter https://192.168.16.39:5443/sdk is currently unavailable - attempting to reconnect
10:57:57,857 ERROR <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [ServiceConnection25] Problem connecting to VirtualCenter at https://192.168.16.39:5443/sdk (java.net.ConnectException: Connection refused: connect)
10:57:57,857 WARN  <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [ServiceConnection25] Not connected to VC.
10:57:57,857 INFO  <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [Audit] VC_OUTAGE:Url:https://192.168.16.39:5443/sdk
10:57:57,857 WARN  <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [ServiceConnection25] VirtualCenter https://192.168.16.39:5443/sdk is currently unavailable - attempting to reconnect
10:57:57,857 WARN  <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [ServiceConnection25] Previous VC reconnection attempt didn't work, will wait before attempting again.
10:58:05,678 WARN  <VcCache poller 190a86e6-34f7-4724-a404-d70368de18b4> [ServiceConnection25] Not connected to VC.
10:58:49,593 ERROR <TP-Processor2> [Connection] Connection to the vCenter Server https://192.168.16.39:443/sdk failed.
10:59:20,685 ERROR <TP-Processor3> [Connection] Connection to the vCenter Server https://192.168.16.39:443/sdk failed.
11:01:57,686 WARN  <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [ServiceConnection25] Problem while performing VC operation: 'java.net.ConnectException: Connection refused: connect' [org.apache.axis.AxisFault] Message: ; nested exception is:
java.net.ConnectException: Connection refused: connect Cause: java.net.ConnectException: Connection refused: connect
11:01:57,686 INFO  <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [Audit] VC_OUTAGE:Url:https://192.168.16.39:5443/sdk
11:01:57,686 WARN  <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [ServiceConnection25] VirtualCenter https://192.168.16.39:5443/sdk is currently unavailable - attempting to reconnect
11:11:45,170 ERROR <TP-Processor2> [Connection] Connection to the vCenter Server https://192.168.16.39:443/sdk failed.
11:12:57,230 ERROR <TP-Processor3> [Connection] Connection to the vCenter Server https://192.168.16.39:443/sdk failed.
11:16:00,670 WARN  <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [ServiceConnection25] Problem while performing VC operation: 'java.net.ConnectException: Connection refused: connect' [org.apache.axis.AxisFault] Message: ; nested exception is:
java.net.ConnectException: Connection refused: connect Cause: java.net.ConnectException: Connection refused: connect
11:16:00,685 INFO  <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [Audit] VC_OUTAGE:Url:https://192.168.16.39:5443/sdk
11:16:00,685 WARN  <VCC-190a86e6-34f7-4724-a404-d70368de18b4-1298544404036> [ServiceConnection25] VirtualCenter https://192.168.16.39:5443/sdk is currently unavailable - attempting to reconnect
11:20:21,788 ERROR <TP-Processor2> [Connection] Connection to the vCenter Server https://192.168.16.39:443/sdk failed.
11:21:31,059 INFO  <TP-Processor2> [RoleUIFlexAdapter] 47

////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

tn=TaskTracker, u=[], nn=vmviewmain, oi=MemberValidationTask})
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [TrackerObject] Sync complete: TaskClusterControllerTracker:MasterController to version: 9
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [TrackerManager] Sending message: (TrackerMessage SYNC {}: {v=9, tn=TaskClusterControllerTracker, u=[], nn=vmviewmain, oi=MasterController})
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [TrackerObject] Sync complete: TaskClusterControllerTracker:node-vmviewmain to version: 38
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [TrackerManager] Sending message: (TrackerMessage SYNC {}: {v=38, tn=TaskClusterControllerTracker, u=[], nn=vmviewmain, oi=node-vmviewmain})
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Node vmviewmain has no new tasks to load
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Current task table
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Task=EventForwarderHandler, state=ON_EXECUTOR, transition=NONE, owner=vmviewmain, TO owner=vmviewmain, load=1, task terminates=0, factory=ViewDatabaseEventForwarder.Forwarder
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Task=Health-federatedtask, state=ON_EXECUTOR, transition=NONE, owner=vmviewmain, TO owner=vmviewmain, load=1, task terminates=0, factory=HealthTask-factory
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Task=BrokerMaxSessions-federatedtask, state=ON_EXECUTOR, transition=NONE, owner=vmviewmain, TO owner=vmviewmain, load=0, task terminates=0, factory=BrokerMaxSessionsTask-factory
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Task=efa50d9d-14d8-4203-b344-76dcdf504860, state=ON_EXECUTOR, transition=NONE, owner=vmviewmain, TO owner=vmviewmain, load=0, task terminates=0, factory=null
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Task=ConfigureAgentVPs, state=ON_EXECUTOR, transition=NONE, owner=vmviewmain, TO owner=vmviewmain, load=1, task terminates=0, factory=class com.vmware.vdi.broker.ConfigureVPsFederatedTask$Factory
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Task=Federated.TransferServerHeartbeatTask, state=ON_EXECUTOR, transition=NONE, owner=vmviewmain, TO owner=vmviewmain, load=1, task terminates=0, factory=Federated.TransferServerHeartbeatFactory
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Task=SGHealth-federatedtask, state=ON_EXECUTOR, transition=NONE, owner=vmviewmain, TO owner=vmviewmain, load=1, task terminates=0, factory=SGHealthTask-factory
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Task=VCC-190a86e6-34f7-4724-a404-d70368de18b4, state=ON_EXECUTOR, transition=NONE, owner=vmviewmain, TO owner=vmviewmain, load=2, task terminates=0, factory=class com.vmware.vdi.vccache.VcCacheFederatedTask$Factory
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Task=FM-190a86e6-34f7-4724-a404-d70368de18b4, state=ON_EXECUTOR, transition=NONE, owner=vmviewmain, TO owner=vmviewmain, load=1, task terminates=0, factory=class com.vmware.vdi.desktopcontroller.FederatedManagerTask$FederatedManagerTaskFactory
2011-02-24 11:24:34,967 DEBUG <TaskFramework:MainHandler> [g] Task=MemberValidationTask, state=ON_EXECUTOR, transition=NONE, owner=vmviewmain, TO owner=vmviewmain, load=0, task terminates=0, factory=MachineMember
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task Federated.TransferServerHeartbeatTask - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task BrokerMaxSessions-federatedtask - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task EventForwarderHandler - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task SGHealth-federatedtask - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task efa50d9d-14d8-4203-b344-76dcdf504860 - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task ConfigureAgentVPs - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task MemberValidationTask - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task EventForwarderHandler - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task Health-federatedtask - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task BrokerMaxSessions-federatedtask - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task efa50d9d-14d8-4203-b344-76dcdf504860 - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task ConfigureAgentVPs - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task Federated.TransferServerHeartbeatTask - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task SGHealth-federatedtask - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task VCC-190a86e6-34f7-4724-a404-d70368de18b4 - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task FM-190a86e6-34f7-4724-a404-d70368de18b4 - performing task callbacks
2011-02-24 11:24:34,967 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task MemberValidationTask - performing task callbacks
2011-02-24 11:24:35,389 DEBUG <Thread-42> [TrackerObject] Sync complete: DomainHealth:VMVIEWMAIN|JOHNSONS to version: 38
2011-02-24 11:24:35,389 DEBUG <Thread-42> [TrackerManager] Sending message: (TrackerMessage SYNC {}: {v=38, tn=DomainHealth, u=[{"type":"SET","item":{"name":"ATTR_DOMAIN_NAME","type":"STRING","stringValue":"JOHNSONS"}},{"type":"SET","item":{"name":"ATTR_DOMAIN_DNS","type":"STRING","stringValue":"Johnsons.local"}},{"type":"SET","item":{"name":"ATTR_DOMAIN_STATE","type":"STRING","stringValue":"OK"}},{"type":"SET","item":{"name":"ATTR_DOMAIN_TRUSTTYPE","type":"STRING","stringValue":"PRIMARYDOMAIN"}},{"type":"SET","item":{"name":"ATTR_DOMAIN_CONTACTABLE","type":"STRING","stringValue":"FULLYACCESSIBLE"}},{"type":"SET","item":{"name":"ATTR_DOMAIN_ISNT4","type":"STRING","stringValue":"false"}},{"type":"SET","item":{"name":"HEALTH_LAST_UPDATE_TIME","type":"LONG","longValue":1298546675389}}], nn=vmviewmain, oi=VMVIEWMAIN|JOHNSONS})
2011-02-24 11:24:35,545 DEBUG <VCHealthUpdate> [TrackerObject] Sync complete: VcHealth:VMVIEWMAIN|190a86e6-34f7-4724-a404-d70368de18b4 to version: 36
2011-02-24 11:24:35,545 DEBUG <VCHealthUpdate> [TrackerManager] Sending message: (TrackerMessage SYNC {}: {v=36, tn=VcHealth, u=[{"type":"SET","item":{"name":"HEALTH_LAST_UPDATE_TIME","type":"LONG","longValue":1298546675545}}], nn=vmviewmain, oi=VMVIEWMAIN|190a86e6-34f7-4724-a404-d70368de18b4})
2011-02-24 11:24:35,592 DEBUG <ConfigureAgentVPs-1298544395244> [ConfigureVPsFederatedTask] VP policies: licensed=false, desktops=0, pools=0, machines=0, skipped=0, noVP=0, matched=0, toupdate=0
2011-02-24 11:24:35,733 DEBUG <Federated.TransferServerHeartbeatTask-1298544394722> [g] Handling a tracker update for Federated.TransferServerHeartbeatTask, item name=pae-TaskPercentageComplete
2011-02-24 11:24:35,733 DEBUG <Federated.TransferServerHeartbeatTask-1298544394722> [g] Handling a tracker update for Federated.TransferServerHeartbeatTask, item name=pae-TaskProgressData
2011-02-24 11:24:35,733 DEBUG <Federated.TransferServerHeartbeatTask-1298544394722> [TrackerObject] Sync complete: TaskTracker:Federated.TransferServerHeartbeatTask to version: 55
2011-02-24 11:24:35,733 DEBUG <Federated.TransferServerHeartbeatTask-1298544394722> [TrackerManager] Sending message: (TrackerMessage SYNC {}: {v=55, tn=TaskTracker, u=[{"type":"SET","item":{"name":"pae-TaskPercentageComplete","type":"INTEGER","integerValue":-1}},{"type":"SET","item":{"name":"pae-TaskProgressData","type":"MAP","mapValue":{"Waiting for next heartbeat":"PENDING","Waiting for transfer servers":"RUNNING","Getting updates from transfer servers":"PENDING"}}}], nn=vmviewmain, oi=Federated.TransferServerHeartbeatTask})
2011-02-24 11:24:35,733 DEBUG <Federated.TransferServerHeartbeatTask-1298544394722> [g] Have updated the progress in the tracker for task Federated.TransferServerHeartbeatTask
2011-02-24 11:24:35,749 DEBUG <TaskFramework:CallbackHandler> [g] Handling a tracker update for task Federated.TransferServerHeartbeatTask - performing task callbacks
2011-02-24 11:24:35,796 DEBUG <CBHealthUpdate> [TrackerObject] Sync complete: BrokerHealth:VMVIEWMAIN to version: 57
2011-02-24 11:24:35,796 DEBUG <CBHealthUpdate> [TrackerManager] Sending message: (TrackerMessage SYNC {}: {v=57, tn=BrokerHealth, u=[{"type":"SET","item":{"name":"HEALTH_LAST_UPDATE_TIME","type":"LONG","longValue":1298546675796}},{"type":"SET","item":{"name":"ATTR_BROKER_VERSION","type":"STRING","stringValue":"4.5.0"}},{"type":"SET","item":{"name":"ATTR_BROKER_BUILD","type":"STRING","stringValue":"4.5.0 build-293049"}},{"type":"SET","item":{"name":"ATTR_BROKER_IP","type":"STRING","stringValue":"192.168.16.157"}},{"type":"SET","item":{"name":"ATTR_BROKER_DNS","type":"STRING","stringValue":"vmviewmain.Johnsons.local"}},{"type":"SET","item":{"name":"ATTR_BROKER_NETBIOSNAME","type":"STRING","stringValue":"VMVIEWMAIN"}},{"type":"SET","item":{"name":"ATTR_BROKER_CLUSTERID","type":"STRING","stringValue":"Cluster-VMVIEWMAIN"}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_SESSIONS","type":"INTEGER","integerValue":0}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_SESSION_HIGH","type":"INTEGER","integerValue":0}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_SVI_SESSIONS","type":"INTEGER","integerValue":0}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_SVI_SESSIONS_HIGH","type":"INTEGER","integerValue":0}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_CHECKEDOUT_VMS","type":"INTEGER","integerValue":0}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_CHECKEDOUT_VMS_HIGH","type":"INTEGER","integerValue":0}}], nn=vmviewmain, oi=VMVIEWMAIN})
2011-02-24 11:24:36,828 DEBUG <SGHealth-federatedtask-1298544395014> [SGHealth] Processing health info from secure gateway vmviewmain
2011-02-24 11:24:36,828 DEBUG <SGHealth-federatedtask-1298544395014> [SGHealth] Cannot obtain an identity for vmviewmain that can be used by the broker.
2011-02-24 11:24:36,828 DEBUG <SGHealth-federatedtask-1298544395014> [TrackerObject] Sync complete: SGHealth:VMVIEWMAIN to version: 35
2011-02-24 11:24:36,828 DEBUG <SGHealth-federatedtask-1298544395014> [TrackerManager] Sending message: (TrackerMessage SYNC {}: {v=35, tn=SGHealth, u=[{"type":"SET","item":{"name":"HEALTH_LAST_UPDATE_TIME","type":"LONG","longValue":1298546676828}},{"type":"SET","item":{"name":"ATTR_SG_VERSION","type":"STRING","stringValue":"4.5.0"}},{"type":"SET","item":{"name":"ATTR_SG_BUILD","type":"STRING","stringValue":"4.5.0 build-293049"}},{"type":"SET","item":{"name":"ATTR_SG_URL","type":"STRING","stringValue":"https://vmviewmain.Johnsons.local:443"}},{"type":"SET","item":{"name":"ATTR_SG_HOSTNAME","type":"STR...}}], nn=vmviewmain, oi=VMVIEWMAIN})

0 Kudos
ukfatboy
Contributor
Contributor
‎02-24-2011 04:02 AM

It appears the vmview connection server is still attempting to connect to the vcentre server on port 443 EVEN THOUGH i specifically set it to port 5443 during the setup/configuration phase.....i assume this is the reason people seem to be recommending leaving the ports as default during vcentre server setup as the option to specify a port does NOT work when using vmview connection server as it will use port 443 anyway! If this is the case it NEEDS FIXING FAST.

(TrackerMessage SYNC {}: {v=3, tn=VcCacheTrackedVCs, u=[{"type":"SET","item":{"name":"lastSeen","type":"LONG","longValue":1298548588834}},{"type":"SET","item":{"name":"firstRunComplete","type":"INTEGER","integerValue":1}}], nn=vmviewmain, oi=190a86e6-34f7-4724-a404-d70368de18b4})
11:56:46,318 WARN  <TrackerJMSPublisher> [JMSMessagePublisher] Outbound message delayed: 17046 queuesize: 7 (TrackerMessage HEARTBEAT {}: {ns=ONLINE, nn=vmviewmain, hc=16})
11:56:46,318 WARN  <TrackerJMSPublisher> [JMSMessagePublisher] Outbound message delayed: 14544 queuesize: 6 (TrackerMessage HEARTBEAT {}: {ns=ONLINE, nn=vmviewmain, hc=17})
11:56:46,318 WARN  <TrackerJMSPublisher> [JMSMessagePublisher] Outbound message delayed: 12042 queuesize: 5 (TrackerMessage HEARTBEAT {}: {ns=ONLINE, nn=vmviewmain, hc=18})
11:56:46,333 WARN  <TrackerJMSPublisher> [JMSMessagePublisher] Outbound message delayed: 9555 queuesize: 4 (TrackerMessage HEARTBEAT {}: {ns=ONLINE, nn=vmviewmain, hc=19})
11:56:46,333 WARN  <TrackerJMSPublisher> [JMSMessagePublisher] Outbound message delayed: 8272 queuesize: 3 (TrackerMessage SYNC {}: {v=1, tn=BrokerHealth, u=[{"type":"SET","item":{"name":"HEALTH_LAST_UPDATE_TIME","type":"LONG","longValue":1298548598061}},{"type":"SET","item":{"name":"ATTR_BROKER_VERSION","type":"STRING","stringValue":"4.5.0"}},{"type":"SET","item":{"name":"ATTR_BROKER_BUILD","type":"STRING","stringValue":"4.5.0 build-293049"}},{"type":"SET","item":{"name":"ATTR_BROKER_IP","type":"STRING","stringValue":"192.168.16.157"}},{"type":"SET","item":{"name":"ATTR_BROKER_DNS","type":"STRING","stringValue":"vmviewmain.Johnsons.local"}},{"type":"SET","item":{"name":"ATTR_BROKER_NETBIOSNAME","type":"STRING","stringValue":"VMVIEWMAIN"}},{"type":"SET","item":{"name":"ATTR_BROKER_CLUSTERID","type":"STRING","stringValue":"Cluster-VMVIEWMAIN"}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_SESSIONS","type":"INTEGER","integerValue":0}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_SESSION_HIGH","type":"INTEGER","integerValue":0}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_SVI_SESSIONS","type":"INTEGER","integerValue":0}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_SVI_SESSIONS_HIGH","type":"INTEGER","integerValue":0}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_CHECKEDOUT_VMS","type":"INTEGER","integerValue":0}},{"type":"SET","item":{"name":"ATTR_BROKER_NUM_CHECKEDOUT_VMS_HIGH","type":"INTEGER","integerValue":0}}], nn=vmviewmain, oi=VMVIEWMAIN})
11:56:46,333 WARN  <TrackerJMSPublisher> [JMSMessagePublisher] Outbound message delayed: 7053 queuesize: 2 (TrackerMessage HEARTBEAT {}: {ns=ONLINE, nn=vmviewmain, hc=20})
11:56:46,333 WARN  <TrackerJMSPublisher> [JMSMessagePublisher] Outbound message delayed: 4550 queuesize: 1 (TrackerMessage HEARTBEAT {}: {ns=ONLINE, nn=vmviewmain, hc=21})
11:56:51,510 ERROR <TP-Processor3> [Connection] Connection to the vCenter Server https://192.168.16.39:443/sdk failed.

0 Kudos
npeter
Expert
Expert
‎02-24-2011 04:30 AM

Hi,

Yes as i had mentioned in reply-5 this is a known issue and there is a service request filed to fix this.

The problem is that you can connect VC using a non-default port but cannot enable view composer.

Thanks

Noble

-nObLe
0 Kudos
ukfatboy
Contributor
Contributor
‎02-24-2011 06:23 AM

Well in that case it might be worth vmware putting that fact on the download section so when people download they know not to use any other port and therefore won't WASTE THREE DAYS WORK TIME messing about with a product that does not work properly!!!

0 Kudos
npeter
Expert
Expert
‎02-28-2011 09:15 PM

A kb article is available now at http://kb.vmware.com/kb/1035091

-nObLe
0 Kudos