OK.
Here's what I am running:
Intellitrace Collector (powershell 2.0, from VS 2012)
Windows Server 2003, running IIS 6
The target application to be traced is a web service (asmx, ASP.NET 2.0.50727)
Here's what I've done & what happened:
cmdlet Start-IntelliTraceCollection at command pipeline position 1
Supply values for the following parameters:
OutputPath: logs
Start-IntelliTraceCollection : An error occurred during website instrumentation
: Internet Information Services could not be found on the machine.
At line:1 char:29
+ Start-IntelliTraceCollection <<<< MyAppPool .\collection_plan.ASP.NE
T.trace.xml
+ CategoryInfo : NotSpecified: (:) [Start-IntelliTraceCollection]
, IISLegacyVersionException
+ FullyQualifiedErrorId : Microsoft.VisualStudio.Enterprise.WebInstrument.
IISLegacyVersionException,Microsoft.VisualStudio.IntelliTrace.PowerShell.S
tartIntelliTraceCollectionCommand
I tried running powershell as administrator - it didn't help (same error message)
Am I missing something here ?
Is any of the components I mentioned not supported ? ie: version of IIS, version of Windows Server ? I am suspicious that the IIS version isn't supported (IISLegacyVersionException was raised)
Much appreciated for your time + attention.
Cheers.
This Microsoft page on collecting IntelliTrace data from IIS using the standalone collector using VS2012 mentions
ASP.NET Web apps hosted on Internet Information Services (IIS) version 7.0, 7.5, and 8.0
as a requirement, so you're right, IIS6 is not supported.
Related
Installed VS2019 on Windows 7.
Created ASP.NET web application from template.
Do nothing.
Run project "IIS Express + FireFox"
Get message about installing development certificate and running site under HTTPS
Accept certificate and IIS starts site on https://localhost:43315
Get error from browser Error code: SSL_ERROR_UNSUPPORTED_VERSION
Switching to Edge, I get NET::ERR_SSL_OBSOLETE_VERSION
Have tried :
https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-troubleshoot
https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client
https://support.microsoft.com/en-gb/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi
https://www.pluralsight.com/guides/visual-studio-2017-resolving-ssl-tls-connections-problems-with-iis-express
But have had no luck.
So as far as I can see:
I have a cert
The site is running on the right port range
Checking all the registry values (and many reboots) suggests TLS 1.2 is available.
so what's wrong ?
Thanks in advance all.
My Environment
.NetCore SDk - 2.1.300
Microsoft.AspNetCore.SignalR - 1.0.0
IIS - Version 10.0.12393.0 in Window Server 2016
Sample Code for AspNetCore.SignalR
I follow the instructions by link https://learn.microsoft.com/en-us/aspnet/core/signalr/get-started?view=aspnetcore-2.1&tabs=visual-studio to complete a sample AspNetCore.SignalR chat code.
I can run it successfully in Visual Studio.
After that, I publish it to my server (window server 2016, IIS has websocket feature), and it also works fine. That means, my server environment support AspNetCore.SignalR well.
Abp for AspNetCore.SignalR
I download the ABP template code from ABP website
Upgrade the .net core sdk to .net core 2.1
Upgrade nuget packages
Follow my above steps to add sample AspNetCore.SignalR chat code in the project.
Run it successfully in visual studio
The issue is, when I publish it to the server (same as my above server), and run it, it throws a error - AspNetCore.SignalR.HubConnectionContext - Failed connection handshake.
I have research it, but didn't get any solution. could you please help to look at it what the issue is?
I have push my project into github: https://github.com/lcyhjx/AbpExample, you can pull and run it (Just run AbpExample.Web.Host). It works fine in Visual Studio, but failed in IIS.
The error detail:
Information: Normalizing '/chatHub' to 'http://localhost:6011/chatHub'.
Information: WebSocket connected to ws://localhost:6011/chatHub?id=2zix_nPHODwLEv2p_4VCAw'
Error: Connection disconnected with error 'Error: Server returned handshake error: An unexpected error occurred during connection handshake.'.
I have addressed the issue. It's a code issue, in my code I have set
HandshakeTimeout = TimeSpan.MaxValue;
If I comment above code, then all works fine in both VS and IIS.
The same here, but a bit different: I ran the server in Rider and everything worked. I put it in another directory and I've got handshake errors. Removing the handshake timeout and it works everywhere.
I'm investigating an issue with the asp.net core 1.1 web app.
We had to install the latest VS 2017 on the build server. And straight after that, all the deployed builds return 502 responses. Nothing changed in the app code or the referenced packages, however, many binaries are different after VS 2017 install. The deployment is done via FTP.
I also noticed there is now a small difference in Http response headers. API Response Headers used to have Server: Kestrel. But now, after installing VS2017, the deployed builds return Server: Microsoft-IIS/10.0. This probably explains 502 error, but why would the Server now switch to IIS?
Managed to fix it. The error is caused because IIS server (proxy) can't access AspNetCoreModule, the process that hosts kestrel. Usually, the reason is because kestrel in some trouble.
The solution starts with checking Application logs in Event Viewer on the server.
In my case it was:
Application 'MACHINE/WEBROOT/APPHOST/MyApp.API' with physical root '\servername\c$\inetpub\wwwroot\MyApp.Api\' failed to start process with commandline '"dotnet" .\MyApp.Api.Web.dll', ErrorCode = '0x80004005 : 80008083.
So, by googling the error code I've realised that the server didn't have the right asp.net core version (for some reason).
Downloaded the installer, works fine now! :)
I got a new laptop for my job and was thinking about installing Win8 CP as my main operating system, I love it, so I tried to do some tests in a VM to see if AppFabric cache can work in Win8 CP. The official response from MS is "AppFabric is not supported in Win8 and we would tell you how to run it when Win8 is released" and of course that is not a nice answer for me, so I tried... and failed...
After installing .Net 3.5SP1 and latest updates AppFabric cache was installed and configured without any problem in my Win8 machine using my local user and a XML provider in a shared folder, I gave permissions and everything to that folder...
The first problem is that the Cache Administrator Console answer back with this message every time I open it:
Use-CacheCluster : ErrorCode<ERRCAdmin040>:SubStatus<ES0001>:Failed to connect
to hosts in the cluster At line:1 char:46
+ Import-Module DistributedCacheAdministration;Use-CacheCluster
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Use-CacheCluster], DataCacheException
+ FullyQualifiedErrorId : Microsoft.ApplicationServer.Caching.DataCacheException,Microsoft.ApplicationServer.Caching.Commands.UseCacheClusterCommand
PS C:\Windows\system32>
Well, looks like something is not right... let's try to start the cache cluster
PS C:\Windows\system32> start-cachecluster
HostName : CachePort Service Name Service Status Version Info
-------------------- ------------ -------------- ------------
win8:22233 AppFabricCachingService UP 0 [0,0][0,0]
PS C:\Windows\system32>
The version info answer is not right at all, so problably create a new cache would fail
PS C:\Windows\system32> new-cache IPE
New-Cache : Object reference not set to an instance of an object.
At line:1 char:1
+ new-cache IPE
+ ~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-Cache], NullReferenceExce
ption
+ FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Applicat
ionServer.Caching.Commands.NewCacheCommand
PS C:\Windows\system32>
And pretty much that's all...
I tried everything I could find in the internet:
Starting the Remote
Registry Service Modifying the host file in windows/system32/drivers/etc/host to place an explicit entry to localhost and my machine name
Checking permissions
Installing updates
Opening firewall rules
(For the firewall rules I tried something like this)
netsh advfirewall firewall set rule group="Windows Server AppFabric: AppFabric Caching Service" new enable=Yes
netsh advfirewall firewall set rule name="Remote Service Management (RPC)" profile=domain new enable=Yes
netsh advfirewall firewall set rule name="Remote Service Management (RPC-EPMAP)" profile=domain new enable=Yes
netsh advfirewall firewall set rule name="Remote Service Management (NP-In)" profile=domain new enable=Yes
And still getting the same problem... I have no idea where to start or continue to fix the problem... I would really appreciate any help, and yes, would be really really hard for me to wait until Win8 official release.
Start the Remote Registry service, if not started. AppFabric uses this service even to connect to your local machine
link
I am trying to generate a WCF proxy client code for a Windows mobile application that uses basicHttpBinding and I'm continuously receiving the follow error:
Error: An error occurred in the tool.
Error: Error in the application
I was able to generate the proxy before but I don't know why suddenly this happens.
I have read the Sameh Samir's post but the service I use doesn't use any Message Contracts created by me (I've used LINQ to SQL ORD) and the WCFTestClient can connect to the service and shows the contracts.
UPDATE
It seems the problem was with the Windows 7 RC1. I was trying it on Win7 and after running the NetCFSvcUtil on XP everything works just fine.
Anyone knows how can I report this problem to the Microsoft?
THere is now a new tool available that replaces the older version of NetCFSvcUtil. It came out on Monday, August 10, 2009. It can be downloaded at the following link:
http://download.microsoft.com/download/6/2/0/6205ED05-E435-44FC-AA82-B763CA5F8B1A/NetCFSvcUtil.exe
Best of luck!
I found this: http://blogs.msdn.com/habibh/archive/2009/06/26/netcfsvcutil-exe-and-windows-7.aspx
Basically, it states:
Currently, there are no fixes available for this issue. The only workaround is to run NetCFSvcUtil.exe on Windows Vista (SP1 or earlier) or Windows Server 2008 (SP1 or earlier) and then copy the generated client code to other machines.