Can someone help me with stsadm command to add user as site collection admin?
View Complete Post
I am having moss2007 production server.I am taking backup of site using command. My command is
C:/Program files/common files/Microsoft shared/Web Server Extension/12/BIN/stsadm -o backup -url http://fsplintranet/ -filename \\192.168.0.56\image\backup.dat
When i run this command backup process starts, but after some time it terminates. Showing error is:
Action cannot be completed, Please try again.
Please suggest how to complete this backup.
Thanks in advance.
Usage analysis processing is enable for my farm in both Central Administration and in the SSP.
I've checked TImer Job Status and the three timer jobs responsible for doing the log analsis are all running.
I've also checked the log file locations and the log files are being generated.
Yet when I browse the "Site collection usage summary" report (SpUsageSite.aspx) I get the following:
No data is available for this report. Usage analysis might have been enabled only recently, or there might have been insufficient usage to result in any values for the report.
My farm is running 2007 Enterprise SP2 (22.214.171.12421).
Can someone confirm if this issue was fixed with one of the CU's that were issues post-SP2?
Does anyone know if the Site Collection Usage Report includes activity that occurs from Outlook? For example, if a user contributes to a discussion board without ever physically touching the site or if the user just reads list content from Outlook,
is this included?
ANY help at all is greatly appreciated.
When I move sites from test to staging to production, I am using the stsadm –o export command with the –includeusersecurity option in the staging environment. In production environment,
I then use the stsadm –o import command with the –includeusersecurity option. I was assuming that this option was bringing over the security on the exported site only. This does not seem to be the case.
Last night I exported one sub site
to produtction. Today, I was notified that the security groups on other sub sites have been altered.
So why is it when using the –includeusersecurity option effect all sub sites and not just the one sub site being moved from staging to production
In our SharePoint installation we have an SSP which indexes local office sharepoint server sites.ÃÂ However there is a problem, although we can do portal searches which reveal search results it is not able to doÃÂ local searches at the site collection level and as aÃÂ result we are presented with the typical error below.
No results matching your search were found.
I am unsure as to why this strange event is occuring.ÃÂ We do not have the WSS Search component running in the MOSS environment as the SSP service should be able to index and server search queries at the portal and local site collection level.
Any thoughts to this?