First Web Client Login error - DRM 11.1.2.1

Similar Questions

• Just improved 5.0 to 6.0u2 vcenter.  How do eliminate you the web client certificate error?

  We were a vSphere 5.0 shop for many years and enjoyed the client c# 4.0, 4.1 and 5.0 then days.  We just upgraded 6.0 Update 2 this week and although always, we are primarally used to the c# client and will use it for a while to come, I am getting used to the web client for the new features that are available only in it, such as SRM and VR.

  I was able to click through the numours of screens of reminder to get via Firefox after all these certificate warnings and even easier just click the one or two things in Chrome or IE to get in.  But how could eliminate total certificate errors?  Example, now I'm with Chrome, but the https:// in the address bar is red with a slash through it.

  In most all other device based on web or connection we have, as HP iLO, Dell iDrac etc... usually, we create a CSR on this device and it present our internal Windows certificate authority and recover a file to go back to the device.  Is it possible to do this with the web client?  We have a certificate of 'Server Web 2' model that generates the sha256 return certificate and inherently all field devices to trust him because the area is important our root certificate authority.

  Also, we are running services such as replication vSphere and SRM, I would not change certificate affects only or same vSphere Update Manager.  We have two sites HQ and DR.

  I ended up getting rid of the cert errors by following this page: 6 replacement vSphere SSL certificate / implementation by using the Certificate Manager-automation tool

  I followed the procedures for "Certificate of Machine (Reverse HTTP Proxy) replace with certificate custom" and just that.  I didin 't' t mess with root VMCA with custom signature certificate certificate because its seems to me like he wanted to do an endless number of the signature of the certificate request and keys.  But the first option considered for our internal Windows CA took care of her.

  For replication of vSphere 6.1.1 that I had to turn off the virtual devices from replication via customer web vSphere vSphere and then put them back on.  Then connect to their URL of web management (port 5490) and make the reconnection to the vsphere on the connection tab, where he was invited to accept the new certificate.

  For AUVS I had to run the VMwareUpdateManagerUtility.exe under C:\Program Files (x 86) \VMware\Infrastructure\Update Manager and to the third option of re - register to vCenter, and then restart the service.

  Surprisingly, SRM sites remained paired although I've read that some people have trouble with it.  I'm on 6.0 update 2 and I think one of the questions was fixed in 6.0 Update 1 b.

• NDMS Siebel Developer Web Client Setup error.

  Hello!

  When you try to install the Client Web of Siebel Developer (8.1.1.10) find an error on the step to choose DB.

  You will not be able to connect to Microsoft SQL. Please make sure that NAC is installed

  I use MS 2003 Server/SQL 2008. I had already installed NAC v.10. It is officially support on this version of Siebel (8.1.1.10).

  Bookshellf:

  "For the Microsoft SQL Server deployments, the correct versions of SQL Native Client (SNAC) and Microsoft Data Access Components (MDAC) must reside on the computer where you install the Web Client of Siebel. For Microsoft SQL Server 2008, you use SQL Server Native Client 10.0 instead of SQL Native Client. »

  Please, help to find the right solution.

  Kind regards

  
  

  You can check whether the message is relevant?

  Siebel Developer and Mobile Siebel Tools client installation: prior checks fails (Doc ID 1321056.1)

  Looks like you might have more success with NAC 9.0.

• vCenter 5.5 Web Client Login - authentication hangs for minutes...

  I just finished an upgrade on the VCSA since the latest 5.1 to, I guess, the last 5.5.0b. Upgrade was surprisingly fast and clean and, so far, the only large thing of sorts (apart from the environment variable missing for remote console causing Java to fail - I fixed) is the process of connection.

  It is a very simple VCSA executes all integrated services (SSO database) with no external authentication or other difficulties. The some user accounts and passwords seem to have met very well as well.

  Each connection is working, but the progress bar hangs 'Authenticating' animated on the screen for several minutes before allowing the user access. Once, things seem to work well (at their level usual slow, but not worse than 5.1 was never for us).

  Any thoughts on the source of this endless hang?

  -Aaron

  Ah! Too bad. I did some more research and found this POS removal procedure:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2038356

  It worked like a charm. Login is back to normal now.

  I hope this helps others if they encounter the problem!

  -Aaron

• FRM-92150: WEB Client Version too new.

  Hi all
  
  I had installed 11i in a RHEL ES4
  Installation happens to be successful...
  
  But when I try to access the forms of the same application from a XP Professional client machine. I get the following error:
  
  FRM-92150: WEB Client Version too new.
  
  What version of jinitiator issue...?
  
  When I gathered some solution for the problem above, I found that the reference jar in the file formsweb.cfg file must be changed.
  
  But he did not explain what must be changed in detail...
  
  It would be a great help if I can get advice for the same problem to solve...
  
  Thank you very much...

  First try to clear the CACHE POT.

  -> Jinitiator Console-> tab Cache-> click on clear cache.

  on the other

  "" Note: 164220.1 review: Troubleshooting "FRM-92160: too old Web client version ' error in R11i:

• The /drm-web-client/Logon.aspx file was not precompiled and cannot be requested.

  Hi all

  We currently use DRM Version 11.1.2.2.302 patch.

  We are facing the error when we open the web console below.

  The /drm-web-client/Logon.aspx file was not precompiled and cannot be requested.

  It used to work very well and we see that this web configuration file has been updated. I assume that there is a problem with Internet Information services.

  Any help would be greatly appreciated.

  Thank you

  VINET

  Hi all

  The Web configuration file has been modified by windows service and after restarting the server, new web configuration file has been created and we have web access console.

  VINET

• The Web client error

  We reinstalled device - 5.5.2.1 - 2179237, but after the deployment, we are not able to connect via browser. Error is the following: connection failed: incompatibility of the username/password or account temporarily blocked after too many failed attempts

  1. Log in to vSphere Web Client as an administrator of the SSO, [email protected] with the password defined during installation.
  2. Click Administration.
  3. If closed, expand Single Sign-On by clicking the arrow to the left.
  4. Click on Configuration.
  5. Click the tab of the identity Sources .
  6. Click the Add identity Source ( ) under the options menu.
  7. Select Active Directory (Windows integrated authentication) .

     Note: If the domain name field is not propagated automatically with the good DNS Windows domain, enter the appropriate DNS domain.

  8. Select the user account from the computer , and then click OK.

     After the Active Directory identity source is configured, users in this domain can be added to vCenter Server. Then you can login with the password and user of the AD.

• vSphere SSL for the Web Client (device vCenter) certificate error

  Hello

  I installed ESXi 5.5 and right once I deployed the device vCenter. After the configuration and a few reboots, I navigates to the web client, and I get this error when I try to logon:

  "Based on the current configuration, the authentication server's SSL certificate was not reliable."

  I have until this google everything on the subject and outside tutorials on how to change certificates in the Windows version of vCenter, nothing on the device of vCenter. I was happy when I found the 'Certificate regeneration enabled' checkbox, but that did not help either. I can test successfully SSO settings in the control panel of vCenter.

  Everyone please?

  
  

  Edit: I should also mention that I am not able to connect to vCenter with the vSphere client. I get the "Cannot complete the connection by incorrect username or password". I use [email protected] as user name.

  Have you tried that? VMware KB: Troubleshooting the vCenter Server Appliance with Single Sign-On login

• vCenter Appliance Web Configuration of Client SSO error

  Currently have a vSphere 4.1 with two hosts ESXi environment.  vCenter is on a VM dediated on a single host.

  I'm moving to 5.1 and have chosen to deploy the unit vCenter instead of upgrading my VM.  A through the deployment and installation of the device through the web GUI.  Everything seemed to have configured correctly (DB, SSO, AD auth, etc.).  This is where it gets weird.

  I can access the vCenter via web client uses Windows authentication.  By using the same user credentials in the local client on my computer, it says I don't have permission.  In the web client, when I go to Administration-> Sign-On and discovery-> Configuration, I get an error on any tab, I selected:

  Error: com.vmware.vim.binding.sso.fault.InvalidCredentials:

  inherited from com.vmware.vim.binding.vmodl.fault.SecurityError:

  inherited from com.vmware.vim.binding.sso.fault.InvalidCredentials

  I'm about to give up and just upgrade my current vCenter, but I like the idea of the dedicated device.  I can't find any documentation on this error, or what I'm doing wrong.  It is very difficult to find documentation on the device.

  Thoughts? v

  Well, I can't tell you how to solve this problem, but maybe Kendrick Coleman 5.1 vSphere vCenter Virtual Appliance and vSphere Client video tutorial Web series will help you to successfully deploy the vCenter Server Appliance. At least she helped me to solve some problems I had with the first installations.

  André

• VCSA 6.0u1 (updated 6.0 VCSA) vSphere Web Client error

  

  After that I upgraded my VCSA 6.0 to 6.0u1, I can't connect to the Web Client vSphere.

  How upgrade from 5.x and 6.x VCSA to VCSA 6.0 Update 1? virtuallyGhetto

  Clock animation Flash Adobe turn for a few moments, then it gives the error in the attached screenshot. «There is an internal error occurred - Index '0' specified is out of range.» It happens in IE10 and Chrome.

  It is a standalone PSC and I can connect to the device management https:// < vcsa >: 5480 and apparently in good health. Can I deploy a new VCSA from scratch, but it would be nice if I could fix it.

  Any suggestion would be appreciated!

  And if the clearing the cache of the web browser does not solve your problem, try to delete the database of serenity:

  To delete the files in the VMware vSphere Client Web serenity database:

  1. Stop the vSphere WebClient service. For more information, see stopping, starting, or you restart the services of VMware vCenter Server (1003895) and the stop, start, or restart services from VMware vCenter Server 6.0 (2109881).
  2. To delete the files in the database of serenity, type these commands:

     For Windows vCenter Server 5.x:

     Use File Explorer to delete the content of C:\programdata\vmware\vSphere Web Client\SerenityDB\serenity
     For Windows vCenter Server 6.0.x:

     Use File Explorer to delete the content of C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity

     For the VMware vCenter Server Appliance 5.x:

     Type this command when logged in as root with a shell of the console or SSH session:

     rm - rf/etc/vmware-vsphere-client/SerenityDB/serenity / *.

     For the VMware vCenter Server Appliance 6.0.x:

     Type this command when logged in as root with a shell of the console or SSH session:

     rm - rf/storage/vsphere-client/SerenityDB/serenity / *.

  3. Restart the vSphere WebClient service. For more information, see stopping, starting, or you restart the services of VMware vCenter Server (1003895) and the stop, start, or restart services from VMware vCenter Server 6.0 (2109881).

  Source: VMware KB: The VMware vSphere Client Web reports an internal error 1009

• "VerifyError: Error #1053: illegal override of CustomProxy...". ', for the plugin in Web Client 6.0

  I'm having a problem with a plugin developed for 5.1. Works very well with the two web client 5.1 and 5.5.

  I'm trying to deploy the same plug-in in the web client 6.0 and follows with the reference of this binding changes for compatibility:

  2 important reminders for your plugin 5.5 is compatible with the Web Client 6.0

  -Change Web-ContextPath, vsphere client /-name of the plugin in the MANIFEST. MF

  -Configured by default two channels, one amf and secure-amf services - config.xml and remote - config.xml.:

  After these changes, I was able to resolve the "cannot load resources... '. "errors. And I am able to see my plugin icon.

  
  

  I made changes to my own proxy class (CustomProxy) to use ServiceUtil.getDefaultChannelUri (). I added the ServiceUtil code to my plugin rather the upgrade of an SDK 5.1 to SDK 5.5.2.

  Now get an error message when you click the icon of the plugin:

  "VerifyError: Error #1053: illegal override of CustomProxy...". ». Please find the screenshot of the flash error attached drive.

  Could someone guide possible cause and resolution of the issue?

  
  

  Thank you.

  Now I realize the you will not be able to compile it:

  public void callService(methodName:String,_arguments:Array,_callback:Function_=_null,_callContext:Object_=_null,_ _opId:String_=_null_):void {}

  It turns out that BaseProxy backward compatibility is broken If we substitute the callService method . We'll resolve this in the next version of hotfix or update.

  I can you advice how to solve this problem for your plugin. And it will work with 6.0. But after that we released the patch, your code will break. The only thing you can do at this stage is to remove from your CustombaseProxy.

  So I recommend the following:

  1 extract the logic that you have about the utility class, for example ProxyArgumentsUtil

  I don't understand why keep you the reference to m_reqMetaData and not to create a new instance for each request.

  If you do this, you can have a simple util class with a single static method in it. If you need this reference, then your utility class should be instantiated.

  2. all the classes that extend CustomBaseProxy should extend directly the BaseProxy

  3. whenever you call callService, use this ProxyArgumentsUtil to manage your "arguments" parameter

  4. remove the CustomBaseProxy

  Apologize for the inconvenience.

• vCenter Web client: a server error has occurred. [500] SSO error: null

  Hello all, I have problem with vCenter 6.0

  I installed vCenter 6.0 with service of external platform controller.

  I saw when I worked in the Web client alert (warning), something like "vAPI health alarm.

  Now, I can not connect to the Web client with the error 'a server error has occurred. .

  [500] SSO error: null

  " Check the logs from the Server Web Client vSphere for details."

  And I can't connect to vCenter with vsphere client.

  In the logfile "vsphere_client_virgo.txt" I have seen the error:

  [2015 04-08 T 14: 28:38.505 - 07:00] [WARNING] http-bio-9443-exec-1

  70000146 100005 200003 org.springframework.flex.core.DefaultExceptionLogger

  The following exception occurred during treatment with the BlazeDS MessageBroker in demand and will be serialized to the client: flex.messaging.MessageException: com.vmware.vsphere.client.error.ApplicationException: unable to connect to the services of vSphere.  Connection for vSphere Web Client and try again.

  at flex.messaging.services.remoting.adapters.JavaAdapter.invoke(JavaAdapter.java:444)

  at com.vmware.vise.messaging.remoting.JavaAdapterEx.invoke(JavaAdapterEx.java:50)

  at flex.messaging.services.RemotingService.serviceMessage(RemotingService.java:183)

  at flex.messaging.MessageBroker.routeMessageToService(MessageBroker.java:1400)

  at flex.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:1011)

  to flex.messaging.endpoints.AbstractEndpoint$ $FastClassByCGLIB$ $1a3ef066.invoke (< generated >)

  at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)

  to org.springframework.aop.framework.Cglib2AopProxy$ CglibMethodInvocation.invokeJoinpoint (Cglib2AopProxy.java:689)

  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)

  at org.springframework.flex.core.MessageInterceptionAdvice.invoke(MessageInterceptionAdvice.java:66)

  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

  at org.springframework.aop.framework.adapter.ThrowsAdviceInterceptor.invoke(ThrowsAdviceInterceptor.java:124)

  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

  to org.springframework.aop.framework.Cglib2AopProxy$ FixedChainStaticTargetInterceptor.intercept (Cglib2AopProxy.java:573)

  to com.vmware.vise.messaging.endpoints.AMFEndpoint$ $EnhancerByCGLIB$ $75e2a5d4.serviceMessage (< generated >)

  at flex.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:103)

  at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:158)

  at flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:44)

  at flex.messaging.endpoints.amf.BatchProcessFilter.invoke(BatchProcessFilter.java:67)

  at flex.messaging.endpoints.amf.SerializationFilter.invoke(SerializationFilter.java:166)

  at flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.java:291)

  to com.vmware.vise.messaging.endpoints.AMFEndpoint$ $EnhancerByCGLIB$ $75e2a5d4.service (< generated >)

  at org.springframework.flex.servlet.MessageBrokerHandlerAdapter.handle(MessageBrokerHandlerAdapter.java:109)

  at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)

  at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)

  at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)

  at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)

  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

  at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

  at com.vmware.vise.security.SessionManagementFilter.doFilterInternal(SessionManagementFilter.java:82)

  at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

  at com.vmware.vsphere.client.logging.MDCLogFilter.doFilterInternal(MDCLogFilter.java:41)

  at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

  at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)

  at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)

  at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)

  at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)

  at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)

  at org.eclipse.virgo.web.tomcat.support.ApplicationNameTrackingValve.invoke(ApplicationNameTrackingValve.java:33)

  at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)

  at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)

  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)

  at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)

  to org.apache.coyote.AbstractProtocol$ AbstractConnectionHandler.process (AbstractProtocol.java:607)

  to org.apache.tomcat.util.net.JIoEndpoint$ SocketProcessor.run (JIoEndpoint.java:315)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

  to java.util.concurrent.ThreadPoolExecutor$ Worker.run (ThreadPoolExecutor.java:615)

  at java.lang.Thread.run(Thread.java:745)

  Caused by: com.vmware.vsphere.client.error.ApplicationException: unable to connect to the services of vSphere.  Connection for vSphere Web Client and try again.

  at com.vmware.vsphere.client.error.ErrorReportUtil.getService(ErrorReportUtil.java:126)

  at com.vmware.vsphere.client.error.ErrorReportPage.toErrorStack(ErrorReportPage.java:168)

  at com.vmware.vsphere.client.error.impl.ErrorReportServiceImpl.getErrorStack(ErrorReportServiceImpl.java:48)

  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

  at java.lang.reflect.Method.invoke(Method.java:606)

  at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)

  at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)

  at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)

  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

  at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)

  at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)

  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

  at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)

  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

  at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)

  at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)

  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

  at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)

  to com.sun.proxy. $Proxy232.getErrorStack (unknown Source)

  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

  at java.lang.reflect.Method.invoke(Method.java:606)

  at flex.messaging.services.remoting.adapters.JavaAdapter.invoke(JavaAdapter.java:418)

  ... 56 omitted common images

  I tried to restart the vcenter services and received the error

  

  Then I tried to start vcenter sevice

  

  Once I rebooted two virtual machines (vCenter and PSC) it works short time (about 2-3 days).

  Who knows how to solve this problem?

  Hi KissTobor,

  I solved my problem, but it was different in my case.

  In vsphere web clients log I found massaes something like this "psc.test.local don't answer."

  I try ping psc.test.local, result was compensate, DNS name has not solved. As a result, I found that I can't ping my domen controller. Problem was in my network, routing did not work well.

  Thanks for trying to help me.

• Error in the logs when a workflow running on the web client of vSphere WARN {} [TypeQualifierToDecoratorConverter] could not find the mapping for: class ch.dunes.model.type.qualifier.TQCallerParameter, [kind:null, name:contextualParameter, value: __NULL__

  I see this error:

  WARN {} [TypeQualifierToDecoratorConverter] could not find the mapping for: class ch.dunes.model.type.qualifier.TQCallerParameter, [kind:null, name:contextualParameter, value: __NULL__]

  pop up in newspapers of vCO a few times on a workflow when I try to run it from the web client of vSphere.  I wonder if it is somehow contributing to the time it takes to render the page.  We never saw it or someone has a clue about what might be the cause.  Newspapers are clean when I run the workflow of the vCO client.

  TQCallerParameter is a kind of decorator that is not exposed in the REST API. This warning message is safe and does not affect performance at all.

  You don't see it during execution of the workflow of vCO customer because the customer vCO does not use the REST API and therefore does not need to run conversions Decorator.

• vSphere Web Client error - an internal error occurred - error #1009.

  I'm running a questions accessing the page plug-ins of the client in the Web Client vSphere. The error is in the subject line and an extract from the journal of the vsphere_client_virgo is below. Here is the scenario in which I believe is the origin of the problem, I don't know how to fix it.

  I had a third-party web client-plugin registered (Manager Cisco Nexus 1000v). and I disabled it. I then went through the steps to cancel the webclient plugin which was to remove the extension from the extensions through the CROWD handler. I deleted the extension to go from the CROWD and remove the files from the client web plugin on the server vCenter successfully, but now I get the above error. I think I'm getting this because the web client tries to find a reference to the disabled extension, either vCenter Server binaries or the extension, I removed from the CROWD. Whatever it is, I have no idea how to move forward. All ideas are welcome!

  vCenter Version: 5.5 build 1476327

  Caused by: java.lang.NullPointerException: null

  at com.vmware.vise.extensionfw.ExtensionManager.getDisabledPluginPackageInfos(ExtensionManager.java:618)

  at com.vmware.vise.extensionfw.impl.ExtensionServiceImpl.getDisabledPluginPackageInfos(ExtensionServiceImpl.java:110)

  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

  at java.lang.reflect.Method.invoke (unknown Source)

  at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)

  at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)

  at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)

  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

  at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)

  at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)

  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

  at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)

  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

  at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)

  at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)

  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

  at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)

  to com.sun.proxy. $Proxy223.getDisabledPluginPackageInfos (unknown Source)

  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

  at java.lang.reflect.Method.invoke (unknown Source)

  at flex.messaging.services.remoting.adapters.JavaAdapter.invoke(JavaAdapter.java:418)

  ... 53 omitted common images

  I ended up doing a reinstall of the vCenter. Once I uninstalled it, I also had to remove everything from \ProgramData\VMware.

• VSphere Web client and client heavy cannot connect to Vcenter server 5.5, web client fails with 2032 error before the connection, then the work after one minutes ferw.

  Hi all

  I really need help here.  I have a new installation of Esxi5.5 and installed the server vcenter build 5.5.0.5201 device 1476389.

  I have host files properly configured for DNS and Server 2008 R2 running that I use to connect with the client or web client heavy.

  Initially, I get an error with the web client to connect, he began to paint Vmware and when it comes to 'r' in the name it fails with #2032, so I can no longer

  access the page at all, he says: connection refused for the page. If I wait a while I can connect again.

  heavy client vSphere fails at this time as well.  However, I cannot communicate directly with Vsphere client to server esxi host and it works all the time.

  There seems to be a problem with the device of vcenter server because the thick client fails, and does not open a backup program using vcenter server

  inventory when this happened.

  Please help, it drives me crazy...

  Dan

  Hello

  Since I found the solution to the problem of connecting to the device of vcenter.  It is a conflict of IP address on the network.  There was a machine with the same IP address virtuall

  as the vcenter server.  This caused intermittent problems etc.. Why web client would still work if I have the vmware client open I do not know

  so thank you for your help.

  Dan