Sign in
Microsoft.com
 
SharePoint Products TechCenter
 
 
 
SharePoint Products TechCenter > SharePoint Products and Technologies Forums > SharePoint - Setup, Upgrade, Administration and Operation (pre-SharePoint 2010) > "The evaluation version .... is expired" when configuring SSP (MOSS from Action Pack)
Ask a questionAsk a question
Search Forums:
 

Answer"The evaluation version .... is expired" when configuring SSP (MOSS from Action Pack)

  • Friday, February 06, 2009 8:38 AMMark Ferkaluk - EFEXCON AG Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Greetings,

    I'm getting a strange error message, when I try to configure my Shared Service Provider on my MOSS 2007. When I click "user profiles and properties" (in German: Benutzerprofile und Eigenschaften) it occours the following error message (sounds a little different because I have a German system):

    The evaluation version of Microsoft Office Sharepoint Server 2007 for this server is expired.

    Die Evaluierungsversion von Microsoft Office Sharepoint Server 2007 für diesen Server ist abgelaufen.

    I don't understand that at all. I used the MOSS 2007 of the Action Pack, and this is no evaluation version.

    Has someone an idea?

    Thanks in advance!

    Best regards,

    Mark
    • Edited byMike Walsh MVPMVP, ModeratorFriday, February 06, 2009 9:17 AMSubject amended to indicate the problem and the fact that you are using the version from the Action Pack
    •  
     

Answers

  • Tuesday, February 10, 2009 9:51 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hello Mark,

     

    The issue may be a little complex and please try the following method firstly:

     

    1.       Add the application pool account to the local admin group.

    2.       Perform an IISRESET on the SharePoint server.

    3.       Run the PSconfig wizard. Test if the issue goes away. If it does, go to Step 4.

    4.       Remove the user back from the local admin group, perform an IISRESET again.

     

    Thanks.

     

    Best Regards,

    Lionel

     
  • Wednesday, February 11, 2009 2:27 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hello Mark,

     

    Sorry for not clarifying it.

     

    Please test both SSP application pool identities and other application pool accounts. You could find these accounts via the following steps:

     

    1.       Enter Central Administration.

    2.       Switch to Operation tab.

    3.       Click Service Account under Security Configuration.

    4.       In Service Account page, choose the Web application pool check box and select Windows SharePoint Services Web Application. Then, select the application pool in Application pool drop-down list.

    5.       You will then find the application pool identity listed in text box in the Select an account for this component section.

    6.       Please make a note for all of them and temporarily add them into local admin group.

     

    As this issue cannot be reproduced in my environment, the solution above is based on my experience with similar cases. Please give it a try and let us know the result.

     

    Thanks.

     

    Best Regards,

    Lionel

     

All Replies

  • Tuesday, February 10, 2009 9:51 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hello Mark,

     

    The issue may be a little complex and please try the following method firstly:

     

    1.       Add the application pool account to the local admin group.

    2.       Perform an IISRESET on the SharePoint server.

    3.       Run the PSconfig wizard. Test if the issue goes away. If it does, go to Step 4.

    4.       Remove the user back from the local admin group, perform an IISRESET again.

     

    Thanks.

     

    Best Regards,

    Lionel

     
  • Tuesday, February 10, 2009 10:32 AMMark Ferkaluk - EFEXCON AG Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hello,

    thanks for your reply!

    I don't exactly know which application pool or user u mean. Do you mean the user that is configured on the ssp property page (login information for the ssp-service)?

    Thanks.

    Greez,

    Mark
     
  • Wednesday, February 11, 2009 2:27 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hello Mark,

     

    Sorry for not clarifying it.

     

    Please test both SSP application pool identities and other application pool accounts. You could find these accounts via the following steps:

     

    1.       Enter Central Administration.

    2.       Switch to Operation tab.

    3.       Click Service Account under Security Configuration.

    4.       In Service Account page, choose the Web application pool check box and select Windows SharePoint Services Web Application. Then, select the application pool in Application pool drop-down list.

    5.       You will then find the application pool identity listed in text box in the Select an account for this component section.

    6.       Please make a note for all of them and temporarily add them into local admin group.

     

    As this issue cannot be reproduced in my environment, the solution above is based on my experience with similar cases. Please give it a try and let us know the result.

     

    Thanks.

     

    Best Regards,

    Lionel

     
  • Monday, February 16, 2009 8:38 AMMark Ferkaluk - EFEXCON AG Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    thank you very much! That solutions worked for me.

    Greez,

    Mark
     
  • Thursday, September 17, 2009 4:42 AMMOSS Goss Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Well thank you Mark for raising this issue and thank you very very much Lionel for explaining the solution in such a clear manner. Sorted!