Occurred: Is There A Problem Here?: Occurred

Showing posts with label Occurred. Show all posts

20110908

Problem ID: 2550799104346194733
Entered by: Ben Simo

Quit what cannot start?

@jangles tweets: Is this the most useless Microsoft Outlook error message or what?

Edit

20110904

Problem ID: 621626757916737839
Entered by: Ben Simo

An illegal state has occurred

@Maylor tweets: Just got this error message using the new version of @googleanalytics. So many political jokes, so little time...

Edit

20110901

Problem ID: 1293414026076037925
Entered by: Ben Simo

Processing the appearance of an object

@Racco tweets: such a usefull error message Adobe. thanks

What object? A code object? A GUI object? Some other kind of object?

And, what error occurred while processing this unspecified object?

My 10th grade English teacher often said "There are no such things as things and stuff. Be specific." I'd like to add "object" to "things and stuff".

Edit

20110828

Problem ID: 8053903988938253995
Entered by: Ben Simo

Bugs multiply

All I wanted to do what blog about a bug I encountered while blogging about a bug...

... but that quickly turned into blogging about a bug I encountered while blogging about a bug I encountered while blogging about a bug I encountered while blogging about a bug I encountered while ...

The Blogger editor in Picasa is broken. I can't type any text without getting Javascript errors.

Edit

20100215

Problem ID: 4682648210590265605
Entered by: Ben Simo

2 >= 2

"#Eclipse comes with brilliant error messages like this" - @jashaj

Edit

20100203

Problem ID: 3889710955971384511
Entered by: Ben Simo

No errors

Submitted by Nandagopal.

Considering the prevalence of software errors, no errors could be considered an error. :)

Edit

20100201

Problem ID: 2468126752835325087
Entered by: Ben Simo

System error: 1814

Error 1814? What does that mean? Login to what service? Running the application as another user? What terminates?

Edit

20100128

Problem ID: 4638555566957031347
Entered by: Ben Simo

Please provide the following to Oracle Support

@dotbart: Ah yes, crystal clear error handling by Oracle

I've got lots of unknown (to me) files on my system. Which ones does Oracle want? ;)

Edit

20100124

Problem ID: 7117915253723892658
Entered by: Ben Simo

Find the stack trace in the HTML source?

Do developers of the Manfrotto web site really expect consumers looking at camera tripods and tripod heads to view the page source code and look for a stack trace to deal with errors? And why would a stack trace be output to the user in an HTML file and not be displayed without viewing the source?

How do I contact an administrator?

What is Jahia?

Why should I find a stack trace in source code to send to an unknown site manager if an email has been sent to an administrator?

Clicking the link to return to Jahia -- whatever that may be -- displays the following.

The Manfrotto web site developers must be thinking their photographer users are also web developers who are willing to investigate their software issues. Right? ;)

Edit

20100123

Problem ID: 331197613513923239
Entered by: Ben Simo

Keep waiting?

@edfladung: great error messages from movable type, how 5 years ago is this?

An error occurred. Is the error that the user is performing a search? Or did an error occur in performing the search? Should the user keep waiting for an erroneous search to complete?

Edit

20100118

Problem ID: 3085747891278830446
Entered by: Ben Simo

SCORM?

I didn't even know I had a SCORM that could error.

Other than the context line, this information doesn't appear to be very helpful for the programmer either.

Edit

20100115

Problem ID: 7501688042513587620
Entered by: Ben Simo

Context, Context, Context.

@jacksri: This error message might be slightly better than useless if I knew which app generated it.

Error messages that don't specify to what they apply aren't very helpful.

If I have to click Cancel to ignore, I'm not really ignoring it. Am I?

What is the difference between Yes and Cancel?

Edit

20100112

Problem ID: 9069110056659713566
Entered by: Ben Simo

Undefined is null or not an object

@scottpatton: an IE script error on an atm? tha makes me feel "safe". NOT!!!!!!

Nothing increases confidence in banking technology like Internet Explorer script errors on ATM machines. ;)

Edit

20100105

Problem ID: 9064221379360064619
Entered by: Ben Simo

The exception unknown software exception occurred in the application

Tweeted by TomasSedovic.

Edit

Problem ID: 6438437602060845671
Entered by: Ben Simo

The local device name is already in use

What is "local device name"? The drive letter to which the network file share is mapped?

Apparently, "local device name is already in use." is the error message displayed when I try to access a mapped file share from a Windows workstation after the share has been removed from the specified server.

So why not report something like "The file share does not exist"?

Edit

20100103

Problem ID: 2411550725315953078
Entered by: Ben Simo

Your form was submitted previously

I receive a link and am asked to complete a quick survey to access customized information based on my answers. I complete the survey and am shown customized links to other data. In clicking links, and then the browser back button to access this data, I click back one too many times and go back to the survey. Upon resubmitting the survey to return to my page of links, I get the above error.

I cannot re-access the page of links in order to view the rest of the data.

Perhaps if I clear cookies ...

Edit

20100101

Problem ID: 1373444459477418661
Entered by: Ben Simo

Refer to the Wii Operations Manual

yoonhoum: Y'll know about Window's Blue Screen of Death right...? Introducing... Nintendo wii's Black Screen of Death... *s

Edit

Problem ID: 3098457381746598014
Entered by: Ben Simo

Seriously Serious

maishsk: I wonder what would have happened if the error was not SO Serious ..

Edit

20091230

Problem ID: 3376802480909208966
Entered by: Ben Simo

You can now have a life

“JAJAJAJA / Best error page ever jaja. ¿De dónde es?” - @Ac_Queen

Edit

Problem ID: 2336937486662221227
Entered by: Ben Simo

You have been signed out of PlayStation(R) Network

“ACTVISION!!! >:O. HELP!!! I tried everything. I called Sony” - @Ice_95

Edit

Software testing tools: Heuristics for recognizing problems.

Usability Heuristics

from Jakob Nielsen

• Visibility of system status Visibility of system status: The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
• Match between system and the real world Match between system and the real world: The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
• User control and freedom User control and freedom: Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
• Consistency and standards Consistency and standards: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
• Error prevention Error prevention: Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
• Recognition rather than recall Recognition rather than recall: Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
• Flexibility and efficiency of use Flexibility and efficiency of use: Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
• Aesthetic and minimalist design Aesthetic and minimalist design: Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
• Help users recognize, diagnose, and recover from errors Help users recognize, diagnose, and recover from errors: Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
• Help and documentation Help and documentation: Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

Consistency Heuristics

from James Bach
and Michael Bolton

-F amiliar Familiar: The product is not consistent with the pattern of any familiar problem.
E xplainable Explainable: The product is explainable.
W orld World: The product is consistent with the real world.
H istory History: The present version of the product is consistent with past versions of it.
I mage Image: The product is consistent with an image that the organization wants to project.
C omparable Products Comparable Products: The product is consistent with comparable systems.
C laims Claims: The product is consistent with what important people say it’s supposed to be.
U ser Expectations User Expectations: The product is consistent with what users want.
P roduct Product: Each element of the product is consistent with comparable elements in the same system.
P urpose Purpose: The product is consistent with its purposes, both explicit and implicit.
S tatutes Statutes: The product is consistent with applicable laws.

FAILURE Heuristics

from Ben Simo

F unctional Functional: The error detecting, reporting, and handling functions properly.
A ppropriate Appropriate: Errors are reported at the appropriate time in an appropriate manner.
I mpact Impact: The impact of the failure is communicated to those impacted.
L og Log: The error is appropriately logged; or not logged.
U ser Interface User Interface: The error is reported in the user interface in terms that the user understands.
R ecovery Recovery: The user is informed of what they need to do to recover from the error.
E motions Emotions: The error handling and reporting has a positive influence on user emotions.

Security Vulnerabilities

the OWASP Top 10

1. Injection Injection: Injection flaws occur when untrusted data is sent to an interpreter as part of a command. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without authorization.
2. Broken authentication and session management Broken authentication and session management: Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities.
3. Cross-Site Scripting Cross-Site Scripting (XSS): XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.
4. Insecure Direct Object References Insecure Direct Object References: A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to gain unauthorized access to data.
5. Security Misconfiguration Security Misconfiguration: Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.
6. Sensitive Data Exposure Sensitive Data Exposure: Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.
7. Missing Function Level Access Control Missing Function Level Access Control: Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.
8. Cross-Site Request Forgery Cross-Site Request Forgery (CSRF): A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.
9. Using Components with Known Vulnerabilities Using Components with Known Vulnerabilities: Running software components with known vulnerabilities can compromise the vulnerable components and anything those components can access -- undermining defenses.
10. Unvalidated Redirects and Forwards Unvalidated Redirects and Forwards: Using untrusted data, without validation, to determine the destination of redirects and forwards can enable attackers to redirect victims to phisihing or malware sites.

20110908

20110904

20110901

20110828

20100215

20100203

20100201

20100128

20100124

20100123

20100118

20100115

20100112

20100105

20100103

20100101

20091230

Problem or no problem?

Usability Heuristics

Consistency Heuristics

FAILURE Heuristics

Security Vulnerabilities

Popular

Recent Problems

Recent Comments