doc.Send(True) crashes server

Hello,

A domino intranet application that has been running on multiple versions of Domino for the past six years, now crashes the server after an upgrade from 7.0.3 to 8.0.1.

It is a background agent for a website that is executing a doc.send(true, thisuservar). When the user clicks the Submit button, the agents runs ok until it encounters the doc.send, then crashes the server.

We have resigned the database since the upgrade and that did not help. There were no design changes to the databases before or after the upgrade.

Has anyone experienced anything similar?

We opened a PMR with IBM and they returned the following, but that is not telling us why we are crashing.

Agent Start: agent “SubmitOnlineForm” in

 "abc/intranet/intranet.nsf" (thread [409130:16857:00034-0000009A])     

5/05/2008 12:51:32 *** Agent Start: agent “ApproveDisapproveRequests” in

         "abc/intranet/INetDocs.nsf" (thread [409130:16857:00013-00000085])       

Thanks

Cindy

Subject: Valid User?

I haven’t encountered this with our Notes 8 server, but I had a sort of similar problem with a past upgrade. It didn’t kill the server but killed the agent if I tried to send to a user who was not in the Domino Directory. Is it possible that is what is happening here?

Subject: Yes, valid users

Yes, all of the users are valid. The app had been running for 6 years, so that is what is so confusing about this.

I did have some fields (@dblookups) that were utilitizing @IsError, and I heard a rumor that that should not be used anymore, and I removed all of those, but it did not have an impact.

I did find an entry on the IBM site for the R5.5 release where some servers were crashing due to doc.send but it had to due with a keyring of some sort.

Thanks for the suggestion.

Subject: Support

What exactly did IBM support tell you?

Subject: Working the problem

We are providing them a cut down version of the database to see if they can reproduce the crash on their server, so no solution just yet.

Subject: Post the FATAL THREAD section…

Hi

Can you post the FATAL THREAD section of the NSD files with the few lines under it

For example:

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

FATAL THREAD 1/2 [ domdsm:107a8:67076]

FP=0x0012a34c, PC=0x60069a86, SP=0x0012a2f0, stksize=92

EAX=0x01a3088c, EBX=0x01a48650, ECX=0x0000bffe, EDX=0x01a325e6

ESI=0x00004000, EDI=0x0032ff78, CS=0x0000001b, SS=0x00000023

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

Exception code: c0000005 (ACCESS_VIOLATION)

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

@[ 1] 0x60069a86 nnotes._fdDelete@4+118 (4000,12a368,608770ef,4000)

@[ 2] 0x60069a0c nnotes._OSFileClose@4+12 (4000,12adc0,12a380,60872ea7)

@[ 3] 0x608770ef nnotes._sqloclose+15 (4000,12b59c,5010,0)

@[ 4] 0x60872ea7 nnotes._sqlpgclf+71 (12adc0,1aaa2cb,70,1aaa2f3)

@[ 5] 0x60885458 nnotes._sqlpgfdl+616 (12b9a4,1aaa2cb,41,12be44)

@[ 6] 0x60876a6f nnotes._sqlpgcdl+927 (12bf44,12b9a4,0,12be44).

Date

Topic

Frequently asked question - How to analyze Notes/Domino NSDs? (Jean-Yves Riverin)

JYR

Subject: Thread info

This is all we have right now. They have a copy of the db to test it. I’ll post more when I find out.

Agent Start: agent “SubmitOnlineForm” in

   "fci/intranet/intranet.nsf" (thread [409130:16857:00034-0000009A])     

5/05/2008 12:51:32 *** Agent Start: agent “ApproveDisapproveRequests” in

           "fci/intranet/INetDocs.nsf" (thread [409130:16857:00013-00000085])

Subject: Solution found for crash

In the HTML Head field on the form, the code was

“<script language="JavaScript">” + @NewLine +

“var dbpath = "” + DB + “"” + @NewLine +

“var clienttype = "” + @ClientType + “";” + @NewLine +

“”

We have modified it to the following and no longer experience server crashes under 8.0.x on iSeries.

“<script language="JavaScript" type="text/javascript">” + @NewLine +

“<!–” + @NewLine +

“var dbpath = "” + DB + “"” + @NewLine +

“var clienttype = "” + @ClientType + “";” + @NewLine +

“// -->” + @NewLine +

“”

Note: The type="text/javascript" did not affect the agent. The two lines that made all the difference were

“<!–” + @NewLine +

“// -->” + @NewLine +