Hi all,

I have also purchased this control yesterday and have the same issue. "AJAXPro is not enabled yet." the changes had been made to the Web.config. My provider is GoDaddy.com I'm not sure if this is an issue.

Thank you,

Ernesto.

Ernesto,

Thank you.  Please see the ticket that you opened recently with our help desk.  Your license information is contained in the ticket.

I face the same problem as well, what I have done is :

1. I have old version of DNN, I install swirlchat 2.02 and it working fine
2. I update to DNN4.7, but swirlchat become not working.
3. I try to enable ajax at "host Setting", it mention it enable successfuly and the httphandler exist at web.config. But after I click update, popup says "Ajax Not enable" occur

FYI, I am using own server(windows 2000 with SQL 2005 express). Kindly please advice urgently

thanks

We have seen several customers who are using the SwirlChat module on sites that ALSO run the PageBlaster provider from Snapsis Software.  It appears that under some default configurations of PageBlaster, the AJAX communications may be being cached causing the infamous "Ajax Not Yet Enabled" dialog/error.

The fix for this problem, in most instances, has been accomplished by adding the following line to the PageBlaster configuration:

< path pattern="(\.asmx|\.axd|\.ashx|rss|admin|install|wizard|filemanager)" excludeFrom="All" />

This configuration keeps the AJAX communications from being intercepted and cached by PageBlaster.

Please see this forum thread at Snapsis for more details:

http://www.snapsis.com/Support/SnapsisSupport/tabid/601/view/topic/forumid/9/postid/5445/Default.aspx

Additionally, we have found that some installations of DotNetNuke did not properly install the "ActiveDirectoryAuthentication" package.  If you are NOT using Active Directory Authentication for your website, and you are continuing to have problems getting the "Ajax Not Yet Enabled" error message even though you have already enabled AjaxPro, you can do the following to test and see if your ActiveDirectory Authentication package is corrupted on your site:

First, you should look into your website's "\bin\Providers" folder and see if the following DLL is present:
DotNetNuke.Authentication.ActiveDirectory.dll
If the DLL is not present, then your ActiveDirectory Authentication provider is probably corrupt, and needs to be uninstalled completely. (You can download the latest version of the AD Authentication from DotNetNuke.com if you need it in the future).

To uninstall the ActiveDirectory Authentication Provider Package, do the following:

1. Login as Host
2. Goto:  Host > Host Settings > Advanced Settings > Authentication Settings
3. click the red "X" next to Active Directory Authentication package to remove this package (don't just uncheck "enabled", but actually remove the package).
4. Follow the prompts to completely remove the package (you can always re-install the package with the latest update from DotNetNuke.com).

You can also test to see if the ActiveDirectory Authentiaction Provider corruption is causing problems by performing the following as well:

1. Open your web.config file in your favorite text editor
2. Find the line: <customErrors mode="RemoteOnly" />
3. Change the line to: <customErrors mode="Off" />
4. Browse to the following URL on your site: http://yourwebsite_root/DesktopModules/SWIRLChat/core.ashx
5. If you get the following error message, then your ActiveDirectory Authentication Package is broken, and is causing problems with Swirlchat and Ajax:
   [NullReferenceException: Object reference not set to an instance of an object.]
      DotNetNuke.Authentication.ActiveDirectory.Configuration.GetConfig() +62
      DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule.OnAuthenticateRequest(Object s, EventArgs e) +276
      System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
      System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
6. Once you confirm the error or not, then you can change your web.config file back to it's original condition (<customErrors mode="RemoteOnly" />)