Always a possibility that your config files could cause loading issues.
I troubleshoot config files by removing 1/2 of the config file at a time and load with just that 1/2 of the file. If the problem disappears is still there, it is likely that one of the options in that 1/2 of the file is the problem, Depending on how large your config files, you can keep cutting them in 1/2 and testing each 1/2 until you get it narrowed done to just a few. Then test each setting. Once narrowed to a few, it's usually easy to spot the most likely candidates for problems.
In Creo, open the config.pro and config.sup files and see if there are any flags indicating an invalid or out-dated option.
Steve's plan is a good one if all options appear to be valid.
@BenLoosli , and @StephenW, I appreciate your help, I was able to go in and take a look at those items, I even went as far as Commenting out all of the configurations that were in those files. Unfortunately, this didn't solve the problem. But it lets me know that the Config.pro, and the Config.sup are not the culprits. Which leads me to the IPEM Configuration to connect Teamcenter and Proe together. I will need to take a different route, as I thought the issue was on the Proe side of the solution. Turns out its on the Teamcenter side.
First time posting in the forums here, and was pleasantly surprised with the response time and speed.
It's a good way to rule out the obvious potential issues.
If you have and customization on the interface, you may also want to temporarily rename creo_parametric_customization.ui file .
Just to rule out that it is trying to load something that may be causing the issue.
In time, I may be asking you questions! Our Engineering technology group has been testing the IPEM connection to Teamcenter. I don't think they have decided on the implementation or not!