2011-09-29 02:20 AM - edited 2015-12-18 01:24 AM
I am getting an irritating issue when configuring SnapManager for SharePoint in a farm. I was hoping someone could point me in the right direction?
Here is my setup:
SharePoint 2010 Farm:
Sp-web1 and Sp-web2 are a both Web Front Ends.
Sp-app1 is a SharePoint Search/Indexer and Office application server.
Sp-SQL1 is the database server.
Sp-SQL1 has Snap Manager for SQL (not configured yet) and the SharePoint Media and Manager Roles. It also has the SnapManager agent running as a SMMOSS Member Agent.
All other servers have the SMMOSS agent installed.
All agents are showing in the Management console, but I am not able to change any options as they are greyed out. I think this is because I haven’t installed any agents as ‘SMMOSS Control Agent’. This should be applied on the web front ends, but it doesn’t let me .
The snap drive service account has Farm Administrative and Local Admin rights across the farm.
When looking in the event log, I am getting a couple of 'Informational Errors':
smmoss,0.0 [agent version=126.96.36.199]
non sharepoint or get farmname error: system.nullreferenceexception: object reference not set to an instance of an object.
get total memory size is fail.system.management.managementexception: invalid class
at system.management.managementexception.throwwithextendedinfo(managementstatus errorcode)
2011-09-29 04:08 AM
I have checked the permissions and the service account (Agent Run-As) has sysadmin across the SQL Server. Is this correct?
The account is also local administrator across the board.
2011-09-29 05:07 AM
Actually there is some place within the SQLDB Admin Tools, where one can manage access to the data within SQL. Thats where it needs access too. I'm not a SQL Admin, but had them do this a couple of times in the last years...
Hope this helps.
2011-09-29 06:11 AM
Thanks Peter. I have now checked all ther permissions on both SQL and Windows (the SQL permissions you talk about are 'View Server State' at the server level, and it must also be mapped as DB_Owner on all databases). However, I am still getting the issue where it cannot detect any sharepoint configuration. I have narrowed this down to not having a Control Agent installed anywhere on the farm (it wont let me choose that option).
Is there anything else you can think of that may be stopping me from choosing this option during the Agent Installation?
If any one else is wondering what permissions are required across Windows/SQL, they should be:
Local Administrator on all servers where a SMSPagent is installed - where a group policy with restrictive settings isinstalled, check the local security policy for each server (Run >gpedit.msc > Windows Settings > Security Settings > Local Policies> User Rights Assignment) and ensure the following permissions:
SharePoint Central Admin
SQL Server Mgmt Studio
2011-09-29 06:54 AM
Yes, if you have no Control Agent, this error is normal.
1. downloaded the "**_Agent.exe" from NOW?
2. installed this agent package on the WebFrontend Server?
PS thanks for the access overview!
2011-09-29 06:57 AM
I have manually install SMMOSS50_Agent.exe on all front ends. I am able to validate the connection to the SMMOSS manager, but when asked to choose the Agent Type, both options Member and Control Agent are greyed out.
2011-09-29 07:16 AM
I will try and use another port. I am able to Telnet to all the ports outlined in https://kb.netapp.com/support/index?page=content&id=2014035, which would suggest the ports and open and are not conflicting.
Here is my Agent configuration (with names and IPs removed). It is as though the application can't detect Sharpoint is installed. Does the application only search the default install path (C:\Program Files\Sharepoint)? I have install Sharepoint to a seperate drive.