skip to main |
skip to sidebar
Description:
In Microsoft Office SharePoint Server 2007, after initiating a full user profile import, the user profiles fail to import and the crawl log contains the following error: "The specified domain either does not exist or could not be contacted. (Exception from HRESULT: 0x8007054B)"
Solution:
Adding WINS addresses to the LAN Connection properties corrected this issue.
1.From the Index server: Control Panel > Network Connections > LAN Connection Properties > WINS tab
Add WINS server addresses
2.SSP Admin > User Profile and Properties > Import
Perform user profile importVerify import is successful
Description:
This blog post explains how to add a new portal to a SharePoint Portal Server 2003 farm having two front end web servers.
Solution:
Web Server #1
* From Windows Explorer: Create a directory on a non operating sytem drive to be used for the new IIS web site.
* From IIS Manager: Create a new web site, using the new directory as the home directory. Disable anonymous access.
* From SharePoint Portal Server 2003 Central Administration: SharePoint Portal Server > Portal Site and Virtual Server Configuration > Create a Portal Site Name: Give the portal a name, consider using host header or port number in name. Virtual Server: Select the new IIS web site. Site URL: e.g. http://webserver1:port Account Name, Email Address
Web Server #2
* From Windows Explorer: Create a directory on a non operating sytem drive to be used for the new IIS web site.
* From IIS Manager: Create a new web site, using the new directory as the home directory. Disable anonymous access.
* From SharePoint Portal Server 2003 Central Administration: Windows SharePoint Services > Virtual Server Configuration > Extend or Upgrade Virtual Server Provisioning Options > Extend and map to another virtual server Current Virtual Server: Verify this is set to the web site you want to extend Server Mapping: Select the virtual server that was created on web server #1 Wait for refresh cache on the other serverse to succeed and click ok.
Description:This blog post explains how to configure the Author managed property so that it may be used effectively in Search within an Office SharePoint Server 2007 environment.
Solution:
SSP Admin > Search Settings > Metadata Property Mappings > Managed Properties > Author
Step 1
Set the "Mappings to crawled properties" radio button to "Include values from a single crawled property based on the order specified." It is common to expose the Author property in search results, so don't "include all values from crawled properties mapped" because your search results will end up with mulitple names listed beside the search result and it will be difficult to distinguish which is really the author.Step 2Map the most relevant crawled properties to the Author managed property, and position them in the best possible sequence. Obviously, if authors are truly dilligent about maintaining the Office document Author property within the document itself , then this is best candidate for first position. However, in many organizations, this property is not actively maintained. SharePoint's Created By property isn't always an accurate indicator of who actually created the document, so this one also tends to fail as being a reliable first position candidate. In many cases, the best thing to do is to create a custom Author site column, make it required, and add it to all document content types. Then, map the corresponding crawled property as first position. This ensures that the Author information will be maintained to some degree by people touching the documents. Once the first position is set, then add and order the subsequent crawled properties.
Description:
During preparation for an upgrade to Microsoft Office SharePoint Server 2007, after running prescan.exe on a SharePoint Portal Server 2003 environment, the pre-upgrade report lists an error such as the one below.
06/04/2007 16:26:59 Error: Cannot get content database Id for SPSite: http://servername/sites/sitename06/04/2007 16:26:59 Microsoft.SharePoint.SPException: There is no Web named "/sites/sitename". ---> System.Runtime.InteropServices.COMException (0x81070504): There is no Web named "/sites/sitename". at Microsoft.SharePoint.Library.SPRequestInternalClass.OpenSite(String bstrUrl, Boolean bGetUrlOnly, String& pbstrServerRelativeUrl, Guid& pgSiteId, Int32& pOwnerID, Int32& pSecondaryContactID, DateTime& pdtLastContentChange, DateTime& pdtLastSecurityChange) at Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String& A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7) --- End of inner exception stack trace --- at Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String& A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7) at Microsoft.SharePoint.SPSite.c() at Microsoft.SharePoint.SPSite.get_ID() at Microsoft.SharePoint.PreupgradeReport.Scan.GetContentDBBySite(SPSite site, SPVirtualServer vs)
Solution:
Windows SharePoint Services 2.0 and SharePoint Portal Server 2003 each have their own approach to cleaning up orphaned records. The KB articles below provide information on related hotfixes and explain how to use command line utilities to clean up corrupted databases.
Windows SharePoint Services 2.0http://support.microsoft.com/kb/924881http://support.microsoft.com/kb/918744From: \program files\common files\microsoft shared\web server extensions\60\binTo Detect: stsadm -o databaserepair -url http://ServerName -databasename DatabaseName To Repair: stsadm -o databaserepair -url http://ServerName -databasename DatabaseName -deletecorruption
SharePoint Portal Server 2003http://support.microsoft.com/kb/919175http://support.microsoft.com/kb/918742From: \programfiles\Sharepoint Portal Server\BinTo Repair: spsadm repairorphans http://ServerName
I recently configured MOSS Search to index Lotus Notes. Here is an overview of the process.Preparation:* Lotus Notes server name* Lotus Notes database file name* List of fields you want to display in search results* Notes user logon file (e.g. user.id)* User credentials for installing Notes client
Steps:* Install Lotus Notes Client 6.0 to the SharePoint Index Server* From the index server, share the c:\program files\lotus\notes\data directory allowing WSS_WPG group access* From an existing workstation, copy a valid user id file to index server c:\program files\lotus\notes\data* Download the Lotus C++ API Toolkit 3.0I* Extract the files* Copy lcppn30i.dll to the index server, c:\program files\microsoft office servers\12.0\bin* Rename 1cppn30i.dll to 1cppn30.dll* From index server, c:\program files\microsoft office servers\12.0\bin, execute notessetup.exe* Specify the server name, database file, view, etc.* From index server, cmd prompt, net stop osearch, then net start osearch* SSP Admin > Search Settings > Content Sources: Configure content source for Lotus Notes* SSP Admin > Search Settings > Scopes: Configure scope for Lotus Notes content source* SSP Admin > Search Settings > MetaData Property Mappings: Create managed properties for those Lotus Notes properties that you want to search or display in search results* Search Center: Configure the search web parts and search results web parts (and related xml files) to display useful field when the search result item is coming from the Lotus content source
Lessons:* The notessetup.exe won't work with the 1cppn30i.dll file name, need to rename it to 1cppn30.dll* I used 6.0 Notes Client, because Notes Client 6.5 did not create a data directoryReferences:* Configure Office SharePoint Server Search to crawl Lotus Notes (Office SharePoint Server 2007 for Search)
* Using SharePoint 2007 to Index Lotus
* Secure crawls of Lotus Notes with SharePoint
* How to Configure Search to Honor Lotus Notes Security Settings
* MOSS2007 Search and Index Lotus Notes
* IBM software downloads (for Lotus C++ API ToolKit)
