Recursos para Profesionales de TI >
Página principal de foros
>
Forefront Security for SharePoint
>
Manual Scan not showing sharepoint sites
Manual Scan not showing sharepoint sites
- I have 2 web front ends, 1 app server(doing index and search, this server has central admin on it) and the sql server cluster. All are moss 2007 sp1, windows server 2008 x64
I did a full install on forefront for sharepoint on the web servers, and just the admin console on the app server.
When i click manual scan, it shows the computername:port for central admin on the app server.
When i start a manual scan, it takes 20 seconds and scans no documents.
Do i have to do a full install on the app server as well?
on my testing server, which is just 1 server(has moss, sql, etc) the sharepoint sites show on the manual scan window.
thanks for the help
Respuestas
- I found the problem!!!!
The sharepoint sites within IIS were renamed different than the names sharepoint originally gave them. Changed them back and manual scan is working.- Marcado como respuestawvrider martes, 04 de agosto de 2009 19:54
Todas las respuestas
- Hi wvrider,
Try connecting the Administrator console to one of the frontend web servers (not sure if you are doing this). You should be able to see all of the site collections under OPERATE>Run Job>Manual Scan then. It is not necessary to install FSSP on the Application Server, no.
Kind Regards,
Andy Day
CSS Security, Sr. Support Engineer (Antigen/Forefront Server Security) - thanks andy for the reply. I lost a couple of my bookmarks when i was cleaning them up.
I open the admin console on the web servers and it gives the same error, it does not enumerate the sites like it does on my single testing server(single server running moss, sql).
I have spoke with our microsoft rep and he said he is going to escallate, but have not heard anything else.
I figure a use of a forum is good as I can't imagine we are the only one with the problem and that the information is out there for people when they do have an issue.
Thanks - Hi wvrider,
It would indeed be useful to give a solution to this on the forum, however I don't have one for you at present. I do not know of any similar cases and we would need a deeper analysis of you installation to find out where the problem lies (i.e. through a support case).
Having said that, you may find some indication of the cause in the ForefrontInstall.log file (in the C:\ root), or in ProgramLog.txt (in the %Program Files (x86)%\Forefront Server Security\Sharepoint\Data folder).
Kind Regards, Andy Day | CSS Security, Sr. Support Engineer (Antigen/Forefront Server Security) - whoops, i posted this using my other account, i am wvrider as well.
we finally have microsoft moving on this, two of their guys(so hopefully within a week or so we can get an answer). Last monday just ran the fscdiag.exe and forwarded over.
I will definately post the solution here.
I was just out for some reading and ran across two phrases that seem a bit confusing to me on the domain account required for forefront.
Here are the general information on the account (our account for forefront followed this as it was part of the technet article i was using at time of install):
Enter the account to be used for remote SharePoint database access. This account must be a member of the local Administrators group on which SharePoint Portal Server is installed (one who is a local administrator on the Web server or who has System Administrator rights on the database server). The user name must be entered in the following format:<domain or server name\user name>
and then i found this: -from here(http://technet.microsoft.com/en-us/library/bb795167.aspx)
FSSPController
FSSPController is the agent responsible for communicating with the SharePoint SQL Server™ databases. This service runs under the account used by the SharePoint Administration service. You will be requested to enter the account information during the install process.
On our production servers in question, the account for forefront is different than the sharepoint admin service is running under (as we are using sql authentication), the dev server that works is the one and the same account.
Would this cause the problem? Well either way, i'll post back what microsoft says.- Editadobarmatt80 viernes, 31 de julio de 2009 1:06
Instructed by microsoft, i uninstalled forefront and reinstall forefront with sp3 and forwarded over output from the fscdiag.exe command. They report no reason the enumeration of sites and manual scan should not be working. They are in the moment to build a test environment using sql authentication to reproduce.
I'll keep it updated.- I found the problem!!!!
The sharepoint sites within IIS were renamed different than the names sharepoint originally gave them. Changed them back and manual scan is working.- Marcado como respuestawvrider martes, 04 de agosto de 2009 19:54
