Dim SEDoc As Object = c_SolidEdgeApp.ActiveDocument
Any ideas to make this more robust? Originally, I was just using the SePvAdp.exe standalone converter through the Process object, but, unfortunately, it does not honor the assembly occurrence property setting to hide parts in higher assemblies.
Posted by: Brent Newsom Post date: 7/25/2007 8:57:02 AM
That is truely odd. When it does throw an exception, is it always on the same file or it completely random? And does the SePvAdp.exe experience the same exception randomly? The only thing I'd know for you to do is to submit an IR to GTAC and see what they say. It's going to be tough for them to diagnose the problem if it's not easily reproduceable. Understandibly.
You said that the code is called inside a Windows Service .dll. Have you tried creating just an .exe and testing that way? I'm wondering if the Windows Service thing has anything to do with it. I don't think GUI COM components play well within the realm of Windows Services.
Posted by: Jason Newell Post date: 7/29/2007 8:13:22 PM
It turns out, I made a bad assumption about how my dll was being used on the server. I have a property which controls how many JT conversions should be run before closing and restarting Solid Edge. This code was not being called. We now have Solid Edge closing and restarting after every conversion and the issue went away.
Posted by: Brent Newsom Post date: 7/31/2007 5:21:27 AM