Success message checksum content error contact your application administrator перевести

Success message checksum content error contact your application administrator

After I successfully installed Application Express 4.2.1.00.08 (latest version in this moment), I decided to test Apex Listener. So I installed (latest version in this moment) Apex Listener 2.0.0 354.17.05, which seems to be stable enough.

First tried standalone version but very soon found out that this is not a good way to run this product even in demo environment.

So I decided to install Tomcat 7.0 as free solution and implement Apex Listener as classic application. Regardless this combination is officially not supported by Oracle, after some small configuration problems (mainly with SQL Developer as configuration platform), my Apex was running fast as hell . and I was very glad to know that this combination really rocks. And the best of all free!

This looked very, very promising. I was courios what other problems I might run into . but for some time there were none.

The problem

But while I was developing one app, I run in the problem which I firstly thought it is pure Apex problem. Notification message on protected page was making fatal Apex error. This is the error content from WEB developed session:
Very soon I discovered that this error was triggering only when in it’s content was Croatian (or any other) national characters (like €, Ł etc). Here are the step to reproduce the problem.

1. Create a authentication page with «Page Access Protection» defined as «Arguments must have checksum»
2. Create a page process (On Submit After Computation and Validation).
3. In that process use Apex application variable ( G_APP_MESSAGE , in mine case) as a holder for success message. Code is exactly like
4. After submitting page, everything went fine . and success message is shown as expected.

If You change step 3) so G_APP_MESSAGE is defined as :
Just to accent that I changed uspjesno->uspješno (s->š), and submit a page again, I get an error described previously.

I tried change G_APP_MESSAGE in a way:
I get success message as:
but without error.
🙂
When I return back mine š sign to s (now message again has only USA characters), remove «utl_url.escape», page is submitted normally and success message is ok (but again without national signs).

The solution

The End

Even this is not a rocket science, it may shorten finding the solution to someone else.

Источник

Notification message checksum content error — Contact your application administrator.

I am in apex.oracle.com . Trying to create a custom authentication .

When I login with correct password, it works fine. However If I enter a wrong password, instead of going to the login page and display the failure message, it shows some checksum error.

I checked various postings on web, and tried different setups. No success

Can anyone please help.

This is not locally installed, This is on apex.oracle.com trial workspace version 5.0

Here is the detail

• is_internal_error: true
• apex_error_code: APEX.NOTIFICATION_MSG.CHECKSUM_CONTENT_ERROR
• component.type: APEX_APPLICATION_PAGES
• component.id: 70731000000101
• error_backtrace: —— PL/SQL Call Stack —— object line object handle number name 0x49785b860 641 package body APEX_050000.WWV_FLOW_ERROR 0x49785b860 709 package body APEX_050000.WWV_FLOW_ERROR 0x49785b860 1013 package body APEX_050000.WWV_FLOW_ERROR 0x49aed7ea0 1082 package body APEX_050000.WWV_FLOW_SECURITY 0x49aed7ea0 1099 package body APEX_050000.WWV_FLOW_SECURITY 0x497ab6138 4273 package body APEX_050000.WWV_FLOW 0x4977e7308 173 procedure APEX_050000.F 0x325c2e5f8 2 anonymous block

The custom authentication has only two functions

create or replace FUNCTION obfuscate(text_in IN VARCHAR2) RETURN RAW IS

—dbms_obfuscation_toolkit.md5(input => utl_raw.cast_to_raw(text_in), checksum => l_returnvalue);

l_returnvalue := dbms_obfuscation_toolkit.md5(input => utl_raw.cast_to_raw(text_in));

create or replace FUNCTION authenticate(p_username IN VARCHAR2

,p_password IN VARCHAR2) RETURN BOOLEAN IS

l_username VARCHAR2(100) := p_username;

l_password VARCHAR2(100) := p_password;

l_obfuscated_password := obfuscate(text_in => l_password);

FROM socmis_users a

AND upper(a.user_name) = upper(l_username)

AND a.password = l_obfuscated_password;

OR too_many_rows THEN

WHEN OTHERS THEN

IF l_value = 1 THEN

Following is the URL I get when the error comes. The error comes only when I enter wrong password

I noticed that This is happening with one particular application only , and the error is coming even with Oracle_application_express Accounts standard authentication . Not just custom

Only happen, when a wrong password is entered.

Источник

Errorprint success message checksum content error:

I have apex data enrty form and I am get this error message after SUBMIT but data get insterted in to the table.

Could anyone please tell what cause this error.

Contact your application administrator.
Error print success message checksum content error: :
917218E366D837B40E77F857E5423E6A
OK

Did this begin happening after you made a change? What is your version? What happens after the DML process, what kind of branch? What is in the process success message (exactly)? Can you reproduce it on apex.oracle.com?

Scott,
this is just simple form build based on one table with many item. not much validation.

error does not occurs frequently. i am having problem to debug this..

it has one branch. After hit thr submit button it throws the error but the data was inserted in the table.

if i don’t get any error i get the custome sucess message which we put in.

here is the url..

any help is appericated
thanks
james

There appears to be something in your network environment that causes requests from the same browser to appear to the application as coming from different IP addresses. Maybe there is some kind of load-balancing component. When this happens, Application Express assumes you are a different client trying to use a session already in use by another, so it gives you a new session ID. This causes the checksum verification to fail on the process success message because the checksum uses the original session ID as a salt.

We’ll try to provide a fix for this in the 3.0.1 patch that we’re putting together now.

Thanks for reporting it and giving the working example.

Thanks for your reply . i didn’t see this for a long time. Are you in the developing team of APEX.

When will APEX 3.0.1 will release? Is there any quick fix for this??

we need to put the application in prodcution soon.

Here is our hardware config.

we are using Netscalar hardware swicth., Application server,database server..

Connection flow is .

browser-> Netscalar swicth—> Application server (DAD)—> database server

please give some info on this.

Are you in the developing team of APEX.

When will APEX 3.0.1 will release?

We hope by the end of June but this is not an official commitment.

Is there any quick fix for this??

The only thing I can think of is to create a new DAD and always use that DAD for your application, i.e., public users of the application would use URLs containing the new DAD. In this DAD definition, the connecting user would be a new user that you create, say, APEX_PUBLIC_USER2. Create this database user and grant it «create session» privilege and nothing else.

we need to put the application in prodcution soon.

Источник

Errornotification message checksum content error

The problem is — if a wrong user name or password is supplied, apex throws a strange error —

Contact your application administrator.
Error notification message checksum content error: C53F0B90C7CA15BF701E5AC623A579BE
OK

But URL has notification error message — https://host/apex/f?p=800:101:914565140300946:&notification_msg=Invalid%20Login%20Credentials/858CAE75D64C062356B42548E99769A2/

When I login without SSL everything work OK.

My architecture is:
CentOS (5.6) -> Oracle 11g SEO -> OC4J -> APEX Listener -> Apache Revers Proxy (with SSL)

Can you please help me in fixing this error?

Best Answer

But I found one thing in your ssl.conf I’d take a closer look on: As far as I know, Rewrite will encode all non-ANSI characters as %xx hex codes in output if you don’t disable it: So in case you already get them encoded, this will cause the double encoding you see.
You should check if all requests come in that way. Otherwise you should leave the inital rule unchanged and add a Rule (before that one) which just matches success messages and leaves all other requests untouched.

If that’s not the solution, I have one other guess: mod_headers is (of course) loaded before, so the headers are modified by that handler. Though I’d usually not expect some effect like what you see in this module, possibly the url is (re)encoded here as well. You could try to check that by either commenting out that section or the line where mod_headers is loaded.

Answers

which locales do proxy and OC4J use? And do you use APEX in a translated version or in English? Any special characters have to be treated correctly by each component on the way. Since your proxy needs to rebuild the request in the SSL case, it could happen that the request to OC4J gets some unsupported encoding. Do you see similar errors in other situations, e.g. other notifications in APEX?
And just to make the picture complete, which APEX and APEX Listener versions do you use?

I use Apex 4.0.2.00.07 English ver.
APEX Listener ver. 1.1.1.104.21.28

Incorrect login return Error notification message checksum content error
I notice, after correct login no Notification Messages (without error) only in URL I can read messages.

URL Messages are specific
. &success_msg=Region%2520Updated.%2520Report%2520attributes%2520
but I think it can be
. &success_msg=Region%20Updated.%20Report%20attributes%20
This is couse of checksum error in login error.

It look like reprocess URL %20 changed to %2520.

I don’t know How can I check Locale in Apache and OC4J, can you help ?

Obviously there happens some double URL encoding: *%25* is the code for a *%*

Do you have any additional URL encoding rule on the proxy?

First, you could display the current locale setting by executing and review additional settings with Especially for the OC4J, you can also check if some special JVM-arguments have been set by executing There is a bunch of other locations to configure NLS parameters.

A nice guide on this is included in the [url http://download.oracle.com/docs/cd/B32110_01/core.1013/b31263/iasconfig.htm#BHCEECHI]OAS Globalization Guide, which covers both the OHS (pretty close to Apache HTTPD) and OC4J parts of that scenario.

[]# locale
every row exclude LC_ALL contain the same value = «pl_PL.UTF-8»
LC_ALL have not value:
LC_ALL=

[]# env | grep -E «LC|NLS»
nothing

[]# echo $OC4J_JVM_ARGS
nothing

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

StartServers 8
MinSpareServers 5
MaxSpareServers 20
ServerLimit 256
MaxClients 256
MaxRequestsPerChild 4000

StartServers 2
MaxClients 150
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
MaxRequestsPerChild 0

LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_alias_module modules/mod_authn_alias.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule include_module modules/mod_include.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule expires_module modules/mod_expires.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule headers_module modules/mod_headers.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule info_module modules/mod_info.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule cache_module modules/mod_cache.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule version_module modules/mod_version.so

#
# Load config files from the config directory «/etc/httpd/conf.d».
#
Include conf.d/*.conf

User apache
Group apache

Options FollowSymLinks
AllowOverride None

#
# Possible values for the Options directive are «None», «All»,
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that «MultiViews» must be named explicitly — «Options All»
# doesn’t give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be «All», «None», or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride None

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all

#
# UserDir is disabled by default since it can confirm the presence
# of a username on the system (depending on home directory
# permissions).
#
UserDir disable

#
# To enable requests to /

user/ to serve the user’s public_html
# directory, remove the «UserDir disable» line above, and uncomment
# the following line instead:
#
#UserDir public_html

DirectoryIndex index.html index.html.var

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#

Order allow,deny
Deny from all

#
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
#
TypesConfig /etc/mime.types

# MIMEMagicFile /usr/share/magic.mime
MIMEMagicFile conf/magic

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat «%h %l %u %t »%r» %>s %b »%i» »%i»» combined
LogFormat «%h %l %u %t »%r» %>s %b» common
LogFormat «%i -> %U» referer
LogFormat «%i» agent

# «combinedio» includes actual counts of actual bytes received (%I) and sent (%O); this
# requires the mod_logio module to be loaded.
#LogFormat «%h %l %u %t »%r» %>s %b »%i» »%i» %I %O» combinedio

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a
# container, they will be logged here. Contrariwise, if you do
# define per- access logfiles, transactions will be
# logged therein and not in this file.
#
#CustomLog logs/access_log common

#
# If you would like to have separate agent and referer logfiles, uncomment
# the following directives.
#
#CustomLog logs/referer_log referer
#CustomLog logs/agent_log agent

#
# For a single logfile with access, agent, and referer information
# (Combined Logfile Format), use the following directive:
#
CustomLog logs/access_log combined

#
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (internal error documents, FTP directory
# listings, mod_status and mod_info output etc., but not CGI generated
# documents or custom error documents).
# Set to «EMail» to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
#
ServerSignature On

Alias /icons/ «/var/www/icons/»

Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all

#
# WebDAV module configuration section.
#

# Location of the WebDAV lock database.
DAVLockDB /var/lib/dav/lockdb

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing «/» apply to ScriptAlias directives as to
# Alias.
#
ScriptAlias /cgi-bin/ «/var/www/cgi-bin/»

#
# «/var/www/cgi-bin» should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#

AllowOverride None
Options None
Order allow,deny
Allow from all

#
# Redirect allows you to tell clients about documents which used to exist in
# your server’s namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Example:
# Redirect permanent /foo http://www.example.com/bar

#
# Directives controlling the display of server-generated directory listings.
#

#
# IndexOptions: Controls the appearance of server-generated directory
# listings.
#
IndexOptions FancyIndexing VersionSort NameWidth=* HTMLTable

#
# AddIcon* directives tell the server which icon to show for different
# files or filename extensions. These are only displayed for
# FancyIndexed directories.
#
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip

AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*

AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core

AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^

#
# DefaultIcon is which icon to show for files which do not have an icon
# explicitly set.
#
DefaultIcon /icons/unknown.gif

#
# AddDescription allows you to place a short description after a file in
# server-generated indexes. These are only displayed for FancyIndexed
# directories.
# Format: AddDescription «description» filename
#
#AddDescription «GZIP compressed document» .gz
#AddDescription «tar archive» .tar
#AddDescription «GZIP compressed tar archive» .tgz

#
# ReadmeName is the name of the README file the server will look for by
# default, and append to directory listings.
#
# HeaderName is the name of a file which should be prepended to
# directory indexes.
ReadmeName README.html
HeaderName HEADER.html

#
# IndexIgnore is a set of filenames which directory indexing should ignore
# and not include in the listing. Shell-style wildcarding is permitted.
#
IndexIgnore . * *

*# HEADER* README* RCS CVS *,v *,t

AddLanguage ca .ca
AddLanguage cs .cz .cs
AddLanguage da .dk
AddLanguage de .de
AddLanguage el .el
AddLanguage en .en
AddLanguage eo .eo
AddLanguage es .es
AddLanguage et .et
AddLanguage fr .fr
AddLanguage he .he
AddLanguage hr .hr
AddLanguage it .it
AddLanguage ja .ja
AddLanguage ko .ko
AddLanguage ltz .ltz
AddLanguage nl .nl
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pl .po
AddLanguage pt .pt
AddLanguage pt-BR .pt-br
AddLanguage ru .ru
AddLanguage sv .sv
AddLanguage zh-CN .zh-cn
AddLanguage zh-TW .zh-tw

#
# LanguagePriority allows you to give precedence to some languages
# in case of a tie during content negotiation.
#
# Just list the languages in decreasing order of preference. We have
# more or less alphabetized them here. You probably want to change this.
#
LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW

#
# ForceLanguagePriority allows you to serve a result page rather than
# MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
# [in case no accepted languages matched the available variants]
#
ForceLanguagePriority Prefer Fallback

#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default. To use the
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8

#
# AddType allows you to add to or override the MIME configuration
# file mime.types for specific file types.
#
#AddType application/x-tar .tgz

#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz

# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz

#
# AddHandler allows you to map certain file extensions to «handlers»:
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add «ExecCGI» to the «Options» directive.)
#
#AddHandler cgi-script .cgi

#
# For files that include their own HTTP headers:
#
#AddHandler send-as-is asis

#
# For type maps (negotiated resources):
# (This is enabled by default to allow the Apache «It Worked» page
# to be distributed in multiple languages.)
#
AddHandler type-map var

#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add «Includes» to the «Options» directive.)
#
AddType text/html .shtml
AddOutputFilter INCLUDES .shtml

#
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
#

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 «The server made a boo boo.»
#ErrorDocument 404 /missing.html
#ErrorDocument 404 «/cgi-bin/missing_handler.pl»
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# Putting this all together, we can internationalize error responses.
#
# We use Alias to redirect any /error/HTTP_ .html.var response to
# our collection of by-error message multi-language collections. We use
# includes to substitute the appropriate text.
#
# You can modify the messages’ appearance without changing any of the
# default HTTP_ .html.var files by adding the line:
#
# Alias /error/include/ «/your/include/path/»
#
# which allows you to create your own set of files by starting with the
# /var/www/error/include/ files and
# copying them to /your/include/path/, even on a per-VirtualHost basis.
#

Alias /error/ «/var/www/error/»

AllowOverride None
Options IncludesNoExec
AddOutputFilter Includes html
AddHandler type-map var
Order allow,deny
Allow from all
LanguagePriority en es de fr
ForceLanguagePriority Prefer Fallback

#
# The following directives modify normal HTTP response behavior to
# handle known problems with browser implementations.
#
BrowserMatch «Mozilla/2» nokeepalive
BrowserMatch «MSIE 4.0b2;» nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch «RealPlayer 4.0» force-response-1.0
BrowserMatch «Java/1.0» force-response-1.0
BrowserMatch «JDK/1.0» force-response-1.0

#
# The following directive disables redirects on non-GET requests for
# a directory that does not include the trailing slash. This fixes a
# problem with Microsoft WebFolders which does not appropriately handle
# redirects for folders with DAV methods.
# Same deal with Apple’s DAV filesystem and Gnome VFS support for DAV.
#
BrowserMatch «Microsoft Data Access Internet Publishing Provider» redirect-carefully
BrowserMatch «MS FrontPage» redirect-carefully
BrowserMatch «^WebDrive» redirect-carefully
BrowserMatch «^WebDAVFS/1.[0123]» redirect-carefully
BrowserMatch «^gnome-vfs/1.0» redirect-carefully
BrowserMatch «^XML Spy» redirect-carefully
BrowserMatch «^Dreamweaver-WebDAV-SCM1» redirect-carefully

# P3P IE SSL Frame

Header set P3P «policyref=»/w3c/p3p.xml», CP=»NOI DSP COR NID CUR ADM DEV OUR BUS»»

RewriteEngine on
RewriteRule ^/$ https://%/apex/f?p=800$1 [R]

Alias /i/ /path/i/
# Directory dla plików APEX-owych

Options None
AllowOverride None
Order allow,deny
Allow from all

# Cachowanie plików

ExpiresActive On
ExpiresDefault «access plus 1 month»

### Typy plików, które powinny być kompresowane

AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/x-javascript
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE text/x-component

# flash Chart #HOST#
ProxyPreserveHost On

ProxyPass /apex http://localhost:8888/apex
ProxyPassReverse /apex http://localhost:8888/apex
———————————————-

My ssl.conf file

LoadModule ssl_module modules/mod_ssl.so

#
# When we also provide SSL we have to listen to the
# the HTTPS port in addition.
#
Listen 443

AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl .crl

# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds).
#SSLSessionCache dc:UNIX:/var/cache/mod_ssl/distcache
SSLSessionCache shmcb:/var/cache/mod_ssl/scache(512000)
SSLSessionCacheTimeout 300

# Semaphore:
# Configure the path to the mutual exclusion semaphore the
# SSL engine uses internally for inter-process synchronization.
SSLMutex default

SSLRandomSeed startup file:/dev/urandom 256
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random 512
#SSLRandomSeed connect file:/dev/random 512
#SSLRandomSeed connect file:/dev/urandom 512

SSLCryptoDevice builtin
#SSLCryptoDevice ubsec

##
## SSL Virtual Host Context
##

# Wirtual host

ServerAdmin [email protected]
ServerName mydomain.pl

RewriteEngine on
RewriteRule ^/$ https://%/apex/f?p=800$1 [R]

SSLEngine on
SSLCertificateFile /path/server_key.txt
SSLCertificateKeyFile /path/private_key.txt
SSLCACertificateFile /path/ca_key.txt

But I found one thing in your ssl.conf I’d take a closer look on: As far as I know, Rewrite will encode all non-ANSI characters as %xx hex codes in output if you don’t disable it: So in case you already get them encoded, this will cause the double encoding you see.
You should check if all requests come in that way. Otherwise you should leave the inital rule unchanged and add a Rule (before that one) which just matches success messages and leaves all other requests untouched.

If that’s not the solution, I have one other guess: mod_headers is (of course) loaded before, so the headers are modified by that handler. Though I’d usually not expect some effect like what you see in this module, possibly the url is (re)encoded here as well. You could try to check that by either commenting out that section or the line where mod_headers is loaded.

Udo You are Great : )

It helped: RewriteRule ^/$ https://%/apex/f?p=800$1 *[NE,R]*

please help me if you can. I see you had a great solution for this kind of problem.

So, I have the exact same error message (notification message checksum content error) when I try to log in to my app. BUT the circumstances not the exact same.

Oracle DB version: 10.2.0.5
APEX version: 4.0.2.00.07
APEX Listener version: 1.1.3.243.11.40

There is no SSL, there is no other complicated configuration.

My httpd.conf file:

ServerRoot «/usr/local/apache2»
Listen 80
LoadModule jk_module modules/mod_jk.so

ServerAdmin [email protected]
DocumentRoot «/usr/local/apache2/htdocs»

Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all

Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all

Order allow,deny
Deny from all
Satisfy All

ErrorLog «logs/error_log»
LogLevel warn

LogFormat «%h %l %u %t »%r» %>s %b »%i» »%i»» combined
LogFormat «%h %l %u %t »%r» %>s %b» common

# You need to enable mod_logio.c to use %I and %O
LogFormat «%h %l %u %t »%r» %>s %b »%i» »%i» %I %O» combinedio

CustomLog «logs/access_log» common

ScriptAlias /cgi-bin/ «/usr/local/apache2/cgi-bin/»

AllowOverride None
Options None
Order allow,deny
Allow from all

TypesConfig conf/mime.types
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz

SSLRandomSeed startup builtin
SSLRandomSeed connect builtin

# Setup APEX static file path
Alias /i/ /usr/apex/images/

Order allow,deny
Allow from all

# Add extra mime types
AddType text/xml xbl
AddType text/x-component htc

# Mod_jk Settings
JkWorkersFile /root/tomcat/apache-tomcat-6.0.33/conf/jk/workers.properties
JkLogFile /root/tomcat/apache-tomcat-6.0.33/logs/mod_jk.log
JkLogLevel info
JkLogStampFormat «[%a %b %d %H:%M:%S %Y] »
JkMount /apex/* default

There’s no other configuration!

The error occured after I enabled the session state protection. It is unbelievable, but if I disable the session state protection the error is the same.

What can be the solution? Is there a workaround for this?

Источник

CMOS Checksum Error Defaults Loaded при загрузке — как исправить

Иногда при загрузке компьютера или ноутбука вы можете столкнуться с ошибкой: CMOS checksum error — defaults loaded и другими вариантами этой же ошибки, в зависимости от производителя материнской платы: System CMOS checksum bad, CMOS checksum is invalid, CMOS checksum failed, Setup settings error CMOS checksum error or CMOS battery loss occurs — во всех случаях речь идёт об ошибке контрольной суммы данных микросхемы CMOS.

В этой инструкции подробно о том, что может вызвать ошибки CMOS checksum при загрузке ПК или ноутбука и как исправить проблему. Отмечу, что ошибка не зависит от установленной системы — это может быть Windows 11, Windows 10 или даже Linux.

Способы исправить ошибки CMOS Checksum

Причина рассматриваемой ошибки — несовпадение сохранённой контрольной суммы для данных, хранящихся в микросхеме CMOS (память BIOS для хранения параметров конфигурации компьютера) и фактической контрольной суммы этих данных на момент проверки при загрузке. Происходить это может по разным причинам — проблемы с питанием, сбои при записи параметров БИОС или обновлении, в редких случаях — какие-либо аппаратные неисправности.

Для того, чтобы исправить ошибку CMOS checksum error — defaults loaded и аналогичные, можно использовать следующие подходы:

1. При однократном появлении ошибки, например, после замены комплектующих, и нормальной загрузке операционной системы после этого, попробуйте выполнить простую перезагрузку ОС — возможно ошибка больше не проявит себя.
2. Если вход в БИОС/UEFI при ошибке возможен, сбросить параметры БИОС на настройки по умолчанию (Load Defaults, Restore Defaults или Load Optimized Defaults, как правило на вкладке Exit). Учитывайте, что при сбросе могут сброситься и важные параметры загрузки (режим UEFI и Legacy, Secure Boot и их необходимо будет вернуть в прежнее состояние для исправной загрузки системы). Иногда описанный метод срабатывает однократно, но затем ошибка появляется вновь.
3. Замена элемента питания CR2032 на материнской плате (замена «батарейки БИОС»). На настольном компьютере это — очень простая процедура, а вот на ноутбуке добраться до батарейки бывает сложно (впрочем, на ноутбуках рассматриваемая проблема менее распространена), при этом сама батарейка обычно не просто «вставляется», а подключается проводом, как на втором изображении ниже. После замены элемента питания не забудьте установить правильные настройки БИОС, включая дату и время.
4. Если вход в БИОС невозможен, попробуйте выполнить сброс параметров либо отключив батарейку из предыдущего шага на несколько минут (компьютер при этом должен быть обесточен) либо с помощью кнопки (обычно её требуется удерживать для сброса CMOS) или контактов на материнской плате: у разных производителей эти контакты могут располагаться в разных местах, но обычно подписаны как CLEAR CMOS, CLR_CMOS, CLRTC и аналогичным образом: это либо два контакта, которые нужно замкнуть, либо три — в этом случае джампер (перемычку) необходимо переставить с одного расположения в другое — проделываем это на выключенном компьютере, а уже после установки перемычки включаем питание.
5. Попробуйте обновить БИОС с официального сайта производителя материнской платы компьютера (именно для вашей модели МП), либо с официального сайта производителя ноутбука.
6. Если ошибка, наоборот, стала появляться после обновления БИОС, проверьте: существует ли возможность установки предыдущей версии или же дождитесь очередного обновления (возможно, в установленном содержались ошибки).
7. В случае, если батарейка БИОС заменена, а ошибки CMOS Checksum продолжают появляться, проверьте: существуют ли какие-то закономерности её появления, например: ошибки нет при использовании пункта «Перезагрузка» в меню Пуск Windows, но она появляется после использования пункта «Завершение работы» по прошествии некоторого времени (в этом случае можно попробовать отключить функцию Быстрый запуск).
8. В некоторых БИОС можно просто отключить сообщение об ошибке (если она не мешает работе). Как правило пункт называется» Halt on (другие варианты: POST Errors, Error Halt) со значением «All Errors» (означает остановку при любых ошибках POST). Если выставить «No errors», то при обнаружении ошибок остановка происходить не будет.

В завершение ещё одна возможная причина ошибки — какие-либо аппаратные проблемы: неисправность компонентов материнской платы, проблемы с электропитанием — замыкания, статические разряды, утечки тока.

Источник

Notification message checksum content error

After I successfully installed Application Express 4.2.1.00.08 (latest version in this moment), I decided to test Apex Listener. So I installed (latest version in this moment) Apex Listener 2.0.0 354.17.05, which seems to be stable enough.

First tried standalone version but very soon found out that this is not a good way to run this product even in demo environment.

So I decided to install Tomcat 7.0 as free solution and implement Apex Listener as classic application. Regardless this combination is officially not supported by Oracle, after some small configuration problems (mainly with SQL Developer as configuration platform), my Apex was running fast as hell . and I was very glad to know that this combination really rocks. And the best of all free!

This looked very, very promising. I was courios what other problems I might run into . but for some time there were none.

The problem

But while I was developing one app, I run in the problem which I firstly thought it is pure Apex problem. Notification message on protected page was making fatal Apex error. This is the error content from WEB developed session:
Very soon I discovered that this error was triggering only when in it’s content was Croatian (or any other) national characters (like €, Ł etc). Here are the step to reproduce the problem.

1. Create a authentication page with «Page Access Protection» defined as «Arguments must have checksum»
2. Create a page process (On Submit After Computation and Validation).
3. In that process use Apex application variable ( G_APP_MESSAGE , in mine case) as a holder for success message. Code is exactly like
4. After submitting page, everything went fine . and success message is shown as expected.

If You change step 3) so G_APP_MESSAGE is defined as :
Just to accent that I changed uspjesno->uspješno (s->š), and submit a page again, I get an error described previously.

I tried change G_APP_MESSAGE in a way:
I get success message as:
but without error.
🙂
When I return back mine š sign to s (now message again has only USA characters), remove «utl_url.escape», page is submitted normally and success message is ok (but again without national signs).

The solution

The End

Even this is not a rocket science, it may shorten finding the solution to someone else.

Источник

Notification message checksum content error — Contact your application administrator.

I am in apex.oracle.com . Trying to create a custom authentication .

When I login with correct password, it works fine. However If I enter a wrong password, instead of going to the login page and display the failure message, it shows some checksum error.

I checked various postings on web, and tried different setups. No success

Can anyone please help.

This is not locally installed, This is on apex.oracle.com trial workspace version 5.0

Here is the detail

• is_internal_error: true
• apex_error_code: APEX.NOTIFICATION_MSG.CHECKSUM_CONTENT_ERROR
• component.type: APEX_APPLICATION_PAGES
• component.id: 70731000000101
• error_backtrace: —— PL/SQL Call Stack —— object line object handle number name 0x49785b860 641 package body APEX_050000.WWV_FLOW_ERROR 0x49785b860 709 package body APEX_050000.WWV_FLOW_ERROR 0x49785b860 1013 package body APEX_050000.WWV_FLOW_ERROR 0x49aed7ea0 1082 package body APEX_050000.WWV_FLOW_SECURITY 0x49aed7ea0 1099 package body APEX_050000.WWV_FLOW_SECURITY 0x497ab6138 4273 package body APEX_050000.WWV_FLOW 0x4977e7308 173 procedure APEX_050000.F 0x325c2e5f8 2 anonymous block

The custom authentication has only two functions

create or replace FUNCTION obfuscate(text_in IN VARCHAR2) RETURN RAW IS

—dbms_obfuscation_toolkit.md5(input => utl_raw.cast_to_raw(text_in), checksum => l_returnvalue);

l_returnvalue := dbms_obfuscation_toolkit.md5(input => utl_raw.cast_to_raw(text_in));

create or replace FUNCTION authenticate(p_username IN VARCHAR2

,p_password IN VARCHAR2) RETURN BOOLEAN IS

l_username VARCHAR2(100) := p_username;

l_password VARCHAR2(100) := p_password;

l_obfuscated_password := obfuscate(text_in => l_password);

FROM socmis_users a

AND upper(a.user_name) = upper(l_username)

AND a.password = l_obfuscated_password;

OR too_many_rows THEN

WHEN OTHERS THEN

IF l_value = 1 THEN

Following is the URL I get when the error comes. The error comes only when I enter wrong password

I noticed that This is happening with one particular application only , and the error is coming even with Oracle_application_express Accounts standard authentication . Not just custom

Only happen, when a wrong password is entered.

Источник

Errornotification message checksum content error

The problem is — if a wrong user name or password is supplied, apex throws a strange error —

Contact your application administrator.
Error notification message checksum content error: C53F0B90C7CA15BF701E5AC623A579BE
OK

But URL has notification error message — https://host/apex/f?p=800:101:914565140300946:&notification_msg=Invalid%20Login%20Credentials/858CAE75D64C062356B42548E99769A2/

When I login without SSL everything work OK.

My architecture is:
CentOS (5.6) -> Oracle 11g SEO -> OC4J -> APEX Listener -> Apache Revers Proxy (with SSL)

Can you please help me in fixing this error?

Best Answer

But I found one thing in your ssl.conf I’d take a closer look on: As far as I know, Rewrite will encode all non-ANSI characters as %xx hex codes in output if you don’t disable it: So in case you already get them encoded, this will cause the double encoding you see.
You should check if all requests come in that way. Otherwise you should leave the inital rule unchanged and add a Rule (before that one) which just matches success messages and leaves all other requests untouched.

If that’s not the solution, I have one other guess: mod_headers is (of course) loaded before, so the headers are modified by that handler. Though I’d usually not expect some effect like what you see in this module, possibly the url is (re)encoded here as well. You could try to check that by either commenting out that section or the line where mod_headers is loaded.

Answers

which locales do proxy and OC4J use? And do you use APEX in a translated version or in English? Any special characters have to be treated correctly by each component on the way. Since your proxy needs to rebuild the request in the SSL case, it could happen that the request to OC4J gets some unsupported encoding. Do you see similar errors in other situations, e.g. other notifications in APEX?
And just to make the picture complete, which APEX and APEX Listener versions do you use?

I use Apex 4.0.2.00.07 English ver.
APEX Listener ver. 1.1.1.104.21.28

Incorrect login return Error notification message checksum content error
I notice, after correct login no Notification Messages (without error) only in URL I can read messages.

URL Messages are specific
. &success_msg=Region%2520Updated.%2520Report%2520attributes%2520
but I think it can be
. &success_msg=Region%20Updated.%20Report%20attributes%20
This is couse of checksum error in login error.

It look like reprocess URL %20 changed to %2520.

I don’t know How can I check Locale in Apache and OC4J, can you help ?

Obviously there happens some double URL encoding: *%25* is the code for a *%*

Do you have any additional URL encoding rule on the proxy?

First, you could display the current locale setting by executing and review additional settings with Especially for the OC4J, you can also check if some special JVM-arguments have been set by executing There is a bunch of other locations to configure NLS parameters.

A nice guide on this is included in the [url http://download.oracle.com/docs/cd/B32110_01/core.1013/b31263/iasconfig.htm#BHCEECHI]OAS Globalization Guide, which covers both the OHS (pretty close to Apache HTTPD) and OC4J parts of that scenario.

[]# locale
every row exclude LC_ALL contain the same value = «pl_PL.UTF-8»
LC_ALL have not value:
LC_ALL=

[]# env | grep -E «LC|NLS»
nothing

[]# echo $OC4J_JVM_ARGS
nothing

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

StartServers 8
MinSpareServers 5
MaxSpareServers 20
ServerLimit 256
MaxClients 256
MaxRequestsPerChild 4000

StartServers 2
MaxClients 150
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
MaxRequestsPerChild 0

LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_alias_module modules/mod_authn_alias.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule include_module modules/mod_include.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule expires_module modules/mod_expires.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule headers_module modules/mod_headers.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule info_module modules/mod_info.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule cache_module modules/mod_cache.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule version_module modules/mod_version.so

#
# Load config files from the config directory «/etc/httpd/conf.d».
#
Include conf.d/*.conf

User apache
Group apache

Options FollowSymLinks
AllowOverride None

#
# Possible values for the Options directive are «None», «All»,
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that «MultiViews» must be named explicitly — «Options All»
# doesn’t give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be «All», «None», or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride None

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all

#
# UserDir is disabled by default since it can confirm the presence
# of a username on the system (depending on home directory
# permissions).
#
UserDir disable

#
# To enable requests to /

user/ to serve the user’s public_html
# directory, remove the «UserDir disable» line above, and uncomment
# the following line instead:
#
#UserDir public_html

DirectoryIndex index.html index.html.var

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#

Order allow,deny
Deny from all

#
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
#
TypesConfig /etc/mime.types

# MIMEMagicFile /usr/share/magic.mime
MIMEMagicFile conf/magic

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat «%h %l %u %t »%r» %>s %b »%i» »%i»» combined
LogFormat «%h %l %u %t »%r» %>s %b» common
LogFormat «%i -> %U» referer
LogFormat «%i» agent

# «combinedio» includes actual counts of actual bytes received (%I) and sent (%O); this
# requires the mod_logio module to be loaded.
#LogFormat «%h %l %u %t »%r» %>s %b »%i» »%i» %I %O» combinedio

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a
# container, they will be logged here. Contrariwise, if you do
# define per- access logfiles, transactions will be
# logged therein and not in this file.
#
#CustomLog logs/access_log common

#
# If you would like to have separate agent and referer logfiles, uncomment
# the following directives.
#
#CustomLog logs/referer_log referer
#CustomLog logs/agent_log agent

#
# For a single logfile with access, agent, and referer information
# (Combined Logfile Format), use the following directive:
#
CustomLog logs/access_log combined

#
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (internal error documents, FTP directory
# listings, mod_status and mod_info output etc., but not CGI generated
# documents or custom error documents).
# Set to «EMail» to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
#
ServerSignature On

Alias /icons/ «/var/www/icons/»

Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all

#
# WebDAV module configuration section.
#

# Location of the WebDAV lock database.
DAVLockDB /var/lib/dav/lockdb

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing «/» apply to ScriptAlias directives as to
# Alias.
#
ScriptAlias /cgi-bin/ «/var/www/cgi-bin/»

#
# «/var/www/cgi-bin» should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#

AllowOverride None
Options None
Order allow,deny
Allow from all

#
# Redirect allows you to tell clients about documents which used to exist in
# your server’s namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Example:
# Redirect permanent /foo http://www.example.com/bar

#
# Directives controlling the display of server-generated directory listings.
#

#
# IndexOptions: Controls the appearance of server-generated directory
# listings.
#
IndexOptions FancyIndexing VersionSort NameWidth=* HTMLTable

#
# AddIcon* directives tell the server which icon to show for different
# files or filename extensions. These are only displayed for
# FancyIndexed directories.
#
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip

AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*

AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core

AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^

#
# DefaultIcon is which icon to show for files which do not have an icon
# explicitly set.
#
DefaultIcon /icons/unknown.gif

#
# AddDescription allows you to place a short description after a file in
# server-generated indexes. These are only displayed for FancyIndexed
# directories.
# Format: AddDescription «description» filename
#
#AddDescription «GZIP compressed document» .gz
#AddDescription «tar archive» .tar
#AddDescription «GZIP compressed tar archive» .tgz

#
# ReadmeName is the name of the README file the server will look for by
# default, and append to directory listings.
#
# HeaderName is the name of a file which should be prepended to
# directory indexes.
ReadmeName README.html
HeaderName HEADER.html

#
# IndexIgnore is a set of filenames which directory indexing should ignore
# and not include in the listing. Shell-style wildcarding is permitted.
#
IndexIgnore . * *

*# HEADER* README* RCS CVS *,v *,t

AddLanguage ca .ca
AddLanguage cs .cz .cs
AddLanguage da .dk
AddLanguage de .de
AddLanguage el .el
AddLanguage en .en
AddLanguage eo .eo
AddLanguage es .es
AddLanguage et .et
AddLanguage fr .fr
AddLanguage he .he
AddLanguage hr .hr
AddLanguage it .it
AddLanguage ja .ja
AddLanguage ko .ko
AddLanguage ltz .ltz
AddLanguage nl .nl
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pl .po
AddLanguage pt .pt
AddLanguage pt-BR .pt-br
AddLanguage ru .ru
AddLanguage sv .sv
AddLanguage zh-CN .zh-cn
AddLanguage zh-TW .zh-tw

#
# LanguagePriority allows you to give precedence to some languages
# in case of a tie during content negotiation.
#
# Just list the languages in decreasing order of preference. We have
# more or less alphabetized them here. You probably want to change this.
#
LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW

#
# ForceLanguagePriority allows you to serve a result page rather than
# MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
# [in case no accepted languages matched the available variants]
#
ForceLanguagePriority Prefer Fallback

#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default. To use the
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8

#
# AddType allows you to add to or override the MIME configuration
# file mime.types for specific file types.
#
#AddType application/x-tar .tgz

#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz

# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz

#
# AddHandler allows you to map certain file extensions to «handlers»:
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add «ExecCGI» to the «Options» directive.)
#
#AddHandler cgi-script .cgi

#
# For files that include their own HTTP headers:
#
#AddHandler send-as-is asis

#
# For type maps (negotiated resources):
# (This is enabled by default to allow the Apache «It Worked» page
# to be distributed in multiple languages.)
#
AddHandler type-map var

#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add «Includes» to the «Options» directive.)
#
AddType text/html .shtml
AddOutputFilter INCLUDES .shtml

#
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
#

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 «The server made a boo boo.»
#ErrorDocument 404 /missing.html
#ErrorDocument 404 «/cgi-bin/missing_handler.pl»
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# Putting this all together, we can internationalize error responses.
#
# We use Alias to redirect any /error/HTTP_ .html.var response to
# our collection of by-error message multi-language collections. We use
# includes to substitute the appropriate text.
#
# You can modify the messages’ appearance without changing any of the
# default HTTP_ .html.var files by adding the line:
#
# Alias /error/include/ «/your/include/path/»
#
# which allows you to create your own set of files by starting with the
# /var/www/error/include/ files and
# copying them to /your/include/path/, even on a per-VirtualHost basis.
#

Alias /error/ «/var/www/error/»

AllowOverride None
Options IncludesNoExec
AddOutputFilter Includes html
AddHandler type-map var
Order allow,deny
Allow from all
LanguagePriority en es de fr
ForceLanguagePriority Prefer Fallback

#
# The following directives modify normal HTTP response behavior to
# handle known problems with browser implementations.
#
BrowserMatch «Mozilla/2» nokeepalive
BrowserMatch «MSIE 4.0b2;» nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch «RealPlayer 4.0» force-response-1.0
BrowserMatch «Java/1.0» force-response-1.0
BrowserMatch «JDK/1.0» force-response-1.0

#
# The following directive disables redirects on non-GET requests for
# a directory that does not include the trailing slash. This fixes a
# problem with Microsoft WebFolders which does not appropriately handle
# redirects for folders with DAV methods.
# Same deal with Apple’s DAV filesystem and Gnome VFS support for DAV.
#
BrowserMatch «Microsoft Data Access Internet Publishing Provider» redirect-carefully
BrowserMatch «MS FrontPage» redirect-carefully
BrowserMatch «^WebDrive» redirect-carefully
BrowserMatch «^WebDAVFS/1.[0123]» redirect-carefully
BrowserMatch «^gnome-vfs/1.0» redirect-carefully
BrowserMatch «^XML Spy» redirect-carefully
BrowserMatch «^Dreamweaver-WebDAV-SCM1» redirect-carefully

# P3P IE SSL Frame

Header set P3P «policyref=»/w3c/p3p.xml», CP=»NOI DSP COR NID CUR ADM DEV OUR BUS»»

RewriteEngine on
RewriteRule ^/$ https://%/apex/f?p=800$1 [R]

Alias /i/ /path/i/
# Directory dla plików APEX-owych

Options None
AllowOverride None
Order allow,deny
Allow from all

# Cachowanie plików

ExpiresActive On
ExpiresDefault «access plus 1 month»

### Typy plików, które powinny być kompresowane

AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/x-javascript
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE text/x-component

# flash Chart #HOST#
ProxyPreserveHost On

ProxyPass /apex http://localhost:8888/apex
ProxyPassReverse /apex http://localhost:8888/apex
———————————————-

My ssl.conf file

LoadModule ssl_module modules/mod_ssl.so

#
# When we also provide SSL we have to listen to the
# the HTTPS port in addition.
#
Listen 443

AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl .crl

# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds).
#SSLSessionCache dc:UNIX:/var/cache/mod_ssl/distcache
SSLSessionCache shmcb:/var/cache/mod_ssl/scache(512000)
SSLSessionCacheTimeout 300

# Semaphore:
# Configure the path to the mutual exclusion semaphore the
# SSL engine uses internally for inter-process synchronization.
SSLMutex default

SSLRandomSeed startup file:/dev/urandom 256
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random 512
#SSLRandomSeed connect file:/dev/random 512
#SSLRandomSeed connect file:/dev/urandom 512

SSLCryptoDevice builtin
#SSLCryptoDevice ubsec

##
## SSL Virtual Host Context
##

# Wirtual host

ServerAdmin [email protected]
ServerName mydomain.pl

RewriteEngine on
RewriteRule ^/$ https://%/apex/f?p=800$1 [R]

SSLEngine on
SSLCertificateFile /path/server_key.txt
SSLCertificateKeyFile /path/private_key.txt
SSLCACertificateFile /path/ca_key.txt

But I found one thing in your ssl.conf I’d take a closer look on: As far as I know, Rewrite will encode all non-ANSI characters as %xx hex codes in output if you don’t disable it: So in case you already get them encoded, this will cause the double encoding you see.
You should check if all requests come in that way. Otherwise you should leave the inital rule unchanged and add a Rule (before that one) which just matches success messages and leaves all other requests untouched.

If that’s not the solution, I have one other guess: mod_headers is (of course) loaded before, so the headers are modified by that handler. Though I’d usually not expect some effect like what you see in this module, possibly the url is (re)encoded here as well. You could try to check that by either commenting out that section or the line where mod_headers is loaded.

Udo You are Great : )

It helped: RewriteRule ^/$ https://%/apex/f?p=800$1 *[NE,R]*

please help me if you can. I see you had a great solution for this kind of problem.

So, I have the exact same error message (notification message checksum content error) when I try to log in to my app. BUT the circumstances not the exact same.

Oracle DB version: 10.2.0.5
APEX version: 4.0.2.00.07
APEX Listener version: 1.1.3.243.11.40

There is no SSL, there is no other complicated configuration.

My httpd.conf file:

ServerRoot «/usr/local/apache2»
Listen 80
LoadModule jk_module modules/mod_jk.so

ServerAdmin [email protected]
DocumentRoot «/usr/local/apache2/htdocs»

Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all

Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all

Order allow,deny
Deny from all
Satisfy All

ErrorLog «logs/error_log»
LogLevel warn

LogFormat «%h %l %u %t »%r» %>s %b »%i» »%i»» combined
LogFormat «%h %l %u %t »%r» %>s %b» common

# You need to enable mod_logio.c to use %I and %O
LogFormat «%h %l %u %t »%r» %>s %b »%i» »%i» %I %O» combinedio

CustomLog «logs/access_log» common

ScriptAlias /cgi-bin/ «/usr/local/apache2/cgi-bin/»

AllowOverride None
Options None
Order allow,deny
Allow from all

TypesConfig conf/mime.types
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz

SSLRandomSeed startup builtin
SSLRandomSeed connect builtin

# Setup APEX static file path
Alias /i/ /usr/apex/images/

Order allow,deny
Allow from all

# Add extra mime types
AddType text/xml xbl
AddType text/x-component htc

# Mod_jk Settings
JkWorkersFile /root/tomcat/apache-tomcat-6.0.33/conf/jk/workers.properties
JkLogFile /root/tomcat/apache-tomcat-6.0.33/logs/mod_jk.log
JkLogLevel info
JkLogStampFormat «[%a %b %d %H:%M:%S %Y] »
JkMount /apex/* default

There’s no other configuration!

The error occured after I enabled the session state protection. It is unbelievable, but if I disable the session state protection the error is the same.

What can be the solution? Is there a workaround for this?

Источник

After I successfully installed Application Express 4.2.1.00.08 (latest version in this moment), I decided to test Apex Listener. So I installed (latest version in this moment) Apex Listener 2.0.0 354.17.05, which seems to be stable enough.

First tried standalone version but very soon found out that this is not a good way to run this product even in demo environment.

So I decided to install Tomcat 7.0 as free solution and implement Apex Listener as classic application. Regardless this combination is officially not supported by Oracle, after some small configuration problems (mainly with SQL Developer as configuration platform), my Apex was running fast as hell … and I was very glad to know that this combination really rocks. And the best of all free!

This looked very, very promising. I was courios what other problems I might run into … but for some time there were none.

The problem

But while I was developing one app, I run in the problem which I firstly thought it is pure Apex problem. Notification message on protected page was making fatal Apex error. This is the error content from WEB developed session:

Error: Success message checksum content error
Contact your application administrator.
 
Technical Info (only visible for developers)
is_internal_error: true
apex_error_code: APEX.SUCCESS_MSG.CHECKSUM_CONTENT_ERROR
error_backtrace:
----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
000007FF7D92A9B0       548  package body APEX_040200.WWV_FLOW_ERROR
000007FF7D92A9B0       599  package body APEX_040200.WWV_FLOW_ERROR
000007FF7D92A9B0       903  package body APEX_040200.WWV_FLOW_ERROR
000007FF7C7F5C30       794  package body APEX_040200.WWV_FLOW_SECURITY
000007FF7DA033F0      5778  package body APEX_040200.WWV_FLOW
000007FF7DA138B0       249  procedure APEX_040200.F
000007FF7C49D528         2  anonymous block

Very soon I discovered that this error was triggering only when in it’s content was Croatian (or any other) national characters (like €, Ł etc).
Here are the step to reproduce the problem.

1. Create a authentication page with «Page Access Protection» defined as «Arguments must have checksum»
2. Create a page process (On Submit After Computation and Validation).
3. In that process use Apex application variable (G_APP_MESSAGE, in mine case) as a holder for success message. Code is exactly like

   :G_APP_MESSAGE := 'Lozinka uspjesno promijenjena!';
   

4. After submitting page, everything went fine … and success message is shown as expected.

If You change step 3) so G_APP_MESSAGE is defined as :

:G_APP_MESSAGE := 'Lozinka uspješno promijenjena!'; 

Just to accent that I changed uspjesno->uspješno (s->š), and submit a page again, I get an error described previously.

I tried change G_APP_MESSAGE in a way:

:G_APP_MESSAGE := utl_url.escape('Lozinka uspješno promijenjena!'); 

I get success message as:

Lozinka%20uspje%BFno%20promijenjena!

but without error.



When I return back mine š sign to s (now message again has only USA characters), remove «utl_url.escape», page is submitted normally and success message is ok (but again without national signs).

The solution

I tried to reproduce the same problem in Apex cloud but this was not the case. So easy conclusion was that something is wrong in mine configuration and the only thing that differed was-Tomcat.
So after some googleing I found the cause. Problem is with Tomcat URI Encoding. Default encoding is ISO-8859-1, but from APEX, comes URL with message encoded in UTF-8. Solution Solution was very easy to implement. Follow next steps:

1. Stop Tomcat service
2. Find file server.xml and make a backup.
3. Open servr.xml file (with some proper editor which can handle UTF-8 encoded files), and find content:

       <Connector port="8080" protocol="HTTP/1.1"
                  connectionTimeout="20000"
                  maxHttpHeaderSize="32767"
                  redirectPort="8443" />;
   

   In mine case it wasline 70.

4. Add URIEncoding=»UTF-8″ before closing tag. Changed value looks:

       <Connector port="8080" protocol="HTTP/1.1"
                  connectionTimeout="20000"
                  maxHttpHeaderSize="32767"
                  redirectPort="8443" URIEncoding="UTF-8" />;
   

Steps 5 and 6 are for Older Apex Listener configuration, but on Apex 2.0 it was not needed at all.

5. Create filters directory (error is not important if exists)

   mkdir $CATALINA_HOME/webapps/apex/WEB-INF/classes/filters
   

6. Insert after the last </servlet-mapping> tag:

   vi $CATALINA_HOME/webapps/apex/WEB-INF/web.xml 
   

     Set Character Encoding
     filters.SetCharacterEncodingFilter
     
      encoding
      UTF8
     
    
   
     Set Character Encoding
     /*
   
   

7. Restart Tomcat.

The End

Even this is not a rocket science, it may shorten finding the solution to someone else.

Hope this helps someone.

Cheers!

I am in   apex.oracle.com    .  Trying to create a custom authentication .

When I login with correct password, it works fine.    However If I enter a wrong password, instead of going to the login page and display the failure message, it shows some checksum error.

I checked various postings on web, and tried different setups.   No success

Can anyone please help.

This is not locally installed, This is on apex.oracle.com   trial workspace  version 5.0

Here is the detail

• is_internal_error: true
• apex_error_code: APEX.NOTIFICATION_MSG.CHECKSUM_CONTENT_ERROR
• component.type: APEX_APPLICATION_PAGES
• component.id: 70731000000101
• error_backtrace: —— PL/SQL Call Stack —— object line object handle number name 0x49785b860 641 package body APEX_050000.WWV_FLOW_ERROR 0x49785b860 709 package body APEX_050000.WWV_FLOW_ERROR 0x49785b860 1013 package body APEX_050000.WWV_FLOW_ERROR 0x49aed7ea0 1082 package body APEX_050000.WWV_FLOW_SECURITY 0x49aed7ea0 1099 package body APEX_050000.WWV_FLOW_SECURITY 0x497ab6138 4273 package body APEX_050000.WWV_FLOW 0x4977e7308 173 procedure APEX_050000.F 0x325c2e5f8 2 anonymous block

********************************************************************

.

The custom authentication has only two functions

create or replace FUNCTION obfuscate(text_in IN VARCHAR2) RETURN RAW IS

    l_returnvalue RAW(16);

  BEGIN

    —dbms_obfuscation_toolkit.md5(input => utl_raw.cast_to_raw(text_in), checksum => l_returnvalue);

  l_returnvalue :=    dbms_obfuscation_toolkit.md5(input => utl_raw.cast_to_raw(text_in));

    RETURN l_returnvalue;

  END obfuscate;

/*************************************************************************************************************/

create or replace FUNCTION authenticate(p_username IN VARCHAR2

                       ,p_password IN VARCHAR2) RETURN BOOLEAN IS

    l_obfuscated_password RAW(16);

    l_value               NUMBER;

    l_username  VARCHAR2(100) := p_username;

    l_password  VARCHAR2(100) := p_password;

    l_return            BOOLEAN;

  BEGIN

    l_obfuscated_password := obfuscate(text_in => l_password);

    BEGIN

      SELECT 1

        INTO l_value

        FROM socmis_users a

       WHERE 1 = 1

         AND upper(a.user_name) = upper(l_username)

         AND a.password = l_obfuscated_password;

    EXCEPTION

      WHEN no_data_found

           OR too_many_rows THEN

        l_value := 0;

      WHEN OTHERS THEN

        l_value := 0;

    END;

    IF l_value = 1 THEN

    l_return :=  TRUE;

    ELSE

    l_return := FALSE;

    END IF;

    RETURN l_return;

  END authenticate;

Following is the URL I get when the error comes. The error comes only when I enter wrong password

https://apex.oracle.com/pls/apex/f?p=70731:101:0:::::&notification_msg=Invalid%20Login%20Credentials%3Cdiv%20id=%2522ape…

Update

**********************

I noticed that This is happening with one particular application only , and the error is coming even with Oracle_application_express Accounts standard  authentication .  Not just custom

Only happen, when a wrong password is entered. 

The application is actually created when apex.oracle.com   was in 4.2  .  When oracle  upgraded to 5.0  it automatically upgraded.

Can someone please help. I am stuck

George

Message was edited by: gkthomas

I have a problem with an application in the HTML DB that I am creating. the problem is:
I create plicacion from each one of the tables, when trying to enter a registry in the application of concept, sends east error to me, but if it stores the registry. the error is:
Error print success message checksum content error: Action procesada./6À1Ç9ÁFE08952600ACEC1E0188ÅC/: 4730F16841157B21D061A969F6640A61.
the design I did it with Oracle designer.
the model contains three tables:
1. file .tab the designer
PROMPT Creating Table ‘CONSULTOR’
CREATE TABLE CONSULTOR
(ID_CEDULA NUMERIC(12) NOT NULL
PROMPT Creating Table ‘CONCEPTO’
CREATE TABLE CONCEPTO
(ID_CONCEPTO NUMERIC(3) NOT NULL
,DESC_CONCEPTO VARCHAR2(120)
,FACTURABLE VARCHAR(5)
PROMPT Creating Table ‘GENERAL’
CREATE TABLE GENERAL
(ID_GENERAL NUMERIC(5) NOT NULL
,CONC_ID_CONCEPTO NUMERIC(3) NOT NULL
,CONS_ID_CEDULA NUMERIC(12) NOT NULL
,FECHA_ACT DATE
,DESCRIPCION_ACT VARCHAR2(120)
,CANTIDAD_HORAS NUMERIC(5)
2. file .con the designer
PROMPT Creating Primary Key on ‘CONSULTOR’
ALTER TABLE CONSULTOR ADD (CONSTRAINT
CONS_PK PRIMARY KEY
(ID_CEDULA))
PROMPT Creating Primary Key on ‘GENERAL’
ALTER TABLE GENERAL ADD (CONSTRAINT
GENE_PK PRIMARY KEY
(ID_GENERAL))
PROMPT Creating Primary Key on ‘CONCEPTO’
ALTER TABLE CONCEPTO ADD (CONSTRAINT
CONC_PK PRIMARY KEY
(ID_CONCEPTO))
PROMPT Creating Foreign Key on ‘GENERAL’
ALTER TABLE GENERAL ADD (CONSTRAINT
GENE_CONC_FK FOREIGN KEY
(CONC_ID_CONCEPTO) REFERENCES CONCEPTO
(ID_CONCEPTO))
PROMPT Creating Foreign Key on ‘GENERAL’
ALTER TABLE GENERAL ADD (CONSTRAINT
GENE_CONS_FK FOREIGN KEY
(CONS_ID_CEDULA) REFERENCES CONSULTOR
(ID_CEDULA))
3 file . lis de designer
Reconcile Report: C:Documents and SettingsrolandoMis documentosasoxxx.lis
Generated on Tue Jun 07 09:55:25 2005 by Server Generator 9.0.4.3.14
====== ======== ================ ==============
Object Property Repository Value Database Value
====== ======== ================ ==============
Object Property Repository Value Database Value
Table CONCEPTO * NOT IN DATABASE * ***
Object Type
Data Persistence Permanent
Cluster
Index Only No
Cached
Initial Transactions
Max Transactions
Percent Free
Percent Used
Initial Extents
Next Extent
Min Extents
Max Extents
Percent Increase
Freelists
Freelist Groups
Tablespace
Parallel No
Comment
Column ID_CONCEPTO * NOT IN DATABASE * ***
Datatype NUMERIC
Max Length 3
Scale
Mandatory Yes
Default Value
Domain
Comment
Column DESC_CONCEPTO * NOT IN DATABASE * ***
Datatype VARCHAR2
Max Length 120
Scale
Mandatory No
Default Value
Domain
Comment
Column FACTURABLE * NOT IN DATABASE * ***
Datatype VARCHAR
Max Length 5
Scale
Mandatory No
Default Value
Domain
Comment
Primary Key CONC_PK * NOT IN DATABASE * ***
Enabled Yes
Deferred No
Immediate No
Exception Table
Key Column ID_CONCEPTO
Index CONC_PK * NOT IN DATABASE * ***
Unique Yes
Global No
Bitmapped No
Compute Statistics No
Reverse No
Nosort No
Initial Transactions
Max Transactions
Percent Free
Percent Used
Initial Extents
Next Extent
Min Extents
Max Extents
Percent Increase
Freelists
Freelist Groups
Tablespace
Parallel No
Snapshot Log No No
Table CONCEPTO Differences: 1
Object Property Repository Value Database Value
Table CONSULTOR * NOT IN DATABASE * ***
Object Type
Data Persistence Permanent
Cluster
Index Only No
Cached
Initial Transactions
Max Transactions
Percent Free
Percent Used
Initial Extents
Next Extent
Min Extents
Max Extents
Percent Increase
Freelists
Freelist Groups
Tablespace
Parallel No
Comment
Column ID_CEDULA * NOT IN DATABASE * ***
Datatype NUMERIC
Max Length 12
Scale
Mandatory Yes
Default Value
Domain
Comment
Primary Key CONS_PK * NOT IN DATABASE * ***
Enabled Yes
Deferred No
Immediate No
Exception Table
Key Column ID_CEDULA
Index CONS_PK * NOT IN DATABASE * ***
Unique Yes
Global No
Bitmapped No
Compute Statistics No
Reverse No
Nosort No
Initial Transactions
Max Transactions
Percent Free
Percent Used
Initial Extents
Next Extent
Min Extents
Max Extents
Percent Increase
Freelists
Freelist Groups
Tablespace
Parallel No
Snapshot Log No No
Table CONSULTOR Differences: 1
Object Property Repository Value Database Value
Table GENERAL * NOT IN DATABASE * ***
Object Type
Data Persistence Permanent
Cluster
Index Only No
Cached
Initial Transactions
Max Transactions
Percent Free
Percent Used
Initial Extents
Next Extent
Min Extents
Max Extents
Percent Increase
Freelists
Freelist Groups
Tablespace
Parallel No
Comment
Column ID_GENERAL * NOT IN DATABASE * ***
Datatype NUMERIC
Max Length 5
Scale
Mandatory Yes
Default Value
Domain
Comment
Column CONC_ID_CONCEPTO * NOT IN DATABASE * ***
Datatype NUMERIC
Max Length 3
Scale
Mandatory Yes
Default Value
Domain
Comment
Column CONS_ID_CEDULA * NOT IN DATABASE * ***
Datatype NUMERIC
Max Length 12
Scale
Mandatory Yes
Default Value
Domain
Comment
Column FECHA_ACT * NOT IN DATABASE * ***
Datatype DATE
Max Length
Scale
Mandatory No
Default Value
Domain
Comment
Column DESCRIPCION_ACT * NOT IN DATABASE * ***
Datatype VARCHAR2
Max Length 120
Scale
Mandatory No
Default Value
Domain
Comment
Column CANTIDAD_HORAS * NOT IN DATABASE * ***
Datatype NUMERIC
Max Length 5
Scale
Mandatory No
Default Value
Domain
Comment
Primary Key GENE_PK * NOT IN DATABASE * ***
Enabled Yes
Deferred No
Immediate No
Exception Table
Key Column ID_GENERAL
Index GENE_PK * NOT IN DATABASE * ***
Unique Yes
Global No
Bitmapped No
Compute Statistics No
Reverse No
Nosort No
Initial Transactions
Max Transactions
Percent Free
Percent Used
Initial Extents
Next Extent
Min Extents
Max Extents
Percent Increase
Freelists
Freelist Groups
Tablespace
Parallel No
Foreign Key GENE_CONC_FK * NOT IN DATABASE * ***
Enabled Yes
Deferred No
Immediate No
Cascade Delete RESTRICT
Cascade Update RESTRICT
Exception Table
Join Table CONCEPTO
Key Column CONC_ID_CONCEPTO
Referenced Column CONCEPTO.ID_CONCEPTO
Foreign Key GENE_CONS_FK * NOT IN DATABASE * ***
Enabled Yes
Deferred No
Immediate No
Cascade Delete RESTRICT
Cascade Update RESTRICT
Exception Table
Join Table CONSULTOR
Key Column CONS_ID_CEDULA
Referenced Column CONSULTOR.ID_CEDULA
Snapshot Log No No
Table GENERAL Differences: 1
====================================================================================================================================
Total Differences: 3
====================================================================================================================================

Существуют несколько вариаций ошибок CMOS checksum error, которые возникают редко, но, как правило, в самый неподходящий момент.

Рассмотрим решение этой проблемы на ошибке «CMOS checksum error Defaults loaded warning! Now System is in safe mode. Pleas re setting CPU frequency in the CMOS setup«.

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

Не будет углубляться во все тонкости и премудрости данной ошибки, так как многим пользователям ПК это просто не нужно, вопрос стоит только в одном, как решить проблему с ошибкой «CMOS checksum error».

Решение проблемы

Мы расскажем, как была решена данная проблема в нашем случае, у кого есть другие варианты, оставляйте их в комментариях.

Итак, часть ответа уже заложена в самом сообщении. Обратите внимание на вот эту часть предложения «Просьбы повторно установив частоту процессора в настройках CMOS». То есть, нам необходимо добраться до настроек CMOS, а по-простому зайти в BIOS.

Как это сделать система уже подсказывает.

Обнуляем BIOS

Но перед тем, как зайти в Биос, как вариант, можно попробовать сбросить выставленные в нем настройки, так как они, наверное, были частично выставлены не правильные.

Для этого необходимо вынуть батарейку памяти CMOS на 1 – 2 минуты. Как это деть показано на фото.

Заходим в BIOS

Обратите внимание на сообщение «Del to enter Setup». То есть нужно, на начальном этапе загрузки компьютера нажать кнопку Del, и вы попадете в настройки BIOS.

Сообщение может быть и другим, к примеру, «F2 to enter Setup» и т.д., поэтому кнопка DEL, это не панацея, все зависит от модели компьютера, ноутбука и версии самой BIOS.

Также от многого зависит, какая перед вами возникнет картинка. Но что она должна быть с синим фоном, это 100%.

Как вариант вы можете наблюдать ниже.

Чтобы не заморачиваться и искать в этих дебрях решение своей проблемы, можно использовать горячие клавиши F5 – Previous Values (предыдущие значения), F7 – Optimized Defaults (значения по умолчанию), F6 – Fail-safe Defaults (загрузка безопасных значений по умолчанию).

Обратите внимание, что в разных BIOS значение клавиш может быть разным, поэтому правильно переводите текст.

В нашем случает помогла клавиша F5 – предыдущие значения. Вы можете попробовать и другие клавиши.

После нажатия клавиши F5, появится окно – Подтвердить выбор Y – да, N – нет. Нажимаете клавишу Y.

Чтобы сохранить все изменения и сразу выйти нажмите клавишу F10 и так же подтвердите свой выбор нажав клавишу Y.

Компьютер начнет перезагружаться и ошибки «CMOS checksum error» уже не должно возникнуть.

Если все же проблема осталась, то обратитесь к специалисту, так как эта статья предназначена для начинающего пользователя ПК, а также среднего уровня подготовки.

Но в любом случае мы надеемся, что вам помогли. Удачи.

Последнее обновление 16.06.2021

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

Где и когда можно встретить ошибку 500

Вы можете увидеть ошибку на любом веб-ресурсе, браузере и устройстве. Она не связана с отсутствием интернет-соединения, устаревшей версией операционной системы или браузера. Кроме того, эта ошибка не указывает на то, что сайта не существует или он больше не работает.

Ошибка 500 говорит о том, что сервер не может обработать запрос к сайту, на странице которого вы находитесь. При этом браузер не может точно сообщить, что именно пошло не так. 

Отображаться ошибка может по-разному. Вот пример:

Если вы решили купить что-то в любимом интернет-магазине, но увидели на сайте ошибку 500, не стоит сильно огорчаться – она лишь сообщает о том, что вам нужно подождать, пока она будет исправлена.

Если ошибка появилась на вашем сайте, то нужно скорее ее исправлять. Далее я расскажу, как это можно сделать.

Причины возникновения ошибки

Итак, ошибка 500 возникает, когда серверу не удается обработать запрос к сайту. Из-за этого пользователи не могут попасть на сайт, а поисковые системы полноценно с ним работать. Очевидно, что ошибка нуждается в исправлении. В первую очередь необходимо найти проблему.

Основной причиной ошибки 500 может быть:

1. Неверный синтаксис файла .htaccess. htaccess – это файл, в котором можно задавать настройки для работы с веб-сервером Apache и вносить изменения в работу сайта (управлять различными перенаправлениями, правами доступа к файлам, опциями PHP, задавать собственные страницы ошибок и т.д.). 
   Узнать больше о файле .htaccess можно в статье «Создание и настройка .htaccess».
2. Ошибки в скриптах сайта, то есть сценариях, созданных для автоматического выполнения задач или для расширения функционала сайта.
3. Нехватка оперативной памяти при выполнении скрипта.
4. Ошибки в коде CMS, системы управления содержимым сайта. В 80% случаев виноваты конфликтующие плагины. 

Как получить больше данных о причине ошибки 

Что означает ошибка 500, мы теперь знаем. Когда она перестала быть таким загадочным персонажем, не страшно копнуть глубже — научиться определять причину ошибки. В некоторых случаях это можно сделать самостоятельно, так что обращаться за помощью к профильному специалисту не понадобится.

Отображение ошибки бывает разным. Ее внешний облик зависит от того, чем она вызвана.

Самые частые причины ошибки 500 можно распознать по тексту ошибки или внешнему виду страницы. 

1. Сообщение Internal Server Error говорит о том, что есть проблемы с файлом .htaccess (например, виновата некорректная настройка файла). Убедиться, что .htaccess является корнем проблемы, поможет следующий прием: переименуйте файл .htaccess, добавив единицу в конце названия. Это можно сделать с помощью FTP-клиента (например, FileZilla) или файлового менеджера на вашем хостинге (в Timeweb такой есть, с ним довольно удобно работать). После изменения проверьте доступность сайта. Если ошибка больше не наблюдается, вы нашли причину.
2. Сообщение HTTP ERROR 500 или пустая страница говорит о проблемах со скриптами сайта. В случае с пустой страницей стоит учесть, что отсутствие содержимого сайта не всегда указывает на внутреннюю ошибку сервера 500.

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

Как открыть панель разработчика

• Нажмите клавишу F12 (способ актуален для большинства браузеров на Windows). Используйте сочетание клавиш Cmd+Opt+J, если используете Google Chrome на macOS. Или примените комбинацию Cmd+Opt+C в случае Safari на macOS (но перед этим включите «Меню разработки» в разделе «Настройки» -> «Продвинутые»). Открыть инструменты разработчика также можно, если кликнуть правой кнопкой мыши в любом месте веб-страницы и выбрать «Просмотреть код» в контекстном меню. 
• Откройте вкладку «Сеть» (или «Network») и взгляните на число в поле «Статус». Код ответа об ошибке 500 — это соответствующая цифра.

Более детальную диагностику можно провести с помощью логов.

Простыми словами: лог — это журнал, в который записывается информация об ошибках, запросах к серверу, подключениях к серверу, действиях с файлами и т.д.

Как вы видите, данных в логи записывается немало, поэтому они разделены по типам. За сведениями о нашей ошибке можно обратиться к логам ошибок (error_log). Обычно такие логи предоставляет служба поддержки хостинга, на котором размещен сайт. В Timeweb вы можете включить ведение логов и заказать необходимые данные в панели управления. Разобраться в полученных логах поможет статья «Чтение логов».

Как устранить ошибку

Теперь поговорим о том, как исправить ошибку 500. Вернемся к популярным причинам этой проблемы и рассмотрим наиболее эффективные способы решения.

Ошибки в файле .htaccess

У этого файла довольно строгий синтаксис, поэтому неверно написанные директивы (команды) могут привести к ошибке. Попробуйте поочередно удалить команды, добавленные последними, и проверьте работу сайта. 
Также найти проблемную директиву можно с помощью логов ошибок (через те же инструменты разработчика в браузере). На ошибку в директиве обычно указывает фраза «Invalid command». Информацию о верном написании директивы или способе исправления ошибок в .htaccess вы можете найти в интернете. Не нужно искать, почему сервер выдает ошибку 500, просто введите в строку поиска название нужной команды или текст ошибки из логов.

Ошибки в скриптах сайта

Скрипт не запускается

Обычно это происходит, когда существует ошибка в скрипте или функция, которая не выполняется. Для успешного запуска скрипта функция должна быть верно прописана, поддерживаться сервером и выполняться от используемой версии PHP. Бывают ситуации, когда функция несовместима с определенными версиями PHP. Получить более подробную информацию о той или иной функции можно в интернете. 

Не хватает оперативной памяти

Если в логах вы видите ошибку «Allowed memory size», для устранения ошибки 500 стоит оптимизировать работу скрипта. Вы можете воспользоваться специальными расширениями для анализа производительности скрипта или обратиться за помощью к специалисту, который поработает над его оптимизацией.

Если ваш сайт размещен на отдельном физическом или виртуальном сервере, можно попробовать увеличить максимальное использование оперативной памяти на процесс (memory_limit). На шаред хостинге этот параметр обычно не изменяется, но есть возможность купить хостинг помощнее.

Ошибки в CMS

Если код CMS содержит неверный синтаксис, это может вывести сайт из строя. В таком случае логи сообщат вам об ошибке 500 текстом «PHP Parse error: syntax error, unexpected». Так происходит, когда некорректно работает плагин (или тема, используемая в CMS, но реже) либо есть ошибки в коде. Ошибка может быть допущена случайно, произойти при обновлении плагина или версии CMS.

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

Также в большинстве случаев подобные проблемы помогает решить поддержка CMS.

Информацию о других распространенных ошибках вы можете найти в статье «6 наиболее часто возникающих ошибок HTTP и способы их устранения».

Удачи! 

Помогла ли Вам статья?