Can anybody explain this?
by Volker Weber
Konstantin has posted one of those error message, that had me shaking my head in disbelief when I first saw them:
I don't really want to know what the error message means — ok, I want to know it — but who in their right mind would even want to display it? Does this work as designed? If so, has anybody shot the designer?
And there are more people stupefied.
Comments
This can happen if the developer forgot to remove a debug message in an untested (rarely hit) code segment. Poor software testing. But I have to admit that thorough testing of GUI applications is a real challenging task. Don’t crucify the designer or the developer. :-)
Error messages like that have been in the product for ages. I don't see them often, but I've seen a few. I used to seem the more frequently way, way back, I can't remember when I saw the last one. There used to be an article and a list explaining some of them in the KnowledgeBase. Don't know if it's still in there.
That's an untranslated internal error code.
What does it mean? Don't know. It's in the range for the package called NEM, but the details of that package aren't exposed in API documentation. I think I used to know what NEM is, but it has slipped my mind. (If I had to guess, it's something to do with the editor module, or it is the editor module.)
Why do you ever see an untranslated error code? There are three reasons that I know of . One is that the Notes client or core code has gotten itself so borked that it can't even try to call the right routines to translate it to a proper error message. If this is the reason, it does work as designed, at least to the point that it does not simply crash. Something else obviously is not working as designed, but at least the module that displays untranslated error codes (as a last resort) is working. In the same circumstances, many other products might just crash without even displaying a diagnostic code that can at least be reported to the vendor's support organization.
The second reason is simply that somebody forgot to create an error string to correspond to that error. The third is that it is a "should never happen" error, or at least the programmers in Westford thought so. Obviously, in both these cases, it doesn't work as designed -- or should have been designed. The fact that it showed up in the wild does tend to point toward it at least being a very uncommon, hard to duplicate error, otherwise QA would have flagged the fact that it was untranslated and it would have been fixed -- but that's no excuse.
I still reckon this takes some beating.
It's Eclipse, obviously, but I've given that up now. I run 8 in classic mode these days.
Simple: Call the AA, your friendly breakdown assistance. Obviously programmed by a Brit.
If I remember correct this has something to do with malformed Richtext in Richtextfields.
I've seen this before a few times, I forget where. I think it was a corrupt local names.nsf, or maybe a bookmark.nsf.
My best helpdesk call years back was a user who rang up to tell me that an "uncorrectable error" had occurred and was there anything I could do.
I asked them to repeat what kind of error it was.
I haven't seen this one in years. I used to get it during setup and teardown of LC LSX connections.
There are a whole load of error messages just like this that crop up from time to time. In my experience they’re nearly always rich text related, with tables being the main culprit. As to why we see them, Richard’s explanation sounds most sensible to me.
I think that means you're running low on power. Please insert 10 AA batteries. ;-)
@Richard: IIRC, NEM is the windowing / graphics portability layer for Notes. I think the acronym means something like Notes Emulation Module.
Wow. Different from the usual #C3:OA. This deserves some thought.
Nah, that was #C3:0A. ;-)
I love these. Not.
#29:3 used to appear quite often with early 6.0x version. Turned out to be related to badly formed MIME messages in conjuction with SwiftFile enabled. I'ts been a while since I've seen that one. :)
I used to get that #10:AA message, but I had forgotten/blanked it (gosh, thanks for reminding me...).
For me it turned out to be a local database corruption.
Running ncompact -c -i on all databases when Notes was closed fixed it.
Since I'm the discoverer, let me add some information on how (or rather when) I first saw this:
Only recently, I switched - or rather was switched from Mozilla Thunderbird (yes, we used it at work!) to Lotus Notes 6.5.6 (incidentally just two weeks before I received an End of Life notice - snicker!). Still used to my Thunderbird shortcuts, I tried to use Ctrl+U to view an HTML message's source code from the Preview view. Result: #10:AA
Doesn't happen when you use Ctrl+U from an open message.
Doesn't happen in 7.0.2.
I tested it in 6.5.3 english, and it does happen if CTRL+u pressed on the view level (so, it is not a translation issue). It does not happen in 7.0.2 as Richard allready pointed out.
I got the #04:0C just yesterday. It had to do with tables and rich text:
I used rtitem.RenderToRichTextItem(doc), and the form used by the document had, in some instances, a dropdown/listbox where there was an error value. Not in the field value itself, but in the formula for available options, the @DbLookup returned an error, and I did not catch that using @IsError. So even if the field value was correct (text data type), it failed to create the correct rich text. An error was thrown in the agent, but the resulting rich text was still stored somehow in teh target document, and when attempting to open that document, I got that non-descriptive error...
Gregory, Just to clarify: by "untranslated" I was not referring to translation from English to (insert other language here). I was referring to translation from a two byte integer error code to an error string. Perhaps I should have used the word "unresolved" instead, to avoid confusion.
Don't be silly, it means the dude in Office #10 is an alcoholic and goes to meetings.
Or the Girl in aisle 10 on the AA flight of the developer was hot.
Post a comment
Recent comments
Ben Poole
on Finally getting started on last.fm at 12:41
Volker Weber
on Finally getting started on last.fm at 12:31
Ben Rose
on Finally getting started on last.fm at 12:22
Yves Luther
on Coming up next Thursday: sticky and sweet at 12:19
Hartmut Wiehr
on Wo gibt es gescheite CD-Läden? at 11:13
Michael Becker
on Wo gibt es gescheite CD-Läden? at 10:26
heiko hebig
on Amazing photos - all taken with a mobile phone at 01:50
Chris Reckling
on Finally getting started on last.fm at 00:53
Alexander Kluge
on Finally getting started on last.fm at 22:31
Volker Weber
on Finally getting started on last.fm at 22:22
Jamey Shiels
on Synchronizing iPhone with ... Lotus Notes at 22:10
Dominik Schwind
on Finally getting started on last.fm at 21:25
Kevin Pettitt
on Showstopper for Lotus Connections at 20:45
Martin Hiegl
on Showstopper for Lotus Connections at 19:27
goran angelov
on iPhone: Can't hear through the receiver or speakers? at 18:53
Sean Cull
on I have seen faster at 18:27
Matthias Leisi
on Coming up next Thursday: sticky and sweet at 18:21
Ted Stanton
on Showstopper for Lotus Connections at 18:17
Handly Cameron
on Showstopper for Lotus Connections at 18:15
Volker Weber
on Showstopper for Lotus Connections at 18:11
Alan Lepofsky
on Showstopper for Lotus Connections at 18:09
Volker Weber
on Showstopper for Lotus Connections at 18:04
Ben Rose
on Showstopper for Lotus Connections at 18:04
Ted Stanton
on Showstopper for Lotus Connections at 17:52
Ben Poole
on Showstopper for Lotus Connections at 17:48
Click here to subscribe
