Where is gayan?

Ok guys...I been missing for some time. At least didn’t blog for some time.

I have done few changes in last few months...

First of all, I am moved out from Canberra and moved in to Sydney..yes.. just next to the Sydney harbour bridge..(at least I can see it from my back yard!!!!)

I have join Microsoft!!!! it is very exciting !!! its been around six weeks now and done lost of travelling during that time...

The good news is, I am still working on SharePoint and will be sharing the MOSS love....

This will be the last blog post I will be doing in this site. Please visit my new blog site for more information.

http://blogs.msdn.com/gayanpeiris/

Please use an unused port for this site error in Central Admin Site

My Central Administration site in MOSS environment was giving me following error message after restarting the server.

IIS was unable to start this site. Another site may already be using the port you configured for this site. Please use an unused port for this site.

Looks like changing the port number through IIS won’t do any good. You will have to do this through the command line. First navigate to following location

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

You need to use STSADM with setadminport parameter

Type stsadm.exe -o setadminport –port [port number]

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. From BDC to CRM

I had a requirement to bring MS CRM data as search results in MOSS search centre. So I start doing my research. First, I found this nice blog post that explains there is already BDC definition file for CRM is available from MS,

BDC metadata definition file for Microsoft Dynamics CRM 3.0

I follow the instruction in the post and change my SQL server and database name to mach my environment. It worked fine. But, it was only displaying the data when I was accessing it from the SharePoint server. When I try to access the BDC data fro my client machine, I was getting following error message in the event log,

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Business Data
Event ID: 5700
Date: 3/07/2007
Time: 6:04:33 PM
User: N/A
Computer: XXXXX
Description:
Could not open connection using 'data source=daustcd01;initial catalog=nea_MSCRM;integrated security=SSPI;pooling=false;persist security info=false' in App Domain '/LM/W3SVC/1229638185/Root-1-128279213588223440'. The full exception text is: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

The BDC definition file is using “PassThrough” authentication mode. I was sure the problem was to do with the authentication. Then I start looking at what are my options here and found following are supported in BDC,

Pass through : The ability of the operating system to pass a client’s authentication information to the back end server. When you use this method, you simply authenticate as the identity of the end user. To avoid losing the logged on users identity when the BDC authenticate to the back end server, you must enable the Kerberos delegation.

RevertToSelf: this allows you to revert this impersonation and authenticate as the underling account that is configured for the IIS application pool. So while IIS runs under the application pool identity, it impersonates the logged on users, and the request runs under the user’s impersonation before it is passed forward.

WindowsCredentials: MOSS authenticates by using MS windows credentials from its default single sign-on (SSO) services.

So I change the BDC definition file to use RevertToSelf authentication mode. Make sure that application pool account in IIS for the MOSS site has access to CRM data. It’s all working fine now!!!!

How come Site Content Upgrade Status page is empty?

I am still working on SharePoint 2003 upgrade for MOSS 2007 environment. Finaly manage to get the farm environment stabilized. Then I was looking at Site Content Upgrade Status page (Central Administration > Operations > Site Content Upgrade Status) for the list of the sites that can be upgraded.

Guess what? It was empty when I knew it should at least have dozen sites listed. I though this may be a security trimming user interface issue and made sure that my account is under Farm Administrators Group (The link “Update farm administrator's group” , Central Administration > People and Groups)

Still not luck. I have two front end web servers and one index server (or Application server). Then I realise the Central Administration site is running under both application server and one front end server.

I don’t get the site list in Site Content Upgrade Status page when I access the Central Administration site through application server. I simply stop the Central Administration service in application server and only had is enabled in my front end web server.

Sounds very simple!!!! But can waste lot of time if you don’t know what you are doing!!!!

Event ID : 6482 and 6398 errors for SharePoint 2003 Upgrade

I am currently conducting a SharePoint 2003 upgrade for MOSS 2007 in Load balanced medium server farm with SQL Cluster. I was getting following error message on my front end server.

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date: 23/04/2007
Time: 3:05:36 PM
User: N/A
Computer: SERVERNAME
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance

(1cf3346b-cb9d-430e-ab11-4ca65c7a93a5).

Reason: Object 61f7f45f-d7ac-4948-91f6-b881dffea275 not found.

Techinal Support Details:
System.Collections.Generic.KeyNotFoundException:

Object 61f7f45f-d7ac-4948-91f6-b881dffea275 not found.
at Microsoft.Office.Server.Search.Administration.

SearchApi.get_App()
at Microsoft.Office.Server.Search.Administration.

SearchApi.SetUsersPermittedToQuery

(String[] userNames, Boolean force)
at Microsoft.Office.Server.Search.Administration.

SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.

ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Following error message in my index server.


Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
Date: 23/04/2007
Time: 3:23:32 PM
User: N/A
Computer: SERVERNAME
Description:
The Execute method of job definition Microsoft.Office.Server.Search.Administration.

AddQueryServerJob (ID d39a43cb-8b90-4094-8f70-f51751700928)

threw an exception. More information is included below.

Index location '\\SERVERNAME\searchindexpropagation' not found on indexer 'SERVERNAME'. Aborting query server deployment for application EntrSharedServices.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


I did following steps to fix this problem,

• Navigate to Check Services Enabled in this Farm (Central Administration > Application Management > Check Services Enabled in this Farm)


• There was the error message
  Service: Office SharePoint Server Search
  Issue: The query server index file location on SERVERNAME is not shared. This location must be shared to allow for this server to receive propagation.
  Impact: Index propagation to SERVERNAME will fail.
  Action: Use the Office SharePoint Server Search Settings page to create the share.
  


• I navigate to the page Office SharePoint Server Search Service Settings page(Central Administration > Operations > Services on Server > Office SharePoint Server Search Service Settings)


• Set up the page.
  
  The above errors were cleared from my event log for good.
  
  I am a very happy man!!!!!!

Server Farm Configuration Not Complete

I was getting above error message in bright red text on left hand top corner in my Central Administration page. I made sure following services are all running,

Document Conversions Launcher Service
Document Conversions Load Balancer Service
Office SharePoint Server Search
Windows SharePoint Services Help Search
Windows SharePoint Services Incoming E-Mail
Windows SharePoint Services Web Application

Then I check on the Check Services Enabled in this Farm page (Central Administration > Application Management > Check Services Enabled in this Farm) to identify any errors. Its fine too.

Then I had to finally create the Shared Services. This make the error message disappear.

The specified name is already in use.

I was working on a content deployment job in MOSS WCM site when I receive the below error messages.

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
Date: 17/04/2007
Time: 11:54:25 AM
User: N/A
Computer: ComputerName
Description:
The Execute method of job definition Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition (ID 1afc019a-3e27-43a8-8ddd-2555d397e34c) threw an exception. More information is included below.

The specified name is already in use.

A list, survey, discussion board, or document library cannot have the same name as another list, survey, discussion board, or document library in this Web site. Use your browser's Back button, and type a new name.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Content Deployment
Event ID: 4958
Date: 17/04/2007
Time: 11:54:25 AM
User: N/A
Computer: ComputerName
Description:
Publishing: Content deployment job failed. Error: 'Microsoft.SharePoint.SPException: The specified name is already in use.

A list, survey, discussion board, or document library cannot have the same name as another list, survey, discussion board, or document library in this Web site. Use your browser's Back button, and type a new name. ---> System.Runtime.InteropServices.COMException (0x81020012): The specified name is already in use.

A list, survey, discussion board, or document library cannot have the same name as another list, survey, discussion board, or document library in this Web site. Use your browser's Back button, and type a new name.
at Microsoft.SharePoint.Library.SPRequestInternalClass.CreateListOnImport(String bstrUrl, Guid& pguidListId, String bstrTitle, String bstrDescription, Int32 lTemplateID, String bstrFeatureId, Guid guidRootFolderId, Int64 llFlags, Int32 iVersion, Int32 iAuthor, String bstrFields, String bstrContentTypes, String bstrImageUrl, String bstrEventSinkAssembly, String bstrEventSinkClass, String bstrEventSinkData, Guid guidDocTemplateId, String bstrViews, String bstrForms, Boolean bCompressedSchema)
at Microsoft.SharePoint.Library.SPRequest.CreateListOnImport(String bstrUrl, Guid& pguidListId, String bstrTitle, String bstrDescription, Int32 lTemplateID, String bstrFeatureId, Guid guidRootFolderId, Int64 llFlags, Int32 iVersion, Int32 iAuthor, String bstrFields, String bstrContentTypes, String bstrImageUrl, String bstrEventSinkAssembly, String bstrEventSinkClass, String bstrEventSinkData, Guid guidDocTemplateId, String bstrViews, String bstrForms, Boolean bCompressedSchema)
--- End of inner exception stack trace ---
at Microsoft.SharePoint.Library.SPRequest.CreateListOnImport(String bstrUrl, Guid& pguidListId, String bstrTitle, String bstrDescription, Int32 lTemplateID, String bstrFeatureId, Guid guidRootFolderId, Int64 llFlags, Int32 iVersion, Int32 iAuthor, String bstrFields, String bstrContentTypes, String bstrImageUrl, String bstrEventSinkAssembly, String bstrEventSinkClass, String bstrEventSinkData, Guid guidDocTemplateId, String bstrViews, String bstrForms, Boolean bCompressedSchema)
at Microsoft.SharePoint.Deployment.ListSerializer.CreateList(SPWeb parentWeb, Dictionary`2 listMetaData, Boolean usingPublicSchema)
at Microsoft.SharePoint.Deployment.ListSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType, Boolean isChildObject)
at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope)
at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)
at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)
at Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader)
at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()
at Microsoft.SharePoint.Deployment.SPImport.Run()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoImport()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.ExecuteJob()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean runAsynchronously)
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition.Execute(Guid targetInstanceId)'

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I have a authoring and production environment in same farm environment. I created a path and Job to migrate content from my authoring publishing site to production publishing site. The production site was created using the publishing template.
To fix above problem, I had to delete the production site and recreate it using the blank site template.

Its all working fine now….

The request failed with HTTP status 407: Proxy Authentication Required.

I am having a single MOSS server with dedicated SQL server for the back end. I was getting above error message when I was trying to execute the Job in Manage Content Deployment Paths and Jobs page. (Central Administration > Operations > Manage Content Deployment Paths and Jobs )

I have the set up the proxy details in my browser as mentioned below,

Configure proxy server settings to bypass the proxy server for local addresses

1. In Internet Explorer, on the Tools menu, click Internet Options.

2. On the Connections tab, in the Local Area Network (LAN) settings area, click LAN Settings.

3. In the Automatic configuration section, clear the Automatically detect settings check box.

4. In the Proxy Server section, select the Use a proxy server for your LAN check box.

5. Type the address of the proxy server in the Address box.

6. Type the port number of the proxy server in the Port box.

7. Select the Bypass proxy server for local addresses check box.

8. Click OK to close the Local Area Network (LAN) Settings dialog box.

9. Click OK to close the Internet Options dialog box.

An unhandled exception occurred in the user interface.Exception Information: OSearch (AccountName)

I was trying very hard to start the “Office SharePoint Server Search” in my MOSS farm environment. I was getting the above error message for the last 2 days and couldn’t figure out what the hell is I am doing wrong.

Guess what???? I had to enter the domain name followed by the user name to fix this problem. (Ex:domainName\AccountName).

Cant believe it took me long to realize this…..live and learn….

Unable to open shim database version registry key - v2.0.50727.00000

I am getting above error in my event log after installing the .NET Framework 2.0 hotfix as I mentioned in my previous post.

I had to install following hotfix to fix the problem

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