Invalid login credentials after upgrading to 3.0.1

I have upgraded our apex2.1 version to 3.0.1. When trying to login for the first time I entered my database user name in the workspace field and enter my database user name and password as per upgrade instructions. However, all I get is the error 'Invalid login credentials'. The upgrade instructions do not mention any additionals action steps that must be taken. Can anyone please advise how to solve this problem.
Thanks, Richard

I had the same problem and tried about everything with no success, until ...
I changed the ADMIN password using the apxxepwd.sql script (can be found in the root of the 3.0.1 apex directory). Run this script under sqlplus as "sys/password as sysdba" and enter twice the ADMIN password when prompted for '&1'. Login on http://localhost:8080/apex/apex_admin, you'll be prompted to change the password. Change the password (may be the same as the old one) and now you can finally login as ADMIN.
I did this on APEX 3.0.1 on a Oracle EXPRESS 10.2.0.1.0 on Windows Vista, and suppose this must work on other platforms too.

Similar Messages

Invalid Login Credentials after a brand new install of APEX 2.2

I'm trying to install APEX2.2 for the first time to see what it can do.
I have followed the install document.
When I got ot here, http://localhost:7777/pls/htmldb
It requests a workspace, username, password.
back to the documentation, it states use http://localhost:7777/pls/htmldb/apex_admin
to create your workspace. And to sign in as admin, and the password passed into @apexins.sql When I try that, it results in the error message "Invalid Login Credentials" The documentation does not describe anything about that!
Please help
Thanks,
Jason

Joel,
I had a cut and paste error in my last posting, I actually ran this:
alter user FLOWS_020200 account unlock;
connect FLOWS_020200/apex
begin
wwv_flow_api.set_security_group_id(p_security_group_id=>10);
wwv_flow_fnd_user_api.create_fnd_user(
p_user_name => 'admin2',
p_email_address => '[email protected]',
p_web_password => 'admin2') ;
end;
alter user FLOWS_020200 account unlock;
I have a thought on why Ben and I both had this same "Invalid Login Credentials" issue. In my case it certainly wasn't because of any special characters in the password. I used apex as a password.
From reading Ben's post I see we both first had a problem with the images directory. Sounds like Ben had the same issue I had. Which was in the marvel.conf I first entered this
Alias /i/ "C:\oracle\product\10.2.0\db_as\Apache\Apache\images"
instead of this:
Alias /i/ "C:\oracle\product\10.2.0\db_as\Apache\Apache\images/"
This caused my http://localhost:7777/pls/htmldb URL to paritially work. I'm thinking that may be what caused the "Invalid Login Credentials" once I made the Alias adjustment.
Thanks,
Jason

Unable to get the login page after upgrade from 11.5.10.2 to R12

Hi ,
We are unable to get the login page after upgrade from 11.5.10.2 to R12, all the services are up and running.
Pls let me know if someone has come across this issue.
Thanks&Regards,
Apps DBA

Hi ,
After compile JSP files manually , now we are facing problem after logging.
Error : You have encountered an unexpected error.
Thanks&Regards,
Apps DBA

Stuck in a "loop" at the login window after upgrading to Leopard

I bought a new iMac Oct 26. It contained Tiger, and included a disk for installing Leopard. I easily got the machine up and running using Tiger, but last night I attempted to install Leopard. When the installation was complete, I tried to get it running. A screen asking for my password came up. I keyed that in and hit logon. Back came the screen asking for the password. To make long story short, I tried everything I could last night, and then called Apple Support this morning. Took quite a while, but I was back in business this afternoon. The technician who helped me sent me the email copied below describing the solution. Perhaps it will help someone else? Romelle
Hello from Apple!
Charles at Apple Service & Support thought that you might find this article useful. We hope that it helps resolve your technical issue.
Link: http://www.info.apple.com/kbnum/n306965
Mac OS X 10.5, iMac (Late 2007): Stuck in a "loop" at the login window after upgrading to Leopard
Issue or symptom
After installing Mac OS X 10.5 Leopard on a 20-inch or 24-inch iMac (Late 2007) computer, you may not be able to log in at the login window. Your login name and password are apparently accepted, but after a blue screen appears for a few seconds, the login window reappears instead of your desktop.
Products affected
20-inch or 24-inch iMac (Late 2007) computer with 2.0, 2.4, or 2.8 GHz processors
Mac OS X 10.5 Leopard
Solution
If Leopard is installed
Start up from the Leopard Install DVD and perform an Archive and Install installation (and select Preserve Users and Network Settings).
After the Archive and Install is complete, you should be able to successfully log in. Use Software Update to install any other updates.
Important: Install the iMac Software Update 1.3 for Leopard after the Archive and Install is complete.
If Leopard is not yet installed
If you have not yet installed Leopard on your 20-inch or 24-inch aluminum iMac computer with a 2.0, 2.4, or 2.8 GHz processor running Mac OS X 10.4.x, but previously installed the iMac Software Update 1.2, you should install the iMac Software Update 1.2.1 (Tiger) or later, before installing Leopard.
Thank you,
Apple

If Leopard came pre-installed and this is a new machne, then the disks that came in the box should let you archive install preserving users & network settings. The disks have a grey label, and if you get more than one use disk #1 for this procedure.
Hold down the "option" (also known as "alt" on the new keyboards) key when starting up with disk #1 in the optical drive. Select the install disk icon on the grey screen and click the arrow. Then when you get to the "select destination pane, click the options button after selecting your hard drive as the destination. In options A& I preserving should be checked by default, if not, select them. Click "ok" to dismiss the options pane, then run the installation.
If this does not work for you, call apple support. They want everything to work. Be patient, they are real busy these days.
Slim

Error: 1051293: Login fails due to invalid login credentials

Need help!
I searched all the threads for this but i still have not found one that works for my issue.
I was trying to add a new essbase server using EAS and i been getting the following error.
I am able to login into the EAS with the same user name and password, but i am getting the following error when i try to ADD essbase server.
admin July 7, 2010 12:40:32 AM CDT com.essbase.eas.admin.defs.AdminCommands.AddServerToUserList Succeeded
winserver com.essbase.eas.essbase.defs.ServerCommands.Connect July 7, 2010 12:40:33 AM CDT Failed : 1051293 Login fails due to invalid login credentials
Error: 1051293 Login fails due to invalid login credentials
Essbase Server: winserver com.essbase.eas.essbase.defs.ServerCommands.Connect July 7, 2010 12:40:33 AM CDT
Error: 1051293: Login fails due to invalid login credentials
HELP!!
Alex

You have already posted the question here :- Error: 1051293: Login fails due to invalid login credentials
Cheers
John
http://john-goodwin.blogspot.com/

How to change the error message Invalid login credentials

Hi all,
How to change the default error messages .
1) In the Login page while giving wrong username or password .It showing
Error message "Invalid login credentials".
But requirement is change the above error message.
2) I need to change the error message instead of "1 error has occureed"
Thanks in Advance
Sudhakar

On the Login Page of the application create a 'Before Header' process with this code if apex_application.g_notification ='Invalid Login Credentials' then
apex_application.g_notification :='Your Altered Failed Login Message Here';
end if;varad

EssBase: Login fails due to invalid login credentials

I am currently running Hyperion System Planning 9, authenticating users through my LDAP server and am having a problem creating new users. I have gone through what I believe are the steps I need to take and have created my users but now when they try to login to EssBase, through the excel add-in, I get this message: "Login fails due to invalid login credentials"
I have searched the forums and the Essbase knowledge base and have come up empty. The only thing I have found is this:
"You just need to provision your shared services user with access to Essbase. Right-click on your user, select provision and then give them the required Essbase rights."
I have provisioned my users several times and made sure that they are added to the correct groups but they still can't log in.
Has anyone had this issue before?
Thanks,
J

Another point that you need verify, the service sequence:
1. Start the analytic Services
2. Star analytic Administration services.
regards,
Wallace

Authentication - "Invalid Login Credentials" ? ? ?

Hey guys,
Need some help regarding Log in.
I have a table in the database (table name USER_SECURITY) which has the list of users who are authorized to log in to the application.
I have to incorporate this in the application page
Could you please help me with the logic how to go about it in APEX
Thank You for your help and suggestions
Jesh

Hi,
I did try the link and it helped me understand alot, [ http://djmein.blogspot.com/2007/07/custom-authentication-authorisation.html]
and I tried an example as mentioned in Duncan Mein's Blog and it did work, but then when I try to use it in my application and entered the username and password it says *"Invalid Login Credentials".*
Here's the code I used:
The table was already created in the database: ASQ_USER_SECURITY
has four columns: USER_ID, USER_ROLE, USER_NAME, PASSWORD
Created an Application Security Package
CREATE OR REPLACE PACKAGE app_security_pkg
AS
PROCEDURE add_user
p_user_id IN VARCHAR2,
p_user_role IN VARCHAR2,
p_username IN VARCHAR2,
p_password IN VARCHAR2
PROCEDURE login
p_uname IN VARCHAR2
,p_password IN VARCHAR2
,p_session_id IN VARCHAR2
,p_flow_page IN VARCHAR2
FUNCTION get_hash
p_username IN VARCHAR2
,p_password IN VARCHAR2
RETURN VARCHAR2;
PROCEDURE valid_user2
p_username IN VARCHAR2
,p_password IN VARCHAR2
FUNCTION valid_user
p_username IN VARCHAR2
,p_password IN VARCHAR2
RETURN BOOLEAN;
END app_security_pkg;
CREATE PACKAGE BODY
CREATE OR REPLACE PACKAGE BODY app_security_pkg
AS
PROCEDURE login
p_uname IN VARCHAR2
,p_password IN VARCHAR2
,p_session_id IN VARCHAR2
,p_flow_page IN VARCHAR2
IS
lv_goto_page NUMBER DEFAULT 1;
BEGIN
IF UPPER(p_uname) = 'ADMIN'
THEN
lv_goto_page := 1;
ELSE
lv_goto_page := 1;
END IF;
wwv_flow_custom_auth_std.login
p_uname => p_uname,
p_password => p_password,
p_session_id => p_session_id,
p_flow_page => p_flow_page || ':' || lv_goto_page
EXCEPTION
WHEN OTHERS
THEN
RAISE;
END login;
PROCEDURE add_user
p_user_id IN VARCHAR2,
p_user_role IN VARCHAR2,
p_username IN VARCHAR2,
p_password IN VARCHAR2
AS
BEGIN
INSERT INTO app_users (USER_ID,USER_ROLE,USER_NAME, PASSWORD)
VALUES (p_user_id,p_user_role,UPPER (p_username),
get_hash (TRIM (p_username), p_password));
COMMIT;
EXCEPTION
WHEN OTHERS
THEN
ROLLBACK;
RAISE;
END add_user;
FUNCTION get_hash (p_username IN VARCHAR2, p_password IN VARCHAR2)
RETURN VARCHAR2
AS
BEGIN
RETURN DBMS_OBFUSCATION_TOOLKIT.md5 (
input_string => UPPER (p_username)
|| '/'
|| UPPER (p_password));
END get_hash;
PROCEDURE valid_user2 (p_username IN VARCHAR2, p_password IN VARCHAR2)
AS
v_dummy VARCHAR2 (1);
BEGIN
SELECT '1'
INTO v_dummy
FROM ASQ_USER_SECURITY
WHERE UPPER (USER_NAME) = UPPER (p_username)
AND PASSWORD = get_hash (p_username, p_password);
EXCEPTION
WHEN NO_DATA_FOUND
THEN raise_application_error (-20000, 'Invalid username / password.');
END valid_user2;
FUNCTION valid_user (p_username IN VARCHAR2, p_password IN VARCHAR2)
RETURN BOOLEAN
AS
BEGIN
valid_user2 (UPPER (p_username), p_password);
RETURN TRUE;
EXCEPTION
WHEN OTHERS
THEN RETURN FALSE;
END valid_user;
END app_security_pkg;
When I tried to Create a Test User it worked and added a record in the database
exec app_security_pkg.add_user ('RS','E','jesh','goodone')
Create your own Authentication Scheme
Authentication Function Section: RETURN APP_SECURITY_PKG.valid_user
Switch on your Custom Scheme: made it “My Auth Scheme”
Also Altered the Login Process on Page 101
app_security_pkg.login (P_UNAME => :P101_USERNAME, P_PASSWORD => :P101_PASSWORD, P_SESSION_ID => v('APP_SESSION'), P_FLOW_PAGE => :APP_ID );
This is pretty much what was there in the Duncan Mein's Blog
Thank you for having a look at the code
Appreciate your help
Jesh

Note 1054131 - Invalid DB objects after upgrade

HI,
We performed a migration from SAP 4.6C/Oracle9i.solaris to SAP 4.6C/Oracle10g/HPUX.
Now we need to upgrade SAP4.6C/Oracle10g/HPUX to ECC6.0.
As a prerequisite, I have checked the note
Note 1054131 - Invalid DB objects after upgrade
And I ran the script
SQL> SELECT OWNER, OBJECT_NAME, OBJECT_TYPE FROM DBA_OBJECTS
2 WHERE STATUS='INVALID'
3 AND
4 OWNER='SYS';
OWNER
OBJECT_NAME
OBJECT_TYPE         STATUS
SYS
DBMS_REPCAT_FLA
PACKAGE BODY        INVALID
SYS
DBMS_REPCAT_MAS
PACKAGE BODY        INVALID
OWNER
OBJECT_NAME
OBJECT_TYPE         STATUS
SYS
DBMS_REPCAT_UTL2
PACKAGE BODY        INVALID
SYS
DBMS_REDEFINITION
OWNER
OBJECT_NAME
OBJECT_TYPE         STATUS
PACKAGE BODY        INVALID
All the invalid objects are package body, can anyone help me how to proceed with this, can I proceed my upgrade to ECC 6.0 or do I need to delete the package body.
If I want to delete the package body,can you pl give me the commands and also post which whether I need to execute any steps
Pl help
Thanks
Senthil

Hi,
I guess you are talking about the Oracle Upgrade and not ECC Upgrade, as following are the pre-requisites for an ECC upgrade.
Making Database-Specific Preparations for Oracle
1. Check the value of parameter shared_pool_size:
4 Preparation
Making Preparations at the Database Level
Oracle 9.2: Check the value in file $ORACLE_HOME/dbs/init<SID>.ora.
Oracle 10.1 and higher:
select NAME, VALUE from v$parameter where name=shared_pool_size;
select NAME, VALUE from v$parameter where name=shared_pool_reserved_size;
If the value is lower than 150 MB, increase it to at least 150 MB (400 MB is better), and restart the
database.
2. Log on as user <sapsid>adm at the operating system level.
3. Log on to the database as the Oracle user system with sqlplus
4. Check the resource quotas of the database user SAPR3 or SAP<SAPSID>:
Oracle error 1536 can occur during the upgrade if the resource quotas of database user SAPR3
orSAP<SAPSID> are limited. Make sure that these quotas are unlimited. Check whether the table
DBA_SYS_PRIVS contains one of the following entries:
grantee=SAPR3/SAP<SAPSID>,privilege=UNLIMITED TABLESPACE,adm=YES
grantee=SAPR3/SAP<SAPSID>,privilege=UNLIMITED TABLESPACE,adm=NO
To do this, enter the following SQLPLUS statement:
select * from dba_sys_privs where grantee = SAPR3/SAP<SAPSID>;
If this entry does not exist, enter the SQLPLUS statement:
grant unlimited tablespace to sapr3/SAP<SAPSID>;
5. Log off from the database with the command quit.
6. Only if using the dictionary managed tablespaces function:
Make sure that the storage parameters MAXEXTENTS and NEXT have the correct values for certain tables and indexes. Otherwise, they may overflow during the upgrade. The Oracle-specific upgrade SAP Note contains the tables and the required minimum values.You can display the current settings with BRSPACE. The index names are not constant. However, you can also determine these names with BRSPACE. SAP Note 11777 describes how to change the parameters NEXT and MAXEXTENTS.
7. Only valid for: SAP R/3 3.1I
Make sure that parameter OPTIMIZER_MODE is set to OPTIMIZER_MODE=RULE.
For Oracle 9.2, check and, if necessary, edit the following Oracle profile:
$ORACLE_HOME/dbs/init<SAPSID>.ora
For Oracle 10.1. and higher, use the following statements:
Sqlplus /nolog
Connect /as sysdba
Alter system set OPTIMIZER_MODE=RULE scope=spfile;
8. Only if you do not switch off archiving during the upgrade:
If you want to leave brarchive running during the upgrade to avoid archiver stuck situations (brarchive -f ...), proceed as follows:
a) Create a temporary copy of brarchive:
4 Preparation
4.23 Making Preparations at the SAP System Level
cp /usr/sap/<SAPSID>/SYS/exe/run/brarchive /tmp
b) Start brarchive as user ora<sapsid> from the temporary directory /tmp/brarchive -f ...
c) After the upgrade, delete the copy of brarchive.
This procedure avoids upgrade errors caused by the program files being overwritten during the upgrade.
9. If your database version is already higher than the minimum version for the new release, we recommend that you exchange the DBA tools (such as BRSPACE) for the upgrade. The Database Software Oracle DVD for the database contains the up-to-date tools that you unpacked on the current kernel when you migrated the database. After you execute PREPARE, unpack this archive again into the exe subdirectory of the upgrade directory. This overwrites the DBA tools optimized for the minimum required database version with the tools best suited to your database version.
And if you are talking about an Oracle Upgrade then you just need these to compare once you have upgraded to 10g.
3.9 Checking for Invalid Database Objects
This optional step lets you check if there are any invalid database objects before the database upgrade to Oracle database 10g starts. After the upgrade it helps you distinguish database objects that have become invalid due to the upgrade process from those that were already invalid to start with.
Procedure
1. Execute the following commands:
SQL> spool invalid_objects
SQL> select unique object_name, object_type, owner from dba_objects where status
= 'INVALID';
SQL> @?/rdbms/admin/utlrp.sql
SQL> select unique object_name, object_type, owner from dba_objects where status
= 'INVALID';
SQL> spool off
A list of invalid objects before the upgrade is now generated.
2. Check the list of invalid objects after the upgrade.
If any objects in the list from before the upgrade are also in the list of invalid objects after the upgrade, you can be sure that this is not due to the upgrade process.
Regards,
Suhas

Invalid login credentials when install oracle xe

Hi friends,
I installed oracle xe version 10.2.0.1.0 correctly, but when i tried to login to adminstration via
http://localhost:8080/apex
with sys or system and the password (which i have given during the /etc/init.d/oracle-xe configure)
It says invalid login credentials
Please Help me out
Thanks

Had same login credentials problem today (and pwd was spelt as it always is). No way was I getting in via frontend or SqlPlus or using any online tip.
Deinstalled and reinstalled several times according to instructions. Note that ¨/etc/init.d/oracle-xe configure¨ doesn´t re-run unless you update ¨/etc/default/oracle-xe¨ file with ¨CONFIGURE_RUN=false¨
Now I am into a whole host of connection problems and the database service does not start. Any ideas?
Listener status:
root@II-laptop1:/usr/lib/oracle/xe/app/oracle/product/10.2.0/server# lsnrctl status
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 22-AUG-2007 17:06:11
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 22-AUG-2007 16:53:34
Uptime 0 days 0 hr. 12 min. 36 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Default Service XE
Listener Parameter File /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/network/admin/listener.ora
Listener Log File /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=II-laptop1)(PORT=1521)))
The listener supports no services
The command completed successfully
Listener logfile:
Started with pid=8156
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=II-laptop1)(PORT=1521)))
Listener completed notification to CRS on start
TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
22-AUG-2007 16:23:12 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=II-laptop1)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=169869568)) * status * 0
22-AUG-2007 16:28:51 * (CONNECT_DATA=(SID=XE)(CID=(PROGRAM=sqlplus)(HOST=II-laptop1)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=59109)) * establish * XE * 12505
TNS-12505: TNS:listener does not currently know of SID given in connect descriptor
22-AUG-2007 16:37:51 * ping * 0
22-AUG-2007 16:38:16 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=II-laptop1)(USER=oracle))(COMMAND=services)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=169869568)) * services * 0
listener.ora:
LISTENER =
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
# SID_LIST_<lsnr>
# List of services the listener knows about and can connect
# clients to. There is no default. See the Net8 Administrator's
# Guide for more information.
SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(SID_NAME=PLSExtProc)
(ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server)
(PROGRAM = extproc)
DEFAULT_SERVICE_LISTENER = (XE)
tnsnames.ora:
XE= (DESCRIPTION =
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=tcp)
(HOST=127.0.0.1)
(PORT=1521)))
(CONNECT_DATA=
(SID=XE)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
Any help would be greatly appreciated, thanks.

Invalid Login Credentials -- urgent

Hi Everyone,
I was in my application. I wanted to change the my user name instead of long big one. I went to Mange Application Express User from Home page. I have changed my user name (i have changed to same as my workspace name). Now I am trying to login but it giving me following error:
"Invalid Login Credentials"
Now I can't use my old user name.
Please help me. How can I use it?
BA

All sorted. Do not worry.

Cannot connect to olap service. Cannot connect to Essbase Server. Error:Essbase Error(1051293): Login fails due to invalid login credentials

Hello All,
I am getting following error, when trying to expand essbase from calculation manager, "Cannot connect to olap service. Cannot connect to Essbase Server. Error:Essbase Error(1051293): Login fails due to invalid login credentials",
I am using EPM 11.1.2.1
Thanks
Yash

If you have moved the server to a new data center and an issue has started occurring then it could point to the change.
Are you able to log into essbase directly with Maxl using the same account?
If you run a registry report do you see any of the configuration with IPs instead of DNS/hostname
Cheers
John
http://john-goodwin.blogspot.com/

Invalid Login Credentials

I am working on my application and can work on the pages but when I try and log in and run them I'm getting the "Invalid Login Credentials" message. It worked fine Friday and when I got to work this morning it wouldn't run. Any ideas? Help!

We are getting a blade in approx. two week which will be dedicated to Apex and I will be setting up the production environment. I'm curious about how to set up a development vs. production area and security issues as well. I think Craig and Ron will be here tomorrow and I'll broach the subject with them.

Login problem after upgrade to mavericks

Hi, i have login problem after upgrade from mountain lion to movericks in imac, I did enter the correct password But back to the login page again.

Hi cpuman8,
Thanks for visiting Apple Support Communities.
If you're not able to log in to your user account after upgrading, try resetting your password using the method in this article:
Resetting the original administrator account password
In OS X Lion or later, you can reset your user password with your Apple ID.
OS X: Changing or resetting an account password
http://support.apple.com/kb/ht1274
Best Regards,
Jeremy

Login Error after Upgrading from BW 3.5 to BI 7.0

Hi Experts,
We have carried out an upgrade from BW 3.5 to BI 7.0.
After Upgrade we are not able to login using SAP GUI. we are getting an error saying..
Username or Password not Valid..
During the upgrade (in Netweaver 2004s ) is there procedure necessary to be followed, which we could have missed..
Your response will be greatly appreciated.
Regards
LRaghunahth

Hi
Thanks a lot for your reponse.
Basically I am able to login thru sap* / ddic and can unlock the users / reset the password.
But the customer wants to know why the user is getting locked and it happened because of any procedure miss whil performing the upgrade..
if it is usual that users get locked during upgrade, any SAP Notes to refer..
Thanks a lot for helping in this community.
Best Regards
L Raghunahth

Invalid login credentials after upgrading to 3.0.1

Similar Messages

Maybe you are looking for