C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>
rabbitmq-plugins.bat enable rabbitmq-management
The directory name is invalid.
The filename, directory name, or volume label syntax is incorrect.
** (MatchError) no match of right hand side value: {:error, {:node_name,
:hostname_not_allowed}}
(rabbitmqctl) lib/rabbitmq/cli/core/helpers.ex:32:
RabbitMQ.CLI.Core.Helpers.normalise_node/2
(rabbitmqctl) lib/rabbitmqctl.ex:232: RabbitMQCtl.merge_defaults_node/1
(rabbitmqctl) lib/rabbitmqctl.ex:225: RabbitMQCtl.merge_all_defaults/1
(rabbitmqctl) lib/rabbitmqctl.ex:103: RabbitMQCtl.exec_command/2
(rabbitmqctl) lib/rabbitmqctl.ex:45: RabbitMQCtl.main/1
(elixir) lib/kernel/cli.ex:105: anonymous fn/3 in Kernel.CLI.exec_fun/2
I get this error when trying to enable management. I have tried reinstalling rabbitmq and erlang. I have tried setting environment variables. nothing seems to work. its running on windows server 2016, otp_win64_21.3, and rabbitmq-server-3.7.14
Update:
I have tried renaming the server all uppercase, all lowercase, and without a dash... none of those helped. The servers are currently named "SQL01-Dev" and "sql01-live"
Update 2:
I have ran the command using the node name and it has no effect. I did notice a case difference in the hostname between the environment variable and the hostname command. Here is my command line output:
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>rabbitmq-
plugins.bat -n rabbit#SQL01-dev enable rabbitmq_management
The directory name is invalid.
The filename, directory name, or volume label syntax is incorrect.
** (MatchError) no match of right hand side value: {:error, {:node_name,
:hostname_not_allowed}}
(rabbitmqctl) lib/rabbitmq/cli/core/helpers.ex:32: RabbitMQ.CLI.Core.Helpers.normalise_node/2
(rabbitmqctl) lib/rabbitmqctl.ex:232: RabbitMQCtl.merge_defaults_node/1
(rabbitmqctl) lib/rabbitmqctl.ex:225: RabbitMQCtl.merge_all_defaults/1
(rabbitmqctl) lib/rabbitmqctl.ex:103: RabbitMQCtl.exec_command/2
(rabbitmqctl) lib/rabbitmqctl.ex:45: RabbitMQCtl.main/1
(elixir) lib/kernel/cli.ex:105: anonymous fn/3 in Kernel.CLI.exec_fun/2
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>Hostname
SQL01-dev
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>echo %COMPUTERNAME%
SQL01-DEV
Update 3
I Have Removed the #Echo Off line. Here is the output:
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM #echo off
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM The
contents of this file are subject to the Mozilla Public License
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM Version
1.1 (the "License"); you may not use this file except in
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM compliance
with the License. You may obtain a copy of the License
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM at
http://www.mozilla.org/MPL/
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM Software
distributed under the License is distributed on an "AS IS"
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM the
License for the specific language governing rights and
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM
limitations under the License.
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM The
Original Code is RabbitMQ.
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM The
Initial Developer of the Original Code is GoPivotal, Inc.
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM Copyright
(c) 2007-2015 Pivotal Software, Inc. All rights reserved.
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>setlocal
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>rem Preserve values that might contain exclamation marks before
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>rem enabling delayed expansion
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>set TDP0=C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin\
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>set STAR=enable RabbitMQ-Management
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>setlocal enabledelayedexpansion
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM Get default settings with user overrides for (RABBITMQ_)<var_name>
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>REM Non-empty defaults should be set in rabbitmq-env
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>call
"!TDP0!\rabbitmq-env.bat" rabbitmq-plugins
The directory name is invalid.
The filename, directory name, or volume label syntax is incorrect.
** (MatchError) no match of right hand side value: {:error, {:node_name,
:hostname_not_allowed}}
(rabbitmqctl) lib/rabbitmq/cli/core/helpers.ex:32:
RabbitMQ.CLI.Core.Helpers.normalise_node/2
(rabbitmqctl) lib/rabbitmqctl.ex:232: RabbitMQCtl.merge_defaults_node/1
(rabbitmqctl) lib/rabbitmqctl.ex:225: RabbitMQCtl.merge_all_defaults/1
(rabbitmqctl) lib/rabbitmqctl.ex:103: RabbitMQCtl.exec_command/2
(rabbitmqctl) lib/rabbitmqctl.ex:45: RabbitMQCtl.main/1
(elixir) lib/kernel/cli.ex:105: anonymous fn/3 in Kernel.CLI.exec_fun/2
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.14\sbin>
Update 4:
I can start and configure the server If I Login under a local account. however, when rabbitmq_management is enabled There is still nothing listening on port 15672. Also my dev machine is Not using a local login but it works just fine for everything. I have compared the output of the Set commands for both systems and the only difference I can see is my dev machine has a few extra variable for things like java. nothing that I would think RabbitMQ needs. I'm still not seeing a major difference between the working environments and the non-working ones. I haven't tested if i can actually connect to the MQ server if it runs from a local account but we'll need to be able to manage the server using domain logins anyway...
Open the "RabbitMQ Command Prompt (sbin dir)" terminal with administrative right, run:"
Before getting invalid path error
Please check your window defender firewall app or features setting as Below:
1. Write down "window defender firewall" on window search
2. Click "Allow an app or feature though Windows Defender Firewall"
3. Click "Change Settings"
4. Check setting for epdm and erl and it should be (Domain= true; private:true and public = true)
5. Click "OK"
Please run below command:
set HOMEDRIVE=C:
rabbitmq-service.bat stop
rabbitmq-service.bat uninstall
rabbitmq-service.bat install
rabbitmq-service.bat start
rabbitmq-plugins.bat enable rabbitmq_management
Related
I'm installing Gazebo Garden on my Windows 10 laptop and recently had some problems regarding building the ignition libraries with cmake.
First, I had an error that make couldn't run the msbuild command. The solution to that was to add the msbuild path to the system environment variables and to delete the cmake cache as in https://stackoverflow.com/questions/4... explained.
Here may be the first source of error. I changed the MS Visual studio version to the correct version of VS 19, but was not sure about the source and build folder. I set the source code folder to /ign-ws/src/ign-cmake from the installation manual (https://gazebosim.org/docs/garden/ins...) and the build folder to a new empty folder.
It kinda worked and I went on to build the libraries, but the command
colcon build --cmake-args -DBUILD_TESTING=OFF --merge-install --packages-up-to ignition-gazebo7
gave an error again. This time the error is something about the VCtargetsPath as shown in the error code:
(ign-ws) C:\Windows\System32> colcon build --cmake-args -DBUILD_TESTING=OFF --merge-install --packages-up-to ignition-gazebo7
Starting >>> ignition-cmake3
Starting >>> ignition-tools2
--- stderr: ignition-cmake3
CMake Error at CMakeLists.txt:6 (project):
Failed to run MSBuild command:
C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/MSBuild/Current/Bin/MSBuild.exe
to get the value of VCTargetsPath:
Microsoft (R)-Build-Engine, Version 16.11.2+f32259642 für .NET Framework
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
MSBUILD : error MSB1009: Die Projektdatei ist nicht vorhanden.
Schalter: VCTargetsPath.vcxproj
Exit code: 1
---
Failed <<< ignition-cmake3 [1.41s, exited with code 1]
Aborted <<< ignition-tools2 [1.27s]
Summary: 0 packages finished [14.7s]
1 package failed: ignition-cmake3
1 package aborted: ignition-tools2
2 packages had stderr output: ignition-cmake3 ignition-tools2
13 packages not processed
I couldn't find any solution connecting both errors. Is the cause of my second error the false source folder? Maybe someone can help?
Operating on Windows 10.
I am trying to install Tensorflow within a conda environment. The Anaconda 3 version I am using is the one that can be installed from within Visual Studio, conda version number is 4.6.14.
I created a new environment with conda create -n test python=3.6 and afterwards tried to install Tensorflow:
> conda activate test
> (test) conda install tensorflow-gpu
after which I'm getting the following error:
Downloading and Extracting Packages
tensorflow-base-1.13 | 217.6 MB | ############################################################################ | 100%
[Errno 2] No such file or directory: 'C:\\Program Files (x86)\\Microsoft Visual Studio\\Shared\\Anaconda3_64\\pkgs\\tensorflow-base-1.13.1-gpu_py36h871c8ca_0\\Lib\\site-packages\\tensorflow\\include\\tensorflow\\include\\external\\eigen_archive\\unsupported\\Eigen\\src\\SpecialFunctions\\SpecialFunctionsPacketMath.h'
Any idea on what could be the error here?
Edit: conda info returned:
active environment : base
active env location : C:\Program Files (x86)\Microsoft Visual Studio\Shared\Anaconda3_64
shell level : 1
user config file : C:\Users\Me\.condarc
populated config files :
conda version : 4.6.14
conda-build version : 3.10.5
python version : 3.6.5.final.0
base environment : C:\Program Files (x86)\Microsoft Visual Studio\Shared\Anaconda3_64 (writable)
channel URLs : https://repo.anaconda.com/pkgs/main/win-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/free/win-64
https://repo.anaconda.com/pkgs/free/noarch
https://repo.anaconda.com/pkgs/r/win-64
https://repo.anaconda.com/pkgs/r/noarch
https://repo.anaconda.com/pkgs/msys2/win-64
https://repo.anaconda.com/pkgs/msys2/noarch
package cache : C:\Program Files (x86)\Microsoft Visual Studio\Shared\Anaconda3_64\pkgs
C:\Users\Me\.conda\pkgs
C:\Users\Me\AppData\Local\conda\conda\pkgs
envs directories : C:\Program Files (x86)\Microsoft Visual Studio\Shared\Anaconda3_64\envs
C:\Users\Me\.conda\envs
C:\Users\Me\AppData\Local\conda\conda\envs platform : win-64
user-agent : conda/4.6.14 requests/2.18.4 CPython/3.6.5 Windows/10 Windows/10.0.17134
administrator : True netrc file : None
offline mode : False
I have the same issue. Like you, I also did the convenient "mistake" of installing Anaconda with the Visual Studio installer. As James pointed out, the problem is indeed that the file path is too long (> 260). Anyway, it would seem we have to swallow the bitter pill, uninstall Anaconda and reinstall it at root level (I'll go for Mini-Conda this time).
Before I do that, I'll try to find a way of moving the Anaconda3_64\pkgs\ to a different location. Should that work, I'll post it here.
Edit: Got the solution, no reinstall necessary!
The problem comes from windows itself, which by default does not support long file paths. But this can be changed using a registry flag:
https://knowledge.autodesk.com/support/autocad/learn-explore/caas/sfdcarticles/sfdcarticles/The-Windows-10-default-path-length-limitation-MAX-PATH-is-256-characters.html
Open Regedit as Admin
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
Change LongPathsEnabled to 1 (DWORD 32 bit)
Warning: it could break compatibility of older programs. So far, for me everything is still working fine. If you should run into problems, simply revert the setting (and remember you have changed this setting!)
i have downloaded mongodb msi file form mongodb website and i have installed successfully in C:\Program Files\MongoDB\Server\3.2\bin
And i used command as mongodb on a command prompt with administrator privileges
but error occurred as
C:\Program Files\MongoDB\Server\3.2\bin>mongo
MongoDB shell version: 3.2.0
connecting to: test
2016-01-05T15:08:52.215+0530 W NETWORK [thread1] Failed to connect to 127.0.0.1:27017, reason: errno:10061 No connection could be made because the target machine actively refused it.
2016-01-05T15:08:52.229+0530 E QUERY [thread1] Error: couldn't connect to server 127.0.0.1:27017, connection attempt failed :
connect#src/mongo/shell/mongo.js:224:14
#(connect):1:6
exception: connect failed
image of cmd prompt is attached here
after executing mongod command error is like
C:\Program Files\MongoDB\Server\3.2\bin>mongod
2016-01-05T15:06:15.150+0530 I CONTROL [initandlisten] MongoDB starting : pid=12512 port=27017 dbpath=C:\data\db\ 64-bit host=DESKTOP-3F1GEI5
2016-01-05T15:06:15.161+0530 I CONTROL [initandlisten] targetMinOS: Windows Vista/Windows Server 2008
2016-01-05T15:06:15.167+0530 I CONTROL [initandlisten] db version v3.2.0
2016-01-05T15:06:15.171+0530 I CONTROL [initandlisten] git version: 45d947729a0315accb6d4f15a6b06be6d9c19fe7
2016-01-05T15:06:15.179+0530 I CONTROL [initandlisten] allocator: tcmalloc
2016-01-05T15:06:15.183+0530 I CONTROL [initandlisten] modules: none
2016-01-05T15:06:15.186+0530 I CONTROL [initandlisten] build environment:
2016-01-05T15:06:15.190+0530 I CONTROL [initandlisten] distarch: x86_64
2016-01-05T15:06:15.195+0530 I CONTROL [initandlisten] target_arch: x86_64
2016-01-05T15:06:15.200+0530 I CONTROL [initandlisten] options: {}
2016-01-05T15:06:15.238+0530 I STORAGE [initandlisten] exception in initAndListen: 29 Data directory C:\data\db\ not found., terminating
2016-01-05T15:06:15.246+0530 I CONTROL [initandlisten] dbexit: rc: 100
mongod direct command contain some by default parameter
mongod --dbpath=C:\data\db\ --port=27017
so create a folder data in c then create a db folder in that then run the command
mongod
your server will be in running state now connect to it using
mongo --port=27017
this will work for you if problem then comment
We just upgraded our test web servers from Server 2008 to Server 2012 R2. We have have a batch script that deploy our site. When it goes to push the site to the server its now failing. Whats weird is that is i can publish through visual studio with the same publish profile and everything is fine. We were able to upgrade our dev web servers and ever ran into this issue.
Here is what happens when i publish through visual studio 2015 (which works):
>C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_compiler.exe -v \ -p "C:\tfs\TRSApps\Test\Web\Secured Account Access\Member\obj\x86\Release\AspnetCompileMerge\Source" -u "C:\tfs\TRSApps\Test\Web\Secured Account Access\Member\obj\x86\Release\AspnetCompileMerge\TempBuildDir"
3>Auto ConnectionString Transformed obj\x86\Release\AspnetCompileMerge\TempBuildDir\Web.config into obj\x86\Release\CSAutoParameterize\transformed\Web.config.
3>Copying all files to temporary location below for package/publish:
3>obj\x86\Release\Package\PackageTmp.
3>Start Web Deploy Publish the Application/package to https://web-test3-new:8172/msdeploy.axd?site=TRS ...
3>Adding directory (TRS/subsections/SecureAccountAccess\App_Browsers).
3>Adding directory (TRS/subsections/SecureAccountAccess\bin).
3>Adding directory (TRS/subsections/SecureAccountAccess\Board).
3>Adding directory (TRS/subsections/SecureAccountAccess\Demographics).
3>Adding directory (TRS/subsections/SecureAccountAccess\Estimates).
3>Adding directory (TRS/subsections/SecureAccountAccess\General Information).
3>Adding directory (TRS/subsections/SecureAccountAccess\Includes).
3>Adding directory (TRS/subsections/SecureAccountAccess\Includes\Images).
3>Adding directory (TRS/subsections/SecureAccountAccess\Includes\Scripts).
Here is the batch statement to deploy the site:
"C:\Program Files (x86)\MSBuild\14.0\Bin\msbuild.exe" "c:\tfs\trsapps\test\Web\Secured Account Access\Member\TRSSecureAccess.vbproj" /p:VisualStudioVersion=14.0;DeployOnBuild=True;Configuration=Release;Platform=x86;PublishProfile="c:\tfs\trsapps\test\Web\Secured Account Access\Member\My Project\PublishProfiles\Membertest.pubxml";AllowUntrustedCertificate=True;Username=bob;Password=MyPassword /t:Clean;Build /p:OutputPath="c:\tfs\trsapps\test\Web\Secured Account Access\Member\bin"
afd
PipelineCopyAllFilesToOneFolderForMsdeploy:
Publish Pipeline Deploy phase Stage PipelineCopyAllFilesToOneFolderForMsdeploy
GenerateMsdeployManifestFiles:
Generate source manifest file for Web Deploy package/publish ...
MSDeployPublish:
Start Web Deploy Publish the Application/package to https://web-test3-new:8172/msdeploy.axd?site=TRS ...
Starting Web deployment task from source: manifest(c:\tfs\trsapps\test\Web\Secured Account Access\Member\bin\_Publish
edWebsites\TRSSecureAccess_Package\TRSSecureAccess.SourceManifest.xml) to Destination: auto().
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : Web d
eployment task failed. (Could not complete the request to remote agent URL 'https://web-test3-new:8172/msdeploy.axd?sit
e=TRS'.) [c:\tfs\trsapps\test\Web\Secured Account Access\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : This
error indicates that you cannot connect to the server. Make sure the service URL is correct, firewall and network setti
ngs on this computer and on the server computer are configured properly, and the appropriate services have been started
on the server. [c:\tfs\trsapps\test\Web\Secured Account Access\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : Error
details:\r [c:\tfs\trsapps\test\Web\Secured Account Access\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : Could
not complete the request to remote agent URL 'https://web-test3-new:8172/msdeploy.axd?site=TRS'.\r [c:\tfs\trsapps\tes
t\Web\Secured Account Access\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : The u
nderlying connection was closed: An unexpected error occurred on a send.\r [c:\tfs\trsapps\test\Web\Secured Account Acc
ess\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : Unabl
e to read data from the transport connection: An existing connection was forcibly closed by the remote host.\r [c:\tfs\
trsapps\test\Web\Secured Account Access\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : An ex
isting connection was forcibly closed by the remote host [c:\tfs\trsapps\test\Web\Secured Account Access\Member\TRSSecu
reAccess.vbproj]
Publish failed to deploy.
Done Building Project "c:\tfs\trsapps\test\Web\Secured Account Access\Member\TRSSecureAccess.vbproj" (Clean;Build targe
t(s)) -- FAILED.
Build FAILED.
"c:\tfs\trsapps\test\Web\Secured Account Access\Member\TRSSecureAccess.vbproj" (Clean;Build target) (1) ->
(MSDeployPublish target) ->
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : Web
deployment task failed. (Could not complete the request to remote agent URL 'https://web-test3-new:8172/msdeploy.axd?s
ite=TRS'.) [c:\tfs\trsapps\test\Web\Secured Account Access\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : This
error indicates that you cannot connect to the server. Make sure the service URL is correct, firewall and network setti
ngs on this computer and on the server computer are configured properly, and the appropriate services have been started
on the server. [c:\tfs\trsapps\test\Web\Secured Account Access\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : Error
details:\r [c:\tfs\trsapps\test\Web\Secured Account Access\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : Could
not complete the request to remote agent URL 'https://web-test3-new:8172/msdeploy.axd?site=TRS'.\r [c:\tfs\trsapps\tes
t\Web\Secured Account Access\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : The u
nderlying connection was closed: An unexpected error occurred on a send.\r [c:\tfs\trsapps\test\Web\Secured Account Acc
ess\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : Unabl
e to read data from the transport connection: An existing connection was forcibly closed by the remote host.\r [c:\tfs\
trsapps\test\Web\Secured Account Access\Member\TRSSecureAccess.vbproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): error : An ex
isting connection was forcibly closed by the remote host [c:\tfs\trsapps\test\Web\Secured Account Access\Member\TRSSecu
reAccess.vbproj]
0 Warning(s)
1 Error(s)
Have you installed the server the server side pre-requisites.
This link may help.
I've finally managed to get mono to build from sources, but make install invoked from the top build directory fails at the following point:
make[6]: Entering directory `/bld/mono/mono-4.0.0/mcs/class/System'
make install-local
WARNING: generic atexit() called from legacy shared library
make[7]: Entering directory `/bld/mono/mono-4.0.0/mcs/class/System'
MONO_PATH="./../../class/lib/build:$MONO_PATH" /bld/mono/mono-4.0.0/runtime/mono-wrapper ./../../class/lib/build/gacutil.exe /i ./../../class/lib/net_4_5/System.dll /f /root /usr/mono/lib /package 4.5
make[7]: *** [install-local] Error 1
make[7]: Leaving directory `/bld/mono/mono-4.0.0/mcs/class/System'
make[6]: *** [do-install] Error 2
Error 1 is the only error thrown.
I can run this command without errors
MONO_PATH="./../../class/lib/build:$MONO_PATH" /bld/mono/mono-4.0.0/runtime/mono-wrapper ./../../class/lib/build/gacutil.exe /i ./../../class/lib/net_4_5/System.dll /f /root /usr/mono/lib /package 4.5
And I can run the final command in mono-wrapper without errors
/bld/mono/mono-4.0.0 $ /bld/mono/mono-4.0.0/libtool --verbose --mode=execute "mono/mini/mono" --config "/bld/mono/mono-4.0.0/runtime/etc/mono/config" "mcs/class/lib/build/gacutil.exe" /i mcs/class/lib/net_4_5/System.dll /f /root /usr/mono/lib /package 4.5
But running 'make install' fails. Any ideas?
Running
make --debug=V install
revealed that it was failing when attempting to execute line 197 of mcs/build/library.make, which is:
196 install-local: $(gacutil)
197 $(GACUTIL) /i $(the_lib) /f $(gacdir_flag) /root $(GACROOT) $(package_flag)
Removing the $(package_flag) variable allowed the build to complete successfully. Caveat: I'm not sure if doing so breaks the install in other ways. Just in case...for future reference...here's the relevant entry in 'man gacutil':
COMMANDS
-i <assembly_path> [-check_refs] [-package NAME] [-root ROOTDIR]
[-gacdir GACDIR]
Installs an assembly into the global assembly cache. <assembly_path>
is the name of the file that contains the assembly manifest
The -package option can be used to also create a directory in in pre-
fix/lib/mono with the name NAME, and a symlink is created from
NAME/assembly_name to the assembly on the GAC. This is used so devel-
opers can reference a set of libraries at once.
The -root option is used to specify the "libdir" value of an installa-
tion prefix which differs from the prefix of the system GAC. Typical
automake usage is "-root $(DESTDIR)$(prefix)/lib". To access assem-
blies installed to a prefix other than the mono prefix, it is necessary
to set the MONO_GAC_PREFIX environment variable.
The -gacdir option is included for backward compatibility but is not
recommended for new code. Use the -root option instead.
Basically, -package appears to be optional.
Feel free to edit this with corrections if necessary.