Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations waross on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Delta Debug Error While in Pro/e

Status
Not open for further replies.

Step24

Mechanical
Aug 26, 2002
5
0
0
US
While working in Pro/e we randomly encounter a Delta Debug error where a dos message window appears with some error messages including "PDMLDBStartTransaction (LDBHandle)","Cannot open LDB File" & the error codes 2410 & 2408.
Once you close this window it kills off pro/e.
I have queried this with PTC help but they have been unable to give us a cause or a fix.
Has anybody else experienced this?
Does anyone know what is causing it and how to fix it?

 
Replies continue below

Recommended for you

Hi,

I have a colegue who encountered a such error few weeks ago: DELTA DEBUG ERROR with a code. The "good" part was that the message appeared on the "message area" and not in a DOS window and that's why PRO/E did'n crash.

I have to tell you it will take you a lot of time to identify the source of the problem. In our case, the error message appeared on a specific assembly, after a regeneration command. I thought that the problem was an subassembly. But when I opened it separately, I had no errors. I suppresed this subaseembly from the main assembly and I had no errors. I reassembled and the error appeared again. What was wrong? My coleague told me he made an restructure, but he did'n notice the error at that time. The only solution to remove this error was to recreate the assembly from the begining.

Now, in your case, try to follow this steps:

1. Identify which part/assembly gives you the error (check also the trail file).

2. Open it separately and see if the error persists after a minor modification and a regeneration. You must "force" a regeneration bu changing something in the model.

3. Files like MDB or LDB are used by Mechanica. Did you performe any structural/thermal/motion analysis on the pars/assembly? If yes, try to make a copy of that part/assembly and then in Integrated Mechanica mode delete all features like loads, constraints etc from the model.

3. If you was able to identify the model in cause, you must know that this type of error that make PRO/E to crash are caused by a feature. Usualy the last. Try to erase it and recreate it again.

By the way, are you working with Intralink?

Try to give us more details about your model, your PRO/E version and build. Maybe at least we can help you.

-Hora.
 
Thanks for your quick response Hora,
We are using 2000i2 build 2001140 and Intralink 2.0 build 2000470.
Unfortunately the error is not restricted to one part or assembly,there are 4 different designers here that I am aware of who have had it happen to them, on separate workstations all on different models and all using different commands.
We are all networked to the one common server though.
We cannot get the error to repeat on demand,it seems to be a random occurrence.
In my case it has been triggered by selecting the following icons: open file,create new file,save,print drawing,zoom.
It doesn't seem to be a model specific problem and if you don't restart the workstation it happens again as soon as you try to get back into Pro/e.
We do not use mechanica or thermal/motion analysis at all here.
We do run all our Pro/e sessions linked to an Intralink workspace.
PTC help thought that the 2410 error may have been a disk space error,but they were not really sure about that and they did not know what the 2408 error meant.
 
This might be wrong... but it could be an interaction error with Intralink that occurs because the proilws.dll file is not correct in Pro/Engineer...

This has been the case for me when installing Intralink After Pro/Engineer was installed...

Try Copying the <Client loadpoint>\i486_nt\illib\proilws.dll to the <Pro/ENGINEER loadpoint>\i486_nt\deflib directory (make a copy of the file from pro/e just in case)...

Also it has worked for me if I Copied the <Client loadpoint>\i486_nt\illib\proilws.dll to the <Pro/ENGINEER loadpoint>\i486_nt\obj directory... (But I'm not certain of this one. the other is a known Fix)...

Goodluck... Daniel Pro/E Specialist
 
Status
Not open for further replies.
Back
Top