[Bug]:SQLite startup fails, no such table SMSet

[JiayangLi7]

Contact Details

a0152591129356@gmail.con

Describe the bug

After installing using docker-compose.yaml, the server fails to correctly parse the element format of the loaded AASX file. As a result, PUT, POST, and other commands cannot be executed.

{
"Messages": [
{
"Code": "InternalServerError",
"CorrelationId": null,
"MessageType": "Error",
"Text": "SQLite Error 1: \u0027no such table: SMSets\u0027.",
"Timestamp": "11/17/2025 15:10:55"
}
]
}

To reproduce

1. use docker-compose.yaml with the following content to install aasx server
   services:
   aasx-server:
   container_name: aasx-server
   image: docker.io/adminshellio/aasx-server-blazor-for-demo:latest
   restart: unless-stopped
   ports:

   • 5001:5001
     environment:
   • Kestrel__Endpoints__Http__Url=http://*:5001
     volumes:
   • ./aasxs:/AasxServerBlazor/aasxs
     #command: --with-db --no-security --external-blazor http://localhost:5001
     command: --with-db --start-index 0 --save-temp 10 --no-security --data-path /AasxServerBlazor/aasxs --external-blazor http://localhost:5001

2. cmd run: docker-compose up to start the container:

3. • Once the AASX file is successfully loaded, open your browser and go to:
     http://localhost:5001

• In the web interface, select a Property element and click its URL to view the details.

Screenshots

Expected Behaviour

A clear and concise description of what you expected to happen.

Version

No response

Operating System

Win

Relevant log output

{
  "Messages": [
    {
      "Code": "InternalServerError",
      "CorrelationId": null,
      "MessageType": "Error",
      "Text": "SQLite Error 1: \u0027no such table: SMSets\u0027.",
      "Timestamp": "11/17/2025 15:10:55"
    }
  ]
}

[listl-franz]

I'm dealing with the same issue. Here are my observations and setup details, which might help narrow down the cause:

• The issue starts specifically with the Docker image 0.3.1.405-aasv3-alpha-latest. Prior versions worked without any problems.
• AASX files are mounted into the container and are confirmed to be in the correct location.
• The container is launched without --with-db flag, still API calls for both Submodels (SMs) and Asset Administration Shells (AASs) consistently result in SQLite Error 1.