Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 203 Source: LicenseService

The user data could not be saved.
This event occured when upgrading a SBS2003 server to SP1. Reseting license logging service, as described in ME883399, solved the problem.
See ME824196 for a description of the License Logging Service in Windows Server Operating Systems.

ME153140 and ME194065 show how to reset License Manager information.
I received this error when attempting to use replication with SQL 7.0. It appears that the install of SQL7 skipped the screen to allow input of the proper license info. So, by default, SQL licensing was set to per client and the default number is zero licenses. Thus, during replication a check in SQL was finding no licenses available and logging the error in Windows.
This event indicates that changes to the user information could not be saved. The License Logging service may be able to successfully save the data later. If not, the data will be lost. Data that is replicated from other servers will be received again during the next replication. Data entered on this server will have to be re-entered.

Also this error seems to occur when the system doesn't have adequate privileges to the system disk.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.