I'm attempting to install and use MSYS2 (just getting started with it). I used the installer msys2-x86_64-20150916.exe and that seemed to go fine. Following the install directions, I ran both the update-core script and package database sync. Both fail. I show some of the output of the update core script below. The database sync fails for same "filename too long" reasons.
==> Update package databases...
:: Synchronizing package databases...
downloading mingw32.db...
downloading mingw32.db...
downloading mingw32.db...
downloading mingw32.db...
downloading mingw32.db...
error: could not open file /var/lib/pacman/sync/process?a=-3-lqCLzXmOVMGhdCngyCV4_GayxZ9J_5BY5vi5g3cT8TnaVOyHNkP3i0c8d5C4blqAp5pNlE0ed_vEU-kPSDHKOg&b=PPNTxJgmwuDT5DPf_2sovf-m6J5IoL2zxXU84ePhgAUcZBDyVD_v4wfG6xGP3FZCi8b3EStJPpKrKU8ykIp4uPYrbGFuUlsd-FOf5alMDNO2Olf-YFTsRpUe24Yfq_ATwekjooJm-B-XXCVQ1YAE-3RUWx6oUzFYRJU02LpZIsToFNPuxq-KAou5Jn0dv8rnnKahdjG5tC2rTNNj4gWmj4P_9EX4TcaNgFcSKXzudqLljMnXiamdT4NGmqOPl_cDHrPSnLGDHLWoQHEqx1lL22LYPuzY135OpobhnKym1KM1DLksJiU3U9CwbJ7-2dUD2k1mXjQYV6qGC0I6VRGIkmjkOUCiGsiLMlz-OnHKs_CgI0NyreR38yFPfW6pnW4skarOGfYj0p9pp2MMCMeXtQF6XDDZs3Hah8QoEBL8ZQjD9pArAbk34E9jUIgJXG4I&blockedUrl=http%3A%2F%2Frepo.msys2.org%2Fmingw%2Fi686%2Fmingw32.db.sig.part: File name too long
...
==> Checking if there are critical packages to upgrade.
error: could not open file /var/lib/pacman/sync/mingw32.db: Unrecognized archive format
...
I am running on Windows 7 Enterprise.
Let's look at that long filename more carefully. Here is an excerpt from it:
blockedUrl=http%3A%2F%2Frepo.msys2.org%2Fmingw%2Fi686%2Fmingw32.db.sig
It looks like you are behind some sort of firewall or censoring software that is blocking a download. You should see if you can download http://repo.msys2.org/mingw/i686/mingw32.db.sig in a normal web browser. If not, then you can report the problem to your system administrator and ask them to unblock repo.msys2.org.
When you test the download, make sure that you are able to download the file without clicking through any interstitial web pages, because the MSYS2 software will not be able to do that. You should be able to just click on the link above and it should directly download the file.
Related
Steps to reproduce are very easy.
Create a Dockerfile.
My Dockerfile has many more lines, but I have trimmed them so we can focus in the source of the problem.
Said that, these two lines alone (without anything more) show the problem.
FROM microsoft/iis
SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue'; $VerbosePreference = 'Continue'; "]
Run docker build . and you get hcsshim::PrepareLayer - failed failed in Win32: Función incorrecta. (0x1).
Windows 10 Pro 1909 (but it happened too in 1903)
Docker version: 2.1.0.5
Engine: 19.03.5
Machine: 0.16.2
I have found the solution to the problem.
Reading all the https://github.com/docker/for-win/issues/3884 bug, some have found a simple solution: rename C:\windows\system32\driver\cbfsconnect2017.sys so it isn't loaded the next boot.
Disabling that driver enables me to do a docker build for the first time in windows containers in almost a year.
In my case Box Sync was the one using that driver.
EDIT: #GustavoTM have found that pCloud raises the same problem.
EDIT2: #VonC have noticed that some people in the issue in GitHub has solved it deleting this other file: C:\Windows\System32\drivers\cbfs6.sys. I haven't tried that, but i put it if it helps others.
The good thing is that I don't need to uninstall Box, but only rename that file.
This is still an issue (still open) with Win10.
Looks like uninstalling cloud storage providers with file system filters like Dropbox, Box, etc. as a workaround is an option for some users.
Deinstall cloud storage providers or virus scanners; if you identify which one is not working please share in https://github.com/docker/for-win/issues/3884
In my case was the problem similar but the file cbfs6.sys was placed somewhere in the rest of uninstalled application Jungle disk, somewhere in the folder c:\Program files\Jungle disk .... It's part of Callback File System signed by EldoS Corporation.
The folder could be rename only and not delete directly. So I could delete its immediately after the PC restart, before running the Docker. So it could be delete during the Docker service restart too.
I am trying to download Appium Desktop in Ubuntu 16 (I've just been using the terminal to run it so far).
I understand that for Ubuntu, I must download the source code release they have on git (Source Code tar.gz), as apposed to their .exe (windows) or .dmg (mac) releases. After downloading it and un-tarring it, I do not know how to "install" it. I tried reading the README.md, but cannot find the instruction.
How to do this?
Many thanks in advance
1.2.0-beta.2 offers an AppImage for Linux - https://github.com/appium/appium-desktop/releases/
Download it, run chmod a+x on it, and then ./AppImage to execute it.
Offical url: https://github.com/appium/appium-desktop/releases
If you have no idea which file to download, there's a file contains "linux" and end with format "yml", the file name is contained in it.
The file should be an AppImage file as above mentioned, you should change the permission by checking box of "Allow executing file as program" of its "Properties".
And then run "./appiumimagename" in terminal to launch Appium Desktop or install it.
download file named'Appium-linux-1.18.2.AppImage'.
change file permission to "Allow executing file as program" in file properties.
Right click and click on RUN.
I have just installed MSys2 (https://msys2.github.io, msys2-x86_64-20150916.exe) on my Windows 10 computer.
Once installed, the terminal is launched. But as soon as I stop it and relaunch it, I get the error: "Failed to run /sbin/nologin: No such file or directory".
Any idea on what to do?
You should figure out why Bash is trying to run /sbin/nologin. Check your Windows home directory (e.g. C:\Users\Joe) for files like .bash_profile, .profile, and .bashrc. Inspect those files and find which one is calling nologin.
If that doesn't help, try creating an empty file in C:/msys64/sbin/nologin, or wherever you actually installed MSYS2. An empty file would be a valid shell script and run without errors.
If the error is non-fatal you might consider just ignoring it.
My SQL Server 2012 suddenly stopped working here is all I got in popup message:
could not load file or assembly 'microsoft.visualstudio.shell.ui.internal' or one of its dependencies. An attempt was made to load a program with incorrect format.
I have Repaired using installation CD but no luck.
I had the same problem and fixed by uninstalling the Visual Studio 2010 Shell and installing back. Simply reinstalling doesn't work.
1. Download the Visual Studio 2010 Shell: https://www.microsoft.com/en-us/download/details.aspx?id=1366
2. Run the exe file and click uninstall(or remove).
3. Run the exe file and click install with default settings.
After these steps the Management Studio will work just fine.
I got this error in VS2013 when reparing in the logfille,
[113C:2588][2018-01-20T16:41:54]i000: MUX: ExecuteError: Package (vs_minshellcore) failed: Error Message Id: 1305 ErrorMessage: Error reading from file C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Shell.UI.Internal\v4.0_12.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Shell.UI.Internal.dll. Verify that the file exists and that you can access it.
and I check the file is exist, and I modify its access authority to complete control to every user account, but this error still occur,
Finally I delete this dll, and find same dll in another Normal Computer with VS , and copy the file paste to the problem computer, and run repair again then pass.
Share my works Microsoft.VisualStudio.Shell.UI.Internal.dll in Here.
But in my case after repair success, vs2013 still got error when opening, so I finally give up and turn to use vs2015, which luckly can work. It is a strange problem.
have this problem also with vs2019 community. I was trying to create the first 2019 project after it is installed. Then I got this. I ran the install exe file, vs_community.exe again in order to repaire it. But I found out that the install program request to restart the pc to finish the last step. Actually I restarted the pc afterwards manually. But I still did it by clicking on the button "restart pc". After the pc is restarted, the problem is gong. I can create project without any error.
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)