SharePoint & more
SharePoint 2007
Microsoft SharePoint reporting services SSRS or CRM ASSERT: Assertion failed! un-named assertion fired for component processing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException
Jul 16th
You may receive these errors when generating reports (often large reports) through Microsoft Sharepoint Reporting Services SRSS or Microsoft CRM.
This error appears in the report server log:
ASSERT: Assertion failed! un-named assertion fired for component processing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException
This error will appear in your web browser when accessing the report:
Reporting Services Error An internal error occurred on the report server. See the error log for more details (rsInternalError)
Solution:
Install SQL Server 2005 Service Pack 3
The cause is SQL server timing values may be incorrect when you use Cool’n'Quiet technology in AMD processors or SpeedStep technology in Intel processors. It can also occur on virtual servers on VMware (Intel or AMD).
Here are some links I hope you may find useful:
Link 1:
http://blogs.msdn.com/b/mariae/archive/2007/12/10/reporting-services-internal-error.aspx
Link 1: Mentions that AMD Cool’n’Quiet settings is the culprit, on further reading on the internet, I have found out that this can occur on intel systems (SpeedStep technology) as well.
Link 2:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;931279
Link 2: States that the issue is a drift may occur between CPU frequency values and the problem was first corrected in SQL 2005 SP 3.
The Microsoft KB article 931279 states that this can occur if we use the CPU stepping or various Windows OS ‘power schemes’ settings. While the former (CPU stepping) is a bit more tricky to check, it would be worth checking the power scheme settings (Start>run>powercfg.cpl).
Link 3:
http://support.microsoft.com/kb/955706/en-us (SQL 2005 SP 3)
Link 3 contains a list of bugs that are fixed by SP3. There evidence that it fixes the SQL server timing values – KB article 931279 (Link 2).
SharePoint disable loopback check (DisableLoopbackCheck dword in registry)
May 24th
Ive found this very handy.. recently, I was working on a server and we were trying to access the local SharePoint site http://127.0.0.1 or http://nameoflocalserver/pages/default.aspx and I was constantly prompted for the username and password. in SharePoint 2010 it can really annoy you by not accepting your username password credentials in the popup window.
Its a ‘feature’ on the server that you need to disable as a workaround..
You would need to create a DWORD registry key in the registry called DisableLoopbackCheck and set it to 1.
Follow these steps:
Click Start, click Run, type regedit, and then click OK
In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value.
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1 and then click OK.
Quit Registry Editor, and then restart your computer.
For more information about this, click the following article number to view the article in the Microsoft Knowledge Base: 281308 (http://support.microsoft.com/kb/281308/ ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name.
MOSS SharePoint 2007 on Server 2008 R2 – Microsoft KB 962935
Apr 9th
When you are installing MOSS SharePoint 2007 on a Windows 2008 R2 server, you may receive an error to look up Microsoft KB 962935
The possible cause is because you are installing MOSS2007 with SP 1 on a Windows 2008 R2 server.
To overcome this, you have two options:
1. Slip stream – extract and update your install with MOSS 2007 SP 2
- Extract OfficeServerwithSP1.exe by executing “OfficeServerwithSP1.exe /extract:C:\MOSS\”
- Extract officeserver2007sp2-kb953334-x64-fullfile-en-us by executing “officeserver2007sp2-kb953334-x64-fullfile-en-us /extract:C:\MOSSsp2\”
- Copying all files from “C:\MOSSsp2\” to “C:\MOSS\Updates\”
2. Download MOSS 2007 with SP2
- For 32bit
http://www.microsoft.com/downloads/details.aspx?FamilyId=2E6E5A9C-EBF6-4F7F-8467-F4DE6BD6B831&displaylang=en
- For 64bit
http://www.microsoft.com/downloads/details.aspx?FamilyId=3015FDE4-85F6-4CBC-812D-55701FBFB563&displaylang=en
Creating custom SharePoint MOSS 2007 & WSS 3.0 themes
Mar 13th
I was looking around for some reading today and I thought of collecting information on whats out there on SharePoint skinning, SharePoint customisation of themes and master pages. There are a few articles on the web that I have read before and would like to share them with you. May I suggest you bookmark this article so you can refer back when you need. I will add more links as I come across them. You may be able to share your favourites with me and I will edit this article to include your valuable suggestions! Thanks!
SharePoint Central Administration High Availability, Load Balancing & General Recommendations
Mar 9th
A few questions have come up about having dual SharePoint Central Administation servers in a farm. In short, it is possible to run two CAs in a farm. (It is Microsoft supported).
In a 5 server farm (3 WFE, 1 Index, 1 CA), we may feel the need to load balance the CAs with Microsoft’s Network load balancing NLB.
I found a good article that helped reinforced some concepts..
http://www.harbar.net/articles/spca.aspx
Configure SharePoint search pdf files with a free ifilter
Feb 4th
1. Download Free ifilter from: http://download.adobe.com/pub/adobe/acrobat/win/all/ifilter60.exe
You can also download Download Adobe Reader 9.0 which contains the ifilter. Necessary for x64 bit systems. http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025
2. Run the newly downloaded file and go through the install wizard with your preferences.
3. Enable the pdf extension in SharePoint. Central Administration > SharedServices > Search Settings > File Types >New File Type
4. Enter ‘pdf’ as a file extension and Click OK.
5. Right click and save the pdf icon from http://www.adobe.com/misc/linking.html
6. Add the Acrobat pdf icon to the SharePoint templates directory. Copy the Acrobat PDF picture called pdficon_small.gif in the 12 Hive\TEMPLATE\IMAGES folder, e.g. %programfiles%\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\IMAGES.
7. Open the 12 Hive\TEMPLATE\XML\DOCICON.XML file.
Find the <DocIcons.ByExtension> part
Add the following: <mapping Key=”pdf” Value=”pdficon_small.gif” OpenControl=”" />
Save
8. Run
net stop osearch
net start osearch
9. Perform a full crawl to reindex your pdf files.
The directory C:\Inetpub\wwwroot\wss\VirtualDirectories\80 is already being used by another IIS Web Site. Choose a different root directory for your new Web application.
Jan 13th
When creating a new web application, you may experience this error:
The directory C:\Inetpub\wwwroot\wss\VirtualDirectories\80 is already being used by another IIS Web Site. Choose a different root directory for your new Web application.
Solution:
1. Ensure you have a proper dns name / entry in the hosts file of your server for the new url you are wanting to create.
2. Ensure you have typed in the ‘host header’ typed in when creating the new web application.
3. If this doesnt work, open IIS Manager – Start>run> inetmgr> and verify the home directory – it could be located on a different drive.
Content type ‘0×01010007FF3E057FA8AB4AA42FCB67B453FFC100E214EEE741181F4E9F7ACC43278EE811′ not found in web
Jan 12th
You may sometimes see this error when creating a new page in a SharePoint MOSS 2007 publishing portal.
“Content type ‘0×01010007FF3E057FA8AB4AA42FCB67B453FFC100E214EEE741181F4E9F7ACC43278EE811′ not found in web ‘http://yoururl’
Two step solution:
1. Go to Central Admin, Application Management, User Permissions for Web Application.
Ensure “Use Client Integration Features” and “Use Remote Interfaces” are enabled.
2. Go to Central Admin, Application Management, Policy for Web Application.
Add your user account with Full Control and Finish!
You may have to do an IISRESET and you should be able to create new pages.
SharePoint MOSS Shared Services SSP delete unprovisioning
Jan 9th
When you try to delete a SharePoint Shared Services Provider – SSP, you may notice the SSP stuck with unprovisioning as its state. Eg. SharedServices1 (Unprovisioning)
Possible Cause: The SSP database has been deleted in SQL and SharePoint is unable to delete the SSP.
Some objects may still be dependent on the configuration database, hence you are unable to delete the SSP.
Solution: Manually delete the SSP by the following stsadm command:
stsadm -o deletessp -title “ssp_name”
You may also want to check if your SSP is providing services to other farms.
1. Go to Central admin > Application Management > Manage Shared Services between Farms
2. Disable “This farm will provide shared services to other farms”
3. Enable “This farm does not participate in shared services between farms”
Try to delete the SSP again.
You may also receive this error:
“An object in the SharePoint administrative framework, “SharedResourceProvider Name=SSP Parent=SPFarm Name=MOSS”, could not be deleted because other objects depend on it. Update all of these dependants to point to null or different objects and retry this operation.
Solution: Identify the GUID of the SSP in SQL and then delete the configuration object by the GUID.
Perform the following steps to get the GUID of the unprovisioning SSP and then delete it:
1. Log into the SQL Management studio and go to the configuration database.
2. Expand the tables and open dbo.object
3. Update the following queryto your database name and run it to receive the GUID
SELECT * FROM [Name of your configuration database].[dbo].[Objects]where name like ‘Name of the Shared Services’
4. Run the following stsadm command
stsadm -o deleteconfigurationobject -id “GUID retrieved from object table in SQL database”
SharePoint Timer Job Administration
Sep 16th
I came across a solution to modify timer jobs from the Central Admin interface. This is the equivalent of using the stsadm -o setproperty command. The best part is you can modify your timer jobs without having to redeploy them!
When you install it, you will get a link in your Central Administration site to ‘Manage Timer Jobs’.
Wait! Theres more, you can also deploy your own custom timer jobs, update job properties and schedule all from this neat interface.
Read more and download here: http://sptimerjobadmin.codeplex.com
