Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

VMware Smart Assurance NCM: RA not accessible post upgrade to 9.5.x/9.6 (78728)

Last Updated: 5/8/2020Categories: TroubleshootingTotal Views: 3237Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Unable to launch RA (http 404 error on page) post upgrade to version 9.6 from 9.3.
$TOMCAT_HOME/logs/Catalina.log will show that tomcat is started and running fine but RA will not launch.
No error is noticed in $TOMCAT_HOME/logs/Voyence.log.

Cause

Multiple RAs are installed in old NCM install. New flag has been introduced from NCM version 9.5 onwards where only single RA can be registered with one AS other RAs which are installed after this will be ignored by AS during registration process.

Snippet from RA logs $TOMCAT_HOME/logs:

Localhost log:

13-Feb-2020 10:39:47.728 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log No Spring WebApplicationInitializer types detected on classpath

13-Feb-2020 10:39:47.740 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.listenerStart Error configuring application listener of class [com.voyence.web.reporting.jreport.JRServerContextListener]

java.lang.ClassNotFoundException: com.voyence.web.reporting.jreport.JRServerContextListener

at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1291)

at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)

at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:544)

at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:525)

at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:150)

at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4667)

at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5207)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

License log:

WARN : 2020-02-10 06:27:05,590: RALicenseListener: RA Web Page cannot be launched, because another RA Server has already registered. Please contact EMC Support.

WARN : 2020-02-13 10:58:43,326: RALicenseListener: RA Web Page cannot be launched, because another RA Server has already registered. Please contact EMC Support.

WARN : 2020-02-13 11:00:11,981: RALicenseListener: RA Web Page cannot be launched, because another RA Server has already registered. Please contact EMC Support.

WARN : 2020-02-13 11:09:24,151: RALicenseListener: RA Web Page cannot be launched, because another RA Server has already registered. Please contact EMC Support.

WARN : 2020-02-13 11:27:02,721: RALicenseListener: RA Web Page cannot be launched, because another RA Server has already registered. Please contact EMC Support.

Resolution

Follow the below steps to resolve the issue
1. Login to AS and execute "source /etc/voyence.conf"
2. Export infraDB with below command:
Navigate to $VOYENCE_HOME/cgi-bin and run ./cflist.cgi > infraDB.txt
3. Take backup of infraDB.txt file. Open file infraDB.txt, edit the attribute RA_SERVER_IP to correct/one RA IP address.
4. Write changes to infraDB with below command:
./cfwrite.cgi < infraDB.txt
5. Restart vcmaster in AS with command "service vcmaster restart".
6. Restart tomcat and httpd services in RA.
7. Try to launch RA and it should work.

NOTE: If you are unaware how to edit InfraDB, create SR with VMware Technical Support Team with this KB number since editing it wrong might corrupt InfraDB and creates inconsistency between InfraDB and controlDB.

Workaround

If restart of services is not an option during business hours, follow below:
Follow steps 1-4 in Resolution section and the implement below:
a. On AS, edit powerup.jnlp available at $VOYENCE_HOME/ncmcore/webapps/voyence for line below, update correct/one RA IP address.
<property name="jnlp.legacy_reports_advisor_url" value="https://RA_SERVER_IP/web/"/>
b. Save and close file.
c. Try to launch RA now and it will work.

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
•
VMware Workspace ONE Intelligent Hub 20.04 for Android リリースのお知らせ (78888)

KB
•
Workspace ONE Intelligence for Consumer Apps 2020/05/06 リリースのお知らせ (78963)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant