Expected response code 250 but got an empty response swift_transportexception Amazon SES - amazon-ses

I am using Amazon SES for sending emails from PHP application through Swift Mailer. I am searching on google from 3 4 days but was unable to find any solution. I tried every possible solution available on Internet but still, my issue is not resolved. Can someone please guide me how to resolve this issue?
This happens intermittently but appears to cause all our mails to stop sending once the initial error occurs - restarting the queue worker fixes it but inevitably the problem re-occurs intermittently.

Related

Mule Application getting redeployed in a loop

I have a couple of Mule applications running on mule container version 3.3.0. Recently I have observed that one of my mule application is getting redeployed again and again in a loop continuously.
The Mule app first get deployed then immediately within 2-3 seconds the mule app gets un-deployed and then gets deployed automatically. This is happening in loop and I don't see any specific errors in the log.
Can somebody please help me out with this problem and let me know the reason for the above behavior and how to fix it.
Thanks
Jai
There has to be an error, the problem is probably that you don't see it. Try locating the logfile named mule.log (or mule_ee.log) rather than mule-app-APPNAME.log. You might find the error there.
Otherwise, triple check that there are no weird permissions on the directory app (as the lock file should be created there).

GCM chrome notifications not being received

I am developing a chrome extension to which I was pushing notifications so far successfully from my server. However, the notifications suddenly stopped working. I can see that my POST to https://www.googleapis.com/gcm_for_chrome/v1/messages is answered with a 204 so its not my server code.
I am sure I have not hit the 10k per day limit because I would be seeing a completely different code otherwise.
I have a few questions:
Is there a rate limit that I may be hitting?
Is it possible that I have spammed the google server too much and am being blocked?

Silverlight Application gives 4004 error when trying to use RIA services

I have written a Silverlight application that is basically an account registration form. I have been able to successfully deploy this to one of our production servers running windows server 2008/IIS7. While this took some time to do, I was able to work through and solve the issues that came up fairly easily. Now I am trying to deploy the application on our main production server. This server is running windows 2003/IIS6 and this is where I have hit some problems.
I have solved most of the issues and now the silverlight application will load and I can see the form for a few seconds before it disappears. I believe during this time it is trying to load data from the database using the RIA services.
In IE I get the following error:
Webpage error details
Message: Unhandled Error in Silverlight Application
Code: 4004
Category: ManagedRuntimeError
Message: System.Windows.Markup.XamlParseException:
System.Windows.Markup.XamlParseException:
System.Windows.Markup.XamlParseException:
Cannot find a Resource with the Name/Key ApplicationResources [Line: 6 Position: 9]
I believe it must be a configuration issue in IIS6 because the app works fine on IIS7 but I am drawing a blank as to what to try. I have spent hours trying to find a solution to this particular problem and while others have mentioned getting this problem the answers always tend to be non-specific in nature.
This is what I have done so far:
Added New Application Pool for .NET 4.
Set the website to use .NET 4 on the ASP.NET tab (nearly had heart failure when this did an iisreset).
Added the MIME types for Silverlight .xaml, .xap, etc.
Unchecked Integrated Windows Authentication (was giving an error when checked).
Give Execute permissions to Scripts and Executables.
Recycled the application pool.
The one thing I have seen suggested but have not tried is an iisreset, and while I am not entirely convinced that doing this would solve the problem, we have scheduled this to be done tonight (if I cannot find a solution before then).
So basically I am wondering if anyone out there has seen this problem and knows how to solve it?
UPDATE 1: We tried an iisreset last night and as I expected this did not solve the problem.
Okay I have solved the problem. As suggested I did a WCF trace on the application. This highlighted the REAL problem straight away, which was 'The SELECT permission was denied on the object...'. Once I fixed this the application works as I expected. It turns out that a colleague of mine had already made this permission change on our other server (running IIS7) so that was why it worked there (this is bad - I know).
Also it didn't help that the javascript error I was receiving on the client side (shown in the question) had nothing to do with the underlying issue and led me well and truly up the garden path.

The system is experiencing problem that requested for support

HI,
We created a web application which is running in many web servers. One of the server was recently updated. When they request the web page which usually streaming PDF content, the alert message displayed and return back to last page visited.
The alert message has the title: Windows Internet Explorer
Alert message is "The System is experiencing problem that requested for support".
We never faced this exception. Can anyone help me?
Thanks,
P.Gopalakrishnan.
grep your source code for the message; it's probably raised by javascript in your app.
What happens when this problem occurs? Does the browser crash?
I've seen this sometimes with IE. I don't know why. It has happened when dowloading Excel spreadsheets, but it has also happened when downloading code from SourceForge.

appc-security-server will be available soon

All of a sudden while opening my dashboard on Titanium Studio I am getting following error:
503 Service Unavailable.
No server is available to handle this request.
I searched on Google for the error but found nothing except for the same question asked at Appcelerator Forum as this link.
The problem got resolved itself I guess it was due to some error from Appcelerator services or their server was down.