Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
edenmack

Avatar / Picture

Member
Registered:
Posts: 49
Reply with quote  #1 
I have a from with several memo fields on it. I'm often getting a "Failed to Commit Action" message in the web browser, and an "Unable to save Server Data" on the back end. In one case I have less then 120 characters in one memo field. Any thoughts?
0
Pete

Senior Veteran
Registered:
Posts: 315
Reply with quote  #2 

Is it possible that you try to assign a value bigger than 250 Chars to a text variable? I usualy get this error then...


__________________
If you want the job done right, hire a professional.
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #3 
A quick search brings up:
http://metastorm.processmapping.com.au/tool/post/ework/vpost?id=2012424

No idea if it helps.


__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
Nappy

Avatar / Picture

Guru
Registered:
Posts: 1,087
Reply with quote  #4 
The back end error is that event log or designer log.
Depending on error one or the other may have some usefull info.

You say several memo fields. Could it be you are trying to write more then 8kb to the database (total data in all the fields?)

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.

PS that's for V6/7 for V9 the problem is V9 at the moment ;)
0
edenmack

Avatar / Picture

Member
Registered:
Posts: 49
Reply with quote  #5 
OK -- thanks for the responses. I have combed these forums extensively before this post and have not seen anything that relates.

The 250 character limit does not apply due to the fact I'm using a memo rather then a text field. Also, While the 8k limit of a memo field could become problematic -- that's not the issue here. I'm passing 100-200 characters in one memo field (with all other fields blank).

I read the helpful thread about eWork limiting Database commands to 3k characters (I may not have understood it completely) and I adjusted my code to split the row creation from the data updates. That helped. . . but I'm still having issues.

The errors I referred to are showing up in the elog table.
0
Nappy

Avatar / Picture

Guru
Registered:
Posts: 1,087
Reply with quote  #6 
did you check the event log of the machine?
And have you checked the Designer log?

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.

PS that's for V6/7 for V9 the problem is V9 at the moment ;)
0
edenmack

Avatar / Picture

Member
Registered:
Posts: 49
Reply with quote  #7 
Nothing in the machine event logs. Where do I find the Designer log?
0
daiwilliams

Veteran
Registered:
Posts: 122
Reply with quote  #8 
I think he is referring to the designer log in the Metastorm Services Manager. Connect to your database, and then it should be diagnostics - designer log. Keep refreshing it if your checking it while working on the procedure for new errors.

Dai


0
Nappy

Avatar / Picture

Guru
Registered:
Posts: 1,087
Reply with quote  #9 
No i'm talking about the designer log admin forms that are in
C:\Program Files\Metastorm BPM\Administrative Tools\Administrative Procedures


__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.

PS that's for V6/7 for V9 the problem is V9 at the moment ;)
0
Jas

Senior Veteran
Registered:
Posts: 429
Reply with quote  #10 

As per Nappy's post; check the ePreEval and ePostEval fields of the eLog table.

0
Doogal

Avatar / Picture

Guru
Registered:
Posts: 1,564
Reply with quote  #11 

I believe the original error is from the eLog table. I think in this case the engine doesn't surface the original reason for the failure. This was certainly the case for me when I tried to assign over 250 characters to a 250 text field. I'd suggest running SQL Server Profiler when you try to commit the form (assuming you're using SQL Server) and see what SQL the engine is throwing at the database and see what happens when you run it yourself.

0
edenmack

Avatar / Picture

Member
Registered:
Posts: 49
Reply with quote  #12 
Doogal is correct -- the original error I provided was from the eLog table as I stated. (this is the table that holds the data displayed by the Metastorm Service Manager and by the XEP refered to by Nappy)

ePreEval and ePostEval fields were both empty.

Looking at SQL Server Profiler indicates that the transaction count was 0 not because anything failed, but because nothing was attempted. Could eWork not be sending any SQL? I'm so confused.
0
KarlD

Avatar / Picture

Guru
Registered:
Posts: 113
Reply with quote  #13 
If the update as a whole is not working then it may be worth trying to update a single field at a time.

It could be any number of things. Spelling mistake or a destination field not set with the right properties or even the user details being incorrect.

I sometimes find that if something isnt working and there is no real indication why, then breaking it down and trying it one step at a time helps. If the first step works then add another little bit and so on.



0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!