SharePoint Products TechCenter > SharePoint Products and Technologies Forums > SharePoint - Setup, Upgrade, Administration and Operation > Your licence for Office Server Search has expired error on MOSS 2007 SP2 on Windows 2008
Ask a questionAsk a question
 

AnswerYour licence for Office Server Search has expired error on MOSS 2007 SP2 on Windows 2008

  • Friday, October 30, 2009 11:31 AMRuth J Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I've just finished installing MOSS SP2 Enterprise on Windows 2008 with a local instance of SQL2008 workgroup edition. (small company,plans to scale out later).
    (This was a slipstreamed clean install of MOSS 2007 SP2 on Windows 2008 in small farm mode, using local SQL2008.
    No install of Project server / CRM on this box.)
    All went well, and I've started the WSS Search services.
    I have now created a Shared Services Provider and configured the default content crawl schedule.

    When I do a Search from the End user environment I get
    "Your licence for Office Server Search has expired"

    In the Event Logs I find

    Error backing up registry hive to the configuration database.

    Context: Application 'Search index file on the search server'

    Details:

    The system cannot find the file specified. (0x80070002)

    From some other older posts relating to MOSS on W2K3 I saw suggestions about re-running the Config and Technologies wizard again, + IISRESET, but this did not help in this case


    Ruth, UK

Answers

  • Wednesday, November 04, 2009 7:26 AMLambert QinMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi Ruth,

     

    If you have a AV/AS software installed on the Index Server, please try to temporarily disable the AV/AS software and see if issue still persists.

    If your issue did not persist, please try to exclude the folders from antivirus scanning following the steps according to KB952167 (http://support.microsoft.com/kb/952167).

     

    If your issue continues to persists, please carefully check the service account permission according to Plan for administrative and service accounts, and make sure the permissions of all the service account are correct.

    Especially, the central administration pool account should be a member of the administrators group.

    Moreover, please make sure HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Office Server\12.0 in Registry has Read-Permission for WSS_WPG, and Full Permissions for WSS_ADMIN_WPG.

     

    Let me know the result if possible.

     

    Lambert Qin

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact mtngfb@microsoft.com  


    Sincerely,
    Lambert Qin
    Posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked As Answer byRuth J Tuesday, November 10, 2009 10:59 AM
    •  
  • Tuesday, November 10, 2009 10:59 AMRuth J Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    A number of related errors caused my problems I think.

    1. I had done a slipstreamed install of MOSS2007 SP2 on Windows 2008
    2. I had not initially put the SP Central Admin account in the Local admins group.

    point 2 was fairly easy to track down and fix.

    Re. point 1 above however, I had missed a vital step. I had only added the MOSS SP2 to the install, not the WSS SP2 as well.

    And weirdly, although I had installed the newest version of the SP2 that should not have had the licensing error, it was giving me the above problems

    So, these are the correct instructions for the slipsteam install:
    http://technet.microsoft.com/en-us/library/cc261890.aspx

    ie MOSS 2007, WSS SP2, and MOSS SP2

    I found the error by comparing the version number of my MOSS install. It should have said 12.0.0.6421 but did not. this list of version numbser helps:
    http://www.sharepointdesignerstepbystep.com/Blog/Articles/How%20To%20find%20the%20SharePoint%20version.aspx

    ****
    I had added the WSS SP2, MOSS SP2 and re-run the SP Technologies and Config wizard, then things improved.
    ****


    Ruth, UK
    • Marked As Answer byRuth J Tuesday, November 10, 2009 10:59 AM
    •  

All Replies

  • Friday, October 30, 2009 11:59 AMRuth J Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    A related error message to the above:

    User tires to edit the MOSS Collaboration Intranet Home page (a publishing page)
    User cannot check in to save draft.
    The following error is displayed:
    "The trial period for this product has expired"


    Ruth, UK
  • Friday, October 30, 2009 12:35 PMRuth J Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    The App Pool identities need extra permissions.

    In my case I put All the AD App pool accounts in a new AD group called SPAccounts

    The I had to Add SPAccounts to
    - Local Administrators group
    - IIS_WPG
    - WSS_WPG

    Looks like that did the trick


    Ruth, UK
  • Friday, October 30, 2009 2:01 PMMagnus Johansson Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Ruth.

    You shouldn't really run your SharePoint accounts as local admins. That's not recommended.

    Maybe you have stumbled upon the Service Pack 2 license bug ?

    Regards,
    Magnus
    My blog: InsomniacGeek.com
  • Tuesday, November 03, 2009 6:41 PMRuth J Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Thanks for the Post Magnus.

    Update 1 fixed, 1 unresolved: Check in to save draft error not showing now. Search Page error still saying "Your licence for Office Server Search has expired"

    Re. Search - I had already found the link above, followed the instructions and

    1. in Central Admin it shows the correct license type

    2. The box to upgrade from trial was greyed out / disabled

    Any other ideas?

    Thanks
    Ruth


    Ruth, UK
  • Tuesday, November 03, 2009 10:01 PMpmeehan Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I just recieved the same error message as well.  It has been a while since I used the search so I don't know when exactly it started, but we are running on MOSS 2007 Enterprise SP2 on a Windows 2003 server connected to a SQL 2008 Standard edition database (on a seperate server).

    Patrick.
  • Wednesday, November 04, 2009 7:26 AMLambert QinMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi Ruth,

     

    If you have a AV/AS software installed on the Index Server, please try to temporarily disable the AV/AS software and see if issue still persists.

    If your issue did not persist, please try to exclude the folders from antivirus scanning following the steps according to KB952167 (http://support.microsoft.com/kb/952167).

     

    If your issue continues to persists, please carefully check the service account permission according to Plan for administrative and service accounts, and make sure the permissions of all the service account are correct.

    Especially, the central administration pool account should be a member of the administrators group.

    Moreover, please make sure HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Office Server\12.0 in Registry has Read-Permission for WSS_WPG, and Full Permissions for WSS_ADMIN_WPG.

     

    Let me know the result if possible.

     

    Lambert Qin

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact mtngfb@microsoft.com  


    Sincerely,
    Lambert Qin
    Posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked As Answer byRuth J Tuesday, November 10, 2009 10:59 AM
    •  
  • Tuesday, November 10, 2009 3:44 AMLambert QinMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi Ruth,

     

    Could you please let me know the current status of your issue?

    If you need further assistance, please feel free to let me know.

     

    Have a nice day!

     

    Lambert Qin

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact mtngfb@microsoft.com  


    Sincerely,
    Lambert Qin
    Posting is provided "AS IS" with no warranties, and confers no rights.
  • Tuesday, November 10, 2009 10:59 AMRuth J Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    A number of related errors caused my problems I think.

    1. I had done a slipstreamed install of MOSS2007 SP2 on Windows 2008
    2. I had not initially put the SP Central Admin account in the Local admins group.

    point 2 was fairly easy to track down and fix.

    Re. point 1 above however, I had missed a vital step. I had only added the MOSS SP2 to the install, not the WSS SP2 as well.

    And weirdly, although I had installed the newest version of the SP2 that should not have had the licensing error, it was giving me the above problems

    So, these are the correct instructions for the slipsteam install:
    http://technet.microsoft.com/en-us/library/cc261890.aspx

    ie MOSS 2007, WSS SP2, and MOSS SP2

    I found the error by comparing the version number of my MOSS install. It should have said 12.0.0.6421 but did not. this list of version numbser helps:
    http://www.sharepointdesignerstepbystep.com/Blog/Articles/How%20To%20find%20the%20SharePoint%20version.aspx

    ****
    I had added the WSS SP2, MOSS SP2 and re-run the SP Technologies and Config wizard, then things improved.
    ****


    Ruth, UK
    • Marked As Answer byRuth J Tuesday, November 10, 2009 10:59 AM
    •  
  • Tuesday, November 10, 2009 11:01 AMRuth J Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks for your help Lambeth.
    Updated the status with what I think solved my issue.
    Ruth, UK