Recovering from a inadvertent change to disk group shares

[Stephen_Beck]

We are experiencing a serious problem resulting from an inadvertent action whereby an additional share was set up for our diskgroups.  The established OnBase hidden share name is OBDATA$ (folder name OBDATA). A second share was set-up on the folder OBDATA called DOCS.  Once this second share was established, OnBase began storing documents to the path (\\<server_name>\DOCS\<folder_name>\)  We discovered the problem and removed the second share and reconfigured the diskgroup platter paths back to \\<server_name>\OBDATA$\<folder_name>\   OnBase is now storing documents in the proper locations.  However, several documents that were uploaded while the second share was active cannot be retrived now.  The error message in Diagnostic Console is: FindlnldFile error: \\<server_name>\DOCS\<folder_name>\OnBase.ID [#FindlnldFile Factory:Get failed : "ID file not found"]

Anyone have a suggestion for a solution?

Steve

[ptam]

Steve,After reconfiguring your disk group platter paths you will need to recycle your OnBase Application Servers because these paths are cached in the App Servers. Please try that and see if it fixes the problem.Paul

[Stephen_Beck]

We have recycled the app server serveral times and the problem persists.

[Thomas_Nowakows]

Hello Steve,

You may want to double-check you updated the platter path in volume information for the volume and Disk Group that is indicated in the error message.  Perhaps you missed a Disk Group volume.

You may wish to reach out to your first line of support for assistance.

[Stephen_Beck]

Actually, Paul you are correct.  We went into IIS and recycled the application pools and that worked.

Thanks for your help

Steve