That was certainly not an expected incident, easy to resolve if you would point out where the issue was.
Infopath forms failed in an specific site, the rest of the site collections seemed to work fine.The message that the user got was:
The server is currently being taken down for maintenance. Check with
your system administrator to see when this server is scheduled to come
back online.
And the image (I will show both versions, MOSS 2007 and SP2010 version of the message):
It was after testing some backup application related to SharePoint.
The version was SharePoint 2010.
After reviewing the database status (read only = NO) and that the Site collection was not lock through the Central administration we checked the status of the farm, because the message was quiet explicit about the maintenance part, and the only idea taht pop-up in my head was that old-fashioned command related to Quiesce.
Open a Sharepoint Power shell using an account with priviledges over the SharePoint (sharepoint administrator) and run the following command:
stsadm.exe -o quiescefarmstatus
If the result is "Farm is Quiesced" then run the following command in order to change this status of the farm, which normally is used for maintenance purposes.
stsadm.exe -o unquiescefarm
stsadm.exe -o quiescefarmstatus you should get now "Farm is not Quiescing"
Short time ago I wanted to check how to enable the Central Administration service in a second server on a farm in a MOSS2007 environment, I didn´t remember how. When you get used to work with 2010 is easy to forget about MOSS2007, the technical jump related to architecture was huge.
Then I get surprise how easy is to get high availability in this basic service in the 2010 version and how different is to enable it on a MOSS2007 environment.
Here you have to run the wizard and press the advanced button to enable the Central administration feature (it will deploy it in the IIS) in the server you want. After remember to change the alternate access mapping (AAM ).
Si necesitas bloquear un sitio en sharepoint puedes utilizar la linea de comandos, rápida y efectiva, y además revisar que se hayan aplicado los cambios a traves de comando o por el interface.
Por que? Puedes bloquearlo para que sólo se disponga de acceso a lectura antes de realizar una copia de seguridad.
Esta opcion sólo sirve para bloquear una collection de sitios, no un subsitio.
-----------------------------
If you need to lock a site collection use the powerfull command-line, stsadm. Just be aware that it´s working for a whole site collection but not for a subsite.
Why? you´ll need this feature before backing up a site collection to avoid inconsistence.
Do you want to move your site under another site? Then follow these steps and enjoy!
Note:As usual follow up all the logical steps to protect your production environment.Be wise.
Method used: Import/export
Properties of import/export: GUIDs are not preserved (alerts, workflows, and some properties are lost with the stsadm import/export process ) but security user features are saved (not in backup)
Note that import/export does not include some site settings, such as Recycle Bin state and alerts.
Why import/export and not backup/restore? Because the second one only works from a root site, it´s not working for a site collection only.
Ie. We´re going to follow an example for understanding better the idea, prepared?
Assuming you have access to the server as an admin, use STSADM.EXE (strong & powerfull sharepoint command-line) to export and then import the site collection into the new location.
Check the amount of free space counting the sites:
C:\Program Files\Common Files\Microsoft Shared\Web Server tensions\12\BIN>stsadm.exe -o enumsites -url http://portal/site1
Procedure
- Create an empty web:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>stsadm -o createweb -url http://portal/sites12/Commercial
Check the export´s log located in the same folder than the log and check the size. If there´s ony few kb instead og some Mb.. check the account your´re using to connect on the application server.
Log checked: 0 errors.
Explication of every flag:
–includeusersecurity :It ensures that the archived content or site will have the same permission requirements as the original.
-quiet: Recommended. Suppresses the output of export progress information to the display window. The final export status (“Operation completed successfully.”) will still be displayed.
-version 4: ensures that all content regardless of version will be included in the archive.
The last step would be to delete the originl site after checking that the new emplace works properly.To avoid any mistake I would keep the old site collection locked (only read access) for some time and after I would delete it. It´s only a recommendation.
Possible issues:
Has been imported only the structure and the lists and document library are missing?? Please check the account you used to connect on the WSS server
