Object reference not set to an instance of an object
Hi!
I was running Newsletter Studio on one test-server, with a local smtp-server. Everything was working good. I moved the whole solution onto a production server. It means files, and database, everything. When I try to send out an test-mail on the prod-server, I get "Object reference not set to an instance of an object". See the enclosed capture. The only difference in the settings of newsletter studio is the SMTP-server. When I click "Test connection" I get a successful message, so the problem doesnt seem to be there.
I am running Newsletter Studio v1.3.5 (trial-mode). I would like to buy the full version, but this problem must be solved first.
the problem is solved. The problem was that I just added a "bogus" sender for testing-purposes which was now allowed. It had to be a sender name which is allowed to relay on the mail-server. When I scheduled the newsletter for sending I got a more informative error message telling me that the sender is not able to relay on the server. When I click the option "Send out as test mail" I got the not so informative error message stated in the previous post.
I guess it could be a good idea to handle the error the same way on "Send out as a test mail", as the other similar events.
Sorry for taking so long with the answer! CodeGarden took a time last week. So this problem was shoing when you did an accual send out? Or when you sent the test email? Where was the error handling good vs. bad?
the good error handling (at least better) is at the actual send out, while the error handling when sending a test e-mail is as stated above (non-informative).
Object reference not set to an instance of an object
Hi!
I was running Newsletter Studio on one test-server, with a local smtp-server. Everything was working good. I moved the whole solution onto a production server. It means files, and database, everything. When I try to send out an test-mail on the prod-server, I get "Object reference not set to an instance of an object". See the enclosed capture. The only difference in the settings of newsletter studio is the SMTP-server. When I click "Test connection" I get a successful message, so the problem doesnt seem to be there.
I am running Newsletter Studio v1.3.5 (trial-mode). I would like to buy the full version, but this problem must be solved first.
Thanks,
Eirik
Hi again,
the problem is solved. The problem was that I just added a "bogus" sender for testing-purposes which was now allowed. It had to be a sender name which is allowed to relay on the mail-server. When I scheduled the newsletter for sending I got a more informative error message telling me that the sender is not able to relay on the server. When I click the option "Send out as test mail" I got the not so informative error message stated in the previous post.
I guess it could be a good idea to handle the error the same way on "Send out as a test mail", as the other similar events.
Cheers,
Eirik
Hi Eirik!
Sorry for taking so long with the answer! CodeGarden took a time last week. So this problem was shoing when you did an accual send out? Or when you sent the test email? Where was the error handling good vs. bad?
// m
Hi Markus,
the good error handling (at least better) is at the actual send out, while the error handling when sending a test e-mail is as stated above (non-informative).
Cheers,
Eirik
Hi!
Okey I see, I'll keep a note of this and we'll try to improve it in upcomming versions.
/ m
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.