Weird Lightroom bug

This bug has existed for a number of Lightroom versions, starting from 1.4. After working with a lot of images and using the shortcut menu extensively (right-click menu), right-clicking will suddenly stop working, and so will many shortcut keys. For some of the shortcut keys, bizarre behavior occurs. For example, CTRL+Z will cause a particular preset to be applied, rather than performing an undo.
The only "fix" for this problem is to restart Lightroom. Any ideas on what's going on?

Lightroom RC3.5 is what brought me here. Wanted to see if the issue had been addressed. It's not mentioned but I guess I'll give it a try.
As far how to reproduce I think the original poster nailed it. Just work in LR for awhile and it starts to do exactly what was posted. Closing LR and restarting does fix it until it starts acting up again.

Similar Messages

Stacks weird visual bug

Hi,
I'm running Leopard 10.5.3 on a 1Ghz iMac G4 which came with a GeForce4 MX graphics card. I've been using stacks from the beginning (and loving it) but every time I use it, a weird visual bug is triggered; basically white semi-transparent rectangles appear along the edges. You can find a screenshot of this at http://picasaweb.google.com/luis.beca/StacksBug/photo#5206710255993309346. Any clues as to why this is happening or how to solve it?
I should point out that I have been stuck with this problem from the very beginning, not just the latest Leopard version 10.5.3. I have an Intel MacBook Pro where this is not an issue.
Many thanks in advance
Luís
PS - How can I submit this to Apple?

I think you can thank Apple for this. See this discussion.
Photoshop CC: MacOS 10.10 Yosemite: Graphics driver problem
Nancy O.

Weird subtitle bugs

I'm running into several weird subtitle bugs in Encore 2.0. My project is a 33 minute training video with 4 subtitle tracks - English, Chinese, Spanish and Russian. I know the project was initially created in 1.5, but I don't remember if the subtitles were imported before or after the conversion.
The first is that some of the subtitles that have been edited are showing the original version of the subtitle. In most cases, if I go back to the edited version in the timeline and add a space at the end, it seems to update to the new version of the subtitle.
The other issue is that in many cases, the subtitles are staying on the screen longer than they should be. In one instance, the subtitle stayed on the screen for about 15 seconds more than it should.
Any comments or suggestions?
This will be the last project for me in Encore - I just can't afford to spend multiple days working around Encore and its "features"
Thanks,
David

Experienced the same subtitling "bugs" you described.
Opened a ver. 1.5 project in ver. 2. Then once in ver. 2, I revised some text in several subtitle clips. The revisions were displayed o.k. during preview, but when I built a new DVD Volume from ver.2, and tested the playback in WinDVD software player, it was the "old" subtitles that were displayed!!!!!
Apparently, the Encore 2 programmers overlooked a crucial subroutine in their coding. If i'm not mistaken, when you type-in or edit a subtitle clip, the program module that runs is something like a wordprocessor that works with the native fonts and formatting; the text in a subtitle clip is later rendered by Encore as a masked bitmap file overlaid onto the main video when you turn on the subtitles when you build the DVD volume (it's like in Photoshop where a text layer will be editable until you rasterize it, in which case the "text" becomes a bitmap image which you can no longer text-edit). I guessed that the edited subtitle clips were not being re-rendered by Encore. So, to work around this, I created/added new subtitle clips next to the "old" one and re-typed the text with the incorporated revisions, then deleted the "old" clip and repositioned the recently added/created clip. Afterwards, the subtitles with the corrected text displayed properly when I played back a re-built DVD volume.
But although this "work-around" works, it would simply be too bothersome if you had to revise hundreds of subtitle clips!!!!! A situation I later found myself confronted with!
What I did, then, was I duplicated the original subtitle track (which Encore failed to re-render properly) on which I had done the revisions; then, once the duplicate subtitle track had been pasted by Encore on the timeline, I deleted the original track and re-built a new DVD Volume. This time, all the revised subtitle clips were displayed correctly when I played back the volume in the software DVD player.
Nevertheless, I hope Adobe becomes aware of this bug and implement the appropriate fixes.

Lightroom Bug: with GoPro Hero4 Silver Lens Profile, crop settings do not sync properly in Lightroom 5.7.1 when Constrain To Warp is checked

I was having a bit of difficultly in getting crop settings to properly sync in Lightroom 5.7.1 (running on OS X 10.10.1) when Constrain to Warp was checked. This appears to be a bug in the latest version(s) of Lightroom that include(s) the GoPro Hero4 Silver Lens Profile settings. I'm working with a lot of files from a GoPro Hero4 Silver camera shot in the time-lapse / interval timer mode. All of them are horizontal with the same resolution (and dimensions). I've tried various sequences to get this to work in terms of using Auto-Sync, resetting the settings on all images except one and then copy and pasting settings, etc, though the crop is not properly syncing regardless of what I do.
Here's are instructions of how to duplicate this issue (there are some extra details/steps here, though this should be clear enough to produce the same result):
     1. in the Develop settings for a single selected image, go to Lens Corrections, click to Enable Profile Corrections (in the Profile tab), and then pick the GoPro Hero4 Silver Edition (Adobe Profile) if it is not automatically chosen for you (if you are using files from a Hero4 Silver camera). After this, click on the Manual tab, and set the Scale setting to 76. (as you will see, you now have the full horizontal width of the image that was getting cropped off, though you do see white around the edges that have been warped/shaped to correct the fisheye distortion)
     2. Press the R key (or click on the Crop Overlay tool just below the histogram). Change the Aspect option to Custom. Click to unlock the lock next to it (this seems to re-lock after setting to custom even if it was locked before). Place a checkmark next to the Constrain To Warp option. (At this point, you'll see the image gets cropped back to an approximately 4:3 ratio and the full horizontal width is not included in the cropped area) Click the upper right most corner of the crop area and drag as much to the right and top as it lets you go. Do the same for the lower left corner, dragging it as far to the bottom left as you can go. (Now, you will see that your cropped area is the maximum rectangular width and height you can select without getting any of the excessive white area) Click the Close button (or press R again) to leave the crop overlay tool.
     3. Press G to go back to the grid of images. Make sure the image you just adjusted the settings for is the only one selected. Right click on it, go to Develop Settings, and click Copy Settings. Click Check All on the window that appears and then click Copy.
     4. De-select the image you were working on. Select multiple other images in the grid. Right click on one of these, go to Develop Settings, and click Paste Settings. (at this point, you will see their aspect ratio has become more panoramic than the 4:3 aspect ratio the images previously were)
     5. De-select these images. Select one of these image, and then press D to go to the Develop settings for this image. Press R to go to the Crop Overlay tool. Here you will see the bug where the crop was not properly copied over from the first image. The selected area is smaller than the full width and height available to crop.
It seems that the bug is that Lightroom is only copying the aspect ratio (and the other settings), but not the actual crop selection.
I just thought of a workaround that I've tested and can confirm works (and will also work in a slightly different workflow than above). In step 1 above, for the Model (and Profile), manually pick the "GoPro Hero4 Black Edition" or the "GoPro Hero3-Silver Edition". If using the "Hero3-Silver" setting, the Scale (also in step 1 above) need only be set to 79 (rather than 76 for the Hero4 profiles). By picking one of these Lens Profiles and doing everything else the same as the other steps above, the crop settings do copy and paste properly. This does also appear to work properly when selecting the "GoPro Hero3-White Edition" Lens Profile, with a Scale setting of 75, which yields a slightly more rectilinear image (with a wider aspect ratio -- almost, but not quite 16:9).
While this isn't too big of deal as it does work by picking one of the other lens profiles (and the Hero4 Black Edition profile appears to make the same exact correction to the image), this was incredibly frustrating last night to notice that some files had the proper horizontal field of view / crop and others didn't, and other users may experience this or not even notice their crop is not copied properly (as, depending on one's composition and image, it's not extremely obvious with such a wide view).
I hope this discovery helps someone else and provides feedback for Adobe to correct this issue in the next version of Lightroom 5.
On a separate, additional note for Adobe: Please allow the crop overlay tool to "crop" an image to a size that is larger than the original dimensions of the image. This would allow for one to retain maximum original sharpness in the center of the image when using the Lens Profile tool to correct, or "de-fish" a lens, without having to scale the image down with the Scale option on the Manual tab of the Lens Corrections settings. For example, when I do the above process selecting the Hero3-White Edition profile, my final image dimensions are 3840 by 2257 pixels, reducing the size of the image in the center by 25%. If the tool allowed one to crop/scale a larger image size, and I kept the Scale option of the Lens Corrections settings at 100 rather than 75, my final image dimensions would be 5120 by 3009 pixels (larger than the 4000 by 3000 pixel dimensions of the original image which the tool now limits me to). Yes, the edges would be a little softer but the center would retain the original detail. (this is essentially what the Calculate Optimal Size button found in the Hugin open source software does, when using it on a single image for lens transformations/corrections)

Can you zip up a few of your GoPro images, upload them to dropbox.com and post a share link, here, so others can experiment with them, or do you mean this issue is global to all camera models?

Lightroom bug: activation state of brush adjustment lost

Since the introduction of Lightroom 2 through 2.4 there has been a bug in the operation of the local brush adjustment. It's as follows.
Start or edit a local brush adjustment so that the little activation bullet (radio like button) appears. Toggle before/after by typing . When returning the after view (after/before/after) the local brush bullet is no longer active, thus forcing me to reselect it. The behavior is especially irritating when I'm zoomed in so the active brush indicator not view (scrolled off). I am then required to zoom out so I can find it and click to reactivate it, then zoom in to continue my editing. I see no reason why the active brush should not remain active between toggling between after/before/after with "\". I prefer to do my before/after viewing with the full frame rather than one of the split pane views because I want to see as much of the image as possible. I've reported this issue directly to Adobe a few times with no response or fix.
p.s. while I'm at it (I'll repost in feature requests). The location of the brush adjustment indicator corresponds to where the mouse down first occurred. I should be able to move the indicator to where it's more convenient after placing it, regardless of where the brush strokes occur. For some images I have a number of local adjustments in the same region. They become crowded, making it hard to distinguish one brush indicator from another.

Hi
Good point, but does not work on all density settings, noda.

Weird AudioFileStreamParseBytes() bug

This is driving me batty. I'm using AudioFileStreamParseBytes() to parse data from an mp3 Shoutcast stream and then hand it off to the Audio queue for playback. The code works fine for all the Shoutcast streams I've tested, except for one - and of course the one that doesn't work is the one I really need to work.
From what I've been able to determine, AudioFileStreamParseBytes() is frequently getting confused by the mp3 stream. It's an MPEG-1 layer 3 VBR stream, at 44100, with an average bitrate of 80. The stream also includes a CRC-16 checksum in each MP3 frame. The stream is being generated by a Barix Instreamer 100 (in case that matters). The stream also plays fine via iTunes.
I'm cross-referencing the stream data with a network sniffer and can confirm I am receiving valid mp3 frames from the Shoutcast server. I also can confirm this identical valid collection of frames is being passed to AudioFileStreamParseBytes(). However, when AudioFileStreamParseBytes() calls my packet callback function with the parsed data, it will frequently skip a valid mp3 frame header and will instead think some data in the middle of the frame (which happens to start with FF) is the mp3 frame header.
Has anyone seen anything like this? The problem is so frequent it occasionally will happen on the very first frame, causing the AudioFileStream logic to misidentify the type of stream (usually resulting in an incorrect frequency or file type).
I'm tempted to just bypass using the AudioFileStream and load the mp3 frame into the AudioQueue directly from my TCP stream, but I thought using the AudioFileStream was supposed to offer some better error handling in case data transmission is temporarily interrupted. As it seems right now, however, the AudioFileStream is introducing errors of its own - at least with this one problematic Shoutcast stream.

Oddly, the problem with AudioFileStreamParseBytes() only exists when compiled for a Mac OS target. If I run the same code on an iPhone (either via the simulator or a real iPhone device) the function parses the MP3 stream just fine.
Weird...
Fortunately, my real target is the iPhone (I was just doing initial development on a Mac since I thought the audio stream debugging would be easier/faster - silly me!), so I guess I don't really mind this bug anymore.

Lightroom bugs: full screen mode and import

I'm considering buying Lightroom, it's quite impressive for a v1.0. But there are some troubling bugs I've run into on my 2nd or 3rd day of use.
Platform: Vista Ultimate, Lightroom 1.0, P4 2.8ghz, 1.5 GB mem + 2 GB ReadyBoost.
- Full screen mode is broken? I switched into full screen mode, and then back into normal mode. But now when I minimize the app and alt tab or click back into it, it's back in full screen mode. So I put it back into normal mode, but it goes back to full screen the next time I return to it. Very annoying. It's not just when I minimize it. If I change window focus *at all*, it sets itself to full screen mode.
- Import from camera doesn't work. When I attached my Canon 20d and selected Import from 20d, it said "Could not find files" or something. I had to import through Canon EOS Viewer.
Both of these features are a pretty basic part of workflow, so I'm surprised they're broken.

There are know issues with Vista which isn't supported yet. Also import has some issues to be resolved.
The read me has some of this noted.

Lightroom bug with GPS in raw files with XMP

I'm quite sure I've stumbled upon a bug in Lightroom. I look in my XMP file and I see my GPS info:
38,53,25118N
77,1,90390W
But in lightroom, it loads the coordinates as:
+58° 52' 25.00", -82° 14' 53.00"
Now I was thinking something was just wrong in the XMP file, so I load the same image in Bridge and I see the correct GPS information. So I know it's a problem with Lightroom.
I searched the forums and haven't found anyone else reporting this bug. So now I'm kind of stuck. Can anyone confirm or deny this behavior? I'm processing hundreds of images from my last vacation and I am really stuck here because I can't continue until this is fixed and the chances of it getting fixed any time soon seem pretty slim.

After hours of painfully trying everything imagineable, here is what the problem is:
I downloaded the images to my PC using Downloader Pro (Breeze Systems) and initially viewed them with Bridge. Using a Windows XP in French. Apparently Downloader Pro used a comma instead of a period. Bridge understands it this way, as it's just a separator. However LR does not.
To fix it, I had to delete all my images from the library, then by hand modify each XMP and change the comma to a period. Then reimport into LR. I tested this on a few images and it works. Now I'm off to do the rest of the photos of my trip.
I'll report this to Breeze Systems as well, as I think it actually originates on their end. It'd be nice if LR could still read it like Bridge does. It seems LR is more strict and that's the problem. This could be considered a bug by LR as well since instead of ignoring the GPS coordinates or giving an error message, LR seems to calculate it and ends up being way off. For example, I was shooting in washington and all my photos showed up as being in North Dakota, Canada, South Dakota, etc.

Can you reproduce this weird playlist bug???

I see this on Windows 7 and Windows 8.   Spotify desktop app.   Curious if it happens for other people, or on any other platforms.
1. Create a new empty playlist
2. Add six albums each with at least 10 tracks. I drag and drop the albums to the playlist, one at a time. You should now have at least 60 tracks in the playlist.
3. Use the default playlist sorting method, By that I mean, don't sort the playlist by song, artist, album name, or date. Should be the order you added the albums.
4. Scroll to the bottom of the playlist and highlight all of the tracks in the last album. Select the first track in the album with the mouse and then hold CTRL while you arrow down or mouse click to select the rest of the tracks.
5. Now drag the selected album up to move the tracks above the second to last album.   You're effectively swapping the bottom two albums in the playlist.
^^^ At this point I get an error message about adding duplicate tracks to the playlist. Which is strange because I have not added any new tracks, I'm only reordering them.
6. Now create another new empty playlist.
7. Select all of the tracks in the first playlist. CTRL-A works.   And drag and drop them to the new playlist
^^^ Notice the new playlist now has TWO copies of each album!   If the first playlist had 60 tracks, this one has 120!!!
Weird, eh?   Very frustrating when I make playlists of full albums....

Bug reproduced with LibreOffice 3.5.1.2 on Arch x86_64 here.
officeuser wrote:Can you also reproduce the bug? Can you create a gdb log of the bug according to these instructions?
I'm afraid I can't. At step 3, when I try to run base within gdb I get no further than the "Database assistant" dialog. Base freezes as soon as the main window is opened when running in gdb.

Image pixelation artifacts on export in lightroom (bug?)

Hi!
I've just noticed that while exporting a picture from Lightroom that the output quality was quite pixelated. I had added a few filters etc so I figured it was because of this. So I loaded (imported) the image as the original and compared it to an external viewer both at 1:3 (300% zoom).
This was the result:
http://adiza.nexticom.net/lightroom.png
Most visible artifact on this picture is if you look at the guy's back where the red and black colors cross. You can se major border pixelation in Lightroom where as the original image displayed to the right does not. These artifacts are actually exported when I save the image from Lightroom.
As you can see I am running the software in QEMU/KVM kernel virtualization. Though I have verified the results in a pure win32 environment aswell. And besides, the image rendering is a software based process as QEMU/KVM will only display the actual pixels rendered by the OS/program (everything else looks quite ok, right? :-))
Got any workarounds? Similarities? :-) The picture looks really bad after exporting. :/
Mikael

Hi again, Tony and Lee. Thankyou for your input. Phyllis: Interesting!
I've conducted an experiment with a few softwares on converting/exporting images and compared the results with LightRoom.
1. To make sure that the image program I was using actually converted the image (applying full export) rather than just copying the file I converted it to a .png lossless file first and verified that it looked OK.
Unfortunatly LR and LightZone could not read .png, but I verified rewritten .JPG file by md5 checksum.
2. The softwares used to load the PNG and then export (resave) it to 100% quality JPEG used was:
LightRoom, F-Photo, LightZone, GIMP, Google Picasa
To address the "interpolated by nearest neighbor" theory while displaying > 1:1 I've taken screenshots of the pictures displayed at 1:1 aswell as 1:3.
3. The viewers used to view the files were (sorry for lack of choices, but should prove the point):
Opera (web browser, but it can show images! ;)), Gnome Eye, GIMP
4. Results! :-)
1:1
http://adiza.nexticom.net/lr_experiment/geye_1_1.png (LR bottom right)
http://adiza.nexticom.net/lr_experiment/gimp_1_1.png (LR bottom left)
http://adiza.nexticom.net/lr_experiment/opera_1_1.png (LR bottom left)
Atleast I see that it's a remarkable difference with the LR export. Looking close at the hat and the coat he is wearing in contrast to the black is far more jagged in the lightroom export.
1:3 (GIMP could just zoom 200 or 400%, so picked 400%):
http://adiza.nexticom.net/lr_experiment/geye_1_3.png
http://adiza.nexticom.net/lr_experiment/gimp_1_4.png
http://adiza.nexticom.net/lr_experiment/opera_1_3.png
Zooming to 300 or 400% in the same viewing program makes the jaggedness show a lot.
Tony: hope this experiments shows what you were referring to.
Though if this is indeed a bug or quality issue of lightroom I would be quite dissapointed knowing that my photos processed through it would be degraded. Especially if I spend $299 on the program.
Thoughts about this test? Anything else I should conduct? Something I have missed?
Even though how it may sound, I would just like this resolved and over with so that I could use LR as it is a great tool :)
Mikael

Weird graphic bug on n760 twin frozr oc edition ?

Greetings;
i have something weird bug on my card. while scrolldown on internet black images top sides turns to green also sometimes in games i got green and purple pixels part of objectives and all pictures on firefox or internet explorer top corner have "shadow effects" when i scrolldown plus when i search something on google all blue links turn to purple when i scrolldown i didint even click them when i stop scrolling they are turns to blue again. this is happend me before 560ti hawk i dont know what should i do ?
i7-2600k
16gb ram
z77a-g43 mainboard
650w psu
always updated windows 7
not any oc. just stock
p.s.: sorry for bad english

Quote
https://www.dropbox.com/s/md8zf4yha2zdyj1/WP_20150318_018.mp4?dl=0
https://www.dropbox.com/s/w6no4xurq4cu6x0/WP_20150318_020.mp4?dl=0
Quote from: xAngelusx on 19-March-15, 04:07:03
not bluring you can see images changes color green/blue/pink
i can't see anything wrong in this movies
Quote
i have something weird bug on my card. while scrolldown on internet black images top sides turns to green also sometimes in games i got green and purple pixels part of objectives and all pictures on firefox or internet explorer top corner have "shadow effects" when i scrolldown plus when i search something on google all blue links turn to purple when i scrolldown i didint even click them when i stop scrolling they are turns to blue again. this is happend me before 560ti hawk i dont know what should i do ?
you have the same issue with your old card too??
can you test your card in another PC?
have you tried to reinstall OS?
have you tried a different cable for the monitor and/or a different monitor?

Weird iCal bug after 10.4.8 update

After updating to Mac OS X 10.4.8 I get the following display bug with my iCal reminders, i.e. the reminder appears way off to the side of the screen. This happens on both of my machines:
http://web.mac.com/csearles/iWeb/Site%202/Photos%202.html
G 4 Cube Mac OS X (10.4.7)

Hello Chris.
Apparently noone at Apple cares enough to
respond to this issue...
Sorry you and at least one other person are experiencing this problem but FYI - this is a user to user help forum only that is provided and moderated by Apple so it is a very rare when an Apple employee responds direct to a post or thread here.
Since I haven't experienced the same and this is the first I've seen such a problem reported, this issue may be caused by a problem with the iCal preference file.
Quit the iCal.app first and locate the iCal preference file in your Preferences folder at Home > Library > Preferences. Move the iCal preference file to the Desktop.
Launch iCal and check your iCal settings since all settings are stored in the preference file for the application.
If this resolves it, you can delete the old iCal preference file from the Desktop. If you can determine this doesn't resolve it before updating any preference settings, you can replace the new preference file created with the old preference file placed on the Desktop with the application quit before doing so.

Lightroom bugs with Windows Vista

I'm having difficulties with one of the file navigation controls in LR running under Windows Vista. The control that pops up with the import (choose files) function works fine, but the control that pops up with the add folder or create new library function misbehaves and causes LR to hang.
I've logged a ticket with Adobe, tried all the standard workarounds (run as administrator, re-create preferences etc.), but to no avail. I think it is a bug.
Has anyone experienced this? Any solutions out there?

What I've seen is that if you try to import from a card reader using the LR downloader, you get a list of files on the card and a message saying that they could not be imported. This also apparently damages the LR database because you cannot import even from a folder on the computer until you delete the database and create a new one. It happens in XP compatibility mode for me too. Otherwise, I have had no troubles using LR on my Vista machine. I can import from a card using another program's downloader and then import the folder into LR for editing.

Very Weird IOS Bug - iPad and iPhone

This is a really weird scenario - which I hope someone may shed some light on.
I'm building a new website, and there are parts of the website that don't function at all on either my iPhone 5, or iPad 2 - (both on IOS 8.3) , yet when I try the very same thing on other peoples iPads or iPhones (various types - some identical configuration to mine), it always works perfectly (I haven't found anyone else's iPad or iPhone yet where it doesn't work).
I've tried everything, upgrading from IOS 8.1 to 8.3, shutting down, removing all cookies and history (repeatably), turning off javascript then back on etc - yet for some reason nothing changes and I cannot get the functionality to work on my iphone or ipad.
There are a number of bit of functionality that fail, but an easy one to test is:
1/. Go Here: http://test.chillisauce.co.uk/hen/london/cocktail-making_15598/
2/. Click the save button
3/. When the modal opens click the top button labelled "Yes - Make A Stag Do"
On my iPhone / iPad the button does nothing. If the code is working on your iPad / iPhone , then you will be taken to another page - if not, like me, the button does nothing.
Even if you don't know what the issue is, I'd be greatful if you could tell me if the function works for you or not.

Hi Big Zee,
It works fine on my iPad mini and my iPhone. Maybe you have some old Javascript stuck in your cache.

Weird AXIS Bug ?

Hi All,
I am trying consume a ejb web sevice deployed using AXIS 1.2 RC2, WEBSPHERE 5.0 and axis custom (De)Serializers and I
am getting below error:
[java] AxisFault
[java] faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
[java] faultSubcode:
[java] faultString: java.lang.NullPointerException
[java] faultActor:
[java] faultNode:
[java] faultDetail:
[java] {http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException
[java] at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
[java] at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
[java] at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083)
[java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1712)
[java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
[java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
[java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
[java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
[java] at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
[java] at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
[java] at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
[java] at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
[java] at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:226)
[java] at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645)
[java] at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
[java] at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
[java] at org.apache.axis.client.AxisClient.invoke(AxisClient.java:173)
[java] at org.apache.axis.client.Call.invokeEngine(Call.java:2719)
[java] at org.apache.axis.client.Call.invoke(Call.java:2702)
[java] at org.apache.axis.client.Call.invoke(Call.java:2378)
[java] at org.apache.axis.client.Call.invoke(Call.java:2301)
[java] at org.apache.axis.client.Call.invoke(Call.java:1758)
[java] at irsc.bluestar.DCPlanListWSBindingStub.getDCPlanList(DCPlanListWSBindingStub.java:180)
[java] at irsc.bluestar.IrscDcPlanListWsClient.query(IrscDcPlanListWsClient.java:41)
[java] at irsc.bluestar.IrscDcPlanListWsClient.main(IrscDcPlanListWsClient.java:60)
[java] {http://xml.apache.org/axis/}hostname:hyddl0337
[java] java.lang.NullPointerException
[java] at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
[java] at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
[java] at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083)
[java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1712)
[java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
[java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
[java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
[java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
[java] at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
[java] at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
[java] at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
[java] at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
[java] at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:226)
[java] at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645)
[java] at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
[java] at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
[java] at org.apache.axis.client.AxisClient.invoke(AxisClient.java:173)
[java] at org.apache.axis.client.Call.invokeEngine(Call.java:2719)
[java] at org.apache.axis.client.Call.invoke(Call.java:2702)
[java] at org.apache.axis.client.Call.invoke(Call.java:2378)
[java] at org.apache.axis.client.Call.invoke(Call.java:2301)
[java] at org.apache.axis.client.Call.invoke(Call.java:1758)
[java] at irsc.bluestar.DCPlanListWSBindingStub.getDCPlanList(DCPlanListWSBindingStub.java:180)
I am not sure what this error means. Any ideas or is it a AXIS Bug ?
Thanks & Regards,
Kumar.

Getting the same error on Oracle envrionment. Did someone find a solution for
java] faultDetail:
[java] {http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException
[java] at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
[java] at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
[java] at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083)
Thanks.

Weird Lightroom bug

Similar Messages

Maybe you are looking for