Some times you cant deploy or retract the solution in the solution management

Some times you cant deploy or retract the solution in the solution management

The administration service is running so all administration jobs will be run in
the timer service.


Symptom:

I had a solution that was stuck in the deploying state.  When I looked at it,
 it had only deployed successfully on one the the front ends.  To solve the
 problem, I ran stsadm execadmjobs. I have done this multiple times in 2007, 
but this time I got this message:

The administration service is running so all administration jobs will
 be run in the timer service.

Problem:

The timer service is set to take care of all admin tasks, so it is telling you that
 the jobs will run when the timer service is good and ready to kick them off, but 
until then, just sit on your hands and wait.

Solution:

Stop the admin service, then run the command to execute the admin jobs, 
then turn back on the admin service.  
These are the three powershell commands to do this:
 •net stop SPAdminV4
•Start-SPAdminJob
•net start SPAdminV4

The first command shuts off the admin service.  The second command is the
 powershell equivalent to stsadm execadmjobs and the third one turns back 
on the admin service.

Add an index server to Existing farm

Add an index server to the farm

SharePoint 2007

0 out of 3 rated this helpful - Rate this topic

Updated: July 15, 2008

Applies To: Office SharePoint Server 2007

Updated: 2008-07-15

You can use this procedure to add and configure an index server in your SharePoint Products and Technologies server farm.

Add an index server to the farm

Use these procedures to install and configure SharePoint Products and Technologies on a new index server to be added to an existing SharePoint Products and Technologies server farm. If your SharePoint Products and Technologies administration includes preset configuration files, be sure to use the procedure for command-line installation.

Before you begin:

• Verify that you know the name of the database server used for the farm you are connecting to
• Ensure that the server you are adding has the following installed software:
  • Microsoft Windows Server 2003 with Service Pack 1 (SP1) and an NTFS file system.
  • The Microsoft .NET Framework version 3.0
  • Microsoft Internet Information Services (IIS) 6.0 with ASP.NET 2.0 installed and enabled

The following procedures contain steps and settings specific to the job of creating and integrating an index server to your farm. For detailed prerequisites and installation instructions for SharePoint Products and Technologies, see Deploy in a simple server farm (Office SharePoint Server).

Important:
You must be a member of the Farm Administrators SharePoint group to complete the following procedure.

Add an index server by using the user interface

1. From the product disc or file share containing the SharePoint Products and Technologies installation files, run Setup.exe.
2. On the Enter your Product Key page, enter your product key, and then click Continue.

   Note:
   Setup automatically verifies the product key, places a green check mark next to the text box, and enables the Continue button after it validates the key. If the key is not valid, Setup displays a red circle next to the text box and prompts you that the key is incorrect.

3. On the Read the Microsoft Software License Terms page, review the terms, select I accept the terms of this agreement, and then click Continue.
4. On the Choose the installation you want page, click Advanced. The Basic option is for stand-alone installations.
5. On the Server Type tab, click Complete.
6. Optionally, to participate in the Customer Experience Improvement Program, select the Feedback tab and select the option you want. To learn more about the program, click the link. You must have an Internet connection to view the program information.
7. When you have chosen the desired options, click Install Now.
8. When Setup finishes, a dialog box appears that prompts you to complete the configuration of your server. To use the configuration wizard, be sure that the Run the SharePoint Products and Technologies Configuration Wizard now check box is selected.
9. Click Close to complete the installation.
10. On the configuration wizard Welcome page, click Next.
    A message is displayed notifying you that Internet Information Services (IIS), the Windows SharePoint Services Administration service, and the Windows SharePoint Services Timer service may need to be restarted or reset during configuration. Click Yes to continue.
11. On the Connect to a server farm page, select Yes, I want to connect to an existing server farm, and then click Next.
12. On the Specify Configuration Database Settings page, in the Database server box, type the name of the database server used for the farm you are connecting to, and then click Retrieve Database Names.
13. In the Database Name box, click the SharePoint configuration database on the drop-down list. This database is usually named SharePoint_Config.
14. In the Specify Database Access Account section, type the user name and password to use to connect to Microsoft SQL Server, and then click Next.
15. On the Completing the SharePoint Products and Technologies Configuration wizard page, verify the settings, and then click Next.
16. On the Configuration Successful page, review your settings for the new Web server, and then click Finish. To finish configuring your index server, see “Configure a new server as an index server” later in this article.

Important:
You must be a member of the Administrators group on the local server computer to complete the following procedure.

Add an index server to the farm by using the command line

1. Open a command prompt window and change to the disk or file share containing the SharePoint Products and Technologies installation files.
2. Type the following command, and then press ENTER:setup.exe /config\\<server>\<folder>\<configuration file name>

   Note:

   When you run Setup.exe, you include a space after the command, followed by a forward slash (/) and the name of the switch, and sometimes followed by another space and one or more parameters. A Setup configuration file is necessary when installing SharePoint Products and Technologies from the command line. You may need to choose from several different configuration files depending on the type of server you are installing. Be sure to choose the configuration file that will result in a front-end Web server. For more information about Setup.exe parameters, seeSetup.exe command-line reference (Office SharePoint Server).

3. After installation is complete, change to the following directory to begin configuration: %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\Bin
4. Type the following command, and then press ENTER:psconfig –cmd configdb –connect –server<database server name>-database<database name>
   where <database name> is the name of the configuration database for the SharePoint Products and Technologies server farm you want to connect to.

Configure a new server as an index server

1. On the SharePoint Central Administration Web site, on the Operations page, in the Topology and Services section, click Servers in farm.
2. On the Servers in Farm page, in the Server column, click the name of the server that you want to configure as your index server.
3. On the Services on Server page, select Search Indexing, and then check the status of the Office SharePoint Server Search service in the table. If the service status is Stopped, click Start.
4. On the Configure Office SharePoint Server Search Service Settings page:
   1. In the Query and Indexing section, select the option for indexing content.
   2. In the Contact E-mail Address section, specify someone whom site owners can contact if problems occur when sites are being crawled.
   3. In the Farm Search Service Account section, provide a name and password for the account that the search service runs on.
   4. In the Index Server Default File Location section, enter the path of the index file.
   5. In the Indexer Performance section, select Maximum.
   6. In the Web Front End and Crawling section, select the search service option running on your server farm.
   7. Click OK.

First Copy the below Script from echo off to echo off in Notepad and change the URL's and save Ext as .bak

Back up schedule: ext- .bak   :
----------------------------------------

@echo off
@echo——————————————————–
@echo This script will backup your site: [SITE COLLECTION Backup]
@echo——————————————————–
cd \Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN
@echo Backup process starts

stsadm -o backup -url http://abcsite-filename C:\spbackup\SharePoint2010backup.bak -overwrite
@echo backup completed
@echo off

 Now, follow the steps below to create the tasks for Task Scheduler to automate the execution of backup files - let's assume we will full-backup weekly and diff-backup daily.

1 - Open Tools > Tasks Scheduler

2 - In the center pane, right-click, and click Create Basic Task

3 - Assign the task a meaningful name - such as SharePoint-BackupFullWeekly

4 - Choose "Weekly " on the When do you want the task to start screen

5 -  Specify the parameter for the weekly task schedule

6 -  Choose "Start a program" from the what action do you want the task to perform

7 -  On the start a program screen type in the command as the screenshot below. The Task scheduler is intelligent enough to recognize that you want to run PowerShell and that you supplied arguments.

Repeat the steps above to create a task for the diff backup.