I am running installer with /verysilent /suppressmessagebox /norestart for upgrading my application (Windows Service). In PrepareToInstall(), I have code in place to check and stop an already running instance of my service using net stop <ServiceName>. I do log the output generated by net stop and it shows that the service has indeed been stopped. However, at times, the installer prompts that :
Message box (Abort/Retry/Ignore):
Setup was unable to automatically close all applications. It is recommended that you close all applications using files that need to be updated by Setup before continuing.
Click Retry to try again, Ignore to proceed anyway, or Abort to cancel installation.
The logs show :
2017-05-10 23:47:38.851 Log opened. (Time zone: UTC-07:00)
2017-05-10 23:47:38.851 Setup version: Inno Setup version 5.5.9 (u)
2017-05-10 23:47:38.851 Original Setup EXE: C:\Windows\TEMP\installer.exe
2017-05-10 23:47:38.851 Setup command line: /SL5="$FD006E,3807712,131584,C:\Windows\TEMP\installer.exe" /verysilent /suppressmessagebox /norestart /log=C:\ProgramData\<ServiceName>\installer_2026493391.txt
2017-05-10 23:47:38.851 Windows version: 6.1.7601 SP1 (NT platform: Yes)
2017-05-10 23:47:38.851 64-bit Windows: Yes
2017-05-10 23:47:38.851 Processor architecture: x64
2017-05-10 23:47:38.851 User privileges: Administrative
2017-05-10 23:47:38.867 64-bit install mode: Yes
2017-05-10 23:47:38.867 Created temporary directory: C:\Windows\TEMP\is-OO761.tmp
.....
..... Some logs irrelevant to the issue at hand
.....
2017-05-10 23:47:39.148 Stopping <ServiceName> Service - begin
2017-05-10 23:47:39.148 Command : /S /C ""net" stop <ServiceName> > "C:\Windows\TEMP\is-OO761.tmp\~execwithresult.txt" 2>&1"
2017-05-10 23:47:39.257 Stopping <ServiceName> Service - done
2017-05-10 23:47:39.257 The <Service Display Name> service is stopping.
The <Service Display Name> service was stopped successfully.
2017-05-10 23:47:39.366 RestartManager found an application using one of our files: <Service Display Name>
2017-05-10 23:47:39.366 Can use RestartManager to avoid reboot? Yes (0)
2017-05-10 23:47:39.366 Starting the installation process.
2017-05-10 23:47:39.366 Shutting down applications using our files.
2017-05-10 23:47:39.382 Some applications could not be shut down.
2017-05-10 23:47:39.382 Message box (Abort/Retry/Ignore):
Setup was unable to automatically close all applications. It is recommended that you close all applications using files that need to be updated by Setup before continuing.
Click Retry to try again, Ignore to proceed anyway, or Abort to cancel installation.
There are 2 issues :
Why is message box displayed in /verysilent mode ? As per this fix, it should not be displayed in silent mode. As per documentation, I do see that :
/SILENT, /VERYSILENT
Instructs Setup to be silent or very silent. When Setup is silent the wizard and the background window are not displayed but the installation progress window is. When a setup is very silent this installation progress window is not displayed. Everything else is normal so for example error messages during installation are displayed and the startup prompt is (if you haven't disabled it with DisableStartupPrompt or the '/SP-' command line option explained above).
Why does RestartManager seem to still believe that the exe is running when it has already been stopped ? Has anyone else seen similar issues and is there a recommended way ? (say, add a 5 second pause after the net stop command)
It's /SUPPRESSMSGBOXES, not /SUPPRESSMESSAGEBOX.
It can be an antivirus or similar, what blocks the file. If you try to move/delete the binary immediately after net stop, does it succeed?
Related
I have a task to install Oracle 11g on a centOS 8 using VM (i'm new to linux / oracle).
I downloaded the Oracle files and unzipped them, then I tried to ./runInstaller but I get an error and this is the full terminal with error:
login as: admin
admin#192.168.163.129's password:
Activate the web console with: systemctl enable --now cockpit.socket
Last login: Thu May 21 09:26:48 2020 from 192.168.163.1
[admin#oracledb ~]$ cd Downloads
[admin#oracledb Downloads]$ cd database
[admin#oracledb database]$ ls
doc linux.x64_11gR2_database_1of2 response runInstaller stage
install linux.x64_11gR2_database_2of2 rpm sshsetup welcome.html
[admin#oracledb database]$ ./runInstaller
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 120 MB. Actual 2027 MB Passed
Checking swap space: must be greater than 150 MB. Actual 1759 MB Passed
Checking monitor: must be configured to display at least 256 colors
>>> Could not execute auto check for display colors using command /usr/bin/xdpyinfo. Check if the DISPLAY variable is set. Failed <<<<
Some requirement checks failed. You must fulfill these requirements before
continuing with the installation,
Continue? (y/n) [n] y
>>> Ignoring required pre-requisite failures. Continuing...
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2020-05-21_09-43-58AM. Please wait ...
DISPLAY not set. Please set the DISPLAY and try again.
Depending on the Unix Shell, you can use one of the following commands as examples to set the DISPLAY environment variable:
- For csh: % setenv DISPLAY 192.168.1.128:0.0
- For sh, ksh and bash: $ DISPLAY=192.168.1.128:0.0; export DISPLAY
Use the following command to see what shell is being used:
echo $SHELL
Use the following command to view the current DISPLAY environment variable setting:
echo $DISPLAY
- Make sure that client users are authorized to connect to the X Server.
To enable client users to access the X Server, open an xterm, dtterm or xconsole as the user that started the session and type the following command:
% xhost +
To test that the DISPLAY environment variable is set correctly, run a X11 based program that comes with the native operating system such as 'xclock':
% <full path to xclock.. see below>
If you are not able to run xclock successfully, please refer to your PC-X Server or OS vendor for further assistance.
Typical path for xclock: /usr/X11R6/bin/xclock
[admin#oracledb database]$
I am using putty and Xming but I still get this error.
Make sure your putty session is connecting with "x-11 port forwarding"
Be sure after you set this that you scroll back up to 'Session' and then 'save'
I was learning how to use the Microsoft Azure Tools for Visual Studio to develop an Azure cloud service at :"Getting Started with the Azure Tools for Visual Studio".
I successfully completed the following steps:
1. Install the Azure tools.
2. Create an Azure cloud service.
3rd step was build and debug the cloud service, where i was stuck.
While debugging i got an error "Failed to initialize Microsoft Azure Storage Emulator".
I did try various methods given on various websites to initialize the Storage Emulator, but none of them worked for me.
When I was trying the command WAStorageEmulator.exe init , i got an error "cannot create database".
Any help would be greatly appreciated.
Step 1 : Start your system in safe mode (Immediately after the computer is powered on or restarted tap the F8 key to enter safe mode).
Step 2 : In safe mode go the path C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator.
Step 3 : Search for WAStorageEmulator.exe - config file.
Step 4 : Edit WAStorageEmulator.exe with Notepad++ (any editor).
Step 5 : Change the port numbers as shown in the above snapshot.
(By default the port numbers will be 10000, 10001, 10002).
<services>
<service name="Blob" url="http://127.0.0.1:30000/"/>
<service name="Queue" url="http://127.0.0.1:30001/"/>
<service name="Table" url="http://127.0.0.1:30002/"/>
</services>
Step 6 : Save the file and restart your system in normal mode and run the program.
I hope this helps.
I had a similar problem and it sounds like one of the answers posted here:
This post talks about removing old mdf files so you can install again
This seems to be closer to what you are experiencing.
I hope this helps
Open MS Azure Command Prompt. Type (depending on your local db name):
SqlLocalDb stop projectv12
SqlLocalDb delete projectv12
Then go to
C:\Users(admin)\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances
and I deleted all instance in there. Then try re-install the Azure storage emulator. This worked for me.
A re-boot is not neccesary as per the accepted answer.
Open a Powershell window in admin mode.
Enter the following command: netstat -p tcp -ano | findstr :10000
That will tell you what process id is using the emulator designated port.
Use the Detail Tab in Task Manager detail to find the associated application for the process id. Often times this is something like bittorrent/utorrent.
Kill that process and you're done.
..
But if you absolutely must run the conflicting application while you develop then you can change the ports used by the emulator.
To change the ports used by the emulator, then in powershell:
chdir "C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator"
.\WAStorageEmulator stop
Then edit the config file as per the accepted answer and just save it.
C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\WAStorageEmulator.exe.config
You don't need to copy it anywhere. Then back into Powershell and :
.\WAStorageEmulator status
.\WAStorageEmulator start
Make sure you have SQL Server Express or SQL LocalDb installed. You should then be able to type
.\AzureStorageEmulator.exe init
Or, in this older case:
.\WAStorageEmulator.exe init
...and it should install the default database. Note I'm using the PowerShell syntax. If using the command prompt, it's minus the .\ portion.
It's not always a port conflict, contrary to what other posts may suggest.
You can download SQL Server Express editions here:
https://www.microsoft.com/en-us/sql-server/sql-server-editions-express
You should see something like this when you run the command:
PS C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator> .\AzureStorageEmulator.exe init
Windows Azure Storage Emulator 5.10.0.0 command line tool
Empty SQL Instance. Autodetecting SQL Instance to use.
Looking for a LocalDB Installation.
Probing SQL Instance: '(localdb)\MSSQLLocalDB'.
Caught exception while probing for SQL endpoint. Login failed for user 'somedomain\someguy'.
Number of SqlErrors Reported: 1
SqlError: System.Data.SqlClient.SqlError: Login failed for user 'somedomain\someguy'.
Could not find a LocalDB Installation.
Probing SQL Instance: 'localhost\SQLExpress'.
Found SQL Instance localhost\SQLExpress.
Creating database AzureStorageEmulatorDb510 on SQL instance 'localhost\SQLExpress'.
Granting database access to user somedomain\someguy.
Database access for user somedomain\someguy was granted.
Initialization successful. The storage emulator is now ready for use.
The storage emulator was successfully initialized and is ready to use.
PS C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>
The problem is with the “(localdb)\MSSQLLocalDB” SQL Service with Permissions.
The best option is using below commands,
Step 1: Go the path “C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator”
Step 2: Open PowerShell as Administrator,
Step 3: Run the below command in PowerShell,
“AzureStorageEmulator.exe init -server . -sqlinstance SQLEXPRESS -forcecreate”
Below is the output,
Step 4: Run the below command in PowerShell to Start Emulator,
“AzureStorageEmulator.exe start”
Below is the output,
Step 5: After that check the “SQLEXPRESS” Databases,
New Database is created.
Now you can use the Storage Emulator.
I am a new linux user and when I installed eclipse and sdk for android in linux.I get below error
when I start emolator and wait for 15 minute. I ran my project.my project run very good and below message is shown.
[2013-05-30 09:53:13 - RamzNegar] Android Launch!
[2013-05-30 09:53:13 - RamzNegar] adb is running normally.
[2013-05-30 09:53:13 - RamzNegar] Performing com.elmos.ramznegar.MainActivity activity launch
[2013-05-30 09:53:13 - RamzNegar] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2013-05-30 09:53:22 - RamzNegar] Uploading RamzNegar.apk onto device 'emulator-5554'
[2013-05-30 09:53:23 - RamzNegar] Installing RamzNegar.apk...
[2013-05-30 09:53:39 - RamzNegar] Success!
[2013-05-30 09:53:39 - RamzNegar] Starting activity com.elmos.ramznegar.MainActivity on device emulator-5554
but i cannot show anything in emolator
I see below image
if answer is ~my emolator not run yet~;why my emolator dont run
how i can solve this problem?
for the first time that you run emulator it will run very slow
and when you run your app ,eclipse didnot get you error
I think this is a bug for google
I hope that speed of emulator will be improve
I have just finished creating an installer using Install Shield Limited edition. My Install shield project compiles without any errors. However, when I run the setup file, after it has copied the program files into the target folder, the installer starts rolling back and deletes the installation folder.
I have not yet put any custom action or defined any pre-requsities.
Has anyone encountered such an issue?
All I am doing in the installer is following:
Creating directory structure under "Program files (x86)" directory using "Files" option of Install shield.
Creating a Website and a application underneath it using the "Internet Information Services" option.
I have attached the settings of web application and web site with this post.
Would appreciate any inputs.
InstallShield 17:29:09: SetAspversion: machine is 64-bit and IIS running in a bit mode other than the currently selected mode
InstallShield 17:29:09: Error with IISRT: -2172
CustomAction ISIISInstall returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 17:29:09: InstallFinalize. Return value 3.
MSI (s) (7C:E0) [17:29:09:312]: User policy value 'DisableRollback' is 0
MSI (s) (7C:E0) [17:29:09:312]: Machine policy value 'DisableRollback' is 0
MSI (s) (7C:E0) [17:29:09:319]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1113951137,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (7C:E0) [17:29:09:319]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (7C:E0) [17:29:09:319]: Executing op: DialogInfo(Type=1,Argument=MyApplication)
MSI (s) (7C:E0) [17:29:09:319]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=1,CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: 1)
Action 17:29:09: Rollback. Rolling back action:
Rollback: ISIISInstall
MSI (s) (7C:E0) [17:29:09:321]: Executing op: ActionStart(Name=ISIISInstall,,)
MSI (s) (7C:E0) [17:29:09:321]: Executing op: ProductInfo(ProductKey={95199403-696F-4BF6-A443-19866156E3BD},ProductName=My Application,PackageName=My Application.msi,Language=1033,Version=16777216,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={F3B9DBEB-71D6-42C3-B18C-1C5CCBA647E0},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
Rollback: Copying new files
Finally found a solution to the a fore-mentioned problem.
The Error with IISRT: -2172 was caused because of the setting of Application pool (app pool) in IIS.
The property named "Enable 32-Bit Applications" was set to False. When I changed its value to True, the installer was able to successfully complete the installation without rolling back.
Problem solved :)
I've installed REDHAWK 2.0.0 from rpms on CentOS 6.7, run shell scripts as required, configured omniORB as required, updated SDRROOT permissions as required, and run cleanomni from a terminal command line, but cannot get REDHAWK_DEV to launch in the REDHAWK IDE. Right-clicking on Target SDR > Launch Domain... brings up the "Launch Domain Manager" dialog box with: red 'x" over the label 'Domain Manager'; default Device Manager visible and selectable; and "OK" button greyed out.
Attempting to connect via right-clicking REDHAWK_DEV > Connect throws error: 'Connecting Domain' has encountered a problem. Failed to connect to REDHAWK_DEV', and Details>> gives:
org.eclipse.core.runtime.CoreException: Error while executing callable. Caused by org.omg.CORBA.ORBPackage.InvalidName'
Any ideas? Thanks in advance!
You should be able to check the error by hovering over the red x marker in the launch domain dialog. But it's likely one of two problems:
Stale info in the naming service (try cleanns at the command line, then re-open the dialog), or
The naming service isn't running (try stopping it, clearing out /var/log/omniORB, and starting it)
The other issue you mentioned (right-click, "Connect" from context menu) is to connect to an already running domain. It doesn't launch it.
Thanks for that advice. But hovering over the red 'x' does not make visible any dialog box or tooltip.
I removed the files error.log, omninames-avl.bak, and omninames-avl.log from the directory /var/log/omniORB, ran cleanns, cleanes, and cleanomni, stopped and restarted both omniNames and omniEvents.
But none of these procedures had any effect on the symptom; the default domain is still visible and selectable, but not launchable.