‎10-09-2009 09:18 AM
When trying to build an application I get the following error code:
Error 15 occurred at CodeSignAPI.lvlib:Get Signing Error String.vi
Possible reason(s):
Error: The Timestamp Authority URL specified does not point to a valid Timestamp Authority server, or an unknown error occurred.
Complete call chain:
CodeSignAPI.lvlib:Get Signing Error String.vi
CodeSignAPI.lvlib:Sign with Certificate.vi
AB_Application.lvclass:PostBuild.vi
AB_Engine_Build.vi
AB_Build_Invoke.vi
AB_Build_Invoke.vi.ProxyCaller
Any idea what a solution might be?
Solved! Go to Solution.
‎10-13-2009 03:02 AM - edited ‎10-13-2009 03:02 AM
Hi Rasmus,
Can you provide a bit more information on the system you are using? Operating System, LV version and Project file?
I presume you are using LV2009 and including a digital signature with your stand-alone application. If this is the case, please check your "Timestamp URL" in Application Properties-->Windows Security.
‎10-13-2009 03:18 AM
‎02-07-2013 05:55 AM
It solved my problem too, thanks!
‎12-18-2015 01:19 PM
What if I want to apply a signature. Then what do I enter for the URLs so it will build without crashing?
‎01-25-2016 04:11 PM
This is totally correct. I have the same problem on LV 2012, and uncheck the digital signature at the application property, the error was gone. Thanks.
‎01-29-2021 01:03 PM
Are you mental. I need code signing. Our system is restrictive and will not allow us to run these applications internally without the code signing. How about you tell me why is suddenly stops working after it had been working for months?
‎06-17-2021 04:57 AM
I also need code signing and get the same error.
‎06-17-2021 08:59 AM
It turned out the timestamp server I was using changed from a free service to a paid one, which is why it stopped working. When I switched to a different timestamp service, it started working again. For the record, I am now using http://timestamp.digicert.com.
‎06-17-2021 09:36 AM
I solved the problem also during the day. Was the same time server issue. Anyway i wouldn't classify this thread as solved when the main solution is to just not use the tool..