SharePoint 2010 Metadata and Taxonomy Management – Lookup on This Field Not Allowed

Jan 10, 2013 9:31 PM, - Posted by Tommy Segoro

In regards to Metadata and Taxonomy Management, when you create a “Managed Metadata” column on your list, it is actually a lookup field to the central Metadata repository.

 

You can’t further perform a lookup on this field from another list.

 

 

Cheers,

Tommy

Upgrading Microsoft Office Sharepoint Server (MOSS) 2007 to Sharepoint 2010 BETA – Part 4 – Content Database Backup/Restore

Jan 10, 2013 9:31 PM, - Posted by Tommy Segoro

At this point of time I’ve given up trying to upgrade MOSS 2007 to Sharepoint 2010 BETA using in-place upgrade approach.

 

I now try it using Content Database backup/restore approach.

 

It’s a very simple process that I was following:

– Create a new VM and install Sharepoint 2010 clean-fresh farm

– Install and deploy all custom WSPs that are currently deployed to MOSS 2007 farm

– Backup MOSS 2007 sites database

– Create a blank Sharepoint website in Sharepoint 2010 farm to restore content DB to

– Remove and take offline the existing content DB

– Restore and re-attach the MOSS 2007 content database

 

AND IT WORKED! WOOHOO!! The only error message  I was getting in the log file was:

==

[STSADM] [SPContentDatabaseSequence] [ERROR] [2/8/2010 3:51:49 PM]: Found a missing feature Id = [c88c4ff1-dbf5-4649-ad9f-c6c426ebcbf5]

 

 

[STSADM] [SPContentDatabaseSequence] [ERROR] [2/8/2010 3:51:49 PM]: The feature with Id c88c4ff1-dbf5-4649-ad9f-c6c426ebcbf5 is referenced in the database, but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

 

==

 

I think I must have missed a feature.

 

But anyway, at the point of writing this article, I can say that this will be the better approach of upgrading 2007 sites to Sharepoint 2010 compared to in-place upgrade.

 

 

Cheers,

Tommy

Upgrading Microsoft Office Sharepoint Server (MOSS) 2007 to Sharepoint 2010 BETA – Part 3 – Another Retry

Jan 10, 2013 9:30 PM, - Posted by Tommy Segoro

Hi everyone,

 

I mentioned that I tried to upgrade a MOSS instance that wasn’t connected to AD. I have now changed this. I re-created my VM, connected that to AD, install MOSS 2007 then upgraded it to Sharepoint 2010 BETA.

 

The result is THE SAME.

 

The existing MOSS 2007 site wouldn’t load. It totally broke. It still said HTTP 403 FORBIDDEN (as per my previous article).

 

New site works no problem at all.

 

The detailed error was still the same ie. the old MOSS 2007 database somehow couldn’t be upgraded.

==

Server Error in ‘/’ Application.

 

 

——————————————————————————–

There is a compatibility range mismatch between the Web server and database “WSS_CSNET_Content”, and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.

 

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

 

Exception Details: Microsoft.SharePoint.Upgrade.SPUpgradeCompatibilityException: There is a compatibility range mismatch between the Web server and database “WSS_CSNET_Content”, and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.
Source Error:

 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

 

Stack Trace:

 

[SPUpgradeCompatibilityException: There is a compatibility range mismatch between the Web server and database “WSS_CSNET_Content”, and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.]

 

Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.ValidateBackwardsCompatibility() +542

Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request) +49

Microsoft.SharePoint.SPWeb.InitializeSPRequest() +258

Microsoft.SharePoint.WebControls.SPControl.EnsureSPWebRequest(SPWeb web) +365

Microsoft.SharePoint.WebControls.SPControl.SPWebEnsureSPControl(HttpContext context) +520

Microsoft.SharePoint.WebControls.UnsecuredLayoutsPageBase.OnPreInit(EventArgs e) +115

Microsoft.SharePoint.WebControls.LayoutsPageBase.OnPreInit(EventArgs e) +49

Microsoft.SharePoint.ApplicationPages.SettingsPage.OnPreInit(EventArgs e) +59

System.Web.UI.Page.PerformPreInit() +42

System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1256

——————————————————————————–

 

Version Information: Microsoft .NET Framework Version:2.0.50727.4200; ASP.NET Version:2.0.50727.4016

==

 

On the next trial I will try to go down the content database attachment approach. I will install Sharepoint 2010 on a completely new VM, installing all features, create a brand new site collection, etc then attach the content database from MOSS 2007.

 

 

I’ll let you know how I go,

Tommy

 

Upgrading Microsoft Office Sharepoint Server (MOSS) 2007 to Sharepoint 2010 BETA – Part 2 – What Did/Didn’t Work

Jan 10, 2013 9:30 PM, - Posted by Tommy Segoro

I haven’t done another upgrade at the moment but from what I’ve done before , I found the following things that worked and didn’t (please read on my other article my current MOSS 2007 environment setup).

 

Worked

– DLLs are all working OK.

– Few changes are needed on web.config (which are – in my opinion – minor).

– Custom site templates working OK – that’s if used for creating a new site collection.

– Features and feature receivers are all working OK – that’s if used for creating a new site collection.

 

Didn’t work

– Existing MOSS 2007 site couldn’t load. Please see the error message I was getting on my previous post. I think it had something to do with the database that couldn’t be upgraded.

 

 

I will now try other methods such as installing all my SP 2010 features, etc on a new farm then restoring MOSS 2007 content database into it. I want to see how that goes.

 

 

Cheers,

Tommy

Upgrading Microsoft Office Sharepoint Server (MOSS) 2007 to Sharepoint 2010 BETA – Part 1

Jan 10, 2013 9:28 PM, - Posted by Tommy Segoro

Yo everyone,

 

I now want to upgrade my MOSS 2007 instance with Sharepoint 2010 BETA. I of course do it on a VM 🙂 Within my MOSS 2007 instance I’ve got the following running:

– Custom site template of CompleteSharepoint.NET (Content Management System Built on-top-of Windows Sharepoint Services 3.0)

– Custom field types and field controls

– Custom feature receivers

– Custom ASP.NET controls

– Custom Site Actions menu

– Custom content types and columns

– Custom administration pages

– Custom master pages and page layouts

– Custom list template and list instance

– Gary Lapointe’s custom STSADM commands

– Central Admin runs at http://machine:9000/

– SSP runs at http://machine:9001/

– MySites runs at http://machine:9002/

– My MOSS 2007 farm is NOT RUNNING ON ACTIVE DIRECTORY! The users are pulled out from local machine.

 

SQL Server is also running from the same VM as MOSS 2007.

 

 

 

So…here it is….I’ll paste some screenshots as I go through.

 

 

BEFORE: Solutions

 

 

BEFORE: Sharepoint site as it stands

 

 

 

BEFORE: Extracting SP2010 Beta executables

 

 

I then installed all the pre-requisites as per my article:

http://sp2010journal.blogspot.com/2010/01/installing-sharepoint-2010.html

 

 

Pre-requisites installed OK

 

 

That’s what it said before installing….

 

 

Installed successfully..now it runs the configuration wizard

 

 

 

Clicking Next before went straight to this screen

 

 

WOW..new screen…I choose to preserve the look and feel

 

 

EXCITING…EXCITING…

 

 

Opening Central Admin…and…BANG….ERROR

 

OK let me fixed that.

 

That’s the reason why it broke

 

 

So then I removed that line from Central Admin’s web.config and:

 

 

Still breaks…fine…I’ll fix that

 

I change the navigation provider to: CurrentNavSiteMapProvider and………

 

 

VOILA!!!

 

I said I had 3 errors. When I opened the log file mentioned at the bottom of the screen I could see errors related to User Profile. It might be caused by my MOSS 2007 wasn’t running on AD?

—

[OWSTIMER] [UserProfileSharedResourceProvider12Sequence] [ERROR] [2/5/2010 1:47:40 PM]: Action 14.0.1.0 of Microsoft.Office.Server.Upgrade.UserProfileSharedResourceProvider12Sequence failed.

[OWSTIMER] [UserProfileSharedResourceProvider12Sequence] [ERROR] [2/5/2010 1:47:40 PM]: Inner Exception: There are no online service instances for this application.

[OWSTIMER] [UserProfileSharedResourceProvider12Sequence] [ERROR] [2/5/2010 1:47:40 PM]: at Microsoft.SharePoint.SPConnectedServiceApplication.get_ApplicationAddresses()

at Microsoft.SharePoint.SPServiceLoadBalancer.<get_endpointaddresses>d__0.MoveNext()

at Microsoft.SharePoint.SPRoundRobinServiceLoadBalancer.GetEndpoints(IEnumerable`1 applicationAddresses)

at Microsoft.SharePoint.SPRoundRobinServiceLoadBalancer.BeginOperation()

at Microsoft.Office.Server.UserProfiles.MossClientBase`1.get_Channel()

at Microsoft.Office.Server.UserProfiles.MossClientBase`1.ExecuteOnChannel(String operationName, CodeBlock codeBlock)

atMicrosoft.Office.Server.UserProfiles.ProfilePropertyServiceClient.ExecuteOnChannel(String operationName, CodeBlock codeBlock)

[OWSTIMER] [UserProfileSharedResourceProvider12Sequence] [ERROR] [2/5/2010 1:47:40 PM]: Exception: There are no online service instances for this application.

[OWSTIMER] [UserProfileSharedResourceProvider12Sequence] [ERROR] [2/5/2010 1:47:40 PM]: at Microsoft.Office.Server.UserProfiles.ProfilePropertyServiceClient.ExecuteOnChannel(String operationName, CodeBlock codeBlock)

at Microsoft.Office.Server.UserProfiles.ProfilePropertyServiceClient.GetProfileProperties()

at

Microsoft.Office.Server.Administration.UserProfileApplicationProxy.RefreshProperties(Guid applicationID)at Microsoft.Office.Server.Utilities.SPAsyncCache`2.GetValueNow(K key)

at Microsoft.Office.Server.Utilities.SPAsyncCache`2.GetValue(K key, Boolean asynchronous)

at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.InitializePropertyCache()

at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.Provision()
at Microsoft.Office.Server.Upgrade.ExtractUserProfileApplication.Upgrade()

at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

[OWSTIMER] [ExtractUserProfileApplication (14.0.1.0)] [DEBUG] [2/5/2010 1:47:40 PM]: Begin Rollback()

[OWSTIMER] [ExtractUserProfileApplication (14.0.1.0)] [DEBUG] [2/5/2010 1:47:40 PM]: End Rollback()

[OWSTIMER] [ExtractUserProfileApplication (14.0.1.0)] [DEBUG] [2/5/2010 1:47:40 PM]: Begin Dispose()

[OWSTIMER] [ExtractUserProfileApplication (14.0.1.0)] [DEBUG] [2/5/2010 1:47:40 PM]: End Dispose()

[OWSTIMER] [ExtractUserProfileApplication (14.0.1.0)] [DEBUG] [2/5/2010 1:47:40 PM]: SQL Query Count=998

[OWSTIMER] [ExtractUserProfileApplication (14.0.1.0)] [DEBUG] [2/5/2010 1:47:40 PM]: SPRequest Objects=0

[OWSTIMER] [ExtractUserProfileApplication (14.0.1.0)] [DEBUG] [2/5/2010 1:47:40 PM]: Execution Time=48390.3856495728

[OWSTIMER] [SPUpgradeSession] [ERROR] [2/5/2010 1:47:40 PM]: Upgrade [SharedResourceProvider12 Name=Default SSP] failed.

[OWSTIMER] [SPUpgradeSession] [ERROR] [2/5/2010 1:47:40 PM]: Inner Exception: There are no online service instances for this application.

[OWSTIMER] [SPUpgradeSession] [ERROR] [2/5/2010 1:47:40 PM]: at Microsoft.Office.Server.UserProfiles.ProfilePropertyServiceClient.ExecuteOnChannel(String operationName, CodeBlock codeBlock)

at Microsoft.Office.Server.UserProfiles.ProfilePropertyServiceClient.GetProfileProperties()

at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.RefreshProperties(Guid applicationID)

at Microsoft.Office.Server.Utilities.SPAsyncCache`2.GetValueNow(K key)

at Microsoft.Office.Server.Utilities.SPAsyncCache`2.GetValue(K key, Boolean asynchronous)

at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.InitializePropertyCache()

at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.Provision()

at Microsoft.Office.Server.Upgrade.ExtractUserProfileApplication.Upgrade()

at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

[OWSTIMER] [SPUpgradeSession] [ERROR] [2/5/2010 1:47:40 PM]: Exception: Action 14.0.1.0 of Microsoft.Office.Server.Upgrade.UserProfileSharedResourceProvider12Sequence failed.

[OWSTIMER] [SPUpgradeSession] [ERROR] [2/5/2010 1:47:40 PM]: at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

[OWSTIMER] [SPUpgradeSession] [DEBUG] [2/5/2010 1:47:40 PM]: Elapsed time upgrading [SharedResourceProvider12 Name=Default SSP]: 00:01:05.

[OWSTIMER] [SPManager] [INFO] [2/5/2010 1:47:40 PM]: Resetting the status of PersistedUpgradableObject: SharedResourceProvider12 Name=Default SSP to Online.

[OWSTIMER] [SPUpgradeSession] [ERROR] [2/5/2010 1:47:40 PM]: Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 14.0.1.0 of Microsoft.Office.Server.Upgrade.UserProfileSharedResourceProvider12Sequence failed. —&gt; Microsoft.Office.Server.UserProfiles.UserProfileException: There are no online service instances for this application. —&gt; Microsoft.SharePoint.SPException: There are no online service instances for this application.

at Microsoft.SharePoint.SPConnectedServiceApplication.get_ApplicationAddresses()

at Microsoft.SharePoint.SPServiceLoadBalancer.<get_endpointaddresses>d__0.MoveNext()

at Microsoft.SharePoint.SPRoundRobinServiceLoadBalancer.GetEndpoints(IEnumerable`1 applicationAddresses)

at Microsoft.SharePoint.SPRoundRobinServiceLoadBalancer.BeginOperation()

at Microsoft.Office.Server.UserProfiles.MossClientBase`1.get_Channel()

at Microsoft.Office.Server.UserProfiles.MossClientBase`1.ExecuteOnChannel(String operationName, CodeBlock codeBlock)

at Microsoft.Office.Server.UserProfiles.ProfilePropertyServiceClient.ExecuteOnChannel(String operationName, CodeBlock codeBlock)

— End of inner exception stack trace —

at Microsoft.Office.Server.UserProfiles.ProfilePropertyServiceClient.ExecuteOnChannel(String operationName, CodeBlock codeBlock)

at Microsoft.Office.Server.UserProfiles.ProfilePropertyServiceClient.GetProfileProperties()

at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.RefreshProperties(Guid applicationID)

at Microsoft.Office.Server.Utilities.SPAsyncCache`2.GetValueNow(K key)

at Microsoft.Office.Server.Utilities.SPAsyncCache`2.GetValue(K key, Boolean asynchronous)

at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.InitializePropertyCache()

at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.Provision()

at Microsoft.Office.Server.Upgrade.ExtractUserProfileApplication.Upgrade()

at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

— End of inner exception stack trace —

at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)

at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)

at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId)–

 

 

Well, let’s open the CompleteSharepoint.NET site now, shall we? 🙂

 

 

I get web.config error. Well..let me fix that then.

 

I commented out that line and I then get the same SPUrl error as before. So I removed the SPUrl line as well and…..

 

 

Error…

 

After trialling and error, I found out that it has something to do with MOSS 2007 HTTPModule. It’s this particular one:

 

 

 

 

 

I then commented that out and I got different error:

 

 

 

Fine I can fix that. It’s actually the lines below:

 

&lt;add verb=”GET,HEAD,POST” path=”*” type=”Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” /&gt;

&lt;add verb=”OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,PROPPATCH,MKCOL,DELETE,(GETSOURCE),(HEADSOURCE),(POSTSOURCE)” path=”*” type=”Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” /&gt;

 

 

It seems that Sharepoint 2010 is not using tag any more. It uses the following instead:

&lt;modules runAllManagedModulesForAllRequests=”true”&gt;
&lt;remove name=”AnonymousIdentification” /&gt;
&lt;remove name=”FileAuthorization” /&gt;
&lt;remove name=”Profile” /&gt;
&lt;remove name=”WebDAVModule” /&gt;
&lt;add name=”SPRequestModule” preCondition=”integratedMode” type=”Microsoft.SharePoint.ApplicationRuntime.SPRequestModule, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” /&gt;
&lt;add name=”ScriptModule” preCondition=”integratedMode” type=”System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ /&gt;
&lt;add name=”SharePoint14Module” preCondition=”integratedMode” /&gt;
&lt;add name=”StateServiceModule” type=”Microsoft.Office.Server.Administration.StateModule, Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” /&gt;
&lt;add name=”PublishingHttpModule” type=”Microsoft.SharePoint.Publishing.PublishingHttpModule, Microsoft.SharePoint.Publishing, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” /&gt;
&lt;add name=”PublishingPageUrlHandlerModule” type=”CompleteSharepoint.NET.Web.PublishingPageUrlHandlerModule,CompleteSharepoint.NET.Web, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9911d32a5d039082″ /&gt;


&lt;/modules&gt;

Anyway, it still failed. It now displayed the following:

 

I tried to hijack to go to /_layouts/settings.aspx and it still failed.

However, if I create a new site collection using my custom CompleteSharepoint.NET site template, IT WORKS! WOOOHOO!! So my CS.NET is working on SP2010! 🙂

See below:

Conclusion
I still can’t get upgrade working. But I’ll keep trying and let you know if it ever succeeded. I think the database couldn’t somehow be upgraded successfully.

Cheers,
Tommy