Skip to main content
C
Chrischhan13-Aquamarine
13-Aquamarine
November 30, 2018
Solved

[1'018] Data store unknown error: [Error occured ....] Possible causes?

  • November 30, 2018
  • 3 replies
  • 1930 views

Hi,

 

We have a TWX 8.2.5 on a Windows Server with MSSQL DB in an offline Production Environment.

We tried to update some parts of the running TWX Application (Mashups and some backend functionality in Things etc.)

But we can not update entities in Composer or import new Extensions because of this generic error: [[1'018] Data store unknown error: [......"

 

What are possible causes of this error?

- Space on devices is good >20GB on the two harddrives.

- Memory is ok with room for more

- Tomcat and MSSQL restarted serveral times

- Tomcat configurations without Memory Settings

 

What can we try to fix this error? We didn't have access to the instance all the time. So I want to check all possibilities before connecting again.

Attached a small screenshot from logview

Best answer by Chrischhan

Soo update on this.

 

We found the issue ...

Short Version: Database was "Full"

Long Version: We used MSSQL Express (has a 10GB Quota on DB Size) but the DB Size was around +4GB so we did not think in the DB full way any more. After Setting up a new Server with the local administration to mirror the system, we found out the admins set a folder quota to the DB Filesystem Folder. So MSSQL can't write to DB because of Storage full. Removed the Quota and all works as expected.

 

EDIT: @unknown DEV is it possible to get more specific errors in such cases? not only generic errors?

3 replies

C
CRArko5-Regular Member
5-Regular Member
November 30, 2018

Hi, Christian.

 

Will check the logs and advise.

 

Thank you,

 

-- Craig A.

C
CRArko5-Regular Member
5-Regular Member
December 4, 2018

Christian,

 

Is this occurring in a single-sign on (SSO) environment?

 

 

Thanks,

 

-- Craig A.

 

C
Chrischhan13-AquamarineAuthorAnswer
13-Aquamarine
January 24, 2019

Soo update on this.

 

We found the issue ...

Short Version: Database was "Full"

Long Version: We used MSSQL Express (has a 10GB Quota on DB Size) but the DB Size was around +4GB so we did not think in the DB full way any more. After Setting up a new Server with the local administration to mirror the system, we found out the admins set a folder quota to the DB Filesystem Folder. So MSSQL can't write to DB because of Storage full. Removed the Quota and all works as expected.

 

EDIT: @unknown DEV is it possible to get more specific errors in such cases? not only generic errors?

Terms & ConditionsCookie settingsAccessibility statement