Endpoint Protection

 View Only
  • 1.  SQL error

    Posted Sep 29, 2009 01:40 AM
    I have this error when i login to the Symantec Endpoint Manager Console. In the HOME PAGE it just take 2 or 3 minutes i prompt just like this.


     The database query time out. Try to reduce the number of filters, or increasing the sql server query timeout value
     An unexpected error occured. Try running the query again by using default filters values.
    String encoding was possible not UTF-8, and may result from copying and paste data instead of typing data, try type data in the input field.



    My database is Microsoft SQL2005.I not familar with microsoft sql 2005 server and how to add  and how to fix. Please help me.


  • 2.  RE: SQL error

    Broadcom Employee
    Posted Sep 29, 2009 01:58 AM


  • 3.  RE: SQL error

    Posted Sep 29, 2009 04:35 AM
    Thank you for your reply. I try your solution but it won't work.do you have another solution?


  • 4.  RE: SQL error

    Posted Sep 29, 2009 04:58 AM
    Pete has sent a good article, try doing a repair of

    try this step again.

    To change the IIS Connection timeout
    1. On the Windows taskbar, click Start > Run.
    2. In the Open box, type the following text:

      services.msc

       
    3. Click OK.
    4. In the right pane, right-click World Wide Web Publishing, and then click Stop.
    5. On the Windows taskbar, click Start > Programs > Administrative Tools > Internet Information Services.
    6. In the left pane, expand Web Sites.
    7. Right-click Default Web Site and then click Properties.
    8. On the Web site tab, under Connections, in the Connection Timeout box, type the value that you want (in seconds).
    9. Click OK.
    10. On the Windows taskbar, click Start > Run.
    11. In the Open box, type the following text:

      services.msc

       
    12. Click OK.
    13. In the right pane, right-click World Wide Web Publishing, and then click Start


  • 5.  RE: SQL error

    Broadcom Employee
    Posted Sep 29, 2009 05:15 AM
    try keep on increasing timeout values also you may reindex the SQL server.