1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

.NET Runtime 2.0 Error Reporting

Discussion in 'Windows Server System' started by griffmaster, 2007/01/18.

  1. 2007/01/18
    griffmaster

    griffmaster Inactive Thread Starter

    Joined:
    2006/09/12
    Messages:
    88
    Likes Received:
    0
    I get my Server Performance Report (email) I get the following error.

    .NET Runtime 2.0 Error Reporting 5000 18/01/2007 00:57 1
    EventType clr20r3, P1 logwrite.exe, P2 1.0.0.0, P3 4498ead6, P4 mscorlib, P5 2.0.0.0, P6 4333ab80, P7 32f8, P8 21c, P9 system.io.ioexception, P10 NIL.

    I have restarted the server several times since early december and the server runs for a few days error free and then after this, the Server Performance Report (email) always lists the error. I dont think that there is any major problems as a result of this error but it is just annoying.

    Any advice would be a great help.
     
  2. 2007/01/18
    Dytrog

    Dytrog Inactive

    Joined:
    2007/01/13
    Messages:
    341
    Likes Received:
    0
    Did you overload your Email storage. i don't know that error but you may have to get rid of stored mail. are you hi speed like cable or slow like dial? download runtime?
     

  3. to hide this advert.

  4. 2007/01/18
    griffmaster

    griffmaster Inactive Thread Starter

    Joined:
    2006/09/12
    Messages:
    88
    Likes Received:
    0
    We only have 5 exchange mail boxes on an SBS2003 server and use the POP connector to get mail from our ISP, we have an 8Mbps ADSL connection.
     
  5. 2007/01/18
    Dytrog

    Dytrog Inactive

    Joined:
    2007/01/13
    Messages:
    341
    Likes Received:
    0
    I don't know that it maters on this subject mine 100 mbps cable modem.
     
  6. 2007/01/18
    Dytrog

    Dytrog Inactive

    Joined:
    2007/01/13
    Messages:
    341
    Likes Received:
    0
    Don't know if it matters my connection speed is 100 mbps.
     
    Last edited: 2007/01/18
  7. 2007/02/08
    griffmaster

    griffmaster Inactive Thread Starter

    Joined:
    2006/09/12
    Messages:
    88
    Likes Received:
    0
    I'm still getting this same error in the daily server report, but the error seems to occur at the same time every morning.

    Source -.NET Runtime 2.0 Error Reporting
    Event ID -5000
    Last Occurrence - 08/02/2007 00:57 (UK date format dd/mm/yyyy)
    Total Occurrences - 1*

    EventType clr20r3, P1 logwrite.exe, P2 1.0.0.0, P3 4498ead6, P4 mscorlib, P5 2.0.0.0, P6 4333ab80, P7 32f8, P8 21c, P9 system.io.ioexception, P10 NIL.

    Any ideas anyone?
     
  8. 2007/02/08
    Dytrog

    Dytrog Inactive

    Joined:
    2007/01/13
    Messages:
    341
    Likes Received:
    0
    .net

    messed up
     
    Last edited: 2007/02/08
  9. 2007/02/08
    Dytrog

    Dytrog Inactive

    Joined:
    2007/01/13
    Messages:
    341
    Likes Received:
    0
  10. 2007/02/13
    griffmaster

    griffmaster Inactive Thread Starter

    Joined:
    2006/09/12
    Messages:
    88
    Likes Received:
    0
    for 40days i have been getting this error and on day 41 the error has gone, but i havent actually done anything. I am very confused. We will see if it comes back tomorrow.
     
  11. 2007/02/14
    griffmaster

    griffmaster Inactive Thread Starter

    Joined:
    2006/09/12
    Messages:
    88
    Likes Received:
    0
    The error has returned at its usual time on 00:57. This is very strange indeed, still not any further to understanding it. The first instance of this error occured on 5th December 2006, and the only thing I can think of that was done around that date was I installed an APC UPS and associated PowerChute Software. Unless there is a conflict between .NET reporting and APC's UPS Monitoring software?
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.