LicenseWatch FAQ
System Administrator Guide
Choose subject below...

1. What Happens During Installation?
2. LicenseWatch Installation Prerequisites
3. Database Problems
4. Hardware and WMI Problems
5. Miscellaneous
6. Is IIS (Internet Information Server) Installed?
7. Is .NET Framework 1.1 Installed?
8. Is ASP.NET Registered Correctly in IIS?
9. Windows 2003: Is ASP.NET Allowed on the Server?
10. Does the Default Website Exist?
11. Paths to Data- and Log Files When Creating a Database on a Remote SQL Server
12. How should LicenseWatch connect to the SQL Server?
13. There is already an Instance of MSDE on the machine!
14. Moving the Database to a Different Server
15. How is the Client Launched?
16. Check if the LWClientRequestHandler website is running correctly
17. Is Client Packages Being Processed Correctly?
18. Does the User Have Write Privileges on the Local Machine?
19. Create a Test-Website on the Server
20. Why Does Clients Report Different Types of Hardware Information?
21. Some Clients can’t Scan Hardware / Installation of WMI
22. Why is there both a LicenseWatch and a LicenseWatchPlatinum Folder?
23. Resolving the ResolveIdentity Error
24. System Folder Aliases
25. What SQL Server Instances are installed on a Machine?
26. Manual Uninstallation of LicenseWatch
27. Problems with Windows Installer
28. Problems when Restoring the Database
29. Changing the License Code Directly in the Database
30. If the LicenseWatch client doesn’t start on Vista clients
31. Creating the LicenseWatch Database manually
32. Launching the LicenseWatch Client as a Service