Crazy Errors using B1 Dev't Environment Project
I had created an Add-On using the B1 Dev't Environment code wizard. On my machine, it works great. I built the setup program also using the B1 Dev't Environment. That too worked well.
I tried installing the add-on onto a different PC, but keep getting an unhandled error from the common language runtime debugging services. It just says "Application has generated an error that cannot be handled". But I have error handling all throughtout the code.
I then built a simple "Hello World" app with only one event. It exhibits the same behaviour.
Has anyone seen anything like this?
I've built apps the "old school" way, but I really like the Dev't environment.
Hopefully, there's a work-around or a fix for this.
Thanks!
Hi Curtis,
I have been investigating the problem you found to run addons generated with B1DE CodeGenerator wizard when Microsoft Visual Studio .NET is not installed in the client machine.
I have found the problem and fixed it, I'm doing some testing on it and it should be released very soon on SDN as a new B1DE version 1.1.
The problem was due to the B1Wizard.dll referenced in your addons, this dll contains all wizard functionality and uses .NET dlls that are not included in the .NET Framework. In the next B1DE release addons will reference a B1WizardBase.dll that only contains the classes needed by your addons.
I will add some information in this main weblog as soon as the new B1DE release is published into SDN.
Regards
Trinidad.
Similar Messages
-
Error using wldeploy in unix environment
I am trying to use wldeploy ant task to deploy and undeploy applications from my server in a unix environment, and keep getting errors there, and not locally on a XP development workstation. Below are my buildfile and the error that I am getting. Anyone have any ideas as to what may be wrong?
build.xml
<target name="undeploy" description="Undeploys app">
<wldeploy user="${user}" password="${password}"
adminurl="${adminurl}" remote="true"
action="stop" name="${appname}" debug="true"
verbose="true"/>
</target>
And here is the error:
[wldeploy] weblogic.Deployer -debug -remote -verbose -noexit -name ${appname} -adminurl iiop://${host}:${port} -user ${user} -password ${password} -stop
[wldeploy] weblogic.Deployer invoked with options: -debug -remote -verbose -noexit -name broker-co
ntact.ear -adminurl iiop://${host}:${port} -user ${user} -stop
[wldeploy] [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE v
ersion V1_4 deployments
[wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at a
lice.healthpartners.com:8001, as user system
[wldeploy] [ServerConnectionImpl.getEnvironment():288] : setting environment
[wldeploy] [Debug.say():43] : getting context using iiop://alice.healthpartners.com:8001
[wldeploy] [Debug.say():43] : Connecting to MBeanServer at service:jmx:iiop://${host}:${port}/jndi/weblogic.management.mbeanservers.domainruntime
[wldeploy] java.io.IOException
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProvide
rBase.java:135)
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProvid
erBase.java:79)
[wldeploy] at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.j
ava:341)
[wldeploy] at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:262)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(Serve
rConnectionImpl.java:240)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServerForTyp
e(ServerConnectionImpl.java:191)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectio
nImpl.java:147)
[wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(Web
LogicDeploymentManagerImpl.java:148)
[wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeplo
ymentManagerImpl.java:118)
[wldeploy] at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentMan
ager(DeploymentFactoryImpl.java:84)
[wldeploy] at weblogic.deploy.api.tools.SessionHelper.getDeploymentManager(SessionHelper.java:4
32)
[wldeploy] at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:302
[wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137)
[wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[wldeploy] at weblogic.Deployer.run(Deployer.java:70)
[wldeploy] at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java
:43)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:615)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:364)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:341)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[wldeploy] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[wldeploy] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:4
0)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[wldeploy] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[wldeploy] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[wldeploy] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
[wldeploy] Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
[wldeploy] java.io.EOFException]
[wldeploy] at weblogic.jrmp.Context.lookup(Context.java:189)
[wldeploy] at weblogic.jrmp.Context.lookup(Context.java:195)
[wldeploy] at javax.naming.InitialContext.lookup(InitialContext.java:363)
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProvide
rBase.java:126)
[wldeploy] ... 35 more
[wldeploy] Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nest
ed exception is:
[wldeploy] java.io.EOFException
[wldeploy] at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:293)
[wldeploy] at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:190)
[wldeploy] at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:321)
[wldeploy] at weblogic.jrmp.BaseRemoteRef.invoke(BaseRemoteRef.java:221)
[wldeploy] at weblogic.jrmp.RegistryImpl_Stub.lookup(Unknown Source)
[wldeploy] at weblogic.jrmp.Context.lookup(Context.java:185)
[wldeploy] ... 38 more
[wldeploy] Caused by: java.io.EOFException
[wldeploy] at java.io.DataInputStream.readByte(DataInputStream.java:269)
[wldeploy] at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:234)
[wldeploy] ... 43 more
[wldeploy] [Debug.say():43] : Closing DM connection
[wldeploy] [Debug.say():43] : Unregistered all listeners
[wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'iiop://${host}:${port}': null. Ensure the url represents a running admin server and that the crede
ntials are correct. If using http protocol, tunneling must be enabled on the admin server.
Thanks.
ScottHi Richard,
I had the same issue using Eclipse. I just tried to run the
ant script outside of Eclipse and it worked fine.
This is an Eclipse-Ant Class Loader issue.
In order to make it work in Eclipse, You have to :
1. Open the External Tool Run Configuration.
2. Select your Ant script.
3. Select JRE Tab.
4. In Runtime JRE section, choose Seperate JRE.
Hope this helps !
Eric -
UNIX: problem running an DEV & QA environment using form/report servlets
UNIX: problem running an DEV & QA environment using form/report servlets
I am trying to setup on one server an DEV and QA environment using the Forms Servlet, Forms Listener Servlet and Report Servlet.
I think I have the Forms Servlet and Forms Listener Servlet running properly. The problem is setting up the DEV and QA environment for running reports.
For example, when in DEV environment I would like to run a report from a directory specified in the REPORTS60_PATH. This doesn't seem possible.
It might be easier if I describe my configuration first:
DEV: run all forms and reports from the directory /data/release/dev
QA: run all forms and reports from the directory /data/release/qa
---DEV & QA Settings Forms Listener Servlet:
zone.properties:
# DEV
servlet.fl60dev.code=oracle.forms.servlet.ListenerServlet
servlet.fl60dev.initArgs=EnvFile=/u01/app/oracle/product/ias/6iserver/forms60/server/dev.env
# QA
servlet.fl60qa.code=oracle.forms.servlet.ListenerServlet
servlet.fl60qa.initArgs=EnvFile=/u01/app/oracle/product/ias/6iserver/forms60/server/qa.env
---DEV & QA Settings Forms Servlet:
servlet.f60servlet.code=oracle.forms.servlet.FormsServlet
--- Settings for Reports Servlet:
servlet.RWServlet.code=oracle.reports.rwcgi.RWServlet
Custom Env files since we are using Developer 6i Patch 7
dev.env and qa.env
Here I specify FORMS60_PATH and REPORTS60_PATH,
eg: DEV -> FORMS60_PATH=/data/release/dev
REPORTS60_PATH=/data/release/dev
likewise for QA ../qa
In the formsweb.cfg file i have something like:
[dev]
serverURL=/servlet/fl60dev
form=test.fmx
[qa]
serverURL=/servlet/fl60dev
form=test2.fmx
I have tested the following and they work without problems:
1. forms listener test page, eg: http://webserver:7777/servlet/fl60dev
2. running forms from the 2 environments
eg: http://webserver:7777/servlet/f60servlet?config=dev
this runs the form in the FORMS60_PATH (/data/release/dev)
Now my problems start with Reports.
When I run a report from forms (using run_report_object) it will not run any reports
as specified in the REPORTS60_PATH
Even using this url:
http://webserver:7777/servlet/RWServlet?server=rep60&report=test.rdf&destype=cache&desformat=html&
userid=scott/tiger@test9i
It NEVER seems to pickup and use the REPORTS60_PATH. I have tried nearly everything.
I have gone throught the instructions in "Integrating Oracle9iAS Reports in Oracle9iAS Forms -
White Paper"
(http://otn.oracle.com/products/forms/pdf/277282.pdf)
and Forms6i Patch 7: Oracle Forms Listner Servlet for Deployment of FOrms on the Internet
(http://otn.oracle.com/products/forms/pdf/p7listenerservlet.pdf)
plus any other documents in metalink relating to forms, or report servlets. I am
totally confused, please help.
I have tried setting the REPORTS60_PATH in the following files without success:
custom.env (as specified by initArgs=EnvFile in zone.properties)
jserv.properties
in the zone.properties I have tried to set a custom env file for the report servlet:
servlet.RWServlet.code=oracle.reports.rwcgi.RWServlet
servlet.RWServlet.initArgs=EnvFile=/u01/app/oracle/product/ias/6iserver/forms60/server/dev_rep.env
NO LUCK.
The only place that I can set the REPORTS60_PATH
is in "[6iserver home]/reports60_server" file when I start the reports server (did I even
get this right - I do have to have a reports server running don't I?)
Does this meaan I have to run multiple report servers for each of my environments?
Based on all the documentation I thought that REPORTS60_PATH as specified in the files relating
to the forms servlet would be the place to specify the path.
As you will understand I am getting really fustrated with this and it seems to
me that the reports servlet configuration in 6i is really half baked and since 9i
is coming out it will never be fixed.I am even not able to run forms servlets from two different forms60_path, Is there any configuration do you make other than what you have mentioned in this post.
I already open a TAR in this regard, I am still waiting reply from ORACLE.
Thanks,
Shaik Ather Ahmed -
We have a tag query that works in our sandbox environment, but not in dev. I loaded the same JDBC drivers on both systems.
The project was exported from the sandbox, and imported into dev.
I have verified the Data Server set up is identical in both environments. Connection status in both environments is identical - running, same number of connections, etc.
When I try to run the query on sandbox in workbench, the query returns data. I get this error on the dev system -
SQL error has occurred on query java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'tag'.
Detailed error -
java.lang.Exception: SQL error has occurred on query [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'publicgrouptag'.
at com.sap.xmii.Illuminator.gui.workbench.populators.IlluminatorPopulator.get(IlluminatorPopulator.java:114)
at com.sap.xmii.Illuminator.gui.workbench.populators.TagListPopulator.get(TagListPopulator.java:47)
at com.sap.xmii.Illuminator.gui.workbench.components.desktop.custom.TagQueryBuilderPanel$6.construct(TagQueryBuilderPanel.java:723)
at com.sap.lhcommon.gui.ThreadCreator$2.run(ThreadCreator.java:94)
at java.lang.Thread.run(Unknown Source)
Any suggestions??One of your included JDBC driver archives has a class that matches the path provided by the JDBCDriver setting for the data server (likely the sqljdbc.jar file).
If you take the JDBCDriver setting:
com.microsoft.sqlserver.jdbc.SQLServerDriver
and replace the periods for sub directories and add a .class on the end you'll have:
com\microsoft\sqlserver\jdbc\SQLServerDriver.class
So if you unpacked the jar file you'd find this java class (and the other ones included with the driver).
Do you get the same error about 'publicgrouptag' and 'tag' objects when you test a tag query request for GroupList mode? These tables/views would be used by the underlying queries used to populate the tag details tab in the WB. Do you see these tables or view within the SQL Server? Does the sa user have appropriate permissions? -
Runtime error using jdk 1.4.1 in jdev
Hi,
I am using jdev 9032. My project uses jdk 1.3.1 the default that comes with jdeveloper. Now i have to make this application work on 1.4.1_05.
But when I run the app in jdev by changing the jdk to 1.4.1 or when I deploy in OC4J (standalone) 903 with JAVA_HOME=C:\JDK1.4.1, I get following error in both the case:
Auto-deploying file:/D:/temp/projects/Myproject/classes/ (No previous deployment found)... MyProjectServices_StatelessSessionBeanWrapper16.java:6: cannot access java.rmi.NoSuchObjectException
bad class file: D:\Utilities\java\jdk\j2sdk1.4.1_05\jre\lib\rt.jar(java/rmi/NoSuchObjectException.class)
class file has wrong version 48.0, should be 47.0
Please remove or make sure it appears in the correct subdirectory of the classpath.
import java.rmi.NoSuchObjectException;
^
1 error
Error compiling D:\temp\projects\Myproject\classes: Syntax error in source
Oracle9iAS (9.0.3.0.0) Containers for J2EE initialized
But when I compile my source using JDK 1.4.1 it is fine, and only gives me error while deploying.
Please let me know how to get this app deployed on OC4J with JDK 1.4.1
THANKS in advance
NarinderHi,
I figured out the solution.
Make the project use 1.4.1 and also replace the tools.jar file under %JDEV_INSTALL%\jdk\lib
In addition to this I have also changed the "SetJavaHome" environment variable in jdev.conf to use JDK 1.4.1
And everything is working fine and as I wanted.
FYI:
Replace tools.jar on OC4J Standalone(I used OC4J 903) with tools.jar of JDK 1.4.1 and then app can be deployed on OC4J as well.
Hope this helps someone.
Regards,
Narinder -
SSL error using Neutron API and CLI directly on controller nodes
VIO 1.0 + NSX + vSphere 6.0
I am trying to execute the following segment of code:
139 credentials = get_credentials()
140 neutron = client.Client('2.0',
141 username=credentials['username'],
142 password=credentials['password'],
143 auth_url=credentials['auth_url'],
144 tenant_name=credentials['tenant_name'],
145 endpoint_url=credentials['url'],
146 token=credentials['token'],
147 insecure=True)
148 response = neutron.list_ports()
When I run the Python script, it errors out with the following:
Traceback (most recent call last):
File "getMACAddr.py", line 148, in <module>
response = neutron.list_ports()
File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 111, in with_params
ret = self.function(instance, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 306, in list_ports
**_params)
File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 1250, in list
for r in self._pagination(collection, path, **params):
File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 1263, in _pagination
res = self.get(path, params=params)
File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 1236, in get
headers=headers, params=params)
File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 1221, in retry_request
headers=headers, params=params)
File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 1156, in do_request
resp, replybody = self.httpclient.do_request(action, method, body=body)
File "/usr/lib/python2.7/dist-packages/neutronclient/client.py", line 192, in do_request
**kwargs)
File "/usr/lib/python2.7/dist-packages/neutronclient/client.py", line 148, in _cs_request
raise exceptions.SslCertificateValidationError(reason=e)
neutronclient.common.exceptions.SslCertificateValidationError: SSL certificate validation has failed: [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
The /var/log/neutron/server.log file has the following corresponding entry for when the script tries to make the connection:
2015-04-11 07:17:31.941 2096 INFO neutron.wsgi [-] (2096) accepted ('10.27.16.164', 34495)
When I run the CLI from the same controller node, I get the error with or without the —insecure flag:
root@controller02:/tmp# neutron port-list
SSL certificate validation has failed: [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
root@controller02:/tmp# neutron --insecure port-list
SSL certificate validation has failed: [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
If I run the neutron CLI command from my local Macbook Pro, it works just fine. That leads me to believe it is a communication error when the controller node tries to talk to itself. I have tried setting the OS_AUTH_URL and OS_URL to both the localhost IP and the 10-network IP address -- both result in the same error.
Any ideas?
ChrisHello Chris,
Thanks for checking out VMware Integrated OpenStack and for sharing your concern.
By default, VMware Integrated OpenStack uses a self-signed certificate, which will require the use of the OS_CACERT environment variable in your openrc file and when using the API.
The better way to resolve this is to use a CA-signed certificate. Fortunately, VMware Integrated OpenStack makes the CSR generation and signed certificate import process very easy.
If this is production, of course, use a trusted Root CA. If this is a Dev Lab, you can generate your own Root CA certificate and use it for testing.
I wrote up a quick blog post on how to do this.
Let us know if you have any further questions.
Regards,
Trevor -
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
DaveDavid,
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.
============================================== -
Getting import error in jsp in creating war project of masthead for portal 7.31
Hi,
I am getting error in customize masthead war project in jsp for import statement.
<%@ page import="com.sapportals.htmlb.*"%>
<%@ page import="com.sapportals.htmlb.hovermenu.*"%>
<%@ page import="com.sap.security.api.UMFactory"%>
<%@ page import="com.sapportals.portal.prt.service.license.ILicenseService"%>
<%@ taglib uri="prt:taglib:tlhtmlb" prefix="hbj"%>
I have asked basis team for jar relative to these but they have not found in system.
We are using portal 7.31 version.
Kindly help me to remove this error from jsp.
Thanks in advance.Hi Hemendra,
At first i have done this and after that even i was facing error that's why i created this thread.
Kindly check my first post for error.
Getting import error in jsp in creating war project of masthead for portal 7.31
This question is Not Answered.(Mark as assumed answered)
Swati Joshi Apr 29, 2015 12:34 PM
Hi,
I am getting error in customize masthead war project in jsp for import statement.
<%@ page import="com.sapportals.htmlb.*"%>
<%@ page import="com.sapportals.htmlb.hovermenu.*"%>
<%@ page import="com.sap.security.api.UMFactory"%>
<%@ page import="com.sapportals.portal.prt.service.license.ILicenseService"%>
<%@ taglib uri="prt:taglib:tlhtmlb" prefix="hbj"%>
I have asked basis team for jar relative to these but they have not found in system.
We are using portal 7.31 version.
Kindly help me to remove this error from jsp.
Thanks in advance. -
Error using Chck out / Check in Function.
Hello Experts,
I have a problem when checking out and then cheking in a Contract Document:
There is a Contract document that needs a 2nd version. The user is checking out the Contract and making the corrections to the document. When he try to check in the Contract he gets the next error:
We are getting this error In production, we haven't had this error befor in DEV or QA.
Any ideas what could be happening.
Thank you in advance, a really appreciate your answers.
Best regards.I think its best to file a ticket on this and include application logs when the error occurs. Is this a particular user with a particular contract document? Or is this a more general issue in this environment?
Gary -
Error creating initial context with environment
Hi,
Currently we are working on a scenarios, where we need to integrate XI and webmethods using JMS.
It was working fine. But recently they have restarted the webmethods server. After that we re getting an error message like,
In Adapter Monitoring:
Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=server:port, java.naming.factory.initial=com.sap.engine.services.jndi.InitialContextFactoryImpl, java.naming.security.principal=XYZ, java.naming.security.credentials=ABC}for profile: ConnectionProfile of channel: CC_RCV_JMS_INon node: 3010950 having object id: ABCXYZ: NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:66)
In RWB
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: STARTING, on event: process_commence for DFA: C_RCV_JMS_IN:e4413a5265a436459e271d5e0dd4859b
Can one please tell me what the problem is?
Thanks in advance.
Regards,
Prasad Babu.Hi,
Check this link looks like same problem
Re: file to JMS(for MQ series)
Thanks
Vikranth -
I just encountered an error using the BPEL console in one of our test environments. I got the error when I clicked 'Manage BPEL Domain' and then clicked the 'Threads' tab. I also get the error when I click the 'Statistics' tab. Other tabs are OK, 'Configuration', 'Logging', 'Adapter Stats'.
Note that this is happening on one test server, other dev/test servers are OK.
Oracle BPEL Server version 10.1.3.3.1
Build: 0
Build time: Wed Jan 16 02:42:55 PST 2008
Build type: release
Source tag: PCBPEL_10.1.3.3.1_GENERIC_RELEASE
Exception Message:
[javax.servlet.ServletException]
The system encounters errors while running as the authenticated identity.
Exception Trace:
javax.servlet.ServletException: The system encounters errors while running as the authenticated identity.
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:429)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.unprivileged_include(ServletRequestDispatcher.java:160)
at com.evermind.server.http.ServletRequestDispatcher.access$000(ServletRequestDispatcher.java:51)
at com.evermind.server.http.ServletRequestDispatcher$1.oc4jRun(ServletRequestDispatcher.java:97)
at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:102)
at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:453)
at domain.jspService(_domain.java:210)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259)
at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51)
at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193)
at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198)
at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:131)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)I just encountered an error using the BPEL console in one of our test environments. I got the error when I clicked 'Manage BPEL Domain' and then clicked the 'Threads' tab. I also get the error when I click the 'Statistics' tab. Other tabs are OK, 'Configuration', 'Logging', 'Adapter Stats'.
Note that this is happening on one test server, other dev/test servers are OK.
Oracle BPEL Server version 10.1.3.3.1
Build: 0
Build time: Wed Jan 16 02:42:55 PST 2008
Build type: release
Source tag: PCBPEL_10.1.3.3.1_GENERIC_RELEASE
Exception Message:
[javax.servlet.ServletException]
The system encounters errors while running as the authenticated identity.
Exception Trace:
javax.servlet.ServletException: The system encounters errors while running as the authenticated identity.
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:429)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.unprivileged_include(ServletRequestDispatcher.java:160)
at com.evermind.server.http.ServletRequestDispatcher.access$000(ServletRequestDispatcher.java:51)
at com.evermind.server.http.ServletRequestDispatcher$1.oc4jRun(ServletRequestDispatcher.java:97)
at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:102)
at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:453)
at domain.jspService(_domain.java:210)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259)
at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51)
at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193)
at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198)
at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:131)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595) -
Wiki or Robohelp - What are the benefits of using a wiki vs publishing projects in robohelp?
What are the benefits of using a wiki vs publishing projects in robohelp? I currently use RH9/RH9 Server and publish multiple SSL. The company is looking to stop using Robohelp and replace our online help authoring tool (RH) with a wiki. Are there any benefits of going to a wiki environment. What RH features/functions that I have today will i not have by having IT import our robohelp files into a wiki?
I know that a wiki is not an authoring tool, but someone must think it is and we'll still have all the functionality of publishing multiple SSLs, reports, etc once in the wiki environment. Any comments - is this the best route?Hi,
There are many differences. The idea of a wiki is to allow anyone to view and/or edit the content. Depending on the wiki system, you can set access control for viewing and editing.
Wiki's typically have simple syntax (html in a wiki is a serious security risk), allow image embedding, links and attachments. You will need to learn the specific syntax (rather easy, but also very limited).
What will you lose? This depends on the features available in the wiki system as well as the available plugins. A few downsides:
- WYSIWYG editor limited, if at all.
- No snippets
- No variables
- Dropdowns (may be possible through plugins)
- Index
- Styling based on css classes (mostly supported through HTML which is a security concern)
- Only one version of your support system: multiple versions require multiple installations/configurations.
- No searching in attachments.
- No CBT (Though some wiki's allow comments in the wiki code)
- No Word/FrameMaker import.
- You have to create your own CSH calls.
On the upside:
- Most wiki systems are free, even for commercial use.
- The syntax is quite simple, allowing you to quickly write text.
- Wiki's typically offer good support for syntax highlighting.
- They are very easy to set up.
- Most wiki's have plugins to enable comments.
The greatest downside in my opinion is that you always have the latest version of all files. Whenever you update a page, everyone immediately has the latest version. And if you want to create help for a feature that isn't released yet, you will have to use access control to make sure not everyone sees the (unfinished) help for the unreleased feature. With RoboHelp you have a single source that creates a one way output.
We use both RoboHelp and wiki's: RoboHelp for customer help and wiki internally to share knowledge. And sharing knowledge is what wiki's are designed for.
Greet,
Willam -
How To Control the Langauge of BI Reports (Using Excel 2013, oData, and Project Server Online 2013)
Although I buried and posted the following question indirectly in a recent post, I would like to do so here to try and elevate it in the hope that I can get an answer.
It is in regards to creating reports using Excel 2103 to querry Project Server 2013 Online using oData. I would like to be able to control the langauge of my reports that I create for others to view.
Just creating and then saving the Report and Data Connections in a language directory does not seem to drive or determine the language of the report. A colleague of mine over here is using the same directories as I am, and his turn
out to be French like his environment. Mine, even though I save the files in same the French directories, display in English.
Any ideas on how I can create reports so that they display in another language, eg., French when using Excel to create reports? I know that we can set the language in an internet browser to control the language that the result is returned, for instance,
when querying https://.../pwa/_api/ProjectData/$metadata
\Spiro Theopoulos PMP, MCITP. Montreal, QC (Canada)Correction! Thanks to Doug Welsby of Microsoft and some our other MS friends who worked behind the scenes to correct/ assist me on this, I got the right answer after all... the difference between, example a French oData command/ statement,
and an English one is the inclusion of the square brackets with the language abbreviation/ code e.g., "[Fr..]" in the oData connection string/ statement. For further reference, see the connection files provided by Microsoft in the Reports and
compare the syntax for the same report/ different language. There is where you will see what and how Excel is able to differentiate/ control what language that the report result will return.
\Spiro Theopoulos PMP, MCITP. Montreal, QC (Canada) -
How to Connect Oracle Database 10g with using Oracle Dev 10g
Hello there,
I have problem with connection on database 10g using oracle dev 10g on the same server.
The message is: TNS... bla..bla... it means not connect.
Please advice
Regards
Leksonojust simple
copy the from the database instance the tnsnames.ora
file's entried into developer folders tnsnames.ora
file and you can connect to DBFirst of all there is no such error as TNS... bla..bla... it means not connect.
there are several errors for the tnsnames, post the exact error
And it is not recommended that you copy it from the database's tnsnames file, it doesn't always work.
to configure the tnsnames.ora you have 2 ways, manual and GUI.
For GUI use the Net configuration assistance from your Devsuite home and for manual you need edit the tnsnames.ora file usually under %ORACLE_HOME%/NETWORK/ADMIN
You need to specify the connection string name, the hostname and the database SID name. It should look something like this.
<connection identifier> =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = host name)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = SID)
)Regards,
Tony -
Yosemite Server: Apache shm errors with proxy_balancer | SASL errors using user alias
Dear OSX Server Ninjas,
I recently upgraded my 10.9.5 Mac mini running Server 3.2.2 to Yosemite + Server v4, directly to v4.0.3. The box serves the whole Mail/Cal/Contacts/VPN palette as well as some websites, Git repos and some custom software. See below for network setup.
After battling the most blatant issues (some easy to fix but hard to find, others hard on both), I'm almost back to a working server setup … but some things keep bugging me even after days of log-reading and OD tricks. In the last days, I have read countless discussions here as well as on stackoverflow/serverfault/apple.stackexchange and blogs, so I'll try to be as thorough and precise as possible to show what I have tried so far – sorry in advance for the long post
… and since you might not read to the bottom: Thanks in advance for any help, especially with the Apache problem!
My setup
OSX Server v4.0.3 running on Yosemite 10.10.1 ➞ both latest official releases
host + DNS
Hostname configured for public domain mydomain.net, web traffic on selected ports comes in through router NAT
Server has a static IP on the local subnet 192.168.178.0/24
Server running local DNS and performing lookups for all clients in the local subnet, forwarding to the router at 192.168.178.1
Primary zone for mydomain.net with records (A, NS, MX) pointing to said static IP
changeip -checkhostname is successful
Public IP is currently configured at the domain registrar through his name servers
SSL
Trusted third-party certificate installed for host.mydomain.net (Common Name + SAN for two subdomains)
Used to secure all services
Qualys SSL Test Grade B (capped due to OSX's openssl 0.9.x not being capable of TLS1.2 and Intermediate CA SHA-1 )
TLS working both inbound and outbound according to CheckTLS.com
OpenDirectory
Recreated after upgrade (probably not necessary, since issue persists), re-imported groups + users from WGM backup files
Only the server itself is bound to the directory, other devices just access services through network accounts (CRAM-MD5, MD5-Digest)
Problems
Apache shm errors: Apache fails to create slot memory when proxy module is enabled
As soon as I start a service which requires the Apache proxy_balancer module (e.g. Cal/Contacts, ProfileManager), this starts filling up my Apache's error log:
[Mon Jan 12 01:41:17.979882 2015] [proxy_balancer:emerg] [pid 2949] (28)No space left on device: AH01179: balancer slotmem_create failed for p26d9e669--1011640492
[Mon Jan 12 01:41:17.979894 2015] [:emerg] [pid 2949] AH00020: Configuration Failed, exiting
[Mon Jan 12 01:41:28.297127 2015] [slotmem_shm:error] [pid 3026] (28)No space left on device: AH02611: create: apr_shm_create(/private/var/run/slotmem-shm-p26d9e669--1001322955.shm) failed
[Mon Jan 12 01:41:28.297347 2015] [proxy_balancer:emerg] [pid 3026] (28)No space left on device: AH01179: balancer slotmem_create failed for p26d9e669--1001322955
[Mon Jan 12 01:41:28.297355 2015] [:emerg] [pid 3026] AH00020: Configuration Failed, exiting
When I increase the Apache LogLevel to trace1, I get this as well:
[Mon Jan 12 02:11:43.190303 2015] [slotmem_shm:debug] [pid 5501] mod_slotmem_shm.c(367): AH02602: create didn't find /private/var/run/slotmem-shm-p26d9e669-813569972.shm in global list
This causes the Apache to crash constantly, which is … unnerving. After googling around for a while, I tried the following steps:
Stop Services that use the Apache (Web, *DAV, ProfileManager)
sudo apachectl stop
Remove all orphan cache/slot files (.shm, ssl-cache, proxy.*) from /private/var/run
Reboot the server
Start up the Services again
Curiously enough, this worked for a while! But I was getting several log messages about dropped proxy connections, and sometimes the ProfileManager page would time out. Then, the issue started to reappear and does not seem to be fixed again with the steps above. I looked through the Apache config files and config plists for the Services in question, as well as the default config files. The only thing I have so far is that as long as there are no active proxy connections, the Apache runs smoothly – but all goes awry when slotmem files are created (a lot of them). Sometimes, I am able to turn on the Calendar service, but switching on Contacts produces the error … one time, I even got Calendar + Contacts running, and all went well until I enabled Profile Manager.
I found several error reports with similar or identical errors from other Apache 2.4.x users, but most of those were developer talk on mailing lists, or suggested steps that did not work for me (or were inapplicable on the OS X Server Apache environment).
SASL errors using user alias for WebDAV-Digest authentication
Short version: I am unable to authenticate through WebDAV-Digest with a user's alias (defined in Server Admin > Users > Context Menu > Advanced Options or WGM). Using the main short name of the same user works flawlessly. Password Server Error log just shows:
AUTH2: {234023578237md5hash2384234, mainshortname} WEBDAV-DIGEST authentication failed, SASL error -13 (password incorrect).
The password is 100% correct: When I set up a test CalDAV account and put in alias+PW, it did not work (OS X Dialog showed “could not be verified”, Server log as above). Leaving the password field filled and just switching the user to the main short name went through instantaneously, with the Server log showing
AUTH2: {234023578237md5hash2384234, mainshortname} WEBDAV-DIGEST authentication succeeded.
Notice the same MD5 hash and canonical short name, yet different results. I don't know if this is a new “feature”, a result of mail aliases being handled differently (at least I read that somewhere) …
Additional Questions
Should I configure the DNS for public use, instead of the Split-Brain configuration (local network gets local IP, outside traffic is directed by registrar NS)? I read several articles explaining that Split-Brain is common in large organizations, but might introduce weird networking issues. Entering the external IP as a Round Robin alternative for the internal does not seem sensible to me.
I also have a question concerning LDAP log entries like this one below, but I'll put that in this already open discussion:
=> bdb_idl_delete_key: c_get failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994)Today the same error occurred on a customers server.
We don't use Calendar or Contacts.
We only have some websites configured and want use NetInstall for deployments.
As soon as I disable the Profilemanager the httpd starts over and other websites and NetInstall via HTTP are working fine.
When I reenable Profilemanager the httpd processes are gone and I see the same stuff in Apache's error log...
Maybe you are looking for
-
4/28/2014 - Release - Flash Player 13
The next version of Flash Player is available for immediate download. In today's release we've updated Flash Player with important security updates. We recommend users update to the latest version. Security update details can be found here: Securit
-
Displaying html page with in the applet
I want to open an html page in the applet. If i use showDocument() of applet, it opens the html page in the browser, but i want to open the html page with in the applet(i.e., applet should display the html page). Is there any way which i can do the a
-
Transfer my movie from iTunes to video app
I purchased tv shows from iTunes. I'd like to watch them offline. How do I transfer them from iTunes to my video app?
-
SOA Composer and editing Routing Rules
I have been trying to edit my human workflow routing rules decision table from the SOA Composer web interface. the routing rules appear in the list of ruiles available to open and edit but when I open the routing rules it defaults to the IF/THEN view
-
Multiple Calendars - Proxied Calendar
We have approx. 130 BB users in our organization, and we're all on BB 9630s, running BES 5.0 (upgrading to the next version on Friday). Using Exchange 2007 as backend email system and Outlook 2007 as the front end. I've browsed through the forums he