<p>The log file got me on my way after a tip from Brad Bell:</p>

<blockquote>
  <p>'CDbException' with message 'CDbCommand failed during the SQL statement: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'craft_assetfiles' already exists' in ...craft/app/framework/db/CDbCommand.php:358</p>
</blockquote>

<p>Removing the database and doing a fresh install solved the issue. </p>

CC BY-SA 3.0
2014-06-30T09:54:15.513Z
2014-07-15T00:23:19.280Z
2014-07-15T00:23:19.280Z
noregt
<p>I'm throwing out a wild guess only, but what happens if you temporarily remove the .htaccess file in the top level of the "craft" folder. It's contents (i.e. "deny from all") may be causing some problem. Could that be causing some files not to be found? </p>

CC BY-SA 3.0
2014-06-27T13:41:35.977Z
Thanks John, I'm afraid that won't help. Could it be that access rights interfere here (I've given 744 for the app folder and subfolders)? What is the typical setup for a shared hoster in that case?
noregt
CC BY-SA 3.0
2014-06-27T13:53:45.970Z
Just did a 777, no difference
noregt
CC BY-SA 3.0
2014-06-27T13:56:29.303Z
My next guess would be to remove the .htaccess file at the base of your "public" folder. Those "500" errors are typically caused by .htaccess problems in my experience.
John Morton
CC BY-SA 3.0
2014-06-27T14:14:30.680Z
Bit of a dumb question maybe, but how do I install craft without the htaccess? I can only start the install with htaccess and /admin
noregt
CC BY-SA 3.0
2014-06-27T14:17:32.703Z
To quick, it worked with index.php?p=admin/install. But still the same.
noregt
CC BY-SA 3.0
2014-06-28T04:51:01.800Z
you definitely do not want to remove the .htaccess file at base of your public folder, where index.php is. I see you understood to hard path it and use a query to try otherwise. What may be going wrong has to do with Craft's automatic 'pathinfo' logic (it's not pathinfo actually). I think you should pass this situation to Craft support. I'd batch up your log files in a zip to include with your report, since you're not to the point after install where Craft could do this automatically.
narration_sd
CC BY-SA 3.0
2014-06-27T13:22:39.447Z
2014-06-27T13:22:39.447Z
John Morton
<p>I've installed craft on some terrible hoster (I know, under force). Because of that I had to install craft in the public folder, next to the index.php file. I've set the path to ./craft and activated the .htaccess file. Now it will show the installation page, but halfway stops
with the attached errors.  </p>

<p>The odd thing is that it searches for /garnish-0.1.min.map in the site root, while it's in the app/resources etc folder?</p>

<p><img src="https://i.sstatic.net/1XEy0.jpg" alt="enter image description here">
<a href="https://i.sstatic.net/1XEy0.jpg" rel="nofollow noreferrer">(Click to enlarge)</a></p>

<p>EDIT: Placing the file garnish-0.1.min.map in the root removes the first error, apparently it's really looking for the files in that place?</p>

CC BY-SA 3.0
2014-06-27T16:00:52.723Z
Check the contents of your craft/storage/runtime/logs files for the actual underlying error that's causing the 500 Internal Server Error.  Either that or lick on the 500 request from your browser's console and check the response.
Brad Bell
CC BY-SA 3.0
2014-06-30T09:50:30.880Z
The log file got me on my way, it gave a warning that the database was already installed, apparently it freezes if that is the case.
noregt
<server><install><error-message>
Installation stops halfway. Files not found and internal server error 500
# Installation stops halfway. Files not found and internal server error 500

(Asked by: username_0 on 2014-06-27)

I've installed craft on some terrible hoster (I know, under force). Because of that I had to install craft in the public folder, next to the index.php file. I've set the path to ./craft and activated the .htaccess file. Now it will show the installation page, but halfway stops
with the attached errors.

The odd thing is that it searches for /garnish-0.1.min.map in the site root, while it's in the app/resources etc folder?

![enter image description here](https://i.sstatic.net/1XEy0.jpg)
[(Click to enlarge)](https://i.sstatic.net/1XEy0.jpg)

EDIT: Placing the file garnish-0.1.min.map in the root removes the first error, apparently it's really looking for the files in that place?

**Tags:** server, install, error-message

> **Comments:**
> **username_1**: Check the contents of your craft/storage/runtime/logs files for the actual underlying error that's causing the 500 Internal Server Error.  Either that or lick on the 500 request from your browser's console and check the response.  
> **username_0**: The log file got me on my way, it gave a warning that the database was already installed, apparently it freezes if that is the case.  

---

## 2 answers

### Answer by username_0 on 2014-06-30. Score: 4 | Accepted answer

The log file got me on my way after a tip from username_1:

> 'CDbException' with message 'CDbCommand failed during the SQL statement: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'craft\_assetfiles' already exists' in ...craft/app/framework/db/CDbCommand.php:358

Removing the database and doing a fresh install solved the issue.


---

### Answer by username_2 on 2014-06-27. Score: 1

I'm throwing out a wild guess only, but what happens if you temporarily remove the .htaccess file in the top level of the "craft" folder. It's contents (i.e. "deny from all") may be causing some problem. Could that be causing some files not to be found?

> **Comments:**
> **username_0**: Thanks John, I'm afraid that won't help. Could it be that access rights interfere here (I've given 744 for the app folder and subfolders)? What is the typical setup for a shared hoster in that case?  
> **username_0**: Just did a 777, no difference  
> **username_2**: My next guess would be to remove the .htaccess file at the base of your "public" folder. Those "500" errors are typically caused by .htaccess problems in my experience.  
> **username_0**: Bit of a dumb question maybe, but how do I install craft without the htaccess? I can only start the install with htaccess and /admin  
> **username_0**: To quick, it worked with index.php?p=admin/install. But still the same.  
> **username_3**: you definitely do not want to remove the .htaccess file at base of your public folder, where index.php is. I see you understood to hard path it and use a query to try otherwise. What may be going wrong has to do with Craft's automatic 'pathinfo' logic (it's not pathinfo actually). I think you should pass this situation to Craft support. I'd batch up your log files in a zip to include with your report, since you're not to the point after install where Craft could do this automatically.  

---

