Error processing request contact your application administrator - Исправление ошибок и поиск оптимальных решений проблем

I have a problem with my Apex Server that I can not solve.

Error processing request.

Contact your application administrator. Details about this incident are available via debug id «3821666».

<!DOCTYPE html>

<html>

<head>

<title>Responsive Table</title>

<style>

* {

margin: 0;

padding: 0;

}

body {

font: 14px/1.4 Georgia, Serif;

}

Generic Styling, for Desktops/Laptops

table {

width: 100%;

border-collapse: collapse;

}

/* Zebra striping */

tr:nth-of-type(odd) {

background: #eee;

}

th {

background: #333;

color: white;

font-weight: bold;

}

td, th {

padding: 6px;

border: 1px solid #9B9B9B;

text-align: left;

}

@media

only screen and (max-width: 760px),

(min-device-width: 768px) and (max-device-width: 1024px) {

table, thead, tbody, th, td, tr { display: block; }

thead tr { position: absolute;top: -9999px;left: -9999px;}

tr { border: 1px solid #9B9B9B; }

td { border: none;border-bottom: 1px solid #9B9B9B; position: relative;padding-left: 50%; }

td:before { position: absolute;top: 6px;left: 6px;width: 45%; padding-right: 10px; white-space: nowrap;}

Label the data

td:nth-of-type(0):before { content: «ID»; }

td:nth-of-type(1):before { content: «PAGE_VIEW_ID»; }

td:nth-of-type(2):before { content: «MESSAGE_TIMESTAMP»; }

td:nth-of-type(3):before { content: «ELAPSED_TIME»; }

td:nth-of-type(4):before { content: «EXECUTION_TIME»; }

td:nth-of-type(5):before { content: «MESSAGE»; }

td:nth-of-type(6):before { content: «APPLICATION_ID»; }

td:nth-of-type(7):before { content: «PAGE_ID»; }

td:nth-of-type(8):before { content: «SESSION_ID»; }

td:nth-of-type(9):before { content: «APEX_USER»; }

td:nth-of-type(10):before { content: «MESSAGE_LEVEL»; }

td:nth-of-type(11):before { content: «WORKSPACE_ID»; }

td:nth-of-type(12):before { content: «CALL_STACK»; }

}

/* Smartphones (portrait and landscape) ———— */

@media only screen

and (min-device-width : 320px)

and (max-device-width : 480px) {

body {

padding: 0;

margin: 0;

width: 320px; }

}

/* iPads (portrait and landscape) ———— */

@media only screen and (min-device-width: 768px) and (max-device-width: 1024px) {

body {

width: 495px;

}

</style>

<!—<![endif]—>

lsearch = function(){

//this.term = document.getElementById(‘S’).value.toUpperCase();

var s = document.getElementById(‘search’).value.toLowerCase();

rows = document.getElementById(‘data’).getElementsByTagName(‘TR’);

for(var i=0;i<rows.length;i++){

if (s ==»» ){

rows[i].style.display =»;

} else if ( rows[i].innerText.toLowerCase().indexOf(s) != -1 ) {

rows[i].style.display =»;

} else {

rows[i].style.display =’none’;

}

this.time = false;

}

</script>

</head>

<body>

<th>MESSAGE_TIMESTAMP</th>

<th>ELAPSED_TIME</th>

<th>EXECUTION_TIME</th>

<th>MESSAGE</th>

<th>APPLICATION_ID</th>

<th>SESSION_ID</th>

<th>MESSAGE_LEVEL</th>

<th>WORKSPACE_ID</th>

<th>CALL_STACK</th>

</tr></thead>

<tr>

<td>%SESSION_CONTEXT.set_app_id:61

%SECURITY.start_page_request:3578

%.start_page_request:1803

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>Reset NLS settings</td>

<td>%LANG.reset_nls:658

%.start_page_request:1815

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>alter session set NLS_COMP=’BINARY’ NLS_SORT=’BINARY’ NLS_CALENDAR=’GREGORIAN’ NLS_TERRITORY=’AMERICA’ NLS_LANGUAGE=’AMERICAN'</td>

<td>%LANG.reset_nls:684

%.start_page_request:1815

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>Fetched language settings for app en: lang=»SESSION», derived from=»»</td>

<td>%LANG.set_g_primary_language:564

%LANG.custom_runtime_message:1647

%ERROR.raise_internal_error:1418

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>setting g_primary_language := en</td>

<td>%LANG.set_g_primary_language:597

%LANG.custom_runtime_message:1647

%ERROR.raise_internal_error:1418

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>no characterset conversion needed</td>

<td>%ESCAPE.init:988

%ESCAPE.__pkg_init:1017

%LANG.replace_param:966

%LANG.system_message:1413

%LANG.custom_runtime_message:1689

%ERROR.get_contact_admin_msg:1748

%ERROR.raise_internal_error:1432

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>Add error onto error stack</td>

<td>%ERROR.internal_add_error:1035

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>… get_component -> APEX_APPLICATIONS </td>

<td>%.get_component:2543

%ERROR.internal_get_error:974

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>Error: Error processing request.</td>

<td>%ERROR.debug_error:1654

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- additional_info: Contact your application administrator.

Details about this incident are available via debug id «3821666».</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1655

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- display_location: ON_ERROR_PAGE</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1656

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- is_internal_error: true</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1664

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- apex_error_code: APEX.UNHANDLED_ERROR</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1665

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- error_backtrace: —— PL/SQL Call Stack ——

object line object

handle number name

0x7fc0a848 971 package body APEX_190100.WWV_FLOW_ERROR.INTERNAL_GET_ERROR

0x7fc0a848 1039 package body APEX_190100.WWV_FLOW_ERROR.INTERNAL_ADD_ERROR

0x7fc0a848 1431 package body APEX_190100.WWV_FLOW_ERROR.RAISE_INTERNAL_ERROR

0x636a2a38 1848 package body APEX_190100.WWV_FLOW.START_PAGE_REQUEST

0x636a2a38 3667 package body APEX_190100.WWV_FLOW.SHOW

0x62835c40 52 procedure APEX_190100.APEX

0x62c53540 2 anonymous block

</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1668

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- component: APEX_APPLICATIONS (4500)</td>

<td>%ERROR.debug_error:1671

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>…Show Error on Error Page</td>

<td>%ERROR.paint_on_error_page:241

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>……Performing rollback</td>

<td>%ERROR.paint_on_error_page:246

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>reset p_keep_sticky_headers=>true</td>

<td>%RESPONSE.reset:229

%ERROR.paint_on_error_page:303

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>render_error_page</td>

<td>%PAGE.render_error_page:2879

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>page metadata still missing — loading now</td>

<td>%PAGE.render_error_page:2882

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>fetch_step_info</td>

<td>%META_DATA.fetch_step_info:627

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>Add error onto error stack</td>

<td>%ERROR.internal_add_error:1035

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>… get_component -> APEX_APPLICATIONS </td>

<td>%.get_component:2543

%ERROR.internal_get_error:974

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>Error: Application «4500» Page «» not found.</td>

<td>%ERROR.debug_error:1654

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- additional_info: Contact your application administrator.</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1655

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- display_location: ON_ERROR_PAGE</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1656

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- is_internal_error: true</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1664

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- apex_error_code: APEX.PAGE.NOT_FOUND</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1665

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- ora_sqlcode: -28500</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1666

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- ora_sqlerrm: ORA-28500: connection from ORACLE to a non-Oracle system returned this message:

[MySQL][ODBC 5.3(a) Driver]MySQL server has gone away {HY000,NativeErr = 2006}

ORA-02063: preceding 2 lines from DB

ORA-06512: at «APEX_190100.WWV_FLOW_LANG», line 685</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1667

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- error_backtrace: ORA-06512: at «APEX_190100.WWV_FLOW_LANG», line 685

ORA-06512: at «APEX_190100.WWV_FLOW», line 1815

</td>

<td>%ERROR.debug:1645

%ERROR.debug_error:1668

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>- component: APEX_APPLICATIONS (4500)</td>

<td>%ERROR.debug_error:1671

%ERROR.exec_error_handling_callback:876

%ERROR.internal_get_error:980

%ERROR.internal_add_error:1039

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>…Show Error on Error Page</td>

<td>%ERROR.paint_on_error_page:241

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>……Performing rollback</td>

<td>%ERROR.paint_on_error_page:246

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>Recursion of Error Page detected!</td>

<td>%ERROR.paint_on_error_page:258

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%META_DATA.fetch_step_info:844

%PAGE.render_error_page:2884

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>reset</td>

<td>%PAGE.reset:3144

%PAGE.render_error_page:2897

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>reset</td>

<td>%REGION.reset:536

%PAGE.reset:3155

%PAGE.render_error_page:2897

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>add_header p_key=>Content-Type,p_name=>Content-Type,p_value=>text/html; charset=utf-8,p_overwrite=>true,p_is_sticky=>false</td>

<td>%RESPONSE.add_header:70

%RESPONSE.mime:321

%PAGE.render_error_page:2899

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>write_headers p_close_header_section=>false</td>

<td>%RESPONSE.write_headers:460

%RESPONSE.add_header:108

%RESPONSE.mime:321

%PAGE.render_error_page:2899

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>APEX-DEBUG-ID=3821666,level=ERROR</td>

<td>%RESPONSE.set_apex_debug_header:120

%RESPONSE.write_headers:478

%RESPONSE.add_header:108

%RESPONSE.mime:321

%PAGE.render_error_page:2899

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>add_header p_key=>APEX-Debug-ID,p_name=>APEX-Debug-ID,p_value=>3821666,level=ERROR,p_overwrite=>true,p_is_sticky=>true</td>

<td>%RESPONSE.add_header:70

%RESPONSE.set_apex_debug_header:121

%RESPONSE.write_headers:478

%RESPONSE.add_header:108

%RESPONSE.mime:321

%PAGE.render_error_page:2899

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>write_headers p_close_header_section=>false</td>

<td>%RESPONSE.write_headers:460

%RESPONSE.add_header:108

%RESPONSE.set_apex_debug_header:121

%RESPONSE.write_headers:478

%RESPONSE.add_header:108

%RESPONSE.mime:321

%PAGE.render_error_page:2899

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>APEX-DEBUG-ID=3821666,level=ERROR</td>

<td>%RESPONSE.set_apex_debug_header:120

%RESPONSE.write_headers:478

%RESPONSE.add_header:108

%RESPONSE.set_apex_debug_header:121

%RESPONSE.write_headers:478

%RESPONSE.add_header:108

%RESPONSE.mime:321

%PAGE.render_error_page:2899

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>add_header p_key=>APEX-Debug-ID,p_name=>APEX-Debug-ID,p_value=>3821666,level=ERROR,p_overwrite=>true,p_is_sticky=>true</td>

<td>%RESPONSE.add_header:70

%RESPONSE.set_apex_debug_header:121

%RESPONSE.write_headers:478

%RESPONSE.add_header:108

%RESPONSE.set_apex_debug_header:121

%RESPONSE.write_headers:478

%RESPONSE.add_header:108

%RESPONSE.mime:321

%PAGE.render_error_page:2899

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>write_headers p_close_header_section=>true</td>

<td>%RESPONSE.write_headers:460

%PAGE.render_error_page:2900

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>APEX-DEBUG-ID=3821666,level=ERROR</td>

<td>%RESPONSE.set_apex_debug_header:120

%RESPONSE.write_headers:478

%PAGE.render_error_page:2900

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>add_header p_key=>APEX-Debug-ID,p_name=>APEX-Debug-ID,p_value=>3821666,level=ERROR,p_overwrite=>true,p_is_sticky=>true</td>

<td>%RESPONSE.add_header:70

%RESPONSE.set_apex_debug_header:121

%RESPONSE.write_headers:478

%PAGE.render_error_page:2900

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>get_grid_template p_page_template_id=></td>

<td>%TEMPLATE.get_grid_template:312

%PAGE.render_error_page:2914

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>emit_page_header</td>

<td>%PAGE.emit_page_header:2440

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>Show page template header</td>

<td>%PAGE.emit_page_header:2441

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>is_desktop_ui p_application_id=>4500,p_page_id=>,p_security_group_id=>10</td>

<td>%PAGE.is_desktop_ui:295

%CSS.get_standard_files:405

%PAGE.emit_page_header:2448

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>get_ui_type p_application_id=>4500,p_page_id=>,p_security_group_id=>10</td>

<td>%PAGE.is_desktop_ui:303

%CSS.get_standard_files:405

%PAGE.emit_page_header:2448

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>…get is_default or first user interface</td>

<td>%PAGE.is_desktop_ui:303

%CSS.get_standard_files:405

%PAGE.emit_page_header:2448

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>… ui type name=DESKTOP</td>

<td>%PAGE.is_desktop_ui:303

%CSS.get_standard_files:405

%PAGE.emit_page_header:2448

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>%COMBINED_FILE.load:122

%COMBINED_FILE.__pkg_init:343

%CSS.add_link:206

%CSS.add_core_file:260

%CSS.get_standard_files:406

%PAGE.emit_page_header:2448

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>reset</td>

<td>%COMBINED_FILE.reset:337

%COMBINED_FILE.load:124

%COMBINED_FILE.__pkg_init:343

%CSS.add_link:206

%CSS.add_core_file:260

%CSS.get_standard_files:406

%PAGE.emit_page_header:2448

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>Ignore concatenated files of application because we are running in debug mode or from Builder</td>

<td>%COMBINED_FILE.load:175

%COMBINED_FILE.__pkg_init:343

%CSS.add_link:206

%CSS.add_core_file:260

%CSS.get_standard_files:406

%PAGE.emit_page_header:2448

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>Ignore concatenated files for APEX libraries because we are running in debug mode</td>

<td>%COMBINED_FILE.load:327

%COMBINED_FILE.__pkg_init:343

%CSS.add_link:206

%CSS.add_core_file:260

%CSS.get_standard_files:406

%PAGE.emit_page_header:2448

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>%COMBINED_FILE.get_file_url:59

%CSS.add_link:206

%CSS.add_core_file:260

%CSS.get_standard_files:406

%PAGE.emit_page_header:2448

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>get_file_url p_url=>/i/app_ui/css/Theme-Standard.css?v=19.1.0.00.15</td>

<td>%COMBINED_FILE.get_file_url:59

%CSS.add_link:206

%CSS.add_core_file:260

%CSS.get_standard_files:407

%PAGE.emit_page_header:2448

%PAGE.render_error_page:2983

%ERROR.paint_on_error_page:338

%ERROR.internal_add_error:1055

%ERROR.raise_internal_error:1431

%.start_page_request:1848

%.show:3667

APEX.apex:52

:2</td>

</tr>

<tr>

<td>get_file_url p_url=>/i/libraries/jquery/3.3.1/jquery-3.3.1.js?v=19.1.0.00.15</td>

<td>%COMBINED_FILE.get_file_url:59

%JAVASCRIPT.add_link:411

%JAVASCRIPT.add_3rd_party_library:980

%JAVASCRIPT.add_jquery:997

%JAVASCRIPT.standard_javascript:1091

%PAGE.emit_page_header:2449

%PAGE.render_error_page:2983

%ER

Источник

Содержание

An error occurred while processing your request, что делать?
Что такое An error occurred while processing your request
Как исправить ошибку An error occurred
Заключение
An error occurred while processing this request contact your administrator
Question
An error occurred while processing this request contact your administrator
Answered by:
Question
Answers
All replies
Решение: An error occurred while processing your request
Error.
An error occurred while processing your request.
Answers
All replies
ravinjaype

An error occurred while processing your request, что делать?

Ряд пользователей браузеров при переходе на какой-либо сайт (наиболее часто данная проблема встречается на сайте Steam) могут столкнуться с ошибкой и соответствующим сообщением «An error occurred while processing your request». Обновление страницы проблемного сайта обычно ничего не даёт, пользователь сталкивается с упомянутой проблемой вновь и вновь. В этом материале я расскажу, что это за сообщение, при каких условиях появляется данная проблема, и как исправить её на вашем ПК.

Что такое An error occurred while processing your request

В переводе с английского языка текст данной ошибки звучит как «Произошла ошибка во время обработки вашего запроса». Как уже упоминалось выше, наиболее часто на возникновение данной ошибки жалуются пользователи Steam, которые при переходе на данный сайт встречают описанную дисфункцию.

При этом данная ошибка может встречаться и на других ресурсах, и в абсолютном большинстве случаев имеет браузерную основу (пользователи различных онлайн-программ практически с ней не сталкиваются).

Причины данной ошибки следующие:

Сбой или перегрузка сервера, обрабатывающего ваш запрос;
Случайный сбой вашего ПК;
Кэш вашего браузера повреждён;
Ошибка SSL-сертификата вашего браузера;
Проблемы с HTTPS-протоколом у ряда сайтов;
Проблема с HTTPS-расширениями вашего браузера (например, с «HTTPS Everywhere»).

После определения причин дисфункции перейдём к описанию того, как избавиться от ошибки Sorry, an error occurred while processing your request.

Как исправить ошибку An error occurred

Итак, вы встретились с упомянутой проблемой и думаете, как её устранить. Рекомендую выполнить следующий ряд действий:

Попробуйте просто перезагрузить свой компьютер. Это помогает чаще, чем может показаться;
Немного подождите. Во многих случаях (особенно это касается пользователей Steam) сервера бывают перегружены или «упали», потому необходимо некоторое время для решения проблемы администрацией сервера. В подобных случаях нужно немного подождать (часто хватает и суток) чтобы проблема была решена;
Очистите кэш и куки вашего браузера. К примеру, в браузере Мозилла это делается переходом в «Настройки», затем в закладку «Приватность», и кликом на «Удалить вашу недавнюю историю». В открывшимся окне «Удаление истории» в «Подробности» поставьте галочку на «Кэш» и удалите последний;

Попробуйте сменить ваш браузер, использовав альтернативный веб-обозреватель при осуществлении перехода на проблемный сайт;

Если вы не можете запустить игру Steam с браузера (через веб-лаунчер), попробуйте использовать находящийся на вашем ПК exe-файл данной игры для её запуска (сам файл часто находится в папке Steam);

Удалите SSL-сертификат проблемного сайт. Удаление SSL-сертификата проблемного сайта, по отзывам пользователей, может помочь в решении ошибки An error occurred while processing your request. Как удалить проблемный сертификат описано;

Попробуйте использовать не зашифрованную версию сайта (при возможности). Обычно адрес зашифрованного сайта начинается с http s . Попробуйте использовать тот же адрес, но с началом на http (без окончания s), это может помочь в вопросе как пофиксить ошибку An error occurred while processing your request;

Удалите (отключите) расширения браузера, принуждающие вебсайты работать только c HTTPS (например, уже упомянутое расширение «HTTPS Everywhere»);

Если данная ошибка возникла при работе с социальной сетью (например, с Фейсбук), попробуйте выйти из неё, а потом вновь выполнить вход;

Уведомьте администрацию проблемного ресурса о возникшей проблеме (обычно, хватает соответствующего письма в службу технической поддержки).

Заключение

В данном материале мной была рассмотрена тема «An error occurred while processing your request, что делать», обозначены причины данной проблемы и намечены пути её решения. В большинстве случаев данная ошибка возникает из-за перегрузки или «падения» серверов, и от пользователя требуется немного подождать, дабы всё пришло в норму. В иных же случаях попробуйте выполнить очистку кэша вашего браузера, так как именно этот совет оказался весьма эффективным в решении данной проблемы на пользовательских ПК.

Источник

An error occurred while processing this request contact your administrator

Question

I have configured CBA / IFD on my client’s Dynamics CRM 2011 Server and now getting the following error when I try to browse the internal / external url:

Reference
number: 005e0041-36c7-4b2c-9b19-c07a3d071dd9

Certificate is a mulit-domain ucc and added correctly in certificate stores.

The Event Viewer in ADFS is giving the following error:

Microsoft.IdentityServer.Web.RequestFailedException: MSIS7012: An error occurred while processing the request. Contact your administrator for details. —>

Encountered error during federation passive request.

Microsoft.IdentityServer.Web.RequestFailedException: MSIS7012: An error occurred while processing the request. Contact your administrator for details. —> System.ServiceModel.FaultException: MSIS3127: The specified request failed.

at Microsoft.IdentityServer.Protocols.WSTrust.WSTrustClientManager.Issue(Message request, WCFResponseData responseData)

at Microsoft.IdentityServer.Protocols.WSTrust.WSTrustClient.Issue(RequestSecurityToken rst, WCFResponseData responseData)

at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.SubmitRequest(MSISRequestSecurityToken request)

— End of inner exception stack trace —

at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.SubmitRequest(MSISRequestSecurityToken request)

at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.RequestBearerToken(MSISSignInRequestMessage signInRequest, SecurityTokenElement onBehalfOf, SecurityToken primaryAuthToken, String desiredTokenType, Uri& replyTo)

at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.BuildSignInResponseCoreWithSerializedToken(String signOnToken, WSFederationMessage incomingMessage)

at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.BuildSignInResponseCoreWithSecurityToken(SecurityToken securityToken, WSFederationMessage incomingMessage)

at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.BuildSignInResponseForProtocolRequest(FederationPassiveContext federationPassiveContext, SecurityToken securityToken)

at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.BuildSignInResponse(SecurityToken securityToken)

System.ServiceModel.FaultException: MSIS3127: The specified request failed.

at Microsoft.IdentityServer.Protocols.WSTrust.WSTrustClientManager.Issue(Message request, WCFResponseData responseData)

at Microsoft.IdentityServer.Protocols.WSTrust.WSTrustClient.Issue(RequestSecurityToken rst, WCFResponseData responseData)

at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.SubmitRequest(MSISRequestSecurityToken request)

Microsoft Certified Business Management Solutions Specialist

Источник

An error occurred while processing this request contact your administrator

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I have already done several AD FS 3.0 setup in SharePoint 2013 environment to allow trusted Active Directory user to be able to access my SharePoint site. However the most recent setup I’m in charge has not been done due to MSIS7012 error. It would be great if someone could tell me some potential reasons causing the error below

Encountered error during federation passive request.

Exception details:
Microsoft.IdentityServer.Protocols.Saml.SamlException: MSIS7012: An error occurred while processing the request. Contact your administrator for details.
at Microsoft.IdentityServer.Web.Protocols.Saml.SamlProtocolHandler.GetSecurityTokenFromSignInResponse(ProtocolContext context)
at Microsoft.IdentityServer.Web.PassiveProtocolListener.ProcessProtocolRequest(ProtocolContext protocolContext, PassiveProtocolHandler protocolHandler)
at Microsoft.IdentityServer.Web.PassiveProtocolListener.OnGetContext(WrappedHttpListenerContext context)

Thuan Soldier
A 23-year-old man loving Microsoft technologies and making crazy ideas on business journey.
SharePoint Vietnam | Blog | Twitter

Answers

You can solve the error executing from powershell logged in the primary ADFS server the below command:

Set-AdfsProperties -EnableIdpInitiatedSignonPage $true

La respuesta se proporciona «TAL CUAL», sin garantías y no confiere derechos. Es recomendable probar siempre cualquier sugerencia en un entorno de prueba antes de implementar! This posting is provided «AS IS» with no warranties and confers no rights! Always test ANY suggestion in a test environment before implementing!

Proposed as answer by Steve1234599999 Tuesday, September 25, 2018 2:22 PM
Marked as answer by Hamid Sadeghpour Saleh MVP Thursday, September 5, 2019 7:56 AM

I had this once with a SP that was using another Signing Certificate than the one provided to us in the Federation Metadata XML we received from them. turned out that every time they ran some wizard to adjust their Federation settings a new Signing Certificate was created and used.

Thuan Soldier
A 23-year-old man loving Microsoft technologies and making crazy ideas on business journey.
SharePoint Vietnam | Blog | Twitter

I encountered the same error as yours. It drove me crazy to figure out the reason why. I searched a lot on the Internet and found that the possible reason could be Certificate Chain Validation and Revocation Status Checking in ADFS.

Somehow, due to security policies, your ADFS server is unable to check the Revocation status of the Token Singing Certificate. I realized that if I use the certificate auto generated by AD FS, this error will not happened. However if I disable the AutoCertificateRollover property, and use certificate same as the one for Service Communications, the error will occur. To resolve it, I have to set the SigningCertificateRevocationCheck property as «None» for the relevant Claims Provider Trust or Relying Party Trust.

Источник

Решение: An error occurred while processing your request

Ошибка An error occurred while processing your request. Reference . возникает в программе Steam, во время запуска или же во время выполнения какого-то действия. Ошибка означает, что во время вашего запроса произошла ошибка.

Необходимые действия, которые надо выполнить:

Убедитесь, что вы используете последнюю версию программы Steam. Перейдите в раздел меню Steam и выберите пункт «Проверить наличие обновлений клиента». Если программа устарела — клиент обновится и ошибка error while processing request больше появляться не будет.
Вторая по популярности проблема — это перезагруженность серверов. Если у вас актуальная версия и ошибка while processing your request то появляется то исчезает — сервер перезагружен. Попробуйте зайти в программу в другое время.
Попробуйте обновить MS Visual C++, MS .NET Framework, VCredist. Эти компоненты необходимы для запуска игр и если у вас установлены старые версии, то вполне вероятно ожидать появление ошибок. Подробнее об обновлении читайте ниже.
Запустите приложение от имени администратора.

Если вы нашли решение проблемы An error occurred while processing your request. Reference . , которое не указано в статье, просим вас помочь сообществу и поделиться решением в комментариях

Источник

Error.

An error occurred while processing your request.

Answers

Open IIS Manager and click on Application Pools. Make sure the Application Pool your MVC app is running under is set to .NET CLR version is 4 and the pipeline mode is Integrated.

Please set the custom errors to false and debug=true in your web.config file to see if it will some specific error message.

No, when client side script has error, the page will still loads. This issue seems like there is some error on the server side.

forgot to tell you that : I am getting this error on landing page..

Open IIS Manager and click on Application Pools. Make sure the Application Pool your MVC app is running under is set to .NET CLR version is 4 and the pipeline mode is Integrated.

I verified both setting are same as mentioned.

ravinjaype

I verified both setting are same as mentioned.

Please provide the entire error message. Perhaps the app is unable to connect to SQL server?

no error detail is coming on page. is there any way to make error show on page?

I verified both setting are same as mentioned.

Go look at the IIS logs.

Maybe you should post to IIS forum.

When you convert the folder to application, there is a button ‘Connect As..’ in the dialog, please check which user you are using and make sure this user has the permission to operate the folders. You can use the Test Settings to check if the current user has the permissions to operate these folders.

Источник

In the upcoming Oracle Application Express (APEX) 5.2 release, support has been added for so-called «Social Sign-In» authentication. This means that your users can login to an APEX application using an external authentication provider. In APEX 5.2, there is built-in support for Google and Facebook accounts. There is also support for «Generic OAuth Providers» and «OpenID Connect Providers». This blog post describes how you can use the «OpenID Connect Provider» to set up authentication with a Microsoft account, such as an Outlook.com account.

Here is how to do it:

A. Register the APEX application with Microsoft

1. Go to Microsoft Application Registration Portal. Note that you need a Microsoft account, such as an Outlook.com email account, to login and use this portal:

https://apps.dev.microsoft.com/

2. Add an app (enter a descriptive name, your users will see this name during the consent prompt in step 20 below). An Application ID gets generated. Click «Generate New Password» to generate a password.

3. Click «Add platform» and choose «Web». Enter the APEX callback URL as the «Redirect URL», for the APEX 5.2 Early Adopter this is:

https://apexea.oracle.com/pls/apex/apex_authentication.callback

4. Add the URL of the APEX app as the «Home Page URL»:

https://apexea.oracle.com/pls/apex/f?p=your_app_alias:10

5. Click «Save»

B. Setup APEX Credentials

6. In APEX, go to Shared Components and click on «Credentials»

7. Create a new Credential and give it a name (for example «Azure OpenID Credentials»). Select «OAuth2 Client Credentials Flow» as the credential type.

8. Add the Application ID from step 2 above as the «Client ID», and the password from step 2 above as the «Client Secret».

9. Save the credentials.

C. Setup APEX Authentication Scheme

10. Go to Shared Components and click on «Authentication Schemes»

11. Create a new authentication scheme and give it a name (for example «Azure AD OpenID»). Select «Social Sign-In» as the scheme type.

12. As credential store, select the credentials created in step 9 («Azure OpenID Credentials»).

13. As authentication provider, select «OpenID Connect Provider».

14. As discovery URL, use the following:

https://login.microsoftonline.com/common/v2.0/.well-known/openid-configuration

15. As scope, type «email» (without the quotes)

16. As username attribute, type «email» (without the quotes)

17. Save the authentication scheme.

D. Test the Login

18. Go to the home page of your application:

https://apexea.oracle.com/pls/apex/f?p=your_app_alias:10

19. You should be redirected to a Microsoft login page. Log in with a Microsoft account (such as yourname@outlook.com).

20. You should be prompted to allow the APEX application to log you in and retrieve your email address to identify you. Accept this.

21. You should see the home page of your APEX application, and the value of APP_USER should now be equal to the email address you logged in with at Microsoft.

Switching between authentication schemes in the same APEX session

APEX version 5.2 also includes a new attributte for authentication schemes called «Switch in Session» that can be either Enabled or Disabled. If enabled, the current session’s authentication scheme can be changed by passing APEX_AUTHENTICATION=scheme name in a URL’s request parameter.

You can use this to present users with multiple login options. For example, you can have the standard APEX Authentication (or your own table-based authentication) set as the current authentication scheme, and then add another button to the login page which switches the authentication scheme to the Microsoft scheme (or Facebook, or Google, etc).

The screenshot above shows an example of a standard APEX login page where I have added an extra button (called «LOGIN_MICROSOFT»), set the icon CSS class to «fa-windows» to get the Windows logo on the button, and set the action attribute of the button to redirect to page 10 (the home page of the application) and also setting the request of the link to «APEX_AUTHENTICATION=name_of_microsoft_auth_scheme». Clicking this button should redirect to a Microsoft page for login, and then redirect the user back to the requested page.

Источник

Содержание

Что такое An error occurred while processing your request
Как исправить ошибку An error occurred
Заключение

Что такое An error occurred while processing your request

Причины данной ошибки следующие:

Сбой или перегрузка сервера, обрабатывающего ваш запрос;
Случайный сбой вашего ПК;
Кэш вашего браузера повреждён;
Ошибка SSL-сертификата вашего браузера;
Проблемы с HTTPS-протоколом у ряда сайтов;
Проблема с HTTPS-расширениями вашего браузера (например, с «HTTPS Everywhere»).

Как исправить ошибку An error occurred

Попробуйте просто перезагрузить свой компьютер. Это помогает чаще, чем может показаться;
Немного подождите. Во многих случаях (особенно это касается пользователей Steam) сервера бывают перегружены или «упали», потому необходимо некоторое время для решения проблемы администрацией сервера. В подобных случаях нужно немного подождать (часто хватает и суток) чтобы проблема была решена;
Очистите кэш и куки вашего браузера. К примеру, в браузере Мозилла это делается переходом в «Настройки», затем в закладку «Приватность», и кликом на «Удалить вашу недавнюю историю». В открывшимся окне «Удаление истории» в «Подробности» поставьте галочку на «Кэш» и удалите последний;
Попробуйте сменить ваш браузер, использовав альтернативный веб-обозреватель при осуществлении перехода на проблемный сайт;
Если вы не можете запустить игру Steam с браузера (через веб-лаунчер), попробуйте использовать находящийся на вашем ПК exe-файл данной игры для её запуска (сам файл часто находится в папке Steam);
Удалите SSL-сертификат проблемного сайт. Удаление SSL-сертификата проблемного сайта, по отзывам пользователей, может помочь в решении ошибки An error occurred while processing your request. Как удалить проблемный сертификат описано;
Попробуйте использовать не зашифрованную версию сайта (при возможности). Обычно адрес зашифрованного сайта начинается с https. Попробуйте использовать тот же адрес, но с началом на http (без окончания s), это может помочь в вопросе как пофиксить ошибку An error occurred while processing your request;
Удалите (отключите) расширения браузера, принуждающие вебсайты работать только c HTTPS (например, уже упомянутое расширение «HTTPS Everywhere»);
Если данная ошибка возникла при работе с социальной сетью (например, с Фейсбук), попробуйте выйти из неё, а потом вновь выполнить вход;
Уведомьте администрацию проблемного ресурса о возникшей проблеме (обычно, хватает соответствующего письма в службу технической поддержки).

Заключение

Опубликовано 02.02.2017 Обновлено 19.02.2021

Источник

how to correct this error.

I am not using ‘WD_RFC_METADATA_DEST’ JCO connections to connect to R/3. Even the, it is displaying this JCO. kindly come up with your expert suggestions.

500 Internal Server Error

Web Dynpro Container/SAP J2EE Engine/6.40

Failed to process request. Please contact your system administrator.

[Hide]

Error Summary

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn’t help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

Root Cause

The initial exception that caused the request to fail, was:

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name ‘WD_RFC_METADATA_DEST’. No such JCO destination is defined in the SLD

at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)

at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:248)

at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222)

at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148)

… 45 more

See full exception chain for details.

Correction Hints

Retrieving a JCO destination with name ‘WD_RFC_METADATA_DEST’ from the System Landscape Directory (SLD) failed, as the destination could not be found in the SLD. The most probable reason for that is that the destination has not been maintained yet.

Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.

Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).

Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can’t be guaranteed to address the original problem in all cases.

System Environment

Client

Web Dynpro Client Type HTML Client

User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727)

Version

DOM version

Client Type msie6

Client Type Profile ie6

ActiveX enabled

Cookies enabled

Frames enabled

Java Applets enabled

JavaScript enabled

Tables enabled

VB Script enabled

Server

Web Dynpro Runtime Vendor: SAP, Build ID: 6.4014.00.0000.20050905165427.0000 (release=630_VAL_REL, buildtime=2005-09-20:20:24:49[UTC], changelist=366934, host=PWDFM026)

J2EE Engine 6.40 patchlevel 98256.313

Java VM Java HotSpot(TM) Server VM, version:1.4.2_08-b03, vendor: Sun Microsystems Inc.

Operating system Windows 2003, version: 5.2, architecture: x86

Other

Session Locale en_US

Time of Failure Fri Dec 30 17:29:24 IST 2005 (Java Time: 1135943964046)

Web Dynpro Code Generation Infos

local/OpenOrderStatus

SapDictionaryGenerationCore 6.4014.00.0000.20050818151336.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:08:16[UTC], changelist=363802, host=PWDFM026.wdf.sap.corp)

SapDictionaryGenerationTemplates (unknown)

SapGenerationFrameworkCore 6.4014.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:01:32[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)

SapIdeWebDynproCheckLayer 6.4014.00.0000.20050818152737.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:15:40[UTC], changelist=363825, host=PWDFM026.wdf.sap.corp)

SapMetamodelCommon 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:02:26[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)

SapMetamodelCore 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:02:18[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)

SapMetamodelDictionary 6.4014.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:05:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)

SapMetamodelWebDynpro 6.4014.00.0000.20050818152356.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:11:31[UTC], changelist=363818, host=PWDFM026.wdf.sap.corp)

SapWebDynproGenerationCTemplates 6.4014.00.0000.20050905165427.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:26:46[UTC], changelist=366934, host=PWDFM026)

SapWebDynproGenerationCore 6.4014.00.0000.20050818152737.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:16:08[UTC], changelist=363825, host=PWDFM026.wdf.sap.corp)

SapWebDynproGenerationTemplates 6.4014.00.0000.20050905165427.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:26:46[UTC], changelist=366934, host=PWDFM026)

sap.com/tc_wddispwda

No information available

sap.com/tc_wdcorecomp

No information available

Detailed Error Information

Detailed Exception Chain

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)

at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)

at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)

at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)

at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)

at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)

at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)

at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)

at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)

at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)

at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:314)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:669)

at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)

at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:347)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)

Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:176)

at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:83)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)

… 42 more

Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name ‘WD_RFC_METADATA_DEST’. No such JCO destination is defined in the SLD

at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)

at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:248)

at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222)

at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148)

… 45 more

Источник

An error occurred while processing your request, что делать?

Что такое An error occurred while processing your request

Как исправить ошибку An error occurred

Заключение

An error occurred while processing this request contact your administrator

Question

An error occurred while processing this request contact your administrator

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" />

Answered by:

Question

Answers

Решение: An error occurred while processing your request

Error.

An error occurred while processing your request.

Answers

ravinjaype

A. Register the APEX application with Microsoft

B. Setup APEX Credentials

C. Setup APEX Authentication Scheme

D. Test the Login

Switching between authentication schemes in the same APEX session

Что такое An error occurred while processing your request

Как исправить ошибку An error occurred

Заключение