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:

Dell EMC Unity: ESRS connectivity Error Code: 0x6400bb9

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



Unity Family

– Usually receives the error Failed to enable Integrated Remote Support. ( Error Code: 0x6400bb9 )

or

– Trying to enable ESRS on the array but continue to receive the following error: Error Code: 0x6400bb9.

The error including the date and time of the error, the activity that may have caused the error, and any other related activities that are in progress in the environment.

Troubleshooting sequence :

To resolve an error, complete the following steps:

1. Note the details of the error including the date and time of the error, the activity that may have caused the error, and any other related activities that are in progress in the environment.

Note: For example, if the error is related to the deletion of a snapshot and if a third-party snapshot software is managing snapshots on the platform, note all the relevant information.

2. To run Collect Service Information from the Unisphere Dashboard:

a. Under the System heading, select Service. The Overview page appears.

b. Select Service Tasks.

c. Select Collect Service Information.

d. Click Execute.

e. Click + to create a service data collection file.

f. Download to save the file.

3. Check the support website for FAQs, Release Notes, and known issues.

4. Close any open windows of the Unisphere GUI (clear browser cache/history, if required) and reopen the browser.

5. Log in to Unisphere again.

6. To check the system health:

a. From the dashboard view, select System Health > Hardware.

b. Check for any detected hardware faults or other issues. If there are any issues, refer to the related Unisphere online help topic or the onscreen instructions to resolve them.

c. Under the Events heading, select Alerts. The Alerts page appears.

d. Check for any alerts that indicate a problem. Check the errors in the log files.

i. Under the System heading, select Service. The Overview page appears.

ii. Select Logs.

e. To check if any SPs are in Service mode:

i. Under the System heading, select Service. The Overview page appears.

ii. Select Service Tasks.

iii. In the Storage Processor pane, check the Mode field for any SPs in Service mode. If any SPs are in Service mode, address the reason. When the SP in Service mode is selected, the Status field shows the reason for the Service mode and Recommended Action field shows the recommended action.

7. To restart the Management Software through the Service System page in Unisphere:

Note: Restarting the management software does not interrupt any system processes or I/O of the storage.

a. Under the System heading, select Service. The Overview page appears.

b. Select Service Tasks.

c. In the Storage System pane, select Restart Management Software.

d. Click Execute to restart the management software.

e. Wait for 4-6 minutes while the management software restarts.

Kindly refer to All Unisphere error codes in the below link.

Troubleshooting Checklist : https://www.emc.com/collateral/TechnicalDocument/docu69358.pdf

Related:

7021956: Secure Shell (SSH, SCP, and SFTP) Return Codes in UNIX

Error Codes

The purpose of an error code is to describe the error occurring in a program; it may display on the command line or in a log or a trace file.

SSH Error Codes

0
Success
1
Generic error
2
Remote host connection failure

SCP/SFTP Error Codes

The numbering scheme of the SCP/SFTP error codes was derived by adding 64 to the RFC4253 error code, for example, 64 + 1 = 65.

Source: RFC4253 error code + 64

65
Host not allowed to connect
66
Protocol error
67
Key exchange failed
68
Host authentication failed
69
MAC error
70
Compression error (not used in SSH2)
71
Service not available
72
Protocol version not supported
73
Host key not verifiable
74
Connection lost
75
Disconnected by application
76
Too many connections
77
Cancelled by user
78
No more auth methods available
79
Illegal user name

Exit Codes

You can display an exit code by typing echo $? after executing an SSH, SCP, or SFTP command.

Attachmate-defined SCP/SFTP Exit Codes

0
Success
1
Undetermined error in file copy
3
Destination is not directory, but it should be
4
Connecting to host failed
5
Connection lost for some reason
6
File does not exist
7
No permission to access file
8
Undetermined error from sshfilexfer
9
File transfer protocol mismatch
255
Error occurred in SSH

Related:

Bluemix dedicated Server error, status code: 500, error code: 0, message:

We are using Continuous Delivery Dedicated to deploy our code. From last couple of days the deploy always failing. When I see the error log it showing “Server error, status code: 500, error code: 0, message: “. I try to push the command bx app push app_name. Its also throw server error with 500 status code along with message RESPONSE: [2017-12-21T21:24:51+05:30]
HTTP/1.1 500 Error
Connection: close
Content-Type: text/xml
X-Backside-Transport: FAIL FAIL

500 Error: Failed to establish a backside connection
Here is the runtime screenshot
![alt text][1]

[1]: /answers/storage/temp/19265-9c62368dc60a1dd.jpg

Our application is very critical application so any help will be appreciated.

Related:

Re: rman backup failed with asdf_output_section1()

hi:

We are getting the following error when backing up a database on AIX server….

RMAN-03009: failure of backup command on t3 channel at 12/12/2016 23:10:35

ORA-19502: write error on file “fullbak1_89rnan7b_2313_930438379”, block number 540289 (block size=8192)

ORA-27030: skgfwrt: sbtwrite2 returned error

ORA-19511: Error received from media manager layer, error text:

asdf_output_section1() failed

xdr=0x111678e90: bp=0x111679230: send_len=262144: type=12800: fhand=0x111679290: wrapper=0x1116792b0: directp=0x1116792d0 (1:4:32)

channel t3 disabled, job failed on it will be run on another channel

RMAN-03009: failure of backup command on t4 channel at 12/12/2016 23:10:35

ORA-19502: write error on file “fullbak1_87rnal1i_2311_930436146”, block number 8172897 (block size=8192)

ORA-27030: skgfwrt: sbtwrite2 returned error

ORA-19511: Error received from media manager layer, error text:

asdf_output_section1() failed

xdr=0x111678cd0: bp=0x111678cf0: send_len=262144: type=12800: fhand=0x111678f30: wrapper=0x111678f50: directp=0x111678f70 (1:4:32)

channel t4 disabled, job failed on it will be run on another channel

released channel: t1

released channel: t2

released channel: t3

released channel: t4

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03009: failure of backup command on t1 channel at 12/12/2016 23:10:50

ORA-19502: write error on file “fullbak1_88rnan0t_2312_930438173”, block number 1266433 (block size=8192)

ORA-27030: skgfwrt: sbtwrite2 returned error

ORA-19511: Error received from media manager layer, error text:

asdf_output_section1() failed

xdr=0x111678dd0: bp=0x111678df0: send_len=262144: type=12800: fhand=0x111678ed0: wrapper=0x111678ef0: directp=0x111678f10 (1:4:1)

Recovery Manager complete.

The backup process failed:

RMAN exited with return code ‘1’.

Exiting with error:

RMAN exited with return code ‘1’.

hxzg_db01: RMAN exited with return code ‘1’.

Related:

Re: Error while Launching AGENTEXEC

Hi,

I am facing error while launching dm_agent_exec utility.

Below is the error in logs :

Fri Sep 15 11:17:17 2017 [FATAL ERROR] [AGENTEXEC or LAUNCHER] Detected during program initialization: Command Failed: dmApiInit();, status: 0, with error message .

The dm_agent_exec utility is exiting due to a fatal error.

Fri Sep 15 12:27:23 2017 407487 [DM_SESSION_W_AGENT_EXEC_FAILURE_EXCEED]warning: “The failure limit of the agent exec program has exceeded. It will not be restarted again. Please correct the problem and restart the server.”

Also, while executing iapi and idql utility i am getting below error message:

dmAPIInit() failed with return code 0.Can’t register Documentum Server Extensions

Also ,No ‘agentexec.log’ found under ‘$DOCUMENTUM/dba/log/<Rep_id>’ location.

Please help me to resolve the issue.

Thanks in Advance!!

Related:

Error while Launching AGENTEXEC

Hi,

I am facing error while launching dm_agent_exec utility.

Below is the error in logs :

Fri Sep 15 11:17:17 2017 [FATAL ERROR] [AGENTEXEC or LAUNCHER] Detected during program initialization: Command Failed: dmApiInit();, status: 0, with error message .

The dm_agent_exec utility is exiting due to a fatal error.

Fri Sep 15 12:27:23 2017 407487 [DM_SESSION_W_AGENT_EXEC_FAILURE_EXCEED]warning: “The failure limit of the agent exec program has exceeded. It will not be restarted again. Please correct the problem and restart the server.”

Also, while executing iapi and idql utility i am getting below error message:

dmAPIInit() failed with return code 0.Can’t register Documentum Server Extensions

Also ,No ‘agentexec.log’ found under ‘$DOCUMENTUM/dba/log/<Rep_id>’ location.

Please help me to resolve the issue.

Thanks in Advance!!

Related:

Handling error codes in Watson conversation

Hi all,

We are calling the watson api using node request npm. In this for some watson error cases like {“code”:500,”message”:”Forwarding error”}, {“code”:504,”message”:”Timeout Exceeded”}, we are still getting the http statuscode as 200.

So how should we handle the error condition? What will be the common error code that we can handle in our app in case of error?

Is there any particular HTTP statuscode that we can consider in common or is there any list of Watson error codes that we should handle?

Looking forward to a good solution as we are getting different errors each time.

Thanks in advance

Related: