Device enrolment fails “Error 1700” (the gateway is unavailable)

I need a solution

Hi there.

Trying to enrol an OS X device and received a fairly unhelpful error message that hasn’t been documented anywhere that I can find.

In any case, opening the browser console makes it pretty clear something is just down.

The response body looks like this:

<html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>

Summary
URL: https://sepc.securitycloud.symantec.com/api/enroll...
Status: 504
Source: Network
Address: 34.227.155.xxx:443

The request POST body looked like this:

{"product-name":"os","company-owned":"true","sep-mobile":true,"mdm-off":false}

I’m generally disappointed by the SEPC portal, but we have to use SEPC more or less because of our size (smaller than would justify an MSP), who our clients are (mostly government that requires US-based antivirus) and our devices (all Macs), so, looking for options. There’s also no obvious way to get online support except for this forum… what’s that about?

0

Related:

  • No Related Posts

DLP Agent 15.1 configure flexresponse Error “PGPsdk.dll is missing”

I need a solution

Hi all

I have a issue install flexresponse integration with symantec endpoint encryption. After I try to install flexresponse on windwos 10 DLP Agent 15.1. 

The Error show message “PGPsdk.dll is missing” . How to resolve the issue?

0

Related:

ViPR Controller: “Error 2000: Unable to find entity specified” when running a custom catalog entry[1]

Article Number: 525313 Article Version: 4 Article Type: Break Fix



ViPR Controller

The user is trying to run a custom ViPR Controller Catalog entry that was created/modified and it errors with the following message:

Error 2000: Unable to find entity specified in URL with the given id urn:storageos:VirtualPool:xxx-xxx-xx-xxx:vdc1

The same type of error could occur for other URNs and not just limited to Virtual Pools.

Previously the user had used ViPR Controller’s functionality to copy an existing catalog entry, rename the copy, and edited the new catalog entry to “Lock in” some values for some of the catalog entries options.

The custom catalog entry was linked to a specific virtual Pool that had since been deleted from VIPR-C.

In this scenario, the user had deleted a virtual pool from their ViPR Controller setup.

Workaround:

Since the Virtual Pool (and Virtual Array in this example) were deleted via the GUI, and since the user had previously locked in those values in a Catalog entry, the workaround was to re-edit the catalog entry and select new values (instead of the old deleted values).

When the user edited the problem catalog entry, they noticed that the “Locked” check box was still selected but the “value” field was empty:

screenshot of catalog editing screen

The user should either select a new value or uncheck the box if they do not want to lock in a specific value.


Resolution:

ViPR Engineering is currently addressing this problem, but has not provided a fix in a released patch.

This solution will be updated with the patch when it has been released.

Related:

Dell EMC Unity: Unisphere Job page fails to load with “Error Code:0x7d13001” (Dell EMC Correctable)

Article Number: 524995 Article Version: 2 Article Type: Break Fix



Dell EMC Unity Family

When accessing Events>Jobs tab in Unisphere you are met with the following error.

The system encountered an unexpected error. Search for the error code on the support website or product forums, or contact your service provider, if available. (Error Code:0x7d13001)Reload Unisphere UI?

EMCCEMlogcemtracer.log

23 Aug 2018 11:50:16 – [COMMON_DB_SHARED_LIB] ERROR – {0:254709:387164896}[22728|28131|d77ffb40][performRequest @ ../../../components/UI/CLI/plugins/commands/common_db/src/DBOperating.cpp:55] Caught pqxx::pqxx_exception (ERROR: integer out of range).

<.>

23 Aug 2018 11:50:16 – [UemCliProvider] ERROR – {0:254709:388543223}[22728|28131|d77ffb40][processRequest @ ../../../components/providers/native/CliProvider/src/UemCliProvider.cpp:435] Request processing completed with error: The system encountered an unexpected error. Search for the error code on the support website or product forums, or contact your service provider, if available. (Error Code:0x100e000)

There is potentially a Job with an elapsed time greater than 24 days which causes the Job tab to fail to load.

Please contact Dell EMC Technical Support or your Authorized Service Representative, and quote this Knowledgebase article ID.

Fix for this issue is scheduled in a future Unity OE release. The problem is cosmetic and only affects the viewing of active jobs. The workaround is non-disruptive and will require support only commands to address.

Related:

Isilon OneFS 8.1 Error enabling ESRS gateway: “Error response code from gateway: 401, Unauthorized”[1]

Article Number: 511087 Article Version: 7 Article Type: Break Fix



EMC Secure Remote Services Virtual Edition,EMC Secure Remote Services Virtual Edition 3.02,EMC Secure Remote Services Virtual Edition 3.04,EMC Secure Remote Services Virtual Edition 3.06,EMC Secure Remote Services Virtual Edition 3.08

Isilon OneFS 8.1 has two possible ESRS configurations, one for ESRS v2, and one for ESRS v3. The v3 requires a username and password. Attempting to enable the v3 configuration with the wrong user name and password will result in the ESRS gateway sending ‘401’ errors back to the cluster.

Example of the error when enabling the ESRS v3 configuration on the cluster:

cluster-1# isi esrs modify –enabled=true –username=user –password=EMC123

Internal error: ESRSBadCodeError: ESRS Add Device failed. Error response code from gateway: 401, Unauthorized. Response dictionary was: {{‘http_response_code’: 401, u’responseCode’: 401, u’serialNumber’: u’ELMISL######’, u’gatewaySerialNumber’: u’########’, u’veType’: u’Connected’, u’message’: u’Invalid username and password.’, u’model’: u’ISILON-GW’}}

messages log

cluster-1: 2017-10-03T11:30:42-05:00 <3.3> cluster-1 isi_rsapi_d[5314]: [0x800704000]: Proxy response contained errors, ESRS was not enabled.

cluster-1: 2017-10-03T11:30:43-05:00 <3.3> cluster-1 isi_esrs_d[75337]: ERROR: tardis ipc error: TARDIS_IPC_ERR_CONSTRAINT_VIOLATION; error while collecting response: UNIQUE constraint failed: kv_table.key, kv_table.os_version (19)

cluster-2: 2017-10-03T11:30:41-05:00 <3.3> cluster-2 isi_esrs_d[48808]: ERROR: tardis ipc error: TARDIS_IPC_ERR_CONSTRAINT_VIOLATION; error while collecting response: UNIQUE constraint failed: kv_table.key, kv_table.os_version (19)

cluster-2: 2017-10-03T11:30:42-05:00 <3.3> cluster-2 isi_rsapi_d[9470]: [0x800704400]: pcm_add_device python call failed: Traceback (most recent call last): File “/usr/local/lib/python2.7/site-packages/isi/esrs/restclient.py”, line 877, in pcm_add_device File “/usr/local/lib/python2.7/site-packages/isi/esrs/restclient.py”, line 842, in _gateway_failover File “/usr/local/lib/python2.7/site-packages/isi/esrs/restclient.py”, line 396, in _pcm_post File “/usr/local/lib/python2.7/site-packages/isi/esrs/restclient.py”, line 106, in _check_return_code ESRSBadCodeError: ESRS Add Device failed. Error response code from gateway: 401, Unauthorized. Response dictionary was: {{‘http_response_code’: 401, u’responseCode’: 401, u’serialNumber’: u’ELMISL#######’, u’gatewaySerialNumber’: u’############’, u’veType’: u’Connected’, u’message’: u’Invalid username and password.’, u’model’: u’ISILON-GW’}}

isi_esrs_d.log

cluster-1: 2017-10-03T11:30:43-05:00 <3.6> cluster-1 isi_esrs_d[75337]: INFO: Node 1 updating registered node tardis variables

cluster-1: 2017-10-03T11:30:43-05:00 <3.3> cluster-1 isi_esrs_d[75337]: ERROR: tardis ipc error: TARDIS_IPC_ERR_CONSTRAINT_VIOLATION; error while collecting response: UNIQUE constraint failed: kv_table.key, kv_table.os_version (19)

Attempting to enable with debug command

cluster-1# isi –debug esrs modify –enabled=true –username=user –password=EMC123

2017-10-03 11:37:46,000 DEBUG rest.py:70: >>>GET [‘remote-service’, ‘5’, ‘esrs’, ‘status’]

2017-10-03 11:37:46,000 DEBUG rest.py:72: args={}

body={}

2017-10-03 11:37:46,001 DEBUG rest.py:92: <<<(200, {‘status’: ‘200 Ok’, ‘content-type’: ‘application/json’, ‘allow’: ‘GET, PUT, HEAD’}, ‘n{n”esrs” : n{n”connectivity_status” : “Disconnected”,n”enabled” : falsen}n}n’)

2017-10-03 11:37:46,001 DEBUG rest.py:70: >>>PUT [‘remote-service’, ‘5’, ‘esrs’, ‘status’]

2017-10-03 11:37:46,001 DEBUG rest.py:72: args={}

body={‘username’: ‘root’, ‘password’: ‘********’, ‘enabled’: True}

2017-10-03 11:37:48,691 DEBUG rest.py:92: <<<(500, {‘status’: ‘500 Internal Server Error’, ‘content-type’: ‘application/json’, ‘allow’: ‘GET, PUT, HEAD’}, ‘n{n”errors” : n[nn{n”code” : “AEC_EXCEPTION”,n”id” : 3,n”lnn” : 3,n”message” : “Internal error: ESRSBadCodeError: ESRS Add Device failed. Error response code from gateway: 401, Unauthorized. Response dictionary was: {{‘http_response_code’: 401, u’responseCode’: 401, u’serialNumber’: u’ELMISL#######’, u’gatewaySerialNumber’: u’##########’, u’veType’: u’Connected’, u’message’: u’Invalid username and password.’, u’model’: u’ISILON-GW’}}\n”n}n]n}n’)

Internal error: ESRSBadCodeError: ESRS Add Device failed. Error response code from gateway: 401, Unauthorized. Response dictionary was: {{‘http_response_code’: 401, u’responseCode’: 401, u’serialNumber’: u’ELMISL0817J7V3′, u’gatewaySerialNumber’: u’ELMESR0617VH56′, u’veType’: u’Connected’, u’message’: u’Invalid username and password.’, u’model’: u’ISILON-GW’}}

2017-10-03 11:37:48,691 DEBUG isi:375: Internal error: ESRSBadCodeError: ESRS Add Device failed. Error response code from gateway: 401, Unauthorized. Response dictionary was: {{‘http_response_code’: 401, u’responseCode’: 401, u’serialNumber’: u’ELMISL########’, u’gatewaySerialNumber’: u’#############’, u’veType’: u’Connected’, u’message’: u’Invalid username and password.’, u’model’: u’ISILON-GW’}}

An associated traceback may also be seen

Traceback (most recent call last):

File “/usr/bin/isi”, line 383, in <module>

run_cli(controllers.isi)

File “/usr/bin/isi”, line 318, in run_cli

level = execute(module, argv, False)

File “/usr/bin/isi”, line 232, in execute

level.execute(data, optvals, **optvals)

File “/usr/local/share/CLI/decorators.py”, line 95, in __call__

super(modify_controller, self).__call__(data, optvals, **kwargs)

File “/usr/local/share/CLI/decorators.py”, line 57, in __call__

self.execute(data, **kwargs)

File “/usr/local/share/CLI/controllers/isi/esrs/modify.py”, line 78, in execute

status_data.put(d)

File “/usr/local/share/CLI/papi/container.py”, line 200, in put

self.last_result = self.conn.transact(papi.PUT, self.uri, args=args, body=value)

File “/usr/local/share/CLI/papi/rest.py”, line 124, in transact

raise RestError(response, message, error_fields)

papi.rest.RestError: Internal error: ESRSBadCodeError: ESRS Add Device failed. Error response code from gateway: 401, Unauthorized. Response dictionary was: {{‘http_response_code’: 401, u’responseCode’: 401, u’serialNumber’: u’ELMISL########’, u’gatewaySerialNumber’: u’##########’, u’veType’: u’Connected’, u’message’: u’Invalid username and password.’, u’model’: u’ISILON-GW’}}

Using incorrect credential when attempting to enable the ESRS configuration on the cluster.

Refer to https://support.emc.com/kb/510767 – Isilon: How To set up ESRS for OneFS v8.1+. It also includes information on troubleshooting new installs.

The issue is outside of Isilon’s control and is dependent upon configuration between ESRS and the Support EMC site. The error showing in the cluster logs, are actually errors the ESRS gateway is sending back to Isilon.

Enabling the ESRS v3 configuration on the cluster requires using the same Support EMC site credentials. The Support EMC credentials are the same ones used when logging into the website to manager Service Requests, search KBs, or download files.

If the credentials being used do not match that of the site, or if the credentials aren’t working or unknown. Engage with the Account team responsible for the site that is using the ESRS gateway. Changes may be required or related to ESRS itself, updates to the Customer Site information, the Install Base, or even changes to the account privileges associated with the Support EMC site.

Also, for the ESRS v3 configuration to work on Isilon, requires a signed and valid license.

Related:

ScaleIO: One SDS hanging causes IO errors and SDS_DISCONNECT / SDC_DISCONNECT events in ESXi environment

Article Number: 493460 Article Version: 3 Article Type: Break Fix



ScaleIO 2.0.0.3

Issue Description

One SDS hanging may lead to multiple ESXi hosts (and SVMs on them) reporting SDS_DISCONNECT / SDC_DISCONNECT events.

Scenario

This issue can usually be caused by bad disk, disk controller, or other hardware issues.

Symptoms

When one SDS hangs (because of bad disk, disk controller or other hardware issues), the following may happen:

  • SDCs start to report IO errors although only one SDS is experiencing issue
  • In ESXi environment, the entire cluster may observe SDC_DISCONNECT and SDS_DISCONNECT events

Impact

High impact. There may not be DU situation but SDCs’ IO requests would fail. When multiple servers start to disconnect, it may eventually lead to MDM_DATA_FAILED event.

The hanging SDS process may leave its sockets open, while not being able to process requests. This may make SDCs continue to try to send IO to it, causing timeout which may then lead to IO errors.

In ESXi environment, this may manifest SDS_DISCONNECT / SDC_DISCONNECT events from multiple servers, due to a bug in ESXi: when SDC sends a non-blocking message, ESXi may treat it as blocking message, resulting in sockets and Keep Alive (KA) misbehave, which in turn causes other components on these hosts (SDS, MDM, etc) to disconnect.

Workaround

N/A


Impacted versions

Below 2.0.0.3

Fixed in version

The unhandled SDS sockets are fixed in 2.0.0.3

VMware will provide fix to the ESXi bug in the following versions:

ESXi 6.0 Update 3 – PR 1407778

ESXi 5.5 P10 – PR 1714474

Related:

ScaleIO: Reset to disk device on SDS caused SDS to go decoupled and ScaleIO became degraded

Article Number: 492681 Article Version: 4 Article Type: Break Fix



ScaleIO 2.0.0.3

Reset to disk device on SDS caused SDS to go decoupled. SDCs saw this as I/O errors.

An SDS had an issue with a disk device which caused the device to be reset twice. During the second reset the system went in to degraded state and the SDS decoupled. Several SDCs saw this as I/O errors.

Following errors were noted on the SDS with the problem device:-

First Reset to the device:-

Oct 31 00:53:15 SDSNAME kernel: hpsa 0000:03:00.0: Abort request on C0:B0:T0:L10

Oct 31 00:53:15 SDSNAME kernel: hpsa 0000:03:00.0: invalid command: LUN:0a00004000000000 CDB:00000000303a00000000000000000000

Oct 31 00:53:15 SDSNAME kernel: hpsa 0000:03:00.0: probably means device no longer present

Oct 31 00:53:15 SDSNAME kernel: hpsa 0000:03:00.0: invalid command: LUN:0a00004000000000 CDB:0000000000003a300000000000000000

Oct 31 00:53:15 SDSNAME kernel: hpsa 0000:03:00.0: probably means device no longer present

Oct 31 00:53:15 SDSNAME kernel: hpsa 0000:03:00.0: FAILED abort on device C0:B0:T0:L10

Oct 31 00:53:15 SDSNAME kernel: hpsa 0000:03:00.0: resetting device 0:0:0:10

Oct 31 00:53:19 SDSNAME kernel: hpsa 0000:03:00.0: device is ready.

Second Reset to the same device:-

Oct 31 01:04:28 SDSNAME kernel: hpsa 0000:03:00.0: Abort request on C0:B0:T0:L10

Oct 31 01:04:28 SDSNAME kernel: hpsa 0000:03:00.0: invalid command: LUN:0a00004000000000 CDB:00000000201100000000000000000000

Oct 31 01:04:28 SDSNAME kernel: hpsa 0000:03:00.0: probably means device no longer present

Oct 31 01:04:28 SDSNAME kernel: hpsa 0000:03:00.0: invalid command: LUN:0a00004000000000 CDB:00000000000011200000000000000000

Oct 31 01:04:28 SDSNAME kernel: hpsa 0000:03:00.0: probably means device no longer present

Oct 31 01:04:28 SDSNAME kernel: hpsa 0000:03:00.0: FAILED abort on device C0:B0:T0:L10

Oct 31 01:04:28 SDSNAME kernel: hpsa 0000:03:00.0: resetting device 0:0:0:10

Oct 31 01:05:31 SDSNAME kernel: hpsa 0000:03:00.0: device is ready.

Oct 31 01:05:31 SDSNAME init: sds main process (21765) terminated with status 255

Oct 31 01:05:31 SDSNAME init: sds main process ended, respawning

On SDC we see the following errors in /var/log/messages file:-

SDC1

cat /var/log/messages|grep -i “I/O”

Oct 31 01:04:34 HOSTNAME1 kernel: end_request: I/O error, dev scinihl, sector 4073287

Oct 31 01:04:34 HOSTNAME1 kernel: end_request: I/O error, dev sciniib, sector 9617223

SDC2

cat /var/log/messages|grep -i “I/O”

Oct 31 01:04:34 HOSTNAME2 kernel: end_request: I/O error, dev scinidh, sector 167200

SDC3

cat /var/log/messages|grep -i “I/O”

Oct 31 01:04:34 HOSTNAME3 kernel: end_request: I/O error, dev sciniiv, sector 94216

The storage device that was experiencing hardware issues was delaying some of the IOs for more than 30 seconds causing an IO error on the SDC side. The issue is that while the device that was holding back some of the IOs for a longer duration was still servicing other IOs submitted to it (either from the device itself or from cache).

The long IO mechanism that was introduced in 2.0.0.3 was looking for IOs that are taking too long. If it detected that even some of the submitted IOs are serviced in a timely manner it would assume that the device is OK and wouldn’t trigger the long IO mechanism.

Issue is fixed in ScaleIO 2.0.0.3 HF Version: R2_0.8005.0

The 2.0.0.3-HF also addresses this issue by tracking all IOs submitted to the storage and not just the general pattern. Thus, 2.0.0.3-HF SDS would have detected that some of the IOs are delayed and would have triggered the Long IO mechanism causing the MDM to cool down the SDS and serve the IO from the secondary SDS.

Related:

VxRail: The server has encountered an unexpected internal error. Please try again later.” when attempting to upgrade from v 3.5 to v 4

Article Number: 500999 Article Version: 3 Article Type: Break Fix



VSPEX,VSPEX BLUE Appliance,VSPEX BLUE Appliance Hardware,VSPEX BLUE Appliance Software

Retry local upgrade from VxRail Manager failes with error ” The server has encountered an unexpected internal error. Please try again later.”

mystic@zptvxrail01:/var/log> cd mystic/

mystic@zptvxrail01:/var/log/mystic> tail -f vxrail-upgrade.log

VxRail-Upgrade: 2017-06-13 11:14:35,947.947 – ERROR Failed to Upgrade VxRail Patches, Due to ERROR: [Errno 12] Cannot allocate memory

VxRail-Upgrade: 2017-06-13 11:14:35,948.948 – DEBUG Clear PageCache, dentries, swap and inodes buffers

VxRail-Upgrade: 2017-06-13 12:29:40,066.066 – INFO Starting to Upgrade VxRail

VxRail-Upgrade: 2017-06-13 12:29:40,071.071 – DEBUG initializing vsphere parameters: Start

VxRail-Upgrade: 2017-06-13 12:29:40,089.089 – ERROR Failed to Upgrade VxRail Patches, Due to ERROR: [Errno 12] Cannot allocate memory

VxRail-Upgrade: 2017-06-13 12:29:40,091.091 – DEBUG Clear PageCache, dentries, swap and inodes buffers

VxRail-Upgrade: 2017-06-13 12:44:16,386.386 – INFO Starting to Upgrade VxRail

VxRail-Upgrade: 2017-06-13 12:44:16,386.386 – DEBUG initializing vsphere parameters: Start

VxRail-Upgrade: 2017-06-13 12:44:16,390.390 – ERROR Failed to Upgrade VxRail Patches, Due to ERROR: [Errno 12] Cannot allocate memory

VxRail-Upgrade: 2017-06-13 12:44:16,396.396 – DEBUG Clear PageCache, dentries, swap and inodes buffers

* rebooted VxRail Manager given hat the error shows Cannot allocate memory. After the reboot we could start the upgrade.

* completed upgrade from 3.5 to 4.0.100 successfully

VxRail Manager is not connected to the internet, internet upgrade is ruled out

lcm.log file is missing becuase the upgrade has not even started.

Related:

  • No Related Posts

Unisphere for VMAX 8.3.0: Unisphere 8.3.0.1 error sending mail

Article Number: 501109 Article Version: 4 Article Type: Break Fix



Unisphere for VMAX 8.3.0

Mail relay is allowed and it can resolve customer’s mail server but Customer gets mailserviceexception failed to deliver javamail message.

From the logs:

2017-05-11 08:24:15,236 ERROR [em.bp.MAIL] (default task-18) EmailNotificationCommandProcessor.processSendMailMessageCommand:Error sending mail message: javax.ejb.EJBException: com.emc.em.common.mail.MailServiceException: Failed to deliver JavaMail message

at org.jboss.as.ejb3.tx.BMTInterceptor.handleException(BMTInterceptor.java:83)

at org.jboss.as.ejb3.tx.EjbBMTInterceptor.checkStatelessDone(EjbBMTInterceptor.java:91)

at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:106)

at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:58)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)

at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73)

at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)

at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

.

.

.

Caused by: javax.mail.AuthenticationFailedException: 334 VXNlcm5hbWU6

at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:892)

at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:814)

at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:728)

at javax.mail.Service.connect(Service.java:364)

at com.emc.em.common.mail.MailService.getTransport(MailService.java:161)

… 117 more

Customer verified against KB: 478937, and 459812 and all checked out.

Upgrading the Unisphere for VMAX to 8.4 resolved the issue. Please refer to KB 494818.

Related:

  • No Related Posts