SharePoint Pros

1. Go to Central Administration > Application Management page and provision a new web application on port 81. The url for this web will be http://SRV1:88.
   
2. Provision a new site collection using the template of your choice to the newly created web application (http://SRV1:88)
   
3. Go to the server that will be hosting the Reporting Service (SRV1)
   
4. Start the Reporting Service Configuration Wizard (All Programs >Microsoft SQL Server 2005 >Configuration Tools > Reporting Service Configuration
   
5. In the Instance Selection menu, enter SRV1 in the Machine Name and MSSQLSERVER in the Instance Name. Click Connect.
   
6. Verify “Service Status shows “Running” under the “Report Server Status”
   
7. Go to “Report Server Virtual Directory” page and set configuration as follows:
   

 

1. Verify that Report Manager Virtual Directory is grayed out. This may not grayed out until a new database is created in SharePoint integration mode.
   
2. Go to Windows Services Identity page and set configuration as follows:
   

1. Go to Web Service Identity page and set configuration as follows:
   

1. Go to Database Setup page and set configuration as follows:
   

1. Go to Central Administration > Application Management > Manage integration settings page and set configuration as follows:
   

Note: if you don’t see Configure Reporting Services Integration option on your Application Management, you need to make sure the feature is enabled.

1. Go to Central Administration > Application Management > Grant database access page and set configuration as follows:
   

1. Go to Central Administration > Application Management > Set server defaults page and set configuration as follows:
   

 

At this point you should be able to browse to http://SRV1:88/reportserver and see listing of site collections. It can take a long for the page to render time if you have many site collections. Our’s took about 30min for the page to come up.

 

1. Troubleshooting
   

Problem:

Reporting Services Error

An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help Error executing child request for /ReportServer/Pages/ReportViewer.aspx.

The type Microsoft.SharePoint.Portal.Analytics.UI.ReportViewerMessages, Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c does not implement IReportViewerMessages or could not be found

Resolution:

Add <remove key=”ReportViewerMessages” /> in the web.config located in C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\ReportServer.

You can verify the integration of Reporting Service with the SharePoint by uploading a report file to a SharePoint site and see if the report gets generated. You should test a bare minimum test report first.

Problem:

An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integration.

 

Resolution:

Add the DisableLoopbackCheck Registry Key to web front ends

1. Open the Registry Editor (regedit).
   
2. Open the following key: HKLM\System\CurrentControlSet\Control\Lsa.
   
3. Create a new DWORD value called DisableLoopbackCheck.
   
4. Set the value to 1.
   
5. Reboot the server.
   

Problem:

Report Server has encountered a SharePoint error (rsSharePointError) Get Online Help User cannot be found.


Resolution:

Follow directions from http://krichie.wordpress.com/2008/09/12/resetting-the-author-on-a-sharepoint-site-or-wherefore-art-thou-author-redux/

and

http://vspug.com/nrdev/2008/08/26/tip-report-server-quot-user-cannot-be-found-quot-error-fix/

Problem:

Reporting Services Add-in for Microsoft SharePoint Installation fails and rolls back. “Product: Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies — Installation failed” shows up in the event log.

Resolution:

1. Open the command window (Start>Run type cmd and press enter)

2. Navigate to the path where the installer (SharePointRS.msi) is stored

3. Execute SharePointRS.msi SKIPCA=1

4. CD to %temp%

5. Execute rsCustomAction.exe /i  to auto-configure the installed files.

So I am trying to restore a database to a sql cluster instance. I’ve done this many time so it should go without a hitch. When I ran the restore script “Restore database myDbName.bak …. with move …” I was hit with the following error:

Msg 5184, Level 16, State 2, Server DBServer\myInstance, Line 1

Cannot use file ‘O:\Databases\myDbName.mdf’ for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it.

Then I realizes that O: drive was recently added to the cluster. So I opened up my Cluster Administrator and checked the Resources. I right clicked “SQL Server (myInstance)” and clicked properties. Under the Dependencies tab, the O: Drive is missing in the “Resource dependencies:” box. So I take “SQL Server (myInstance)” offline, add the drives to the “Resource dependencies:” box and all is fine.

We recently migrated a SharePoint farm from one domain to another domain. Basically, our task was to migrate everything over from the old domain to the new domain. Our farm consists of 50 or so content databases (DBs) and well over 200 site collections plus Mysite site collections. We migrated from one set of servers to new set of servers.

The pre migration activities were as follows:

Create a new farm

Provision CA on the new farm

Provision SSP on the new farm

Provision site collections on the new farm

Delete content DBs from the new farm (stsadm –o deletecontentdb)

Back up and delete content DBs on the new farm (SQL BU and drop DB).

The only DBs we kept were iShare_config and central administration DB.

Mirror (SQL mirroring) content DBs from old farm to the new farm. This was done to reduce the down time. Doing content DB backup from the old and restore to the new will also work but would have taken a lot longer.

During the migration the follow steps were followed:

Lock content DBs on the old farm (stsadm –o setsitelock –url http://mydomain.com–lock noaddition)

Break SQL mirroring on SSP content DB.

Add old farm SSP content DB (stsadm –o addcontentdb) to the new farm

Restore SSP (stsadm -o restoressp. -title <SSP name>) on the new farm

Break SQL mirroring on Project server DBs (ProjectServer_Archive, ProjectServer_Draft, ProjectServer_Published, ProjectServer_Reporting)

Add Project server content DBs (stsadm –o addcontentdb) on the new farm

Delete /pwa from managed path and site collection on the new farm

Provision Project Server on the new farm

Re-link Project Workspaces on the new farm

Break the SQL mirror on the rest of the content DBs

Attach the old farm content DBs to the new farm

Verify sites

Unlock content DBs on the new farm (stsadm –o setsitelock –url http://mydomain.com –lock none)

Configure Reporting Services

        Re-deploy broken solutions

Re-publish infopath forms

Next time, I’ll go over some lessons learned from this project.

When you see the error below during site collection provisioning, you may need to clear the cache from all servers.

An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=Portal Parent=SPWebService is being updated by DOMAIN\XXXX, in the OWSTIMER process, on machine XXXX. View the tracing log for more information about the conflict.

First stop sharepoint timer job from all servers.

Go to C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID directory on all servers. Note guid is not the actual name of the directory but will have some hex values. Then delete all .xml file. This will leave cacahe.ini alone in the directory.

Open the file and change the number to 1. Save the file. Repeat on all servers.

Restart the timer job on all servers.

 

Here is a simple script to clear the cache if you manage a large farm.

You just need to change the value of temp to 1st 2 number of your GUID. In my case the guid id was 3d3e2311-2756-414e-32e4-3a45433dd421. So I am setting the temp to 3d*. And we have 6 servers (Server001 – Server 006) in the farm, excluding the sql and exchange server. Save as a batch file on one of the server and you should be good to go. You need to have sc http://support.microsoft.com/kb/251192 included in the Recourse kit. Your P: drive must not be in use.

 

set temp=3d*

sc \\SERVER001 stop “SPTimerV3″

sc \\SERVER002 stop “SPTimerV3″

sc \\SERVER003 stop “SPTimerV3″

sc \\SERVER004 stop “SPTimerV3″

sc \\SERVER005 stop “SPTimerV3″

sc \\SERVER006 stop “SPTimerV3″

pause

C:

cd C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\%temp%

del *.xml

echo 1 > cache.ini

pause

net use p: /delete

net use p: \\SERVER002\c$

P:

cd P:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\%temp%

del *.xml

echo 1 > cache.ini

C:

net use p: /delete

pause

net use p: \\SERVER003\c$

P:

cd P:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\%temp%

del *.xml

echo 1 > cache.ini

C:

net use P: /delete

pause

net use p: \\SERVER004\c$

P:

cd P:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\%temp%

del *.xml

echo 1 > cache.ini

C:

net use p: /delete

pause

net use p: \\SERVER005\c$

P:

cd P:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\%temp%

del *.xml

echo 1 > cache.ini

C:

net use p: /delete

pause

net use p: \\SERVER006\c$

P:

cd P:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\%temp%

del *.xml

echo 1 > cache.ini

C:

net use p: /delete

pause

sc \\SERVER001 start “SPTimerV3″

sc \\SERVER002 start “SPTimerV3″

sc \\SERVER003 start “SPTimerV3″

sc \\SERVER004 start “SPTimerV3″

sc \\SERVER005 start “SPTimerV3″

sc \\SERVER006 start “SPTimerV3″

C:

cd C:\

pause