.STP File Import Error Message...
.STP File Import Error Message...
(OP)
I have received a large .stp file (34MB) from a supplier and the translation fails. Here is the text I am receiving in the translation window:
"Unhandled UG exception caught.
With the following message <Internal error: memory access violation>.
Please refer to syslog for more info."
I downloaded the .stp file from a supplier FTP site.
We are using NX7.5.
Does anyone have any advice on what I might do to get this file translated?
Thanks in advance.
"Unhandled UG exception caught.
With the following message <Internal error: memory access violation>.
Please refer to syslog for more info."
I downloaded the .stp file from a supplier FTP site.
We are using NX7.5.
Does anyone have any advice on what I might do to get this file translated?
Thanks in advance.





RE: .STP File Import Error Message...
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
http://www.siemens.com/plm
http://www.plmworld.org/museum/
To an Engineer, the glass is twice as big as it needs to be.
RE: .STP File Import Error Message...
( The name of the log file seems to be missing in the NX75 dialogue, it used to be visible in older versions if i remember things correct.)
RE: .STP File Import Error Message...
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
http://www.siemens.com/plm
http://www.plmworld.org/museum/
To an Engineer, the glass is twice as big as it needs to be.
RE: .STP File Import Error Message...
Just note that if you do this, and its a large assembly, NX creates a part file for each component of the STEP assembly in the same directory the original STEP file was in, so if you have a thousand parts in that STEP file you might want to just put it in its own folder so you can keep track of them all.
RE: .STP File Import Error Message...
I tried your idea and received the following Open error message:
"Could not open D:\Documents and Settings\aaekaga\My Documents\iM2700.stp.
The following files could not be loaded causing this open to fail:
D:\Documents and Settings\aaekaga\My Documents\iM2700.stp - Error number: 1
OK"
-----------------------------------------------------------------
John Baker,
I cannot send this file to GTAC because it contains proprietary information that cannot be disclosed.
RE: .STP File Import Error Message...
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: .STP File Import Error Message...
How would I determine that bit of information?
RE: .STP File Import Error Message...
The NX log file will tell you if you have a 32-bit version of 64-bit version. John posted this information a few days ago.
If you have3 a 64-bit system, do you have more than 4GB of memory?
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: .STP File Import Error Message...
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
http://www.siemens.com/plm
http://www.plmworld.org/museum/
To an Engineer, the glass is twice as big as it needs to be.
RE: .STP File Import Error Message...
As for what sytem I am running, 32 or 64-bit, I still cannot find that information. My workstation does only have 3G of memory though.
RE: .STP File Import Error Message...
Help -> NX Log File
...and when the listing window opens near the top of the listing you will find a section which reads something similar to this:
Node Name :- XXXXXXX
Machine type :- GenuineIntel Family 6 Model 5 Stepping 5, Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz
OS :- Windows NT 6.1 (Workstation) (Build 7600)
:- 32 bit software version
# Processors :- 4
:- 1 packages, 2 cores, 4 logical processors
:- cache L1 128Kb / L2 512Kb / L3 4096Kb
Memory :- 4017Mb
The entry just below the line designated 'OS' (underlined above) will tell you what version of NX that you're running, irrespective of the what the system OS is. Of course, you can't run 64-bit NX on a 32-bit OS, but you can run 32-bit NX on a 64-bit system (which is what the log file excerpt above is indicating).
Anyway, I hope this helps.
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
http://www.siemens.com/plm
http://www.plmworld.org/museum/
To an Engineer, the glass is twice as big as it needs to be.
RE: .STP File Import Error Message...
And there it is, thanks again John:
Machine type :- GenuineIntel Family 6 Model 15 Stepping 11, Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
OS :- Windows NT 5.1 (Workstation) (Build 2600: Service Pack 3)
:- 32 bit software version
# Processors :- 2
:- 1 packages, 2 cores, 2 logical processors
:- cache L1 128Kb / L2 4096Kb / L3 0Kb
Memory :- 3069Mb
Total Swap :- 3910Mb
Free Swap :- 2510Mb
Machine supports 3G address space
Running customer environment
Session is running in codeset 1252 17
RE: .STP File Import Error Message...
Machine supports 3G address space
...is a give away that you're only running a 32-bit OS.
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
http://www.siemens.com/plm
http://www.plmworld.org/museum/
To an Engineer, the glass is twice as big as it needs to be.
RE: .STP File Import Error Message...
OS :- Windows NT 5.1 (Workstation) (Build 2600: Service Pack 3)
XP-64 only has 2 SPs!
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: .STP File Import Error Message...
E.g. C:\NX_work". I found that NX does NOT like "spaces" in the file search path....... Nor does it like "å, ä, ö" or the likes.... if you are in the nordic countries.