We have a system where user enters his data in a form and we save Data in CRM (Its in cloud so we have no access to it and all that). Now suddenly we have started getting error everytime, we try to send data.
Error we get is:
An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.
Inner Exception: Authentication Failure DefaultURL
It fails on every command i use like RetrieveMultiple, Create to name a few.
Nothing has been changed, it worked for 6-7 months without any change/problem and suddenly we are getting this error everytime we try to communicate with CRM system.
I have tried connecting to CRM after disabling our firewall and that didnt change anything, so nothing we have changed.
Does anyone getting this error recently? I have tried looking for this but their isn't much help I have found on any blog.
Any help will be appreciated.
After days of investigation, we found that the password we were using to connect to CRM expired and need updating. We updated the password and it worked.
Related
in my organization we have a mailbox that receives email from different sources (about 5) everyday, set to track all incoming emails in the CRM.
All the mails are correctly tracked on the CRM every day, except for one that always fails (same source, similar content every day).
If I send the exact same email from another address, the mail is correctly synchronized with the CRM, so I think it could be something related with Exchange.
This is the message I get if I open the mailbox record:
An unknown error occurred while receiving email through the mailbox "xxxxxx".
The owner of the associated email server profile xxxxx has been notified. The system will try to receive email again later.
Email Server Error Code: Exchange server returned UnknownIncomingEmailIntegrationError -2147220970 exception
Looking for this specific message didn't get me any result, while just searching the error code I found out it could be something related to plugins.
Unfortunately there is no plugin that fires on email creation, same for workflows and so on. By the way, sending the email from another address just works fine.
Has anyone ever had such a problem? Is there some place where I can find other logs and dig deeper in the problem?
Thanks in advance.
For anyone else experiencing this issue: I received the error code -2147218683, which is different, but it turns out this was due to the user in question not having the right security role. Gave the account sys admin and the error went away.
I have recently converted a trial account into a paid starter package and, since I've been assigned a long number, my attempts to send messages via the HTTP API have failed with the following messages in the Message Reports console:
An error occurred while attempting to route the message
Routing error (status 9)
I have confirmed that my username, password, and api id are entered correctly and that the long number has been matched to the active API. I've tried the "Valid Sample Code" provided on the API management console, all with the same result. Below are a few failed message ids if that's helpful for anyone on the Clickatell team.
6d7868662782cfd7d1708996bca066b1
4f837467ed535521ef39d9d885f121f9
2be08f4663a3d9d7cf2e5b9e9cad2d5f
For what it's worth, my trial account worked fine and as expected, so I'm fairly certain that this is not (obvious) user error on my part. I also upgraded a few hours ago; I'm not sure if there is a wait period between account activation and functional service. Thanks for any help on this.
Have you tried setting mo=1 and using your long number as your sender id from=123456789?
make sure you dont add any programming symbols in the text message. i had an exclamation mark and it gave me a status 9 error.
http://api.clickatell.com/http/sendmsg?api_id=xxxx&user=xxxx&from=13055140341&mo=1&password=xxxx&to=xxxx&text=xxxx
For what it's worth, I encountered a very similar problem with the REST API. It also requires the undocumented "mo=1" and "from=[your long number]" fields to be included.
Also, in the FAQ, they have "MO=1" but in actuality, it has to be a lower-case.
From OP:
Clickatell support responded with the following advice that resolved my problem. I also changed the password on my API key during the process which seemed to be part of the issue.
http://api.clickatell.com/http/sendmsg?api_id=xxxx&user=xxxx&from=13055140341&mo=1&password=xxxx&to=xxxx&text=xxxx
"from" is your long number, and because I'm using 2 way messaging , mo=1 needed to be set also. It would have been helpful if this were in the exemplary code provided on the api info and help section, but alas, I had to go through support to get my answer. It took about 2 business days for the response, but they were helpful
Early on in developing an iOS app with Xamarin, another developer and I got push notifications working for it using the Azure Messaging Component. It's a few months later now, and sometime between then and now, the push notifications stopped working. The code is still basically the same as before (which is nearly identical to the example code for the component), it was just moved to its own class for maintainability.
On Hub.UnregisterAllAsync(DeviceToken, error =>, error is:
The operation couldn’t be completed. (NSURLErrorDomain error -1012.)
On Hub.RegisterNativeAsync(DeviceToken, tags, error =>, error is:
URLRequest failed for <NSMutableURLRequest: 0x167dbd80>
{ URL: https://[our namespace].servicebus.windows.net/[our hub name]/Registrations/?$filter=deviceToken+eq+'[long token]'&api-version=2013-04 }
with status code: unauthorized
We tried a new hub, and a new namespace with a new hub, but without luck. I've rolled back the changes we've made since it was working, but with no luck there either. The same error happens on multiple devices, on multiple networks. It never shows any errors in the portal for APNS, so I'm assuming this is something with authenticating to the Hub itself. What is really weird is that a Windows Store app that we wrote to test this registers and receives notifications using the same credentials without any issue. Can anyone point me in the right direction on this? The error messages above aren't very helpful.
It turns out that the test devices all had the automatic date and time synchronization turned off. The iPad I was primarily testing with was only off by about 20 or 30 seconds, so I didn't notice it was off. Another question involving the same thing with a Windows or Windows Phone registration clued me into it, but I can't find the link to it now. Apologies for that, thanks to whoever that was!
Looking at the API, it makes sense why it's so sensitive to this. It uses the date and time to generate the SAS Token, thus the unauthorized response when the time is just a few seconds off.
I have a strange problem with the Facebook C# SDK on Windows Phone 7. I am using the SDK to post pictures to users' walls. For the first authentication and the first few posts, it works great. After a while (I have a feeling the magic cutoff is 24hrs) I start to get an error on every post:
FacebookOAuthException was unhandled
(OAuthException) Error validating access token.
This happens after my line of code that does the actual post has run...
m_facebook.PostAsync(#"/photos", parameters, PostComplete);
... but before my PostComplete callback function is called. No code of mine is running when the exception happens. My Application_UnhandledException is not called - I get the error in a dialog in the middle of the screen in VS, and it says that no source code is available.
If this exception means I need to show the login screen again, that's fine - right now I'm both not sure what it means and not sure how to trap the bugger. Any help appreciated.
Chris
What publishing permissions do you use?
By default, access tokens expire after a short time period to ensure applications only make requests on behalf of the user when the are actively using the application.
For getting a long-lived access token, you need to ask for the offline_access permission.
I've googled this error but came up with no solution, this happened when I installed oracle database 11g, I tried to reach https://localhost:1158/em and this error pops up in firefox
Secure Connection Failed
An error occurred during a connection to localhost:1158.
SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long)
* The page you are trying to view can not be shown because the authenticity of the received data could not be verified.
* Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.
Anyone had similar problem before, I'd be thrilled if someone could help. thank you
Are you sure that the dbconsole was secured and is actually an SSL service? Try to connect to http://localhost:1158/em and see what happens...