Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Search not working after MOSS upgrade

  Asked By: Jordan    Date: Aug 26    Category: Sharepoint    Views: 3395

I am seeing some strange errors while performing an upgrade from Sharepoint
Portal 2003 to MOSS 2007 and was wondering if anyone had any ideas.

The situation is this. I have setup a testing environment on a VM. It is a
single server installation of SPS 2003 with SQL 2000 SP4. I have used the
SPS backup and restore to take a copy of our production site to reproduce it
in the testing environment.

Once this is up and running I have then installed the MOSS 2007 eval. Due to
problems with the in-place upgrade, I have then gone down the gradual
upgrade route. In the most part this has worked fine, with all the sites now
migrated across to MOSS 2007 except for the fact that I am unable to get
searching to function.

From Central Admin -> Operations -> Services on Server Office Sharepoint
Server Search is not running and when I try and click on start I receive an
Error page with the following message

An unhandled exception occurred in the user interface.Exception Information:
Could not find stored procedure 'dbo.proc_MIP_GetObjectVersion'.

I have checked through the various databases and the stored procedure in
question does indeed exist in the SharedServices1_DB database. I am also
logged on as the user context the database runs under and am able to execute
the stored procedure from Query Analyzer.

Uninstalling and re-installing MOSS 2007 doesn't seem to have resolved this
issue.

Share: 

 

3 Answers Found

 
Answer #1    Answered By: Marjorie Humphrey     Answered On: Aug 26

Not wanting to nag, but does anyone have any ideas on this?? Or any
suggestions as to how i might proceed would be helpful.

 
Answer #2    Answered By: Chelsey Watts     Answered On: Aug 26

I haven't seen this error. But if the upgrade  cannot find a stored
procedure, even if it is there, there must be a significant problem with
the environment. Is it possible that the upgrade wizard is looking at
one SQL Server and the migrated site is using another? For instance,
MOSS was installed to use the embedded WMSDE (or whatever it is called
now) and the database from production is on a full version of SQL
Server?

 
Answer #3    Answered By: Nagesh Maulik     Answered On: Aug 26

I have a bit more information on this one as i now have something resembling
working  site.

The problem i was experiencing seemed to be relating to the Shared Services
Database that the migration process was trying to create. When investigated
further, it appeared the database had not been successfully created. The
shared service was also stuck with "provisioning" next to it in the "manage
this farm's shared services" page in Central Administration.

There were a couple of errors  in the Application event log that could be
related. The first was event id 0 from Windows Sharepoint Services 3 which
said;
*"Could not determine if application pool Upgrade_App_Pool uses an
incompatible version of ASP. Ensure all sites associated with this
application pool are using the same version. Additional information is
below.*

*The method or operation is not implemented."*
Followed not long after by Event id 5586, also from Windows Sharepoint
Services 3 which said;
*Unknown SQL Exception 547 occured. Additional error information from SQL
Server is included below.*

*DELETE statement conflicted with COLUMN REFERENCE constraint
'FK_Dependencies1_Objects'. The conflict occurred in database
'SharePoint_Config', table 'Dependencies', column 'ObjectId'.
The statement has been terminated.*
I did try to created an SSP before upgrading the content, but there doesn't
seem to be an option (that i could see) to use an existing SSP for the
purpose of migration (admittedly i didn't explore the command line route).

The shared service database did actually exist in the database, but there
were no stored procedures and only some of the tables. While it was in that
state, i created a new SSP and then copied the stored procedures over. I
then associated the migrated sites with the newly created SSP and was then
able to delete the SSP that was created by the migration process.

Once that was ticking along nicely, i then started the process of upgrading
the sites, which has now successfully completed.

So i am almost there... the only problem i seem to have now is that the
migration process doesn't like my SSP configuration which has different web
applications for main site and my site. If anyone is still reading this,
any thoughts would be greatfully received!!

 
Didn't find what you were looking for? Find more on Search not working after MOSS upgrade Or get search suggestion and latest updates.




Tagged: