
Acoléa
Specialized software application in the Aricie catalog.
Browse the four main areas of the Aricie business portal.
Software products developed and supported by Aricie.

Specialized software application in the Aricie catalog.

Specialized software application in the Aricie catalog.

Specialized software application in the Aricie catalog.

Specialized software application in the Aricie catalog.
Headquarters in Mureils with branches in Paris, Lyon, and Grenoble.
DNN remains a practical content management platform for organisations that need structured publishing, flexible permissions and integrations with existing business systems. Yet when a portal slows down, a module fails or users cannot sign in, IT teams need more than general platform familiarity. They need a repeatable method for finding the cause and restoring service safely.
Effective DNN training for IT teams should focus on real operational work: reading logs, isolating configuration faults, checking database behaviour and distinguishing application errors from infrastructure problems. This approach gives administrators the confidence to handle incidents without relying on guesswork or escalating every issue to a developer.
Australian organisations often support users across several time zones, from Perth to Sydney and Melbourne. A troubleshooting programme must therefore help teams diagnose incidents quickly, document decisions clearly and plan changes around business-critical periods such as end-of-financial-year reporting.
Aricie combines DNN solutions, custom software and professional training for business and technology partners. Its DNN expertise and training can help teams build practical skills that match their environment, whether they manage an internal intranet, a public-facing portal or a collection of connected applications.
The first skill is learning how to define the incident accurately. A blank page, a 500 error, a failed login and a slow page load can all look like “DNN is down”, but each symptom points towards different checks. Training should teach participants to record the affected URL, user role, time of failure, recent changes and whether the issue occurs in every browser or only under specific permissions.
From there, technicians can follow a consistent sequence: reproduce the fault, check the DNN Event Viewer, review IIS logs, inspect Windows Event Viewer and compare the behaviour across staging and production. This method reduces random configuration changes and creates an audit trail that other team members can understand.
DNN portals often depend on third-party modules, custom skins, scheduled tasks and integrations with CRM, finance or identity platforms. Troubleshooting training should show how to identify whether a failure originates in the core platform, an extension or a related service. Version compatibility, assembly conflicts and incorrect module permissions are common sources of disruption.
Teams should also practise using controlled tests. Disabling a recently updated module in a safe environment, checking the browser console and comparing page behaviour with a default skin can narrow the fault without placing production content at risk. This is particularly useful for organisations in regulated sectors where every change requires evidence and approval.
Performance diagnosis requires more than checking whether a page eventually loads. Participants should learn to separate network latency, IIS resource pressure, inefficient SQL queries, excessive caching and heavy page composition. Useful exercises can include reviewing response times, inspecting scheduled jobs and identifying pages that call multiple external services.
Database awareness is equally important. IT staff do not need to become database administrators, but they should understand connection-string failures, transaction errors, blocking, backup status and the effect of poorly designed queries. In a distributed Australian operation, a slow portal can affect staff in Brisbane differently from colleagues in Perth, so monitoring should capture regional experience rather than relying on a single office test.
Debugging is only half the responsibility. A strong course also covers recovery plans, backups, rollback procedures and communication during an incident. Teams can rehearse restoring a previous module version, correcting a web.config setting and validating a portal after an application-pool restart. These exercises make emergency actions more deliberate.
Release discipline matters when systems support customers, members or professional partners. Changes should move through development, test and production with documented approvals, clear ownership and a defined rollback point. Scheduling maintenance outside peak trading hours is useful, while Australian teams should also account for public holidays, daylight-saving differences and the heavier workload that often surrounds EOFY.
The most valuable DNN workshops use scenarios that resemble the team’s daily environment. A useful exercise might involve a permission change that prevents editors from publishing, followed by a separate failure in an external API. Learners must identify the symptoms, collect evidence, prioritise the business impact and explain the fix in language suitable for managers and users.
Training can also include portal governance, knowledge-base writing and post-incident reviews. Teams that support applications such as business dashboards, property workflows or document portals benefit from practising with realistic roles and data flows. Aricie’s broader software portfolio, including solutions such as Acoléa, Adylic, AricieGrid and Budg-Immos, reflects the kind of connected business context in which DNN administrators often work.
A capable support team should leave training with practical runbooks: where logs are stored, which accounts can perform emergency checks, how to escalate a database issue and which tests confirm that service has been restored. These documents are especially valuable when support is shared between offices in France, Australia or other locations, or when an external partner joins an incident.
Australian IT teams can strengthen their DNN operations by choosing training that combines platform administration, debugging practice and incident response. Explore Aricie’s DNN services and professional learning options to equip your administrators with a clearer troubleshooting process, safer release habits and the confidence to resolve portal issues before they become extended business interruptions.