runtime error '-2147217887, Multiple-step operation generated errors

[Deeps]

i get this error while saving one form
but even if it shows this message it saves the data
so is it a problem of sql? because this form saves data in a database which is not on he same where the dev machine server is.

[Rus]

Convert this to HEX and google for the result.

It might tell you more.

[pivotalnd]

it would help if you check the event viewer for additional logs. also check the relation.err to see if any ODBC errors have ocurred. usually multiple step operation errors are middle tier runtime errors that might not be handled.

[Deeps]

Actually my problem is as follows,

In my form i want to add an attachement file
Once i add it and click save/update, it shows me an error message 'unable to save' or ' multiple step operation'
So according to our program, when we save attachements , these are saved in another server database (so not on the same development server).
and once saving its shows the error message , shows the added file in the form, but it doesnt save it in the database .

And this problem is not shown for every client machine. For some systems its working and saving for attachement successfully and others not.

Hope you understood my problem.

[Dean Wooldridge, Jr.]

I'd suggest it is a timing (timeout) issue.

[Deeps]

and is there any solution to increase the time delay? because yeah its a heavy form with aroung somewhat 254 tables included in the view filter.
is it that a reason to have a time out?

[Dean Wooldridge, Jr.]

I don't know to tell you the truth.  Maybe there's somethingon the SQL side that can be set.  I said timing because of two experiences:

1.  When debugging, if I step the code sometimes the action will fail with odd errors and if I takeout the breakpoints the error disappears.  Of course this only works after I have found my error.

2.  We did some enhancement work to the "Process Lead to Opportunity" ASR and found that we would be sporatic failures.  After much work, the opinion was that the process was tasking too long and the transaction was timing out.  Had to rewrite a bunch of code and the problem disappeared.  That's not a real good technical explaination but its what Pivotal told us.  I would guess that if they thought there was some simple setting change to make in SQL, then they would have tried that first.

[pivotalnd]

i think  there is a limitation of 250 tables in a query. with 254 this error seems to be pretty obvious and to be expected. could you reduce the number of tables and then check once?

[Deeps]

yeah we did reduce and we found wat was bugging it had nothing to do with sql
ayway thanx for the suggestion

[eladfrn]

Hi all.
I have the same problem and I dont know what is causing it. I am trying to save a step and the error apears.
I've added the screenshot of the event viewer.
If someone knows how to solve this thing I will be happy to hear.

Thanks,
Elad

[DreamWeaver]

This happens when you are trying to save a form that has a value(s) in some field(s) more than its length/limit.

[jaybee]

Thanks man, saved my life today.