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

Data-collection failure in vRBC due to failure of Microsoft Azure APIs (67518)

Last Updated: 8/18/2023Categories: TroubleshootingTotal Views: 1837Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Azure EA data-collection, Azure EA account addition or Azure EA account update fails.

In /var/log/vrb/data-collector/itfm-azure-dc.log of the vRBC appliance, you see error message similar to:

Caused by: com.xxxxxx.itfm.cloud.datacollector.axxxx.util.AxxxxException: Microsoft Axxxx API server returned an unexpected response: HTTP/1.1 426 Upgrade Required, while making HTTP request: GET https://ea.axxxx.com/rest/xxxxxx/usage-reports?fmt=json

at com.xxxxxx.itfm.cloud.datacollector.axxxx.commons.AxxxxHttpUtils.httpInvoke(AxxxxHttpUtils.java:184) ~[itfm-axxxx-dc-core-7.0.1.0.jar:?]
at com.xxxxxx.itfm.cloud.datacollector.axxxx.commons.AxxxxHttpUtils.httpInvokeWithRetry(AxxxxttpUtils.java:116) ~[itfm-axxxx-dc-core-7.0.1.0.jar:?]
at com.xxxxxx.itfm.cloud.datacollector.axxxx.commons.AxxxxHttpUtils.httpInvoke(AxxxxHttpUtils.java:97) ~[itfm-axxxx-dc-core-7.0.1.0.jar:?]
at com.xxxxxx.itfm.cloud.datacollector.axxxx.commons.AxxxxHttpUtils.getMonthsForEaBillAvailability(AxxxxHttpUtils.java:487) ~[itfm-axxxx-dc-core-7.0.1.0.jar:?]
at com.xxxxxx.itfm.cloud.datacollector.axxxx.api.AxxxxEAClient.login(AxxxxEAClient.java:69) ~[itfm-axxxx-dc-core-7.0.1.0.jar:?]
at com.xxxxxx.itfm.cloud.datacollector.axxxx.service.AxxxxConfigurationService.testConnectionAddDetails(AxxxxConfigurationService.java:39) ~[itfm-axxxx-dc-core-7.0.1.0.jar:?]

Cause

Some of the Microsoft Azure APIs used by vRBC have been retired as of December 31, 2018.

Resolution

Follow the below specified sequence of steps to resolve the issue:

1. Take a snapshot of vRBC appliance
2. If the vRBC version is less than 7.5 , upgrade the vRBC to 7.5
Note: Before upgrade do check the compatibility of other products(like vRA) intgerated with vRBC if any and take necessary actions accordingly.
3. Edit the following file present in the vRBC appliance and add the new properties specified below.
File:
/usr/ITFM-Cloud/va-tools/va-conf/azure/azure.properties

Properties:
EA_BALANCE_SUMMARY_API_TRANSFORMER_SPEC_FILE_PATH=azure_ea_balance_summary_api_transformer.spec
EA_BILLING_PERIOD_API_TRANSFORMER_SPEC_FILE_PATH=azure_ea_billing_period_api_transformer.spec

4. Edit the following file present in the vRBC appliance and add the new properties specified below.
File:
/usr/local/tomcat/itbm-data-collector/conf/azure/azure.properties

Properties:
EA_BALANCE_SUMMARY_API_TRANSFORMER_SPEC_FILE_PATH=azure_ea_balance_summary_api_transformer.spec
EA_BILLING_PERIOD_API_TRANSFORMER_SPEC_FILE_PATH=azure_ea_billing_period_api_transformer.spec

5. Execute the below commands in the vRB VA to create the required specification files

cd /usr/ITFM-Cloud/va-tools/va-conf/azure/
cp azure_ea_billing_api_transformer.spec azure_ea_balance_summary_api_transformer.spec
cp azure_ea_billing_api_transformer.spec azure_ea_billing_period_api_transformer.spec
cd /usr/local/tomcat/itbm-data-collector/conf/azure/
cp azure_ea_billing_api_transformer.spec azure_ea_balance_summary_api_transformer.spec
cp azure_ea_billing_api_transformer.spec azure_ea_billing_period_api_transformer.spec

6. Download the patch vRB_server_patch_7.5.0.26847_11943388.zip by clicking the below link:

ftp://outbound:[email-masked]/patches/19042601601_2267152/vRB_server_patch_7.5.0.26847_11943388.zip

7. Apply the patch using the below steps:

a) On a 7.5 vRB server VA (Either freshly deployed for migration or existing  one) make sure all the services are running by doing  monit summary. This is mandatory in case of migration once you deploy the VA.
b) Enable SSH to the VA from the VAMI
c) Copy the vRB_server_patch_7.5.0.26847_11943388.zip to VA.
d) Unzip the patch zip file using  following command
unzip vRB_server_patch_7.5.0.26847_11943388.zip
e) Now run this command
cd vRB_server_patch_7.5.0.26847_11943388
f) Run this command to apply-hot-patch script using the following command. This will apply the patch.
sh apply-hot-patch.sh
g) After applying the patch, wait for all the services to come up. Monitor the same using 'monit summary'
h) Wait for UI to come up and check if everything is working fine.

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
•
Download and Install VMware Fusion (2014097)

KB
•
Downloading and Installing the standalone VMware Remote Console (VMRC) in vSphere (2091284)

VMware vSphere Client download

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Business for Cloud

Related Versions:

VMware vRealize Business for Cloud 7.5.x

Take Our Survey

Support Assistant