Hi Anders,

What error do you see when you access the schema browser?

Also, are there sub-folders within that study?

Regards,

Jon

Hi Jon
More precisely; the error message comes when I try to open the Study folder from within Schema browser. The error image is attached.

No Sub-folders.

regards, Anders

Anders,

Thanks for confirming. So can you at least get into the details of the dataset rather than viewing the information? Specifically here:

https://labkey01.usit.uio.no/labkey/study/TNS%20%28visit%29/datasetDetails.view?datasetId=5002

and here to edit the definitions:

https://labkey01.usit.uio.no/labkey/study/TNS%20%28visit%29/editType.view?datasetId=5002

I believe you may have a duplicate date column in your dataset, which is causing the error. If we can get access to editing the definitions, you should be able to remove/modify the bad field so you can access the data.

Regards,

Jon

Jon,

1) https://labkey01.usit.uio.no/labkey/study/TNS%20%28visit%29/datasetDetails.view?datasetId=5002

Gives:
"Invalid Dataset ID"


2) https://labkey01.usit.uio.no/labkey/study/TNS%20%28visit%29/editType.view?datasetId=5002

Gives:
"The server encountered an error: 500 There was an error processing the request.
Column date already exists for table c10d88_ogtt
(Error type: java.lang.IllegalArgumentException)"

non of them gives med access.

regards, Anders

Anders,

That's really odd since your original error had dataset 5002 listed in your original attachment.

Can you actually get into the Manage view of the study to look at all the datasets you have?

You would go to the Manage tab in the study, then click "Manage Datasets" and see the list of datasets available.

Do you see dataset 5002 or the name of the dataset you were trying to access?

Regards,

Jon

Jon,
Yes I see it from Manage Datasets,but cannot open it from there, or any other places i have tried.


Manage Datasets > OGTT Dataset Properties

gives:
An unexpected error occurred
Column date already exists for table c10d88_ogtt

regards, Anders

Anders,

Let me do some more research with my developers and get back to you.

Hopefully, we will not have to ask you to provide us with an export of the study or an admin login to your platform to investigate/resolve the issue.

Thanks for your patience.

Regards,

Jon

Jon,
I am happy to give you admin login.

Regards, Anders

Anders,

Ok. Please setup this email address as a site admin: xxx@xxxxxx.xxx

Once we resolve the issue, you can then deactivate/delete the user.

Regards,

Jon

Anders,

Thanks for setting up the user. I will be looking at the TNS (Visit) project.

Regards,

Jon

Anders,

Also, were you able to access that dataset before? Was there anything you did prior (i.e. any changes you made) before the dataset became inaccessible?

Regards,

Jon

Jon,
I am not sure what you mean with the first question, but i uploaded it my self and used it before this yes.
I am not sure exactly what I did with it, but think i wasin Edit Dataset Definition and played with the date.

Regards,
Anders

Hi Anders,

Thanks for the information. After an initial assessment, there are two options here:

1. Allow us remote access to your PostgreSQL database so we can try to fix the underlying table that managed to get two date columns and then fix the dataset.

or

2. Help you delete the OGTT dataset and start over by re-importing the excel files "TNS (visit)-OGTT-2015-02-06-1627.xls" and "TNS (visit)-OGTT-2015-02-06-1635.xls" that are sitting in the files directory for that study (assuming those are the files that you used to create your OGTT dataset from).

Based on what I've seen so far, I think we should take the first option here. So far, in trying to get to that dataset from any place seems to create that error since the platform is trying to read the table first.

However, if you would prefer to try deleting the table, please see if this link will work:

https://labkey01.usit.uio.no/labkey/study/TNS%20%28visit%29/deleteDataset.view?datasetId=5002

If this link works, then the dataset will be deleted. If it doesn't work, then you'll just get the same error as before and we would just proceed with the original plan.

I've created the following bug ticket for tracking purposes: https://www.labkey.org/issues/home/Developer/issues/details.view?issueId=22513

Regards,

Jon

Hi Jon
Thanks for the tips. We removed the extra date field (which was named data1) directly in the PostgreSQL database and problems solved.

 Kind regards
Anders

Anders,

Glad you were able to get the underlying database corrected! Feel free to deactivate/delete the user account you created for my access and let us know if you have any further questions.

Regards,

Jon