Server Crashes on HTTP Tasks - Access Violation

After Upgrade from R5 to R7, server Crashes 2 times, every day around the same hours.The server is on Release 7.0.1FP1 HF84 October 02, 2006 with Windows 2000 SP4

NSD Shows:

############################################################

FATAL THREAD 95/157 [ nhttp: 3284: 4964]

FP=0x233a03d4, PC=0x005034c8, SP=0x233a03d4

stkbase=233b0000, total stksize=262144, used stksize=64556

EAX=0x00000000, EBX=0x233a85e0, ECX=0x73fb0010, EDX=0x0121b0a0

ESI=0x73fb0010, EDI=0x233a858c, CS=0x0000001b, SS=0x00000023

DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010246

Exception code: c0000005 (ACCESS_VIOLATION)

############################################################

@[ 1] 0x005034c8 NINOTES.Link::IsLinkMember+8 (73fb0010,233a8578,233a040c,46c8c6)

@[ 2] 0x00503824 NINOTES.ThreadStorage::Free+36 (73fb0018,233a9770,233a8568,233a987c)

@[ 3] 0x0046c8c6 NINOTES.HTMLfilter::~HTMLfilter+166 (6bd710,0,233a8568,233a047c)

@[ 4] 0x0046856b NINOTES.HTMLpage::~HTMLpage+219 (6bd710,0,233a044c,6bd6f8)

[ 5] 0x7c34347e MSVCR71 (2312a014,233aa9c0,233aa254,233aa840) - SYM FILE OUTDATED!

@[ 6] 0x00457d69 NINOTES.CmdHandlerBase::HandleEditDocumentCmd+873 (6c6e3614,0,2312a014,660a814)

@[ 7] 0x004409f4 NINOTES.CmdHandlerBase::PrivHandle+404 (2312a014,0,23164014,660a814)

@[ 8] 0x0043eff9 NINOTES.CmdHandler::PrivHandle+121 (2312a014,23164014,660a814,7c59c360)

@[ 9] 0x004f01ef NINOTES.CmdHandlerBase::HandleOpenDocumentCmd+639 (2312a014,0,0,23164014)

@[10] 0x0044091c NINOTES.CmdHandlerBase::PrivHandle+188 (23164014,0,0,660a814)

@[11] 0x0043eff9 NINOTES.CmdHandler::PrivHandle+121 (23164014,6c712014,23164014,0)

@[12] 0x0043fa1d NINOTES.CmdHandler::Handler+221 (23164014,660a814,23164030,0)

@[13] 0x00436baa NINOTES.Cmd::Execute+58 (2e56020c,2e55ff20,3,6551f4)

@[14] 0x004797a0 NINOTES.$L170297+699 (2e56021c,2e56020c,2e55ff20,3)

@[15] 0x0047bc2f NINOTES._InotesHTTPProcessRequest+47 (2e56021c,2e5605a4,0,0)

@[16] 0x10015114 nhttpstack.HTInotesRequest::ProcessRequest+36 (2e55ff20,2e55fdb8,0,2e56021c)

@[17] 0x10010afd nhttpstack.HTRequestExtContainer::ProcessRequest+941 (5,1,2e3661e8,0)

@[18] 0x1001fa80 nhttpstack.HTRequest::ProcessRequest+1904 (0,179932bd,0,2f48502f)

@[19] 0x10024e41 nhttpstack.HTSession::StartRequest+897 (179932c9,179932bd,0,179932ef)

@[20] 0x1002c08f nhttpstack.HTWorkerThread::CheckForWork+399 (3,179932bd,10029180,100291aa)

@[21] 0x1002c5a8 nhttpstack.HTWorkerThread::ThreadMain+88 (179932bd,0,0,0)

@[22] 0x60104fc0 nnotes._ThreadWrapper@4+208 (0)

@[23] 0x7c57b396 KERNEL32.lstrcmpiW+183

and Fault Report indicate ever the same database:

Name: BRSPWPH1/PH/Novartis

Notes/Domino Version: Release 7.0.1FP1 HF84 October 02, 2006

Machine Name: PHBRSP-S4006

OS Version: Windows 2000 5.0

Start Time: 13/11/2006 12:33:25

Crash Time: 13/11/2006 18:19:49

Uptime: 0 day(s) 05:46:24

Error message: ACCESS_VIOLATION

Process: nhttp

Callstack: Link::IsLinkMember

ThreadStorage::Free

HTMLfilter::~HTMLfilter

HTMLpage::~HTMLpage

MSVCR71

CmdHandlerBase::HandleEditDocumentCmd

CmdHandlerBase::PrivHandle

CmdHandler::PrivHandle

CmdHandlerBase::HandleOpenDocumentCmd

CmdHandlerBase::PrivHandle

CmdHandler::PrivHandle

CmdHandler::Handler

Cmd::Execute

$L170297

InotesHTTPProcessRequest

HTInotesRequest::ProcessRequest

HTRequestExtContainer::ProcessRequest

HTRequest::ProcessRequest

HTSession::StartRequest

HTWorkerThread::CheckForWork

HTWorkerThread::ThreadMain

ThreadWrapper

Open Databases: F:\Lotus\Domino\Data\PH\FUNCTION\Finance\Approval\PHFBRICO.nsf

Subject: Server Crashes on HTTP Tasks - Access Violation

You should post the stacks, just below FATAL THREAD section or look here

http://www-10.lotus.com/ldd/sandbox.nsf/ecc552f1ab6e46e4852568a90055c4cd/42334489e0ed9f0a85257123004d9eed?OpenDocument&Highlight=0,nsd

Troubleshooting Lotus Domino hangs and crashes

JYR

Subject: Server Crashes on HTTP Tasks - Access Violation

In some cases this error occurs to me or my developers, and all we do to fix it, is run in the Notes Client the application and check in the server console which field are sending the error. Hope this help