Forum Discussion
Hi Mike,
Is UTF-8 enabled? If it is, disable it and try again. I have had this happen and this was the cause. Let us know what happens.
Regards,
Jim Harrison
------------------------------
Jim Harrison
transparency = knowledge + understanding : The Scrum Dudes
------------------------------
- MikeTamoush2 years agoQrew Commander
Good thought. I checked, and it was already disabled. The user logged in with her personal computer, and had no issues. And no other users are having issues. Seems to be related to the computer, but for the life of me I can not understand how a computer could have an issue, but only with one app. The whole situation doesn't make any sense to me....
If it is a computer related issue, I would expect it to have trouble with Quickbase in general, not limited to 1 app.
If it was a QB issue, I would expect other users to have the problem.
------------------------------
Mike Tamoush
------------------------------- MarkShnier__You2 years agoQrew Legend
I would try having the user update their browser to the current version and also try a different Browser (Chrome vs Firefox)
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
- MikeTamoush2 years agoQrew Commander
Tried Chrome, Firefox, and Private Browsing in Firefox. Deleted 7 days worth of cached data, but the next try will be completely clearing the cache (had avoided that because its a pain, but we will clear the cache in the browser the user doesnt usually use). However, since we tried in multiple browsers, I am not optimistic it is a caching issue. Good thought updating browsers, will try that. Since we tried multiple, also not optimistic but willing to try anything!
------------------------------
Mike Tamoush
------------------------------ - MikeTamoush2 years agoQrew Commander
Update: IT believes it may have to do with the antivirus software. They have not come up with a solve. I am also curious as to why it is only happening with one user then....will post back if I get more info.
------------------------------
Mike Tamoush
------------------------------- JimHarrison2 years agoQrew Champion
Hi Mike,
I had a problem in one App only where I would log in and could not expand Reports and Charts or view table properties but instead would see a blank screen. I am a Realm Admin so this should not be the case. Other Realm Admins were not experiencing the problem. Even Quickbase Support didn't understand what was happening. I got on a Zoom call and recorded it with Elvis.
Then I turned UTF-8 off and everything worked. I performed an API_GetSchema with UTF-8 enabled and found there were special characters in some multi-choice fields. As soon as I cleared those the problem went away.
Is it possible there is a multi-choice field with a special character in it?
I don't know why this would happen to one user but this is very similar to what I experienced last week. Also QB is releasing a UTF-8 update this week so there has been some recent work done with character encoding.
Easiest way I have found to check is to use Postman and send API_GetSchema and then read through the response. By enabling UTF-8 before sending the request, all the bad characters will come back as black diamonds with white question marks.
"The replacement character , a black diamond with a white question mark, is a symbol found in the Unicode standard at codepoint U+FFFD in the Specials table. It is used to replace an unknown or unrepresentable character, or indicate problems when a system is not able to render a stream of data to a correct symbol."
If IT finds the AV isn't the problem give that a shot.
------------------------------
Jim Harrison
transparency = knowledge + understanding : The Scrum Dudes
------------------------------- MikeTamoush2 years agoQrew Commander
Hmm, interesting Jim. I don't have UTF-8 on but the fact that you had the same behavior and only in one app certainly sounds like more than a coincidence. Our problem suddenly fixed itself and it has made myself and IT even more confused.
It very much seemed to be linked to the anti-virus. They would turn it off and it would work, turn it back on and they got the error. The uninstalled and reinstalled the anti-virus, but that didn't solve anything. I am running the same AV version, and have no issues, and no one else in the company is having issues, so that made it more confusing (if it was the AV, why isnt it happening for anyone else?). But there at least seemed to be a very clear link between the AV and the issue.
IT was going to work on it some more today, and boom. It was just working today without issue.
No idea what happened or how it fixed itself.
------------------------------
Mike Tamoush
------------------------------