I have created a Visual Studio 2017 offline installer using the command: mu_visual_studio_enterprise_2017_x86_x64_10049783.exe --layout c:\vs2017offline
Behind firewall, when I execute mu_visual_studio_enterprise_2017_x86_x64_10049783.exe, in the vs2017offline folder, I'm getting the following error:
Details
WebClient download failed: The remote server returned an error: (407) Proxy Authentication Required.
Bits download failed: Error context: BG_ERROR_CONTEXT_REMOTE_FILE, Error code: -2145844841
WinInet download failed: Url 'https://download.microsoft.com/download/0/1/2/012ECA6A-588A-4E9A-9759-62DB964C511A/VSInitializer.exe' returned HTTP status code: 407
Seems the installer still attempts making a connection to the internet.
Help.
For me it was the issue with validating the certificates the packages has been signed with. Since validation was failing, it was trying to connect to the internet to get the packages again. I imported all the certificates in the /layoutRoot/certificates folder and retried the installation and it worked.
I work on a completely air-gapped network and managed to install from the off-line installer without seeing any problems. However today my colleague using the same installer saw the error saying their was no Internet connection. After some investigation and comparison with my machine I managed to get it installed on his machine.
Firstly I had created a Visual Studio 2017 Enterprise offline installer using the following command:
mu_visual_studio_enterprise_2017_x86_x64_10049783.exe --layout c:\vs2017offline --lang en-US
Performing the following steps got it installed for my colleague.
Go into the 'certificates' directory in the installer directory, right click on each of the three files and select 'Install PFX'. I am not sure if this actually helps for the later step.
Start a Command Prompt running as Administrator. This should start you in the Windows system directory, e.g. c:\windows\system32.
Type the command
cd c:\windows\system32\drivers\etc
Type the command
notepad hosts
Add the following lines to the end of the file
127.0.0.1 ctldl.windowsupdate.com
127.0.0.1 ocsp.verisign.com
127.0.0.1 crl.verisign.com
127.0.0.1 csc3-2009-2-crl.verisign.com
127.0.0.1 github.com
127.0.0.1 nuget.org
127.0.0.1 download.codeplex.com
127.0.0.1 tools.google.com
127.0.0.1 www.startssl.com
127.0.0.1 ctldl.windowsupdate.com
127.0.0.1 crl.microsoft.com
127.0.0.1 crl.thawte.com
127.0.0.1 referencesource.microsoft.com
127.0.0.1 msdl.microsoft.com
Save the file.
Now run
mu_visual_studio_enterprise_2017_x86_x64_10049783.exe
It should churn away for a little while before eventually display the screen for selecting the VC workloads.
It really works. But....
1. The downloading process for the packages is not always error-free, sometimes it is aborting.
What you have tried, is downloading ALL, I would not recommend that...
2. It's really big.
Take this:
The following command downloads the whole VS 2017 for only English language, and there was exactly 20,6 GB shown in explorer (1901 files).
I don't know how big the whole data for all languages
With downloading only a part of this
And I am not sure, if I got all, with another try I got less...
So at least add the language parameter: "--lang en-US" or two languages...
3. In internet connection is used always for initialization (there should be parameters to avoid that, but there is are not exactly known which should work until now...)
4. No.3 seems is bad, admitted. But there is a good point to say about the installer too: It is enough to download only a part of files offline, and the installer is smart enough to download all these files from internet, which don't exist (offline) on your disk.
So, you can start with:
vs_enterprise__873301792.1489161815.exe --layout %CD%\vs2017offline --lang en-US --add Microsoft.VisualStudio.Workload.ManagedDesktop
This downloads only 1 GB. It should be possible to extend that line with:
--add Microsoft.VisualStudio.Workload.Data
--add Microsoft.VisualStudio.Workload.NetWeb
--add Microsoft.VisualStudio.Workload.Node
--add Microsoft.VisualStudio.Workload.Universal
--add Microsoft.VisualStudio.Workload.NetCoreTools
If there is an error, download them step-by-step.
Then you have all main .NET parts. (Cordova, Azure, MS Office adapter, game programming, Unity not mentioned here).
For more details, look here: Visual Studio 2017 workload and component IDs.
For C++ standard install add:
--add Microsoft.VisualStudio.Workload.NativeDesktop (for C++)
More possible options/packages:
--add Component.GitHub.VisualStudio
--add Microsoft.Component.Blend.SDK.WPF
--add Microsoft.Component.HelpViewer
--add Microsoft.VisualStudio.Component.TestTools.Core
--add Microsoft.VisualStudio.Component.TestTools.MicrosoftTestManager
--add Microsoft.VisualStudio.Component.TestTools.WebLoadTest
--add Microsoft.VisualStudio.Component.TypeScript.2.0
--add Microsoft.VisualStudio.Component.TestTools.CodedUITest
All together, it's less than 3 GB... Maybe you prefer this to the 20++ GB monster. Make an .iso out of that (I have used AnyBurn), and: ready. You can install on a PC with mobile connection without big costs, only be sure to select the correct language (here English) for the VS installer, if your Windows was started in another language. Because of that, the VS installer downloaded again 1 GB, but it was my fault...
After the offline has been successfully downloaded, these simple steps help me keep out of the setup troubles, hope this also help someone else :
1. Ensure you're connected to the internet.
2. Validating the certificates.
3. Make sure you have enough space for the installation.
If you receive messages like "file not found" retry to resume the offline by retyping the same command in the same folder.
4. run the installer
I was getting a prompt for internet connection, however after I did install all 3 certificates, installation was a success!, Maybe you guys need to confirm the download wasn't broken, or maybe install
aio-runtime 2.4.1
mainifestCounterSignCerficates.p12
mainifestSignCertificates.p12
vs_installer_opc.SignCertificates.p12
Related
How to connect Visual Studio Code on mac with Team Foundation Server(TFS).
Or any other way to connect with tfs?
This are the steps to effectively connect a TFS (TFVC) Repository to your VS Code on Mac:
INSTALL THE SOFTWARE
Install Visual Studio Code for Mac (currently here: https://code.visualstudio.com/download).
Install the TFS extension for VS Code: Go to the Extensions tab in VS Code, Search for TFS and install.
Install TEE-CLC. Follow this guide: https://www.youtube.com/watch?v=VPNaEIVZfr0&feature=youtu.be.
CREATE A LOCAL TFVC WORKSPACE IN YOUR MAC
Now you need to have a local TFVC Workspace on your machine. If you don't have one (as it was my case), you need to create it. The following steps are partially extracted from https://stackoverflow.com/a/21785438/2816119.
Create a local folder where you are going to download and locally store the source code.
Open a Terminal window.
Create a local workspace from your terminal window with the following command:
tf workspace -new MyWorkspace -collection:<<<http://full.URL.of/your/repository>>>
Map your repository folder to your local folder with the following command:
tf workfold -map '$/your/repository/folder/path' /your/local/folder/path -collection:<<<http://full.URL.of/your/repository>>> -workspace:MyWorkspace
If everything went well, you'll see a new sub-folder ".tf" in your local folder.
Open your local folder with VS Code. If everything went well you'll se after a few seconds the TFVC icons in the bottom bar:
GET THE SOURCE CODE
To get the source code you'll need to go to the Source Control Tab -> Ellipsis (...) button -> Sync.
Once you press it you'll see a progress bar moving in the Source Control Tab and you'll see how the source code is downloaded to your local folder.
ENJOY
Now you can use your TFVC repository as described in their guides.
If something is not clear or you have questions please let me know. I'll try to help you :-)
Get the software
tee-clc (can be installed with HomeBrew), which depends on
Java 6, 7, or 8 (see How to install Java 8 on Mac -- as of this writing, Java 9 will not work.)
Create a workspace using tee-clc ("tf")
Tell tee-clc to remember your credentials (in OSX's Keychain) by adding this line to your .bash_profile. Then close and reopen your terminal or just paste the same command.
export TF_AUTO_SAVE_CREDENTIALS=0
Accept the EULA.
tf eula
Create a workspace.
tf workspace -new MyCoolWorkspace -collection:https://my-server.example.com/tfs/DefaultCollection
Map a path on the server to a local folder.
tf workfold -map '$/Path/To/Folder' /path/to/your/local/folder -collection:https://your-server.example.com/tfs/DefaultCollection -workspace:MyCoolWorkspace
Get the code and store your password. Make sure you type your actual username; if you enter your_username here it may get stored in the OSX Keychain and tee-clc is really dumb about replacing it later.
cd /path/to/your/local/folder
tf get -login:your_username
If it works, it will download your code to that folder. You can also use the other commands.
Use the Azure Repos Extension on VS Code
Get the Azure Repos extension.
Add the following settings (CMD+,):
{
"tfvc.location": "/usr/local/bin/tf",
"tfvc.restrictWorkspace": true
}
Type which tf in Terminal to find out what the value for location should be. I'm not sure if "restrictWorkspace" is necessary. I got it from a comment on Github while I was troubleshooting.
Finally, open the folder containing your code. From the command palette (⌘+⇧+P) type Team: Signin. If that works, you can start using the other features in the plugin.
GIT
VS Code ships with a Git source control manager (SCM) extension. Most of the source control UI and work flows are common across SCM extensions.
More details please refer this tutorial：Using Version Control in VS Code
Note: VS Code will leverage your machine's Git installation, so you need to install Git first before you get these features. Make sure you install at least version 2.0.0.
TFVC
You can connect to TFVC using the Visual Studio Team Services extension since version 1.116.0 (2017/04/12).
Note: You need Team Foundation Server 2015 Update 2 or later.
Check the below link. It is working fine for me
How to use TFS on a Mac
Steps to be followed:
Step 1: Install Eclipse
Step 2: Download and install the TFS everywhere plugin
Step 3: Checkout your solution using the eclipse to a local folder
Step 4: Open the solution in Visual studio and make the code changes
Step 5: Open eclipse and commit your changes.
I know there's a ton of there install error posts but I have tried EVERYTHING from editing the registry to command line parameters, I cannot get VS Community to install.
A couple of years ago I tried to install VS Community to my old E:\ drive. That drive corrupted and/or stopped working, so I got a new drive (F:) and am currently trying to install it. I would be fine with installing it on my C:\ if necessary. I'm running Windows 10 Pro 64x.
I have also tried,
Disabling all firewalls
Re-downloading the installer
Deleting the VS Folders from Local and Program Files
Literally everything I've seen here and on other forums. Oddly, the installer does not create log files in Temp either, so I'm at a loss of stuff to show.
And lastly, in apps, Visual Studio Community 2015 is listed with uninstall, however, when I go to uninstall, it also throws an error (no error code) saying:
Fatal Error while installing.
And the exact install error:
Invalid Drive
There's no error code but there is a grayed out box containing the drive path E:\
Honestly, I'm about ready to explode, I've been trying to install this nonsense for the last year. I wish installers were still the simple Windows Installer Wizard style, but of course developers have to come around and mess that up. Ironic though, the purpose of having this software is to make a app...let alone deal with one.
According to your description, the VS installation location defaults to the old invalid drive E:. This is because once a set of shared components is installed, we install all the other components to the same directory structure. When you have multiple editions installed, this saves disk space since shared files occupy the same location on disk – not to mention results in faster install times since Windows Installer doesn’t copy the same bits again.
Heath Stewart has instructions on how to find the products that also installed these shared components and remove them; after that you should be able to modify VS installation location.
Download and install http://psmsi.codeplex.com. These are general-purpose PowerShell cmdlets I created for all sorts of development and troubleshooting operations for Windows Installer-based installs. You do not need to elevate to install them, though if you pre-elevate you can install them per-machine (by default they are per-user).
Open an elevated PowerShell command prompt and run the following to discover which products have installed the key shared component:
get-msicomponentinfo '{777CBCAC-12AB-4A57-A753-4A7D23B484D3}' |
get-msiproductinfo
If you’re fine with uninstalling all the listed products (especially given that you’re probably going to install RTM next), run the following:
get-msicomponentinfo '{777CBCAC-12AB-4A57-A753-4A7D23B484D3}' |
get-msiproductinfo | uninstall-msiproduct -properties IGNOREDEPENDENCIES=ALL
I have a PostgreSQL database on a Linux system that I want to access from my Windows PC. But the only Windows binaries I have been able to find are the full installer, which includes the database server and client.
Is it possible to get a client-only Windows binary install for PostgreSQL from anywhere?
(To clarify, I want the standard PostgreSQL client, psql - not a GUI client or independent tool).
Unfortunately there is no real client "only" installer.
What you can do, is to download the ZIP archive of the complete Postgres binaries:
http://www.enterprisedb.com/products-services-training/pgbindownload
and then remove the "server" part from it.
When you unzip it, you get the following directories:
bin
doc
include
lib
pgAdmin III
share
StackBuilder
symbols
You can remove the doc, include, pgAdmin III, StackBuilder and symbols directories. As far as I can tell (but I am not sure) the client also doesn't need the share or lib directories, but you would need to test that. So that leaves only the bin directory.
I think the share directory could be needed for localized error messages in psql but I'm not sure about that.
Inside the bin directory you can essentially remove all .exe files (except psql.exe of course). You can also remove all wx*.dll files, they are only needed for pgAdmin. The libxml2.dll and libxslt.dll are also only needed for the server.
If you do want some of the other client tools, you might want to keep
pg_dump.exe
pg_dumpall.exe
pg_restore.exe
One drawback of this approach is that this requires the Visual C++ Redistributable to be installed. But you can overcome that as well by simply putting the MSVCR120.DLL from some computer where it is installed into the bin directory.
So that leaves you with these files (from the bin directory) that are required for the psql client:
iconv.dll (libiconv-2.dll in newer Postgres versions)
libeay32.dll
libintl-8.dll
libpq.dll
msvcr120.dll
ssleay32.dll
zlib1.dll
psql.exe
Of course you can also take all that from an existing Postgres installation without the need to download the ZIP archive.
It is obviously not a real installer, but if you put the cleaned up directory into a ZIP file, you can distribute that and whoever needs it just unzips the archive. Personally I find unzip to be the best "installer" anyway (I also use that to install the Postgres server, the Windows installer just has too many quirks)
As of 2020, when you click download the full installer from here , click next and next and you get the option to install only the command line - tools
. Remember to add the path to the bin folder in the PATH variable.
Actually there are client CLI tools in pgAdmin. All you need is just to install it on your Windows machine from https://www.postgresql.org/download/windows/.
Then you'll be able to find those tools in folder like C:\Program Files (x86)\pgAdmin III\1.22 or C:\Program Files (x86)\pgAdmin 4\v2\runtime, depends on the pgAdmin version you have installed.
Thanks to everyone who has posted on this thread.
For what it's worth, I got psql.exe from PostgreSQL 10.10 working under Windows 10 with just the following files from the zip archive:
libcrypto-1_1-x64.dll
libiconv-2.dll
libintl-8.dll
libpq.dll
libssl-1_1-x64.dll
psql.exe
When connecting to AWS Redshift, I got the following error:
psql: FATAL: invalid value for parameter "client_encoding": "WIN1252"
I resolved this by running
set PGCLIENTENCODING=UTF8
I found this solution at https://forums.aws.amazon.com/thread.jspa?messageID=600088
HTH.
I realize this is an older question, but when I used the Windows installer for the latest version of Postgres (10.4), it gave me the option to install just the command line tools. I just unchecked server and pgadmin in the installer's window when prompted to choose what I wanted to install.
Below are the steps I followed to connect to Amazon Redshift with postgres12 psql on windows:
download postgres 12.4 from below location:
https://www.enterprisedb.com/downloads/postgres-postgresql-downloads
run the installer which will take few minutes and prompt you for installations options
select command line tools as shown in below screenshot and install that
Above will install postgres12 command line in below folder C:\Program Files\PostgreSQL\12\bin. Make sure to add this to your PATH environment variable
open cmd and run command
set PGCLIENTENCODING=UTF8
run psql to connect to redshift. Make sure to change below parameters highlighted in red for your cluster endpoint, userid, copy script file name and log script file name respectively
psql -h redshift-cluster-1.abcdefgh.us-east-1.redshift.amazonaws.com -U demo_user -d dev -p 5439 -f d:\demo\redshift_script.sql -L d:\demo\log_redshift_script.log
all commands in redshift_script.sql file would get executed in PSQL and logs will be stored in log_redshift_script.log file
There is a third-party command-line tool available known as PGCLI - A command-line interface for Postgres with auto-completion and syntax highlighting.
Install:
pip install pgcli
Connect to POSTGRES Server from Command-line:
pgcli -h localhost -U xyz -d app_db
For official documentation, visit PGCLI
If there's pgadmin v4 installed then just copy these libraries (from C:\Program Files\pgAdmin 4\v4\runtime\):
libcrypto-1_1-x64.dll
libpq.dll
libssl-1_1-x64.dll
These were enough for me to connect from a client Windows 10 x64 PC to a remote Postgres 13 server. Note, that libraries coming with the ZIP archive mentioned above are slightly different and have more dependencies.
I kind of cheat. I install sqlbackupandftp.com on a Windows server - which has a free version that can schedule a single database backup. In the binaries, pg_dump.exe is there - typically on the C: drive like C:\Program Files (x86)\SQLBackupAndFTP\dbms\PostgreSql
I built standalone versions for windows and linux.
It has less dll dependecies and smaller size and work with many linux.
https://github.com/hemnstill/StandaloneTools/releases?q=pg_dump
You can also download "https://www.nuget.org/packages/Postgres.psql" nuget package to get "psql.exe"
Whenever I try to install the Visual Studio SDK I get the following error:
Windows Program Compatibility mode is on. Turn it off and then try Setup again.
I have checked and Compatibility mode is not turned on. From what I've read, renaming the installer to vssdk_full.exe should help. That hasn't had any impact.
I got the installer from Microsoft's website.
What do I need to do to get this to install?
Are you installing on Windows 10? If so, then I have the same problem and it seems as though the current SDK setup is checking the Windows version and 10 isn't currently supported. See https://social.technet.microsoft.com/Forums/en-US/77c61be0-1303-4040-a587-62843d321159/visual-studio-2013-sdk?forum=WinPreview2014General for more info
I have managed to get it to install on windows 10, download the sdk, it will download vssdk_full.exe, run this with /layout path which will extract the actual setup file.
Then set compatibility on the new file to win 8 and it will install just fine.
You might not need to do the/layout thing but that is what I did.
ed
I had the same problem. I downloaded .iso file with install package form the internet. Then I mounted it using PowerISO and tried to start it from virtual CD drive. It ended up in the same message as above.
I looked it up and thought that in Properties of .exe install file, it's enough to uncheck some boxes compability section. But nothing was checked.
Soon afterwards I unzipped the package to a temporary directory with PowerISO and installed Visual from there. Worked without problems.
I had this problem, I renamed the instalation file to "vssdk_full.exe" and it installed without problems.
I'm trying to install cygwin on a windows 2008 server. I managed to get a hold of the cygwin setup.exe version 2.721.
Since cygwin.com is down at the moment, i tried several mirrors found through the google cache of the cygwin mirrors. I ran into the same problem like this guy: Help needed installing cygwin: may be ini file problem
Like they suggested, I tried http://mirrors.kernel.org as mirror. It downloads some setup.bz files fine. Then I get the error "Unable to get setup.ini from http://mirrors.kernel.org/". Any suggestions how to install cygwin now?
I got this error when I tried to use http://cygwin.com/setup.exe and not http://cygwin.com/setup-x86.exe or http://cygwin.com/setup-x86_64.exe. It seems the mirrors have just recently removed support for setup.exe. The setup.exe is still available to download but none of the mirrors work.
The solution is to use either the setup-x86.exe or the setup-x86_64.exe.
The mirror should be the full path http://mirrors.kernel.org/sourceware/cygwin
If you get complaints about the .ini being from a newer version of setup, you'll need to find a newer setup.exe somewhere on the net that you trust. (And cygwin guys? Grrr for not including setup.exe in your mirrors and for not signing your exe!)
the reason is so simple:
the setup.ini changed its's location!
just go to cygwin site, download the latest setup.exe file. it will be OK.
While installing, select Install through http/ftp proxy. Firewall may block the installation. Hence, proxy will help. Also try running as Administrator.
It helps..
Regards,
Frank..!!
For those who are still getting this error even with the correct installer, make sure that you're running the setup file on your local hard drive.
My problem was that I was trying to launch the executable from a mapped network drive. Copying down and running the program locally fixed the issue.
Can you use another mirror? Try lug.mtu.edu or something like that. I've always had nothing but good results from there.
Was giving me the same Unable to get setup from ... error.
I used the new setup-x86_64.exe from the Cygwin.org site & had to select the option Use Internet Explorer Proxy Settings.
It fetched the mirror urls.
It worked that way for me.
But, if it does not fetch all the mirrors by itself, we can
add the url http://mirrors.kernel.org in the Download list.
Initially, when it was not downloading the mirrors list by itself, I had tried adding the above http://mirrors.kernel.org url manually & it had worked that way too.
Was facing the Same issue... Run the installer in administrator mode and set the FTP/HTTP proxy to the proxy setting configured in internet explorer. Later if the download doesn't occur try different proxies. Selecting this mirror http://mirrors.kernel.org worked for me.