none
General Network Error. Check your network documentation RRS feed

  • Question

  • Hi,

    I am using .Net 1.1 for my web application.

    And my database server is SQL Server 2005.

    My application is running fine, as i can login to it and also able to view pages. But when i open Order management(having 3K records) its give me error,

    General Network Error. Check your network documentation

     

    I have also searched many articles  and tried following solutions but nothing working

    - connectiontimeout = 0, max pool size = 7500/100, pooling = false

    - SSL disabling enforce security false as mentioned in microsoft kb article.

    And there's  nothing any issue with hardware/firewall as my application's login and other forms are working fine(which use same database with same connection string)

     

    Can any one please help me to solve this error?
    Thursday, October 4, 2007 5:17 AM

Answers

  • Hi,

    Finally i got solution.

    that rather then adding connectiontimeout = 0 in connection string.

    We have to assign it in command property.

    cmd.ConnectionTimeout = 0

    because if we didn't assign in command microsoft internally set it's default value.

    If you see SqlCommand class code by disassemble, in it's constructor  it set this property  to 30.
    so if you not assign value 0 its default value is 30. it can not take  value from  connection  string.


    And it's working fine.

    Finally i got so now i can take breath, otherwise my client calling me every 15-20 mins for solution.

    Friday, October 5, 2007 4:18 AM

All replies

  • Hi Mayank,

     

    Hava a look at below article. Do fix even if you are not using SSL, to just see if it works or not. Probably you can try first checking with data being returned in query analyzer, then you try in SQL Profiler (admin rights req) to see what exactly is being passed. If all works okay, then try to minimize number of records in result set for a time being. If then it works okay that means may something to do with bandwidth or so on. Try this out n let me know.

     

    http://support.microsoft.com/kb/821289

     

    Regards

     

    Nikunj Thakkar

     

    Thursday, October 4, 2007 12:37 PM
  • Hi,

    Finally i got solution.

    that rather then adding connectiontimeout = 0 in connection string.

    We have to assign it in command property.

    cmd.ConnectionTimeout = 0

    because if we didn't assign in command microsoft internally set it's default value.

    If you see SqlCommand class code by disassemble, in it's constructor  it set this property  to 30.
    so if you not assign value 0 its default value is 30. it can not take  value from  connection  string.


    And it's working fine.

    Finally i got so now i can take breath, otherwise my client calling me every 15-20 mins for solution.

    Friday, October 5, 2007 4:18 AM