• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Plesk issues with SQL 2005 express - Is someone going to help me out of shine me on?

C

coolvibe

Guest
About one month ago I had paid a consultant to connect my install of SQL Server 2005 express. Before this connection, I had no problems with SQL Server or DNN. It seemed like the connection to Plesk was successful. I was able to install DNN with no problem. Then I tried installing modules to DNN. This is where the problems started. I first received an error loading the DNN blog module. Here's a link to that forum entry.

http://www.dotnetnuke.com/Community.../108/threadid/281659/scope/posts/Default.aspx

I have tried new DBS and they all seem to have an issue after being connected to Plesk. I know it's may be something small. But, I or the consultant who connected it know what's wrong.

The web address of my dnn install is www.coolvibeonline.com/talent

The host login = host

Password = Travertin3

The error statement for the blog module can be found on the blog page.
 
Back
Top