| | | Forum Member
       
Group: Forum Members Last Login: 12/11/2008 9:10:13 AM Posts: 36, Visits: 81 |
| | We just upgraded to Point 5.3 and PDS 5.3 this past weekend. I have gotten several complaints today from people who save a file, then when they try to go back in, get the message about the file being reserved by themself, and would they want to open it read-only. Has anyone else run into this? One thing I wonder about... when I finished the upgrade, the PDS Organization Security Key had been set back to the default value, so I had to go to the PDS Admin page, to Configuration, Parameters to change it. I see there is a field in there called Reservations which is currently set at 30 minutes time out. I am wondering if we had changed that to a shorter amount and it got reset back to 30 when we did the upgrade. What do others have this value set at? Is it okay to try lowering it? Thank you, Steve |
| | | | Forum Member
       
Group: Forum Members Last Login: 12/11/2008 9:10:13 AM Posts: 36, Visits: 81 |
| | Just thought I would let everyone know what the fix was on this one. I ended up calling tech support; we had done some Windows Updates on this server, as well, and it turns out ones of the updates messed up some file permissions on the Point Data Server. Thanks to Greg at tech support for his help! Here is the article which shows how to reset permissions properly: http://messageboard.calyxsupport.com/Topic2215-19-1.aspx |
| | | | 
www.ehuna.org
       
Group: Administrators Last Login: 12/17/2008 10:36:11 PM Posts: 258, Visits: 13,336 |
| | Steve, thanks for following up and telling everyone what was the fix. Just one remark: with PDS 5.3, the Configuration Wizard now contains a tool to reset NTFS permissions. Instead of manually using the table you linked to, this tool resets the permissions for you. You can read more about it at: Q10777 - INFO: (v5.3) Chapter 4 - PDS Configuration Wizard http://pdskb.calyxsoftware.com/article.aspx?id=10777 Scroll down to the "Reset NTFS Permissions screen" section.
Disclaimer: this post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post. |
| |
|
|