cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Getting Data store unknown error

SOLVED
Highlighted
Guest

Getting Data store unknown error

Am getting this error :

Execution error in service script [NotificationData InsertOrUpdateDeviceNotification] : Wrapped java.lang.RuntimeException: com.thingworx.common.exceptions.DataAccessException: [1,018] Data store unknown error: [Error occurred while accessing the data provider.] Cause: com.thingworx.common.exceptions.DataAccessException: [1,018] Data store unknown error: [Error occurred while accessing the data provider.]

NotificationData is data table. I tried restarting tomcat but still this error persist. Previously it was working fine.

Am using ThingWorx 7.3.1-b39 and tomcat 8.5.

Tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions

Re: Getting Data store unknown error

Hi Nisha Bhagtani​,

You are using double slash ( // ) in the platform-settings.json which starts with drive letter C: which indicates a Windows server. There should be single slash ( / ) in windows while defining the Path.

Also, in the main question thread; you mentioned that you are using tomcat 8.5 for ThingWorx 7.3.1-b39. Tomcat 8.5 is not a supported version of Tomcat for ThingWorx 7.3.1-b39. I would recommend you to downgrade to 8.0.x with a minimum of 8.0.33.

View solution in original post

11 REPLIES 11

Re: Getting Data store unknown error

Is your database and TWX application on same server ? is database services up ? was there any Db upgrade ?

Re: Getting Data store unknown error

Yes both database & TWX application are on same server. Using postgress and services are running and there is no upgrade

Re: Getting Data store unknown error

Please attach your platform setting.json file .

Re: Getting Data store unknown error

Hi Nisha,

Please provide more details with enabling the stack trace logging.

  • To further troubleshoot the error, enable Stack Tracing on the LoggingSubsystem:
    • From Composer, select System > Subsystems > LoggingSubsystem
    • Select the Configuration page
    • Check (enable) the Enable Stack Tracing option checkbox
    • Click the Save button.
  • With Stack Tracing enabled on the Logging Subsystem, additional information will be logged to the ErrorLog.log file when the error occurs again.
    • This file is only accessible from the ThingWorx server's file system; it is not available in the Log Viewer Mashup.
    • A number of exception call stacks will be logged for this error at the same timestamp.  Generally, the first exception in the set will contain the underlying reason for the error.

Thanks,

Br,

Anna

Re: Getting Data store unknown error

Nisha it looks like Postgresql setup could you please confirm the same or let us know if it's not PostgreSQL. If it is indeed PostgreSQL could you please share the version and the postgresql.log from the postgresql installation directory?

Re: Getting Data store unknown error

please check platform settings file

Re: Getting Data store unknown error

Version is 9.4.

Log is empty

Re: Getting Data store unknown error

Hi Nisha Bhagtani​,

You are using double slash ( // ) in the platform-settings.json which starts with drive letter C: which indicates a Windows server. There should be single slash ( / ) in windows while defining the Path.

Also, in the main question thread; you mentioned that you are using tomcat 8.5 for ThingWorx 7.3.1-b39. Tomcat 8.5 is not a supported version of Tomcat for ThingWorx 7.3.1-b39. I would recommend you to downgrade to 8.0.x with a minimum of 8.0.33.

View solution in original post

Re: Getting Data store unknown error

Nisha Bhagtani​ , Ankit Gupta​ pointed out few reasonable changes , Allow default storage and remove // from platform setting and see if it works .

Log is empty because it tries to create storage folder while you launch Tomcat . Also let me know if your storage folder is getting created at the mentioned location.

Further , using un-supported tomcat version against Thingworx might cause certain issue.  So would suggest check that as well.

This issue need basic  troubleshooting to some extent and I believe this should get fixed.

Announcements

Thingworx Navigate content has a new home! Click here to access the new Thingworx Navigate forum! ______________________________