I have a functionality where i can copy the tokens which has some errors - clarion

Errorcode is 05 Access Denied/48 Unable to Log Transaction, this has come from RTL, not a custom function message, and only happens sometime when tokens are being fetched from database.
Everytime I trigger this function I use to get different error, what might be the reason, I have attached the screenshot but I wanted to know the root cause, why these errors are different everytime, would these be a TPS database related error.
Application is developed in Clarion 6.0 and compiled i n 8.0 and these issues don’t come up regulary, this errors are intermittent and occur at any stage, if it works smooth it doesn’t cause any issues but once issue pops up it will keep coming, any idea on these, do you think these is the code issue or can be a clarion custom error?
Files are on network drive and db is topspeed.PFA

Related

Powerapps to Azure SQL Server connection sudden error Bad Data source Inner exception, Not a valid data Source

I've been working with Powerapps for about 3 to 4 months now, and this particular app I've created connects to 3 tables in an Azure SQL Server Database. It's been working great until today. This morning I logged in to edit a feature on the app and my galleries were empty with an error message saying: "Bad Data source Inner exception, Not a valid data Source".
My first thought was, something is off on the database, some planned work possibly during the night, but that's not the case, and the DB is working perfectly as I also use it in PowerBI.
I googled for the error and found several people with a similar issue, and most of them reported that deleting the Data Source connections from power apps and adding them again would fix the issue, as well as deleting and creating the Galleries again. I've performed both actions, and the same error returns. I tried creating a fresh new canvas app, with a gallery and a brand new connection to the Azure Sql DB and still got the same error. I've also tried to restore one of the oldest versions of the app, and I still got the same error. This to me all indicates there's a problem with the DB, but...when I publish the APP, and run the app after publishing, It works perfectly, and I have full usability of the app, which means the connection to the DB is actually working.
It feels like a bug to me. I'll share the screenshot of the error:
Error Message
I'm worried I will lose all my work, so if someone could help me, that would be great.
Finally, I got the solution for this issue. This are the steps I followed to solve the issue.
Remove all the Database connectors from your app.
Go to File -> Settings -> Advanced Settings -> Disable enhanced Microsoft SQL Server Connector.
Add all your Database connectors back again.

Should an app be fully error free before publishing?

My app has been test running without crashes for some weeks now. However, in Logcat there are 3 persistent errors (lines marked with "E"). I do not know how to solve them, but they do not appear to harm the proper functioning of the app.
E/zygote64: Failed sending reply to debugger: Broken pipe
E/MemoryLeakMonitorManager: MemoryLeakMonitor.jar is not exist!
E/vndksupport: Could not load vendor/lib64/egl/libGLES_mali.so from sphal namespace: dlopen failed: library "vendor/lib64/egl/libGLES_mali.so" not found.
How usual is it for developers to publish apps (like on Google Play) that knowingly have errors in them that don't seem to be "mission critical"?
The google play console has a 'Bad beheivour treshold' of '1.09%'.
This is calculated by: 'Percentage of daily sessions during which your users experienced at least one crash. A daily session refers to a day during which your app was used.'
So you should aim to have a lower crash rate of 1.09%. There will always be bugs in your app that you haven't encountered yet in in your tests so an app will (almost) never be completely crash free. So a lot of developers publish their apps while there are still (mostly unknown) error's in them.
Sadly enough I can't help you with your exact errors but I hope I have helped you with the Google Play Console Guidelines.

"Error: 'sessionAsSigner' not found" after Firefox updated to ver 28.0

Using sessionAsSigner in SSJS which worked fine until Firefox updated itself to version 28.0
Now get this error: "Error: 'sessionAsSigner' not found"
Still works in Internet Explorer 9.0
Anyone else experienced this and/or know how to resolve it?
I faced this when My xPage/CustomControl and attached ScriptLibrary are signed with different signers.
Resigning the database with server ID and re-building the application fixed the issue.
'sessionAsSigner' works fine now.
I think the browser update was a red herring.
If you get this error every time the code has run then you should ensure all design elements are signed with the same ID. Clean (Project -> Clean) the database if errors continue. I have found that sometimes 2 cleans are needed to resolve this (and other strange xPage issues).
However, I found that even after this has been done a user can still get this error randomly. When the user runs the code a second time it usually runs without error.
I would appreciate anyone's insight into why this could occur randomly.

MOSS 404 errors for some users on certain sites, sometimes

Everything works fine for most accounts 100% of the time but here and there some users who are able to access a subsite fine one day are greeted with a standard 404 the next. This can last for an hour or two days, it's really inconsistent.
I check the iis logs and it says the status is also a 404 for these requests, nothing else looks unusual. Sharepoint logs have nothing for the timestamps either.
Correct me if I am wrong but if it was a permission issue an access denied message would be shown.
It is not the individual computer because when a user is having this problem and I can log in with their account and I also get the 404 error although I am on the exact site with another account in another browser at exactly the same time, and it works perfect.
Any suggestions would be greatly appreciated, I've done a fair amount of searching but can not find a similar situation or help anywhere.
Since the information is very strict at the moment, I will throw a few questions that might lead you towards the problem.
Are we on a loading balance setup? The intermittent 404 might be cause by one of the servers Web FrontEnds not correctly serving requests.
Are we running out of disk space in the SQL Server machine? This might cause it
Are the blogcache or site caches enabled? Some routines may break them
Do we have Anti-Virus on the server? (it HAS to be asked :p)
We get very high packet loss between the servers? (The error would be different though)
Something that might occur very often is when you have, say, custom code a DLL on the GAC or the bin folder, and since you could be on loading balance the second server does not have this DLL in its own GAC or BIN folder. Sharepoint usually raises 404s when assemblies are not found too, not only requests.
This seems like a longshot, but... could those SharePoint sites be throwing a 404 HttpException? It seems like you'd see that in the SharePoint logs, too, so it's even more unlikely.
At any rate, is your SharePoint logging level set to an appropriately verbose level to debug weird stuff like this?
Are people checking in & publishing master page changes when new CSS files and/or other includes (script files, etc.) are not yet published at all? I've seen this cause a 404 a few times when users forget to check before they publish.
I have had to write custom code within a SharePoint context and I had those 404 errors as well. The solution, in my case, was to ensure that the block of code executing had these 2 conditions met:
1) Run with elevated privileges, regardless of the fact that it is a 404 this was part of the solution.
2) web.AllowUnsafeUpdates = true; This line of code needed to be added even though it was wrapped within an elevated privileges block.
Once these were added the issue did not occur. This was happening on both load and non-load balanced environments.
This reminds me of a strange asp.net bug that I had a few months back.
It was caused by a patch that had been applied (to the framework if I remember correctly)
try downloading this Windows update list tool and have a look at what has changed since the problem started.
I concede that if there was a problem with a patch then its more likely that it would be a consistent error, but it's worth a look.
It was a permission issue, I had figured this out awhile back but basically a few accounts were not setup properly and could not load a fresh copy of the page, when someone else would hit it they would be able to view the cached page fine. Error was never thrown as a permission issue or access denied anywhere but this is what fixed the problem.

Problem with Starteam and Cruise Control.Net

Does anyone have problem getting files from starteam using the cruise control tool for setting up automatic build job??
The script seems to run fine but fail after some time with the error message
Error occurred:
Unable to read data from the network: the connection to the StarTeam server has been lost.
I am not sure whether the problem is the way our Starteam server has been setup, we have 4 licenses shared across the team and the server automatically logs people out if it detects inactivity for a period of time
I've got StarTeam working with cruise control.net so I can tell you that it works, but its a pain, especially the fact that starteam won't remove deleted files from working directories on its own.
I've seen that error once before, but If I remember right, it had to do with an IPSec configuration problem and was immediate, not after a delay. Is the amount of time it takes to fail shorter/longer/same as the timeout for inactivity? Are any/all/none of your source files making it into the working directory before it fails?

Resources