After an evening and a morning wrestling with a DotNetNuke installation it finally started working.

As I’ve mentioned before, eventually I screw around with things long enough to stuff them up. This time was no exception.

The ‘deal breaker’ on this occasion was, once again, permissions. File system permissions, database permissions, permissions, permissions, permissions. Yuk.

All sorts of weird error messages ensued from my reluctant, system administrator-wise, attitude to permissions.

For example:

  • Could Not Find Part Of Path <drive>:\
  • Object reference not set to an instance of an object
  • Login failed for user ‘DotNetNuke’. Reason: Not associated with a trusted SQL Server connection
  • …and others that elude me at this time

Fortunately a solution was eventually had.

Points of note:

  • SQL Server
    • Setting MSSQL to use Windows Authentication is more secure but means that you have to jump through more hoops. If you don’t want to jump through those hoops but don’t discover this until after the fact you have to make changes.
    • Changing the DotNetNuke database owner to the MACHINENAME\ASPNET user account is not ideal but solves a lot of problems.
  • DotNetNuke README
    • “the {Server}/NetworkService user account must have Read, Write…” blah, blah… simply didn’t work for me. I assigned the permissions to the MACHINENAME\ASPNET user account and got on with my life.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.