Deployment Issue for crm.b2c ( Modified) Authorization Issue !!!!!!

Question

Hi
I have created modified version of crm.b2c ear file with ISA Build Tool & trying to deploy it through RemoteGui at Server after logging with default connection & usernam as
J2EE_ADMIN but here is problem i am getting while deployment.
Please help on this .
Thank you.
===========================================================================
Deployment started Sat May 13 17:27:41 GMT+05:30 2006
===========================================================================
Starting Deployment of crm.b2c_z_b2c
Aborted: development component 'crm.b2c_z_b2c'/'sap.com'/'SAP AG'/'400.200605131718':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [SAPCRM] with user name: [J2EE_ADMIN]     Check your login information.     Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: User not authorized.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment of crm.b2c_z_b2c finished with Error (Duration 26516 ms)

Answer 1

Hi John,
it's not quite that
I will provide more detail:
In fact, we are 3 server Essbase : development, acceptance and operational there are a lot the new version of Essbase 11.1.2.3.501.
The maxl treatment are launch since a other server : a treatment server that are a client maxl and ESSCMD in the same version.
Before that, I'm migrate all the application and database from all alder server Essbase to this new architecture Essbase.
All application and DATABASE (in BSO) was migrated by expot-import process, the all object (csc, rul, rep ...) was transfer by copy in each directories of database.
The test after migration are very  satisfying.
Now, we are on process of life on the Essbase server 11.1.2.3.501.
The back office of India used the usually process to developed the lot.
They take the source on SVN application (take the rule), deployed the rule on the development server, modify the rule and have this error.
This error not appear after migration with the same rule ...
I am skeptical
Tx to your help on this subject.