Archive for May, 2008

MOSS: Send email to all site users

The trick is simple with one prerequisite. The prerequisite is that one ocument library should exist which can be access by all users of the site.

Upload and open or open an existing MS Word Document. It will have Shared Workspace on the left of the screen. If not, click on “Shared Workspace” under “Tools” menu. “Shared Workspace” select “Members” tab and it has option “Send an email to all members…”. Click on it and get email address of all the users of the site.

Leave a Comment

SharePoint 2003 to MOSS 2007 Upgrade: Database migration

Of all the three upgrade techniques, my favorite is database migration. Database migration can be defined as “Requires the server administrator to install the new version on a separate farm or separate hardware, and then manually migrate the databases into the new environment.”

 

Database Migration enables moving to new farm or new hardware while SharePoint Portal Server 2003 environment is available and is untouched by upgrade. Microsoft says that database migration is a “Complex process that requires many manual steps and a higher risk of error. Requires additional manual steps to retain original URLs for sites. Search scopes must be re-created and search settings must be reapplied. Requires new server farm, and twice the amount of SQL Server storage space”. My advise is don’t be afraid and do try.

 

These steps are done for upgrade from WSS2.0/SharePoint 2003 to WSS3.0/MOSS 2007 in a single form environment. For different architecture, you may need some more steps. The steps are under: 

·     Get ready your MOSS 2007 environment.

·     Run PreScan on SharePoint Portal Server 2003.

·     Set the content database of SharePoint Portal Server 2003 as read only.

·     Take back up of content database of SharePoint Portal Server 2003.

·     Restore back up on SQL Server attached with MOSS 2007.

·     Create web application in MOSS 2007.

·     Remove content database of the newly created web application in MOSS 2007.

·     Attach restore database with the newly created web application in MOSS 2007.

 

And that’s itJ.

 

I am not going into the details of creating MOSS 2007 environment. We will start from the second step:

 

Run PreScan on SharePoint Portal Server 2003:

 

The first step is to run PreScan.exe. For details kindly visit the following blog:

 

https://farhanfaiz.wordpress.com/2008/05/15/sharepoint-upgrade-prescanexe/

 

Set the content database of SharePoint Portal Server 2003 as read only:

The content database of SharePoint Portal Server 2003 ends with 1_SITE like Abc1_SITE.

 

The steps for setting database as read only are:

 

For SQL Server 2000

 

1.     In Microsoft® SQL Server™ Enterprise Manager, right-click the name of the database that you want to set to read-only, and then click Properties.

2.     In the Properties dialog box, click the Options tab.

3.     Under Access, select the Read-only check box, and then click OK.

 

 

For Server 2005

1.     In Microsoft SQL Server Management Studio, right-click the name of the database that you want to set to read-only, and then click Properties.

2.     In the left pane, click Options.

3.     In the right pane, under Other options, under State, next to Database Read-Only, click the down arrow, and then select True.

 

Take back up of content database of SharePoint Portal Server 2003:

 

For details kindly visit the following blog:

 

https://farhanfaiz.wordpress.com/2008/05/16/sharepoint-2003moss-2007-take-back-up-of-content-database-in-sql-server-2000-and-sql-server-2005/

 

Let the name of the back be “Portal_Site.bak”. Wait after this. The time of database backup depends upon the system power and database size.

 

 

Restore back up on SQL Server attached with MOSS 2007:

 

The first step in restoring database is to create a database in SQL Server 2005. Let the newly created database name is “Portal_Site_Restore”.

 

1.     Expand Database “Portal_Site_Restore”, right-click the database you want to restore, point to Tasks, point to Restore, and then click Database. The Restore Database dialog box appears.

2.     On the General page, the name of the restoring database appears in the To database list box.

3.     In the To a point in time text box (if using SQL Server 2005 Enterprise Edition), retain the default (Most recent possible).

4.     To specify the source and location of the backup sets to restore, click From device, and then specify the database backup path (in our case, it is “Portal_Site.bak”) in the list box.

5.     In the Select the backup sets to restore grid, select the backup path.

6.     From the options tab, select “overwrite existing database”.

7.     Specify the paths for .ldf and .mdf in the options tab.

8.     Click OK to start the restore process.

 

Wait after this. The time of restoring database depends upon the system power and database size.

 

 

Create web application in MOSS 2007

 

In the SharePoint Central Administration, move to “Application Management” and click on “Create or extend Web application” under “SharePoint Web Application Management”.

 

Again click on “Create Web application”. Set the settings according to your own needs (do check the name of the web application and content database. Let the name of the web application be “http://servername:1234” and the name of the content database be “WSS_Content_1234”) and click OK. Don’t create any site collection.

 

 

Remove content database of the newly created web application in MOSS 2007

 

We can do that using Central Administrator or stsadm utility. I will like to do that using stsadm. Central Administration is easy. You will be able to learn that if you know how to do it using stsadm.

 

The command for removing content database using stsadm is ‘deletecontentdb’. The description is as under:

 

stsadm.exe -o deletecontentdb

-url <URL name>

-databasename <database name>

[-databaseserver] <database server name>

 

Parameter name

Value

Required?

Description

url

A valid URL, such as http://serverame:1234

Yes

Specifies the Web application from which the content database will be detached.

databasename

A valid database name, such as “WSS_Content_1234”

Yes

Specifies the name of content database to be detached.

databaseserver

A valid database server, such as “SQLServer1”

No

Database server name to be detached.

 

A typical command will be like:

 

stsadm.exe -o deletecontentdb -databasename WSS_Content_1234 -url http://servername:1234

 

Attach restore database with the newly created web application in MOSS 2007

 

We can do that using Central Administrator or stsadm utility. I will like to do that using stsadm. Central Administration is easy. You will be able to learn that if you know how to do it using stsadm.

 

The command for removing content database using stsadm is ‘addcontentdb’. The description is as under:

 

stsadm.exe -o addcontentdb

-url <URL name>

-databasename <database name>

[-databaseserver <database server name>]

[-databaseuser <database username>]

[-databasepassword <database password>]

[-sitewarning <site warning count>]

[-sitemax <site max count>]

 

Parameter name

Value

Required?

Description

url

A valid URL 

Yes

URL of

the Web

application

to which

the content

database is

being

added.

databasename

A valid

database name

Yes

Database

name.

databaseserver

A valid

database

server name

No

Database

server

name. The

default

server

is used

if a

value

not

provided.

databaseuser

A valid user

name in the

form “domain\login”

No

Account

used for

SQL authentication. Must be

used in

conjunction

with the

database

password parameter.

databasepassword

A valid

SQL

password

No

The database

password parameter should only

be used

where Windows authentication is not

implemented.

sitewarning

A valid

integer

number,

such as

10

No

Integer number

of site

collections allowed in

the content

database

prior to

generating

a warning

event in the

Windows event log.

sitemax

A valid

integer

number,

such as

10

No

Specifies

the maximum

number of site collections allowed in

the content

database.

 A typical command will be like:

 

stsadm.exe -o addcontentdb -url http://servername:1234 –databasename Portal_Site_Restore

 

Wait after this command. The time of adding content database depends upon the system power and database size.

 

 

http://office.microsoft.com/download/afile.aspx?AssetID=AM101638521033

 

http://technet.microsoft.com/en-us/library/cc263422.aspx

 

http://technet.microsoft.com/en-us/library/cc262449.aspx

 

 

Comments (55)

SharePoint 2003/MOSS 2007: Take back up of content database in SQL Server 2000 and SQL Server 2005

 

The content database of SharePoint Portal Server 2003 ends with 1_SITE like Abc1_SITE and for MOSS 2007 the convention is WSS_Content_ (followed by large string of numbers).

 

In order to take the backup of this database either it is in SQL Server 2000 or SQL Server 2005 follows the steps:

 

For SQL Server 2000

 

1.     On your database server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

2.     In SQL Server Enterprise Manager, click the plus sign next to Microsoft SQL Servers.

3.     Click the plus sign next to SQL Server Group.

4.     Click the plus sign next to (local) (Windows NT).

5.     Click the plus sign next to Databases.

6.     Right-click the database you want to back up, point to All Tasks, and then click Backup Database.

7.     In the SQL Server Backup dialog box, in the Name box, specify a name for the backup, and then in the Backup area, select Database – complete.

8.     In the Destination area, either select an existing destination, or:

a.     Click Add.

b.     In the Select Backup Destination box, select File Name, and then next to the File Name box, click the Browse button.

c.      In the Backup Device Location – (local) dialog box, in the File name box, type a file name, and then click OK.

d.     Click OK again to close the Select Backup Destination dialog box.

9.     Click OK to start the backup process.

10.    Click OK to acknowledge that the backup process has completed.

Repeat these steps to back up the databases that are used by SharePoint Portal Server 2003 in your environment, except for the configuration and component settings (search) databases.

 

 

For SQL Server 2005

 

1.     On your database server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2.     In the Connect to Server box, fill in the connection information, and then click Connect.

3.     After connecting to the appropriate instance of the SQL Server 2005 Database Engine, in Object Explorer, click the server name to expand the server tree.

4.     Expand Databases, right-click the database you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.

5.     In the Source section, in the Database box, verify the database name.

6.     In the Backup type box, select Full.

7.     Under Backup component, click Database.

8.     In the Name text box, either accept the default backup set name that is suggested or type a different name for the backup set.

9.     In the Destination section, choose the type of backup destination by clicking Disk or Tape, and then select a destination. To create a different destination, click Add.

10.    Click OK to start the backup process.

 

http://office.microsoft.com/download/afile.aspx?AssetID=AM101638521033

Leave a Comment

SharePoint Upgrade: Prescan.exe

You can download prescan.exe from this link or it can be found at “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN” along with preupgradescanconfig.xml

 

PreScan is a pre-upgrade scan tool used to scan all Web sites in your environment (by using the /all parameter) or to scan a specific URL (by using the /v <URL> parameter). If you do not supply a scoping parameter, all Web sites will be scanned. The pre-upgrade scan tool takes the following parameters:

 

Parameter

Description

/all

Scans all site collections in a server farm.

/v <URL>

Scans all site collections at a specific URL.

/c preupgradescanconfig.xml

Uses the preupgradescanconfig.xml file while scanning. This configuration file contains additional logic to identify the portal site templates as standard templates used by SharePoint Portal Server 2003 rather than as custom templates based on Windows SharePoint Services 2.0. You must use this parameter when scanning site collections based on SharePoint Portal Server 2003. This parameter has no effect when scanning site collections based on Windows SharePoint Services 2.0.

 

 

To run Prescan.exe, perform the following steps:

 

On the command line, change to the folder that contains the file, and then run the prescan.exe command with the appropriate parameters. For example,

 

prescan.exe /all or

prescan.exe /c preupgradescanconfig.xml /all or

prescan.exe /c preupgradescanconfig.xml /v http://sps

  

I will recomend to use the second option.

  

After successful run, it will generate reports with name PreupgradeReport_uniqueID_Log.txt (where uniqueID is a number string) located in the temp directory on the computer of the user who ran the tool (for example, C:\Documents and Settings\User\Local Settings\Temp or Temp\2).

 

An example output is:

 

=====================Totals===================

Number of sites skipped (already scanned):   0

Number of sites scanned:   12

Number of broken sites:   0

Number of webs scanned:   41

Number of broken webs:   0

Number of webs using custom template:   0

Number of pages scanned:   4145

Number of unghosted pages:   40 (0.97% of total).

 

 

For errors, check Bill Baer blog:

 

http://blogs.technet.com/wbaer/archive/2006/12/22/prescan-errors-what-they-mean.aspx

 

Comments (2)

SharePoint 2003: Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists.

Error:

 

Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists.

 

Description:

 

We tried to upgrade SPS 2003 to MOSS 2003 using in place upgrade which was a disaster. Fortunately it was our development serverJ. We uninstall SPS 2003 and reinstall SPS 2003. When we try to open the portal main page “http://portal/default.aspx”, found the error “Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists.” on every web part. Other links like “Sites” were also not working.

 

Resolution:

 

It turns out that our SharePoint Central Administration and Virtual Server was running under ASP.Net 2.0…… We changed it back to 1.1…… through IIS and everything was fine.     

Comments (3)

ERROR: SharePoint Portal Server 2003 on the server does not match the language you are currently trying to install

Exception:

 

When you try to install SharePoint Portal Server 2003, you get the following error:

 

“SharePoint Portal Server 2003 on the server does not match the language you are currently trying to install.”

 

Reason:

 

On my side, this exception occur when I try to install SharePoint Portal Server 2003 and uninstall process get stuck. I restart the system and when try to install SharePoint Portal Server 2003, got the above the exception.

 

Resolution:

 

Go from Start -> Run and type “regedit”.

 

Move from HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> SharePoint Portal Server

 

Either delete the entry “SharePoint Portal Server” or rename it like “SharePoint Portal Server discard”.

Leave a Comment

SharePoint Portal Server 2003: Site Creation Page get stuck

Problem: 

The problem is about site creation. While creating a new site, the screen doesn’t respond. After entering the general information, and clicking OK, the button grays out but just sits there. In order to continue, I write the site link directly in the browser, and then it brings me back to the site creation flow.The problem is that the site created through this work around is not coming up in searches, or in the list of all sites. I can only get to it by typing in the exact link. Although, site is created in the database. 

Resolution: 

The solution is as under: 

1- Install WSS Service Pack 3  

http://www.microsoft.com/downloads/details.aspx?FamilyId=2BBFC89B-EB59-49FF-B58F-684693CB25A7&displaylang=en 

2- Install SharePoinr SharePoint Portal Server 2003 Service Pack 3 (SP3)  

http://www.microsoft.com/downloads/details.aspx?FamilyId=2BBFC89B-EB59-49FF-B58F-684693CB25A7&displaylang=en 

Hopefully the problem will be solved.  

This may generate a new error when you try to view Documents / list items using “Eidt in DataSheet” option following error may occur: 

“The list is displayed in Standard view. It cannot be displayed in Datasheet view for one or more of the following reasons: A datasheet component compatible with Windows SharePoint Services is not installed, your browser does not support ActiveX controls, or support for ActiveX controls is disabled.” 

you don’t need to worry 

3- Install hotfix. From the following URL, send request to Microsoft. 

http://support.microsoft.com/kb/943167 

Comments (1)

Older Posts »