how to fix export mysql dump version error - mysql-workbench

i'm newbies of mysql workbench. i'm having this error when im trying
to export data,
( ERROR CHECKING MYSQLDUMP VERSION. error retrieving version
mysqldump.exe (exit 1)).
I already try to run administrator. and clearing the path in edit preference. but it doesnt work. please can you help me.

Related

My datagrip fails to load my postgres while downloading driver. How do I solve this?

Hi I'm trying to run postgres locally so that I could read the local postgres from
datagrip.
However, when I add postgres into my datagrip I ran into this problem.
So I tried to download driver files (I was expecting it would solve this problem)
Then it shows this.
I was stuck here and tried to figure out but I couldn't.
What should I do to solve this issue?
The last stage I was stuck is one step after when I hit 'set up http'
Can anyone help me on this?
DataGrip couldn’t download the driver, and details should have been recorded in idea.log. See where to find it: https://intellij-support.jetbrains.com/hc/en-us/articles/207241085-Locating-IDE-log-files

Error builtin:list-members on trying auto complete in mysql workbench

Till yesterday auto complete was working in mysql workbench. Today getting below error on trying auto complete(Ctrl+space).
Kindly help to resolve it if you have an idea.
I restarted MySQL Workbench and now its working fine.
It appears this is a known bug in MySQL workbench since 2018: bugs.mysql.com...
Others have had success from rolling back to version 6.3.10. The bug is still present in the current version 8.0.23.
Another potential solution is delete the .column_widths file in:
[username]\AppData\Roaming\MySQL\Workbench\cache
Ironically Mysql Workbench's .column_widths appear to be a sqlite version 3 file
I believe you corrupted your Workbench installation somehow, so the easiest way to fix that is to re-install the application.

typo3_console throws error Doctrine\DBAL\Driver\Mysqli\MysqliException - No such file

Update of TYPO3 6.2 to TYPO3 8.7.
After changing the sources i am able to start all update scripts in install tool as expected. But when i try to run them via typo3_console i get the following errors:
./typo3cms database:updateschema safe
[ Doctrine\DBAL\Exception\ConnectionException ]
An exception occured in driver: No such file or directory
caused by
[ Doctrine\DBAL\Driver\Mysqli\MysqliException ]
No such file or directory
installtool is working, no error there
environment without errors
flush cache in installtool works but ./typo3cms cache:flush ends up in the same error messages.
Any ideas?
Thanks!
The error was sitting in front of the screen.
I changed unintentionally the php version of cli from 7.2 to 7.0. typo3_console should work with 7.0 - it tests versions from 7.0 to 7.3 - so no error was thrown. But it doesn't: all errors are gone after switching to 7.2 back again.
Sorry for the noise ... perhaps it helps someone with the same problem.
This error might also occur if your TYPO3 instance is running in a container (e.g. ddev) but you are trying to run your command from the host of the container.
So in case of ddev you have to run ddev ssh before trying to run a console command.
As you might have guessed: This happened to me ;)
Are you changing the DB credentials based on the TYPO3_CONTEXT? then you need to set this also in CLI, e.g. using
TYPO3_CONTEXT=Production/Staging ./typo3cms <your command>

Error while creating extension in postgresql

I am using https://tada.github.io/pljava/install/install.html link to create pljava extension in postgresql.
Build is ok and there is no unsuccessful operation. However when i tried to create extension using the statement below:
create extension pljava;
It is giving me the error:
ERROR: java.text.ParseException: Excpected keyword 'SQLActions'
Internet gave me no result about this error. Any help is appreciated to solve this problem.
That is definitely unexpected. To begin to look for the cause, could you please run
pg_config --version --sharedir
and then also post the contents of
$SHAREDIR/extension/pljava.control
where $SHAREDIR is as reported by the pg_config command?
Have you ever had an earlier PL/Java version in use with this database?
Does postgresql.conf contain any settings of pljava.* or of dynamic_library_path?
Also, what's your operating system and version?
If you have a github account, you could open this as a PL/Java issue there.

Magento2 error: We're sorry, an error has occurred while generating this email

I am getting below error in magento 2 local system:
We're sorry, an error has occurred while generating this email.
It is not showing me the sample data installed in catalog. Please help me out to get solution of this problem.
Regards,
Rakesh Kumar
The first thing you need to do is go to your .htaccess file. Uncomment
SetEnv MAGE_MODE developer
The error message is 90% of the time misleading and most likely you have an xml parsing issue. Either way turning on the developer environment and clearing the cache will pull the error.
Without seeing your error log it'd be hard to give an exact diagnosis. Some users will say sendmail will fix this error but generally this is because the error is trying to be emailed to you and that is because you are not in the correct developing environment to debug the issue. This could be because you are in default or production mode which is not ideal for fixing issue.
The sendmail module is meant to allow a site to operate and if any issues do occur with the site then the developer can be notified and hopefully the error hasn't caused a full site rendering issue. This way a site can still operate unbeknown to users and the issue can be resolved by a qualified developer behind the scenes.
This error is quite misleading. In my case an error in MySql query was causing this.
You should enable developer mode the get the exact error.
php ./bin/magento deploy:mode:set developer
In My case issue get solved by giving permissions to directory pub/media/catalog/product/
Enable developer mode using command line php bin/magento deploy:mode:set developer
Clear cache using command line php bin/magento cache:flush
Reload the frontend page
After reloading the page the message will change to
Error filtering template: Unable to write file into directory \C:/xampp/htdocs/Magento/pub/media/catalog/product\cache\f073062f50e48eb0f0998593e568d857/m/b. Access forbidden.
Follow this link to fix Magento 2: Unable to write file into directory. Access forbidden
Clear cache
Reload the frontend page again
If you see another message after enabling developer mode you can search for it
In my case it was missing php-gd extension on my machine.
This was on my exception log (magento_root/var/log/exception.log):
main.CRITICAL: exception 'Exception' with message 'Required PHP extension 'gd' was not loaded.' in /var/www/html/magento2/vendor/magento/framework/Image/Adapter/Gd2.php:620
Solved by installing php-gd library on my Ubuntu machine with the following command:
sudo apt-get install php-gd
If you want to install for php5.6 then you may run:
sudo apt-get install php5.6-gd
This can be for any error occurred in the page. The notice is different. The notice is given when system tries to send error email to administrator and failed while in Production mode.
For actual error one should enable developer mode and enable display error in app/bootstrap.php and checking error logs. It can be any error like php or mysql.
ini_set('display_errors', 1);
Thanks
Please check your /var/log/exception.log
This is issue raised because your product does not upload. so check your database or upload your sample database again .Let me know what error in exception.log