Help is requested to delete a database I have created in TYPO3 setup.
I have installed XAMPP in Ubuntu 16.04 and configured it correctly and it runs. Now I was in the process of configuring TYPO3 in XAMPP using this very good guide.
After creating the "typo3cms" database, the next stage asked for a user name and password. I think I was supposed to put in my Ubuntu username and password, but erroneously I put in a new username and password and got the error of not being able to connect to my database.
I tried to go back to the previous stage of creating a database, which I can't because it already exists. But then I cannot go forward anymore. I have no idea where the database resides so that I can delete it and recreate it. I have tried uninstalling typo3 and reinstalling it. I have tried to google the problem without success.
Short of purging xampp completely and starting from scratch, is there a way I can delete the typo3cms database I have created?
It sounds like you are so early in the install process that you can start over (by removing all files and doing the install from the beginning).
Alternatively you should be able to remove typo3conf/LocalConfiguration.php and make sure that FIRST_INSTALL exists in document root (this is an empty file used to indicate that TYPO3 is doing the first install, it gets removed after - and you can use touch FIRST_INSTALL in terminal to create the file). Or if you prefer a completely manual approach, manually edit the typo3conf/LocalConfiguration.php file to correct or remove the database credentials and then resume the install.
Related
I recently tried to create an FAQ Page with the TYPO3 extension jpfaq.
I did set up everything as it was described in the manual. But for some reason when i preview the page, it shows a bunch of different error. For example:
TYPO3\CMS\Extbase\Persistence\Generic\Storage\Exception\SqlErrorException
Table 'xxx_typo_dev.tx_jpfaq_domain_model_ttcontent' doesn't exist
When I "unbind" the FAQ database I created it shows me the correct FAQ page (just without the questions and answers). So there might be a problem with the database?
Cleared cache. Deleted and installed the extension again. Didn't help.
Sounds like the you need to fix the Database Structure.
Normally the Database Structure is fixed when you install new extensions in the Extensions module.
If you use Composer Mode the installation is done with composer and you need to fix it by hand.
This can be done in the InstallTool / Maintenance Module: Analyze Database Structure.
Or you use the commandline: vendor/helhum/typo3-console/typo3cms database:updateschema (don't forget to use composer require helhum/typo3-console)
I'm scared to ask this because people can be a little mean on here but I've watched 1000 of YouTube videos and went through just as many google searches. I was trying to create a data dictionary for mysql diagram. I used this website https://dataedo.com/kb/tools/mysql-workbench/how-to-export-data-dictionary#toc_0 to help me. I downloaded the .py link listed in the install plugin step. The followed the instructions in mysql. It said the plugin install was successful and to restart my workbench. After that I started getting the error shown in the picture. I have tried everything:
Restart workbench
Repair workbench through msi download
Followed the steps in this link: https://www.tutorialspoint.com/how-do-i-kill-all-the-processes-in-mysql-show-processlist
Updated all my sql products in mysql installer
Made sure mysql services were turned on and running
I don't know what else to do. I can't even open workbench to see if the plugin is the issue because again I can't get in. I just need some help
That is a strannge error, where mysql workbench has some corrupt files.
Deinstall MySQL Workbench with the MySQL Installer
Install Workbench again
So everything will start normal again, the configuration and connections will stay and can be used again as normal
This is not an installation issue, so don't waste your time by trying to fix this issue by repeating the installation.
The error comes from the approach where MySQL Workbench tries to ensure there's only one instance of it running. For that it searches the process list for another instance and, if one was found, sends the command line parameters it got to that instance, letting the already running instance handle them (and shuts itself down after that).
But again: this happens only if another instance is found, so check your process list carefully. Filter by the term "MySQL" to see any MySQL related processes (including that of a MySQL server). Shutdown/kill any of these processes and try launching WB again.
Same issue happened to me and it was like what the heck. Don't waste your time to uninstall and reinstall because it won't solve your problem.
Solution: open your file explorer and delete the entire folder "Workbench"
Path: %appdata%\MySQL\Workbench
I have the same issue with this file.
Just as Jr Relampagos says, delete the .py file here : AppData\Roaming\MySQL\Workbench\modules
Restart Workbench, it works for me.
With me I'm just go to C:\Users<USER>\AppData\Roaming\MySQL\Workbench\modules and then delete the .py file you install, then open the Workbench again
I fumbled around with an ancient T3 installation (tried an upgrade from 4.5 to 6.2) and before the fumbling created a backup from the entire directory on the webserver as well as the database.
Now I tried to re-activate that backup (a.k.a. 4.5). The install tool works fine, DB-Connection seems to be ok, but when I try to access the backend, it tries to access /typo3/sysext/install/Start/Install.php which isn't present at the described location.
I tried to delete all caches, emptied the typo3temp folder - nothing helps. It seems there's something stuck from the upgrade process, but I have no idea where.
Any ideas?
The Problem's solved. T3 6.2 uses the PHP Opcode Cache which can't be reset in the 4.5 install tool. Something must have been stuck there. I wrote a little PHP script that clears the cache and viola, it worked.
opcache_reset();
I am trying to upgrade the site from v 7.6 to v. 7.15.1.
I have done the upgrade on localhost which included updating the db.
Now I transferred my files from localhost o the test site and on there I am getting an error in log:
ERROR Umbraco.Core.UmbracoApplicationBase - An unhandled exception occurred
System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'umbracoUserLogin'.
and I can't login to the backoffice.
It seems to be looking for umbracoUserLogin on test while it doesn't exist yet because on test the db is not updated yet.
How to update the db on test in this case while the files have already been updated on localhost and transferred to test site?
I have done 2 umbraco upgrades recently; one is from 7.5.7 to 7.13.1 and the recent one is from 7.13.1 to 7.15.1.
During my upgrade; I have seen this problem and fix in this issue can help you for your problem(and I didn't see this problem again after doing the upgrade again, but this time checking all the auto changing files and accepting them one at a time-see details below for this) but coming back to your question; "What's the best way to upgrade from umbraco 7.6 to 7.15.1(including db upgrade)"; here are the steps that you should follow;
Create a backup for your project and your umbraco db before you start. If you are using Git, then things will be super easy for this.
Open up Nuget Package Manager for your Umbraco project and do the package upgrade using the Nuget Package Manger window or the consol. Search for UmbracoCms version 7.15.1 for your case.
Once you start doing the upgrade, you will see some popup windows that will ask you to approve some auto file changes(including some config files changes). As you don't want to lose some of your pre-upgrade settings, don't accept them all or discard them all, check all of them one by one, and as a general rule; if you don't have any custom changes for those files, then simply approve the change, otherwise, check your changes and make sure you don't loose anything and discard some of these file changes as a result.
Once you're done with your UmbracoCms upgrade(which will automatically do some dependency package upgrades), build your project, make sure all is looking good then go to your local project's umbraco back-office url, this will trigger the rest of the umbraco upgrade process and simply complete the upgrade steps by following the screens- at this point your umbraco db changes will be done automatically and it is possible that you might have some issues with some old corrupt cached files, if this happens, then simply delete App_Data/TEMP files and App_Data umbraco.config file and try again. If you see some other problems during the installation, check the logs(browser developer tools can be handy to understand the problems in this case), and fix them one at a time. It is possible that you don'T need some of your old web.config settings and they might cause some issues, simply comment out those lines and see if this will fix some of the issues.
Once you are done with you local upgrade, deploy your code to your testing environment, and go to the umbraco url of your test environment and follow the screens to complete the installation for your testing environment. If you see any problems, please check my notes for step 4 above.
Do your umbraco upgrade for other testing environments(QA, UAT, Training etc) and complete your umbraco upgrade tests. Once the tests are done, then you are ready to go live. After the live deployment, you will have to complete the umbraco upgrade one last time, but this time for the live system.
Always get your back-ups for each environment before you do the upgrade, so you will be ready to rollback your changes if things go wrong(which might happen as you're doing a big umbraco upgrade).
Final note; there are some good articles for this, please take a look to understand the process better. Good luck!
I'm trying to install mongo DB on my local machine with the installer from the official website. But I'm continuously getting this message, can someone help?
I've tried the solution provided here but didn't help.
I suggest doing the following:
Hit Win+R to open up you run.exe then inside of it enter services.msc to open up services. Try locating the service under the name of MongoDB Server and set the Startup Type manually to Automatic - [In addition to that, you could set the username and password manually. If you get a message saying the user was granted login as a service right, try hitting retry on the MSI dialog and see if it starts].
Important:
Don't forget to save and close everything (services.msc) before continuing.
Also very important, you should (must) check your .NET framework version and update it to version 4.5 and above. You could download a software like eg Driver Booster to update all of your drivers and additional components that are outdated.
I ran into the same issue. My problem was the installation location. I was trying to install under C:\MongoDB. I resolved it by installing in the default MongoDb location which is C:\Program Files\MongoDB.
For me this is usually an issue with the configuration file %ProgramFiles%\MongoDB\Server\x.x\bin\mongod.cfg
At some time there was an invalid option "snmp" enabled (only valid in enterprise version).
Nowadays, although the installer asks for directories for data and logs it doesn't ALWAYS seem to use these, but defaults to %MONGO_DATA_PATH% or %MONGO_LOG_PATH%, respectively. I don't know where these should be defined, but the server fails at accessing c:\data\db (which doesn't exist). So you have to correct the paths.
I also faced this kind of error. But I just change the Network service to Local system in Log On As tab.
Follow my step-by-step below to resolve it:
Press Win+R, type: services.msc, then looking for MongoDB Server (MongoDB)
Double click on MongoDB Server (MongoDB).
Then it will open properties tab. On that tab click on Log On
After that check two items i.e. Local System account and Allow service to interact with desktop
After that press Apply and OK button. That's it, cheers!!
Open command prompt and copy the following command:-
"C:\Program Files\MongoDB\Server\4.2\bin\mongo.exe"
NOTE: This Tricks is work on my Windows 8.1 PC.
Comment out string with mp: in configuration file: %ProgramFiles%\MongoDB\Server\x.x\bin\mongod.cfg
Like this:
...
#snmp:
#mp:
Click Windows+r, type lusemgr.msc , Go to Groups and double click Administrators, Click Add, Click Advanced and click Find Now. Double click in Network Service (in bottom list) and click OK.
It worked for me.
Installing in the other locations other than the windows directory caused me this error. Reinstalling the setup with the recommended method of "complete" fixed it.
The problem occurs if you have Windows version previous to Windows 10.
Install the following update before installing MongoDB. Click on the link below.
https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows
It worked for me.
The problem occurs if you have Windows version previous to Windows 7. Install the following update by going to below link you have to download
Windows6.1-KB2999226-x64.msu
#You have to download and install then go to servies.msu and start MongoDB server by Start also go into log on and set to #local machine
https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows