Error in documents shared with me on doc server

Docs
1

Hi @Nikolas,

After the upgrade problem I shared in this link, we are using the Community edition without a problem. However, I noticed a problem with the documents shared with me.

  • When I click on it, I get an error: “Provider id not found or you have no access”
  • The selected file opens when clicking the new file badge that shows the new documents and selecting a file from the list.
  • The Documents module opens and the same error message appears on the screen when I try to return to the file location from the file menu in the opened documents.
  • The shared files can not be accessible after that because the new file badge disappears after opening the shared document.

I found nothing in Windows Event Viewer or the application’s logs. I wonder if a field was missing in the database tables during the update.

Since I couldn’t find a similar question in the forum, I wanted to ask you directly.

Can you suggest to me something to find a solution?

PS: The common section works as expected.

Thanks,

2

Hey @koksal.basar :hugs:

Could you please provide a video showing the issue?

It would be much easier to understand the problem and reproduce it accurately, as it’s a bit difficult to follow based solely on the description. A video will help us identify the exact steps.

3

Hi @Nikolas ,

The link contains a video demonstrating the error. I hope it’s explanatory enough.

Shared with me is not working but common is working as you see.

1 Like
4

Hello @koksal.basar :wave:

I apologize for the delay in responding; I was unable to reply sooner.

Thank you for providing the video and details regarding the issue. I’ll review the video and assess the problem tomorrow. Thank you again for your patience, and my apologies once more for the delay :handshake:

1 Like
5

Hi @koksal.basar :vulcan_salute:

You mentioned in your previous post: “After installing the MySQL database backup I took before, I cannot log in with either the new user or the previous user information. Users cannot log in at the current stage. Since the e-mail system does not work, the password change process cannot be sent. For this, I tried to get the relevant link from the notify_queue table and run it. However, I get an ‘Invalid e-mail or expired link’ error.”

To help me better understand the current problem, could you clarify how you resolved this login issue?

I suspect there may be some issues related to database updates that could be contributing to your current issue with document access.

As a potential solution, you could try creating a backup of the portal and a system backup for safety, then install ONLYOFFICE Workspace on the same machine as a fresh installation, and finally, restore the OO backup.

6

Hi @Nikolas,

Sorry for my late reply. I missed your answer.

  1. I can’t take backups via OnlyOffice. So I backed up the data to MSSQL using HeidySQL (as you suggested).

  2. I installed the new version of Workspace and transferred the backups to this database. However, due to the errors that occurred, I prepared scripts to recreate the tables. I think this caused the fields of some tables in the new version to be lost.

  3. When the new installation did not work and I saw from the logs that some fields were missing in some tables (I didn’t note which ones :()), I made a new installation on another virtual machine. I compared each table one by one. I added the missing fields to the tables (Maybe I missed some). Based on my instincts, I determined that their contents were null or had default data :).

  4. In general, the problems of logging in, creating and opening files disappeared. However, the file sharing problem that I shared with you appeared.

The truth is that we somehow use the portal as it is. I apply the golden rule of information systems. “If it works, don’t touch it.” :slight_smile:

Finally, I don’t know if backup works on the community version. Because backup doesn’t work on this setup either.

That’s it. :slight_smile:

If you have any suggestions, I’d love to hear them.

Good luck

1 Like
7

Hey @koksal.basar :handshake:

Hmm, I don’t have any immediate ideas for resolving this issue. :thinking:
I will think it over when I have some time, but I can’t promise I’ll find a solution.