Error using the JNDI Attributes interface on LDAP

I'm having a problem accessing an objects attributes on an LDAP server.
Encountered the following naming exception: ' javax.naming.CommunicationException: Bad file descriptor [Root exception is java.io.IOException: Bad file descriptor]; remaining name '' '
This occurs when executing the line:
DirContext ctx = (DirContext)initialContext.lookup(name);
initialContext is a valid Context which has already been instantiated, and name is a valid String value.
Any help would be greatly appreciated.
Regards,
Paul

What initial context factory and ldap you are using? They have different formats for files. So even your name is a valid String name it may be in wrong format. You should check it out. Follow the specified format.
PC

Similar Messages

How to get the naming attribute of an LDAP using JNDI.?

Hi,
How do we fetch the naming attribute of a LDAP using JNDI. Is this possible using JNDI..?
By default, every LDAP has been set with a naming attribute such as 'uid' or 'cn'. This could be changed according to business needs.
How to determine this using JNDI.
Regards,
Barani

Are you trying to call the portlet Customization form directly from the browser?

Error occurred in deployment step 'Add Solution': A feature with ID '' has already been installed in this farm. Use the force attribute to explicitly re-install the feature.

Hi I am getting the error
Error occurred in deployment step 'Add Solution': A feature with ID 10495515-2482-41fd-98eb-3c87f739f54b has already been installed in this farm. Use the force attribute to explicitly re-install the feature.
when trying to deploy web parts
question 1 - how do i use the force attribute when deploying from visual studio
question 2 - am i deplying it to the right place, if i deply it to the
url:port that points to my central admin tool it deploys but i cant seem to see it in any of my webs in my site collection, if i deploy it to the
url:port that points to my site collection I get this error.
im new to all this by the way :)
thanks in advance

If you are deploying from Visual Studio then please follow this post:
http://sharepointfordeveloper.blogspot.com/2014/03/solved-visual-studio-issue-error.html
Open the visual Studio and navigate to the feature XML file and add the bellow attribute.
AlwaysForceInstall="TRUE"
The <FeatureName>.Template.Xml output would be some think link this.
<?xml
version="1.0"
encoding="utf-8"
?><Feature
xmlns="http://schemas.microsoft.com/sharepoint/"
AlwaysForceInstall="TRUE"></Feature>

Using the binding attribute within Tomahawk's t:dataList tag

I am trying to create a .jsp page with a dynamic list of tables. Each table on the page has a dynamic number of columns. I read an excellent blog ([The BalusC Code - Using datatables|http://balusc.blogspot.com/2006/06/using-datatables.html#PopulateDynamicDatatable]) that taught me how to create dynamic tables using the binding attribute. I can now get the tables with dynamic columns working.
What I would like to do next is nest the dynamic tables within a Tomahawk t:dataList tag:
<t:dataList value="#{utilitiesTableSegBean.attributeTables}" var="attributeTable">
    <h:outputText value="#{attributeTable.title}"/>
    <h:panelGroup binding="#{attributeTable.dynamicTableGroup}/>
</t:dataList>
{code}
When I run my app I get this error:
javax.servlet.ServletException: javax.servlet.jsp.JspException: org.apache.jasper.el.JspPropertyNotFoundException: /s/UtilitiesTableSeg.jsp(57,56) '#{attributeTable.dynamicTableGroup}' Target Unreachable, identifier 'attributeTable' resolved to null
Why do I get this error?
If I remove the h:panelGroup tag then the h:outputText tag works just fine. Why does 'attributeTable' resolve to null for the binding attribute of h:panelGroup, yet works for the value attribute of h:outputText?
So then I thought that I might be able to make it work with an index into a bean property that returned the list of table objects. So I tried to modify my panel group tag to:
{code}<h:panelGroup binding="#{utilitiesTableSegBean.attributeTables[0].dynamicTableGroup}"/>{code}
I was just doing a quick initial test and expected to see the first table repeated over and over because I had hard coded the value of '0' as the index. But I was wrong. It listed through all of the tables correctly. Why? This makes no sense to me!
So I changed my jsp again so that it looked like this:
{code}
<t:dataList rowIndexVar="tableIndex" value="#{utilitiesTableSegBean.attributeTables}" var="attributeTable">
    <h:outputText value="#{attributeTable.title}"/>
    <h:panelGroup binding="#{utilitiesTableSegBean.attributeTables[tableIndex].dynamicTableGroup}"/>
</t:dataList>
{code}
This is how I expected to code it so that the tables would all be shown correctly. And it gives this error:
org.apache.jasper.JasperException: An exception occurred processing JSP page /s/UtilitiesTableSeg.jsp at line 57
(Line 57 is the line with the h:panelGroup tag.)
Root cause: javax.servlet.ServletException: javax.servlet.jsp.JspException: java.lang.IllegalArgumentException: null
I would really like to get the original version working, but any feedback and/or suggestions would be greatly appreciated. I have spent a lot of time trying to figure this out and I just don't know where else to look.
Thank you very much!
Dave

Yes, sorry about that - I started off trying to prove a potential solution.
Aim:
A user logs onto a weblogic application and is authenticated against OID. The application is making SOAP service calls to a proxy endpoint monitored by another vendors software which authenticates the user against the ldap and checks their roles to see if the user can call the service.
Solution so far:
The initial application gets the username from the JAAS principal, but the password is not supplied. I can easily supply the SHA password digest to it (but putting a cleartext password in the header will probably not be given the go-ahead). This would enable the application to make the SOAP call with a username and digest.
The software protecting the services can be configured in a variety of ways to authenticate the user to the ldap. One involves using the wsse username token in the header (cleartext password or digest).
This authentication is failing and I don't yet have the diagnostic tools available to see which stage is in error. I was trying to prove that you could actually authenticate with an SHA password digest by doing a bind.
Regards

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.
==============================================

How to add or modify an entry using the JNDI

Hi all,
Usually I have used the netscape library to write directory application, now I have to use the JNDI ...
Could I have some examples about the add modify and delete entry on the directory?
Thanks a lot!
M@x

Download the LDAP Service provider at http://java.sun.com/products/jndi/index.html#download_ldap
It has some example code too

Feature with ID 15/.. has already been installed. Use the force attribute to explicitly re-install the feature

Hi everyone,
I really become desperate with this one. I know, it's mentioned hundred times in the web, and it really works when you use a force deployment, but my simple question is: Why?
To explain my issue: We have several SharePoint 2010 solutions which we want to deploy to SharePoint 2013 with Visual Studio 2012 running on Windows Server 2012. Site solutions work. But farm solutions just don't. I get the error (you
guessed it): A feature with ID 15/... has already been installed in this farm. Use the force attribute to explicitly re-install the feature.
And it does really work with the force attribute, but why on earth do you have to use the force flag? Something has to be different, and if there is an already installed feature with this ID, then why can Visual Studio not uninstall or
deactivate it by itself first? This error never occurred with SharePoint 2010 and VS2012, although features are already installed.
Thanks a lot for your effort.
Best regards,
Patrick

Hi Check this
1.Double click on the feature.... ( or right click and choose properties)
2.then in the properties window make
3. ALWAYS FORCE INSTALL = false... (this should be false)
Manoj Gangwar | Sharepoint MCPD | Sharepoint MCTS |

The name attribute on the img element is obsolete. Use the id attribute instead.

When I valadate my page I get an error "The name attribute on the img element is obsolete. Use the id attribute instead." In DW CS5.5 I cannot seem to enter an ID without DW also adding the ID as a name attribute too. Aside from manually going in and removing the name attribute from the code.

It won't hurt to leave the name attribute in your <img> tag. In fact, it may be necessary if you are going to add an image rollover behavior, since DW's javascript relies on that name attribute's value to correctly identify the desired image on the page.

CNiGraph3D: MsgBox "Error accessing the controls custom interface"

When calling CNigraph3D:lot3DSurface(CNiReal64Vector, CNiReal64Vector, CNiReal64Matrix) under W2k I get a message box: "Error accessing the controls custom interface". The same application runs on a different multi-boot machine under Win98, WinNT and W2k. What causes this error? DLL incompatibilities?

Hello,
this error occurs only for the Graph3D (the application has also a 2D-Graph which works fine).
I think the ActiveX is properly installed, since I can see the graph3D before the data is scanned. The user can rotate the view, zoom in, change the scale,...
Only when the scan is finished an the application wants to plot the data, the message box pops up.
I did not install the controls on the testing machine, since LabVIEW 6 was installed and the controls have been installed. The *.ocx have the same size/version/date as on my dev. machine. LabVIEW has no problems with the graph3D control. (I forgot to mention this in my question, sorry for that).
Are there any differences in installing the controls when used by LabVIEW and by an MS VC++ app usin
g CW-controls?
On another machine is was sufficient to call regsvr32 to the *.ocx and everything worked fine.
thank you
Steffen

How can I use the color adjustments interface that shows up for camera RAW on jpeg files?

How can I use the color adjustments interface that shows up for camera raw on other files types? The HLS controls had the secondary color adjustments (6 colors instead of the 3). Plus, it had same vibrancy and a better Curves interface. Yesterday was the first time I imported raw into Photoshop CS5 and I got that really cool interface. What is that? Can I use that on other file formats?

Actually I am using the Tradional Chinese Version, when I try to edit the jpg file with camera raw, the system shows that there is no camera raw plug-in. The cmaera raw never work.

How to get cm:search to use the max attribute when creating the SQL query?

When we use the max attribute in the cm:search tag, it does not seem to honor the max attribute when creating the SQL query. However, the result returned from the tag is limited to the number specified by the max attribute. Then the tag seems to work as intended, but the performance will be sub optimal when the SQL query returns unnecessary rows to the application.
We use the cm:search tag to list the latest news (ordered by date), and with the current implementation we have to expect a decrease in performance over time as more news is published. But we can’t live with that. We need to do the constraint in the SQL query, not in the application.
The sortBy attribute of cm:search is translated to “order by” in the SQL query, as expected.
Is it possible to get cm:search to generate the SQL query with an addition of “where rownum <= maxRows”?

Hi Erik,
The behavior of a repository in regards to the search tag's max results parameter is dependent on the underlying repository's implementation. That said, the OOTB repository in WLP does augment the generated SQL to limit the number of rows returned from the database. This is done in the parsing logic. This behavior may differ with other repository implementations.
-Ryan

Help! with creating a J2ME program using the http connectivity interface

So this is what I have to do using the http connectivity interface:
1.Creating two threads – one for communication (receiving and sending) and the other (main) thread will be for interaction with the user.
2.The main thread will make use of three midlet forms. The first form will ask for web page address (URL) and separately for a delimiter which will separate the words in the URL document, the third form will display the ratio of all symbols on the page and the number of occurrences of the delimiter specified
3.The second thread should perform http connectivity to the WWW, utilise the web page address supplied and connect to the appropriate web page and read its content, count all symbols on the chosen page, count the number of occurrences of the delimiter given as user input on the same form as the web page address, calculate the ratio between the two and pass this information to the first thread to display.
I have many questions but my main concerns are:
*1. How to communicate using HTTP interface within a thread*
*2. What is a delimiter in the context above and how should it be implemented*
I've been thrown in at the deep end with little programming experience with this assignment. If anyone can share a similar example or answer my concerns I'd be more than happy.
Thanks in advance.

thelane wrote:
hi thanks for the response.
As I said I have coded in other languages before, but this is a new for me in java. I needed to get it working quickley. Now I can clean up.
I will have a look at method and see how I get on.
ANy similiar examples would be great.
Thanks.I can certainly give you a similar example.
Say you have code such as this:
int a = 10, b = 11;
int temp = 1;
for(int i = 2; i < a; ++i) {
temp *= i;
System.out.println(a + " factorial is " + temp);
temp = 1;
for(int i = 2; i < b; ++i) {
temp *= i;
System.out.println(b + " factorial is " + temp);Each section of code takes the factorial of the current variable an outputs it. The factorial code can be placed within a method to be called more easily, as such:
public void factorial(int num) {
int temp = 1;
for(int i = 2; i < num; ++i) {
temp *= i
System.out.println(num + " factorial is " + temp);
}Then, whenever you need to call it, you can just do so:
int a=10,b=11,c=12;
factorial(a);
factorial(b);
factorial(c);

HELP!!! Message - (One or more applications are using the iTunes scripting interface. Are you sure you want to quit?) How do I get this to stop?

I bought a new Sony Vaio Laptop running Windows 8, 64bit, i7 processor. Everytime I open iTunes and then close out, the following message occurs: (i-tunes message - One or more applications are using the iTunes scripting interface. Are you sure you want to quit?) Then it starts counting down from 20 seconds unless I just click on the (Quit) button. How do I get this to stop? Please be specific, I am challenged when it comes down to computers.
Thank You

This was extremely annoying for me, also. I started uninstalling unneeded Sony applications to try to narrow down the problem. It turned out not to be a Sony application... it is some functionality built into the bluetooth driver software package by Broadcom. Uninstalling the bluetooth package (via the control panel) takes care of the problem. Itunes also boots up way quicker. But uninstalling it will remove features related to bluetooth and nfc. For me, that isn't an issue, since I don't use them. Since you said you're "computer challenged" I would probably just send an email to sony complaining about the problem. They'll get in touch with Broadcom eventually (the manufacture of the drivers) and get the problem fixed.
Side note: the Broadcom package is huge... nearly 1GB in size. Which is crazy. I can't imagine what it does considering the size of it. Entire operating systems can take up less storage. Also, I have no idea how it starts an itunes plugin without placing it into the standard plugin directories.

Trunking on a T2000 using the internal ipge interfaces.

We have a new T2000 with solaris 10 + sun trunking for solaris 10 installed.
Has anyone been able to setup trunking on a T2000 using the internal ipge interfaces
The T2000 has four of these interfaces and would be nice to run trunking over a pair for performance / redundancy reasons.
I did first look at link aggregation in solaris 10 but the ipge interface is recognised as a legacy device not supported by link aggregation.
Thanks for any help

From: http://www.sun.com/servers/coolthreads/tnb/parameters.jsp
Improving Network Performance by Transitioning from ipge to e1000g Network Drivers
Transitioning to the e1000g network driver provides significant enhancements to network performance as a result of:
* better handling of small network packet sizes
* lower processor utilization
* network port link aggregation (trunking)
To transition to the e1000g driver, please follow the steps below:
* Install patch 118833-24 or later
* Convert from ipge to e1000g by installing patch 123334-02 and running the script provided
* Update the /etc/system file so that is contains only the following command:
set pcie:pcie_aer_ce_mask=0x1
* reboot your system
No tuning is needed for e1000g

ITS Error: "Use the most recent SAPGUI"

We currently have an SRM 4.0 system with support package 6 with a basis
component at 640 suport package 13. We are using the classic scenario
and are connected to an R/3 system what was recently upgraded to ECC
6. When we attempt to try to use the WBS, Cost Center or asset search
helps we get the following error: "Use the most recent SAPGUI
version". We can click past the error and eventually get the search
results.
This issue does not occur when we switch over to using the internal ITS
in SRM 4.0. Since SAP currently supports SRM 4.0 connected to ECC 6.0,
the fact that we are using the external ITS in SRM 4.0 should not be an
issue since it is still supported.
Does anyone know If there is a requirement for our SRM system to be on the internal ITS
while connecting to an ECC 6 system? Also, can anyone please let us know and/or provide any
published document that states this, I have not found anything that
states this requirement.
Regards,
-Paul

Hello there
I'm not quite sure what differences to HCM the SRM has but we had the same problem. Please check OSS Note 905135 and following. As far as I know the 6.20 external ITS was the last "external" version. Which means all scenarios connecting to a 2004s or higher system need to use other technologies or the internal ITS.
Lots of luck.
Harry

Error using the JNDI Attributes interface on LDAP

Similar Messages

Maybe you are looking for