Long uptime = Weird behaviour in IIS?

i'm looking for others with experience in long uptimes on windows 2003 with iis 6.0

i'm a unix admin so i didn't care about this crap before but now i have to manage a few windows machines and one thing i've noticed is that they start acting weird after they've been up for a while, i'm so used to them acting like this that i can tell you for sure that after 15 days people start calling saying their asp scripts don't work(fixes itself after reboot) and we temporarily solved this problem by setting a cronjob that executed iisreset at like 05:00 in the morning every 24h, this made the server just go and go for like 62 days before a developer i know called and said his sessions stopped working, the problems could have started before that but you know how it is, some customers don't call and just sit there waiting for us to fix it

has anyone seen this happen before? maybe some of you MCSE people can give me some hints, could this be caused by not using the default application pool for domains in iis?

are these asp scripts/programs made by your company or by microsoft?
one of the problems we had with iis5 at my company was that the asp scripts didnt have good memory management and would eat up system ram and not release it, which would cause the system to slow down after a few days or 2 weeks.
you can "probably" assume that if you are running iis6 within the proper guide lines that it isn't microsofts fault. maybe i dont know. but i would first check the applications running on the system first. and then start looking for new bugs in iis6.
i wish i had some links handy, but there are apps that let you track performance of asp scripts. you might also wanna check into the built in performance counters for Windows 2003 and iis6

IIS itself has no problems running for long times, follow nonsence's advice.