- Support
- Why is ItemPath not able to connect and write to the SQL database?
-
Account & Licensing
-
Installing & Updating
-
Power Pick Connections
-
Data Push & Data Pull
-
API
-
Reports
-
Snapshots & Dashboard
-
Workflows
Why is ItemPath not able to connect and write to the SQL database?
Issue:
Errors like "unable to open database file" or "Gateway Timeout" (504) because disk space is full; cannot write to db.
Resolution:
Add or clear out disk space on the host machine.
If ItemPath is failing to write to the local file system, it could be that the local disk is full of data. Space should be added or cleared out.
You may want to restart ItemPath after making more disk space.
It is worth letting the ItemPath support team know so we can make sure there are no issues with ItemPath's backups not cleaning up data over time, or check if ItemPath is writing more data than usual.
Resources
To learn more about ItemPath and see it in action, please book a demo with our sales team. In the meantime, here are some of our popular articles and key topics.
Installing & Updating
How long does ItemPath store data, and when does it back up?
Data Storage Here are the sets of data that ItemPath stores for a period of time: Data from Snapshots is stored depending on the interval of the snapshot. Pictured below are these ...
Installing & Updating
How much disk space is ItemPath using?
du -h ~/ItemPath This command shows the disk usage of the ItemPath folder where all data and backups is stored. It shows the folder size, including subfolders, so there is some ...