Forums / Install & configuration / ez 3.5 Orc1 error instaling

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

ez 3.5 Orc1 error instaling

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
Jorge estévez	Tuesday 23 November 2004 4:27:01 pm All goes ok until: --------- The setup wizard was not able to complete the creation of your selected sites. The following errors were detected: EZSW-051Could not install addon package named contact_us EZSW-040Failed to initialize site package news If you think you have fixed the errors you can try and click the "Retry" button. In a second instalation I got a similar error (with package named NEWS) ---------- How can I fix the error if I do not know what error happened? I am using: Apache 1.3.28 PHP 4.3.6 Running on windows XP SP2 With 6 sites on production without any errors on instalation. Please help I want to get my hands on ez 3.5 as soon as possible, Waiting from 6 a.m. for the release :-) As described in the instalation requirements (PHP version 4.3.2 or later, with the pcre extension enabled.) Where is the pcre defined (in a windows XP enviroment)?? thanks! Diseño Web Cuba Web Design Cuba www.elfosdesign.com
Frederik Holljen	Wednesday 24 November 2004 12:39:45 am A few quick questions: Are you using the installer or the source distribution? Did you try the plain package? Are you sure your disk is not full?
Jorge estévez	Wednesday 24 November 2004 7:35:22 am Hi! Are you using the installer or the source distribution? Source distribution (unpacking the files, setting apaches configurations, etc, etc) Did you try the plain package? No I did not, I checked all the modules. Are you sure your disk is not full? I think 16G is enough. Please help, thanks! Diseño Web Cuba Web Design Cuba www.elfosdesign.com
Benjamin Erhart	Tuesday 25 January 2005 3:23:44 am Hi, i?m experiencing the same problems but on a slightly different system: ez 3.5 release Windows 2000 SP4 Apache 2.0.52 PHP 4.3.10 (running as module) MySQL 4.0.23 I allready played around with different versions of A/M/P but there is no change. I tried the ez installer and that one works properly, but I really would appreciate it to install it under my own system, because I don?t like the idea of having 2 installations of AMP on one system! Additionally I wonder how the installation will behave on a real web server when it comes to going live... I hope it won?t be a problem like this one! Because I really like Exponential and would be glad to sell solutions based on it to my customers, but if I can?t get it up and running this will be difficult! I would be very glad if someone has a solution for this! Thanks in advance, Benjamin
Frederik Holljen	Tuesday 25 January 2005 3:48:22 am Can you try with the plain package and see if you get the same problem?
Benjamin Erhart	Tuesday 25 January 2005 4:33:07 am Wow! Thank you for the quick answer! I tried it and this works. (Sorry I didn?t get this hint earlier in the text, I?m not so familier with ez terms yet..) But now it?s so - plain ... I wanted to create two sites - one "Corporate" and one "Shop" and don?t like the idea to do it from scratch. Will it be much more work to start from "plain", or is there any workaround to get that going? I?m sounding really newbie, am I? :-) With kind regards, Benjamin
Frederik Holljen	Tuesday 25 January 2005 4:42:42 am Personally I would reccomend using the plain (or even no package at all) when starting the production of a large site where you need to have controll over everything. For smaller projects where you don't need to know the system that well.. feel free to use the packages. The installer behavior you are experiencing is probably triggered by some combination of your AMP installation. You are saying that the installer works so what you can do is: exchange your the parts of your AMP with the versions provided by the installer. Continue with this process until you find out which part is causing the problem. If you send the resulting information to us in a bug report we would be very thankfull (and of course we may be able to resolve the issue).