I'm trying connect to an in-process StreamInsight host running in Visual Studio (as opposed to the windows service version) using the Event Flow Debugger tool, and I have been unsuccessful.
Does anyone have experience with this? I'm looking at the following blog posts:
End to end StreamInsight example: http://blogs.msdn.com/b/masimms/archive/2010/08/10/building-your-first-end-to-end-streaminsight-application.aspx
In-process vs. Standalone Host deployment models: http://seroter.wordpress.com/2010/06/27/leveraging-and-managing-the-streaminsight-standalone-host/
You need to explicitly open up a WCF management service endpoint for any embedded StreamInsight host. You can choose any URL that you have permission to create. Once you start up your embedded server with the management point host opened, you can connect the Event Flow Debugger to the URL chosen.
For the standalone host, there is an entry in the StreamInsight.exe.config file that holds the management service endpoint URL used by the standalone Windows Service. This host is automatically opened when you start the Windows Service associated with the instance.
Related
I am trying to remote debug web application by using Remote debugger (msvsmon.exe)
I am connecting ok and can see processes problem is server is running multiple applications and I am not sure which one to attach debugger to. One that I am trying to debug is not listed in IIS APPPOOL\... (should it be?) which I have hidden from screencap.
How can I tell which process to attach to?
1. If you have RDC (Remote Desktop Connection) to the server machine, then in IIS Manager (Internet Information Services Manager) you can see which ones are Network Services and which ones are Local Services.
I was lucky to get one that was Local Services which I had only one running on that server...
2. user friendly way
On the server go to IIS Manager -> Worker Procesess -> then you can match IDs to the IDs in attach to debugger window in Visual Studio...
3. Another way that can give you some insight is to use IDs of processes - IDs in your VS attach to process window can be matched to remote machine IDs (they are also in Task Manager on the server...)
To match ID to application pools on server run Command Prompt - As Administrator and run from %windir%\system32\intesrv\ folder command - appcmd list wp to get process ID to application pool mapping, this might help to narrow it down....
When you know which app pool which process is running, you can map them to applications that are running on that app pool in IIS Manager and pray that they will be one-to-one application to pool...
I know this is old but I ran into this because I was researching something relative.
Although you should be able to identify the process by the UserName column. You should go onto the server and identify the app pool your app is running under. Then you can look for that App Pool name in the UserName column.
On the other hand, you can go onto your server and follow the instructions below to get a full list.
Go to C:\Windows\System32\inetsrv\ in your windows explorer. Enter the command “appcmd.exe list wp”. It will list all the process associated with the Application Pools.
I managed to get remote debugging working on our Windows Server 2008 R2 Server running some ASP.Net WebSites manually (not as a service)
However, I want to run it as a service and I can't figure out how to set it for no authentication as a service or how to specify what users have access to connect to it.
Does anyone know if it has a manual config file somewhere I can modify in notepad, or something of that nature?
we want to connect the Azure database by using console application. my application sheduled in system it has dynamic IP. so i have problem to connect Sql Azure.
then developed a webservice and hosted in windows azure and consumed the web service from console still we have same issue.
please suggest
If you know the IP range, you can allow the entire range on the database firewall. It's not very elegant but will work.
When I create a new "WCF Service Application" in Visual Studio and right-click Service1.svc, I can choose "View in Browser". A web browser appears showing http://localhost:50311/Service1.svc, which says
Service1 Service
You have created a service.
To test this service, you will need to create a client and use it to call the service. You can do this using the svcutil.exe tool from the command line with the following syntax:
svcutil.exe http://localhost:50311/Service1.svc?wsdl
...
The service somehow seems tied to Visual Studio itself, since the web page becomes inaccessible if I close the solution. What's going on? I don't have a web server installed, and I didn't (knowingly) start the service. What is the source of the displayed web page, and why is it on port 50311? Can the page be customized?
What you're seeing is the development web server that starts when you run a debugger instance of a project that requires a web server. (WCF, ASP.NET).
The port 50311 is determined by your project settings (most likely random, but you can specify).
The page for a .svc file is not meant to be customized. Since the service is waiting for a caller, that default page simply tells you that it's running properly.
Keep in mind that WCF offers several binding options that use various protocols (HTTP, TCP). Depending on the protocol that you choose, you will have to host in either IIS, a Windows Service or elsewhere. By default, new services will adopt a binding that works in IIS.
Check out Introduction to Building Windows Communication Foundation Services
I have a windows service in which i host a wcf service.
What is the best approach to control the windows service via the wcf service? I already created the interfaces for the wcf service, but I have no idea how to interact with the windows service's classes and functions.
just to check that I'm understanding your problem correctly - you want to run a wcf service, so you create a windows service to host it, and you want your desktop client to be able to control the windows service (that's hosting the wcf service) by talking to the wcf service?
If that's the case, what is it that you're trying to do with the windows service? In some of the work I've done, I've set up the server such that there's the windows service hosting all the wcf services I want to run, and in order to interact with that windows service remotely (e.g. starting/stopping/restarting) I have another service running on the server (usually baked into the Amazon instance image so it's running on every new server that gets brought up) which my remote client can talk to instead. That way I have a means to trigger a service restart on all my servers without having to manually connect/remote desktop to each server. Of course, the second wcf service is secured by some means so it can't be exploited easily.
Is that the sort of thing you're looking to do?