Cant install, "could not connect to module process"

Server
1

Steps to reproduce

  1. Install latest VirtualBox
  2. Import latest appliance Image
  3. start VM

Expected behaviour

I’d like to install.

Actual behaviour

After some loading i get the message “internal server error: could not connect to the module process”. I can click “ok” and nothing happens. I can reach the VM via a browser and get a login screen, but as far as i understand it, the password is set during installation, which does not start.

Server configuration

Operating system: Windows Server 2008 R2

ownCloud version: latest VirtualBox Appliance (DL 21.09.2018)

Updated from an older ownCloud or fresh install: fresh image

**Where did you install ownCloud from:**owncloud.org

Login as admin user into your ownCloud and access 
http://example.com/index.php/settings/integrity/failed 
paste the results into https://gist.github.com/ and puth the link here.
--> i cant login, i can not start the installation

edit: some more information … i searched for this error and someone wrote that switching to SCSI storage mmight help. Did change that in virtualbox, didnt change behaviour. The VM gets an ip, i can reach it via a browser.
I just installed a fresh VirtualBox and the latest appliance, which should work out-of-the-box …
I’d prefer having an appliance install for hyper-v, but i understood that hyper-v isnt supported anymore.

Anything i can try?

2

There is a easier way.

Download this.

https://updates.software-univention.de/download/images/UCS-Hyper-V-Image.zip

This is an UCS server, there is an app store, in this app store you can easily install the ownCloud app.

1 Like
3

The solutions is very simple. Go to UCS-OWNCLOUD VM “settings/display” and change VBox to VMSVGA. Save and start. After boot, the wizard appears.
I tested on Windows 10 64b + Vbox 6.1.12r +Univention-App-owncloud-virtualbox “production 10.3.1 2019/12/20”.

2 Likes