Leftovers following upgrade to 2010

Got some strangeness...
A while back I did an in-place upgrade and everything seemed to go ok - people are using 2010 with no problems.
Today I went to mysite and tried to create a new site below it (FAST search) and just get the dreaded error occured.
I looked at the logs (ULS viewer) and see a critical error saying duplicated data - so I googled and came up with a post saying that upgrades can often still reference the 12 hive and to rename the folder to .old
So I did... now I get a bunch of critical errors in the log (although SP still seems to work fine) saying that c:/...../12 is an invalid path.

Why are things still looking at 12 and not 14?
How can I see what is referencing it?
LVL 29
QPRAsked:
Who is Participating?
 
KoenVostersConnect With a Mentor Commented:
Do you have any custom development on your environment? As sometimes these developers referenced the 12 hive in their SharePoint 2007 solution.
0
 
Ted BouskillConnect With a Mentor Senior Software DeveloperCommented:
I have some bad news.  By invitation only I was invited to attend a "SharePoint 2010 Deep Dive" at Microsoft in Redmond and spent a few days with the heads of all the SharePoint technology teams.  I spent a couple of hours with the thier top expert regarding upgrading MOSS 2007 to SharePoint 2010.

He had reviewed our work and said it was top-notch.  Our work was awarded the Microsoft SharePoint Customer of the Quarter in 2009 and we had followed all the best practices.

Despite those accolades regarding our best practices with MOSS 2007 he told us bluntly "Don't upgrade in-place".  He stated it might seem to work but eventually you will run into a lot of problems.  He told us the in-place upgrade was actually only intended for use on installations of 'Small Business Server' running WSS 3.0

A lot of SharePoint experts here and on the web say it can be done, however, when the SharePoint upgrade Top-Gun that works for Microsoft says don't do it, I tend to believe him.  Considering he wasn't telling us what we wanted to hear I gave his word even more weight.

If you can answer the previous comment about custom development we will try to help as best we can.
0
 
QPRAuthor Commented:
Thanks guys (I think :-)
Only custom development I can think of is the fab 40 templates...
We have 2 of these in use - training and service desk.
They work, just about but I realise they aren't supported and have recently heard at a SP conferecne there are no plans to make any for 2010

Anyways, could this be the culprit?

When I (DBA, .NET developer, long time web developer) get my head around this SP admin and development I might look at rewriting them but, as a one person sharepoint person here at work, it's taking some time!
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

 
Ted BouskillSenior Software DeveloperCommented:
Hmm, I'd be surprised if the Fab 40 are the problem, however, they could be.  Those were created a long time ago when MOSS 2007 was first released and they might not be following best practices even if Microsoft supplied them.
0
 
QPRAuthor Commented:
Word from MS (NZ) is that they were created by the MOSS marketing team (rather than the developers) as a showcase to what was possible.

I can't think of anything that isn't OOTB with some browser created changes made to them.
But I do fee that it is partially crippled in places. Lots of oddities and I can't put them all down to my lack of admin experience!

0
 
KoenVostersCommented:
QPR, can you provide us with the error message of the error you were getting initially? It's clear something is pointing to the 12 hive, but if we can take a look at the error message then we might also be able to identify what it is.  If you get a general error, you can use the following steps to identify the error:
http://koenvosters.wordpress.com/2009/08/06/showing-the-real-error-message-in-sharepoint/
0
 
QPRAuthor Commented:
Not specifically related to the 12 hive but while I see it...
Here is the result of me attempting to create a new FAST site under my "my site"

Failed to open the file 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Resources\pws.en-US.resx'.

#20015: Cannot open "": no such file or folder.

I will rename the 12 hive again so it generates some errors related to this question and post them
0
 
QPRAuthor Commented:
Did a search on 12\log (ULS viewer) on a couple of files from a day or two ago and did find this...

Importing usage log file: 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\WDC-MOSS1-20110404-1328.usage'.

I wonder if this is part of the reason that I can't get web usage stats to work (not provisioned) despite everything being supposedly started?
I also see this
Failed to find the XML file at location '14\Template\Features\Analytics\feature.xml'


But try as I might I cannot reproduce a cannot find 12/logs entry yet!
Will keep looking


0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.