application builder error.llb

Similar Questions

• Application Builder error

  Hello

  I use LV 8.6 and Application Builder. My Labview vi uses some third party vi to control a linear motor. The vi works well not respected. Can I complie an exe without errors, but when I run the exe, (on the same PC), I get the below error. (Connect.vi is the third party VI used to start communication with the motor). In this case with my vi and vi example of a third. I also have an exe from one of the vi from the engine supplier that works.

  On the error, I don't know why he mentioned NEITHER-488, I've never used (I don't think) so why it causes an error?

  Thank you

  Richard

  

  
  

• Creating application builder error

  After installing Labview 9.0f2, is no longer possible to build the application

  Depending on the anti-virus, an exclusion zone should be created on the directory where the exe file are created.

• Application Builder error 7

  LabVIEW 8.0

  We use mutual FUNDS to gain access to the data fields.
  Here's the problem during construction Exe Application & Source Dist:
  -----------------------------
  7 error to ABAPI Dist report read link Info Error.vi-> ABAPI Dist
  Parameters of the CMP on the drive Hier.vi-> ABAPI get File.vi settings->
  EBEP_Invoke_Build_Engine.VI-> EBUIP_Build_Invoke.vi->
  EBUIP_Build_Invoke.VI.ProxyCaller

  Possible reasons:

  LabVIEW: File not found. The file may have been moved or deleted, or the
  the file path might be incorrectly formatted for the operating system. For
  use for example- as Windows path separators: on Mac OS, and Linux.
  ---
  NOR-488: No Board

  We tried to recompile using CTRL + SHIFT & arrow button, but it has not been resolved.

  Thank you all...
  I manage this problem.
  Just an FYI... The main problem is that I had ignored the warning box that is pop up, after I opened the vi. Some sub vi were responsible for different folder.
  The point is to "Make sure that there is no caveat will appear after the opening of the screw."

  -----------

• Application builder cannot build the exe. Error 8 has occurred in AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi

  I bought a new Dell laptop (Windows 10 Pro) and LV 2015 (32-bit) is installed. I copied my project files and tried to build the exe file and received the error 8. After much searching for an answer, I created a minimal test with just a single white vi project and an exe based build spec to reproduce the error with. Whenever I try to build, I get the same error 8:

  An error occurred during the generation of the application. You don't have the appropriate permissions to create the application at the specified location, or the application is in use.

  Invoke the node in AB_Engine_Build_Method_Wrapper.vi-> AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi-> AB_UI_Frmwk_Build.lvclass:Build.vi-> AB_UI_FRAMEWORK.vi-> AB_Item_OnDoProperties.vi-> AB_Item_OnDoProperties.vi.ProxyCaller
  
  Method name: Build: Application

  Error 8 has occurred to AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi

  Possible reasons:

  LabVIEW: File permission error. You do not have the correct permissions for the file.

  I can't quite imagine I could have permissions issues. I of course have full admin on the machine privileges.

  I've seen other messages (like this one) who speak to have Windows Explorer opened the path of construction when it tries to go up and get this error. I made double sure that I don't have ANY Windows Open Windows Explorer, trying to build. There was a mention in one of the positions which perhaps of LabVIEW in current directory is defined in the file generation, but I'm not quite what that means, or why that might happen when there isn't usually prevents me to build on other machines.

  I tried the procedure described in the KB, but no help.

  Interestingly, I have created a virtual machine (Win 10) for a different project and installed LV 2015 32 bits in the virtual machine, and all my applications build very well in the virtual machine. But on OS from my physical machine, I get this error 8 for all construction applications.

  I tried to fix LabVIEW, and also I tried to uninstall reinstall LabVIEW. Nor was the error to go away completely. After the repair, the project has successfully generated once. But subsequent attempts to build fail with the same error.

  See the attached test project and the build log.

  Thank you

  Nathan Scharfe

  CLD

  My best guess is that some external process is the use of the folder and do not let you write here. The most likely candidates are anti-virus software or a service of indexation of a certain type. I'm guessing that he sometimes managed everything simply because it is a race condition and in these cases, the blocking part yet or is already done.

  You could try the building to a network drive, when these forces are less likely to be able to make the lock or you could try to find a software that shows you what software has handles opened in a folder and control for an offender. I seem to remember that the Process Explorer and SIW show this, but it's far from my area of expertise.

• 1 error in writing on a text - installer with Application Builder file

  I wrote an installer using the Application Builder to install the runtime engine that allows any computer without LabVIEW to run an .exe program. Setup runs and installs engine race and then as a .exe VI. When it is done installing, the .exe VI opens automatically.

  An error appears when the .exe opens and says "1 error in writing to a text file". If the user clicks on the error that it can run the program without problem, it converts file formats in a file .lvm. Automatically, it generates a new file name and saves the file in the same directory, but with a different name.

  Why did it only happen when opening first upward? The program tries to run when it automatically opens? Is there a file path residual left in the program that trys to run first, before that the user put his own file path in the program?

  I am semi new to labVIEW (a few months) and that nothing shows that would create this error at the beginning of the program.

  Thank you

  Hi Scott,.

  Well, you could model a little VI and turn on debugging highlighted to test your idea!

  THINK THE STREAM!

  How a Boolean entry should WAIT for the action of the user? It should be read according to the stream!

  What this small pseudo-code:

  REPEAT
  
    Wait (50ms)
  
  Until the button

  Or how about an event in the user queue structure?

• LV Application Builder: fixed error "the system cannot find the file specified."?

  Hi all

  I don't mind banging my head out of something that feels complex, but it's still frustrating to be baffled by something that seems simple... I have LabVIEW 2014 and Application Builder. I've built a program that works perfectly as a VI, and then compiles and runs without fault as a .exe. But I can't get the installer to work. I get the following error:

  

  The suggestions in this thread and this KB article, I created a new specification to build installer, then a new application build spec, then a new project with all my screws in, build and test setup at each stage. None of this seems to make a difference.

  I ran the installer as an administrator, I created the Advanced installation directories (in which case it does not have the privileges to create folders) and built an installer without the performance in. None of this worked either. Finally, I played a bit with put all my subVIs in a library.

  So I guess it's a quirk in my program from the tutorial worked. Does anyone have any experience or advice on what specific aspects of a piece of Nice program with AB installers? It is a primary VI, less than a dozen, some Type Defs and no material integration subVIs. Seems to be a program fairly simple and straightforward, but maybe something in it is persona non grata with Application Builder?

  Are you running in deep subfolders with long folder names and file names? Perhaps some of the paths are getting too much time managing?

• ORA-28112: failed to perform the function of guidance - error in the Application Builder

  Hey all,.
  
  I added a political function to one of my paintings, and now I get this error when I try to update a report region that refers to this table.
  
  "The query cannot be parsed into the generator. If you believe that your query is syntactically correct, check the generic "columns" box below the source of the region without analysis. "ORA-28112: failed to perform the function of guidance."
  
  If I remove the policy then everything works fine. My application works well with the policy in place. I just get these errors in the application builder when refreshing a report or a LOV that references the secured table.
  
  The analysis schema is APPL_USER.
  
  Here's the political function:
  
  FUNCTION DOCUMENT_TABLE_POLICY (object_schema IN VARCHAR2 DEFAULT NULL
  object_name IN VARCHAR2 DEFAULT NULL)
  RETURN VARCHAR2 IS
  v_nt_seq NUMBER;
  BEGIN
  IF use = "APPL_USER" or INSTR(user, 'ITFC_') = 1 THEN
  RETURNS A NULL VALUE.
  END IF;
  
  IF V ('APP_USER') IS NOT NULL THEN
  IF V ('F_NT_SEQ') IS NOT NULL THEN
  v_nt_seq: = V ('F_NT_SEQ');
  ON THE OTHER
  SELECT NT_SEQ
  IN v_nt_seq
  OF APPL_USERS
  WHERE UPPER (NT_ID) = UPPER (V ('APP_USER'));
  END IF;
  
  RETURN ' (DOCUMENT_TYPE, MANAGED_BY_ELEMENT, PROGRAM_CODE, CONTRACT_NUMBER) IN (SELECT DISTINCT R.DOCUMENT_TYPE, USL. ELEMENT, USL. PROGRAM_CODE, USL. CONTRACT_NUMBER OF USL, R IPRACA_SECURITY_ROLES IPRACA_USERS_SECURITY_LINK WHERE R.SECURITY_ROLE_SEQ = USL. SECURITY_ROLE_SEQ AND USL. NT_SEQ = ' | To_char (v_nt_seq) | ')';
  END IF;
  
  -UNAUTHORIZED USERS CANNOT SEE ANY DATA
  RETURN '1 = 0';
  END;
  
  This is how to set up the policy:
  
  BEGIN
  
  DBMS_RLS. () ADD_POLICY
  object_schema = > 'APPL_USER '.
  , object_name = > 'APPL_DOCUMENT '.
  , policy_name = > 'APPL_DOCUMENT_POLICY '.
  , function_schema = > 'APPL_USER '.
  , policy_function = > ' APPL_SECURITY. DOCUMENT_TABLE_POLICY'
  );
  
  END;
  
  
  Any help would be greatly appreciated!
  
  Thank you
  
  Jonathan Hart
  APEX 3.1.1

  It is possible that this raises an exception:

  SELECT NT_SEQ
  IN v_nt_seq
  OF APPL_USERS
  WHERE UPPER (NT_ID) = UPPER (V ('APP_USER'));

  Is there a line in APPL_USERS where NT_ID = ?

  Scott

• Application Builder: the Application closes after the Launcher

  I'm launching my application executable that was built with the Application Builder. I use framework actor and have a Launcher.vi which is defined as the start VI and launched the actor parent. When I run the executable, I can see the front Launcher.vi opens and closes quickly, but the main façade never opens. Where should I start to debug my executable? Is there something obvious that I do not forget to do? I compared my configuration of the application to the actor framework example (that does not produce an executable work) and can not find something that is different.

  OK, I thought about it. I went back and watched closer launcher for the example of master actor and I noticed the block launch actor VI didn't have "Open front actor Core" value true which seemed strange because the front opens correctly for this application. I searched in VI properties for the parent of project example actor Core.vi and saw that the appearance of the window has a custom configuration. The options to see the façade when called and then close while initially closed have been verified in the sample project but unchecked for my project. I also watched the run settings and saw that the example is configured to reentrant run clone Shared while my project is configured to run not reentrant.

  Changing the appearance of window correctly launching my main façade. I played with the run settings to see what those and noticed that when my VI is configured to not reentrant run, child actors do not seem to get started. In addition, the stop on my front button will close the front panel, but the application is still running. Change the mode to Shared clone lance child actors correctly and completely closes the application when you press the stop button. I also tried clone reentrancy pre-allocated to see what would happen. errors of launcher just immediately say the call by reference VI is not executable.

  I guess it makes sense. Framework of the actor expects that the State is not maintained when a player is destroyed, so shared clone ensures that each instance of a child actor has its own pool of memory to be erased when the player is stopped. http://zone.NI.com/reference/en-XX/help/371361J-01/lvconcepts/reentrancy/

• LabView Application Builder, FieldPoint-> Programmabsturz beim Aufstarten einer erzeugten EXE-Datei

  Hallo, habe folgendes problem:

  Fur einen Kunden wurde ein Programm zur Datenerfassung developed (2005).

  Die Daten werden über die Fieldpoint-Schnittstelle und einer CSV-Datei abgespeichert erfasst.

  Fur ein Folgeprojekt der Kunde einer Version dieses Programms eine möchte.

  Therefore, one wurde der Application Builder acquired um eine Exe-Datei zu ruler.

  Da ich sonst nichts mit mache LabView ist meine nicht mehr die latest LabView-Version

  Version of LabView 7.1

  Application Builder as LabView 7.1

  FieldPoint Version 4.1

  DAS create einer EXE-Datei war auch been, nur beim EXE der implement auf dem neuen Zielrechner, das Gingold

  Programm beim Aufstarten die application great mit einer Fehlermeldung ab (Fehlerbericht a Microsoft senden...) und one sharp.

  The Rechners green Ereignisanzeige der in diesem Falle immer die message ".NET Runtime 2.0 Error Reporting."

  Typ: Fehler

  Ereignisskennung: 1000

  Warum das Programm ist leider nicht auszumachen absturzt sometimes, der of mit of ich aber dass Schnittstelle schatze

  zu FieldPoint (Version 4.1) hat zu tun.

  Wenn ich das Programm aus meiner Entwicklungsumgebung aus Starte works are properly.

  Testweise habe ich auch schon die Entwickungsumgebung auf dem neuen Zielrechner installed, auch dann so mein Programm wenn ich're manuell von sleeps aus starte. Kann ich beim ruler der Exe-Datei noch was please gemacht haben? Aber warum die EXE-Datei dann ab und zu works?

  Hi ralfn,

  Thank you for the information on Hyperthreading.

  The new PC contains a CPU dualprocessor.

  After deactivation of the screening "will launch several threads" in the LabView software

  (Tools-> Options-> Performance and memory), my EXE file works fine.

  Thank you, best regards,.

  Schnetzi

• Application builder bands DLL

  Hello

  I have a project that controls a piezo stage. This is done via a DLL from the manufacturer, and I used the wizard 'Import-> Shared Library' to make a library lvlib in the user.lib folder. The lvlib folder contains a bunch of screws and two DLLs (a manufacturer and I think come from LabView: wdapi1120.dll).

  The screws of this project are now being used in another project which brings together several projects material control. The lvlib file appear correctly under this meta-project dependencies.

  I then tried to build a stand-alone executable, but the manufacturer request stripped away of the two DLLs from the lvlib: wdapi1120.dll. This leads to two error messages (see images). The workaround I found is to uncheck "additional Exclusions-> Remove unused members of the libraries in the project" so it works now.

  But I wonder, why the application builder strips way a DLL file that was placed there by before LabView? I guess he's checking the references. So if there is no reference, why must she then?

  My feeling is that I'm missing something here if all clearification would be great.

  This DLL is not a LabVIEW DLL but your first DLL dependency. And this DLL was only placed by LabVIEW in the lvlib if there is any explicitedly VI accessing it. Otherwise, it has been added in there by which it is created the driver and LabVIEW interface.

  Given that your project does not call any VI that refers to this the application builder DLL determines that it is not used and deletes if you check the option according to. Cannot be generic for LabVIEW determine that your DLL must this second other than reimpleminting all Windows executable DLL loader in LabVIEW, which is certainly beyond the scope of what LabVIEW should never try.

• Application builder does not

  Hi people.

  I can't build this application. When I try and open it I get the following error (also attached).

  Exception: Access to EIP Violation (0xC0000005) = 0x772D8E19

  Version: 1.0.0.0

  When I run like a VI in labview, it works very well without any problems, but when I build it with the application builder I can not open the .exe file.

  The project is only 1 VI, which opens an executable file from the command line, implements a few keys to generate a QR code in the file called, then cropps it and saves it.

  Is this something to do with how I'm building the application. If it works in labview surely it should work when built.

  I've built other projects from the command line, use the .exe and they open very well, but I can't talk about it.

  Any help would be greatly appreciated.

  Select this option.

  Code too sequential sems with many duplicate ode and it uses 100% of CPU core when doing nothing. There should be a small wait in the case of fake of big business structure. Couldn't you mix together into a single table U8 once and use a single autoidenxing FOR loop? Code would take on a postcard! I would use also "build path" to create paths.

  In any case, why the UIBC use a relative path ("...) "" "\Windows\System32\user32.dll")? Try changing it to 'user32.dll' instead.

• the application builder exe file does not work

  Hi all

  I have a usb data acquisition module, it is USB 2408-2AO of MC. I order the module with a VI and it works very well. I used the Application Builder to create an exe of the VI. The exe works great too, but only on my own computer and not on other computers.

  I already made the other screws's exe files and never had any problems to run the exe on other machines. I also tried to do an installation of the VI program and not just a stand-alone application, but once again the final application does not work. The application runs without problem on the target computer, no errors are displayed, but it just does not control the USB module as it should. I think the problem is that the builder Application does not include al screws required in the installation program, particularly MC devices to control the USB device. I tried to manually choose the screws, but it seems that everything is included... I am sure that the problem is the USB device, as I did other exe files and they all work very well (but they do not control the USB device) on other machines. Someone has any idea how to solve the problem?

  
  

• Report Generation Toolkit and Application Builder

  I'm going crazy trying to get out.

  I am trying to build an EXE using Application Builder program. The program uses the Office Report Generation Toolkit.

  I tried including the dynamic screw in the project, the computer development and the CD. I still have the same problem: the application does not start Excel. It's as if the commands are going into a black hole. It's not even an error message.

  I enclose my VI report for you to view. Any help is appreciated.

  
  

• chronic build error

  Since today, I get a build error in all of my projects:

  Error occurred during the build.

  Errors under builder "App descriptor Validator" of the project "MNKit".

  java.lang.NullPointerException

  Google gives no guidance on this. Restarting Momentics, or clean up projects does not help.

  At the opening of bar - descriptor.xml, I get:

  java.lang.NullPointerException
  to com.qnx.tools.bbt.core.signing.BarSignerTool. (BarSignerTool.java:105)
  to com.qnx.tools.ide.bbt.internal.core.BBTNativeSDKProvider$ BBTNativeSDKDescriptor.getBarSigner (BBTNativeSDKProvider.java:172)
  at com.qnx.tools.bbt.core.sdk.AbstractBlackBerryTabletSDKDescriptor.getValidator(AbstractBlackBerryTabletSDKDescriptor.java:122)
  at com.qnx.tools.ide.bbt.internal.core.BBTNativeSDKProvider.getValidSDKs(BBTNativeSDKProvider.java:97)
  to com.qnx.tools.bbt.core.sdk.IBlackBerryTabletSDKDescriptor$ IRegistry$ Impl.collectValidSDKs (IBlackBerryTabletSDKDescriptor.java:327)
  to com.qnx.tools.bbt.core.sdk.IBlackBerryTabletSDKDescriptor$ IRegistry$ Impl.getValidSDKs (IBlackBerryTabletSDKDescriptor.java:311)
  at com.qnx.tools.bbt.internal.core.utils.BlackberryTabletSDKUtils.getAvailableTargetPlatformVersions(BlackberryTabletSDKUtils.java:130)
  at com.qnx.tools.bbt.xml.internal.ui.editor.bbtxml.forms.GeneralAdvancedPart.getAvailablePlatformVersions(GeneralAdvancedPart.java:146)
  to com.qnx.tools.bbt.xml.internal.ui.editor.bbtxml.forms.GeneralAdvancedPart. (GeneralAdvancedPart.java:69)
  at com.qnx.tools.bbt.xml.internal.ui.editor.bbtxml.forms.GeneralPage.createLeftContent(GeneralPage.java:65)
  at com.qnx.tools.bbt.xml.internal.ui.editor.bbtxml.forms.GeneralPage.createFormContent(GeneralPage.java:54)
  at com.qnx.tools.bbt.xml.internal.ui.editor.bbtxml.forms.BBTFormPage.createFormContent(BBTFormPage.java:92)
  to org.eclipse.ui.forms.editor.FormPage$ 1.run(FormPage.java:152)
  at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
  at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:150)
  at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:241)
  at org.eclipse.ui.forms.editor.FormEditor.addPage(FormEditor.java:325)
  at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:211)
  at org.eclipse.ui.forms.editor.FormEditor.addPage(FormEditor.java:308)
  at com.qnx.tools.bbt.xml.internal.ui.editor.bbtxml.BBTXMLEditor.addBBTPage(BBTXMLEditor.java:233)
  at com.qnx.tools.bbt.xml.internal.ui.editor.bbtxml.BBTXMLEditor.createGeneralPage(BBTXMLEditor.java:240)
  at com.qnx.tools.bbt.xml.internal.ui.editor.bbtxml.BBTXMLEditor.addPages(BBTXMLEditor.java:324)
  at org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:138)
  at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348)
  at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670)
  at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
  at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
  at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:289)
  at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2945)
  at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2850)
  to org.eclipse.ui.internal.WorkbenchPage.access$ 11 (WorkbenchPage.java:2842)
  to org.eclipse.ui.internal.WorkbenchPage$ 10.run(WorkbenchPage.java:2793)
  at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
  at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2789)
  at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2773)
  at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2764)
  at org.eclipse.ui.ide.IDE.openEditor(IDE.java:651)
  at org.eclipse.ui.ide.IDE.openEditor(IDE.java:610)
  at org.eclipse.ui.actions.OpenFileAction.openFile(OpenFileAction.java:99)
  at org.eclipse.ui.actions.OpenSystemEditorAction.run(OpenSystemEditorAction.java:99)
  at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:221)
  to org.eclipse.ui.navigator.CommonNavigatorManager$ 3.open(CommonNavigatorManager.java:185)
  to org.eclipse.ui.OpenAndLinkWithEditorHelper$ InternalListener.open (OpenAndLinkWithEditorHelper.java:48)
  to org.eclipse.jface.viewers.StructuredViewer$ 2.run(StructuredViewer.java:866)
  at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
  to org.eclipse.ui.internal.JFaceUtil$ 1.run(JFaceUtil.java:49)
  at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
  at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:864)
  at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1152)
  at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:462)
  to org.eclipse.jface.viewers.StructuredViewer$ 6.handleOpen(StructuredViewer.java:1256)
  at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:275)
  to org.eclipse.jface.util.OpenStrategy.access$ 2 (OpenStrategy.java:269)
  to org.eclipse.jface.util.OpenStrategy$ 1.handleEvent(OpenStrategy.java:309)
  at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
  at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
  at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
  at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
  at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
  at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
  at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
  at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
  at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
  at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
  to org.eclipse.ui.internal.Workbench.access$ 4 (Workbench.java:2499)
  to org.eclipse.ui.internal.Workbench$ 7.run(Workbench.java:679)
  at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
  at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
  at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
  at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
  at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:597)
  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
  at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

  I am running on a Mac with the new Oracle Java 1.6.0.37 Mountain Lion.

  solved.

  Re-install Momentics and the simutaor is done.