This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Error 1730 you must be an administrator ....
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Jul 06, 2015
12:03 AM
Error 1730 you must be an administrator ....
Hello anyone , after I create install project for half year ago , It work great , I'm appreciate on it
But yesterday , after I login with normal-permission window , I cant update my application , it popup error 1730 you must be an administrator .........
but with admin-permission ,it still work great.
I try to edit permission that user on install folder to full-control but it don't work.
How can I solve it.
.
But yesterday , after I login with normal-permission window , I cant update my application , it popup error 1730 you must be an administrator .........
but with admin-permission ,it still work great.
I try to edit permission that user on install folder to full-control but it don't work.
How can I solve it.
.
(2) Replies
‎Jul 06, 2015
09:03 AM
Hi,
I think you are trying to perform a major upgrade with files in a per machine location.
If that is correct, then what you are seeing is expected. Most likely, you install that package as an admin and will require another admin to uninstall it during the major upgrade.
You will also need admin privileges to install to a per machine location.
I think you are trying to perform a major upgrade with files in a per machine location.
If that is correct, then what you are seeing is expected. Most likely, you install that package as an admin and will require another admin to uninstall it during the major upgrade.
You will also need admin privileges to install to a per machine location.
‎Jul 15, 2015
04:49 AM
kyi wrote:
Hi,
I think you are trying to perform a major upgrade with files in a per machine location.
If that is correct, then what you are seeing is expected. Most likely, you install that package as an admin and will require another admin to uninstall it during the major upgrade.
You will also need admin privileges to install to a per machine location.
Thank you for your replying.
But I don't understand as much as you reply.
Do limited version have some options that can config permission access?