Technical Notes and Troubleshooting

This section contains technical notes and tips for troubleshooting the Signature Product Registration Application.

Any procedures covered in this section should be performed ONLY by authorized technical personnel, such as IT or WennSoft Consulting.

Technical Notes

About Registration Key Tables

The Signature Product Registration Application creates two tables in the system database.

• WSRegKey
  Created when the product is registered (using the Registration Key Setup application).
• WSRegistrationSettings
  Created upon initial installation and contains the location of the WSRegistration web service.

About WS SQL Database Users

Signature uses three SQL database users in a system capacity for Service Management and Job Cost.

• WSRegUser$Dynamics
  Created when enabling the registration keys. For more information, see Enable Signature Registration Keys.
• WSMPUser$Dynamics
  Created by Signature during the software installation. This SQL user is used internally for MapPoint integration.
• WSMiscUser$Dynamics
  Created by Signature during the software installation. This SQL user is used internally for document attachments to the SQL database.

Troubleshooting

Viewing Errors in the Web Service Event Viewer

Any errors relating to the Signature Product Registration Web Service appear in the Internet Information Services (IIS) Event Viewer. To access the Event Viewer.

1. Select Start > Control Panel > Administrative Tools > Event Viewer.
2. Select Signature.

Verify the SignatureRegistration Web Service is Installed and Working Correctly

After installing and enabling the registration key application, if you receive any errors relating to web services when logging into Microsoft Dynamics GP, follow the steps below to troubleshoot the problem.

1. Select Start > Control Panel > Administrative Tools > Internet Information Services (IIS).
2. Expand the server, then Web Sites, then Default Web Site.
3. Locate the virtual directory called SignatureRegistration, as shown below. 
   • Computer Name
     • Application Pools
     • Sites
       • Default Web Site
         • aspnet_client
         • SignatureRegistration
4. Right-click SignatureRegistration and select Properties.
5. Select the Virtual Directory tab, then select Configuration.
6. 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:
   1. Select Start > Run, then type "cmd" and select Open to open a DOS command window.
   2. Use the "cd" command to switch to the following folder: C:\windows\microsoft.net\framework\v2.0.50727
   3. Run the "aspnet_regiis -i" command.
7. When finished, open IIS again and verify that the additional .DLL files are present with the correct .NET version.

Verify the Registration Keys are Registered

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.

Verify the Web Service Location Match IIS

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).