Support Forums - View Thread

View Thread

The following is the text of the current message along with any replies.

Messages 1 to 4 of 4 total

Fri, Jun 13 2014 7:57 AM	Permanent Link
Roy Lambert NLH Associates Team Elevate	Anyone know what can make the configuration file go read only? I just tried to EMPTY TABLE to receive a 403 error. Shut 3 PCs down, restarted and things now back to normal. Roy Lambert
Fri, Jun 13 2014 9:01 AM	Permanent Link
Raul Team Elevate	On 6/13/2014 7:57 AM, Roy Lambert wrote: > Anyone know what can make the configuration file go read only? I just tried to EMPTY TABLE to receive a 403 error. Shut 3 PCs down, restarted and things now back to normal. Nope. Are you saying after reboot it went back to normal (read/write) ? Only times i've seen funny things happen to file permissions is due to anti-virus app or if for some reason file is created in a temp folder and then moved over to working folder and it then retains the (incorrect) permissions from temp folder. However i can't ever recall read-only being reset after reboot so i'm thinking it's something interfering with the file (like AV). Raul
Fri, Jun 13 2014 9:52 AM	Permanent Link
Roy Lambert NLH Associates Team Elevate	Raul >Nope. Are you saying after reboot it went back to normal (read/write) ? Exactly that >Only times i've seen funny things happen to file permissions is due to >anti-virus app or if for some reason file is created in a temp folder >and then moved over to working folder and it then retains the >(incorrect) permissions from temp folder. > >However i can't ever recall read-only being reset after reboot so i'm >thinking it's something interfering with the file (like AV). Could be - or could be the LAN playing silly buggers or something. My first thought was "oh 2.17b1 has a new feature so I can't empty a table without it being exclusive" then I read the error message and thought WTF Roy
Fri, Jun 13 2014 11:33 AM	Permanent Link
Raul Team Elevate	Roy, << Could be - or could be the LAN playing silly buggers or something. My first thought was "oh 2.17b1 has a new feature so I can't empty a table without it being exclusive" then I read the error message and thought WTF >> Assuming you were not executing the "empty table" in the context of configuration db which would cause this error also i'd say maybe your lan did have an hiccup or this is just one of those file share issues that seem to be more and more common with newer OS's. Raul