Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Listing Directory Group entities fails (52773)

Last Updated: 11/16/2018Categories: TroubleshootingTotal Views: 2990Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

From the vSphere Web Client (NSX plugin):

Listing Directory Group entities fails when creating or editing a Security Group with an error: Internal server error has occurred

In the NSX Manager logs (using show log manager), you see entries similar to:

2018-01-25 15:02:24.774 GMT WARN http-nio-127.0.0.1-7441-exec-3 RemoteInvocationTraceInterceptor:87 - Processing of VsmHttpInvokerServiceExporter remote call resulted in fatal exception: com.vmware.vshield.vsm.securitygroup.service.SecurityGroupFacade.getApplicableMembersByType
java.lang.NullPointerException
at com.vmware.vshield.blueprint.useridentity.service.ADMemberProvider.setDomainScope(ADMemberProvider.java:185)
at com.vmware.vshield.blueprint.useridentity.service.ADMemberProvider.getMembersByType(ADMemberProvider.java:105)
at com.vmware.vshield.vsm.securitygroup.service.SecurityGroupServiceImpl.getApplicableMembersByType_aroundBody116(SecurityGroupServiceImpl.java:823)
at com.vmware.vshield.vsm.securitygroup.service.SecurityGroupServiceImpl$AjcClosure117.run(SecurityGroupServiceImpl.java:1)
at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
at com.vmware.vshield.vsm.aspects.security.VsmSecuredAspect.secureCheck(VsmSecuredAspect.java:126)
[...]
2018-01-25 15:02:24.780 GMT DEBUG http-nio-127.0.0.1-7441-exec-3 RemoteInvocationBasedExporter:94 - Target method failed for RemoteInvocation: method name 'getApplicableMembersByType'; parameter types [java.lang.String, java.lang.String, java.util.Map, java.lang.String]
java.lang.NullPointerException
at com.vmware.vshield.blueprint.useridentity.service.ADMemberProvider.setDomainScope(ADMemberProvider.java:185)
at com.vmware.vshield.blueprint.useridentity.service.ADMemberProvider.getMembersByType(ADMemberProvider.java:105)
at com.vmware.vshield.vsm.securitygroup.service.SecurityGroupServiceImpl.getApplicableMembersByType_aroundBody116(SecurityGroupServiceImpl.java:823)
at com.vmware.vshield.vsm.securitygroup.service.SecurityGroupServiceImpl$AjcClosure117.run(SecurityGroupServiceImpl.java:1)
at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
at com.vmware.vshield.vsm.aspects.security.VsmSecuredAspect.secureCheck(VsmSecuredAspect.java:126)
[...]

In the vCenter virgo logs (vsphere-client/logs/vsphere_client_virgo.log), you see entries similar to:

[2018-01-25T15:02:24.875Z] [WARN ] http-bio-9090-exec-99 org.springframework.flex.core.DefaultExceptionLogger The following exception occurred during request pr
ocessing by the BlazeDS MessageBroker and will be serialized back to the client: flex.messaging.MessageException: com.vmware.vshield.vsm.remoting.server.exceptions.RemoteBaseExcept
ion : Internal server error has occurred.
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)
at flex.messaging.endpoints.AbstractEndpoint$$FastClassByCGLIB$$1a3ef066.invoke(<generated>)
[...]

From REST API (GET /api/3.0/ai/directorygroup):

The NSX Manager returns: HTTP 500 Internal Server Error

The response body is: <error><errorCode>100</errorCode></error>

In the NSX Manager logs (using show log manager), you see entries similar to:

2018-05-25 10:38:58.930 CEST ERROR http-nio-127.0.0.1-7441-exec-166 BaseRestController:518 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] REST API failed : 'null'
java.lang.NullPointerException: null
at com.vmware.vshield.blueprint.ai.reports.facade.EntityServiceFacadeImpl.fromDo(EntityServiceFacadeImpl.java:288) ~[blueprint-1.0.jar:?]
at com.vmware.vshield.blueprint.ai.reports.facade.EntityServiceFacadeImpl.getDirectoryGroups_aroundBody4(EntityServiceFacadeImpl.java:129) ~[blueprint-1.0.jar:?]
at com.vmware.vshield.blueprint.ai.reports.facade.EntityServiceFacadeImpl$AjcClosure5.run(EntityServiceFacadeImpl.java:1) ~[blueprint-1.0.jar:?]
at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149) ~[aspectjweaver-1.8.9.jar:1.8.9]
at com.vmware.vshield.vsm.aspects.security.VsmSecuredAspect.secureFeatureCheck(VsmSecuredAspect.java:162) ~[vsm-core-1.0.jar:?]
at com.vmware.vshield.vsm.aspects.security.VsmSecuredAspect.ajc$inlineAccessMethod$com_vmware_vshield_vsm_aspects_security_VsmSecuredAspect$com_vmware_vshield_vsm_aspects_security_VsmSecuredAspect$secureFeatureCheck(VsmSecuredAspect.java:1) ~[vsm-core-1.0.jar:?]
[...]

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs when some metadata is missing on the NSX Manager for a Directory Group object.

Impact / Risks

There is no impact to this issue. However, automation may not work due to the REST API call failing, and creating/editing Security Groups containing Directory Group entities from NSX Plugin for vSphere may not be possible.

Resolution

This issue is resolved in:
VMware NSX for vSphere 6.4.2, available at VMware Downloads.
VMware NSX for vSphere 6.3.7, available at VMware Downloads.

Note: Upgrading an affected NSX Manager to 6.4.2 or 6.3.7 will resolve the issue.

Workaround

To work around this issue if you do not want to upgrade, file a support request with VMware Support and quote this Knowledge Base article ID (52773)  in the problem description. For more information, see How to Submit a Support Request.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
ESXi 6.x 主机从 vCenter Server 断开 (2145106)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant