Skip to main content

Dear community,

 

Reach out to this community due to an issue with a JSON datasource connector.

The situation:

TimeXtender on premise (v20.10.40) using a Cdata ADO.net Provider for JSON 2021 (21.0.8011.0) in the Business Unit layer of the project. The connector uses a general account-password access for this datasource.

User 1 logs on to the server TimeXtender is running on, does read data for this connector and got all the information expected.

User 2 logs on to the server TimeXtender is running on, does read data and get just some information but not even related to this source. No error.

Both users use the same connector with that general account to connect to this JSON datasource, but with different results.

I asked for logfiles with verbosity = 3 of both users and attached are anonymized files. I am not sure how to interpret the differences in the logs.

The log with the wrong results starts with a time out but playing around with this kind of setting does not change the outcome. Also some additional data is added in the buffered content in comparison with the buffered data in the right log. This confuses me.

At the end of the wrong log more execution information is written than in the right log, so to speak. Something different is happening but why?

So I reach out to this community hoping that someone has seen this before and or knows what to look for or even already has a solution.

Thanks in advance for your reaction and kind regards,

 

Aad Dijksman

 

 

Hi @adijksman 

When you say “User 2 logs on to the server TimeXtender is running on, does read data and get just some information but not even related to this source” - what do you mean by “some information”?

What data is User 2 not getting that User 1 is getting?

It would be great if you could send a video (i.e. screen recording) in order to get a better sense of the different outcomes experienced by User 1 and User 2


Hi @adijksman is this still an issue? if so could you please help explain what data is User 2 not getting that User 1 is getting?


Hi Christian,

 

No, issue is solved and the solution was simple afterwards. An obsolete RSD file in the User2 %APPDATA%\CData\JSON Data Provider\Schema directory which first was claimed not to be there, was the cause. Removing this RSD file was the solution.

 

Thanks for thinking along and support and kind regards,

 

Aad


Reply