Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
absiin

Avatar / Picture

Member
Registered:
Posts: 13
Reply with quote  #1 
Hi all :)

First of all, thanks for accepting me Jerome :)

As a quick introduction, my name's Sara, I'm 24 and live in the UK - London.

I'm working for a huge healthcare company as a 3rd line support engineer.

I've been working with BPM Metastorm 6 since December last year and I'm really interested in development - I've learnt loads so far and am really looking forward to learning even more!

For a few weeks now I've been struggling to get my FFAdmin to connect to the db as I keep getting an OutOfMemory exception every time... Our DB is sitting on a SQL Server 2000 (slightly outdated...) with 2GB RAM  and we're running windows server '03 and windows 7 on local machines...

I've attached the error description/details to this thread and was wondering if anyone could shed some light on what might be the problem... I'm not sure if I should request memory increase and at the mo upgrade is not an option as I'm the only one here with 'some' knowledge in workflow and I'm not comfortable with putting myself forward to upgrade it with no support in case things go 'tits up' and I end up causing a lot more problems than I'd be solving... 

Whilst this hasn't been working I've been doing all the user/folder maintenance through SQL but it's sooo time consuming...

Any help will be extremely appreciated!

Thank you,
Sara :)

 
Attached Files
txt RTE_freeflow.txt (13.23 KB, 9 views)


__________________
Absiin

0
BMellert

Guru
Registered:
Posts: 688
Reply with quote  #2 
SQL 2000 and MBPM (eWork) V6 and Windows Server 2003?
SQL 2000 is desupported; as is Windows Server 2003.  V6 is desupported as well unless you have "superseding support" service -- which your organization may.  However, when we used that configuration 2G of memory was adequate.

Is this occurring in the designer, while deploying or at runtime / launching form (user viewed error)?
The answer may differ depending on when the error occurs, though there's nothing obvious to me quite yet.
0
absiin

Avatar / Picture

Member
Registered:
Posts: 13
Reply with quote  #3 
Quote:
Originally Posted by BMellert
SQL 2000 and MBPM (eWork) V6 and Windows Server 2003?
SQL 2000 is desupported; as is Windows Server 2003.  V6 is desupported as well unless you have "superseding support" service -- which your organization may.  However, when we used that configuration 2G of memory was adequate.

Is this occurring in the designer, while deploying or at runtime / launching form (user viewed error)?
The answer may differ depending on when the error occurs, though there's nothing obvious to me quite yet.


Nope... We are aware that our version of workflow is extremely old and opensource has said this to my bosses but I don't think they're too bothered with it to be honest... As it's "working" it's not a problem for them... I've tried to push for upgrade of the server, software and processes but we don't have the time nor the resource for it at the moment... 


The error happens about 10 mins after I initiate FreeFlow Administrator... The screen goes blank and then crashes...

freeflow.PNG 
I'm thinking it might be a problem with the initial query that it runs... How can I get what is actually running on the database?

The program itself hasn't changed so it can only be a data problem...

The FF process on my laptop is munching away on half my physical memory and everything freezes...

tas.PNG 

perf.PNG 


__________________
Absiin
0
BMellert

Guru
Registered:
Posts: 688
Reply with quote  #4 
Ahh, I should have read a bit closer.  I'm not familiar with FreeFlow so I cannot provide much specific insight on that.  (I've worked on M/BPM versions 6 through 9.)

As far as the actual queries running on the database, your database administrators can run a SQL trace for your session/user during a brief period of time and provide the results of everything that ran during that period.
0
Doogal

Avatar / Picture

Guru
Registered:
Posts: 1,564
Reply with quote  #5 
Wow, people are still using FreeFlow! Looking at your error log, it seems that it falls over when it's loading up the contents of the eLog table. It would also appear I didn't ever think to limit the number of rows that are read from that table, so my guess would be you have a fairly large eLog table which is causing the issue. I'd suggest having a look in there via the SQL Server tools and clearing out anything over a few months old
0
absiin

Avatar / Picture

Member
Registered:
Posts: 13
Reply with quote  #6 
Quote:
Originally Posted by Doogal
Wow, people are still using FreeFlow! Looking at your error log, it seems that it falls over when it's loading up the contents of the eLog table. It would also appear I didn't ever think to limit the number of rows that are read from that table, so my guess would be you have a fairly large eLog table which is causing the issue. I'd suggest having a look in there via the SQL Server tools and clearing out anything over a few months old


Ah you did reply to me! :) 

Yes this was the issue everyone, the eLog table was GIANT! Cleaned that, all working perfectly fine :)

Crisis mode OFF! Thank you all!

__________________
Absiin
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!