Priority REST: There are no useful errors - priority-web-sdk

If the server can not respond, it always sends a status of 500 with the text "An error has occurred."
This is an incorrect behavior, the server should return a 4xx status with descriprion of error.
For example, if we send incorrect type for some filter:$filter=CUSTNAME eq P1122
Server should return error "400 - Bad Request" with message "Invalid filters."
Is this issue are common for whole Priority REST ?
How can we enable correct information for errors ?

Yes. Request that contains syntax errors or incorrect entity names or variable types,
may result in a 500 error.
I suggest you add to the web.config file the line
<customErrors mode="Off" />
in the system.web section.
Then you may see a more informative error.
In most cases it should help you figure out the reason for the error.


When we are getting error like: “Rejected by filter, soap fault sent” in datapower?

Could any please help me at which situation we are getting the following error in datapower
"Rejected by filter, soap fault sent"
You will get that error in any service where the Processing Policy or service processing throws an error.
It is a generic error response that does not indicate any error reason. You will need to examine the logs to find out the reason for the error.

What would cause a phantom 500 - Internal server error?

I get a "500 - Internal server error." when I visit a specific address:
chattahoochee tech - president
The problem is, that url doesn't exist! I even created a folder and it still shows a 500 error. Typically when I see this I typically have a php syntax error or something. All other non-existent urls tell the user it's a bad URL. This is the only page page that gives a 500 error.
any ideas on how this single page that doesn't exist throw that error?

Meteor errors internationalization

I'm trying to implement internationalization through just-i18n and it works fine so far.
Problem is I'm also using accounts-password and especially Meteor.loginWithPassword(user, password, [callback]).
On login error, the callback has an error object that basically looks like this :
details: undefined,
error: 403,
errorType: "Meteor.Error",
message: "User not found [403]",
reason: "User not found"
I thought the error code was unique and went with a i18n configuration file like this : 'fr_FR',
signin: 'S\'authentifier'
403: 'L\'utilisateur n\'existe pas'
So I could call it this way :
Session.set "error", i18n("errors." + err.error)
But actually, no matter what's the error, user not found or incorrect password, the error code is not unique :
details: undefined,
error: 403,
errorType: "Meteor.Error",
message: "Incorrect password [403]",
reason: "Incorrect password"
As i don't consider checking on a string value really consistent, how can i differenciate both ?
How would I go implementing internationalization with meteor built-in login ?
403 here is not a Meteor number for the particular error, but rather a HTTP status code. The same code can be caused by different errors.
Since the only difference between the error objects you get are reason and message, you need to use one of them to set up the internationalization code. They shouldn't change too much between Meteor releases, so you should be fine with this solution. 'fr_FR',
signin: 'S\'authentifier'
'Incorrect password': 'Le password est incorrectu'
'User not found': 'L\'utilisateur n\'existe pas'
Ah, and don't worry, login, signin, errors and 403 are internally represented as strings as well, so there's nothing inconsistent in such solution.

Active Directory authentication on Weblogic application server with unknown error cause

We've encountered an authentication error on our Weblogic application server (in production environment) while trying to authenticate an user with valid credentials (these credentials are hard coded in the application and this user is essentially used in order to access to technical resources such as web services). The authentication of this user is an automatic process for years, the credientials are hard coded and never change.
The error has never occurred before, and occured only for a while.
Here is the error coming from our application server logs (Weblogic) (the real user name has been replaced by XXX)
<Got AuthenticationException error while authenticating [family\XXX] to Active Directory.
[LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9,
comment: AcceptSecurityContext error, data 548, v1db1]> >
The error code 49 refers to a Invalid credentials error.
See list of LDAP error codes
But as mentioned before, the user and password were valid.
And I can't found anything about the mentionned Active Directory error (here data 548)
Usually, when a Invalid credentials exception occurs, it's due to a bad entered password by the user, and the log trace is as the following with a 52e error
The code 52e refers to invalid credentials
<Got AuthenticationException error while authenticating [family\XXX] to Active Directory.
[LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9,
comment: AcceptSecurityContext error, data 52e, v1db1]> >
The error code 52e refers also to invalid credentials from Active Directory error codes list, but this error is common and understood (wrong credentials given by the user)
I'm more concerned by the error code 548 , which seems to never be documented or even mentioned in search engines results...
See list of Active Directory error codes
By the way, our internal technical support hasn't found any trace of a such problem in the system logs.
Any ideas?
The error code 548 (0x548, or 1352 after hexa to decimal conversion)
seems to refer to the following Windows error code :
The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation.
Documentation of Windows error 1352 - 0x548
According to the following referential, this should be the cause of the problem (the error codes and descriptions seem to match with Active Directory and LDAP error codes)
List of Windows errors
Since you seem to be using domain\user format for the bind DN, I wonder if the 548 error (which is new to me as well and I would love to know its meaning if you ever find it) has to do with the SASL style bind that implies.
Could you try binding with a proper DN format and see if that makes a difference?

Mystery… Faked Referrer Generates 500 Instead of 404 Error

I hope someone can provide some clues.I have begun receiving
regular 500 errors from a page that does not exist. Without providing
the entire error page, here are the essentials:
[Django] ERROR (EXTERNAL IP): Internal Server Error: /sample/
IOError: request data read error
'PATH_INFO': u'/sample/path/',
If I visit the page, I get a 404
error, but the error message referencing the same page generates an
internal server (500) error.
Should I be concerned?
Why do I get a 500 error instead of 404 error?
Any suggestions for troubleshooting?
This has been driving me nuts for a few days. Any help is very
Are you trying to change one of the attributes of request, which are read-only (or at least, should be considered to be read-only"). Are you trying to change request.META['HTTP_REFERER']?
This is still an open bug which might be resolved in v. 1.6.
In the meantime, though, you can use this workaround in your file.