Windows Server 2012 Test Lab

W2008R2 to W2012 Migration Planning

Sharepoint 2010 Access Denied +SP on Hyper-V

A. Access Denied

PROBLEM: Sharepoint 2010 Access Denied
FIX: Delete Domain Account and then recreate.

I’ve recently migrated a Sharepoint Server 2010 from a Dell Poweredge 2850 to Hyper-V.  Everything works fine except one subsite keeps getting “Access Denied”.  I’ve read a lot of documentation and blogs but none of them provided the solution to the problem.

I’ve narrowed down the issue to a specific user and I can repeat the problem over and over.

After several trial and error and no fix in sight, I tried deleting the account in the Active directory and then recreate it and the account started working. 

B. Sharepoint 2010 Migration from Physical to Virtual [Hyper-V] [view P2V Toolkit]
I’ve been testing Sharepoint 2010 for over a year now using a Dell Poweredge 2850 2U Rack Server.  I have a 24U rack in my home office that I utilized for testing and recently, the demand to quite down the office area and reduce the amount of heat generated has become my primary objective lately.  This week I finally able to do it without issues [except the access denied mentioned above]

Benefits:
1. One Server running
2. Less Noise
3. Less Heat
4. Backup/Restore of .vhd is simpler
5. I can use the PE2850 for other tests.

VM Info:

VHD Allocation

CPU and Memory Performance of Sharepoint2010 on Hyper-V

Process

Install and configure RBS (SharePoint Server 2010)

Install and configure RBS (SharePoint Server 2010)

via Install and configure RBS (SharePoint Server 2010).

Open [instead of save] .pdf in Browser in Sharepoint 2010

The default setting for Sharepoint 2010 Server asked you to save a .pdf instead of opening it in the browser.

FIX:
1. Open Central Admin
2. Application Management-Manage Web Application
3. Select the Site
4. Click General Settings-General Settings
5. In Browser File Handling, Change the selection from Strict to Permissive.

Install and configure RBS (SharePoint Foundation 2010)

Install and configure RBS (SharePoint Foundation 2010)

via Install and configure RBS (SharePoint Foundation 2010).

Sharepoint 2010 Excel Import Error “Selected Cells Are Read Only”

PROBLEM: When importing an Excel spreadsheet to a Custom List, the following error occurred:
”The selected cells are read only”

FIX: Change the default enhanced rich text to plain text on the text box you just created.

Force Delete a Sharepoint Web from SQL Management Studio

1. Open SQL Management Studio
2. Go to WSS_Content DB-Tables-DBO.Webs
3. Delete the row containing the site.

Sharepoint is Down-Unable to Connect to my Dynip Servers

1. Verify Dynip Client is running/functional at vdomain
2. Reestablish client connection to Dynip

Sharepoint 2010 Templates

http://www.techsolutions.net/Blog/tabid/65/EntryId/18/Fab-40-for-Sharepoint-Foundation.aspx

HOWTO: Install a new Sharepoint 2010 Template
1. Go to the main Sharepoint 2010 Site
2. Click Stie Actions-Site Settings
3. Under Galleries-Click Solutions
4. Click the Library Tab
5. Click the Solutions Tab
6. Click Upload Solution
7. Browse-Select File and Click OK
8. Click Activate
9. Then Close

HOWTO: Use a Sharepoint 2010 Template
1. Go to the main Sharepoint 2010 Site
2. Click Site Actions-New Site
3. Select a Template
4. Enter Title, url
5. use Unique Permission
6. Navigation, No, No, No

Issue Tracking DB

Project: Sharepoint 2010 +SQL Server 2008R2 on Poweredge 2850

Objective: To deploy Sharepoint 2010 and SQL Server 2008R2 on a production server [PE2850]
Date: 20110901
Hardware and Software Information:
Dell Poweredge 2850, 2.8GHz Xeon 8GB Memory
Drive0-73GB, c: mirror
Drive1-73GB, c: mirror
Drive2-73GB, v: mirror
Drive3-73GB, v: mirror
Drive4-150GB, y: backup
Drive5-150GB, f: sqldata

Software:
OS-Windows 2008R2 Data Center
Sharepoint 2010 Enterprise
SQL Server 2008 R2

Phase 1.0 OS Installation
1. Install Windows 2008 R2 OS
2. Activate Server
3. Run Windows Update
4. Add server to Active Directory
5. Copy Sharepoint 2010 to c:
6. Copy SQL2008 setup files to c:

Phase 2.0 SQL Server Installation
7. Run SQL Server 2008 R2 setup
8. Choose New Installation
9. Support Rules installation->Requirements all pass, 7 items ->Click OK
10. Enter Product Key
11. Accept the Terms-> Click Next
12. Install Setup Support Files
13. Review the warnings, 11 items – 1 yellow Windows Firewall -Click Next
14. SQL Server Feature Installation-Install all features, Pass-6, Failed-0 Warning-0, Skipped-18
15. Select Default Instance
16. Review Disk Space Requirments, 6109 GB Required, 48362 Available
17. Choose Service Accounts
SQL Service Agent, NT Authority\System, Manual
SQL Server Database Engine, NT Authority\System, Automatic
SQL Server Analysis Service, NT Authority\System, Automatic
SQL Server Reporting Service, NT Authority\System, Automatic
SQL Server Integration Service, NT Authority\System, Automatic
SQL Server Full Text Filter, NT Authority\Local Service, Manual
SQL Server Browsing, NT Authority\Local Service, Disabled
18. Choose DB Engine Configuration-Windows Authentication
19. Click Add Current User
20. In Data Directories, choose f: drive [sqldata]
21. In Analysis Service, Add current user
22. In Reporting Service, Select “Install the Sharepoint Integrated Mode”
23. In Error Reporting, Click Next
24. In Installation Configuration Rule, Pass-6, Failed-0, Warning-0, Skipped-2
25. In Summary, Click Install
26. Install SQL 2008 Updates and SP1

Phase 3.0 SQL Server Configuration
27. In Windows Firewall, Advanced Settings, Add an Inboud Rule SQL 2008 Port1433, TCP
28. Enable TCP/IP Protocol in SQL Configuration Manager

Phase 4.0 Sharepoint 2010 Installation
29. Install Sharepoint 2010-Install Prerequisite
30. Install Sharepoint 2010-Enter Key
31. Choose Server Farm [Do not install the Stand Alone, or SQL Server Express will be installed]
32. Select Server Type, Complete
33. Setup Complete
34. Run Windows Update and update everything
35. Install Sharepoint 2010 SP1
36. Run Windows Update again

Phase 5.0 Sharepoint 2010 Configuration
37. Run Sharepoint 2010 Product Configuration
38. Select Create a new server farm
39. Set Sonfiguration Database as:
DB Server=PE2850
DB name=WSS_Config
Username=vdomain\adminstrator
Passphrase=
40. Specify the Port – 7000 and choose NTLM
41. Review the Settings – http://pe2850:7000
42. Run Initial Farm Configuration Wizard
43. Complete the Wizard and http://pe2850:7000 Central Admin Site opens
44. In Customer Experience, Select No, I do not wish to participate
45. Run the Sharepoint Farm Wizard, Click Start Wizard
Service Account-vdomain\spadmin
Service – Select all but Lotus
46. Create a Top Level Site [Enterprise Wiki]
Title-Rigel Research International
URL-http://pe2850
Template-Enterprise Wiki
47. Test the new site
Phase 6.0 Firewall Configuration
48. Open Firewall Exception at Router, 192.168.1.5 Port 8000
49. Open Firewall Exception at Windows Firewall, 192.168.1.5 Port 8000
50. Open IIS Manager, Change Sharepoint-80 binding from Port from 80 to 8000

Phase 7.0 Old Sharepoint 2010 Migration of SQL Data
51. Verify new farm site functionality, http://pe2850
52. Open Central Admin->Manage Web Application->Confirm Site name-Sharepoint-80
53. In Central Admin, Click Manage Content Database and Check “Remove Database”
54. Copy the old WSS_Content.mdf and WSS_Content_Log.ldf to f:\SQLData Location
55. Open SQL Management Studio
56. Right Click WSS_Content database->Task->Detach->Click OK
57. Go to SQL Data Location->Rename the current WSS_Content.mdf to WSS_Contentx.mdf
58. Go to SQL Data Location->Rename the current WSS_Content_Log.ldf to WSS_Content_Logx.ldf
59. Rename the copied backup copy to WSS_Content.mdf and WSS_Content.ldf
60. In SQL Management Studio, Right Click Database->Attach->Add
61. Select WSS_Content.mdf [the old copy]
62. In SQL Management Studio-> Security-> Logins
63. Right Click vdomain\Administrator->Properties-User mapping->Set to dbo for WSS_Content
64. Right Click vdomain\spadmin->Properties-User mapping->Set to dbo for WSS_Content
65. In Central Admin, Click Manage Content Database->Add Database
66. Set Database Configuration
Database Server=PE2850
DB Name=WSS_Content
67. Select Windows Authentication
68. Open IE and test http://pe2850/sites/intranet
69. Confirm that Search Functionality is not working at this time

Phase 8.0 Sharepoint Search Server Configuration
70. In Central Admin, Click Notice from Health Analyzer->View these issues
71. Confirm no crital errors and no Certificate token errors
72. In Central Admin, Click Manage Service Application
73. Select Search Service Application and Click Manage Icon from the Ribbon Toolbar
74. Click Content Sources and Click Local Sharepoint Site
75. Set the following
a. Setup Full Crawl, Daily at 12am
b. Setup Incremental Crawl at 12pm
c. Check-Start Full Crawl Now
76. Click the Refresh Link to see the status
77. Open Task Manager and monitor CPU and Disk I/O of mssearch.exe
78. Open IE and confirm Sharepoint Search Functionality

Phase 9.0 Adobe iFilter Configuration
79. In Central Admin, General Security->Define Blocked Type and check if pdf is not list
80. In Central Admin, Manage Service Application->Search Service Application-Click Manage
81. In Left Pane, Click File Types->New File Type->Enter pdf and Click OK
82. Read and implement kb/2293357
83. Install Adobe iFilter Pack 9.0 x64
84. Download pdf icon and place to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES\ folder
85. Add Entry to docicon.xml located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML
<Mapping Key=”pdf” Value=”pdficon_small.gif”/>
86. Reboot Sharepoint Server
87. Execute Full Crawl again
88. Open IE and confirm Search Functionality with pdf icon showing.

Sharepoint 2010 Security Token Issue

I’ve migrated a Sharepoint 3.0 box to Sharepoint 2010 Foundation a few months ago using the Database Attach method.  The upgrade went well but I could not get the search functionality to work no matter how I tried.  The error below pops up at the Application Event Log which clearly states that there is a problem in the Security  Token mechanism.

An exception occurred when trying to issue security token: Could not connect to http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc/actas. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:32843. .

FIX: Long story short, I have to setup a new Sharepoint 2010 box and then migrate the SQL database to the new server.

Lessons Learned:
1. I’ve learned how to migrate to Sharepoint 2010 over and over [maybe 4x]
2. I’ve learned how to fix a Sharepoint 2010 Search issues [Link]
3. I’ve learned how to fix the .pdf issue “not searching pdf” [Link] [Link2]

Configure Sharepoint 2010 Search Service

http://sharepointgeorge.com/2010/configuring-enterprise-search-sharepoint-2010/

Configure Adobe iFilter for Sharepoint 2010 – kb/2293357

http://support.microsoft.com/kb/2293357
http://www.sharepointsharon.com/2010/03/sharepoint-2010-and-adobe-pdf/

Sharepoint 2010 and Filestream

http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=970

Notes: PowerPivot Excel 2010 and Sharepoint 2010

Download Site
PowerPivot for Sharepoint 2010 Documentation
Business Intelligence Blog 
Demo

Troubleshooting Sharepoint Certificate Issues

Troubleshooting Sharepoint Certificate Issues
http://blogs.blackmarble.co.uk/blogs/rhepworth/archive/2010/01/07/reassigning-the-correct-ssl-certificate-to-sharepoint-2010-web-services-iis-site.aspx

Filestream in Sharepoint2010

http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=970

NOTES: Digital Rights Management in Sharepoint

Apply IRM to a list or library
Full Article

Before IRM can be enabled for lists and libraries, the Microsoft Windows Rights Management Services (RMS) Client with Service Pack 2 must be installed on every front-end Web server for your SharePoint site. In addition, Information Rights Management needs to be enabled in Central Administration for your site. Additionally, a server administrator must install protectors on all front-end Web servers for every file type that the people in your organization want to protect by using IRM.

To apply IRM to a list or library, you must have at least the Design permission level for that list or library.

1. If the list or library is not already open, click its name on the Quick Launch.

If the name of your list or library does not appear, click View All Site Content, and then click the name of your list or library.

On the Settings menu , click List Settings, or click the settings for the type of library that you are opening.

For example, in a document library, click Document Library Settings.

2. Under Permissions and Management, click Information Rights Management.

Note   If the Information Rights Management link does not appear, IRM might not be enabled for your site. Contact your server administrator to see if it is possible to enable IRM for your site. The Information Rights Management link does not appear for picture libraries.

3. On the Information Rights Management Settings page, select the Restrict permission to documents in this library on download check box to apply restricted permission to documents that are downloaded from this list or library.
4. Under Permission policy title, type a descriptive name for the policy that you can use later to differentiate this policy from other policies.

For example, you can type Company Confidential if you are applying restricted permission to a list or library that will contain company documents that are confidential.

5. Under Permission policy description, type a description that will appear to people who use this list or library that explains how they should handle the documents in this list or library.

For example, you can type Discuss the contents of this document only with other employees if you want to restrict access to the information in these documents to internal employees.

6. To apply additional restrictions to the documents in this list or library, do any of the following.

To
Do this

Allow people to print documents from this list or library.
Select the Allow users to print documents check box.

Allow people with at least the View Items permission to run embedded code or macros on a document.

Select the Allow users to access content programmatically check box.

Note   If you select this option, users could run code to extract the contents of a document.

Require that people verify their credentials at specific intervals.

Select this option if you want to restrict access to content to a specified period of time. If you select this option, people’s issuance licenses to access the content will expire after the specified number of days, and people will be required to return to the server to verify their credentials and download a new copy.

Select the Users must verify their credentials every check box, and then specify the number of days for which you want the document to be viewable.

Prevent people from uploading documents that do not support IRM to this list or library.

If you select this option, people will not be able to upload any of the following file types:

• File types that do not have corresponding IRM protectors installed on all of the front-end Web servers.
• File types that Windows SharePoint Services 3.0 cannot decrypt.
• File types that are IRM protected in another program.

Select the Do not allow users to upload documents that do not support IRM check box.

Remove restricted permissions from this list or library on a specific date.
Select the Stop restricting permissions to documents in this library on check box, and then enter the date that you want.

7. After you finish selecting the options that you want, click OK.

HOWTO Enable Anonymous Access to Sharepoint Server

HOWTO Enable Anonymous Access to Sharepoint Server

rakb200810202103

1. Enable anonymous access for the Web application.
2. Open Sharepoint Central Administration–>Application Management Tab
3. Under Application Security, Click Authentication Providers
4. Click Default Zone
5. Check Enable Anonymous Access
6. Click Save and Close Central Admin site.
7. Open the site on which you want to enable anonymous access.
8. On the Site Actions menu , click Site Settings.
9. On the Site Settings page, in the Users and Permissions column, click Advanced permissions.
10. On the Permissions page, on the Settings menu, click Anonymous Access.
11. On the Change Anonymous Access Settings page, select the parts of your Web site that you want anonymous users to access.
12. END

HOWTO: Adding Application Template To Sharepoint

HOWTO: Adding Application Template To Sharepoint

rakb200810190836

1. Download Sharepoint Template from http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb407286.aspx
2. Extract the template to a folder in c: drive
3. Copy the Sharepoint Template with .wsp extension to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN folder
4. Open command prompt at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
5. Type this command in the command prompt.
stsadm -o addsolution -filename ApplicationTemplateCore.wsp
stsadm -o deploysolution -name ApplicationTemplateCore.wsp -allowgacdeployment -local
stsadm -o copyappbincontent
6. Type this command in the command prompt to install KnowledgeBase
stsadm -o addsolution -filename KnowledgeBase.wsp
stsadm -o deploysolution -name KnowledgeBase.wsp -allowgacdeployment –local
7. Type this command in the command prompt to install HelpDesk
stsadm -o addsolution -filename HelpDesk.wsp
stsadm -o deploysolution -name HelpDesk.wsp -allowgacdeployment –local
8. Type this command in the command prompt to install BugDatabase
stsadm -o addsolution -filename BugDatabase.wsp
stsadm -o deploysolution -name BugDatabase.wsp -allowgacdeployment –local
9. Type this command in the command prompt to install CallCenter
stsadm -o addsolution -filename CallCenter.wsp
stsadm -o deploysolution -name CallCenter.wsp -allowgacdeployment –local
10.Type this command in the command prompt to install ITTeamWorkspace
stsadm -o addsolution -filename ITTeamWorkspace.wsp
stsadm -o deploysolution -name ITTeamWorkspace.wsp -allowgacdeployment –local
11. Open your Sharepoint Site
12. Click Site Actions—>Create
13. Under Web Pages, Click Sites and Workspaces
14. Enter Title
15. Enter URL name
16. Under Template Selection, Click Application Template Tab
17. Select the Template you wan to install.
18. User Permission-Same as parent
19. Answer Yes, Yes, Yes if this is a subsite.
20. END

Repeat these commands to install the rest of the template.

stsadm -o addsolution -filename ProjectTrackingWorkspace.wsp
stsadm -o deploysolution -name ProjectTrackingWorkspace.wsp -allowgacdeployment -local

stsadm -o addsolution -filename InventoryTracking.wsp
stsadm -o deploysolution -name InventoryTracking.wsp -allowgacdeployment -local

stsadm -o addsolution -filename DocumentLibraryReview.wsp
stsadm -o deploysolution -name DocumentLibraryReview.wsp -allowgacdeployment -local

stsadm -o addsolution -filename BudgetingTrackingMultipleProjects.wsp
stsadm -o deploysolution -name BudgetingTrackingMultipleProjects.wsp -allowgacdeployment -local

stsadm -o addsolution -filename ContactsManagement.wsp
stsadm -o deploysolution -name ContactsManagement.wsp -allowgacdeployment -local

stsadm -o addsolution -filename EventPlanning.wsp
stsadm -o deploysolution -name EventPlanning.wsp -allowgacdeployment -local

stsadm -o addsolution -filename JobRequisition.wsp
stsadm -o deploysolution -name JobRequisition.wsp -allowgacdeployment -local

stsadm -o addsolution -filename PhysicalAssetTracking.wsp
stsadm -o deploysolution -name PhysicalAssetTracking.wsp -allowgacdeployment -local

HOWTO pdficon Search

HOWTO pdficon Search
rakb200810141200

http://workerthread.wordpress.com/2008/01/03/configure-pdf-ifilter-in-wss-30/

http://blogs.msdn.com/joelo/archive/2007/01/12/why-wss-3-0-x64-and-moss-2007-x64-what-s-the-deal.aspx

1.Save the attached file pdficon_small.gif to c :\Program Files\Common Files\Microsoft Shared\Web Server extensions\12\TEMPLATE\images
2.Go to C:\Program Files\Common Files\Microsoft Shared\Web Server extensions\12\TEMPLATE\XML folder
3.Open the docicon.xml file
4.Add a line just above the </ByExtension>  <Mapping Key=”pdf” Value=”pdficon_small.gif” OpenControl=””/>
5.Save the file
6.Search Sharepoint, the results with pdf document will now have a visible .pdf icon
7.END

HOWTO: Building a Sharepoint Server 3.0 From Scratch

HOWTO: Building a Sharepoint Server 3.0 From Scratch
rakb200809301915

Phase 1.0 Sharepoint Setup

1. Install fresh copy of Windows Server 2003  With IIS
2. Run Windows Update, update all.
3. Download Sharepoint 3.0 With Service Pack1 http://www.microsoft.com/downloads/details.aspx?familyid=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en
4. Run Sharepoint.exe setup
5. Choose Basic (Choose Advance only if you have SQL Server 2005 installed already)
6. Wizard runs –>Services to be restarted IIS, Sharepoint Administration Service, Sharepoint Timer Service.
7. Task 1-10 Configuration
8. Configuration successful–>Click Finish
9. Internet Explorer opens to http://sasdcmpkg:8000/default.aspx (This indicates that Sharepoint was installed correctly). Don’t do anything yet on the site.
10. Open Sharepoint Central Administration from Administrative Tools
11. Perform Administrator Task 1-18 if applicable. (I think you can skip this but just do it anyway)
12. END

Phase 2.0 Sharepoint Setup for Department Site (CMP As an Example)

(Default IIS www port is port 80, in server sasdcmpkg, the port needs to be in 8000 for security reasons)

1. Open the default homepage http://sasdcmpkg:8000/default.aspx (This is the main or root site, don’t do anything special here, this is the root site where all the department subsites will reside)
2. Click the Home tab
3. At Home page, –>Click Site Actions –>Create
4. Under Web Pages –>Click Sites and Workspaces
New Sharepoint Site Page
Title/Description=CMP Sharepoint
Website= http://sasdcmpkg:8000/cmp
Template=Custom –>Choose Team Worksite
Permission=Select Use unique permission

Navigation=NO, Display this site on the Quick Launch of the parent site
Navigation=NO, Display this site on the top link bar of the parent site
Navigation Inheritance=NO, Use top link bar from the parent site
5. Setup Group for this site
Visitor=Use Existing Group
Members=Create a New Group-CMP Sharepoint
Owners=Create a New Group -CMP Owners
6. END

Phase 3.0 Sharepoint Setup for Subsites within the Department Site

1. Click the Home tab
2. At Home page, –>Click Site Actions –>Create
3. Under Web Pages –>Click Sites and Workspaces
New Sharepoint Site Page
Title/Description=TeamEng
Website= http://sasdcmpkg:8000/cmp/TeamEng
Template=Custom –>Choose Team Worksite
Permission=Select Use same permission
Navigation=YES, Display this site on the Quick Launch of the parent site
Navigation=YES, Display this site on the top link bar of the parent site
Navigation Inheritance=YES, Use top link bar from the parent site
NOTE: Repeat steps 1-4 to create additional subsites within the department. take note of the 3 YES answers for the subsites.  This is the option to make the Top Link Bar to be visible on the Department Website.
4. END

Phase 4.0 Sharepoint Search Troubleshooting
If for some reason the search feature is not working, you need to stop and restart the spsearch service from the command line using stsadm.exe.  Do not use the Sharepoint Central Administration site to restart the Search Service or you will need the sqlcmd.exe to drop and create the table which you normally don’t have yet.

1. At the command prompt: type net stop spsearch (to Stop Sharepoint Search Engine)
2. At the command prompt: type net start spsearch to Start Sharepoint Search Engine)
3. Open command prompt, go to folder C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
4. At the command prompt : type stsadm.exe –O spsearch –action fullcrawlstop (to stop Search Engine Crawl)
5. At the command prompt : type stsadm.exe –O spsearch –action fullcrawlstart (to start Search Engine Crawl)
6. Test Search in Sharepoint Website
7. END

Phase 5.0 Enable .pdf Search in Sharepoint

Microsoft Reference: kb927675 http://support.microsoft.com/kb/927675
1. Read/Perform kb927675
2. Install Adobe PDF iFilter plugin
3. Add registry key mentioned in kb927675
4. In command prompt: type net stop spsearch (to Stop Sharepoint Search Engine)
5. In command prompt: ype net start spsearch to Start Sharepoint Search Engine)
6. Open command prompt, go to folder C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
7. In command prompt : type stsadm.exe –O spsearch –action fullcrawlstop (to stop Search Engine Crawl)
8. In command prompt : type stsadm.exe –O spsearch –action fullcrawlstart (to start Search Engine Crawl)
9. Test Search in Sharepoint Website
10. END

Phase 6.0 Sharepoint Backup

1. Create a folder c:\backup to contain the backup file (this can be a share drive)
2. Go to c:\Program Files\Common Files\Microsoft Shared\web server extension\12\Bin
3. Open command prompt inside the Bin folder
4. Type stsadm.exe -O backup -url http://sasdcmpkg -filename c:\backup\fullfarmbackup.dat
5. END

Phase 7.0 TTRM (Time to Read The Manual)

1. Watch the Video Demo from Microsoft to get the big picture of sharepoint.
http://office.microsoft.com/en-us/sharepointtechnology/HA102055631033.aspx
2. On the top right corner of the browser while in Sharepoint Site click the blue button with a question mark. The information there will jumpstart your way in creating/modifying your Sharepoint site.
3. SharepointHosting.com created many helpful video tutorials, watch each one if you don’t want to read the manual. (I did). There is a bug in the flash player, you have to click the slider button once and then click the play button or else it will just sit there and do nothing. Great tutorials.
http://www.sharepointhosting.com/video_tutorials.html
4. For the brave and the hungry to customize Sharepoint 3.0, here’s the advance topics.

http://technet.microsoft.com/en-us/windowsserver/sharepoint/default.aspx
http://office.microsoft.com/en-us/sharepointtechnology/FX100503841033.aspx?ofcresset=1

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

http://technet.microsoft.com/en-us/office/sharepointserver/default.aspx

http://wss.collutions.com/default.aspx

http://www.usingsharepoint.com/default.aspx
http://www.wssdemo.com/default.aspx

Phase 8.0 Building the Knowledge Base Site
I’m always fascinated with how Microsoft built their Knowledge Base System. You search google for an error and then a kbNumber comes up with the information to fix your problem. How simple and smart is that.  Well, we have that here now in SAS Sharepoint. With proper planning of the Wiki site (I call it Knowledge Base), we can do the same here at SAS. 

So how can we come up with a Numbering System? 

I propose this KB numbering system: cmpkb200809300501

Why? Because later on, we can configure the Sahrepoint engine for a wildcard search ie. cmpkb*, or *kb2008 etc. (out of the box, wildcard is not supported)

cmpkb200809300501

Meaning:

cmp-department

kb-knowledge base

2008-year

09-month

30-day

0501-time

TEMPLATE:
TITLE
kbNumber
SYMTOMS
CAUSE
RESOLUTION
MORE INFORMATION
REFERENCE
KEYWORD
AUTHOR

Using a timestamp numbering system is a lot easier and no need to manage the numbers in a database.  There will be no duplicate kb number in your department for as long as you write the time you created the document in 24h format.  You don’t need to ask somebody about what to number your kb.  (TRIZ 40 Principle- Self-Service).

CONCLUSION:
In my opinion, the out of the box configuration of Sharepoint 3.0 is more than enough for SAS needs. We just need to establish a good backup and recovery plan. There is no limit to the size of the Windows Internal Database of Sharepoint 3.0 according to  Microsoft. The only good reason why some administrators use SQL2005 instead of the built in SQL database are scalability and backup method in SQL2005 are better. The location of the SQL database is in this folder C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data (not in the usual SQL data location)

The only customization that you have to do from out of the box is to install the Adobe iFilter mentioned in Phase 5.0 above.  What this filter do is index the text inside the .pdf file just like the default feature of indexing .doc, .xls, .ppt and more. Other than that, once you uploaded your documents to Sharepoint, wait for 5 minutes, perform a search and voila!, your document is found.

Another thing to consider is implementing 5S in the design of your Sharepoint Site.  Do it right the first time and you don’t have to undo the things your team doesn’t like later.  I normally uses the folowing guidelines:

1. What is the purpose of the site? Define this purpose and build on top of it. ie. Effective Team Collaboration
2. Use “segmentation” (TRIZ 40 Principle-Segmentation) , divide your department into smaller groups. ie. By SDWT
3. Use the “10 sec rule”, find what I can do in the site in 10 seconds.
4. Use the “3-click rule”, find any information/document in 3-mouse clicks. (not counting the search engine)

5. Before uploading a document:

o Tidy up the contents

o Provide a descriptive filename

6. Use a third person to test your site and ask how confusing it is. Ask for the negative comments, write it down and then fix it.

7. As DMAIC taught us, C-stands for Control.  manage your site everyweek. In Sharepoint, everyone in your team is a contributor and they will add anything without much thinking, let them do that (no limitations) but manage it effectively.  Keep an eye on the progress of the site. 

HOWTO: Enable .pdf search in Sharepoint 3.0 Site

HOWTO: Enable .pdf search in Sharepoint 3.0 Site

rakb200809300740
Microsoft Reference: kb927675 http://support.microsoft.com/kb/927675
1. Read/Perform kb927675
2. Install Adobe PDF iFilter plugin
3. Add registry key mentioned in kb927675
4. In command prompt: type net stop spsearch (to Stop Sharepoint Search Engine)
5. In command prompt: ype net start spsearch to Start Sharepoint Search Engine)
6. Open command prompt, go to folder C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
7. In command prompt : type stsadm.exe –O spsearch –action fullcrawlstop (to stop Search Engine Crawl)
8. In command prompt : type stsadm.exe –O spsearch –action fullcrawlstart (to start Search Engine Crawl)
9. Test Search in Sharepoint Website
10. END

HOWTO: Enable Sharepoint .chm Upload

HOWTO: Enable Sharepoint .chm Upload

In STS 1.0 you could upload to a document library any file you liked. This obviously had the drawback that you could upload a script (say) and by clicking on it start it carrying out its functions. The usual way round this was for the Administrator to request that such “dangerous” file types (scripts, exes etc.) should be zipped and then the zip file uploaded to the document library.

In WSS there is a set (long) list of file types that can not be uploaded to a document library.

This file () can of course be amended by the administrator – usually I suspect to reduce the list of restricted file types rather than to increase the number. As I wrote enough the default list is *very* long.

The file is ….60/CONFIG/DOCEXTFL.XML

To change the list of non-uploadable files you can either amend the file itself (and probably do IISRestart to make it work) or you can use the User Interface *on the server* as follows (the example being removing chm files from the list).

1. Programs
2. Administrative Tools
3. Open SharePoint Central Administration
4. Under Security Configuration, click Manage blocked file types
5. Remove the line for CHM and click OK

HOWTO: Enhance Command Prompt Sharepoint stsadm.exe

HOWTO: Enhance Command Prompt Sharepoint stsadm.exe
rakb200810010626
Run command line program using cmd.exe anywhere in your computer.
Example: stsadm.exe -O backup -url http://vw2003r2sp -filename B:\_Backup\fullfarmbackup2.dat
In order for this to work, you have to execute the stsadm.exe inside the folder C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
FIX: Add System Variables Path
1. Open Windows Explorer
2. Click Advanced Tab
3. Click the Environment Variables button
4. Under System Variables, Click New
5. Variable Name=Enter Path
6. Variable Value=Enter C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
Now, when you open the cmd prompt, you can right away execute
stsadm.exe -O backup -url http://vw2003r2sp -filename B:\_Backup\fullfarmbackup2.dat -overwrite without going to the directory.
stsadm.exe -help
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Administrator.VDOMAIN>stsadm.exe -help
Usage:
           stsadm.exe -o <operation> [<parameters>]
           stsadm.exe -help [<operation>]
Operations:

           activatefeature
           addalternatedomain
           addcontentdb
           addpath
           addpermissionpolicy
           addsolution
           addtemplate
           adduser
           addwppack
           addzoneurl
           authentication
           backup
           backuphistory
           binddrservice
           blockedfilelist
           canceldeployment
           changepermissionpolicy
           copyappbincontent
           createadminvs
           creategroup
           createsite
           createsiteinnewdb
           createweb
           databaserepair
           deactivatefeature
           deleteadminvs
           deletealternatedomain
           deleteconfigdb
           deletecontentdb
           deletegroup
           deletepath
           deletepermissionpolicy
           deletesite
           deletesolution
           deletetemplate
           deleteuser
           deleteweb
           deletewppack
           deletezoneurl
           deploysolution
           deploywppack
           disablessc
           displaysolution
           email
           enablessc
           enumalternatedomains
           enumcontentdbs
           enumdeployments
           enumgroups
           enumroles
           enumservices
           enumsites
           enumsolutions
           enumsubwebs
           enumtemplates
           enumusers
           enumwppacks
           enumzoneurls
           execadmsvcjobs
           export
           extendvs
           extendvsinwebfarm
           forcedeletelist
           getadminport
           getproperty
           getsitelock
           getsiteuseraccountdirectorypath
           geturlzone
           grantiis7permission
           import
           installfeature
           listlogginglevels
           localupgradestatus
           managepermissionpolicylevel
           mergecontentdbs
           migrateuser
           provisionservice
           refreshdms
           refreshsitedms
           registerwsswriter
           removedrservice
           removesolutiondeploymentlock
           renameserver
           renamesite
           renameweb
           restore
           retractsolution
           retractwppack
           scanforfeatures
           setadminport
           setapppassword
           setconfigdb
           setlogginglevel
           setproperty
           setsitelock
           setsiteuseraccountdirectorypath
           setworkflowconfig
           siteowner
           spsearch
           spsearchdiacriticsensitive
           syncsolution
           unextendvs
           uninstallfeature
           unregisterwsswriter
           updateaccountpassword
           updatealerttemplates
           updatefarmcredentials
           upgrade
           upgradesolution
           upgradetargetwebapplication
           userrole
Examples:
stsadm.exe -o addpath -url http://server/sites -type wildcardinclusion
stsadm.exe -o adduser
           -url http://server/site
           -userlogin DOMAIN\name
           -useremail [email protected]
           -role reader
           -username “Your Name”
           -siteadmin
stsadm.exe -o backup -url http://server/site -filename backup.dat -overwrite
stsadm.exe -o backup -directory c:\backup -backupmethod full
stsadm.exe -o createsite -url http://server/site
           -ownerlogin DOMAIN\name
           -owneremail [email protected]
stsadm.exe -o createweb -url http://server/site/web
stsadm.exe -o deletesite -url http://server/site
stsadm.exe -o deleteweb -url http://server/site/web
stsadm.exe -o enumsites -url http://server
stsadm.exe -o enumsubwebs -url http://server/site/web
stsadm.exe -o enumusers -url http://server/site/web
stsadm.exe -o extendvs -url http://server:80
           -ownerlogin DOMAIN\name
           -owneremail [email protected]
stsadm.exe -o renameweb -url http://server/site/web1 -newname web2
stsadm.exe -o restore -url http://server/site -filename backup.dat
stsadm.exe -o restore -directory c:\backup -restoremethod overwrite
stsadm.exe -o setconfigdb -databaseserver server
stsadm.exe -o unextendvs -url http://server
For information about other operations and parameters,
use “stsadm.exe -help” or “stsadm.exe -help <operation>”
C:\Documents and Settings\Administrator.VDOMAIN>

HOWTO: WSS3.0 Extending Search

REFERENCE:
http://www.knowledge-management.com/news/v4n11/spssearch.html
http://blogs.msdn.com/marioha/archive/2006/02/17/533946.aspx

Enabling Wildcard Search in Sharepoint
This walkthrough will guide  you how to enable wild search using SPS, you need to do the following:

1.Export the search result web part.
2.Customize the DWP file, add query to enable the wild search criteria
3.Import the web part back to SPS and drop it within search page area.

Here are the details:

1.Go to your search page. By default, you won’t be able to modify it, go to this link to enable the shared mode
http://nama_server/search.aspx?mode=edit&view=shared
2.Modify the Shared Page, and export the search result Web Part (just save it in your desktop, by default it has *.dwp extension)
3.The Webpart file (DWP) is basically XML File, so you can open it using Notepad. Go find this section : “QueryTemplateWherePart”
4.Add the following code in the END of the section to enable the wide search : OR CONTAINS(“urn:schemas-microsoft-com:sharepoint:portal:profile:PreferredName”, ‘”%__keywordinput__%”‘) RANK BY COERCION(multiply, 0.01)
OR CONTAINS(#WeightedProps, ‘”%__keywordinput__%”‘)
5.Save the file, go back to your sharepoint modify page – Add Web Parts – Import
6.Drop your modified search result web part to your search page. And that’s all, hope this help…
Secrets of the SharePoint Search Results Revealed – Mauro Cardarelli

From a Microsoft perspective, 2004 was the year of SharePoint Portal Server. Organizations around the world have implemented SharePoint-based solutions for more effective knowledge management and better team collaboration. It is becoming the single source for corporate content… unless, of course, you are trying to find something! I’ve equated the SharePoint search results with my seven year old daughter’s room: I know what I’m looking for is in there somewhere; I just can’t find it. This article is intended to help you better leverage SharePoint’s search results… I’ve given up on my daughter’s room.

Introduction

You’ve created a portal site for your organization. You put documents in document libraries, enabled discussions via discussion threads, and implemented ifilters to include additional content like pdf’s. You have configured SharePoint to crawl your file shares, public folders, and external websites. All this content is searched as part of your portal’s search interface. What a mess! Don’t get me wrong; the search engine is great. It always finds the proper results. Sometimes, I just have trouble understanding how to use this data.

Although it isn’t obvious, SharePoint exposes a great deal of additional search flexibility behind its standard search web part. Let’s look at how to find these parameters.

Viewing SharePoint’s Search Parameters

Follow these steps to export SharePoint’s search parameters to an XML file.

(1) In your browser, go to the following path:
http:///search.aspx?mode=edit&view=shared

(2) You’ll see the context menu ‘Modify My Page’; select ‘Shared View’

(3) You’ll see the context menu ‘Modify Shared Page’; select ‘Design This Page’

(4) Your search page is now in design mode. On the Search Results web part, click the down arrow and select ‘Export…’

(5) Save the file to your hard drive. It will create a .dwp file (this is a web part file extension). The contents are standard XML. You can make changes to this file. It is strongly recommended that you save a copy of this original file.

For the Beginner

If you do nothing else with the search parameter file, add the following line (you can place it above the ‘GroupbyList’ line):

<OpenNewWindowForMatchingItems xmlns=”urn:schemas-microsoft-com:sharepoint:DataResultBase”>true</OpenNewWindowForMatchingItems>

This parameter tells SharePoint to pop up a new window for each selected search item. One of the frustrating behaviors of standard SharePoint search results is that when you select a search item the results are shown in the same window. You lose your connection to your original search list. The only way back is the IE ‘Back’ button or re-executing the search. The method above forces a new window. You can look at the results, close the window, and return to your search list. This has generated a few “Wow’s” in my demonstrations.

For the Bold

Ever wonder why SharePoint always shows the top 40 results? It is a property in the search results file called ‘MaxMatchingItemsNumber’. You can change it by altering its value. The default sort is stored in ‘DefaultSortBy’. You can alter ‘ColumnURIs’ to control the header associated with search results (i.e. you can remove Author, the default middle column, and replace it with the content type).

I suggest that you spend some time and study the XML. It offers some interesting insight into what SharePoint is doing with its search results.

For the Truly Brave

This section is intended for those who are comfortable enough with SharePoint to create more advanced search solutions.

I believe the .dwp file’s most interesting method is the ‘QueryTemplateWherePart’. It contains the logic that controls relevancy as well as scope. If you are truly brave, you can alter the order of the search results as well as limit scope to a specific portal region. As an example, my portal’s search results page contains many results web parts. I have one for just People; another searches technology topics only. I’ve done this by creating unique search parameter files. Note, this works naturally with the standard SharePoint search box… all with no custom code!

Above, I showed how to add a method to pop up search items in a new window. You may wonder what else is ‘missing’ from the standard search file. The list of available methods is at:

http://msdn.microsoft.com/library/en-us/spptsdk/html/cDataResultBase.asp?frame=true

I found this list in my investigation and have actually used a few methods. One that you might want to try is the ‘ShowRankForEachItem’ method. When set to ‘true’, it adds the result rank next to each search item. This is especially useful when the results include several site groupings.

Implementing Your Changes

Save any changes to your modified .dwp file. Don’t forget to change the ‘Title’ node to a name that distinguishes it as a custom version (i.e. ‘KMA Custom Search Results’).

Follow the steps above to place yourself back in design mode.

(1) Delete the current Search Results web part. You can do this through its context menu

(2) Select the ‘Add Web Parts’ from the ‘Modify Shared Page’ context menu; select ‘Import’ from its list

(3) Browse for your modified .dwp file and import it

(4) Drag your web part onto the page under the Advanced Search web part

(5) Go to the homepage and execute a search You can continue to test changes to your web part by re-executing the steps above.

Summary

You can greatly enhance the user experience associated with SharePoint search results by altering and adding a few basic parameters. While these changes are not a substitute for proper information tagging, they offer an easy way for more effectively connecting employees with organizational content.

HOWTO: WSS3.0 Installing Site Template

To install this download:
=========================================================
Note: To complete the following installation, you must
have Administrator rights to the Windows SharePoint
Services site on which it is to be installed.
1. Download the site template EXE file to your computer.
2. Run the EXE file to unpack the template file to a
   location on your computer.
3. Select the template file, <template_name>.stp, from
   the extracted distribution for the application template
   you wish to install.
4. Log into your SharePoint site as the site Administrator.
5. From the Site Actions drop-down menu in the top right,
   select Site Settings.
6. Under the Galleries section, select Site templates.
7. Select Upload to load an application template into this
   SharePoint site.
8. Browse to the <template_name>.stp file from the distribution
   and select Open. If you have several application templates
   to load into your site, you can use the Upload Multiple
   Files… option to load them all at once.
9. Click Ok to complete the upload of the application template
   to your SharePoint site.

=========================================================
Instructions for use:
=========================================================
1. Log into your SharePoint site as the site Administrator.
2. From the Site Actions drop-down menu in the top right,
   select Site Settings.
3. Under the Site Administration section, select Sites and
   Workspaces.
4. Select Create to create a new site using a site template.
5. Complete the new SharePoint site information. In the
   Template Selection section, select the Custom tab. Any
   application templates that have been uploaded will be
   listed here.
6. Select the template to use for this site and click Create.
7. A site has now been created using the application template.

=========================================================
To remove this download:
=========================================================
Note: To complete the following removal, you must have
Administrator rights to the Windows SharePoint Services
site. This process will not remove the templates from
any sites that were already created using this template.
It will only prevent users from creating new sites based
on the template.
1. Log into your SharePoint site as the site Administrator.
2. From the Site Actions drop-down menu in the top right,
   select Site Settings.
3. Under the Galleries section, select Site templates.
4. In the list of site templates, find the application
   template you wish to remove and click the Edit link.
5. Confirm that this is the application template you wish
   to remove. If so, select Delete Item.
6. Click Ok to confirm the deletion.
7. The application template is now unavailable to SharePoint
   sites and has been removed from your SharePoint site
   template gallery.

HOWTO: Moving WSS3 Database to a different drive

HOWTO: Moving WSS3 Database to a different drive (out from c:\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data)
rakb200810080402

Why move the default location of the SQL Content db and the SQL Search db to a different drive?
The default SQL db location for Sharepoint 3.0 is in c:\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data which is great for a site that is not heavily used like a home server or a small office intranet.  But when Sharepoint is being deployed to an intranet that is potentially large ie. SAS, the Content and Search DB needs to be relocated away from c:\drive (system drive).  This files can grow so fast that out of the blue, the system drive will run out of space and crash — BSOD. There is no size limit for the SQL Embeded version of Sharepoint DB, so the physical limit will be the drive space and that is the reason why those 2 growing files needs to be relocated on a different drive. If we relocate those 2 files to a 2nd physical drive (not a partition), the site will perform faster and easier to recover during a disaster.

An Example of a good Sharepoint Server hardware configuration:
Memory=4GB
Drive0=c:\drive
Drive1=c:\drive mirror
Drive2=d:\drive
Drive3=d:drive mirror
1. Install SQL Server Native Client Tool, Download Here
2. Install SQL Command Line Tool, Download Here
3. Create a wss folder in c:\drive to hold the movesharepoint.bat and sharepoint.sql
4. Create a sharepointdb folder in d:\drive to hold the SQL Server .mdf and .ldf files
5. Create a batch file and call it movesharepoint.bat (Courtesy from Ken Warren)
NOTE: The highlighted items correspond to the changes I made on the script to match the drive letter of my serverG:=my c:drive
W:=my 2nd SCSI drive where I wanted to.mdf/.ldf to reside.
PE1550e=my Server Name
————————————-
net stop mssql$microsoft##ssee
copy G:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\WSS_Content*.* W:\SharePointDB\*.*
copy G:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\WSS_Search*.* W:\SharePointDB\*.*
net stop SPSearch
net start mssql$microsoft##ssee
“G:\Program Files\Microsoft SQL Server\90\Tools\binn\sqlcmd” -S \\.\pipe\mssql$microsoft##ssee\sql\query -E -i G:\wss\sharepoint.sql
net start SPSearch
————————————-
6. Creat a sql script and name it sharepoint.sql
————————————-
EXEC sp_detach_db @dbname = ‘WSS_Content’
go
EXEC sp_detach_db @dbname = ‘WSS_Search_PE1550E’
go
EXEC sp_attach_db @dbname = ‘WSS_Content’, @filename1 = ‘W:\SharePointDB\WSS_Content.mdf’, @filename2 = ‘W:\SharePointDB\wss_content_log.ldf’
go
EXEC sp_attach_db @dbname = ‘WSS_Search_PE1550E’, @filename1 = ‘W:\SharePointDB\WSS_Search_PE1550E.mdf’, @filename2 = ‘W:\SharePointDB\WSS_Search_PE1550E_log.ldf’
go
————————————-

7. Open Sharepoint Central Administration –>Application Management Tab–>Click Content Databases
8. Click on the link for WSS_Content
9. In the Database dropdown, select Offline, Click OK
10. Minimize this Sharepoint Central Administration Page, you will need it later to place the db back Online.
11. Verify if you created the folder d:\sharepointdb mentioned in Step 4 above.
12. Go to the script folder c:\wss
13. Open command prompt on this folder
14. At the command prompt, type movesharepoint.bat
15. After the script is complete, Open Sharepoint Central Administration –>Application Management Tab–>Click Content Databases
16. Click on the link for WSS_Content
17. In the Database dropdown, select Ready, Click OK
18. Go to d:\sharepoint folder and try to rename WSS_Content.mdf, if you get an error, the move was successful
19. Go to d:\sharepoint folder and try to rename WSS_Search_Servername.mdf, if you get an error, the move was successful
20. Upload files to your sharepoint site and monitor the growth size of the files WSS_Content.mdf  WSS_Search_Servername.mdf
Here’s the command prompt snapshot of a succesful movesharepoint.bat

G:\wss>movesharepoint
G:\wss>net stop mssql$microsoft##ssee
The Windows Internal Database (MICROSOFT##SSEE) service is stopping.
The Windows Internal Database (MICROSOFT##SSEE) service was stopped successfully
.

G:\wss>copy G:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\WSS_Content*.* W:\Share
PointDB\*.*
G:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\WSS_Content.mdf
G:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\WSS_Content_log.LDF
        2 file(s) copied.
G:\wss>copy G:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\WSS_Search*.* W:\ShareP
ointDB\*.*
G:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\WSS_Search_PE1550E.mdf
G:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\WSS_Search_PE1550E_log.LDF
        2 file(s) copied.
G:\wss>net stop SPSearch
The Windows SharePoint Services Search service is stopping…….
The Windows SharePoint Services Search service was stopped successfully.

G:\wss>net start mssql$microsoft##ssee
The Windows Internal Database (MICROSOFT##SSEE) service is starting.
The Windows Internal Database (MICROSOFT##SSEE) service was started successfully
.

G:\wss>”G:\Program Files\Microsoft SQL Server\90\Tools\binn\sqlcmd” -S \\.\pipe\
mssql$microsoft##ssee\sql\query -E -i G:\wss\sharepoint.sql
G:\wss>net start SPSearch
The Windows SharePoint Services Search service is starting…
The Windows SharePoint Services Search service was started successfully.

G:\wss>