Get A nonfatal JIT error querying a ldap server

I wrote a java program to query a ldap server based on last name. Basically my code does a search for any entry with sn equal to the passed argument. It works fine when it returns a small set of records, but when I try to query sn = * or even sn = l* (which should return a few hundred people) the code bombs with the following:
A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occured in :
'com/sun/jndi/ldap/Connection.readReadOnly (Lcom/sun/jndi/ldap/LdapRequest;)Lcom/sun/jndi/ldap/BerDecoder;': Interpreting method.
Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi
The above come out of stderr. Stadnard output will have 'current thread not owner' after the above error message.
I doubt I am the only person who is doing something like this. If anyone knows what is happening with the above message, please give me a hint.
thanks a bunch.

Not knowing what the underlying problem is, I decided to use the Netscape directory SDK instead of the jndi solution with Sun's ldap service provider. I was able to retrieve 2000 entries and it is actually a lot faster than the jndi method.
I hope this helps others who are trying to connect to a ldap server.

Similar Messages

Can't get IVI Power Meter error query to work properly.

I have been trying to use the IviPwrMeter Error-Query.vi to read possible errors coming from the Power Meter. However, I have found that no errors can be detected using this vi. This is because the returned value 'status' is wired over to the 'error code' input of 'IviPwrMeter Error Converter.vi' and the status value will always be equal to VI_SUCCESS as the attached code signifies.
All of this code was generated by either LabWindows/CVI and/or LabView.
If I wire the error code output of 'IviPwrMeter_error_query' function to the error code input of 'IviPwrMeter IVI error converter.vi', the errors on the Power Meter is at least detected.
Am I doing something wrong here or are there other work arounds?
Source listing of driver call:
ViStatus _VI_FUNC age4418b_error_query (ViSession vi, ViInt32 *errCode,
                                        ViChar errMessage[])
    ViStatus    error = VI_SUCCESS;
    checkErr( Ivi_LockSession (vi, VI_NULL));
    if (errCode == VI_NULL)
        viCheckParm( IVI_ERROR_INVALID_PARAMETER, 2, "Null address for Error Code");
    if (errMessage == VI_NULL)
        viCheckParm( IVI_ERROR_INVALID_PARAMETER, 3, "Null address for Error Message");
if (!Ivi_Simulating(vi))                /* call only when locked */
     ViSession   io = Ivi_IOSession(vi); /* call only when locked */
     checkErr( Ivi_SetNeedToCheckStatus (vi, VI_TRUE));
     viCheckErr( viPrintf(io, "YST:ERR?"));
  viCheckErr( viScanf (io, "%ld,\"%256[^\"]", errCode, errMessage));
else
         /* Simulate Error Query */
     *errCode = 0;
     strcpy (errMessage, "No error.");
Error:
    Ivi_UnlockSession(vi, VI_NULL);
    return error;

Dennis,
I get the same results as you if I don't have a power meter connected. However, this doesn't supprise me because the session handle is probably checked at a higher level.
The calling hiearchy is as follows (I think, because I don't have all of the code) IviPwrMeter Error Query.vi -> IviPwrMeter_error_query (IviPwrMeter.dll) ->age4418b_error_query (age4418b.dll). I would guess that the session is validated in the second layer and not the bottom layer where the actual instrument error query is happening.
Something you may try. If you have any instrument, write a simple program to get a valid handle then call the error query using the error cluster to link them together. Set a breakpoint before the error query, run the program, use MAX to send an invalid command and create an error. Then resume your original program and see if an error is reported in the error cluster after executing the IVI error query.
Bob

Just-In-Time (JIT) Error in Windows 2003 Server Environment

Hi,
I am using the EBS R12.1.1 environment for learning purpose. I am running EBS R12.1.1 on Windows 2003 Server environment on my personal laptop.
I am getting JIT error on FNDLIBR.exe file. This error opens a window and asks me to choose debuggers and by default the MS Visual Studio 2005 debugger is available. This error raises every some time randomly like some time it raises in every 1 min, sometime it raises in every 2 to 5 mins etc. How can I overcome on this error?
Thanks & Regards,
Waqas Hassan

Thanks Mr. Hussein,
I think in learning process i do not need the NLS Patch. So I had a fresh copy of EBS R12.1.1 in VMWare on Windows 2003 Server and now, I am using it without NLS Patch.
Actually I am working on HRMS Setup, in fresh EBS environment there is need to install its legislative data, so I installed it and apply the hrglobal.drv patch according to this document "*Instructions for Running DataInstall/hrglobal.drv on R12 [ID 414434.1]*" but I just skipped only 5th and 6th Step because its about NLS Patch.
I run the 7th step to "*Generate Payroll Dynamic Database Item Translations*" its completed successfully but when I run the 8th Step about "*Bulk Compile Formulas*" its giving error and the error is given below:
FastFormula: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
BULKCOMPILE module: Bulk Compile Formulas
Current system time is 15-APR-2012 00:51:16
Starting verify: 109 formula instances to process.
Accrual:PTO_HD_ANNIVERSARY_BALANCE:0001/01/01 verified OK
Accrual:PTO_PAYROLL_BALANCE_CALCULATION:0001/01/01 verified OK
Accrual:PTO_PAYROLL_CALCULATION:0001/01/01 verified OK
Accrual:PTO_ROLLING_ACCRUAL:0001/01/01 verified OK
Accrual:PTO_SIMPLE_BALANCE_MULTIPLIER:0001/01/01 verified OK
Accrual:PTO_SIMPLE_MULTIPLIER:0001/01/01 verified OK
Accrual Carryover:PTO_HD_ANNIVERSARY_CARRYOVER:0001/01/01 verified OK
Accrual Carryover:PTO_PAYROLL_CARRYOVER:0001/01/01 verified OK
Accrual Carryover:PTO_ROLLING_CARRYOVER:0001/01/01 verified OK
Accrual Carryover:PTO_SIMPLE_CARRYOVER:0001/01/01 verified OK
Accrual Ineligibility:PTO_INELIGIBILITY_CALCULATION:0001/01/01 verified OK
Accrual Subformula:PTO_HD_ANNIVERSARY_PERIOD_ACCRUAL:0001/01/01 verified OK
Accrual Subformula:PTO_PAYROLL_PERIOD_ACCRUAL:0001/01/01 verified OK
Accrual Subformula:PTO_ROLLING_PERIOD_ACCRUAL:0001/01/01 verified OK
Accrual Subformula:PTO_SIMPLE_PERIOD_ACCRUAL:0001/01/01 verified OK
Appraisal Competency Line Scoring:PERF_X_PROF:0001/01/01 verified OK
Appraisal Competency Line Scoring:PERF_X_WEIGHTING:0001/01/01 verified OK
Appraisal Competency Line Scoring:PROF_X_WEIGHTING:0001/01/01 verified OK
Appraisal Objective Line Scoring:PERF:0001/01/01 verified OK
Appraisal Objective Line Scoring:PERF_X_WEIGHTING:0001/01/01 verified OK
Appraisal Total Scoring:AVG_COMP_AND_OBJ:0001/01/01 verified OK
Appraisal Total Scoring:SUM_COMP_AND_OBJ:0001/01/01 verified OK
CAGR:HR_CAGR_PYS_TEMPLATE:1951/01/01 verified OK
CAGR:HR_CAGR_TEMPLATE:1951/01/01 verified OK
Element Skip:SA_ONCE_EACH_PERIOD:0001/01/01 verified OK
APP-FF-34004: Element Skip:SA_ONCE_EACH_YEAR:0001/01/01 FAILED
APP-FF-33005: The local variable GOSI_REFERENCE_EARNINGS_ASG_YTD was used before being initialized
Cause: The variable named in the error message is being used before any value has been assigned to it, so it has no meaningful value.
Action: Please ensure variables have been assigned to before using them.
Element Skip:PTO_ORACLE_SKIP_RULE:0001/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_CONSOL_SET:1900/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_ELEMENT_NAME:1900/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_ELEMENT_SET:1900/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_EXTRACT_ENDDT:1900/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_EXTRACT_NAME:1900/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_EXTRACT_STARTDT:1900/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_LOCATION:1900/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_ORG_NAME:1900/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_PAYROLL_NAME:1900/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_PERSON_TYPE:1900/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_REPORT_OPTION:1900/01/01 verified OK
Extract Header/Trailer Data Element:PAY_GLOBAL_PEXT_SELECTION_CRITERIA:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_CHK_ASG_ACTIONS:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_FID_EMP_STATUS:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_ACTUAL_SALARY:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_ANN_COMP:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_BAL_VAL:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_DDF_DF_VALUE:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_ELE_ETRY_VALUE:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_EMP_CATEGORY:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_EMP_STATUS:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_NORMAL_HOURS:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_PAY_VALUE:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_PLAN_CONTR_VALUE:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_SIT_VALUE:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_GET_TERMI_DATE:1900/01/01 verified OK
Extract Person Data Element:PAY_GLOBAL_PEXT_PAYROLL_DATE:1900/01/01 verified OK
Extract Person Inclusion:PAY_GLOBAL_PEXT_CRITERIA_FP:1900/01/01 verified OK
Extract Post Process:PAY_GLOBAL_PEXT_POST_PROCESS:1900/01/01 verified OK
Net to Gross:DEFAULT_GROSSUP:0001/01/01 verified OK
OTL Approvals:HXC_OVERRIDE_APPROVER_WF_PERSON:0001/01/01 verified OK
OTL Time Entry Rules:HXC_ASG_STD_HRS_COMPARISON:0001/01/01 verified OK
OTL Time Entry Rules:HXC_APPROVAL_ASG_STATUS:0001/01/01 verified OK
OTL Time Entry Rules:HXC_APPROVAL_MAXIMUM:0001/01/01 verified OK
OTL Time Entry Rules:HXC_CLA_CHANGE_FORMULA:1901/01/01 verified OK
OTL Time Entry Rules:HXC_CLA_LATE_FORMULA:1901/01/01 verified OK
OTL Time Entry Rules:HXC_ELP:0001/01/01 verified OK
OTL Time Entry Rules:HXC_FIELD_COMBO_EXCLUSIVE:0001/01/01 verified OK
OTL Time Entry Rules:HXC_FIELD_COMBO_INCLUSIVE:0001/01/01 verified OK
OTL Time Entry Rules:HXC_PERIOD_MAXIMUM:0001/01/01 verified OK
OTL Time Entry Rules:HXC_PTO_ACCRUAL_COMPARISON:0001/01/01 verified OK
OTL Time Entry Rules:HXC_TIME_CATEGORY_COMPARISON:0001/01/01 verified OK
Oracle Payroll:NI_VALIDATION:0001/01/01 verified OK
APP-FF-34004: Oracle Payroll:SA_GOSI_CALCULATION:0001/01/01 FAILED
APP-FF-33005: The local variable GOSI_REFERENCE_EARNINGS_ASG_YTD was used before being initialized
Cause: The variable named in the error message is being used before any value has been assigned to it, so it has no meaningful value.
Action: Please ensure variables have been assigned to before using them.
APP-FF-34004: Oracle Payroll:SA_GOSI_CALCULATION:2006/01/01 FAILED
APP-FF-33005: The local variable GOSI_REFERENCE_EARNINGS_ASG_YTD was used before being initialized
Cause: The variable named in the error message is being used before any value has been assigned to it, so it has no meaningful value.
Action: Please ensure variables have been assigned to before using them.
Oracle Payroll:US_EVS:0001/01/01 verified OK
Oracle Payroll:CALC_GROSSUP_PAY_VALUE:0001/01/01 verified OK
Oracle Payroll:HR_CWK_MOVE_TYPE_TEMPLATE:0001/01/01 verified OK
Oracle Payroll:HR_MOVE_TYPE_TEMPLATE:0001/01/01 verified OK
Oracle Payroll:HR_PERSON_TYPE_TEMPLATE:0001/01/01 verified OK
Oracle Payroll:PTO_TAGGING_FORMULA:0001/01/01 verified OK
Payment:SA_EFT_BODY:0001/01/01 verified OK
APP-FF-34004: Payment:SA_EFT_BODY_CUSTOMER:0001/01/01 FAILED
APP-FF-33005: The local variable ORG_SA_BANK_NAME was used before being initialized
Cause: The variable named in the error message is being used before any value has been assigned to it, so it has no meaningful value.
Action: Please ensure variables have been assigned to before using them.
Payment:SA_EFT_FOOTER:0001/01/01 verified OK
APP-FF-34004: Payment:SA_EFT_FOOTER_CUSTOMER:0001/01/01 FAILED
APP-FF-33005: The local variable ORG_SA_ACCOUNT_NUMBER was used before being initialized
Cause: The variable named in the error message is being used before any value has been assigned to it, so it has no meaningful value.
Action: Please ensure variables have been assigned to before using them.
Payment:SA_EFT_HEADER:0001/01/01 verified OK
APP-FF-34004: Payment:SA_EFT_HEADER_CUSTOMER:0001/01/01 FAILED
APP-FF-33005: The local variable ORG_SA_ACCOUNT_NUMBER was used before being initialized
Cause: The variable named in the error message is being used before any value has been assigned to it, so it has no meaningful value.
Action: Please ensure variables have been assigned to before using them.
Payroll Run Proration:SA_USER_PRORATION_FORMULA:0001/01/01 verified OK
People Management Message:US_EMPLOYEE_TRANSFER:0001/01/01 verified OK
People Management Message:US_NEW_STARTER:0001/01/01 verified OK
People Management Message:US_PAYROLL_INT_HIRE:0001/01/01 verified OK
People Management Message:US_PAYROLL_NEW_STARTER:0001/01/01 verified OK
People Management Message:US_RELOCATION_NOTIFICATION:0001/01/01 verified OK
People Management Message:QH_ASSIGNMENT_NAME:0001/01/01 verified OK
Promotion:PROMOTION_TEMPLATE:0001/01/01 verified OK
APP-FF-34004: QuickPaint:US_EMPLOYEE_TRANSFER:1000/01/01 FAILED
APP-FF-33005: The local variable SCL_ASG_US_TAX_UNIT was used before being initialized
Cause: The variable named in the error message is being used before any value has been assigned to it, so it has no meaningful value.
Action: Please ensure variables have been assigned to before using them.
APP-FF-34004: QuickPaint:US_NEW_STARTER:1000/01/01 FAILED
APP-FF-33005: The local variable SCL_ASG_US_TAX_UNIT was used before being initialized
Cause: The variable named in the error message is being used before any value has been assigned to it, so it has no meaningful value.
Action: Please ensure variables have been assigned to before using them.
APP-FF-34004: QuickPaint:US_PAYROLL_INT_HIRE:1000/01/01 FAILED
APP-FF-33005: The local variable SCL_ASG_US_TAX_UNIT was used before being initialized
Cause: The variable named in the error message is being used before any value has been assigned to it, so it has no meaningful value.
Action: Please ensure variables have been assigned to before using them.
APP-FF-34004: QuickPaint:US_PAYROLL_NEW_STARTER:1000/01/01 FAILED
APP-FF-33005: The local variable SCL_ASG_US_TAX_UNIT was used before being initialized
Cause: The variable named in the error message is being used before any value has been assigned to it, so it has no meaningful value.
Action: Please ensure variables have been assigned to before using them.
APP-FF-34004: QuickPaint:US_RELOCATION_NOTIFICATION:1000/01/01 FAILED
APP-FF-33005: The local variable SCL_ASG_US_TAX_UNIT was used before being initialized
Cause: The variable named in the error message is being used before any value has been assigned to it, so it has no meaningful value.
Action: Please ensure variables have been assigned to before using them.
QuickPaint:EXAMPLE_BIS_OT_BAND1:0001/01/01 verified OK
QuickPaint:QH_ASSIGNMENT_NAME:0001/01/01 verified OK
QuickPaint:TEMPLATE_ABSENCE_DURATION:0001/01/01 verified OK
QuickPaint:TEMPLATE_BIS_DAYS_TO_HOURS:0001/01/01 verified OK
QuickPaint:TEMPLATE_BIS_TRAINING_CONVERT_DURATION:0001/01/01 verified OK
QuickPaint:TEMPLATE_FTE:0001/01/01 verified OK
QuickPaint:TEMPLATE_HEAD:0001/01/01 verified OK
Template Information:PER_QH_JOB_EI:0001/01/01 verified OK
Template Information:PER_QH_ORG_EI:0001/01/01 verified OK
Template Information:PER_QH_POSITION_EI:0001/01/01 verified OK
Template Information:PER_QH_SUPERVISOR_CONTACT_EI:0001/01/01 verified OK
User Table Validation:CHECK_RATE_TYPE:0001/01/01 verified OK
The formula wrapper package was created successfully.
Executing request completion options...
Finished executing request completion options.
Concurrent program returned no reason for failure.
Exceptions posted by this request:
Concurrent Request for "Bulk Compile Formulas" has completed with error.
Concurrent request completed
Current system time is 15-APR-2012 00:51:23
Please help me out.
Thanks & Best Regards,
Waqas Hassan

Trying to sync my macs but getting this... error connecting to the server

trying to sync my macs but get this .....error connecting to the server,check server name or ip address ?????

Same problem . . . any resolutions out there?

Getting iCal 3 to work with an LDAP server

I've managed to set up Directory Utility with a third-party LDAP server (part of Communigate Pro) so that Directory will look up people.
However I expected that once I did this, iCal would consult the LDAP server to do autocompletion when adding attendees to events. It doesn't.
I thought maybe I could use Address Book's Directories Group to facilitate adding attendees. Both the LDAP server configured through Mail and the LDAP Directory Service configured through Directory Utility are visible here--but even though I can look people up, I can't drag any of the resulting names into the Attendees list in iCal.
It seems I first have to drag them into a local Group; only then can I drag them into Attendee lists in iCal.
Finally, iCal has a feature called the Address Panel which I thought might make use of an LDAP server configured through Directory Utility, but it hasn't worked for me. The Panel says "Open Directory Lookup" near the top of the window, which suggests it might not be intended to function with any old LDAP implementation.
Any suggestions?
By the way, I have the LDAP server's entry in Directory Utility as RFC 2307 with an empty searchbase for all mappings. However I haven't modified any of the mappings themselves.
Thanks.

iCal 3 looks for certain specific LDAP attributes which are (somewhat) unique to Open Directory.
Some information on mimicking Open Directory can be found at http://wiki.expertmx.com/doku.php?id=applecalendarserver

Nonfatal JIT error

We are getting then following error, when running WLS 5.1 with SP4, on
NT 4.0 using the JRE that comes with WLS
A nonfatal internal JIT (3.10.107(x)) error 'Structured
Exception(c0000005)' has occurred in :
'weblogic/jndi/internal/BuiltinTransportableObjectFactory.getObjectInstance
(Ljava/lang/Object;Ljavax/naming/Name;Ljav
ax/naming/Context;Ljava/util/Hashtable;)Ljava/lang/Object;':
Interpreting method.
Please report this error in detail to
http://java.sun.com/cgi-bin/bugreport.cgi
The server terminates after this error occurs.
We have tried to use JDK1.3 instead - and have not seen the error on
this JDK
/Peter Reetz - Nykredit

Oh well, I was afraid you were going to say that.
The only advice I have recieved so far from weblogic support is to not
use the JIT. This is pretty bad because of the serious degradation in
performance without the JIT. I know that weblogic would like us to move
to 5.1, but we have a large number of ejbs and can't just re-target to
the latest platform.
Any other suggestions?
Carles
Michael Girdley wrote:
>
JDK 1.3 will not be supported for version 4.5.x.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Carles Pi-Sunyer" <[email protected]> wrote in message
news:[email protected]..
I would like to use jdk1.3, particularly with hotspot, but it is not on
the supported list for weblogic 4.5.1. Do you know if the list will be
updated in include jdk1.3 w/ hotspot for 4.5.1? Previously, when this
question was asked, the answer was no.
We are currently running the latest version of jdk1.2.2.
Thanks,
Carles
Michael Girdley wrote:
I suggest updating to either the latest version of JDK 1.2.2 Windows NT
or
JDK 1.3.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Carles Pi-Sunyer" <[email protected]> wrote in message
news:[email protected]..
We are getting the following error (in an apparently random way):
A nonfatal internal JIT (3.10.107(x)) error 'Structured
Exception(c0000005)' has
occurred in :
Unfortunetely, even though the error thinks that it is nonfatal, it is
killing the server.
We are running WL 4.5.1 sp8 with NT 4.0 sp4, Sun jdk1.2.2.
Has anyone else seen this error?
Any suggestions on how to prevent it?
Thanks,
Carles

Since upgrading to FF5, i get the following xml error on local development server (IIS 7 Windows 7): XML Parsing Error: no element found, Line Number 1, Column 1. The pages display fine when uploaded to hosting server. How do i resolve it

All aspx pages running locally via IIS or Visual studio inbuilt server can not be displayed in FF5. This problem has only occured since upgrading to FF5. The same sites/code worked fine with the previous version of FF.
When uploaded onto a hosting server the pages display fine. Pages all display ok on local IIS on IE, chrome, opera etc.
I do go through a proxy server, but so do the other browsers.
All this means i can't develop locally on FF. Help please!

Maybe your application doesn't support "Send NTLMv2 response only. Refuse LM & NTLM".
https://support.software.dell.com/zh-cn/foglight/kb/133971

How to query LDAP server and get DB Service names?

Hi, before making a connection to an Oracle database, if i want to get list of Databases available,
i could use OracleClientFactory (and CreateDataSourceEnumerator and GetDataSources) to get list of tnsnames from the local tnsnames.ora file
Now, if i instead want to query the LDAP server with a given context and get the DB Service list,
how can i do that using ODP.NET?
I am using Visual Studio C# 2010 and ODP.NET 11.2
Thanks,
-srinivas yelamanchili

The oracle client has an ldap.ora file, how can I use ODP.NET to read the ldap.ora file and get list of oracle instances available?
Thanks,
-sri

"GPIB error Query Interrupted" flashes on HP54542A

I've written a display and control program in Delphi 7 for the HP54542A. The program uses NI commands and the GPIB-32.dll library, per NI's recommendation. The program appears to work properly, but I frequently get the message "GPIB error-Query Interrupted" flashing on the scope screen. I've tried putting delays in the software after read and write commands, but that seems to have no effect. Any suggestions? The version of the GPIB-32.dll that I have is dated 1999. I'm using a fairly new NI PCMCIA card in a new Dell laptop.

tfowler,
Perhaps someone in the community has some experience with the HP54542A. We do have a newer GPIB driver which has a newer GPIB-32.dll that you could try:
NI-488.2 Download
We also have CVI and LabVIEW instrument drivers for this instrument that you could try out (since you are using Delphi you could at least check out what the drivers are doing and get some ideas):
54542A Driver Downloads
Craig H.

After creating a contained database, getting a login failure error while trying to connect to it.

After creating a contained database and a user with passowrd under the same database, I tried connecting to the contained database. I entered the server name, login credentials and went to the connection properties tab to select the contained database using
<browse server> option under "connect to database". Here I get the login failure error.
TITLE: Browse Server for Database
Failed to connect to server <servername>\<login>. (Microsoft.SqlServer.ConnectionInfo)
But when I manually enter the Database name instead of selecting from the <browse server> option the connection gets through.
Is this a Bug ? Has anyone else faced this error?

Hello,
Is this a Bug ? Has anyone else faced this error?
It's not a bug, it's working as intended. Contained users don't have instance level permissions and cannot "login" to the instance (which is what the "browse" button is attempting). In order for it to work, the database name must be in the connection string
(which with the browse button, it will not be).
Welcome to contained users, they aren't for everyone.
Sean Gallardy | Blog | Microsoft Certified Master

Network error since moving Essbase server into new VLAN

We just moved a Solaris zone containing an Essbase server into another VLAN and now I am seeing strange problems with network timeouts. When EAS runs "query database" commands in MAXL (when you click on a database, for example), it can hang for ten minutes and then timeout. If I run this locally on the server via essmsh:
MAXL> query database <Db> get estimated size;
I get, after ten minutes:
ERROR - 1056213 - message from server [Network error [145]: Unable to connect to [chr7z037:1423]. The client timed out waiting to connect to Analytic Services Agent using TCP/IP. Check your network connections. Also make sure that server and port values are correct].
THe server isn't down and I can connect to it via EAS and HSS.
I am not sure what service is reporting this error - must be APS or HSS (which run on a seperate windows box)?
Also EAS data previews are painfully slow and/or timeout with the same network error as above.
The essbase server is in HSS mode.

Hi Philip,
As CL said ,even I had faced the similar issue. In our case , it was the concept of DMZ ( they were in 2 different DMZ's ) and not able to communicate and gave the error ( which you mentioned in your post).
Try to open up the ports ( Try to telnet also to check)
Sandeep Reddy Enti
HCC
http://hyperionconsultancy.com/

The LDAP server is unavailable after installing KB2868725

After installing the KB2868725 Windows Update, a strange LDAPs connection problem occur.
Context : we have a C# web site (.NET 4.0) that perform an LDAPs Bind operation over LDAPs. The web server is not on the same domain (bind operations are perform again multiple LDAPs Server), and the code work like a charm more than a year.
So after installing the KB2868725 Windows Update we get a “System.DirectoryServices.Protocols.LdapException: The LDAP server is unavailable.” exception from the same application. When we uninstall the update, the error stop.
The problem is present ONLY over a SECURE connection.
We have multiple web server in production and every server where the KB2868725 Windows Update is not installed are working perfectly.
We build a test application with this simple code, work fine on “non-KB2868725 updated server”:
void BindLDAP()
LdapDirectoryIdentifier ldi = new LdapDirectoryIdentifier("example.com", 636, true, false);
LdapConnection ldapCnn = new LdapConnection(ldi, new NetworkCredential("myUsername", "myPassword"), AuthType.Basic);
ldapCnn.SessionOptions.VerifyServerCertificate = new VerifyServerCertificateCallback(Validate);
ldapCnn.Bind();
private static bool Validate(LdapConnection connection, X509Certificate certificate) { return true; }
Stack trace:
System.DirectoryServices.Protocols.LdapException: The LDAP server is unavailable.
at System.DirectoryServices.Protocols.LdapConnection.Connect()
at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential)
Server: Windows Server 2008 R2 Standard, Service Pack 1 (64-bit)
We tried to change every connections settings, change .NET version (2.0, 3.5 and 4.0), build the test application directly on the server and nothing work.
If we use others LDAP tool (like http://technet.microsoft.com/en-us/sysinternals/bb963907.aspx) the problem also occur : “The server is not operational.”
Moreover, if we installed these updates the problem also occur: KB2574819, KB2830477, KB2871997, KB2592687.
We can’t install any Windows Updates, that’s a problem. We would like to find a solution, please help us ;-)

Hi,
The server is configure to get the Windows Update from a WSUS server. Those updates are downloaded from Microsoft.
I follow these steps:
1. Uninstall Windows Update : KB2574819, KB2830477 (KB2857650) and KB2913751;
2. Perform a LDAP connection test : work perfectly;
3. Install Update KB2574819;
4. Perform a LDAP connection test : not working (The LDAP server is unavailable.);
5. Install Update KB2830477 (KB2857650 is include in KB2830477 update);
6. Perform a LDAP connection test : not working (The LDAP server is unavailable.);
7. Install Update KB2913751;
8. Perform a LDAP connection test : not working (The LDAP server is unavailable.);
The problem here is we can’t install KB2574819, KB2830477 (KB2857650) and KB2913751 on our productions servers because of the connections problems (install process work fine, is the effects of these Windows Updates).
Philippe Bernier

Error communicating with AdobeID server - DAY 3

So, I'm trying to activate the Digital Editions of Adobe on my MacBook, but I keep getting this darned message:Error communicating with AdobeID server. Please try again later.
What in the world is happening? I've been trying to get this to work for nearly 3 days. My classes will begin soon, and I'm REQUIRED to have this Adobe Digital Editions in order to download my books. WTH?! Can someone please help me get around this problem please?
Thank,
Monique

I'm getting the same problem. I'm in the UK
My error message is: E_AUTH_DATABASE_CONSISTENCY http://adeactivate.adobe.com/adept/SignInDirect AdobeID
(I have removed my ID)

Server 2012 errors for timeout -- LDAP error number: 55 -- LDAP error string: Timeout Failed to get server error string from LDAP connection

Hello, currently getting below error msg's utilizing software thru which LDAP is queried for discovering AD objects/path and resource enumeration and tracking.
Have ensured firewalls and port (389 ) relational to LDAP are not closed, thus causing hanging.
I see there was a write up on Svr 2003 ( https://support.microsoft.com/en-us/kb/315071 ) not sure if this is applicable, of if the "Ntdsutil.exe" arcitecture has changed much from Svr 03. Please advise.
-----------error msg ----------------
-- LDAP error number: 55
-- LDAP error string: Timeout Failed to get server error string from LDAP connection

The link you shared is still applicable. You can adjust your LDAP policy depending on your software requirements.
I would also recommend that you in touch with your software vendor to get more details about the software requirements.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Getting HTTP 500 Error When Trying To Authenticate Against LDAP Server (Active Directory)

Hello,
I am currently facing an issue when I try and use LDAP authentication in my Apex application as I am getting a HTTP 500 Internal Server Error message. For my authentication scheme I have used the pre-configured option of how to connect to an LDAP server and in my development environment this seems to be working fine but now I have deployed my application to our staging environment and I am getting the error. If I switch to the Application Express Authentication scheme then I don't get the error.
I've had a look at the log file on the server and I see I am getting this error:
[#|2015-03-31T16:19:11.254+0100|SEVERE|glassfish3.1.2|null|_ThreadID=21;_ThreadName=Thread-2;|JDBCException [kind=UNAVAILABLE]
    at oracle.dbtools.common.jdbc.JDBCException.wrap(JDBCException.java:99)
    at oracle.dbtools.common.config.db.DatabaseConfig.getConnection(DatabaseConfig.java:81)
    at oracle.dbtools.common.jdbc.ora.OraPrincipal.connection(OraPrincipal.java:69)
    at oracle.dbtools.apex.ModApexContext.getConnection(ModApexContext.java:372)
    at oracle.dbtools.apex.OWA.getStatement(OWA.java:536)
    at oracle.dbtools.apex.OWA.init(OWA.java:308)
    at oracle.dbtools.apex.ModApex.doPost(ModApex.java:138)
    at oracle.dbtools.apex.ModApex.service(ModApex.java:303)
    at oracle.dbtools.rt.web.HttpEndpointBase.modApex(HttpEndpointBase.java:347)
    at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:130)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
    at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
    at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
    at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
    at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
    at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
    at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
    at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
    at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
    at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
    at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
    at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
    at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
    at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
    at java.lang.Thread.run(Thread.java:662)
Caused by: java.sql.SQLException: Exception occurred while getting connection: oracle.ucp.UniversalConnectionPoolException: All connections in the Universal Connection Pool are in use
    at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:488)
    at oracle.ucp.util.UCPErrorHandler.throwSQLException(UCPErrorHandler.java:163)
    at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:928)
    at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:863)
    at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:855)
    at oracle.dbtools.common.config.db.DatabaseConfig.getConnection(DatabaseConfig.java:71)
    ... 33 more
Caused by: oracle.ucp.UniversalConnectionPoolException: All connections in the Universal Connection Pool are in use
    at oracle.ucp.util.UCPErrorHandler.newUniversalConnectionPoolException(UCPErrorHandler.java:368)
    at oracle.ucp.util.UCPErrorHandler.throwUniversalConnectionPoolException(UCPErrorHandler.java:49)
    at oracle.ucp.util.UCPErrorHandler.throwUniversalConnectionPoolException(UCPErrorHandler.java:80)
    at oracle.ucp.util.UCPErrorHandler.throwUniversalConnectionPoolException(UCPErrorHandler.java:131)
    at oracle.ucp.common.UniversalConnectionPoolImpl.borrowConnectionWithoutCountingRequests(UniversalConnectionPoolImpl.java:279)
    at oracle.ucp.common.UniversalConnectionPoolImpl.borrowConnection(UniversalConnectionPoolImpl.java:142)
    at oracle.ucp.jdbc.JDBCConnectionPool.borrowConnection(JDBCConnectionPool.java:157)
    at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:916)
    ... 36 more
So it seems that every time I try and use LDAP I hit this error. Also after awhile I have to re-start the Apex Listener for that domain. I have came across this thread: LDAP Authentication Question but I am not sure if the user got the problem solved or not.
Our infrastructure is as follows:
Database: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
Apex Listener: 2.0.3.221.10.13
GlassFish Server Open Source Edition 3.1.2.2 (build 5)
If anybody has any idea what is causing this that would be great.
Cheers,
Paul.

Hi Colm,
Thanks for getting back to me on this. I have downloaded and created a new ORDS server with 2.0.10 and while I don't get the error:
Exception occurred while getting connection: oracle.ucp.UniversalConnectionPoolException: All connections in the Universal Connection Pool are in use
I am now getting the following (I have turned on the logging)
No more data to read from socket java.sql.SQLRecoverableException: No more data to read from socket
at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1157) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:345)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:205)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1043)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1336)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3612)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3713)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4755)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1378)
at sun.reflect.GeneratedMethodAccessor1991.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.ucp.jdbc.proxy.StatementProxyFactory.invoke(StatementProxyFactory.java:230)
at oracle.ucp.jdbc.proxy.PreparedStatementProxyFactory.invoke(PreparedStatementProxyFactory.java:124)
at oracle.ucp.jdbc.proxy.CallableStatementProxyFactory.invoke(CallableStatementProxyFactory.java:101)
at $Proxy432.execute(Unknown Source) at oracle.dbtools.apex.OWA.execute(OWA.java:145)
at oracle.dbtools.apex.ModApex.handleRequest(ModApex.java:201)
at oracle.dbtools.apex.ModApex.doPost(ModApex.java:152)
at oracle.dbtools.apex.ModApex.service(ModApex.java:303)
at oracle.dbtools.rt.web.HttpEndpointBase.modApex(HttpEndpointBase.java:350)
at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:132)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:662)
I cant see anything glaring that is causing this. I have also increased the Minimum Connections to 30 and Maximum Connections to 100 with the administration part of Configuring ORDS via SQL Developer and it still has no desired effect.
The application works fine in our Development and Testing Environment but since I have ported it over to our production instance I am unable to log into it using my Active Directory credentials.
Cheers,
Paul.

Get A nonfatal JIT error querying a ldap server

Similar Messages

Maybe you are looking for