I tried adding the following task to the DNN Scheduler but when it runs I'm getting the following exception error message:

EXCEPTION: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it

My local account username and password are apparently not working for authentication. Does anybody know a method to do a WebRequest without knowing a system administrator's username and password? My real username and password below were altered for security reasons.

================

using System;
using System.Collections.Generic;
using System.Text;
// using System.Reflection;
using System.Net;
using System.IO;


namespace KeepAlive
{
public class KeepWebSiteAlive : DotNetNuke.Services.Scheduling.SchedulerClient
{
public KeepWebSiteAlive(DotNetNuke.Services.Scheduling.ScheduleHistoryItem objScheduleHistoryItem)
{
base.SchedulerEventGUID = "";
base.aProcessMethod = "";
base.Status = "";
base.ScheduleHistoryItem = new DotNetNuke.Services.Scheduling.ScheduleHistoryItem();
this.ScheduleHistoryItem = objScheduleHistoryItem;
}
public override void DoWork()
{
try
{
this.Progressing(); // Optional

// access web site
WebRequest req = WebRequest.Create("http://www.aoballoons.com/DNN/KeepAlive.aspx");
req.PreAuthenticate = true;
NetworkCredential networkCredential = new NetworkCredential("xxxxxxx@aoballoons.com", "yyyyyy");

// Associate the 'NetworkCredential' object with the 'WebRequest' object.
req.Credentials = networkCredential;

WebResponse resp = req.GetResponse();
Stream s = resp.GetResponseStream();
s.Dispose();
// resp.Close();
// req.Abort();

this.ScheduleHistoryItem.Succeeded = true; // Required
this.ScheduleHistoryItem.AddLogNote("Accessed web pages to keep them alive");
}
catch (Exception exc)
{
this.ScheduleHistoryItem.Succeeded = false; // Required
this.ScheduleHistoryItem.AddLogNote("EXCEPTION: " + exc.ToString()); // Optional

// notification that we have errored
this.Errored(ref exc);

// log the exception
DotNetNuke.Services.Exceptions.Exceptions.LogException(exc); // Optional
}
}
}
}

 

We've just released a free module, which does the job without the need for an external service. The site pings itself only once at recycle time, which triggers a restart.

Check the corresponding post.

---

Jesse CTO - Aricie

Well I would say that keeping the site alive and monitoring its up time and activity does not have to be the same issue.

I think that some people will be happy having the option to sort out the keeping alive without the need for an external artefact. I also encouraged the core team to integrate some kind of similar system in the next releases.

There is also the gain of having null idle time if the site runs critical client tasks, without the cost of heavy pinging (only one ping per recycling is needed).

Finally I'd add it resulted studip simple, only a few lines of code, quasi null processing time, so I naturally made it free with source code included.

---

Jesse CTO - Aricie