application crashed after installed .Net agent

[CommunityUser]

Hi all,

Once my customer installed .Net agent on their test environment, the application crashed immediately and alert the exception below.

Dose the BT header matter?

Thanks for reading!

************** 例外狀況文字 **************    (Exception)
System.Net.WebException: 基礎連接已關閉: 連接意外關閉。  

(System.Net.WebException: The underlying connection was closed)

Server stack trace:
   於 System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessResponseException(WebException webException, HttpWebResponse& response)
   於 System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   於 System.Runtime.Remoting.Channels.SoapClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
   於 System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   於 System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   於 UMC.Monitor.DataAccess.WebCfgAccess.GetPrivilege(String iGroup)
   於 UMC.Monitor.MonitorUI.LogInInfo.Login_Info..ctor(String iUserID, String iGroup)
   於 UMC.Monitor.MonitorUI.MainForm.MainForm_Load(Object sender, EventArgs e)
   於 System.Windows.Forms.Form.OnLoad(EventArgs e)
   於 System.Windows.Forms.Form.OnCreateControl()
   於 System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   於 System.Windows.Forms.Control.CreateControl()
   於 System.Windows.Forms.Control.WmShowWindow(Message& m)
   於 System.Windows.Forms.Control.WndProc(Message& m)
   於 System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   於 System.Windows.Forms.ContainerControl.WndProc(Message& m)
   於 System.Windows.Forms.Form.WmShowWindow(Message& m)
   於 System.Windows.Forms.Form.WndProc(Message& m)
   於 System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   於 System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   於 System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[CommunityUser]

Hi,

are you sure, this is due to the installation of the agents?

Seems to me as if there was a connectivity-problem while issuing a remoting (?) call.

Does it work again, when uninstalling the client (or just removing the config-portion for AD) ?

Regards,

Kristof

[CommunityUser]

Hi Kristof,

After removing the Application Servce agent, the customer's applicaiton works, again.

So I wonder what matters.

[CommunityUser]

Hi again.

which version of AppDynamics Agents are you using? We faced problems with crashing App-Pools with a 3.5 release. However this might not be the case with your application as it seems to crash right after startup.

So first of all we need to clarify which portion of the app crashes and what type of application this is. Is it the front-end or the remote-service which crashes? What kind of front-end are you using (ASP.NET, MVC, Silverlight, WinForms...) and what type of services are you calling (WCF, Web-Service, Remoting...).

Secondly we should try to verify whether it is the application which produces the exception or the agent. From you call-stack I think it has to be your application, however you should verify that the concerned servers can connect to your controller on the configured port (try to issue a telnet-session on that port from each of the servers).

And then: Maybe the agents' logfiles contain information which is relevant...

Sorry for not being able to help you right away - I'll keep trying 😉

-Kristof

[CommunityUser]

Hi,

1. The version of AppDynamics is 3.6.4.38.

2. It was remoting service fail.

3. The Front End is WinForm.

4. Please find the attached logfile.

Thanks!!

[Robert_Petty]

Chris,

Can you please zip your entire logs folder and provide the configuration you are using so I can inspect for any obvious problems?

I also have noticed the coordinator is not configured correctly as it is not pointing to the controller you are using.  Please open the application.config and put in the host name and any other settings that are missing or incorrect then restart the Coordinator service. 

Thanks.

Rob