My call to SMJobBless() is returning error 5 (kSMErrorToolNotValid), even though SMJobBlessUtil.py check doesn't find any problems. (It did initially, and I resolved them all)
SMJobBlessUtil checks a lot of stuff, including:
Code singing on app and tool, including checking designated requirements
info.plists refer to each other correctly
Label field in launchd.plist is correct
What else could cause it to fail?
OK, so it just turns out I was referring to my tool by the wrong name. So the "not valid" error can also mean "not found".
Related
My Software is writing to an ini file in c:\users...\documents and from time to time I get error reports from users where the WritePrivateProfileString call returns false and then GetLastError returns 2 (ERROR_FILE_NOT_FOUND).
I don't understand how this can happen and I wasn't able to reproduce it, since WritePrivateProfileString is supposed to create the file if it's missing.
If the directory didn't exist, the error would be ERROR_PATH_NOT_FOUND, if the file couldn't be created for permission reasons, it would be ERROR_ACCESS_DENIED.
So does anyone know why/when this function can produce this error? And how I can deal with it? As in: I rely on the file being created if necessary.
I think I may have found the answer myself.
The problem seems to occur when Windows Security -> Ransomware protection -> Controlled folder access is enabled and the application isn't white-listed.
ERROR_FILE_NOT_FOUND is a very confusing error message for this situation imho...
Might be a stupid question but hopefully not.
I'm due to launch my site in the next couple of days, and I am worried that there may be a couple bugs about, i've done the best to exterminate them but there may eventually be a couple that slip through the net, that i aint aware about.
I am wondering if it is possible, when an error does appear in codeigniter, instead of specifically saying what the error i can just set some text to be displayed like
"Error found, this has been sent to the website admin"
If you are using CodeIgniter 3, the error pages will be in application/views/errors/. There's different pages for database error, exception errors, php errors, and so on. You can remove the error message from these files and customize the page in any way you'd like. So for the errors/html/error_db, you'd just remove the line with <?php echo $message; ?>.
You can also disable displaying errors by setting the ENVIRONMENT constant to production and enable logging by changing the log_threshold in application/config/config.php.
I have searched the answers to similar questions asked about this SagePay error, and checked that the fixes don't appear to apply to my problem.
Specifically:
I am using a correct 2-letter country code for BillingCountry and DeliveryCountry.
I am POSTing VPSProtocol, TxType and Vendor as well as the Crypt value.
I have re-checked that I am using the correct encryption key from the MySagePay test portal.
Now I was using http://localhost:8084/app/success and http://localhost:8084/app/failure for my success and failure URLs, since I thought that although these are (obviously) not visible externally, it shouldn't matter since SagePay is re-directing at the end of its part of the transaction. (Is this assumption correct, or do these URLs need to be externally accessible?) Some of the answers have thrown doubt on this, so I changed them to an external website I own, and I still get the same error.
Another line of thought is that the client I am developing for has already gone live, and there seem to be hints that once you have gone live, you no longer have access to the test server (Is this true?)
Is there anything else I should be checking? (Additional info: I'm using the SagePay api (sagepay-api-1.2.2.0.jar and related libraries) to validate the form contents and encrypt them.
I used the integration from https://github.com/tolzhabayev/sagepayForm-php
I had this error (5080) and spoke to SagePay support and they guided me to the MySagePay portal where you can view Invalid transactions to be able to troubleshoot this error easily!
Hope this helps someone.
Chris Rickards
I had exact same problem and I tried everything that you described as well, one day after I found that the problem was in "VendorEMail" field, it had 2 email addresses separated by ;, once I removed second and left only one email everything worked.
We're using "burst_pdf" conversions and they have been working fine until recently.
However, since two days back all jobs fail, and looking at the Blitline dashboard we see that queued jobs fail with the following error:
"Image processing failed. comparison of String with 1.2 failed"
Also, the error messages say:
"Original Photo Metadata -> null", but I'm not sure if that's related to what's causing the errors.
The original submissiosn to the queue work just fine and we get a valid response back from Blitline. However, we no longer get any postbacks, even though I was expecting one even if a job fails (to notify us that an error occured)?
Have reached out to Blitline for help but haven't heard anything back yet.
Turns out this was due to a Blitline bug which has since been fixed.
I have just upgraded from kendoui.web.2013.1.514 to kendoui.web.2013.2.716 and have noticed that in the parts of the code where I require (through require.js) a certain kendo.culture.xx-XX.min.js file that also an unsuccessful request for kendo.core.min.js happens and I get an error in the console.
This did not happen with kendoui.web.2013.1.514 and I think this part inside the kendo.culture.xx-XX.min.js files might be to blame:
("function"==typeof define&&define.amd?define:function(e,n){return n()})(["../kendo.core.min"]
Also this reference to kendo.core appears to only be present in the minified versions. Note that I already have kendo.web.min.js fully loaded and the app works fine even with the invalid request so is this a bug?
If you are using the bundles (i.e. kendo.web.min.js) then you shouldn't use RequireJS to load them or any culture files.
I'm sorry that the documentation didn't mention it, I just added a section to explain this.