Every project fails during startup after the user logs in with administrator privileges. The log confirms an initialization failure involving EnfMVC and PersistentAdo, but it does not identify a product version, database file, provider, or definitive root cause. Treat the article-database theory as a hypothesis until configuration and data-access checks reproduce the failure.
Read the Failure Sequence
| Order | Module | Code | Recorded condition |
|---|---|---|---|
| 1 | URRightsManager | S332003 | The user logged in as administrator. |
| 2 | BaseDecider | S000000 | A generic message error was recorded. |
| 3 | EnfMVC | S015009 | An error occurred during initialization. |
| 4 | PersistentAdo | S000000 | Arguments were incorrect, outside the permitted range, or in conflict. |
The sequence occurred at 14:11:32 and repeated at 14:18:08. Because the administrator login succeeded before both failures, the evidence does not support treating authentication as the immediate failure point.
Separate Confirmed Behavior from the Database Hypothesis
PersistentAdo is the lowest-level module named in the recorded failure chain, and its message indicates an invalid, out-of-range, or conflicting argument. This supports investigating the data-access request used during initialization. It does not prove that the article database itself is corrupt; the failing argument could also originate in configuration, a connection definition, or data passed to the persistence layer.
The report states that the error appears when starting any project. If verified under the same user and workstation, that pattern shifts attention from one project file toward shared application configuration or shared data access. The evidence does not establish which shared component is responsible.
Diagnostic Procedure
- Reproduce the failure and confirm that the log retains this order: successful URRightsManager login, BaseDecider error, EnfMVC initialization error, then PersistentAdo argument error.
- Compare the result across more than one project. Record whether every project reaches the same PersistentAdo message; do not classify the incident as project-specific if the sequence is identical.
- Inspect the application's configured data source and article-data settings for missing, malformed, out-of-range, or mutually conflicting values. The evidence provides no parameter names, so validate existing entries without inventing replacements.
- Capture the complete log around the first error and preserve the affected configuration before changing it. Use the earliest PersistentAdo occurrence as the diagnostic anchor because later messages may be consequences of failed initialization.
Verification and Escalation
After correcting an identified configuration or data-access issue, start the same projects again. Verification requires successful initialization with no S015009 EnfMVC error and no S000000 PersistentAdo argument error. If the sequence remains unchanged, provide the complete log, application identity and version, project scope, and relevant data-source configuration to the manufacturer's official support channel; those product details are absent from the evidence and are necessary for a product-specific remedy.
FAQ
What does PersistentAdo S000000 mean during project startup?
The recorded message says that arguments are incorrect, outside the permitted range, or in conflict. It identifies a data-access argument failure but does not identify the offending setting.
Does EnfMVC S015009 prove that the article database is corrupt?
No. S015009 records an initialization failure, while PersistentAdo reports an argument problem. Database corruption is not confirmed by the available log.
Why does the same startup error occur in every project?
If multiple projects produce the identical module sequence, investigate shared application configuration and shared data-access settings before treating one project as defective. Confirm this by reproducing and comparing the complete logs.
