Hello Ventuzians!
THE FORUMS ARE CLOSED!

Please join our discord server HERE!! << click me :D

We are shutting our Ventuz Forum, but don't worry, it will all be archived for you to search in if you have a query. From now on, please add all your comments, questions or observations into our Discord Server

Thanks for the great time - see you on discord!!
Dee, Karol, Daniel and the whoooole Product and Support team!

3.6 & 3.7 Installer

Please report bugs in this group. We will maybe populate a list of known bugs with a possibly modified description at a later time.

Moderator: Support

Post Reply
User avatar
Joe Styles
Posts: 82
Joined: 19 Jan 2012, 12:10
Location: UK
Contact:

3.6 & 3.7 Installer

Post by Joe Styles » 19 Jun 2012, 16:22

Hi,

Is anyone else having issues with the installer in regards to it complaining about not being able to access the "C:\Users\Public\Documents\Ventuz3\Projects"? We seem to have come across it alot with 3.6 and it is still happening with the latest 3.7 installer. The way we get around it is to rebot and it seems to work if it is the first thing you do on the machine. A little frustrating when you are updating several machines :oops:

I have attached the error.
Can it be fixed with the next installer?

Thanks!
Joe
Attachments
ventuz installer issue.png
Joe Styles
Kinetic Pixel

User avatar
Joe Styles
Posts: 82
Joined: 19 Jan 2012, 12:10
Location: UK
Contact:

Re: 3.6 & 3.7 Installer

Post by Joe Styles » 19 Jun 2012, 16:24

I also came across this error today which wasted me a lot of time as it was hidden behind the installer window.
Attachments
ventuz installer issue 2.png
Joe Styles
Kinetic Pixel

User avatar
Robert
Posts: 318
Joined: 21 Jan 2012, 09:25
Location: Toulouse - France
Contact:

Re: 3.6 & 3.7 Installer

Post by Robert » 19 Jun 2012, 21:55

Joe,

We have the same problem as your first one here with administrator rights.

@+

robert

User avatar
Karol
Posts: 640
Joined: 10 Jan 2012, 12:07

Re: 3.6 & 3.7 Installer

Post by Karol » 21 Jun 2012, 09:26

Hi Joe,

we encountered this problem here only occasionally. But it was not necessary to reboot - just restarting the installer helped.
I will issue a bug ticket for this. The problems are that his happens very rarely on our developer machines and the installer is a third-party component.

Cheers
Karol

Post Reply