Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
itcscm

New Member
Registered:
Posts: 9
Reply with quote  #1 
Hi,
We've had problems recenty with the eFolder table locking in the DB. We are also finding we need to restart the engine every few weeks.

It appears that the table is locking and preventing other procedures from connecting to the DB.

Not sure if the problems are related but during the last occurrence we got the following message logged on the server running the engine:

Event Type:    Error
Event Source:    e-Work Engine
Event Category:    eException
Event ID:    89
Date:        3/25/2008
Time:        3:17:30 PM
User:        N/A
Computer:    EWORK02
Description:
ErrorCode: '-2147217871' Description: 'Timeout expired'  Source: 'Microsoft OLE DB Provider for SQL Server'  SQL State: 'HYT00'  NativeErrorCode: '0'   

Has anyone experienced this before or got any ideas about where we could look for more info?

Thanks

Colin

0
Doogal

Avatar / Picture

Guru
Registered:
Posts: 1,564
Reply with quote  #2 
I've only seen the 'Timeout expired' error message when the database server is very busy, we occasionally get it when the database is being backed up.

For your main problem, I'd suggest using the Activity Monitor to see if there are lots of connections opened on the database (we suffered that for a while) and the Profiler to see if there are lots of queries being run against the eFolder table.

Also make sure none of your %SelectSQL etc queries running agaisnt the e-Work database are specifying a DSN.
0
menges

Member
Registered:
Posts: 27
Reply with quote  #3 
Hi,

as far as our experience goes we had similar problems on e-work 6.6.4 and SQL Server. If we were using a grid, that was populated with table data within the e-work schema AND defining the odbc connector in the property page from the grid explicitly - then the e-work form could not be send and runs into time-out. If we remove the database connector entries from the grid property page it works fine.

e-work 6.6.4, SQL Server 2005, ODBC Connector with Win-SSO

Regards,
Thilo
0
vasantha

Member
Registered:
Posts: 40
Reply with quote  #4 

Did you get the solution for this? I am having a problem where teh efolder table gets locked ...and its comes uop after sometime with an error. The blank forms woulnt open and I get the Timeedout error. when i check the error log ..it says the problem is with a Grid. but i dont see any problem there? in  the event viewer the error is

ErrorCode: '-2147217871' Description: '[Microsoft][ODBC SQL Server Driver]Timeout expired' Source: 'Microsoft OLE DB Provider for ODBC Drivers' SQL State: 'S1T00' NativeErrorCode: '0'

Please help me out with this.

Thanks

__________________
vasu
0
vasantha

Member
Registered:
Posts: 40
Reply with quote  #5 
Any suggestions to the above problem ??? well, when I deleted the Grid with which connects to an external database thent the blan forms will open. But, I need to have the grid in my application. is there some way where I can have the grid which calls the external database ...i never had this problem before...not sure why it comes up now.

Plese help me out with this.

Thanks in advance.

__________________
vasu
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #6 
what is the grid connected to. Can you post the SQL for the grid? IYou can get this from the properties, or from eField.eDataValue for that field.

__________________
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
prafulla

New Member
Registered:
Posts: 1
Reply with quote  #7 
Hi ,

Blank form and Admin form were not opening.
and got failed to invoke aciton error.
When i check the event logs i got following  error

 

ErrorCode: '-2147217871' Description: 'Timeout expired' Source: 'Microsoft OLE DB Provider for SQL Server' SQL State: 'HYT00' NativeErrorCode: '0'

 

I solved this problem by removing old entries from Efolder table.(due to huge size of Efolder  it might cause the time out error)

Regards


__________________
prafulla
0
anil

Avatar / Picture

Member
Registered:
Posts: 11
Reply with quote  #8 

We also faced Same 'Timeout expired' error and resolved by clearing some old entries from eAlert table.

 


__________________
Thanks,
         -- A C.
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!