Digital graph causes exception in 8.5

Wanted to port some of my older LV panels to 8.5. I noticed that LabView would generate the following message when attempting to load one of my panels:
"Unhandled exception at 0x007513e0 in LabVIEW.exe: 0xC0000005: Access violation reading location 0x00000000"
The following is a snippit of code from the debugger:
007513B0 aaa
007513B1 adc         esi,dword ptr [ebp]
007513B4 bound       edx,qword ptr [ebx]
007513B6 jne         007513B8
007513B8 jnp         007513CD
007513BA jne         007513BC
007513BC xchg        eax,esp
007513BD adc         esi,dword ptr [ebp]
007513C0 xor         ecx,ecx
007513C2 xor         eax,eax
007513C4 test        edx,edx
007513C6 je          00751461
007513CC mov         eax,dword ptr [edx+4]
007513CF test        eax,eax
007513D1 push        esi
007513D2 mov         esi,dword ptr [edx]
007513D4 jle         0075145B
007513DA mov         edx,dword ptr [edx+8]
007513DD push        edi
007513DE mov         edi,eax
007513E0 mov         al,byte ptr [esi]    <<<<************************************************ Dies here
007513E2 cmp         al,2
007513E4 jne         007513EB
007513E6 or          ecx,4
007513E9 jmp         00751412
007513EB cmp         al,5
Panels like this one are mid sized, containing 10 - 20 sub VIs.  I stripped the panel down to try and find what exactly was causing LV 8.5 to crash. It turns out to be the digital graph.    I have attached a very simple panel that just contains the digital graph with nothing wired to it. If you try to run this in 8.5 I am guessing it will cause the problem. I tried it on a few PCs and get the same results.
Attachments:
main.vi ‏20 KB

Looking at my disks, version 6 appears to have been the first release to support digital graphs. I remember using as soon as it was available.
I tried several tests to see if I could further narrow down the problem for NI.
I am able to load the raw version 6.0 examples directly into 8.5.
1) I saved version 6.0 example "Simple Digital Waveform Graph" (SDWG) into a seperate VI.   It loads in both 6.1 and 8.5 with no exception.
2) Loaded main.vi example and copied it into the SDWG using 6.1.   Causes exception in 8.5
3) Connect the two graphs together in example so digital data is shown on both graphs, then saved the values as defaults. This version loads in 8.5 with no exception.
4) Start with main.vi, clear all the waveform data and save as defaults. Causes exception in 8.5
So, problem appears to have nothing to do with the cursors but does appear to be something with the data that had been stored into this graph when the defaults were saved.   It is really strange that clearing the data does not solve the problem.  Maybe this is a bigger problem than I originally thought.
Message Edited by lecroy on 10-09-2008 01:07 PM

Similar Messages

Digital graph cursor text not visible after build

We are using Labview 2011. Our application has been using digital graphs, with cursor text to define digital transition information since Labview 7.1. We have ported our application to Labview 2011 (and also 8.6.1 in which it works fine). While in the Labview development environment, the cursor text displays correctly. However when we build it, and run the .exe, we cannot see the cursor text. Our debugging efforts have been in vain - the xy locations are correct, but the cursor text is not visible.
We want to standardize our next version software on 2011 (even though the Labview 2011 version is 4x larger and 2.2 x slower than the Labview 7.1 version) because we need x64 support, and want to run in Linux as well. We have spent considerable time trying to find out what is wrong, but the debugging time is very long to go through the thought - build - run cycle.
Any help on why this might be would be gratefully appreciated.
- Bart Schroder, Cleverscope

Bart,
Can you please post a screenshot of your code as well as what's happening when you run your code?
Thanks,
Renee M
Applications Engineer
National Instruments
Regards,
Renée M
Applications Engineer
National Instruments

LORD - ERP Error ERP_LORD_GET_HEAD caused exception EXC_LORD_NOT_LOADED

Hello,
We have an CRM 7.0 system linked to EHP4 ECC.
We have implemented LEAN Order Interface.
Now while saving an ERP Sales Order from CRM Screen, it gives an errror saying "ERP Interfaced stopped / failed unexpectedly".
We have implemented enhancement spot ENH_SPOT_LORD for the same in ECC.
No Detailed error description is appearing, no application log is being written, neither in ECC nor in CRM.
Required Switches are also made activated in SWF5. Mapping Structures are also mapped in LORD_MAPPING and LORD_MAPPING_RO.
error message that I get is : ERP_LORD_GET_HEAD caused exception EXC_LORD_NOT_LOADED
Can some1 please help the BADI's and the mandatory methods that needs to be over written in Enhancement.
Or can some1 please tell where I am going wrong?
Thanks & Regards,
Narendra.

Hi Narendra,
Did you get a solution to this please?
Thks,
William

Finally cause Exception be forgotten

In trying out that finally cause previous return value be forgotten, as described on page 206 of "The Java Programming Language, 3rd edition", I wrote the following code, and tested it with jdk1.3.1. To my supprise, not only the return value was forgotten, the exception was appeared forgotten as well:
class PException extends Exception {
class Final {
    void f1(int i) {
     int result;
     System.out.println("f1("+i+")");
     try {
         result = f2(i);
         System.out.println("result = " + result);
     } catch(Exception e) {
         System.out.println("caught an Exception: " + e);
     try {
         result = f3(i);
         System.out.println("result = " + result);
     } catch(Exception e) {
         System.out.println("caught an Exception: " + e);
    int f2(int i) throws PException {
     try {
         if (i == 1) {
          System.out.println("generate exception");
          throw new PException();
         return 1;
     } finally {
         return 2;
    int f3(int i) throws PException {
     if (i == 1) {
         System.out.println("generate exception");
         throw new PException();
     return 1;
    public static void main(String[] args) {
     Final f = new Final();
     f.f1(1);
     f.f1(2);
     f.f1(1);
}Here is the result:
f1(1)
generate exception
result = 2
generate exception
caught an Exception: PException
f1(2)
result = 2
result = 1
f1(1)
generate exception
result = 2
generate exception
caught an Exception: PException

The concern here is that when the
try {
finally {
}pattern is used, without the catch block, purelly for flow control purpose, a return statement in the finally block could be problematic. If a finally block ends with a return statement, any exception that might be thrown in the try block would be ignored. The unhandled exception will not propergate, it simply lost in the midst. Because any code could throw unchecked exception, if the exception cannot afford to be lost, then one should be careful not to use return in the finally block. See the following test code:
class Finally {
    void test() {
     int result;
     System.out.println("test()");
     try {
         result = f1();
         System.out.println("result = " + result);
     } catch(Exception e) {
         System.out.println("Caught an Exception: " + e);
     try {
         result = f2();
         System.out.println("result = " + result);
     } catch(Exception e) {
         System.out.println("Caught an Exception: " + e);
     try {
         f3();
     } catch(Exception e) {
         System.out.println("Caught an Exception: " + e);
     try {
         f4();
     } catch(Exception e) {
         System.out.println("Caught an Exception: " + e);
    int f1() {
     System.out.println("f1()");
     int a = 0;
     int b = 0;
     try {
         a = 1/0; // this generate an unchecked exception
         b = 1;
     } finally {
         return b; // this return clobber the unchecked exception
    int f2() {
     System.out.println("f2()");
     int a = 0;
     int b = 0;
     a = 1/0; // this generate an unchecked exception
     b = 1;
     return b;
    void f3() {
     System.out.println("f3()");
     int a = 0;
     int b = 0;
     try {
         a = 1/0; // this generate an unchecked exception
         b = 1;
     } finally {
         return;   // this return clobber the unchecked exception
    void f4() {
     System.out.println("f4()");
     int a = 0;
     int b = 0;
     try {
         a = 1/0; // this generate an unchecked exception
         b = 1;
     } finally {
    public static void main(String[] args) {
     Finally f = new Finally();
     f.test();
/code]
Here are the results:test()
f1()
result = 0
f2()
Caught an Exception: java.lang.ArithmeticException: / by zero
f3()
f4()
Caught an Exception: java.lang.ArithmeticException: / by zero
We see that the devide by zero exception throw by f1() simply vanished, the unintended result 0, instead of the intended result 1, is returned. The test() method did not detect any abnormality in f1(), which is scary. To drive the point home, we try f3() and f4(), which has void return type. A simple return statement in f3() causes exception be lost. The stack frame seems intact, for otherwise, the test() method would exit abruptly before f2() even get a chance to be called.

Code causing exceptions at its own sweet time and place

import java.lang.*;
class newthread implements Runnable
     Thread t;
     int click=0;
     public volatile boolean running=true;
     newthread(int p)
          t=new Thread(this);
          t.setPriority(p);
     void start()
          t.start();
     public void run()
          while(running)
               click++;
     void start1()
          running=true;
     void stop()
          running=false;
class threadpriority2
     public static void main(String argv[])
          newthread ob1=new newthread(Thread.NORM_PRIORITY+2);
          newthread ob2=new newthread(Thread.NORM_PRIORITY-2);
          ob1.start();
          ob2.start();
          try
               Thread.sleep(5000);
          catch(Exception e)
               System.out.println("error detected:"+e);
          System.out.println("first one:"+ob1.click);
          System.out.println("first one:"+ob2.click);
          System.out.println("the priority of ob1 is:"+ob1.t.getPriority());
          System.out.println("the priority of ob2 is:"+ob2.t.getPriority());
          ob1.stop();
          ob2.stop();
          ob2.t.setPriority(Thread.NORM_PRIORITY+3);
          ob1.t.setPriority(Thread.NORM_PRIORITY-3);
          ob1.start1();
          ob2.start1();
          ob1.start();
          ob2.start();
          System.out.println("the priority of ob1 is:"+ob1.t.getPriority());
          System.out.println("the priority of ob2 is:"+ob2.t.getPriority());
          try
               Thread.sleep(5000);
          catch(Exception e)
               System.out.println("error detected:"+e);
          ob1.stop();
          ob2.stop();
          System.out.println("first one:"+ob1.click);
          System.out.println("first one:"+ob2.click);
errors during runtime:
Exception in thread "main" java.lang.IllegalThreadStateException
at java.lang.Thread.start(Unknown Source)
at newthread.start(threadpriority2.java:17)
at threadpriority2.main(threadpriority2.java:77)
when i run this code it causes exceptions at its own sweet locations when i run it separately.if once it displays some valid input it would then be followed by the exception
next time if i run it it will throw exception as soon as i run it at the very start without displaying even an iota of valid data like the previous case
is ti because the os is placing restrictions on the threads growth or something else.incase there is an error in my code it should atleast pop up the exceptions at one particular loaction in the output and not give different outputs

1) When you post code, please use and tags as described in Formatting tips on the message entry page. It makes it much easier to read.
wasnt aware of it.will keep it in mind i post nexttime.sorry for the inconvenience[\b]
3) You have multiple threads, right? The scheduling of which thread gets how much CPU time when is not subject to your control or prediction, so of course you'll see different timings in subsequent runnings of the same code.[b]actually the problem is not with multiple threads showing different times.whats happening is that exceptions are being thrown randomly at runtime.once when i ran it the exception was displayed at the very beginning of the output and the program snapped.next when i ran it first some output which was slated to be displayed got displayed and then the exceptions appeared in the output.now if the exceptions are thrown at the very beginning its obvious theres some problem at the background coz in the second case that never happened[\b]
i guess the formatting tips have taken effect[:D]

How to set causing Exception correctly?

I'm trying to nest exceptions. I've written a JUnit tests which does this, but while it works for simple nesting, it doesn't for my more complex Exception.
The following works:
        Exception e1 = new Exception("bla");
        Exception e2 = new Exception("whatever");
        e1.initCause(e2);
        Assert.assertEquals(e2, e1.getCause());
        Exception e3 = new Exception("yet another exception");
        e2.initCause(e3);
        Assert.assertEquals(e3, e1.getCause().getCause());
        Exception e4 = new Exception("yawn");
        e3.initCause(e4);
        Assert.assertEquals(e4, e1.getCause().getCause().getCause());The following doesn't:
     * The exception to use when a Hibernate transaction can't be ended.
     * The causes of this are created according to the given exceptions.
     * If <code>exception</code> exists:
     * <pre>
     * this
     * |
     * +--> exception
     *      |
     *      +--> hibernateException1
     *           |
     *           +--> hibernateException2 (if it exists)
     * </pre>
     * If <code>exception</code> is <code>null</code>:
     * <pre>
     * this
     * |
     * +--> hibernateException1
     *      |
     *      +--> hibernateException2 (if it exists)
     * </pre>
     * @param errorMessage The error message to show
     * @param exception The exception coming from the business process, which may be <code>null</code>
     * @param hibernateException1 The first Hibernate exception, which <strong>must exist</strong>
     * @param hibernateException2 The second Hibernate exception, which may be <code>null</code>
    public RecoverableSystemException(String errorMessage, Exception exception, HibernateException hibernateException1, HibernateException hibernateException2) {
        super(errorMessage, getCause(exception, hibernateException1, hibernateException2));
     * Gets the causing exception for {@link #RecoverableSystemException(String, Exception, HibernateException, HibernateException)}.
     * @param exception The exception coming from the business process, which may be <code>null</code>
     * @param hibernateException1 The first Hibernate exception, which <strong>must exist</strong>
     * @param hibernateException2 The second Hibernate exception, which may be <code>null</code>
     * @return The causing exception to use for the constructor
    private static Exception getCause(Exception exception, HibernateException hibernateException1, HibernateException hibernateException2) {
        if (hibernateException2 != null && hibernateException1 != null) {
            hibernateException1.initCause(hibernateException2);
        if (exception == null) {
            return hibernateException1;
        else {
            if (hibernateException1 != null) {
                exception.initCause(hibernateException1);
            return exception;
    }with the test looking like this:
        this.hibernateException1 = new HibernateException("h1");
        this.hibernateException2 = new HibernateException("h2");
        this.businessProcessException = new Exception("e1");
        RecoverableSystemException recoverableSystemException = new RecoverableSystemException("Test", null, this.hibernateException1, this.hibernateException2);
        Assert.assertEquals("Checking Hibernate exception 1", this.hibernateException1, recoverableSystemException.getCause());
        // THIS FAILS
        Assert.assertEquals("Checking Hibernate exception 2", this.hibernateException2, recoverableSystemException.getCause().getCause());Any help would be greatly appreciated!

initCause is rarely if ever used. It is possible that the way HibernateException is written does not support the use of this call. Have a look at its source to find out if it does.

Programmatically reset scale layout in digital graph

Hi all,
I'm using a digital graph to display digital signals.
During visualization, digital line name can change, then plot names can changes at run time.
My issue is due to the scale layout. When plot name is too long, plot name is overlayed to the graph. I can fix the problem using Reset scale layout, but it seems that Reset scale layout cannot be enabled programmatically.
Can you help me?
Thanks in advance

HI AC_85
I verified that Reset scale layout cannot be enabled programmatically. I think you know the plot name size before changing it, why don't you change the plot area position according to that? Maybe you can use property node "plot area" to programmatically set the position of the plot area.
Regards

Digital Signatures causing performance issue

I have created a form for a two-step process in which the first user will open, enter data, and submit the form for another user to approve. The problem is that during the approver phase, they will digitally sign the form (there are two digital signature fields for each section of the form, the approver is required to sign at least once in order to submit) and then submit, but the process seems to lag for about 20-30 seconds after they click submit.
I understand that the digital signatures may add to the size of the form overall, but is one or two signatures enough to cause a delay?
I have some javascript that I fire at the pre-submit event using AWS_Action to see what the user action is and if the user selects to submit then it will test to see if at least one signature field is signed and valid, if so then changes the signature field type to disabled (I have the signature fields become required type based on certain fields containg data) and submits the form. Is it possible that this script could cause such a delay after the submit? We aren't having any delays when the first user submits the form without digital signatures so I assume this is what is causing the problem.

I expect that the lag may be related to the script you are executing, rather that specifically by the digital signature itself. Are you able to test the form outside of the process to see if the lag remains? Could you change the submit button to a mailto: uri and see how long it takes for the "pre-submit" code to execute?
Regards
Steve

3D graphs cause LabVIEW 2010 to hang

I've been using LabVIEW 2010 for several weeks without any problems, but today I noticed that it doesn't work at all with anything related to the 3D picture control. Today was the first time that I tried doing anything with the 3D picture tool since installing LV 2010. Dropping any of the 3D Graphs on the front panel of a new VI causes LV2010 to hang. (By hang, I mean the VI window remains open but most UI things no longer work. Right-clicking on the window does not show a context menu. The main menu doesn't work. The X button does not close the VI front panel window nor the diagram window. Control-Q does not cause LabVIEW to quit. I have to kill the process in Task Manager.) It is the same story with just a plaing 3D picture indicator. Also, the solarsystem.vi example does not work either. The problems start as soon as I open the solarsystem.vi. After killing LV with Task Manager and relaunching LV10, I do not get the LV message about a previous crash.
The problem I am talking about is for LabVIEW 2010 with the f2 patch running in Win7. I am actually running it using VMware Fusion 3.1.3 on a 2009 Mac Pro running Lion. The Mac drivers are all updated. Since it is VMware Fusion machine, the video driver on the Windows side is part of the VMware Tools installation, which is up to date.
After searching the forums, I've tried all the other potential solutions I could find: 1) repaired LV2010 using add/remove programs and 2) tried using the compatibilty mode settings to turn off Aero.
Interestingly, 3D graphs work fine on the Mac side for LV2010 for Mac.
Even more insterestingly, 3D graphs work fine on Win7 for LV 8.5, which I still have installed. The fact that it works fine for LV 8.5 would seem to indicate that Lion did not introduce the problem and that the video driver is working fine.
Solved!
Go to Solution.

Yep, it's the same virtual machine. I set it up almost 2 years ago and it has been extremely stable. Both LabVIEW 8.5 and 2010 have been perfectly happy on it. It's a great way to do LabVIEW on Win7. I didn't notice any changes at all to the VM when I upgraded from Snow Leopard to Lion. I installed LabVIEW 2010 before upgrading to Lion, but I didn't have occasion to work with 3D controls before the upgrade to Lion so I don't know if it would have worked on Snow Leopard. The Mac versions of both LabVIEW 8.5 and LabVIEW 2010 also work great on the both Snow Leopard and Lion.
I happen to have an XP virtual machine too, but I haven't installed LabVIEW there. Let me know if that would be a worthwhile test.
You might check with Marc Page--unless he has already upgraded again I think he has a similar machine to mine.
The video card is the original stock:
NVIDIA GeForce GT 120:
Chipset Model: NVIDIA GeForce GT 120
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0640
Revision ID: 0x00a1
ROM Revision: 3386
Displays:
Cinema HD Display:
Resolution: 2560 x 1600
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Display Connector:
Status: No Display Connected

3D Graphs cause LV 2009 to CRASH

Hi all,
The placing of any of the new 3D graph controls on the front panel causes LV 2009 to Crash!
Please advise.
Battler.
Solved!
Go to Solution.

Hi battler.,
Unfortunately, that CAR was closed because it was not reproduceable. My recommendation at this time would be to do a LabVIEW Repair. To do this, go to Control Panel»Add or Remove Programs»National Instruments Software»Change/Remove»LabVIEW 2009»Repair. You may need your installation discs for this operation.
Thank you for choosing National Instruments.
Aaron Pena
National Instruments
Applications Engineer
http://www.ni.com/support

SO Wait causes exception occurred within external code called by call library node

when trying to run some old code that used to work ok, i now get this error message:
exception occurred within external code called by call library node
and the vi flagged as calling the exception is SO Wait. the error occurs with different soundcards. does anyone know what is causing this problem?

Hi Kreuters
It sounds as if you have a case of memory corruption. Which version of LabVIEW and DAQ (traditonal or DAQmx) are you running and also on which operating system?
would it be possible for you to post your VI on this thread? in some cases there are ways to fix the problem
Regards
YatinM
NIUK

Some Search Admin Pages Causing Exception 0x80131904

I have a SharePoint 2013 Farm with multiple servers, though most applications, services and sites currently run on the main Front-End system.
I have been tasked with re-building the Search Architecture, so as to distribute search components across some of the other servers. During this process, I have been reviewing & documenting the current Search configuration. However, I keep
running into an error on several of the Search Admin pages. I am able to navigate to the "Search Service Application: Search Administration" page, which shows that everything appears healthy under both 'System Status' and 'Search Application
Topology'
However, I receive a "Sorry, something went wrong" error message, with "Exception from HRESULT: 0x80131904" page when I click on any of the following links: "Crawl Log", "Crawl Health Reports", or "Content
Sources."
All the other Quick Links in the Search Administration page appear to work fine. But other than a "Correlation ID" that I do not know how to use, I can find no other information about this error or how to diagnose it further.
Anyone know how I can restore access to these Search Administration pages?
Thanks in advance,
Elohir

Hi Elohir,
You can use the Correlation ID to find more detailed information in logging file, the path of the file is : C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS .
Also , you can see the logging file through Event Viewer (typing Event Viewer in ‘run’).
0x80131904 is generally happened from SQL Server side. It may be caused by tempdb or Content Database is out of space.
In addition, here are some similar posts for you to take a look at:
http://social.technet.microsoft.com/Forums/en-US/62ed2e1f-1d2c-46b2-9a64-ba6b2d65dfdf/exception-from-hresult-0x80131904-in-sharepoint-2013-default-page?forum=sharepointadmin
http://social.technet.microsoft.com/Forums/en-US/66e600ef-4b40-48a3-bd66-3de8b10e01ba/exception-from-hresult-0x80131904-sharepoint-2010-central-admin?forum=sharepointadminprevious
http://vbthineshkumar.blogspot.in/2011/11/sql-express-database-full-error-in.html
http://johanolivier.blogspot.in/2011/04/resolve-sharepoint-errors-caused-by-sql.html
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

JEditorPane PageLoader thread causing exceptions, not on EDT

Hello,
I have a swing GUI that creates a JEditorPane component and loads up an HTML file using the setPage() method to finally display it. I'm occaisionally getting NullPointerExceptions and ArrayIndexOutOfBoundsExceptions when running the GUI. It is apparent that the JEditor pane spawns a page loading process to load up the HTML. When the loading completes, this page loading thread signals the swing JEditorPane component to update its display. Because the signalling is being done from the pageloader thread and not from the EDT it seems to be creating race conditions and therefore the exceptions.
An example of the typical stacktrace thrown is:
Exception in thread "Thread-6" java.lang.NullPointerException
at javax.swing.text.CompositeView.replace(CompositeView.java:200)
at javax.swing.text.CompositeView.loadChildren(CompositeView.java:97)
at javax.swing.text.FlowView$LogicalView.loadChildren(FlowView.java:684)
at javax.swing.text.CompositeView.setParent(CompositeView.java:122)
at javax.swing.text.FlowView.loadChildren(FlowView.java:122)
at javax.swing.text.CompositeView.setParent(CompositeView.java:122)
at javax.swing.text.FlowView.setParent(FlowView.java:272)
at javax.swing.text.html.ParagraphView.setParent(ParagraphView.java:58)
at javax.swing.text.CompositeView.replace(CompositeView.java:200)
at javax.swing.text.BoxView.replace(BoxView.java:164)
at javax.swing.text.CompositeView.loadChildren(CompositeView.java:97)
at javax.swing.text.CompositeView.setParent(CompositeView.java:122)
at javax.swing.text.html.BlockView.setParent(BlockView.java:55)
at javax.swing.text.CompositeView.replace(CompositeView.java:200)
at javax.swing.text.BoxView.replace(BoxView.java:164)
at javax.swing.text.html.TableView$RowView.replace(TableView.java:1457)
at javax.swing.text.CompositeView.loadChildren(CompositeView.java:97)
at javax.swing.text.CompositeView.setParent(CompositeView.java:122)
at javax.swing.text.CompositeView.replace(CompositeView.java:200)
at javax.swing.text.BoxView.replace(BoxView.java:164)
at javax.swing.text.html.TableView.replace(TableView.java:896)
at javax.swing.text.CompositeView.loadChildren(CompositeView.java:97)
at javax.swing.text.CompositeView.setParent(CompositeView.java:122)
at javax.swing.text.html.TableView.setParent(TableView.java:800)
at javax.swing.text.CompositeView.replace(CompositeView.java:200)
at javax.swing.text.BoxView.replace(BoxView.java:164)
at javax.swing.text.CompositeView.loadChildren(CompositeView.java:97)
at javax.swing.text.CompositeView.setParent(CompositeView.java:122)
at javax.swing.text.html.BlockView.setParent(BlockView.java:55)
at javax.swing.text.html.HTMLEditorKit$HTMLFactory$BodyBlockView.setParent(HTMLEditorKit.java:1277)
at javax.swing.text.CompositeView.replace(CompositeView.java:200)
at javax.swing.text.BoxView.replace(BoxView.java:164)
at javax.swing.text.View.updateChildren(View.java:1095)
at javax.swing.text.View.insertUpdate(View.java:679)
at javax.swing.plaf.basic.BasicTextUI$RootView.insertUpdate(BasicTextUI.java:1590)
at javax.swing.plaf.basic.BasicTextUI$UpdateHandler.insertUpdate(BasicTextUI.java:1849)
at javax.swing.text.AbstractDocument.fireInsertUpdate(AbstractDocument.java:185)
at javax.swing.text.DefaultStyledDocument.create(DefaultStyledDocument.java:145)
at javax.swing.text.html.HTMLDocument.create(HTMLDocument.java:281)
at javax.swing.text.html.HTMLDocument$HTMLReader.flushBuffer(HTMLDocument.java:3323)
at javax.swing.text.html.HTMLDocument$HTMLReader.flush(HTMLDocument.java:2127)
at javax.swing.text.html.HTMLEditorKit.read(HTMLEditorKit.java:231)
at javax.swing.JEditorPane.read(JEditorPane.java:557)
at javax.swing.JEditorPane.read(JEditorPane.java:585)
at javax.swing.JEditorPane$PageLoader.run(JEditorPane.java:648) As can be seen from the stack trace, the javax.swing.text.AbstractDocument.fireInsertUpdate(AbstractDocument.java:185) line is called from the PageLoader.run thread which attempts to manipulate the swing component.
I haven't prepared a small compact test case for this yet as it is a race condition and only occurs under certain timings. The GUI on my machine throws these exceptions on almost every second run but far less frequently on another test machine.
I'm using Java 6 u 13 b 3 in linux ubuntu Jaunty.
Is there a way to load the page synchronously or to correctly load the page without causing these exceptions?
Thanks,
Mark
Edited by: Mark_Silberbauer on Jun 9, 2009 11:30 AM

I would try to create a HTMLDocument instance and read content there by the kit you use. When the document's filling is finished just call editorPane.setDocument() in EDT.
Regards,
Stas

How to combine Digital Graphs

Hi,
how to combine or merge the 1D array of digital waveform with a simple digital waveform. As givien in the attached VI, I want to display the datalines graph & control lines graph in a single digital waveform graph.
Thanks in advance
Solved!
Go to Solution.
Attachments:
Combine Graph.vi ‏10 KB

Hi gurum,
Well, you can use 'Build Array' to merge the 2 1D arrays and connect the output to the Digital Waveform Graph as shown below:
Hope it helps
Warmest regards,
Lennard.C
Learning new things everyday...

SPDiagnosticsServiceBase.GetLocal causes exception during SPFeatureReceiver.FeatureInstalled

If a SharePoint farm solution is deployed using Sever Object Model or PowerShell calling the SPDiagnosticsServiceBase.GetLocal in the SPFeatureReceiver.FeatureInstalled code causes an exception:
The installation of features failed during deployment of the solution.
CAS_SP : Configsetting with key 'CAS.SharePoint.Common.TypeMappings' could not be set 'CAS.SharePoint.Common.ServiceLocation.ServiceLocationConfigData' with type 'CAS.SharePoint.Common.ServiceLocation.ServiceLocationConfigData'. The technical exception was: CAS.SharePoint.Common.Logging.LoggingException: One or more error occurred while writing messages into the log.\r\nThe error while writing to the EventLog was:An exception has occurred.
ExceptionType: 'SPDuplicateObjectException'
ExceptionMessage: 'An object of the type CAS.SharePoint.Common.Logging.DiagnosticsService named "" already exists under the parent Microsoft.SharePoint.Administration.SPFarm named "SharePoint_Config_c8ae0268-40ff-4bea-82f0-eddcd464e806". Rename your object or delete the existing object.'
StackTrace: ' at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Microsoft.SharePoint.Administration.ISPPersistedStoreProvider.PutObject(SPPersistedObject persistedObject, Boolean ensure)
at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()
at Microsoft.SharePoint.Administration.SPDiagnosticsServiceBase.Update()
at Microsoft.SharePoint.Administration.SPDiagnosticsServiceBase.GetLocalToFarm[T](SPFarm farm)
at Microsoft.SharePoint.Administration.SPDiagnosticsServiceBase.GetLocal[T]()
at CAS.SharePoint.Common.Logging.TraceLogger.Trace(String message, Int32 eventId, TraceSeverity severity, String category)
at CAS.SharePoint.Common.Logging.SharePointLogger.WriteToDeveloperTrace(String message, Int32 eventId,
The same solution deployed using Central Administration tool works fine. The code also works fine while executing it from command line application.
I have reproduced this problem on two SharePoint Servers and one Foundation instance.
It seems as a SharePoint bug, but is there any workaround you know? How to report it to the SharePoint developers team ?
Mariusz

The farms that you are doing this on, are they multiserver farms (multiple wfes), or have you repro'd on a single server farm? It almost seems as though some config cache is having a problem, or psconfig is clashing with itself (if it involves multiple
servers).

Digital graph causes exception in 8.5

Similar Messages

Maybe you are looking for