Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM 2011 Tracing Won't Turn Off RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've checked through all the forums and tried everything to no avail.

    I've rebooted, reset IIS, used the CRMDiag tool, updated the MSCRM_CONFIG.dbo.OrganizationProperties table, changed the registry settings, stopped and restarted AppPools.  

    I'm generating close to 100MB per minute on my CRM 2011 server and performance is suffering.  Can anyone offer a solution to this issue?

    I'm unable to change the trace settings through PowerShell. I had initially enabled tracing through PowerShell, but now it times out. I had initially enabled it in Verbose mode to troubleshoot some issues I was having with Claims Based Authentication. Here is my PowerShell Code and Errors:

    Windows PowerShell
    Copyright (C) 2009 Microsoft Corporation. All rights reserved.

    PS C:\Users\administrator> Add-PSSnapin Microsoft.Crm.PowerShell
    PS C:\Users\administrator> try {Get-CrmSetting TraceSettings}
    >> catch
    >> {
    >> echo $("Error| " + $_.Exception)
    >>
    >> echo $("Error| Stacktrace: " + $_.Exception.Stacktrace)
    >>
    >> if($_.Exception.GetType() -eq [System.ServiceModel.FaultException[Microsoft.Xrm.Sdk.Deployment.DeploymentServiceFault
    ]])
    >> {
    >> echo $("Error| Details: ")
    >> foreach ($edwError in $_.Exception.Detail.ErrorDetails)
    >> {
    >> echo $($edwError.Key + ": " + $edwError.Value)
    >> }
    >> }
    >>
    >> break
    >> }
    >>
    Error| System.Net.WebException: The operation has timed out
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.Crm.PowerShell.DeploymentServiceFactory.GetDeploymentServicePrincipalName(String dwsAddress)
       at Microsoft.Crm.PowerShell.DeploymentServiceFactory.GetEndpointIdentity(String dwsAddress)
       at Microsoft.Crm.PowerShell.DeploymentServiceFactory.CreateDeploymentService()
       at Microsoft.Crm.PowerShell.DeploymentCmdletCommand.get_DeploymentService()
       at Microsoft.Crm.PowerShell.GetCrmSettingCmdlet.ProcessRecordInternal()
       at Microsoft.Crm.PowerShell.DeploymentCmdletCommand.ProcessRecord()
       at System.Management.Automation.CommandProcessor.ProcessRecord()
    Error| Stacktrace:    at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.Crm.PowerShell.DeploymentServiceFactory.GetDeploymentServicePrincipalName(String dwsAddress)
       at Microsoft.Crm.PowerShell.DeploymentServiceFactory.GetEndpointIdentity(String dwsAddress)
       at Microsoft.Crm.PowerShell.DeploymentServiceFactory.CreateDeploymentService()
       at Microsoft.Crm.PowerShell.DeploymentCmdletCommand.get_DeploymentService()
       at Microsoft.Crm.PowerShell.GetCrmSettingCmdlet.ProcessRecordInternal()
       at Microsoft.Crm.PowerShell.DeploymentCmdletCommand.ProcessRecord()
       at System.Management.Automation.CommandProcessor.ProcessRecord()
    PS C:\Users\administrator>

    Thanks,

    Susan

    Susan

    Wednesday, January 8, 2014 6:06 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Database Settings:

    Registry Settings:

    CRM Trace Log Header:

    # CRM Tracing Version 2.0
    # LocalTime: 2014-01-08 13:20:22.933
    # Categories: Exception.*:Error
    # CallStackOn: Yes
    # ComputerName: SERVER1
    # CRMVersion: 5.0.9900.1060
    # DeploymentType: OnPremise
    # ScaleGroup:
    # ServerRole: AppServer, AsyncService, DiscoveryService, ApiServer, HelpServer, DeploymentService, SandboxServer, DeploymentManagementTools

    Susan

    Wednesday, January 8, 2014 6:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    1. Try manually changing the value in the TraceRefresh key in the registry.  Step the value up or down to let the system know that there has been a change.

    2. Have you added Oledbtimeout or ExtendedTimeOut keys to the CRM registry?  If so, remove these and let CRM fall to the default values.  It is not good practice to leave these keys in place beyond troubleshooting purposes.

    3. Check the deployment manager and confirm the url's are correct.

    4. Have there been any changes made to IIS, especially timeout values?  Do you have more than one http and https binding?

    5. Is the environment patched to current level released by Microsoft?

    6. Is there more than one CRM server you are dealing with in this environment?

    7. Has your permission to the deployment manager and/or permissions to the mscrm_config database changed?  Just wondering if the timeout message is showing instead of a permission error.

    Jason Peterson

    Thursday, January 9, 2014 10:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    1. Tried this, no change.

    2. I do not have those values.

    3. URL's are correct.

    4. No changes to IIS and only one binding

    5. Environment is current

    6. This is one CRM server.

    7. No permission changes.

    Susan

    Thursday, January 9, 2014 6:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Any help with this would be appreciated.  This server is suffering from a performance perspective and the hard drive is filling up daily.

    Thanks,


    Susan

    Susan

    Wednesday, January 15, 2014 3:45 PM