We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
I use WinXP and Acrobat 9 Standard version 9.3.4. I'm signing 50 - 100 documets per day. Security with smartcard / Infineon SICRYPT. Sometimes, not every day, I get the error message number 2148073504. Then I must close Acrobat and wait some time. After waiting time the digital signing is possible again. I read that Adobe solved the problem with the last update, but the problem persists.
Sometimes I have to start and close Acrobat several times until signing is possible again.
Does somebody have an idea how to avoid the error?
I get the same error sometimes.
Win7 64 Bit
ReinerSCT cyber Jack
D-Trust SiG Card with Cert (German law approved)
Nexus Personal 4.16
Open PDF - assign Signature - Acrobat ask for Cert - then the error 2148073504.
Close Acrobat - wait 1-2 Minutes .... it runs .... sometimes .... restart PC ..... sometimes.
I have even the same problem:
my machine: XP Pro
nexus personal 4.5.1
siemens cardOS M4.3
Acrobat Adobe 9.3.2
This error makes me crazy, but I need the digital signing funktion. And no solution, I cant believe it.
Hey where are you, adobe support?
My problem still persists. I will try Acrobat 10 next week and Win 7 instead of XP. Perhaps that will solve my problem.
I have, maybe a solution. The plan is to break the connection between Nexus Personal<->Windows Cryptographic Service Provider<->Acrobat. You have to register the Nexus Modul direct in Adobe Acrobat. You can see it in my screenshot. Sorry, for the wrong language. I hope it will works for you.
Thanks for your solution, kohibu, but my Infineon Sicrypt smartcard doesn't have PKCS#11. So I'm not able to register it in Acrobat.
By the way: Language is no problem, because I'm located in Germany.
Fool If you think it's over. Well known error last friday. I can't believe it.
Aswer is wrong. It works. See my last Post.
the error still alive also in 9.4.2.
Open PDF - sign - error 2148073504 - close PDF - wait - Open - error - close - ... - open - SIGNING 🙂
I think the problem is the Windows crypt API.
Has anyone the same problem with PKCS#11 directly attached?
(With directly attach you will also get SHA256 and no fallback to SHA1)
see my Post from Mar 18, 2011, it works for me. But pay attention to choose the right signature. Not the signature stored in the windows certification store! Only the signature from the SmartCard. (directly attached with personal.dll)
I have a client with a similar issue. I cannot import a personal.dll(PKCS#11) , i am blocked in IE from exporting that cert. I can get a .p12 key. Will this also work.
I also have a Windows Digital ID. How can I tell Adobe to use the Digital Files and not the Windows Digital ID.
Thanks for your help.
If you have ePass2003 uninstall it ..
again re install ePass2003 while selecting CSP
make sure you have selected MicrosoftCSP
then continue installation
then error should not come