Configurator User Interface

can any one tell how can I create a new Custom User Interface in th oracle configurator developer with out using the standard UI Templates.

Hi,
I think this is a bit old posting , I hope by this time you would have solved the problem.
Are you getting any errors when you press the Test Button?
If not please see whether the % of Layout Area allotted for Navigation Frame, Make sure that its not less than 30.
I don't see any other reasons why its not getting displayed.But If there is any error coming up in the run time configurator screen then would be able to help you more.
Thanks,
Chanchal
[email protected]

Similar Messages

Problem in Configuring the Object Editor User Interface

Hi,
     I m using NetWeaver 7.0.11 & facing the problem in Configuring the Object Editor User Interface.In the Configuration Browser ,when i click on Object Editor & choose New Configuration & try to select service,it shows the flollowing error:
com.sap.caf.rt.exception.CAFBaseRuntimeException: Service manager initialization failed Illegal argument exception: Unable to create javax.ejb.EJBObject.
     at com.sap.caf.rt.ui.cool.generic.ServiceFacade.init(ServiceFacade.java:121)
     at com.sap.caf.rt.ui.cool.generic.ServiceFacade.<init>(ServiceFacade.java:50)
     at com.sap.caf.rt.ui.cool.generic.ServiceFacadeFactory.getFacadeInstance(ServiceFacadeFactory.java:51)
     at com.sap.caf.ui.utils.cool.CoolUtils.getServiceFacade(CoolUtils.java:123)
     at com.sap.caf.ui.ptn.objecteditor.ObjectEditorCC.getServiceFacade(ObjectEditorCC.java:505)
     at com.sap.caf.ui.ptn.objecteditor.wdp.InternalObjectEditorCC.getServiceFacade(InternalObjectEditorCC.java:245)
     at com.sap.caf.ui.ptn.objecteditor.config.OEconfiguratorLayout.onActionSelectModule(OEconfiguratorLayout.java:322)
     at com.sap.caf.ui.ptn.objecteditor.config.wdp.InternalOEconfiguratorLayout.wdInvokeEventHandler(InternalOEconfiguratorLayout.java:300)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Can anybody please tell,what can be the problem?
regards
Sumit

Hello Sumit
This is most probably the result of metadata corruption on runtime.
A possible workaround for this situation is:
Undeploy all the metadata DCs of all the CAF applications you have
deployed (these are the components which names end on "/metadata", excl.
caf/core/metadata and caf/tc/metadata (which are part of CAF itself)).
And then deploy the CAF applications again.
Regards,
Désiré

Configuration of SAP MDG User Interface in Customer Namespace - 7.0

Hello All.
I have been constantly reading about the mentioned content,
SAP MDG user interfaces from one single place. A dedicated WebDynpro application is provided to manage all user interface configurations.
You can also copy a standard SAP user interface configuration to the customer namespace and configure it to your requirements.
Can anyone give more details about the SAP MDG User Interface or share any links which denotes the same in detail.
Any Help Appreciated !!.
Regards,
Shankar

The document mentioned in the link does not state anything related to use user interface in customer namespace as suggested by sap in Innovations page. this is more about FPM applications.
Can you please suggest how do we use MDG User Interface in the customer environment directly as suggested by SAP.
Regards,
shankar

Status LIS9 of the User interface MP000200 missing

Hi All,
While creating leaving action. System is giving error (Status LIS9 of the User interface MP000200 missing.
Mentions below are my configuration.
Infogroup
COP 0001 Org assignment
LIS9 0002 Personal Data
LIS9 0006 address
LIS9 0105 Communication
And Personnel Action type are:- 0 0 0 MSN20 (Tick) (Tick) (Not tick)
Let me know how to resolve it.
Regard
Ashish

Hi,
make sure that LIS9 should not be used to the Infotypes which are having Time Constraint 1
Check V_T582A for time constratints and also check V_T588D to remove the operation LIS9 forLeaving/ termination action.
for your information
Infotype 0002 should NEVER be delimited as part of the Leaving Action.
The help text for the Operations field of the Info Group states the following:
In the Leaving action, use the "delimit" (LIS9) operation to delimit records.
Please remove the infotype 0002 from the info group, then run the leaving action, you will not find an error message
The reason why you get the error is because the status LIS9 does not exist on MP000200 .
You can see this via the menu painter via SE41.
regards,
mohammed
Edited by: 0mohammed1 on Oct 14, 2011 1:51 PM

My laptop will not start - it's telling me that "the logon user interface dll csgina.dll fail to loa

My Laptop will not start - it's a 4 year PC and it's runing on XP.
When I start I get this message" The Logon USer Interface DLL failed to load - Contact your administratoe to replace the DLL or restore the original".
How do I fix so I can start my windows.
Thanks,

Hello -
Try this:
- When you receive the error message that is described in the "Symptoms" section, click Restart.
- Press F8 repeatedly as your computer begins to restart. This triggers the Windows Advanced Options menu.
- Use the arrows on your keyboard to select Last Known Good Configuration, and then press ENTER.
(Also, You can try Safe Mode and do a "System Restore" from there.)
***Last Resort, you will have to edit the registry and this may prevent your computer from booting***
- boot your system and tap away at F8
- Select Safe Mode
- After Windows loads into safe mode.
- Start >> Run >> “regedit” Press Enter.
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon
- Look for the GinaDLL Key
- Select and delete this key and this key ONLY. DO NOT delete the entire Winlogon folder of keys.
- Close Regedit with the RED "X"and reboot the machine
****Although I am an HP employee, I am speaking for myself and not for HP.****
****Click the White Kudos star to say thanks****
****Please mark "Accept As Solution" if it solves your problem****

How to add a new Field to the WEB User Interface in CRM 2007

Dear experts,
I have been struggling to add a new field to the (CRM 2007) user interface from available fields for a specific view.
I have maintained settings in BS__WD_CMPWBàRuntime Repository editoràComponentàViewàConfigurationàNew ConfigurationàAvailable FieldsàField Propertiesàand save.
But the field is only appearing in display mode in the Web UI, which doesnu2019t allows any user input.
I need your help to resolve the issue, I would be grateful if you could provide step-by-step documentation with screenshots or any other kind of documentation.
Each suggestion will be appreciated.
Best regards,
Raghu ram.

Hi Raghu Ram,
I think you added a new custom field using some method like EEWB etc.,
Then, you are adding the field onto the UI using UI Configuration Tool .. right ?
These are the steps to diagnose:
Method 1.Check the field properties in the model browser first.
It should be showing 'C' i.e., CHANGEABLE. If it is showing as 'R', it is only READABLE.
In such a case you need to find a BADI to change the field properties.
For example, in Marketing Applications OBJ BADI has a method CHANGE FIELD PROPERTIES for this purpose.
Method 2. Debug and check what is the value coming for RV_DISABLED parameter in the GET_I method in BSP_WD_CMPWB. This should be FALSE.
Method 3. Check what are the field properties in the UI Configuration tool.
Make sure it is not a display only field.
Regards,
Masood Imrani S.

Error while deploying IDM 7.1 user interface file on Netweaver Java AS sys

Hi,
I am in process of installing IDM 7.1 in my landscape. I have done IC, RC in one system with windows 2003 + oracle. On other system I have Netweaver 7.0 SP14 Java AS system. I have configured as per SAP documentation.
While deploying IDM user interface 7.1 on SAP Netweaver Java system 7.0, I get following error in SDM:
Loading archive 'E:\software\IDM\DATA_UNITS\IC_UIS_710\IDMIC00_0.sca'
May 11, 2011 5:16:12 PM Error: Unresolved dependencies found for the following SDAs:
1.: development component 'tc/idm/wd/model'/'sap.com'/'MAIN_IDM710_C'/'3542284'/'0'
dependency:
name:     'tc/ddic/runtime/facade'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/wd/api'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'engine.j2ee14.facade'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/bl/logging/api'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/wd/legacy'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/bl/exception/lib'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/aii/base/offline/facade'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/bl/jrfc/api'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
May 12, 2011 11:04:09... Info: Loading archive 'E:\software\IDM\DATA_UNITS\IC_UIS_700\IDMIC00_0.sca'
Please advise,
Thanks,
Digesh

Hi,
SMP : http://service.sap.com/swdc -> SAP NetWeaver and complementary products" SAP NW IDENTITY MANAGEMENT" SAP NW IDENTITY MANAGEMENT 7.1
You would need to deploy the NW IDM IC 7.10 UIS FOR NW 7.00 component.
Regards,
Srikishan

Why do I get -18001 Errors using Customised TestStand User Interface

Hi all
I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
If anyone
has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
Thanks
Dave

David,
I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
LabVIEW : VI is not executable.
An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
2) The same error will occur when
a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
Building The Operator Interface
The following are steps if you are using a LabVIEW operator interface.
1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
Creating a LabVIEW Run-time Server
If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
Assembling the Test VIs for Run-Time Distribution
This distribution process uses one of the shipping TS examples that calls LV VIs.
1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
3) Confirm that the sequence runs without problem.
4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
6) Set the target directory to be something distinct like C:\temp\AssblVIs.
7) If you are using TestStand 2.0 skip adding Dynamic VIs
8) Save with or without diagrams. Its your choice.
Change Search Directories
Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
1) In the sequence editor select Configure>>Search Directories.
2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
3) Close the Edit Search Directories dialog box.
4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
1) In the sequence editor select Configure>>Adpaters.
2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
Distributing Components
-To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
-To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
-You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
Hope this helps.
Regards,
Kitt
=========================================
Title:
Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
Components that need to be distributed:
TS engine
Operator interface
LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
LabVIEW run-time engine
LabVIEW test VIs
Test sequence files
Actions before distributing:
It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
Assemble the test VIs for distribution.
Update the TestStand search directories so that the sequences reference the assembled VIs.
Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
Test the distribution components on the development machine.
Enter section headings, separating each section with a line break:
TS Engine Component
Operator Interface Component
LabVIEW ActiveX Server
Configuring the LabVIEW Standard Prototype Adapter
LabVIEW Run-time Engine Component
Assembling your Test VIs for Distribution
Note
TS Engine Component
With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
Operator Interface Component
You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
LabVIEW ActiveX Server
You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
Configuring the LabVIEW Standard Prototype Adapter
When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
LabVIEW Run-time Engine Component
If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
Assembling your Test VIs for Distribution
After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
Links: See Distributing LabVIEW Test VIs below
Note
Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
==============================================

What is the best way to get data to a user interface?

Hi,
I'm using labview 6i. I have an application with a handful of "core" vi's that actually run my application, doing the data acquisition, analysis, and control. I am currently using these same vi's for my user interface. I also have a number of vi's that contain menu's for configuring the "core" vi's. My questions is, what is the best way to seperate the "core" vi's from the user interface vi's. Global's, data socket, control references, others?
Thanks for the help.

Hi Sal,
I have been a strong advocate of control refnums ever since LV 6i hit the streets. I recomend you look into using them to provide this conectivity.
You could accomplish this by using a variation on the following.
In your UI, create refnums for each of the controls or indicators that must be monitored or updated. Pass the appropriate refnums to each of the "core.i's" at program init time. Inside each of the core.vi's, use property nodes to read the control's values when appropriate and similarly for display purposes. (Note: Not all boolean mechanical actions are compatible with this technique. In those case you will have to explicitly write false values after find the control to be true or vise versa).
By using this technique, you can keep the UI diagrams clea
n. Depending on your app. the UI diagram could consist of the init's I mentioned above, and a while loop that watches if it's time to exit.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Error -17501 flxCVIadp.dll when starting CVI full featured user interface on Windows 7

We see the following error dialog when we launch the CVI full-featured user interface (TestExec.exe):
"Error:
Unable to load test environment adapter 'flxCVIadp.dll'. Run setup to re-install or remove this adapter.
Could not connect to TSAutoMgr.exe server. DCOM permissions might be incorrect because of configuration changes for remote execution. To fix this issue, ensure that the current user is in the default DCOM access permissions or that no users are in the access permissions section of the dcomcnfg.exe dialog box. You can use the dcomcnfg.exe program, located in the Windows System directory, to change DCOM access permissions.
Error code: -17501, Unexpected Operating System Error."
When this error happens, we can't run any calls to CVI code from within the User Interface.
We are running Windows 7. We don't see the error if we run TestExec.exe from the default location:
C:\Users\Public\Documents\National Instruments\TestStand 2013\UserInterfaces\Full-Featured\CVI
We get the error message if we copy the CVI directory to somewhere else on the C:\ drive (C:\MyUserInterface for example). The error happens when we run TestExec.exe directly, but it does not happen if we are already running Labwindows/CVI and we launch TestExec.exe from CVI.
We are seeing this error with both TestStand 4.2.1 and TestStand 2013 running on different PCs. This error happens on Windows 7, but not Windows XP. Though we get the same error with our custom user interface, we see the same error with the stock CVI full-features user interface provided by NI.
Any ideas about why we can run this from the TestStand directories, but not any directory on our C:\ drive?
Thanks,
Peter

Hi Peter,
Based on the error messages it looks like this might be a Windows 7 security issue, which would be why it doesn't occur on XP since security is handled differently in that OS. Have you gone into dcomcnfg.exe and checked the DCOM permissions as described in the error message?

How do I fix incorrect resolution for Firefox user interface on Retina display Mac?

I have a 15" retina display Mac (roughly a year old) running Mountain Lion. A couple weeks ago the user interface in Firefox seems have switched from using the normal zoom level of every other application to the native dpi of the retina display monitor. This means that the UI elements are all extremely tiny, etc. Is there anyway to reset this without simply reinstalling or reseting the rest of my configuration?
Currently running Firefox 27.0.

You can try to modify the gfx.hidpi.enabled pref on the <b>about:config</b> page (<=0: disable; 1:all screens same res; >1:enable always).
*http://kb.mozillazine.org/about:config
Try to disable hardware acceleration in Firefox (you need to close and restart Firefox).
*Firefox > Preferences > Advanced > General > Browsing: "Use hardware acceleration when available"
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
You can set the layout.css.devPixelsPerPx pref on the <b>about:config</b> page to 1.0 and if necessary adjust layout.css.devPixelsPerPx starting from 1.0 in 0.1 or 0.05 steps (1.1 or 0.9) to make icons show correctly.
*http://kb.mozillazine.org/about:config
See also:
*https://support.mozilla.org/kb/forum-response-Zoom-feature-on-Firefox-22
Use an extension to adjust the text size in the user interface and the page zoom in the browser window.
You can look at this extension to adjust the font size for the user interface.
*Theme Font & Size Changer: https://addons.mozilla.org/firefox/addon/theme-font-size-changer/
You can look at the Default FullZoom Level or NoScript extension if web pages need to be adjusted after changing layout.css.devPixelsPerPx.
*Default FullZoom Level: https://addons.mozilla.org/firefox/addon/default-fullzoom-level/
*NoSquint: https://addons.mozilla.org/firefox/addon/nosquint/

Row currency has changed since the user interface was rendered.

Hi All,
we have developed and deployed an Application in Production, before four months,
Suddenly for the past two days we are getting an error after the page being idle for 2- 3 minutes.
Row currency has changed since the user interface was rendered. The expected row key was oracle.jbo.Key[3259 ]Once we get the error, the session scoped beans are resetting the values, and all the vo's cache are getting cleared(All the buttons in the page will get disabled and the menu will disappear).
but the same EAR is working perfectly in UAT and QA environments.
We have changed the "Enabletokenvalidation" as false and tested again, but the page itself is not loading after the change .
We have checked the Production and UAT weblogic server settings , but didn't find anything wrong.
WebLogic Server Version: 10.3.3.0
Studio Edition Version 11.1.1.2.0
if any ideas,
please help us...
Regards,
Ranjith

Hi All,
We have checked the error "Row currency has changed since the user interface was rendered. The expected row key was oracle.jbo.Key[3259 ]", we tuned the view objects, we changed the application page flows, and it is found that once we turn off the statevalidation (statevalidation =false), the error is not popping up, but it is getting fired in the server side as
oracle.jbo.JboException: JBO-35007: Row currency has changed since the user interface was rendered. The expected row key was oracle.jbo.Key[3259 ]
     at oracle.adf.model.binding.DCBindingContainerState.throwRowNotFoundException(DCBindingContainerState.java:318)
     at oracle.adf.model.binding.DCBindingContainerState.validateIterator(DCBindingContainerState.java:341)
     at oracle.adf.model.binding.DCBindingContainerState.validateStateFromString(DCBindingContainerState.java:482)
     at oracle.adf.model.binding.DCBindingContainerState.validateStateFromString(DCBindingContainerState.java:492)
     at oracle.adf.model.binding.DCBindingContainerState.validateToken(DCBindingContainerState.java:602)
     at oracle.adf.model.binding.DCBindingContainer.validateToken(DCBindingContainer.java:4852)
     at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.prepareModel(PageLifecycleImpl.java:117)
     at oracle.adf.controller.v2.lifecycle.Lifecycle$2.execute(Lifecycle.java:137)
     at oracle.adfinternal.controller.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:192)
     at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.access$400(ADFPhaseListener.java:21)
     at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$PhaseInvokerImpl.startPageLifecycle(ADFPhaseListener.java:231)
     at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$1.after(ADFPhaseListener.java:269)
     at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.afterPhase(ADFPhaseListener.java:72)
     at oracle.adfinternal.controller.faces.lifecycle.ADFLifecyclePhaseListener.afterPhase(ADFLifecyclePhaseListener.java:54)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:364)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:421)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:421)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:160)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)No Difference in server side configurations of prod and UAT
we are not using back button press or any other rowItearation in these pages and we are not changing the row key through code.
Simple Master page, with inline edit , add and delete with thousands of records.
Error is popping up after the page is being idle for 2- 3 mins. on the next request after the idle time, the error will pop up .
once the row currency error came, the current state of the view objects will get reset to the initial state(First row).
we don't know how to fix this issue, this issue is coming in production server only...
if any body comes across such an issue, please help us to resolve this issue..
Regards,
Ranjith C

This advertised application will not be installed because it might be unsafe. Contact your administrator to change the installation user interface option of the package to basic.

Hi there,
I was wondering whether anyone could tell me which feature in Windows 7 produces this message "This advertised application will not be installed because it might be unsafe. Contact your administrator to change the installation user interface option of
the package to basic." and whether it can be turned off in Windows to prevent this message from appearing when installing certain programs that aren't WHQL certified. At first I thought it was the UAC control that generated this message but found out
that it wasn't and then thought it was the DEP control and found out that it wasn't this either. I'm only seem to be getting this message when installing FileDirector Component Service Version 3 on a few of our workstations which is an add-on that allows file
integration with Office and is part of FileDirector WinClient Version 3.
Your help would be much appreciated.
Many thanks,
RocknRollTim
P.S. I know of a way to bypass this message but would ideally not like to have the feature turned on and for the message not to be appear for non WHQL certified program installations in order to make non WHQL certified program installations in the future much
easier, more simpler and straightforward to carry out. I was redirected by a moderator off the Microsoft Community Forum.

Hi,
You can try following options to disable this prompt, but we don't recommend you to do so since this feature helps you to protect your computer.
Option 1: Run command as admin:
bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Restart your computer to apply changes.
Option 2: Disable in GPO:
1.Type gpedit.msc in the Run dialog and press Enter.
2.In the Group Policy Editor, navigate to User Configuration → Administrative Templates → System → Driver Installation.
3.Double-click on Code signing for device drivers in the right-side pane as shown above.
4.In the windows that opens, choose Enabled. In the Options, choose Ignore as shown. Then click on the OK button to save the settings.
Restart your computer to apply changes.
Kate Li
TechNet Community Support
Unmarked as Answer based on OP's request.
https://social.technet.microsoft.com/Forums/en-US/35ab1279-c3a1-46be-9f7d-45e8606c1410/this-advertised-application-will-not-be-installed-because-it-might-be-unsafe-contact-your?forum=w7itproappcompat
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Reading the output values after each step executes in LabVIEW User Interface

Hello all,
Development environment: TestStand 2010 SP1 and LabVIEW 2010 SP1
Problem: is there a way to execute the subsequent steps programatically and get the output values from each of them?
I have already extended a little bit a Full OI interface for TestStand to load up any sequence, choose some of the steps and run them step by step (something like option to Run Selected steps). What I am trying to do is to add some actions between each step and do that in User Interface (I can't modify the sequence!), so I am starting the NewExecution with some previously configured InteractiveArgsParam and set an option breakAtFirstStep to True. Afterwards I am just doing something like Step Over when debugging the sequence and this works good, but I didn't fine a way yet to read the output values from the steps...
Then, if I wait until the execution finishes I can read my Results by processing the ResultObject, but this works only after finalizing of the test sequence. Since I wanted to stop after each step, read the values, do some actions and continue to the next step I tried to register an event callback for Trace of Execution View Manager. I can see that after each executed step this event is triggered, but when I try to read a ResultObject returned in Event Data it is not filled with values (ResultList seems to be empty?). Is it a proper behaviour or maybe I am doing the readout in wrong way? (It is the same VI as for reading ResultObjects after sequence finishes and there it works fine for arrays, containers and other data types).
Like I mentioned I can't modify the Test sequences, I can't add a UImessages.
What are my options? Should the trace event returns all output values from each steps or is it just used for status checking? Or maybe there is completely different approach to that matter?
Thanks in advance for any suggestions,
Best Regards.
CLA, CTD, CLED @ Test & Measurements Solutions Poland
Solved!
Go to Solution.

Thanks for your replay, I have tried to build it in my LabView Block Diagramm, es seems like this image.
But the variable GetNumSubProperties ist always 0. Why?
PS: I need only the variable "Step.Result.PassFail" from the last step, do you know, how can I get it? I think, it is maybe easier than read all the "Result".
Attachments:
ReadStepResultInLabview.JPG ‏39 KB

Disabling Controls in the Full Featured User Interface

Hi Ppl,
I do not want few controls (variables view, stack view) to be displayed in my full featured User Interface. What is the best way to do this. Are there configuration parameters(UserInterface.xml) that could make these controls in visible. Or Should these controls be make in visible only through the Visible Property.
Thanks

Hi Dennis,
Will Deleting the controls solve the purpose ? I tried moving the controls from the visible part of the front panel. but when the code was run the controls came back to their original position. Then I discovered that the full featured user interface has some code to set the position,size etc of the controls. This part of the code also checks the number of controls present. So I was wondering if just editing the configuration alone could disable the controls.
Thanks

Configurator User Interface

Similar Messages

Maybe you are looking for