Hi,
I installed Nx I-deas 6.5 on Win 10. But while I was installing Orbix, I got an error.
I could do design with Nx I-deas 6.5 on Win10. But when I tried to export step/iges or another format, I got an error about Orbix.
I tried to run Nx I-deas 6.5 on Win7. I didn't get the error. I could export it. Doesn't orbix win10 work? or what should I do to run it?
I did not check this but I am not very convinced that this is related to the graphic driver... beacause the only change was the deinstallation of Office 2016 and the installation of Office 365 - on both machines...
Based on similar discussion in the private forum,
Hi Mehmet,
That's right, I had the same issue. The Orbix installation (from the I-DEAS prerequisites or the command line) fails to complete. Some of it is installed, so you can continue installing I-DEAS, but the Orbix services are not created. The STEP/IGS translators need Orbix, so that is why they are not working.
I finally got them created and running. The workaround is to create the Orbix domain and services from the command line.
These are the complete steps (not sure if you need all of them, but this did the trick for me):
Hope this helps!
Eric
Hi
FYI in attachment. Thank you.
plmLHT
Looking into upgrading to NX1847.
I can't find documentation where it states what version of MS Office is supported.
Found the Windows info, but not MS Office.
Any help would be appreciated.
Hi
Platform, Browser and Excel (not MS Office entirely) etc. information can be found by referring release notes of each NX version.
Thanks.
I was looking under GTAC and found the Windows info and thought Excel info would be there also.
My mistake, thanks again.
Hi,
resolved, the absolute WCS was very far from the CSYS.
I used to use "ug_askCurrentWorkPart" with "Update for external change" to control a set of part name attributes.
But that was painful in large assemblies. The update took a long time because that command rolls through every single feature.
I found using a custom "Save As" Journal to be the best way around that.
Whenever the journal is used to save the part it parses the filename with logic and writes the data to a set of attributes.
All,
If this was me I would have a look into the defining process. I would break it down to simpler entities with a bit of "directional sence".
Best Regards
Fred
Hi
Thank you for the information 
. I completed all the steps but I got an error about domain. I have wrote a .batch file to compile the script which you shared with me on the last step.However there is a problem with the NX_IDEAS_6 domain information. How can i solve it ? You can find the batch file below.
-----------------------------------------------------------------------------------------------------------------------------------------------------
@echo off
cd /d "C:\PLM\IONA\etc"
start "OrbixE2AInstall.exe" /domain NX_IDEAS_6 /hostname mehmet /install /java_home C:\Program Files (x86)\Java\jdk1.8.0_121 /license C:\PLM\IONA\etc\RunTimeLicenses.txt /orbix_dir C:\PLM\IONA
-----------------------------------------------------------------------------------------------------------------------------------------------------
After running the batch file , i got below error.
Best Regards
Mehmet
Hi Mehmet,
The domain name might be different, because I had the issue in NXI 6.6. The domain should be listed in your InstallDir\bin\setup_varbs.cmd.
Kind regards,
Eric Berben
Hi
Just so you are aware: we do not support I-deas 6.5 on Windows 10.
The first certification on Win 10 was I-deas 6.6. We just released I-deas 6.7 last week, which also supports Win 10.
If you are doing a fresh install at this point, to be the most "future proof", I suggest downloading and using 6.7.
One of the biggest issues we found when we were first testing I-deas on Win 10 is that most operations require Run as Admin, because of the way I-deas is structured (it calls other scripts and executable that access files on the OS - Win 10 has locked many such operations for better security).
So be sure the CMD window you run with is Run as Admin and also set any short-cuts you execute the same.
I added some notes on this point to the README for Win 10 when we released 6.6.
I don't think you have an issue with the DOMAIN name. It has not changed from NX_IDEAS_6 since I-deas 6.0 (we probably will never change it).
I also suggest looking the previous thread where
Hi
Please try the following:
1) From Excel select: "File > Options > Add-Ins"
Is Ug listed? It should be.
2) At the bottom of the Add-ins dialog, set: "Manage: Excel Add-ins" and select "Go"
Is the Ug add-in checked? It should be.
3) From Excel select: "File > Options > Trust Center > Trust Center Settings". Select Trusted Locations (left menu)
Is the path to the Ug.xla was listed? If not, add it (next step).
4) Select "Add new location... > Browse" and browse to the NX install directory that contains the
ug.xla (e.g., C:\Program Files\Siemens\NX 10.0\UGII) > OK > OK > OK > Exit Excel
5) Restart NX, create a new part and select Menu > Tools > Spreadsheet
Regards, Ben
Hi
I recently upgraded from Office 2016 to 365 myself, as did my cube-neighbor.
He had a similar issue and it turned out he needed to re-register his ExcelAddin (we are both using 1847 Series, where a single add-in replaces ug.xla for both 32 and 64-bit Office).
In your case, since you are still on NX 12...
1) Make sure ug.xla is still set correct (e.g. if you remove NX 12 it will remove it, but then you would get message along the lines of "cannot find ug.xla").
Make sure the Excel Add-in Manager can still "find" ug.xla in the NX 12 path.
2) NX 12 only supported 32-bit Office, 32/64 started from January 2019 with 1847 Series. Not even sure there is a 32-bit option for 365, but apparently the other machine you tested in OK , so either your 365 is different, or you have 32-bit:
https://docs.plm.automation.siemens.com/tdoc/nx/12/release_notes#uid:index_xid920445:xid732649
I'll leave it at that since it sounds like GTAC is already on the case.
Taylor, any update on this?
We have a big round of reviews coming up In August. think for now we'll implement additional steps for our designers, -reserve a layer for the measurment display
-show that layer in every view
-be certain to make that layer the work layer when the model is saved for the last time
Not a big deal to work around this bug, but hopefully it's something on the next rollout/update to correct
Hello Experts,
I have created my template parts and drawing sheet templates and I use the master model approach to create drawings.
When I create a part and add attributes for example Tol_Class_Holes on the part file the same is carried across to the drawings theoratically by using DB_DWG_TEMPLATE_Tol_Class_Holes.
This works for me if the attributes are assigned a value in the part file before the drawing is created, however, if a user does not assign a vlaue to these attributes before creating the drawing and edits it later, the same are not passed on to the drawing.
In the attached example, my part file has attributes that have been filled after the drawing is created, however not all are passed on to the drawing.
When I add an extra sheet to the same drawing, template is populated correctly.
Is there a way to force load this on the drawing file so that everytime a user changes value in the part file the same will get reflected staright away?
Thanks in advance.
Regards,
Rushi
I have done this already.
At first the ug.xla was not there but I added it manually and now all your described checks are OK - but it still does not work... any reg keys I can check?
