cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Have a PTC product question you need answered fast? Chances are someone has asked it before. Learn about the community search. X

PDMLink and Wildfire Issues

mfortis
2-Explorer

PDMLink and Wildfire Issues

All,

We just upgraded (last weekend) to PDMLink 9.1 M050 from M030 and Wildfire 4.0 M120 to M150 and we are running across some serious bugs/problems. The problems are limited to the Windows XP 64-bit OS. When you go to the information page of any object and select the History menu followed by the Iteration option Pro/E will crash. It pretty much happens with any of the pull-down menus on the information page, but its most consistently happens with the History one.
It also does not occur on all 64 bit machines. It just so happened that I did all my testing on a 64 bit machine that is not experiencing this issue.
We have tried installing M150 from the disk, since we initially just copied and replaced the M120 files via WinZip, but still saw the problem. We also tried going to M140, but we still are the issue. We will be trying M130 today to see if that solves it, but that's our last hope since there are only three build of ProE that are compatible with PDMLink M050.

Does anyone have any ideas of what maybe causing Pro/E to crash? I am thinking it could be something in our environment. But I have not been able to pin it down since the only common thread in the affected machines is the OS. Any help at this point would be welcomed.

Thanks,
Mike
858.612.3098
3 REPLIES 3

I don't know if this will help, but we make sure that the jre memory settings are higher than the default:

Double select the empty text field under Java Runtime Parameters and Enter this string:

-Xms64m –Xmx256m

Most likely if you have a ProE 64bit box you can utilize more than the ~4GIG limitation. Thus, you can increase the minimum and maximum accordingling. We did see ProE crash when opening drawing sketcher and similar behavior. Also make sure that your IE cache is not set to automatic but always on every visit and so on.

We are testing with Windows 2008 on 64 bit with out any current issues. We are going with the fastest CPU dual or quad. Since ProE only runs off 1 core, it is a complete waste of money to invest in multiple cores for ProE.

Hope this helps.

I don't know if this will help, but we make sure that the jre memory settings are higher than the default:

Double select the empty text field under Java Runtime Parameters and Enter this string:

-Xms64m –Xmx256m

Most likely if you have a ProE 64bit box you can utilize more than the ~4GIG limitation. Thus, you can increase the minimum and maximum accordingling. We did see ProE crash when opening drawing sketcher and similar behavior. Also make sure that your IE cache is not set to automatic but always on every visit and so on.

We are testing with Windows 2008 on 64 bit with out any current issues. We are going with the fastest CPU dual or quad. Since ProE only runs off 1 core, it is a complete waste of money to invest in multiple cores for ProE.

Hope this helps.

Dmi3U
15-Moonstone
(To:mfortis)



Hi, Mike!
Works for me!

Announcements


Top Tags