Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
17415 - event every minute - consumes CPU on server as if I have virus or malware RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am on Server 2003 and CRM 4 Rollup 6

     

    Host VS-722_VDS-101: error while processing organization 107efd8a-ca1a-dd11-a1e6-000002ae842c. Exception: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

    The statement has been terminated.

    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

    at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

    at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

    at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean

     

    We just need to extend the OLEDBTimeoutvalue and add a new DWORD key ‘ExtendedTimeout’. You can create the 2 keys if does not exist. By right OLEDBTimeout is already inserted during installation.
    1.Run >regeditexpand the tree to
    >HKEY_LOCAL_MACH INE\SOFTWARE\Microsoft\MSCRM Change the default value 30 on OLEDBTimeout to the seconds you prefer. (Modify by Decimal)Next, right click MSCRM, NEW DWORD rename to ‘ExtendedTimeout’. (Modify the Decimalvalue to 1 000000)lmportant: in Decimal value do not type value larger than 2,147,4831647After you successful run those ‘resources hungry’ tasks, set back to original value. Delte those key that previously does not exist.
    Additional Comments
    http:1/eastoceantechnical.blogspot.com/2009/02/timeout- during- heavyl oaded- tasks- on.html

    I added those 2 new KEYS and it has seemed to stop the error events. The cpu though is still very slow. But still no tasks are showing as consuming all the cpu.

    Friday, April 16, 2010 12:42 AM

Answers