AppD Archive

Installation on Sharepoint Farm will cause Error 500 on Site-Page

CommunityUser
Splunk Employee
Splunk Employee

After the Installation, the SharePoint Site Page will Display Error 500..

But Administration Site is still Good.

AppDynamics Changed the configuration files..?

I am 100% this was caused by AppDynamics, I tested twice with Virtual Machine Snapshot..

Any Fix for this problem..?

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi steven,

Our theory is that the IIS threw this error even before the request reached an entry point so that we could classify the request as a BT and then take a snapshot.

Your event viewer logs may contain more information about why this error occurs. Can you please take a look at the event viewer logs from this time frame and provide us the details. Also share us the appdynamics log files by default located at "C:\Appdynamics\Logs" .

Regards,

Vishwanath K

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi!

I guess that I have the same problem. When I install the lite version SP only displays a 500 error on the application but Central admin works fine. 

The event viewer shows:

".NET Runtime version 4.0.30319.18408 - The profiler was loaded successfully.  Profiler CLSID: 'AppDynamics.AgentProfiler'.  Process ID (decimal): 13688.  Message ID: [0x2507]."

and then from SharePoints Claims Authentication:

"An exception occurred when trying to issue security token: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)."

Log from AgentLog

2013-10-25 15:45:44.2567 3704 w3wp 21 Info ConfigurationChannel Setting local var nodeName = Application-***-SharePoint - ***.local80-0-1-0
2013-10-25 15:45:44.2567 3704 w3wp 21 Info DotNetAppAgentConfigurationRequest Sending node name: Application-***-SharePoint - ***.local80-0-1-0
2013-10-25 15:45:44.2567 3704 w3wp 21 Info ConfigurationChannel Sending Registration request with: Application Name [LocalMachine], Tier Name [Application], Node Name [Application-***-SharePoint - ***.local80-0-1-0], Host Name [***] Node Unique Local ID [Application-***-SharePoint - ***.local80-0-1-0], Version [3.4.0.0]
2013-10-25 15:45:44.2567 3704 w3wp 21 Warn ConfigurationChannel Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [localhost], port[8990], exception [System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)
at System.Net.HttpWebRequest.GetResponse()
at AppDynamics.Agent.Communication.g.lq(Byte[] c, String i)
at com.appdynamics.ee.agent.appagent.dotnet.w.y()]

/Henrik

0 Karma

Theo_Jungeblut
Path Finder

Hi Henrik,

What version of SharePoint are you using?

In general, I would recommend you to try out the Pro trial as it includes many new features, support for new version of frameworks and bug fixes as the lite agent and we have many customer I am aware of using it successfully with SharPpoint.

Kind regards,

Theo

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi!

We are running SP2013 and it looks like the error is specific to claims authentication since the CA site is still working. I know that other profilers have problems with claims applications as well. Do you know if someone of your other customers has it working with claims authentication?

/Henrik

Matt_Jensen
Explorer

Hi Henrik, by default SP2013 uses the legacy code access security model which is less configurable than the latest 4.0 model and not needed in most installations.

 

As you've noticed, our profiler isn't compatible with the legacy model. To resolve the issue, just update the web.config so that legacyCasModel is set to false.

 

<trust level="Full" originUrl="" legacyCasModel="false" /> 

 

Thanks,

Matt

 

 

 

 

CommunityUser
Splunk Employee
Splunk Employee

Hi,

Can you please share the location of "Web.config" file to edit.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

We are also facing the same problem in our sharepoint environment. We have .Net agent v3.9.6. What is the impact on SharePoint application after the following change as you suggested.

To resolve the issue, just update the web.config so that legacyCasModel is set to false.

 

<trust level="Full" originUrl="" legacyCasModel="false" />

Regards,

Shahid

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Thx, that did it!

/Henrik

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...