I would like to run installer with no admin privileges.
But when i would like to run my created .exe file, this error message appears:
Unable to execute file in the temporary directory, Setup arborted.
Error 1260: This program is blocked by group policy. For more information, contact your system
administrator.
Is ist possible to fix this problem in the inno setup script?
Related
I used installShield LE 2015 to build my application's installer and is successful. The problem am having now is that there's a Ms access db file in the installation location which i need to restore from the main application, but when i try to restore it, i get an error "Access to the path "C:\Program Files (x86)\RC record system\RecordSystemDb.accdb" is denied. Please someone should tell me how to resolve this issue.
I'm trying to create a wcf service in a lab using vsts.
I have created a build definition that works using a msbuild task. It then uses robocopy to copy the relevant dlls to a remote directory inside a lab using the Publish Artifacts step.
However, I need the content to be created as a windows service, and started after it has been published. It seems like something is running since I see a created log file about 9 minutes after a successful publish, but i cannot see my service inside the services menu, or in IIS.
When I try to run a bat script (using the run script step) that does an sc create, I get an access denied error even though on the vsts build definition I have given the step permission to modify the environment.
This is the full error:
2018-05-17T13:00:13.7702615Z ##[section]Starting: Run script GloBill/InstallBackEnd.bat
2018-05-17T13:00:13.7705444Z ==============================================================================
2018-05-17T13:00:13.7705561Z Task : Batch Script
2018-05-17T13:00:13.7705655Z Description : Run a windows cmd or bat script and optionally allow it to change the environment
2018-05-17T13:00:13.7705748Z Version : 1.1.3
2018-05-17T13:00:13.7705824Z Author : Microsoft Corporation
2018-05-17T13:00:13.7705924Z Help : [More Information](https://go.microsoft.com/fwlink/?LinkID=613733)
2018-05-17T13:00:13.7706023Z ==============================================================================
2018-05-17T13:00:13.7775377Z ##[command]C:\agent\_work\1\s\GloBill\InstallBackEnd.bat
2018-05-17T13:00:13.8030595Z
2018-05-17T13:00:13.8031049Z C:\agent\_work\1\s>sc create GloBillBackEnd ../Services/GloBill.WS.exe
2018-05-17T13:00:13.8048684Z [SC] OpenSCManager FAILED 5:
2018-05-17T13:00:13.8048781Z
2018-05-17T13:00:13.8048901Z Access is denied.
2018-05-17T13:00:13.8048957Z
2018-05-17T13:00:13.8064609Z ##[error]Process completed with exit code 5.
2018-05-17T13:00:13.8073202Z ##[section]Finishing: Run script GloBill/InstallBackEnd.bat
I'm running out of ideas.
The problem was that I was trying to deploy a release from a hosted agent that resided on another machine.
I had to configure a new agent solely for deploying, then i had to tweak my installation script a little by adding the -executionpolicy bypass command.
Here is the new script:
(%1 is the file path)
Powershell.exe -executionpolicy bypass -File %1 -username Username -password ****** -exepath *exe* -serviceName *svcName*
I have an old VB 6 app that someone is trying to install. The user is trying to register Comctl32.ocx. The file is in C:\windows\system32. The user has Windows 10 Home. When trying to register using:
Regsvr32 c:\windows\system32\comctl32.ocx
The user gets the message:
The module "comctl32.ocx" failed to load. Make sure the binary is
stored at the specified path or debug it to check for problems with
the binary or dependent .DLL files. The specified module could not be
found.
Any ideas what the user can try?
See https://support.microsoft.com/en-us/kb/249873
Basically: You are trying to register from the wrong directory, 32 bit OCx must be in c:\windows\syswow64
Also make sure you execute that command from an elevated command prompt (Admin).
I am using the 7zip standalone .exe to unzip a file. I am using the Execute Process task for this. I have tested this over and over again on multiple machines and I know it works (at least in debug mode/visual studio). I have uploaded this package the server. I have created a job that calls said package from the Package Store. The package is not able to find the .exe no matter where I put it.
My first thought was to put the .exe on the C:\ drive, which failed. I have also failed in my attempts to place the .exe on a network location that the account the package is running under has full control over.
Basically, has anybody else had issues getting the Execute Process Task to find an executable when the package is uploaded to the server?
The error message is
Can't find 7za.exe in directory C:\7zip
I'll risk a downvote for being wrong, but I believe you have a permission issue.
You say it runs fine on other servers from BIDS, try it without BIDS. Call it from a command-line on a box that it works on.
dtexec.exe /file C:\HereComesTheUnzipper.dtsx
If that works, then repeat the step on the troublesome server. RDC into the box and try again
dtexec.exe /ser localhost /sq HereComesTheUnzipper
If that still works, then you are looking at an issue with the job. What account is the SQL Agent service running as? Is the SSIS job step running as a particular set of credentials? If so, is it a SQL Server login (which wouldn't map to anything on the physical box)? Regardless of what your answer is, the resolution will be to ensure the account has access to
7z.exe
whatever scratch area 7zip may use while unpacking files (I assume %temp%)
the output folder (C:\bin\7z.exe -e e:\data\MyThing.7z)
Per the subject... I made a Setup.exe with Inno Setup which is supposed to
install to "{pf}{#MyAppName}". It does so on Win XP and also Win 7 if I'm
logged in with admin rights, but if I try on Win 7 as a limited user, I get
this error message:
"Setup was unable to create the directory C:\Program Files\AppName".
What to do? I don't want (or need) the user to install as an admin.
If you want to install to %ProgramFiles%, you do need to install as an admin. Regular users don't have write access to %ProgramFiles% directory.
If installing to %ProgramFiles% is not a requirement, just let the user pick a destination directory, or install to {localappdata} instead of {pf}. {localappdata} is guaranteed to be writable for it's owner. It expands to something like C:\Users\<user name>\AppData\Local.
You can also install to {pf} if running as admin and to {localappdata} if running as restricted user; use IsAdminLoggedOn to decide.
If installing to %ProgramFiles% is a must, you have no choice but to run as admin.
For this to work correctly, make sure that your .iss file either does not define PrivilegesRequired option, or it's set to admin. Then, when an unprivileged user runs the installer, a UAC prompt will appear asking for credentials with enough access rights (unless UAC is disabled, in which case the only way to install is Run As).