DPE Provider UI Plugin Shows Error: "TypeError: e.error.json is not a function!"

Resumo: DPE Provider UI Plugin shows error: TypeError: e.error.json is not a function.

Este artigo aplica-se a Este artigo não se aplica a Este artigo não está vinculado a nenhum produto específico. Nem todas as versões do produto estão identificadas neste artigo.

Sintomas

API requests do not complete, are not responding.

Business Impact: DPE is offline, unable to backup or restore virtual machines using DPE.

Issue seen on VCP 19.4.
Operating System: Other

The following errors are seen on the VPA under /var/log/vcp/srv/vcp-server.log:
2021-02-10 14:25:08,885 [Avamar Update] ERROR (VcUpdateContext.java:73) - BAD backup appliance: bf9b3f09-49b4-46e4-8ac1-57eb2528e5de name: bg-example-av-com -- 01101: Connection refused
2021-02-10 14:25:08,888 [Avamar Update] ERROR (VcUpdateWorker.java:1541) - Update to Avamar encountered an error. Will retry later.
2021-02-10 14:25:08,903 [Avamar Update] INFO  (RestTemplateFactory.java:125) - GET https://bg-example.av.net:8443/vcp-ba-ads-ws/BackupServer
2021-02-10 14:25:08,905 [Avamar Update] ERROR (RestTemplateFactory.java:249) - Connection Refused: org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://bg-fqdn:8443/vcp-ba-ads-ws/BackupServer": Connect to bg-fqdn8443 [bg-fqdn/IP] failed: Connection refused (Connection refused); nested exception is
.
.
2021-02-10 14:25:28,034 [Avamar Update] ERROR (RestTemplateFactory.java:249) - Connection Refused: org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://bg-example.av.net:8443/vcp-ba-ads-ws/BackupServer": Connect to bg-example:8443 [bg-example.fqdn/IP] failed: Connection refused (Connection refused); nested exception is org.apache.http.conn.HttpHostConnectException: Connect to bg-example.av.net:8443 [bg-example.fqdn/IP] failed: Connection refused (Connection refused)

VCP-MANAGER Service log on the VPA at /var/log/vcp/vcp-manager.log shows the following error:
2021-02-16 03:47:48,167 [AMQP listener 2] ERROR (VcpBaseMessageHandler.java:156) - HTTP 400 : com.emc.vcp.service.exceptions.URLServiceException: 02202: Application not found.
2021-02-16 03:47:58,732 [AMQP listener 1] ERROR (VcpBaseMessageHandler.java:156) - HTTP 400 : com.emc.vcp.service.exceptions.URLServiceException: 02202: Application not found.
2021-02-16 03:47:58,838 [AMQP listener 5] ERROR (VcpBaseMessageHandler.java:156) - HTTP 400 : com.emc.vcp.service.exceptions.URLServiceException: 02202: Application not found.
2021-02-16 03:48:42,035 [AMQP listener 9] ERROR (VcpBaseMessageHandler.java:156) - HTTP 400 : com.emc.vcp.service.exceptions.URLServiceException: 02202: Application not found.
2021-02-16 03:48:42,121 [AMQP listener 8] ERROR (VcpBaseMessageHandler.java:156) - HTTP 400 : com.emc.vcp.service.exceptions.URLServiceException: 02202: Application not found.
2021-02-16 03:54:05,039 [AMQP listener 3] ERROR (VcpBaseMessageHandler.java:156) - HTTP 500 : com.emc.vcp.service.exceptions.AdsClientException: 11002 : Error in browsing backup:
2021-02-16 03:54:06,590 [AMQP listener 8] ERROR (VcpBaseMessageHandler.java:156) - HTTP 500 : com.emc.vcp.service.exceptions.AdsClientException: 11002 : Error in browsing backup:
2021-02-16 03:54:16,278 [AMQP listener 5] ERROR (VcpBaseMessageHandler.java:156) - HTTP 502 : com.emc.vcp.service.exceptions.AdsClientException: 02105: User is not authorized to access this Resource.
2021-02-16 03:54:16,593 [AMQP listener 6] ERROR (VcpBaseMessageHandler.java:156) - HTTP 502 : com.emc.vcp.service.exceptions.AdsClientException: 02105: User is not authorized to access this Resource.
com.emc.vcp.service.exceptions.AdsClientException: 02105: User is not authorized to access this Resource

Verifying the service status and services may show as running:
vcp-cli bg status (Checks Backup gateway service status on VPA)
vcp-cli srv status (Checks SRV/Cell service status on VPA)
systemctl status vcp-manager.service  (Checks VCP-MANAGER service status on VPA)

Causa

Under investigation.

Resolução

  1. Open SSH to VPA VM.
  2. Restart vcp-manager service:
systemctl restart  vcp-manager.service
  1. Verify that the service is running:
systemctl status vcp-manager.service
  1. Restart the srv-cell service:
vcp-cli srv stop --password <MASTERPASS> <Cell-Instance-name>
vcp-cli srv start --password <MASTERPASS> <Cell-Instance-name>
  1. Verify that the service is running:
vcp-cli srv status
  1. Restart the BG service:
vcp-cli bg stop --password <MASTERPASS>  <BG-Instance-name>
vcp-cli bg stop --password <MASTERPASS>  <BG-Instance-name>
  1. Verify that the service is running:
vcp-cli bg status
  1. Reopen DPE Provider UI and confirm that Data Protection tab populates correct information and Backup gateways report correct version. 

Produtos

PowerProtect Data Protection Appliance, Avamar Data Store, Avamar Virtual Edition, PowerProtect Data Protection Software, Integrated Data Protection Appliance Family, vCloud Director Data Protection Extension
Propriedades do artigo
Número do artigo: 000183861
Tipo de artigo: Solution
Último modificado: 20 dez. 2022
Versão:  5
Encontre as respostas de outros usuários da Dell para suas perguntas.
Serviços de suporte
Verifique se o dispositivo está coberto pelos serviços de suporte.