Reached maximum subscriptions per user limit for one of the users. The current configured limit is %1. The last user who reached this limit is %2. Use Dbanalyze or Snooper resource kit tools to see the complete list of users who reached this limit. Cause: A user has reached the configured limit for maximum subscriptions. Check the eventlog description for more information. Resolution: Please use server management tools to change the limit. Increasing the limit to a high value might have performance implications.
QoE Monitoring Server startup is pending as configuration database is not yet available. Cause: Possible local configuration ...
Reached maximum contacts per user limit for one of the users. The current configured limit is %1. The last user who reached ...
Reached maximum container members per user limit for one of the users. The current configured limit is %1. The last user ...
Reached maximum permissions per user limit for one of the users. The current configured limit is %1. The last user who reached ...
Reached maximum subscriptions per user limit for one of the users. The current configured limit is %1. The last user who ...
Reached the maximum category subscriptions per publisher limit for one of the users. The last user who reached the limit ...
Reason: {0}" & vbcrlf & "Description: {1}" & vbcrlf & vbcrlf & "Please refer to the Diagnostic Reports information below ...
Reason: {0}" & vbcrlf & "Description: {1}" & vbcrlf & vbcrlf & "Please refer to the Diagnostic Reports information below ...
Registrar backend store could not be prepared for first time use. Registrar store could not be prepared for first time use. ...