Ninox hanging, not letting me edit and very slow
Hi guys, since yesterday I have not been able to work on my ninox db as it is hanging and going into a readonly mode. The order of events is as follows:
- Yesterday,for the first time as I needed names of some fields for coding, during my live testing I had both browser and Ninox app opened together. Made some changes in browser, but after about 2nd save or so, db hangs. Closed everything and rebooted. However, same thing; the db app just would hang (See attached).
- I even updated my app to the latest version incase there is something missing. However, same thing.
- After searching through the forum, I came across https://forum.ninox.com/t/x2y67wv/since-latest-upgrade-i-cant-do-anything I have cleared the cache twice and also used the terminal to run the command twice, but now after about 2nd save or so, db goes into readonly mode. After very long time, it allows you 1 click and on the second click it goes into readonly mode again.
The internet connection is good, everything else is working fine. Can't think of anything else. So far, the test user is not getting this issue. Only myself.
Can anyone please help. I finally have my db for live testing and now I am unable to work on it. Can't understand this lagging.
9 replies
-
Yesterday I was getting a lot of server taking longer than expected issues. Today it seems better
-
Alan. On the rare occasion I get this - I moan at Ninox to KICK their server and when they do all seems fine
Are you also aware that in part you can now do this yourself?
Go into stacked disk image
Select view on active background processes
This will show you running processes
Select Restart at bottom of the form
Certainly helpw when i have run a "do as server based script and is dleletin many old images etc..
OR worse still I have the loop wrong and it sends their server into a client /server spin !!!
-
Hi All, my apologies for the delay in responding but I was having trouble signing into the forum. So far, I have uninstalled, reinstalled, cleared the cache and used the terminal command and more; but nothing worked. I had to stop my test users from using it, and my deadline has already been pushed by 2 weeks. This issue is now with the third tier of support and I am so hoping to get this fixed (fingers crossed).
Content aside
- Status Answered
- 4 mths agoLast active
- 9Replies
- 121Views
-
4
Following