Hi,
Every now and then I check the "Query Logs" it took a while to understand the "error" message and I think that every time the application is started the Browser tries to do "something" under the "quest" account.
This results into an error by trying to create / update an index.
Is this a right assumption or do I have to make an alteration in one of the Application settings?
I don't use quest accounts.
Ron
Query Logs
Re: Query Logs
Hi Ron,
that behaviour sounds very strange. Do you have any custom code that runs once the application is started via the browser? I do not see any of this type on my applications, so I would assume that there must be something different.
best
that behaviour sounds very strange. Do you have any custom code that runs once the application is started via the browser? I do not see any of this type on my applications, so I would assume that there must be something different.
best
Any help offered comes with the best of intentions. Use it at your own risk. In any case, please make a backup of your existing environment before applying any changes.
Re: Query Logs
Hi,
just a quick note.
I have created a view with the name of an AG internal table. I notice the same (sometimes), when e.g. AG (or my code?) tries to create an index on that - which of course does not work for a view.
Why I have a view that's named like an AG table is easy to explain: This way I can use the contents as a lookup field in a different table. Unfortunately this is not possible directly from AG.
Olaf
just a quick note.
I have created a view with the name of an AG internal table. I notice the same (sometimes), when e.g. AG (or my code?) tries to create an index on that - which of course does not work for a view.
Why I have a view that's named like an AG table is easy to explain: This way I can use the contents as a lookup field in a different table. Unfortunately this is not possible directly from AG.
Olaf
Some postings I was involved, you might find useful:
Multi Path Upload (MPU) / dynamic upload folder; SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button
Multi Path Upload (MPU) / dynamic upload folder; SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button
Re: Query Logs
Hi Gents,
I'm still searching. This application started in 2012 en I've always updated the versions.
I have 2 more application and they don't cope with this issue.
Is it possible that some old coding still sucks somewhere?
Ron
I'm still searching. This application started in 2012 en I've always updated the versions.
I have 2 more application and they don't cope with this issue.
Is it possible that some old coding still sucks somewhere?
Ron
Re: Query Logs
Hi Ron,
as you say, the other do not have the issue, so it is most likely that some custom code is causing this.
as you say, the other do not have the issue, so it is most likely that some custom code is causing this.
Any help offered comes with the best of intentions. Use it at your own risk. In any case, please make a backup of your existing environment before applying any changes.
Re: Query Logs
Having a view with the same name as an internal table could cause unpredictable conflicts. But anyway one thing to check: Admin area > Utilities menu > View/rebuild fields. From that page, scroll down the to the membership_userpermissions table and take a screenshot of what you see there. My doubt is that it could reveal some comparison bug the app is doing that could need a fix.
Re: Query Logs
Hi Ron,
are you using any hooks?
For me it seems strange - like pbotcher said. The question remains why this happens. Does it only occur with the "guests" account?
are you using any hooks?
For me it seems strange - like pbotcher said. The question remains why this happens. Does it only occur with the "guests" account?
Some postings I was involved, you might find useful:
Multi Path Upload (MPU) / dynamic upload folder; SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button
Multi Path Upload (MPU) / dynamic upload folder; SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button
