Creo - Unhandled exception

[jndejak]

Martin,

I am trying to setup IFX on a network.  I believe I have everything setup correctly but get a similar error to the one above.  Using your solution and running IFX through the creo load point, everything works fine just like in this post.  The problem I have is when I point the IFX configuration PATH_ABS_LIBRARY to my network location I get the hole_com.cpp error.  Can you help with this?

[MartinHanak]

---

@jndejak wrote:

Martin,

I am trying to setup IFX on a network.  I believe I have everything setup correctly but get a similar error to the one above.  Using your solution and running IFX through the creo load point, everything works fine just like in this post.  The problem I have is when I point the IFX configuration PATH_ABS_LIBRARY to my network location I get the hole_com.cpp error.  Can you help with this?

---

Hi,

I hope @OliverGräbner can comment your request.

[OliverGräbner]

Hi @jndejak 

can you please provide more information.

Can you send the 'hole_com.cpp' error message.

Do you use own customized *.hol files with creo option 'hole_parameter_file_path' set to your hole folder?

If this problem is not related to your first problem, it might make sense to create a new post for it.

@MartinHanak - thanks for mention me.

[jndejak · Accepted solution]

Oliver,

Thanks for your quick response.  I eventually determined that the assembly model I was using to validate all my changes in moving fasteners to our network somehow became corrupt.  I'm guessing some IFX data remained in the models as I deleted and reinserted fasteners to test.  While waiting for your response I created a new assembly with two plates.  Now everything works seemlessly.  I was able to copy metric fasteners from IFX prolibrary and change instance names and add additional parameters for our buying information.

I also came across another post of yours where I realized the .DAT and the family table instance names need to match, which was an addition issued I had.

All works well now.  Thanks.

[OliverGräbner]

@jndejak that a good news. 

Thanks for feedback.