his is how when I upload your site to my website, so give it problems: MSBuild.Microsoft.VisualStudio.Web.targets.14.0.0.3 It is the only time it makes mistakes that's when it will upload to my App service.
I've tried this:
https://stackoverflow.com/a/19826448/6576684
and download its here: http://www.nuget.org/packages/MSBuild.Microsoft.VisualStudio.Web.targets/
I sit in visual studio 2015 and I have version number: 14.0.25420.01 Update 3
When it gives me error so doing the 10 attempt to create access it or how to explain it.
I also looked at the properties area and neither can I find nothing about it.
With that I looked at it here but is unsure of how to solve it ?: https://blogs.msdn.microsoft.com/webdev/2012/08/21/visual-studio-project-compatibility-and-visualstudioversion/
2>C:\Users\Jesper\Desktop\Sitename\packages\MSBuild.Microsoft.VisualStudio.Web.targets.14.0.0.3\tools\VSToolsPath\Web\Microsoft.Web.Publishing.targets(4276,5): Warning : Retrying the sync because a socket error (10054) occurred.
2>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 10 of 10.
2>C:\Users\Jesper\Desktop\Sitename\packages\MSBuild.Microsoft.VisualStudio.Web.targets.14.0.0.3\tools\VSToolsPath\Web\Microsoft.Web.Publishing.targets(4276,5): Error : Web deployment task failed. (Unable to read data from the transport connection: An existing connection was tvangsafbrudt of a remote host.)
2>Publish failed to deploy.
In Visual Studio 2013.3 I have created a test .Net 4.5 C# MVC 5 project to run in an Azure Website. I created a new Azure a/c and logged into it in VS. When I try and publish the project (running VS as Administator) the Validate Connection fails with no error code. I have re-downloaded the Publish settings from Azure to make sure I have the correct publish settings. The message I get is:
(2014-10-27 11:04:13) An error occurred when the request was processed on the remote computer.
The server experienced an issue processing the request. Contact the server administrator for more information.
When I try and publish the project anyway I get the following message:
C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(4270,5):
Error : Web deployment task failed. ((2014-10-27 11:06:25) An error
occurred when the request was processed on the remote computer.)
(2014-10-27 11:06:25) An error occurred when the request was processed
on the remote computer. The server experienced an issue processing the
request. Contact the server administrator for more information.
Publish failed to deploy.
I have installed the latest Azure SDK for Visual Studio 2013 2.4.1 via MS Web Plaform Installer 5.
The online Azure management pages shows the default website running. I'm running Windows 8.1.
One thing I have noticed is that if I change the sitename in the Publish settings I get:
Could not connect to the remote computer [...] The Remote name could
not be resolved.
Also when I try to ping the remote url i.e. [sitename].scm.azurewebsites.net:443 it times out, however, I can access it via a browser.
[UPDATE]
By Changing the output to verbose I get this message:
(2014-10-27 12:28:01) An error occurred when the request was processed on the remote computer.
The server experienced an issue processing the request. Contact the server administrator for more information.
at Microsoft.Web.Deployment.AgentClientProvider.GetHttpResponse(HttpWebRequest request)
at Microsoft.Web.Deployment.AgentClientProvider.PerformHeadRequestHelper(Boolean getVersionInfo, Version& maximumSupportedVersion, Version& minimumSupportedVersion)
at Microsoft.Web.Deployment.AgentClientProvider..ctor(DeploymentProviderContext providerContext, DeploymentBaseContext baseContext, String serverVersion)
at Microsoft.Web.Deployment.DeploymentManager.CreateObjectPrivate(DeploymentProviderContext providerContext, DeploymentBaseOptions baseOptions, DeploymentObject sourceObject, String serverVersion)
at Microsoft.Web.Deployment.DeploymentManager.CreateDestinationObject(DeploymentProviderOptions providerOptions, DeploymentBaseOptions baseOptions, DeploymentObject sourceObject, String serverVersion)
at Microsoft.Web.Deployment.DeploymentObject.SyncTo(DeploymentProviderOptions providerOptions, DeploymentBaseOptions baseOptions, DeploymentSyncOptions syncOptions)
at CallSite.Target(Closure , CallSite , Object , Object , Object , Object )
at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid4[T0,T1,T2,T3](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3)
at Microsoft.Web.Publishing.Tasks.VSMSDeployObject.SyncTo(VSMSDeployObject destObject, Object syncOptions, IVSMSDeployHost _host)
at CallSite.Target(Closure , CallSite , VSMSDeployObject , VSMSDeployObject , Object , IVSMSDeployHost )
at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid4[T0,T1,T2,T3](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3)
at Microsoft.Web.Publishing.Tasks.BaseMSDeployDriver.InvokeMSdeploySync()
at Microsoft.Web.Publishing.Tasks.VSMSDeployDriverInCmd.StartSync()
at Microsoft.Web.Publishing.Tasks.BaseMSDeployDriver.SyncThruMSDeploy()
at Microsoft.Web.Publishing.Tasks.VSMSDeploy.Execute()
VSMSDeploy: Publish failed to deploy.
Done executing task "VSMSDeploy" -- FAILED.
Many thanks in advance.
Will
I ran to a similar problem while trying to publish Azure Mobile Service. Finally I managed to get rid of the problem by using MSDeploy.exe with -verb:delete parameter. I cannot provide you with the exact command line for your case, but in my case I've downloaded .publishsettings file from Azure Management portal and then I've run the following command:
set MSDeployPath=C:\Program Files\IIS\Microsoft Web Deploy V3\
"%MSDeployPath%"\msdeploy.exe -verb:delete -dest:ContentPath=<site name here>,PublishSettings=<path to downloaded .publishsettings file here>,AuthType='Basic'
Without .publishsettings file you'd have to deal with detailed parameters: computername, username and password.
After running the above command, I could publish my mobile service from VS.
It turned out to be an issue with the Windows region setting I was using. Apparently the region I was using wasn't supported by the VS publish system and Microsoft hadn't a fall back setup. I posted the question on an MSDN forum and a Microsoft engineer worked out what was going on.
I've spent hours trying to setup iisnode and keep getting stuck at this error when I navigate to any of the sample apps:
iisnode encountered an error when processing the request.
HRESULT: 0x2
HTTP status: 500
HTTP reason: Internal Server Error
You are receiving this HTTP 200 response because system.webServer/iisnode/#devErrorsEnabled configuration setting is 'true'.
In addition to the log of stdout and stderr of the node.exe process, consider using debugging and ETW traces to further diagnose the problem.
The node.exe process has not written any information to stderr or iisnode was unable to capture this information. Frequent reason is that the iisnode module is unable to create a log file to capture stdout and stderr output from node.exe. Please check that the identity of the IIS application pool running the node.js application has read and write access permissions to the directory on the server where the node.js application is located. Alternatively you can disable logging by setting system.webServer/iisnode/#loggingEnabled element of web.config to 'false'.
-The iisnode/www folder is readable/writable for iusr and iis_iusrs
-Node.exe is executable by them too
-There is a mapping setup for each of the sample applications in web.config and I can see this in iis as well.
-I've also tried x64 bit versions of iisnode and nodejs without any difference in the error
-application pool is set to enable 32-bit applications
I'm out of ideas as to what to do other than install some previous version. Anyone run into this problem and find a solution?
edit: etw trace -- http://pastebin.com/heHTpCei
So just recently my main computer has started having an issue with the Window Azure emulator. When I try and debug my solution using the emulator it just ends up looping through trying to connect.
This is what I get in the output window:
> iisexpress.exe Warning: 0 : WARNING: <SimpleSendReceiveModule> d8c9fa85-ded3-48ad-94a3-ec31e2123bb3:Request - 1, result - Status=ChannelOpenFailed[System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.255.0.0:20004
at Microsoft.ApplicationServer.Caching.AsyncResultNoResult.EndInvoke()
at Microsoft.ApplicationServer.Caching.AsyncResult`1.EndInvoke()
at Microsoft.ApplicationServer.Caching.TcpClientChannelFactory.EndConnect(IAsyncResult asyncResult)
at
Microsoft.ApplicationServer.Caching.TcpClientChannel.ConnectionCallback(IAsyncResult result)] for end point [net.tcp://127.255.0.0:20004]
Microsoft.WindowsAzure.ServiceRuntime Verbose: 500 : Role instance status check starting
Microsoft.WindowsAzure.ServiceRuntime Verbose: 502 : Role instance status check succeeded: Ready
Microsoft.WindowsAzure.ServiceRuntime Verbose: 500 : Role instance status check starting
Microsoft.WindowsAzure.ServiceRuntime Verbose: 502 : Role instance status check succeeded: Ready
Microsoft.WindowsAzure.ServiceRuntime Verbose: 500 : Role instance status check starting
Microsoft.WindowsAzure.ServiceRuntime Verbose: 502 : Role instance status check succeeded: Ready
Microsoft.WindowsAzure.ServiceRuntime Verbose: 500 : Role instance status check starting
Microsoft.WindowsAzure.ServiceRuntime Verbose: 502 : Role instance status check succeeded: Ready
iisexpress.exe Warning: 0 : WARNING: <DistributedCache.SocketClientChannel.1> Request 1 to host net.tcp://127.255.0.0:20004/ failed Status=ChannelOpenFailed[System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.255.0.0:20004
at Microsoft.ApplicationServer.Caching.AsyncResultNoResult.EndInvoke()
at Microsoft.ApplicationServer.Caching.AsyncResult`1.EndInvoke()
at Microsoft.ApplicationServer.Caching.TcpClientChannelFactory.EndConnect(IAsyncResult asyncResult)
at Microsoft.ApplicationServer.Caching.TcpClientChannel.ConnectionCallback(IAsyncResult result)]
iisexpress.exe Warning: 0 : WARNING: <SimpleSendReceiveModule> d8c9fa85-ded3-48ad-94a3-ec31e2123bb3:Request - 1, result - Status=ChannelOpenFailed[System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.255.0.0:20004
Through research I've found that the 127.255.X.X ip is the ip that the emulator makes from it's internal load balancer. What I don't understand is why my machine just decided it doesn't want to accept this connection. I've turned off all my firewalls, reinstalled visual studio, completely reinstalled windows azure and still no luck. It's definitely not code based because my colleagues and my secondary machine have no issues. However, working with my seconday machine is not preferable so I'd like to get this one working and I'd like to find a solution that doesnt involve completely formatting my machine which is about where my knowledge is at at this point.
Currently running the October 2012 release of azure, visual studio 2012 and .net 4.5.
Any help would be appreciated.
I had a similar problem with Azure SDK 2.0 under Windows 8, while I had no problem with Azure SDK 1.8 under Windows 7. Like you I've initially thought of a network related problem. I then tried to disable caching and noticed that other roles in my cloud projects correctly noticed that the caching service was unavailable with another error message.
In my experience, it is likely that the issue is related to your regional settings, in particular to the way Long Time format is specified. I discovered from this SO question that the cache emulator uses logman.exe for logging purposes and it passes a duration to the cnf parameter using the Long Time format from regional settings (for example HH.mm.ss in my Windows 8 machine with Italian settings) -- but in fact cnf requires the duration to be exactly in the format HH:mm:ss (with the colons instead of the dots). After I've changed the Long Time format, caching started working correctly in Computer Emulator.
You may also consider these solutions:
reboot your computer, as suggested in this thread on MSDN forums;
use two instances for the cache, as suggested in this SO thread.
I am trying to access a shared folder in my company network via JCIFS. But when i try to list the files under the shared folder, it throws an SmbException as below,
jcifs.smb.SmbException: 0xC000009A
at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:563)
at jcifs.smb.SmbTransport.send(SmbTransport.java:663)
at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:316)
at jcifs.smb.SmbSession.send(SmbSession.java:218)
at jcifs.smb.SmbTree.treeConnect(SmbTree.java:176)
at jcifs.smb.SmbFile.doConnect(SmbFile.java:911)
at jcifs.smb.SmbFile.connect(SmbFile.java:954)
at jcifs.smb.SmbFile.connect0(SmbFile.java:880)
at jcifs.smb.SmbFile.getType(SmbFile.java:1282)
at jcifs.smb.SmbFile.doEnum(SmbFile.java:1733)
at jcifs.smb.SmbFile.listFiles(SmbFile.java:1715)
at jcifs.smb.SmbFile.listFiles(SmbFile.java:1648)
0xC000009A says it is a NT_STATUS_INSUFFICIENT_RESOURCES but what do i have to do to fix this. The shared folder is only accessible by myself. I used the follwoing url format.
smb://domain;username:password#ip-address/<foldername>
Appreciate your help.
I faced same error developing file upload to windows shares using JCIFS.
It turned out, target windows machine had an error entry in system log:
Source: srv
Event ID: 2017
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SERVER01
Description: The server was unable to allocate from the
system nonpaged pool because the server reached the configured limit
for nonpaged pool allocations.
This error is (possibly) caused by using an older (SMB1, e.g. Windows XP prooflink) version of the protocol when connecting to modern (Vista and above) versions of Windows.
This article contains a workaround for the problem. It requires editing the target machine's registry values, so I can't call it a full solution.
Updated link for the registry changes needed:
https://social.technet.microsoft.com/Forums/windows/en-US/30919e4f-6810-48d6-8769-2cff61f07544/event-id-2017-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-server?forum=w7itpronetworking