We have a custom menu built using J-Link. After months of successful use, out of the blue, the menu no longer launches on one of our Windows 7 64-bit workstations. It's isolated to this one workstation....the same user can sign on to any other workstation (XP 32bit or W7 64bit) and the menu will launch fine. Also, other users (plus administrator) have the same issue when signed into the problem workstation. This workstation did not have available "restore points" so reverting back to a previous working time is not an option. Something must be preventing its launch. We are close to simply wiping that workstation clean. Has anyone seen this or have any ideas?
I'm sending this on behave of our Toolkit app developer and can get more details if/when needed.
WF4 M150 DELL Precision T1500 W7, 64-bit
Mike Bills Ingersoll Cutting Tools Company Rockford, IL
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
I would compare the configuration files on the problem machine with the files from the one that works. When I say "compare", I mean you should get a tool like WinMerge or BeyondCompare to display two file versions side-by-side with differences highlighted.
At the same time, find out what external settings (environment variables, config.pro settings, etc.) this menu application depends on. It might have a dependency on an environment variable set by Windows before Pro/E launches.
Do any of these machines use a Java Runtime Environent (JRE) different from that furnished with Pro/E? Make sure the problem machine uses the same JRE as the others.
Finally, consider attaching a Java debugger to this application and testing its start() method. To do that, you'll need to launch at least one other JLink app, attach the debugger to the JRE, then start the menu application. This is an elaborate step; you'll need to attach the debugger remotely or install Java development tools on the problem machine.
Good luck with this -
|+| M a r k |+|
Mark Stallard Rapid Response Development information Solutions Integrated Defense Systems Raytheon Company
This message contains information that may be confidential and privileged. Unless you are the addressee (or authorized to receive mail for the addressee), you should not use, copy or disclose to anyone this message or any information contained in this message. If you have received this message in error, please so advise the sender by reply e-mail and delete this message. Thank you for your cooperation.