workflow foundation - Windows Service Starts then Stops -


I have a Windows service that I inherited from a vendor developer. Windows service is just fine in the QA environment when I install the service and run it locally, I get this error:

The service can not be started System.InvalidOperationException: The requested display Counter is not a custom counter, it has to be started as a read only.

Here is the code:

  ExternalDataExchangeService ExchangeService = new ExternalDataExchangeService (new)); WorkflowRuntime.AddService (exchangeService); WorkflowRuntime.edseva (new SQL Tracking service (app contact. SCL connectionimplogorg)); ChallengerWorkflowService challengerWorkflowService = New ChallengerWorkflowService (); ChallengerWorkflowService.SendDataEvent + = New EventHandler & lt; SendDataEventArgs & gt; (ChallengerWorkflowService_SendDataEvent); WorkflowRuntime.AddService (challengerWorkflowService); WorkflowRuntime.StartRuntime (); & Lt; ---- The exception is thrown here.  

Check the installer code. Often you will find that counters are created within the installation (which is being run on the client site under admin investigation) and codes then use them as they exist - but they will not try to make it because they expect Not permissions

If you get the source and then try to run it, the counter / counter class is not present, then you fall immediately (optionally check whether the counter exists or you have local Administrator if they have made the code in service.)

Previously it was mentioned.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

jquery - SimpleModal Confirm fails to submit form -

php - Multiple Select with Explode: only returns the word "Array" -