%11Notification Server on %1 failed to connect to the site database %2.%12 Possible cause: Notification Server failed to connect to the site database. Possible causes: 1. The network is temporally unavailable. 2. Firewall misconfiguration. 3. Authentication issues. Verify that the site database is up and running. To help identify the problem, see the bgbserver.log on the management point %3.%0
Note: To ensure the highest level of functionality and compatibility, it is recommended that you make sure this location ...
NOTE: Uninstalling this secondary site will not remove it from its parent site hierarchy. You must manually delete this secondary ...
Note: You can use the same alternate path to install multiple sites. Always verify that the alternate path contains the most ...
Notification Manager failed to initialize.%12 Possible cause: Failed to initialize with error code %1. To help identify the ...
Notification Server on %1 failed to connect to the site database %2.%12 Possible cause: Notification Server failed to connect ...
Notification Server on %1 failed to initialize the TCP listener on port %2.%12 Possible cause: TCP port %3 might be in use ...
Notification Server on %1 failed to initialize.%12 Possible cause: Failed to initialize with error code %2. To help identify ...
Number of corrupt .SVF files received by SMS_STATUS_MANAGER via the Status Manager inbox since SMS_STATUS_MANAGER was last ...
Number of status messages replicated at high priority by SMS_STATUS_MANAGER to the parent site since SMS_STATUS_MANAGER was ...