vsphere web client

[MAB_VM]

I want to open Vsphere web client for managing esx servers

i have this problem with firefox and explorer :smileyx: :smileyinfo:

[SavkoorSuhas]

Hello

Please enter the following in the url tab:

https://<vcenter_ip>:9443

Is this occurring with all your browsers?

[MAB_VM]

Hello !

Thanks SavkoorSuhasSavkoorSuhas

i'm trying with " https://<vcenter_ip>:9443 " But it's the same problem :smileyalert:

[SavkoorSuhas]

Hello,

Can you please upload the Web Client logs?

• Windows: C:\ProgramData\VMware\vSphere Web Client\serviceability\
• Linux: /var/log/vmware/vsphere-client/

Which version of vCenter are we running here? Is it Windows Based or Linux Based?

[MAB_VM]

Version: vcenter sever 6.0

sur windows server 2008

• Windows: C:\ProgramData\VMware\vSphere Web Client\serviceability\ :::

- <!--   Virgo log configuration

  See http://www.eclipse.org/virgo/documentation/virgo-documentation-3.6.3.RELEASE/docs/virgo-user-guide/h...

  -->

- <configuration>

  <contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator" />

- <!--  vsphere_client_virgo.log is the main Virgo log file

  -->

- <appender name="LOG_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">

  <file>C:/PROGRA~3/VMware/VCENTE~1/logs/VSPHER~1/logs/vsphere_client_virgo.log</file>

- <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">

  <FileNamePattern>C:/PROGRA~3/VMware/VCENTE~1/logs/VSPHER~1/logs/vsphere_client_virgo_%i.log.zip</FileNamePattern>

  <MinIndex>0</MinIndex>

  <MaxIndex>9</MaxIndex>

  </rollingPolicy>

- <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">

  <MaxFileSize>50MB</MaxFileSize>

  </triggeringPolicy>

- <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">

  <Pattern>[%d{yyyy-MM-dd'T'HH:mm:ss.SSSXXX}] [%-5level] %-28.28thread %X{sessionGuid} %-64.64logger{64} %X{medic.eventCode} %msg %ex%n</Pattern>

  </encoder>

  </appender>

- <!--  Per user logs are disabled by default as they don't add much value. To track a particular user in the main log (vsphere_client_virgo.log)

     find its login name and the clientId associated with it, then find all instances of that clientId

   <appender name="SIFTED_LOG_FILE" class="ch.qos.logback.classic.sift.SiftingAppender">

      <discriminator>

         <Key>userName</Key>

         <DefaultValue>noUser</DefaultValue>

      </discriminator>

      <sift>

         <appender name="${userName}_LOG_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">

            <file>C:/PROGRA~3/VMware/VCENTE~1/logs/VSPHER~1/logs/byUser/${userName}.log</file>

            <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">

               <FileNamePattern>C:/PROGRA~3/VMware/VCENTE~1/logs/VSPHER~1/logs/byUser/${userName}_%i.log.zip</FileNamePattern>

               <MinIndex>1</MinIndex>

               <MaxIndex>10</MaxIndex>

            </rollingPolicy>

            <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">

               <MaxFileSize>1MB</MaxFileSize>

            </triggeringPolicy>

            <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">

               <Pattern>[%d{yyyy-MM-dd'T'HH:mm:ss.SSSXXX}] [%-5level] %-28.28thread %X{sessionGuid} %-64.64logger{64} %X{medic.eventCode} %msg %ex%n</Pattern>

            </encoder>

         </appender>

      </sift>

   </appender>

  -->

- <appender name="EVENT_LOG_STDOUT" class="org.eclipse.virgo.medic.log.logback.ReroutingAwareConsoleAppender">

- <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">

  <Pattern>[%d{yyyy-MM-dd'T'HH:mm:ss.SSSXXX}] [%-5level] %-28.28thread %X{sessionGuid} <%X{medic.eventCode}> %msg %ex%n</Pattern>

  </encoder>

  </appender>

- <!--  eventlog.log is a small log recording only important events in Virgo, i.e. bundle activities, etc.

  -->

- <appender name="EVENT_LOG_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">

  <file>C:/PROGRA~3/VMware/VCENTE~1/logs/VSPHER~1/logs/eventlog.log</file>

- <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">

  <FileNamePattern>C:/PROGRA~3/VMware/VCENTE~1/logs/VSPHER~1/eventlogs/eventlog_%i.log.zip</FileNamePattern>

  <MinIndex>1</MinIndex>

  <MaxIndex>4</MaxIndex>

  </rollingPolicy>

- <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">

  <MaxFileSize>10MB</MaxFileSize>

  </triggeringPolicy>

- <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">

  <Pattern>[%d{yyyy-MM-dd'T'HH:mm:ss.SSSXXX}] [%-5level] %-28.28thread %X{sessionGuid} <%X{medic.eventCode}> %msg %ex%n</Pattern>

  </encoder>

  </appender>

- <!--  query_profile_dataservice.log is only used for debugging

  -->

- <appender name="DS_QUERY_PROFILE_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">

  <file>C:/PROGRA~3/VMware/VCENTE~1/logs/VSPHER~1/logs/query_profile_dataservice.log</file>

- <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">

  <FileNamePattern>C:/PROGRA~3/VMware/VCENTE~1/logs/VSPHER~1/logs/query_profile_dataservice_%i.log.zip</FileNamePattern>

  <MinIndex>0</MinIndex>

  <MaxIndex>9</MaxIndex>

  </rollingPolicy>

- <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">

  <MaxFileSize>50MB</MaxFileSize>

  </triggeringPolicy>

- <filter class="ch.qos.logback.core.filter.EvaluatorFilter">

- <evaluator class="ch.qos.logback.classic.boolex.OnMarkerEvaluator">

  <marker>DS_QUERY_PROFILE</marker>

  </evaluator>

  <onMismatch>DENY</onMismatch>

  <onMatch>NEUTRAL</onMatch>

  </filter>

- <encoder>

  <pattern>%msg%n@!@!@</pattern>

  </encoder>

  </appender>

- <root level="INFO">

  <appender-ref ref="LOG_FILE" />

- <!--  appender-ref ref="SIFTED_LOG_FILE" /

  -->

  </root>

- <!--  Here is how to increate the log level for a particular package

   <logger level="DEBUG" additivity="false" name="com.package_path...">

      <appender-ref ref="LOG_FILE" />

   </logger>

  -->

- <logger level="INFO" additivity="true" name="com.vmware.vise.data.query.impl.DataServiceImpl">

  <appender-ref ref="DS_QUERY_PROFILE_FILE" />

  </logger>

- <logger level="INFO" additivity="false" name="org.eclipse.virgo.medic.eventlog.localized">

  <appender-ref ref="EVENT_LOG_STDOUT" />

  <appender-ref ref="EVENT_LOG_FILE" />

  </logger>

- <logger level="INFO" additivity="false" name="org.eclipse.virgo.medic.eventlog.default">

  <appender-ref ref="LOG_FILE" />

- <!--  appender-ref ref="SIFTED_LOG_FILE" /

  -->

  </logger>

  </configuration>

[Peter_Ivanov]

Hello,

Please lookup and upload the vsphere_client_virgo.log file from your vCenter machine.

Another thing that might be helpful when troubleshooting login problems is to see the network traffic from your browser.

In Firefox, click Tools -> Web Developer -> Network

Please upload that too so that I can see when exactly the error occurred.

P.S. You can sent the files privately to me.

[MAB_VM]

I

[Peter_Ivanov]

Hello,

I can see a lot of errors and none of them seems browser-dependent.

I see a lot of deployment exceptions like this:

[2015-07-29T16:49:39.671+02:00] [ERROR] Thread-30                     com.vmware.vise.extensionfw.impl.JMXBundleDeployer                Error deploying file:/C:/PROGRA~1/VMware/VCENTE~1/WEBCLI~1/plugin-packages/vsphere-client/plugins/cis-data-service-6.0.0.war java.rmi.UnmarshalException: error unmarshalling return; nested exception is:

  java.lang.ClassNotFoundException: javax.management.openmbean.CompositeDataSupport in KernelBundleClassLoader: [bundle=com.vmware.extensionservice_6.0.0] (no security manager: RMI class loader disabled)

So I wonder if the web client is working at all...

Then come the errors from the SSO:

[2015-07-30T11:51:38.060+02:00] [ERROR] http-bio-9090-exec-6         70000031 100004 ###### com.vmware.vsphere.client.security.websso.MetadataGeneratorImpl   Error when registering ngc metadata. com.vmware.vise.vim.security.sso.exception.SsoServiceException: com.vmware.vim.vmomi.client.exception.VmomiProtocolException: com.vmware.vim.vmomi.core.exception.UnmarshallException: Unexpected element 'html'. Expected element is '{http://schemas.xmlsoap.org/soap/envelope/}Envelope'

[2015-07-31T12:17:11.270+02:00] [ERROR] cm-catalog-manager-pool-5     com.vmware.vise.vim.security.sso.impl.NgcSolutionUser             Login as solution user failed. com.vmware.vim.vmomi.client.exception.VmomiProtocolException: com.vmware.vim.vmomi.core.exception.UnmarshallException: Unexpected element 'html'. Expected element is '{http://schemas.xmlsoap.org/soap/envelope/}Envelope'

Then the client was restarted. After the restart I don't see deployment exceptions, which is good.

But then I see gain the SSO errors:

[2015-07-31T12:44:58.396+02:00] [ERROR] ing.timer.TimerFactoryBean#0  com.vmware.vise.vim.security.sso.impl.NgcSolutionUser             Login as solution user failed. com.vmware.vim.vmomi.client.exception.VmomiProtocolException: com.vmware.vim.vmomi.core.exception.UnmarshallException: Unexpected element 'html'. Expected element is '{http://schemas.xmlsoap.org/soap/envelope/}Envelope'

Can you try to do the following:

1. Stop the web client service

2. delete the   C:\Program Files\VMware\vCenter Server\WebClient\server\work folder

3. delete (or move) the web client log file (vsphere_client_virgo.log), so that I can see only the relevant log messages

4. start the web client service

5. try to login the web client

6. send me the new log file

Can you elaborate further on your setup:

- Are you using the embedded SSO?

- Is this a fresh install or an upgrade from previous release?

It is possible that initial registration of the Web Client in SSO has failed. I can see that from different log file.

Can you send me ngc_firstboot*.log from the following folder:

C:\ProgramData\VMware\vCenterServer\logs\firstboot

[RajeevVCP4]

If you have external PSC , check VC and PSC time should be correct.

if time synchronization is correct you can apply this KB, it worked for me.

https://kb.vmware.com/s/article/2144304