Error when installing Open Atrium 2 using DAMP/WAMP [#2573871]

Hi,

I'm new to Drupal and Open Atrium. I need to install and configure Open Atrium 2 for the company I work for, but I can't install it, because I get the following error about 45 percent into the profile instalation, after selecting standard insltal instead of the quick one:

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://ccrintranet.dd:8083/install.php?profile=openatrium&locale=en&db_i... StatusText: OK ResponseText: Fatal error: Call to undefined function ctools_export_load_object_reset() in D:\CCRintranet\profiles\openatrium\modules\contrib\breakpoints\breakpoints.module on line 484

I have downloaded Open Atrium 2 from: https://www.drupal.org/project/openatrium
and DAMP from: http://www.acquia.com/downloads

I have used the default setting in DAMP, meaning PHP version 5.5.27.

I have installed DAMP also on another PC and imported the Open Atrium 2 folder, and I got the same error. I also downloaded the Open Atrium 2 installation directly through DAMP and got the same error. Any ideas how I can resolve this issue? Thanks!

Comment	File	Size	Author
#35	OA_2.45_Fedora_22_Server_installation_instructions_English.pdf	83.22 KB	dpoletto
#29	openatrium250.jpg	87.87 KB	alexandru2882
#27	Screenshot 2015-11-04 16.10.32.jpg	33.58 KB	alexandru2882
#16	openatrium-quickinstall2.jpg	249.09 KB	alexandru2882
#16	openatrium-quickinstall.jpg	95.95 KB	alexandru2882
#15	radix.jpg	137.94 KB	alexandru2882
	open-atrium-2-error.jpg	49.58 KB	alexandru2882

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

24 September 2015 at 08:55

alexandru2882 created an issue. See original summary.

Comment #2

alexandru2882 CreditAttribution: alexandru2882 commented 25 September 2015 at 07:43

I also installed WAMP on my computer:

APACHE 2.4.9
PHP 5.5.12
mySQL 5.6.17

And during the Install profile step I get the following error:

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://localhost/install.php?profile=openatrium&locale=ro&db_import_file... StatusText: OK ResponseText: ( ! ) Fatal error: Call to undefined function ctools_export_load_object_reset() in C:\wamp\www\profiles\openatrium\modules\contrib\breakpoints\breakpoints.module on line 484 Call Stack #TimeMemoryFunctionLocation 10.0002248632{main}( )..\install.php:0 20.0017608808install_drupal( )..\install.php:26 30.17687774376install_run_tasks( )..\install.core.inc:77 46.476630542120install_run_task( )..\install.core.inc:339 56.477130627488_batch_page( )..\install.core.inc:450 66.477330648168_batch_do( )..\batch.inc:80 76.477330648408_batch_process( )..\batch.inc:161 86.478130737792call_user_func_array:{C:\wamp\www\includes\batch.inc:284} ( )..\batch.inc:284 96.478230737864_install_module_batch( )..\batch.inc:284 106.478230738656module_enable( )..\install.core.inc:1600 116.590735957664module_invoke( )..\module.inc:475 126.590735958000call_user_func_array:{C:\wamp\www\includes\module.inc:866} ( )..\module.inc:866 136.590735958344navbar_install( )..\module.inc:866 146.590735960408breakpoints_breakpoint_save( )..\navbar.install:24

Comment #3

alexandru2882 CreditAttribution: alexandru2882 commented 28 September 2015 at 12:55

Assigned:

alexandru2882

» Unassigned

Comment #4

alexandru2882 CreditAttribution: alexandru2882 commented 28 September 2015 at 12:56

Issue summary:

View changes

Comment #5

Argus CreditAttribution: Argus as a volunteer commented 30 September 2015 at 22:31

Component:	Code	» Miscellaneous
Category:	Bug report	» Support request
Priority:	Major	» Normal

Did you read Installing or Updating Open Atrium and it's child pages? And did you follow all (server) recommendations described there?

Comment #6

kunago CreditAttribution: kunago commented 1 October 2015 at 08:51

I did read all child pages and have the same problem mentioned. I am running WT-NMP with Nginx engine and PHP 5.6.13.

EDIT: Tried to raise memory_limit from 256M (required in the docs) to 512M and it was able to install with no issues. Maybe the latest update is more resouce hungry?

Comment #7

dpoletto CreditAttribution: dpoletto commented 1 October 2015 at 09:38

@kunago, that's interesting...but "...at least 256M" basically means "...strictly equal to or more than 256M" (so >= 256M)...maybe that (minimum) threshold value, among others threshold values suggested for PHP and MySQL/MariaDB/PostgreSQL databases in setting up the correct environment for Drupal, depends also on the underlying Server environment chosen (because various XMP stacks like DarwinXMP, WindowsXMP, LinuxXMP or IllumosXMP where Web Server component X could be Apache or nginx may behave differently on how allocated resources are then used by components).

Comment #8

alexandru2882 CreditAttribution: alexandru2882 commented 1 October 2015 at 12:47

First of all, I want to thank you for your reply.
After I read https://www.drupal.org/node/2169701 and its child pages, I installed DAMP or Acquia Dev Desktop2 and started modifying the settings. I clicked on “Acquia Dev Desktop” > “Preferences..” > “Config” and then “php5_6\php.ini > Edit” and changed the following settings:
max_execution_time = 300 seconds
memory_limit = 512M

and “mysql\my.cnf > Edit”
max_allowed_packet = 128M -in 3 places in this file
I also checked in PHP mode: “Apache module”. Then I restarted the server application.
I chose “Standard install” and got the same error: An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging…
Any thoughts? I also tried to install Open Atrium 2 again, yet on another computer, and got the same error.

Comment #9

mpotter CreditAttribution: mpotter commented 1 October 2015 at 13:15

Perhaps you can try just installing plain Drupal 7 first to debug any issues with that. Then you can ramp it up by trying to install the Panopoly distro. If that works then Open Atrium should also work.

Comment #10

alexandru2882 CreditAttribution: alexandru2882 commented 1 October 2015 at 13:27

After giving more thought to @kunago's solution I searched with Windows search all the PHP.INI files and changed in all of them memory_limit = 512M . It looks like Acquia Dev Desktop doesn't use the php.ini file that you can edit through its Preferences menu because IT WORKED! I'm going to have a drink in the honor of this issue being solved !

But I have another question. During the "Verify Apps support" part of the install I got the following error messages that filled my whole window:

Notice: Undefined index: oa_radix in drupal_theme_initialize() (line 100 of ...\Sites\devdesktop\openatrium-7.x-2.45-core\includes\theme.inc).

Notice: Trying to get property of non-object in _drupal_theme_initialize() (line 146 of ...\Sites\devdesktop\openatrium-7.x-2.45-core\includes\theme.inc).

The install finished anyway, but should I worry about some future errors when using Open Atrium 2?

Thank you again for your time!

Comment #11

mpotter CreditAttribution: mpotter commented 1 October 2015 at 13:38

Now that it's working, a good tip is to go to the Reports -> Status from the Admin menu and scroll down to the PHP section. There should be a link for PHP Info that you can click to show your PHP config. One of the things it will show is the file path to the actual php.ini file that is being used.

The error about oa_radix does sound like a problem. Now that you got the memory limit solved, you might want to remove your database and start over and select the quick install which skips the Apps support section.

Comment #12

Wolfflow CreditAttribution: Wolfflow as a volunteer and commented 2 October 2015 at 16:59

following - have similar issue but i'm first going to review the comments above and will report back in case.
I am installing Atrium on a Ubuntu 15.05 server with MariaDB.

Comment #13

Wolfflow CreditAttribution: Wolfflow as a volunteer and commented 2 October 2015 at 19:13

No way to install for testing purposes on a development server.
Suggestions above readed.

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://myserver.com/install.php?profile=openatrium&locale=en&db_import_filename=/var/www/atrium/profiles/openatrium/db/openatrium.mysql&quickstart=standard&id=1&op=do StatusText: OK ResponseText: Fatal error: Call to undefined function ctools_export_load_object_reset() in /var/www/myserver.com/profiles/openatrium/modules/contrib/breakpoints/breakpoints.module on line 484

I had a look around the code and have strongly the impression that if not direct registered on the Atrium Server there is no really chance to have this distribution on own amchine, am I wrong?

Comment #14

alexandru2882 CreditAttribution: alexandru2882 commented 5 October 2015 at 09:25

I tried to reinstall Open Atrium 2 in order to get rid of all the errors on 2 different computers, with windows 7 and 8.1, but I got a whole lot more errors, despite respecting the settings. So, in order to try something new, I uninstalled DAMP (Acquia Dev Desktop) and deleted its hard drive content, which was left behind from the uninstall. I also deleted its registry keys.
After that I performed a clean reinstall of DAMP, I edited the php.ini found in ...\DevDesktop\php5_6:

memory_limit = 768M
upload_max_filesize = 768M

I eddited ....\DevDesktop\mysql\my.cnf :

max_allowed_packet = 768M -in 3 places in this file

and I edited the file called .htaccess found in the root of ...\openatrium-7.x-2.45:

php_value upload_max_filesize 768M
php_value post_max_size 768M

I changed PHP mode to “Apache module” in the application“Acquia Dev Desktop” > “Preferences..” > “Config”.
I downloaded from https://www.acquia.com/downloads the "tar.gz" version of Open Atrium 7.x-2.45 and unzipped it and then imported it into DAMP (Acquia Dev Desktop).
The Open Atrium 2 reinstall was without errors. I selected “Standard installation” in the section “Choose installation method”. I didn't get any errors until I got to the “Install Apps” section where I got once again the ”oa_radix” error.

OK. I decided to reinstall Open Atrium and then skip the modules installation. So I opened PHP my admin, selected the Open Atrium’s database, dropped all the tables and proceeded to install it once again. This is the error I got when the standard installation reached 50%, at the “Module filter” part:

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://openatrium-7-x-2-45.dd:8083/install.php?profile=openatrium&locale... StatusText: OK ResponseText: Fatal error: Call to undefined function ctools_export_load_object_reset() in C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\profiles\openatrium\modules\contrib\breakpoints\breakpoints.module on line 484

It looks like I cannot install Open Atrium 2. I will uninstall everything once again, restart my computer and then start from scratch.

Comment #15

alexandru2882 CreditAttribution: alexandru2882 commented 5 October 2015 at 09:24

File	Size
radix.jpg	137.94 KB

I deleted from the DAMP application the folder with the Open Atrium installation and also its database. I imported a new folder and then proceeded with the standard installation. I skipped the "Install Apps" section, but in the end I still got this errors (I even uploaded a print screen):

Notice: Undefined index: oa_radix in drupal_theme_initialize() (line 100 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _drupal_theme_initialize() (line 146 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _theme_load_registry() (line 335 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _theme_load_registry() (line 319 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _theme_build_registry() (line 713 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _theme_build_registry() (line 713 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _theme_build_registry() (line 713 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _theme_save_registry() (line 343 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Undefined index: oa_radix in drupal_theme_initialize() (line 100 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _drupal_theme_initialize() (line 146 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Undefined index: oa_radix in drupal_theme_initialize() (line 100 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _drupal_theme_initialize() (line 146 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Undefined index: oa_radix in drupal_theme_initialize() (line 100 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _drupal_theme_initialize() (line 146 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Undefined index: oa_radix in drupal_theme_initialize() (line 100 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _drupal_theme_initialize() (line 146 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Undefined index: oa_radix in drupal_theme_initialize() (line 100 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _drupal_theme_initialize() (line 146 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Undefined index: oa_radix in drupal_theme_initialize() (line 100 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _drupal_theme_initialize() (line 146 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Undefined index: oa_radix in drupal_theme_initialize() (line 100 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _drupal_theme_initialize() (line 146 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Undefined index: oa_radix in drupal_theme_initialize() (line 100 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _drupal_theme_initialize() (line 146 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Undefined index: oa_radix in drupal_theme_initialize() (line 100 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).
Notice: Trying to get property of non-object in _drupal_theme_initialize() (line 146 of C:\Users\Alex\Sites\devdesktop\openatrium-7.x-2.45\includes\theme.inc).

Any ideas on why am I getting these errors? I will try to perform now a Quick install, hoping to get NONE :)

Comment #16

alexandru2882 CreditAttribution: alexandru2882 commented 5 October 2015 at 09:42

File	Size
openatrium-quickinstall.jpg	95.95 KB
openatrium-quickinstall2.jpg	249.09 KB

I tried a Quick install and it was really quick. But I got more problems:
1. The "Configure site" screen looks unstyled, like it lost the css file (I have attached a print screen).
2. I get more errors when the installation is complete (I have attached a print screen).
3. My Open Atrium site looks completely BLANK.

Comment #17

Wolfflow CreditAttribution: Wolfflow as a volunteer and commented 6 October 2015 at 21:16

I really feel with alexandru2882 and all of those you try to test "Open Source Software" for learning and at a comprehensive time get hand on their own projects. Many of the last developments on Distros like OpenAtrium and others become more complex and quite struggling with high setups. I am still continuing to succed as I did in the Past, with earlier Atrium releases to achieve a successfull installation, but I ma quite sure that without a deeper knowledge of the modulare Drupal System in order to filter out some really deep linked modules with Drupal Service Provider, without the possibility to disable on a reasonable drupal profile installation process such not desired modules that stay a really hard job.

But I'm confident that one Day someone that simpatize with my IMHO thoughts, maybe will help me to build a Jung Staff for provide forks from the wonderfull Drupal-Distro out there but putting an Eye to those who really want approach Drupal CSM and Framework getting the chance to simplify things.

Best Regards

Comment #18

dpoletto CreditAttribution: dpoletto commented 7 October 2015 at 06:36

@Wolfflow: interesting point of view.

Please let me add mine to your one: mine were *good* experiences in evaluating Open Atrium (so no rant here and maximum appreciation to Open Atrium Developers/Sponsor for their continuous work on sustaining the project, enhancing existing features/modules, developing new ones, fixing bugs and for the frequent support they provide to all OA's users).

My experiences: I installed/updated Open Atrium many times now (since at least 2.30 and up to 2.45) using mostly Fedora Server (21 and 22) as base OS (I've very particular tastes due to particular reasons!) following the suggested procedure/requirements and, each time, I was able to complete the Open Atrium installation procedure without hitting any blocking issue having it up and running (not customized) for production/testing purposes in about just half an hour <- a result that, IMHO, is quite good considering that, at least the first two times, I had to figure out (and also to document) how to correctly configure some parameters of MariaDB, Apache and PHP (well, in the end, maybe a little more than half an hour considering I also had to learn how to manage SELinux to avoid issues without simply disabling it *brute force*).

I understand that "the matter under dispute" here is the issue some of you are experiencing on installing Open Atrium on a (D)AMP platform and not on any other (L)AMP platform but, hope to use the correct phrasing, keep in mind that there are ways and means to install Open Atrium (or any other Drupal Distribution) as there are ways and means to select/install/configure the underlying OS (whichever you can use for AMP or similar software bundles). My 2 cents.

Comment #19

Wolfflow CreditAttribution: Wolfflow as a volunteer and commented 7 October 2015 at 07:23

-> dpoletto , thank you for your 2 cents. I was not directly ranting, maybe frustrated a bit that it's not easy to debug some big Distros like OpenAtrium is. No question ! OpenAtrium is a Drupal Platform who helped and helps 1000s or even more, of People in the World to follow developing projects etc etc. I beg pardon if my consideration have a bit touch in a bad manner.
Anyway will folllow up alexandru2882 case, maybe I can give him some clue where to put his hands on. By the way I know very much Unix/linux different AMP system environments Stacks or not. I last tryied on a Debian Server installing all parts by console and not in a default LAMP - WAMP - MAMP ready to use packages/Stacks.
It would be great if some out here would have a good tipp in what direction alexandru2882 and me could have to look at for gain to the right route. Thanks

Comment #20

Wolfflow CreditAttribution: Wolfflow as a volunteer and commented 7 October 2015 at 07:56

-> alexandru2882 maybe here you may find some good suggestions if you may try to install in a linux machine, which in my opinion would be best for you to test and get confident with OA -> Basic installation of OpenAtrium

good luck

Comment #21

alexandru2882 CreditAttribution: alexandru2882 commented 13 October 2015 at 11:10

Thanks for your responses. Unfortunately I haven't got the basic idea how to use Linux. I barely know how to install a Drupal instance. But regarding the errors I get, I strongly believe that the key resides in the settings I have to make in the server software. I have reinstalled (for the 20th time) Open Atrium and I got only the "radix" error. I am now learning how to use this software by following this easy tutorial I found: https://www.fastcomet.com/tutorials/open-atrium/ .

What I did to get rid of "An AJAX HTTP error occurred" was to give full reading and writing rights to the directory where Open Atrium is installed.

To do this in Windows 8.1 you have to follow these instructions: Right click on the Open Atrium directory, click on Properties. Then Security>Edit>Add..>Advanced>Find Now>search for Everyone and select it, than OK>OK>check Full control>OK>OK.

Right now, if you get "An AJAX HTTP error occurred", go to PHPmyadmin and drop all the tables in the Open Atrium database and install Open Atrium again. For me it worked the second time. I only got the "radix" error at the end of the installation. But the software works. I hope I won't get any more errors in the future because of this.

Comment #22

Wolfflow CreditAttribution: Wolfflow as a volunteer and commented 19 October 2015 at 00:08

@alexandru2882: thanks for replay, I will follow your suggestion and see if I will succede. will report back here soon.

Comment #23

alexandru2882 CreditAttribution: alexandru2882 commented 2 November 2015 at 17:31

A long time has passed from my last post.

I have tried installing Open Atrium 2.45 on a virtual Linux server (Cent OS) and failed miserably. I still get these errors. I have absolutely no way to install this software.

I am very sad to say that my only option in this moment is to give up!

Thanks for all your answers.

PS I installed Panopoly and I had no trouble with it. It installed correctly. But when it comes to Open Atrium, I can't get past the Ajax Error 200.

Comment #24

dpoletto CreditAttribution: dpoletto commented 2 November 2015 at 18:46

@alexandru2882: Don't give up!

If you want I can post an homemade step by step guide I wrote down to setup OA on a Fedora based LAMP server (note that Fedora 21/22 and 23 - this one available tomorrow November, 3 - are very similar to CentOS 7), a machine I then used to install and run OA 2.4x without particular issues so far.

Probably, with very minor specific adaptations (Fedora is quite cutting edge with respect to CentOS), such guide could be useful to figure out an install of OA also on CentOS 7.

Comment #25

alexandru2882 CreditAttribution: alexandru2882 commented 4 November 2015 at 08:33

Right now I tried installing Open Atrium version 2.50 rc1 and I got this ERROR in Standard instalation:

An AJAX HTTP request terminated abnormally. Debugging information follows. Path: http://127.0.0.1/openatrium-7.x-2.50-rc1/install.php?profile=openatrium&... StatusText: ResponseText: ReadyState: 4

I use Windows 8.1 and Easy PHP 4.1.

Comment #26

alexandru2882 CreditAttribution: alexandru2882 commented 4 November 2015 at 08:38

Thanks @dpoletto for your response. Unfortunately I asked a friend to install Cent OS for me on a virtual machine because I haven't got the basics of Linux. I can't do anything in it. Your guide might prove too hard for me.

But if you think that I'll manage with the installation on Fedora Linux and configure it to be a web server, than, let's give it a try! :)

Comment #27

alexandru2882 CreditAttribution: alexandru2882 commented 4 November 2015 at 14:12

File	Size
Screenshot 2015-11-04 16.10.32.jpg	33.58 KB

I read another thread regarding the new error I'm getting and @mpotter recommended to use Quick Install. I did this and after it finished I got the following error. Also the install looks like the attachment (with no graphics).

Error message

Warning: file_put_contents(temporary://filA916.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA917.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA918.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA929.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA92A.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA92B.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA92C.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA93C.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA94D.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA94E.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA94F.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA950.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA951.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA952.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.
Warning: file_put_contents(temporary://filA953.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 1936 of C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\data\localweb\openatrium-7.x-2.50-rc1\includes\file.inc).
The file could not be created.

Congratulations, you installed Open Atrium 2!

Comment #28

mpotter CreditAttribution: mpotter commented 4 November 2015 at 14:25

The errors in #27 mean that you do not have the correct permissions set for your /tmp file system. Please search for general information about how to install Drupal on a Windows server for help on that.

Comment #29

alexandru2882 CreditAttribution: alexandru2882 commented 17 December 2015 at 11:38

File	Size
openatrium250.jpg	87.87 KB

I have downloaded again Open Atrium version 2.50 and tried to install it on Windows 8.1 using Easy PHP 14.1. I changed all the settings for PHP and MySQL as recommended. First, the install froze at Install profile 100%. I had to delete the database and start again. I used only Quick install. The second time, my version of Open Atrium installed without a theme, as in the screenshot.

I don't think that it is possible to install Open Atrium on a PC.

Comment #30

alexandru2882 CreditAttribution: alexandru2882 commented 17 December 2015 at 11:43

I would also like to add that I learned how to set permissions in windows, so I've given full permissions to all Open Atrium installation directories and to all Easy PHP directories, where the tmp folder exists. So it is not a permissions problem after all.

Comment #31

alexandru2882 CreditAttribution: alexandru2882 commented 17 December 2015 at 11:46

Just for fun I have tried a standard installation of Open Atrium 2.50. I got this error message:

An AJAX HTTP request terminated abnormally. Debugging information follows. Path: http://127.0.0.1/openatrium-7.x-2.50/install.php?profile=openatrium&loca... StatusText: ResponseText: ReadyState: 4

Is this a bug? Who can help solve this issue?

Comment #32

dpoletto CreditAttribution: dpoletto commented 17 December 2015 at 11:49

Well...IMHO...it's more acceptable a statement in which you say that it's difficult to install Atrium on Microsoft Windows 8.1 operating system. If you want to play, using any Linux (Distribution) is the way to go...seriously. I still have the instructions I wrote down when I installed Atrium 2.45 on (Linux) Fedora Server 21 (basically also valid for Atrium 2.50 and Fedora 22 or 23).

Those errors ("The file could not be created") look like permission issues that pop up in your scenario.

Comment #33

advMT CreditAttribution: advMT commented 18 December 2015 at 10:12

Have the same error:
An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://portal/install.php?profile=openatrium&locale=en&id=1&op=do StatusText: OK ResponseText: Fatal error: Call to undefined function ctools_export_load_object_reset() in /var/www/html/portal/profiles/openatrium/modules/contrib/breakpoints/breakpoints.module on line 484

CentOS 7 + Apache/2.4.6 (CentOS) + Postgres(9.2.14) + PHP(5.4.16).

How to fix it?

Comment #34

advMT CreditAttribution: advMT commented 18 December 2015 at 12:50

If you want I can post an homemade step by step guide I wrote down to setup OA on a Fedora based LAMP server (note that Fedora 21/22 and 23 - this one available tomorrow November, 3 - are very similar to CentOS 7), a machine I then used to install and run OA 2.4x without particular issues so far.

Probably, with very minor specific adaptations (Fedora is quite cutting edge with respect to CentOS), such guide could be useful to figure out an install of OA also on CentOS 7.

Can you do this? Thank you.

Comment #35

dpoletto CreditAttribution: dpoletto commented 18 December 2015 at 13:31

File	Size
OA_2.45_Fedora_22_Server_installation_instructions_English.pdf	83.22 KB

@advMT, sure! Here we go. Please note that your mileage may vary consistently (you should also fix or verify that CleanURLs feature works as expected) with respect to what I've written for my personal use, take it cum grano salis (it's just an example and it could contain errors I ignore but it's better than nothing) and adapt to your specific scenario.

Comment #36

Argus CreditAttribution: Argus as a volunteer commented 18 December 2015 at 23:14

Could anyone change this issue into a how-to? (Title: How to install OA using DAMP)

Comment #37

alexandru2882 CreditAttribution: alexandru2882 commented 21 December 2015 at 19:58

I would like to mention that I have tried without success to install Open Atrium on Windows 7, Windows 8.1 and CentOS 7.

Comment #38

cirun CreditAttribution: cirun commented 2 January 2016 at 17:03

I experienced almost exactly what @alexandru2882 has experienced!

Is there anyone has successfully installed Open Atrium 2.5 on Windows platform? I am using windows 10 +WAMPServer 2.5. All the errors occurred during my installation process. Like:

1. Warning: file_put_contents(temporary://filA94D.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in
2. The Ajax issue
3. The blank page after installation.

I am almost driven crazy. ^_^ Shake Hands @alexandru2882.

Comment #39

raphael waeselynck CreditAttribution: raphael waeselynck commented 20 January 2016 at 17:29

Hello, same issue for me than original post. Standard install of the very last version of open atrium (openatrium-7.x-2.52) leads to a dead end with ajax error Fatal error: Call to undefined function ctools_export_load_object_reset()
Guess a module which just install calls this function while ctools module has not been installed yet.

Comment #40

dawnherald CreditAttribution: dawnherald commented 30 April 2016 at 04:17

Having the same issues trying to install Open Atrium on Dev Desktop 2.

1. Warning: file_put_contents(temporary://filA94D.tmp): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in
>>> several failed statements (line 1936 of C:\Users\...\includes\file.inc)

2. The Ajax issue
>>> not seen this yet

3. The blank page after installation.
>>> no css being used

It would save people wasting time if this is never intended to work on dev desktop for windows.

Since appears to work on linux installations, is it a case of setting up the dev desktop web server correctly?

I've looked at the guides for setting up drupal on windows, the directions are heavily outdated with no directions specific to DAMP or Open Atrium which it appears this is needed.

Unless it is actually impossible.

Comment #41

dawnherald CreditAttribution: dawnherald commented 30 April 2016 at 04:57

Is the issue specifically SSH2? Im having some trouble getting it installed. The only version readily installable for windows is 0.12 from here:
http://pecl.php.net/package/ssh2

The last update was 4 years ago.

Would be nice if there was a clear answer so some of us could avoid days chasing this now and in the future.

Comment #43

fo10 CreditAttribution: fo10 as a volunteer commented 9 May 2016 at 06:37

I managed to get OA2 working on a local windows 7 machine.

Using this answer here:
http://drupal.stackexchange.com/a/175242

here are the main steps I followed:

Installed/used WAMP (+ Updated all VC++ distributions as suggested in its initial install screens) - my previous Xampp setup did not seem to work but it may have been the VC++.
Updated the php/mysql values created the user, db, as suggested in the OA2 documentation
* I also needed to double the max_execution_time value in the php.ini (solves a timeout error that may appear)
Ran the standard drupal OA2 setup
Here's where it gets tricky: If/When the template breaks (the failed to open stream: error, -> as in @alexandru2882 screenshots here)
-> continue adding the info the installation requires and proceed normally.
The (unstyled) OA2 welcome screen should appear. Look at the menu on the left. Navigate to ..> Media > File System.
In the page that appears, replace the value under Temporary directory with sites/default/files - and save.

Everything should be working normally now.
hope this helps.

Comment #44

Argus CreditAttribution: Argus as a volunteer commented 9 May 2016 at 21:44

@fo10 Thanks for the detailed step by step info, you seem one of the first who managed to solve running OA on a Windows machine locally...

I just wanted to point to an alternative solution for local deployment, although still in beta: Kalabox. It works great for OA (through Pantheon), although I only tested it on a Mac, but it supports Windows (and Linux) as well.

Comment #45

IKN CreditAttribution: IKN commented 26 January 2017 at 19:37

Using https://ftp.drupal.org/files/projects/openatrium-7.x-2.612-core.tar.gz (Original post above was 7.x-2.45.)
Have tried several times on both Ubuntu 16.04 and 16.1 server and have always gotten the same error:
ResponseText: Error: Call to undefined function ctools_export_load_object_reset() in breakpoints_breakpoint_save() (line 484 ... /.../breakpoints.module). 1 year and 4 months after original post.

Comment #46

Argus CreditAttribution: Argus as a volunteer commented 14 February 2017 at 23:18

Title:

Error when installing Open Atrium 2 using DAMP

» Error when installing Open Atrium 2 using DAMP/WAMP

Meh. Don't try to install OA on your local machine. (Ab)Use the available options to test/deploy it: https://dashboard.pantheon.io/products/openatrium2/spinup

Comment #47

joseph.olstad

French

CreditAttribution: joseph.olstad commented 10 April 2018 at 01:59

Solution for standard installation is to upgrade the breakpoints module to the latest release. simply replacing the old version of breakpoints with the latest version (7.x-1.6 released march 2018) fixed the issue for me.

and for good measure, I upgraded the file_entity module to the latest release (it includes a performance improvement) (released yesterday april 8th 2018)