Jump to content


Photo

Importing default site: Failed! - Installation failed!


  • Please log in to reply
15 replies to this topic

#1 E. Mo Tite

E. Mo Tite

    Etomite Forum Newbie

  • Member
  • 13 posts

Posted 21 August 2004 - 01:34 PM

Hello,

Not sure if I should post this in the bugtracker but here goes...

I'm attempting to install Etomite v0.6 (RC2) over (RC1) and continue receiving the above message. The connection to the database goes smoothly before I receive the error message about importing the default site, and a lot of undecipherable code. :?

Here's a screen grab of what happens:
Posted Image

Can anyone show me where I'm going wrong? Would it have been a better idea to overwrite the files rather than run the installer?

Regards.

The full message reads:

"Etomite setup couldn't install the default site into the selected database. The last error to occur was You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 during the execution of SQL statement INSERT INTO `etomite_/export/"

#2 Guest_Alex_*

Guest_Alex_*
  • Guests

Posted 21 August 2004 - 03:05 PM

OK, I have no idea why it's showing what it is showing, but if don't need to install RC2, just upload the files over the old ones.

Read the last post in in this thread for more info: http://www.etomite.com/viewtopic.php?t=528&start=75

#3 breezer

breezer

    Likes Etomite Forums!

  • Member
  • PipPip
  • 308 posts

Posted 21 August 2004 - 03:52 PM

:?: I deleted this post since it was not relevent.

breezer

#4 Dean

Dean

    Loves Etomite Forums!

  • Admin
  • 4,790 posts

Posted 21 August 2004 - 03:57 PM

have you tried installing it into a database without the [ ] in? i notice from your screenshots that it is installing to a db that has them in it.....

just my .02 anyway
;)

#5 E. Mo Tite

E. Mo Tite

    Etomite Forum Newbie

  • Member
  • 13 posts

Posted 21 August 2004 - 07:49 PM

deanstev,

Yep, tried that. I removed the full name of the database using a graphics program.

#6 Dean

Dean

    Loves Etomite Forums!

  • Admin
  • 4,790 posts

Posted 21 August 2004 - 07:51 PM

deanstev,

Yep, tried that. I removed the full name of the database using a graphics program.


oh, ok.

have you tried a completely new (unused) db?

#7 E. Mo Tite

E. Mo Tite

    Etomite Forum Newbie

  • Member
  • 13 posts

Posted 21 August 2004 - 08:01 PM

yep, tried that too. :Cry: i've even tried reinstalling rc1 but the same problem occurs. i'll try to put up some screenshots...

#8 E. Mo Tite

E. Mo Tite

    Etomite Forum Newbie

  • Member
  • 13 posts

Posted 21 August 2004 - 08:58 PM

After attempting to reinstall rc2 again I received a similar message as before :( :

Posted Image

After deleting etomite and creating a new database I tried again and this seemed to have solved the problem :D :

Posted Image

But the following message appeared when I logged in :? :

Posted Image

I attempted logging in again using another browser and it stopped responding after the following screen was displayed :-x :

Posted Image

I might migrate back to v0.5 for the time being (if I'm able to!) as it's able to cope with a small project I'm working on which will go online shortly. So any thoughts, ideas, suggestions, hate-mail?? :?

#9 Guest_Alex_*

Guest_Alex_*
  • Guests

Posted 21 August 2004 - 09:54 PM

I have no idea...

There is something weird going on here. Are you running some sort of accelerator or something? It seems as if your MySQL setup is messed up. I also have no idea why it's outputting that pink debug info. That is certainly nothing in Etomite itself.

#10 E. Mo Tite

E. Mo Tite

    Etomite Forum Newbie

  • Member
  • 13 posts

Posted 21 August 2004 - 10:24 PM

I suspedted this mightn't be an Etomite problem. I'll do some investigating and fill you in when it's been sorted.

#11 Ralph

Ralph

    Loves Etomite Forums!

  • Admin
  • 6,539 posts

Posted 21 August 2004 - 10:29 PM

This might be a longshot, but you might want to try upgrading to the newest release of the Zend Optimizer... I've seen garbage similar to what you are displaying before... I'll talkning Zend Optimizer, not Zend Engine... Give it a try... http://www.zend.org/store/products/zend-optimizer.php

#12 E. Mo Tite

E. Mo Tite

    Etomite Forum Newbie

  • Member
  • 13 posts

Posted 23 August 2004 - 03:37 PM

Rad, I tried your solution but still no luck I'm afraid. :(

PS: I like the new look forum! B)

#13 E. Mo Tite

E. Mo Tite

    Etomite Forum Newbie

  • Member
  • 13 posts

Posted 25 August 2004 - 02:11 PM

Good news folks!

I've no idea what the problem was but everything is now in order and running smoothly -- fingers crossed! Thanks for your input!

#14 Guest_Jens_*

Guest_Jens_*
  • Guests

Posted 25 August 2004 - 04:14 PM

Remark to this error: When I installed etomite for the first time yesterday, I told the installer to use the database prepend "01_". This caused a failure reading the database. Obviously the database prepend must begin with a letter (char) instead of a number (integer) for what ever reason. I have only one MySQL database running on my host, which is the reason why I normally take a number for the database prepend. Maybe this explanation helps to figure out, what exactly the above descriped issue was.

#15 Guest_Alex_*

Guest_Alex_*
  • Guests

Posted 25 August 2004 - 05:10 PM

OK, thanks for the tip! I'll test it, to see why it doesn't like numbers as prefix.

Remark to this error: When I installed etomite for the first time yesterday, I told the installer to use the database prepend "01_". This caused a failure reading the database. Obviously the database prepend must begin with a letter (char) instead of a number (integer) for what ever reason. I have only one MySQL database running on my host, which is the reason why I normally take a number for the database prepend. Maybe this explanation helps to figure out, what exactly the above descriped issue was.



#16 Ralph

Ralph

    Loves Etomite Forums!

  • Admin
  • 6,539 posts

Posted 25 August 2004 - 05:45 PM

I believe that the problem you are referring to has to do with how MySQL indexes database tables, and is not a problem within Etomite... As I recall, yet couldn't locate in the manual when I just searched, MySQL doesn't like table names or prefixes that start with numbers... I seem to recall reading it somewhere, however... B)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users