Archive for February, 2011

Installing Digital Signature Control for Web Based Infopath Forms (Digital Signature)

February 8, 2011 1 comment

When creating a web based infopath form with Digital Signature enabled and uploading it into a SharePoint document library users might be prompted to Install the Digital Signature Control when they click “New” to create a new Infopath form.

When clicking “Yes”  users might be prompted with the Microsoft Software License Terms Agreement:

By clicking the checkbox next to “I Accept the terms in the License Agreement” and clicking “Next” users might experience that nothing else happens.  It seems as if the License Agreement just hangs there.

This is usually due to two Active-X .DLL files that are missing on the client workstation to allow for digital signatures.  The Active-X DLL files needed are (DSigCtrl.dll & DSigRes.dll).  These DLL files will need to be copy and then registered in the “windows\system32” directory on the client workstations.

You can find these two .dll files packaged in two .cab files on the SharePoint server in the 12 hive TEMPLATES\LAYOUT\1033 directory.  Location:  “c:\program files\common files\microsoft shared\web server extensions\12\TEMPLATES\LAYOUT\1033

1.  Copy the two .cab files ( & to your local workstation.
2.  Extract the contents of  the .cab files
3.   Copy the two .DLL files from the .cab files (DSigCtrl.dll & DSigRes.dll) to the local “c:\windows\system32” directory
4.  Next open up a command prompt window (with Administrator privilages) and change directory to the “windows\system32” directory

5.  Next run these two commands, one right after each other:  regsvr32 DSigCtrl.dll and then regsvr32 DSigRes.dll
6.  If  the DLL files were registered succesfully you will see the messages:  “DllRegisterServer in DSigCtrl.dll succeeded” and “DllRegisterServer in DSigRes.dll succeeded
7.  Now try to create a new Infopath form in SharePoint.  Users should now not be prompted to Install the Digital Signature Control and will not be required to agree to a license agreement.

If these DLL need to be deployed to many workstations, a vbscript can be created and then deployed via GPO push.