...
- Choose Start > Control Panel > Administrative Tools > Internet Information Services (IIS).
- Expand the server, then Web Sites, then Default Web Site.
- Locate the virtual directory called SignatureRegistration, as shown below.
- Right-click SignatureRegistration and choose Properties.
- Select the Virtual Directory tab, then choose Configuration.
- Under Application Mappings, you should see 30 or more .DLL files listed, most referencing the string "2.0.50727." If there are several fewer than this, you need to run the following command from a DOS window:
- Choose Start > Run, then type "cmd" and choose Open to open a DOS command window.
- Use the "cd" command to switch to the following folder: C:\windows\microsoft.net\framework\v2.0.50727
- Run the "aspnet_regiis -i" command.
- When finished, open IIS again and verify that the additional .DLL files are present with the correct .NET version.
...
To verify that registration keys are registered, you can query the WSRegKey table:
- SuiteID
The suite the key belongs to. There can be many records in this table, but only one per SuiteId. - EncryptedKey
The actual key that gets decrypted. - Modified User
The user who is logged in when registering the key. - Modified Date
The system date when the key gets registered.
...
To verify that these match, query the WSRegistrationSettings table in the system database to see the value stored in that table, for example,
JASONE/WSRegistration
Next, go back into IIS and make sure the WSRegistration web service appears under the correct location (in our example, JASONE).
