Accepted Solutions
This is a typical error for failure. You likely also have an error indicating that indicates Object reference not set to an instance of an object.
There are many considerations to determine the area of the misconfiguration or lacking permission. First since you have the log open let us consider a few prerequisites. The Webservice must be installed and deployed on every server in the sharepoint farm at the same version of the client that is attempting to scan the webapp. You will see entries as below , please confirm they match each other.
Client version: 3.1.9.003
Webservice version: 3.1.9.003
You also need to point the scanner to the webapp and not a website or a list in the webapp for scanning. You will have the choice on whether to include the particular sites or lists under a monitored share once it is configured. BUT you must use the webapp as point of entry and have the appropriate SharePoint credentials as documented in the guides to traverse the webapp to discover the sites and all objects within.
Since your error is on discovery (this happens before we scan the objects for metadata, or audit for access events by reading the SharePoint audit logs) my first inclination would be to verify you have added a proper webapp your credentials have adequate permissions for.
For a table and explanation of the required parameters change the <MS_Name> to your console server in a browser that can reach the Webserver for the console.
https://<MS_Name>/symhelp/CS.do?ProdId=SDISYMHELPV_40&vid=sdi_task_add_edit_webapp
A proper formatted Webapp looks like the address to the SharePoint server
Versus the URL to a site
Please check that yours is configured correctly.
If I have left further questions to your query please reply with further information such as the Symantec DataInsight (SDI) version deployed or feel free to initiate a Symantec Technical Support Case for dealing directly with your log and context of the entries the inquiry is based upon for further explanation.
Rod
This is a typical error for failure. You likely also have an error indicating that indicates Object reference not set to an instance of an object.
There are many considerations to determine the area of the misconfiguration or lacking permission. First since you have the log open let us consider a few prerequisites. The Webservice must be installed and deployed on every server in the sharepoint farm at the same version of the client that is attempting to scan the webapp. You will see entries as below , please confirm they match each other.
Client version: 3.1.9.003
Webservice version: 3.1.9.003
You also need to point the scanner to the webapp and not a website or a list in the webapp for scanning. You will have the choice on whether to include the particular sites or lists under a monitored share once it is configured. BUT you must use the webapp as point of entry and have the appropriate SharePoint credentials as documented in the guides to traverse the webapp to discover the sites and all objects within.
Since your error is on discovery (this happens before we scan the objects for metadata, or audit for access events by reading the SharePoint audit logs) my first inclination would be to verify you have added a proper webapp your credentials have adequate permissions for.
For a table and explanation of the required parameters change the <MS_Name> to your console server in a browser that can reach the Webserver for the console.
https://<MS_Name>/symhelp/CS.do?ProdId=SDISYMHELPV_40&vid=sdi_task_add_edit_webapp
A proper formatted Webapp looks like the address to the SharePoint server
Versus the URL to a site
Please check that yours is configured correctly.
If I have left further questions to your query please reply with further information such as the Symantec DataInsight (SDI) version deployed or feel free to initiate a Symantec Technical Support Case for dealing directly with your log and context of the entries the inquiry is based upon for further explanation.
Rod
