Note 436685 - Blank screen when you first logon after system restart
Summary
SymptomWhen you first logon after restarting an SAP System, the a blank screen without menus is displayed instead of the usual logon screen (only icons for "Enter", "Create a new session", "Generate a shortcut on the desktop", "Customizing of local layout" are shown).
When you logon again, the normal logon screen appears.
Additional key wordsBEAD
Cause and prerequisitesThe internal consistency checks have detected an error in the system configuration. Until now, an error screen with an OK code message of the type "Inconsistency with database: start transaction SICK" was generated during the first login. This no longer happens (the reasons have not yet been clarified). Instead a blank screen appears.
Under ST22 (display ABAP runtime error), a corresponding short dump START_CALL_SICK should be listed.
SolutionAfter logon, execute transaction SICK to determine the cause of the inconsistency. SICK should also provide information on how to remedy the error.
Productive operation can only be resumed when the inconsistency has been eliminated.
In relation to this, please note the following:
Due to an error in SQL 2000 relating to NULL values, customers (with SQL 2000 or SQL 2000 SP1) should switch as soon as possible to SQL 2000 service package 2. Alternatively, if this is not possible, they must import a hotfix (see note 425946). This is now also checked in the consistency check. If SICK issues the following messages
SAP System Check
--------------------------------------------------------------
DB CHECK Invalid MSSQL 2000 release
DB CHECK Please see note 126973
--------------------------------------------------------------
Severe problems were detected during initial system check.
Please, do not use that system before fixing these problems.
, you must procees as described in note 126973 (or 425946).
When you logon again, the normal logon screen appears.
Additional key wordsBEAD
Cause and prerequisitesThe internal consistency checks have detected an error in the system configuration. Until now, an error screen with an OK code message of the type "Inconsistency with database: start transaction SICK" was generated during the first login. This no longer happens (the reasons have not yet been clarified). Instead a blank screen appears.
Under ST22 (display ABAP runtime error), a corresponding short dump START_CALL_SICK should be listed.
SolutionAfter logon, execute transaction SICK to determine the cause of the inconsistency. SICK should also provide information on how to remedy the error.
Productive operation can only be resumed when the inconsistency has been eliminated.
In relation to this, please note the following:
Due to an error in SQL 2000 relating to NULL values, customers (with SQL 2000 or SQL 2000 SP1) should switch as soon as possible to SQL 2000 service package 2. Alternatively, if this is not possible, they must import a hotfix (see note 425946). This is now also checked in the consistency check. If SICK issues the following messages
SAP System Check
--------------------------------------------------------------
DB CHECK Invalid MSSQL 2000 release
DB CHECK Please see note 126973
--------------------------------------------------------------
Severe problems were detected during initial system check.
Please, do not use that system before fixing these problems.
, you must procees as described in note 126973 (or 425946).
Header Data
| Release Status: | Released for Customer |
| Released on: | 19.09.2001 22:00:00 |
| Master Language: | German |
| Priority: | Recommendations/additional info |
| Category: | Program error |
| Primary Component: | BC-DB-MSS Microsoft SQL Server |
yurtdışı kargo
ReplyDeleteresimli magnet
instagram takipçi satın al
yurtdışı kargo
sms onay
dijital kartvizit
dijital kartvizit
https://nobetci-eczane.org/
YLML