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
I have attached the error.
Can it be fixed with the next installer?
Thanks!
Joe
Hello Ventuzians!
THE FORUMS ARE CLOSED!
Please join our discord server HERE!! << click me
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!
THE FORUMS ARE CLOSED!
Please join our discord server HERE!! << click me
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
Moderator: Support
- Joe Styles
- Posts: 82
- Joined: 19 Jan 2012, 12:10
- Location: UK
- Contact:
- Joe Styles
- Posts: 82
- Joined: 19 Jan 2012, 12:10
- Location: UK
- Contact:
Re: 3.6 & 3.7 Installer
I also came across this error today which wasted me a lot of time as it was hidden behind the installer window.
Joe Styles
Kinetic Pixel
Kinetic Pixel
Re: 3.6 & 3.7 Installer
Joe,
We have the same problem as your first one here with administrator rights.
@+
robert
We have the same problem as your first one here with administrator rights.
@+
robert
Re: 3.6 & 3.7 Installer
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
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