Cannot create a new group or apply a license in Symantec Mail Security for Domino
|Article:TECH94187|||||Created: 2009-01-26|||||Updated: 2012-01-25|||||Article URL http://www.symantec.com/docs/TECH94187|
No server names show in the server list for any group.
Symptom 1- If creating a new group you will not be able to assign a server to the group because there are none in the list to select from. If you try to save the new group anyway, it will say that you must add at least one server to the server group.
Symptom 2 - When there is no groups other than the unassigned servers group, you go into the unassigned servers group settings and see no servers in the servers list. You then proceed to Licensing and try to add a license file and get an error saying that you must add at least one server to the server group.
Without being able to see any servers in the lists you can not create new user groups or license the product.
Here is the pseudocode for how this area of our product works: 1. AllServers = all servers listed in the names.nsf file 2. UsedServers = all servers in sav.nsf assigned to any group other than unassigned servers group 3. AvailableSevers = AllServers - UsedServers As you can see we need proper access to be able to read the names.nsf file and the sav.nsf file because we create the AllServers list and the UsedServers list from both of these. By default Domino sets -Default - ACL for names.nsf as author access. Some customers change this to no access. The replication was created by reducing the level of ACL access to the administrator account for the sav.nsf and also the names.nsf. However, producing a similar situation by reducing the ACLs on the sav.nsf will generate more access errors when going into the settings. But if you give the administrator account full access on sav.nsf and make sure -Default- ACL on names.nsf is set to no access, the user does not belong to any of the groups that have access, etc. there will be no errors when just opening the sav.nsf and going into the unassigned servers group. You will not see an error unless you try to save a group or try to license the product.
Make sure that the user trying to administer our product has proper access minimally to the sav.nsf and to the names.nsf. I would recommend at least author access to names.nsf and full access to all of our databases. This is also means adding the roles for the users access on the savquar.nsf file.
Article URL http://www.symantec.com/docs/TECH94187