Administrator password was not updated in the database error in configuring ATG version 11.0.0 integrated with Endeca - atg

I'm facing an error while configuring the ATG 11.0.0 with Oracle DB and with Endeca 11.0.0.
Here is the error:
Importing ( 8 of 8 ) /CIM/tmp/import/switchingA-import4.xml:
/CommerceReferenceStore/Store/Storefront/data/storecontent.xml to /atg/store/
stores/StoreContentRepository
/CommerceReferenceStore/Store/KnowledgeBase/install/data/basic-urls.xml to /
atg/multisite/SiteRepository
...Success
Update:
administrator password (1 of 1). The administrator password was not
updated in the database. The update was bypassed. Please check the cim.log for
details
-------DATA IMPORT FAILED-------------------------------------------------------
enter [h]Help, [m]Main Menu, [q]Quit to exit
Make sure you have configured the connection details and created the schema.
1 of 8 data imports had errors. Please check D:\E2E\ATG\ATG11.0\CIM\log/
cim.log for more details.
*[D] Done - Mark Import as Done
[C] Continue
Please suggest a solution to this problem.
Thanks in Advance

It may be because the schema is corrupted..
Drop the production,CAT_A and CAT_B schemas and do the steps on

I had this problem too, such that I couldn't login to the dynamo admin servers on bcc and prod instances. I modified the unpacked ear file to start up with Admin.Reset, which resets it to admin/admin and it works.

Related

Accessing Admin on DB2 Dev on Mac

I installed the IBM DB2 Developer Community Edition a while ago and when I wanted to log in to the Data Server Manager I realised I forgot my pasword.
DB2 tells me to contact the OS administrator to reset the pw. I am the admin but I have idea whatsoever how to do this on a Mac.
Could anyone please help?
The Data Server Manager password is set when DSM is first set-up.
If you stop the DSM server
ibm-datasrvrmgr/bin/stop.sh
then run the setup again, you will be prompted to setup a password again
ibm-datasrvrmgr/setup.sh
https://www.ibm.com/support/knowledgecenter/en/SS5Q8A_2.1.x/com.ibm.datatools.dsweb.ots.installconfig.doc/topics/installing_quick.html

Mysql Workbench error 1142 "Error querying security information" on Data Export

yesterday I updated my Workbench to the latest version available, the 6.3.6 build 511 CE on Windows 10.
Now I'm trying to make a dump of a remote database via the "Data Export" feature, which has always worked.
But, as soon as I click the "Start Export" button, I get this error:
Unhandled exception: Error querying security information: Error
executing 'SELECT * FROM mysql.user WHERE user = '[username]' and
Host = '[host]' ORDER BY User, Host'
SELECT command denied to user '[username]'#'[host]' for table 'user'
SQL Error: 1142
I know that I don't have the permissions to read that table, but why is that needed to perform a data export?
I've tried to check the force option (Continue even if we get an sql-error) but it's still not working.
Is this a Workbench bug? Or is there any way to avoid this query?
I had this exact same issue. The solution provided in this thread (same as the_nuts answer) is to uninstall 6.3.6 and install 6.3.4 from the archived versions: https://downloads.mysql.com/archives/workbench/
Update as of 13th June 2016
This bug has now been fixed
Download 6.3.7 (or later if available) from here
Found, this is indeed a bug of the version 6.3.6:
MySQL Bugs: #79807: Workbench Data Export: Unhandled exception: Error querying security information
MySQL Workbench has the correct behavior. If you are using a user other than 'root' MySQL Workbench will display that alert. However, if you setup your access to the server and database as root you will not run into problems exporting/importing because you have the right access to do so.

xWiki 6.3. changing database (HSQL to PostgreSQL) and migrating data

I have an instance of xWiki 6.3 running on default database i.e. HSQL.
I need to move it to PostgreSQL database.
I have installed PostgreSQL and have followed following steps from documentation to point xWiki 6.3 to my new PostgreSQL database.
1 - Copied jdbc drivers at required path in xwiki
2 - In xwiki.cfg file, I have un-commented following two lines
xwiki.store.migration=1 (was already un-commented)
xwiki.store.migration.databases= all
3 - commented hsql related section in hibernate.cfg.xml and have un-commented and updated PostgreSQL related section with required information.
After that, once I start my xWiki 6.3 instance, it shows me a home page with Add Button. However none of the existing content is visible.
I can see that all the tables are moved to postgreSQL if I connect to Database.
Also, I am unable to login with the admin account that was working when the application was running on hsql.
Any idea if I am missing something ?
Regards,
I don't think your process will port any existing data (i.e. the rows, ather than the tables) from one database to the other, not least because your configuration will only know about one database at a time. I suggest you follow the guidelines to export your content as a XAR while configured for HSQL and then import it again once you've reconfigured for PostgreSQL.

Moving ejabberd default DB to MySQL shows authentication failure

I am trying to setup an ejabberd server on my Amazon EC2 Ubuntu instance.
With the default DB Provided by ejabberd, I can easily setup my connection. But I need to replace the mnesia DB with MySQL. I found some tutorials over the internet. From those tutorial I found out a solution. I will explain it as step by step.
I am using ejabberd 2.1.11. I made the following changes on ejabberd.cfg file
Commented the following line :
{auth_method, internal}
Uncommented this:
{auth_method, odbc}
Configured my MySQL DB
{odbc_server, {mysql, "localhost", "students", "root", ""}} // No Password set
Change mod_last to mod_last_odbc
Change mod_offline to mod_offline_odbc
Change mod_roster to mod_roster_odbc
Change mod_private to mod_private_odbc
Change mod_privacy to mod_privacy_odbc
Change mod_pubsub to mod_pubsub_odbc
Change mod_vcard to mod_vcard_odbc
Then I installed ejabberd-mysql driver from the following link
http://stefan-strigler.de/2009/01/14/ejabberd-mysql-drivers-for-debian-and-ubuntu/
After making all these changes I restarted my ejabberd server.
Then I tried to login to my ejabberd server. It shows me the login prompt.
After entering the credentials it takes a lot time and then displays authentication failed.
Any help on the topic is appreciated.
Let's dig into problem
Your setup is working that means your config file is fine. But then
Why does auth fails ?
What schema you have in your students database ?
If you have a proper schema installed then does the user present in ur db's users table?
Have you also updated conf/odbc.ini with proper mysql details.
Even if both the conditions meet then I'll advice you to set mysql password and try again.
Let me know if that helps or not.
Update :-
update your config with {loglevel, 5}
then hit the login and tail all the log files.
odbc.ini
1 [ejabberd]
2 Driver = MySQL
3 DATABASE = students
4 PWD =
5 SERVER = localhost
6 SOCKET = /tmp/mysql.sock
7 UID = root
One Major basic part that one can easily miss is that data which was previously stored in mnesia database will no longer will be available for your new configuration so again you have to create one admin user like this to access your admin account.
./ejabberdctl register admin "password"

add customer to parallel plesk

i have plesk 10.1.1 install in centos 5 when i want to add a customer i got this error
Error: system user update is failed: unable to create system user: usermng: PAM password change failed: 24, Failed preliminary check by password service
i searched manay times and i have no idea what to do
tnx
We got this fix and we wrote an article (in Spanish) with all the related info in http://www.hackingballz.com/articulos/104/1/Plesk-PAM-Error-system-user-update-is-failed-Unable-to-create-system-user/Page1.html
Basically, you should replace the passwd and the system-auth with the configuration that we publish and it will start working. Tested in 3 different servers with those errors and all are working properly.