none
Project Server 2007 - Quick Launch Issue - Urgent RRS feed

  • Question

  • I have quite a big issue on a Project Server 2007 installation :

    We have two Project Server instances:

        * http://project/mops-prod : production instance
        * http://project:84/MOPS-Test2/ : test instance

    Today, I went to the test instance in order to modify values in a “Lookup table” used by an “Enterprise Custom Field” for test purposes, before doing the same in the production instance.

    After this modification, I went back to the production instance, and immediately I noticed some issues and I couldn’t access some data.

    After investigation, I noticed some modifications on the Project Web Access (PWA) home page: all the links in the quick launch menu have been modified and are now wrong.

    For example: the link “Project Center” quick launch is now  “http://project/mops-test2/projects.aspx” instead of “http://project/mops-prod/projects.aspx”

    If I modify manually the link in the address bar, I will access the page without any problem

    Another example, the “Server Settings” quick launch is now “http://project/mops-test2/_layouts/pwa/admin/admin.aspx” instead of “http://project/mops-prod/_layouts/pwa/admin/admin.aspx” and I can access the Server Settings page modifying manually the url (prod instead of test2).

    All the url in the quick launch menu (PWA home page) are now different and wrong. If I go to the Server Settings page, the quick launch links are still goog, the url have note been modified. Concerning all the Project Workspaces and project schedules on the different data bases, everything seems ok.

    It’s quite a big issue for us because our production instance is now not available and the users (about 300) are not able to access the data via the PWA home page, but they can access directly to the project workspace (if they know the url)

    Have you ever heard about a similar issue?

    What do you think I could do?

    Best regards
    Monday, April 2, 2012 8:57 AM

Answers

  • Hi,

    Thank you for your time and your answers. I don't know a lot about NLB but I think this is not implemented and we have no AAM.

    Actualy, we have fixed the issue following these steps :

    - suppression of the test instance and associated web app,

    - in the SharePoint central administration : we launched the "Sharepoint product and technology configuration wizard"

    At the end off the wizard, the issue was fixed.
    • Marked as answer by YvesZ Friday, January 4, 2013 6:33 AM
    Wednesday, April 4, 2012 8:03 AM

All replies

  • Yves,

    that sounds really weird... As an attempt to quickly make PWA work again, you could try to manually modify one of the Quick Launch items (e.g. Project Center) from the Server Settings Quick Launch page. You mentioned that the links displayed there are still correct. Regardless, I would try to edit one and save the changes and then see what happens. Hopefully, this will at least fix the link in the Quick Launch. If it works, I'd go ahead and do this for all of the links listed in the Quick Launch.

    Once the PWA instance is running again, I would then spend time to investigate what went wrong. Did you have a look at the ULS logs around the time this first happened? I find it really odd that you started noticing this as you changed some values in a look-up table. Are you sure that the Quick Launch issue hasn't surfaced before that? Maybe it's just pure coincidence in terms of timing...

    Hope this helps...

    Monday, April 2, 2012 10:47 AM
  • I would also double check your SharePoint Alternate Access Mappings in Central Admin to ensure you're not getting some crossover redirects. Check to see is someone has modified this area recently. The following link may help explain access mappings further:

    http://technet.microsoft.com/en-us/library/cc261814(v=office.12).aspx


    Regards,

    Piet Remen
    http://pietremen.blogspot.com.au

    Tuesday, April 3, 2012 3:10 PM
  • Sometime NLB can play a major role in this kind of behavior. It looks like you are not using FQDN and you are using NetBIOS name, so NLB shouldn't be an issue.

    But we can still can try following steps to identify whether there is any issue with NLB or not;

    1. Add entries of the all the Server names in the Alternate Access Mappings. http://technet.microsoft.com/en-us/library/cc261814(v=office.12).aspx
    2. Remote into the Application Server of the farm.
    3. Try accessing PWA by providing the name of the Application Server/PWA instancename.
    4. See the behavior. If you still see the same behavior, then remote into the Web Front End Server (one by one) of the farm and try accessing PWA site Web App Server Name/PWA instancename and see the behavior.
    5. Incase you see the normal behavior with any of the above steps then NLB should be an issue.

    Please reply if above steps are not applicable to your environment or you need further help.

    Regards,

    Jignesh

    Tuesday, April 3, 2012 5:00 PM
  • Hi,

    Thank you for your time and your answers. I don't know a lot about NLB but I think this is not implemented and we have no AAM.

    Actualy, we have fixed the issue following these steps :

    - suppression of the test instance and associated web app,

    - in the SharePoint central administration : we launched the "Sharepoint product and technology configuration wizard"

    At the end off the wizard, the issue was fixed.
    • Marked as answer by YvesZ Friday, January 4, 2013 6:33 AM
    Wednesday, April 4, 2012 8:03 AM
  • Hi Yves,

    I just ran into the same issue like you did and optimistically tried the proposed solution running the configuration wizard did not work :-(

    Christoph

    Tuesday, July 17, 2012 10:04 AM
  • I made the same, but no success.

    Does anyone have a solution for it?


    Tuesday, August 13, 2013 1:37 PM
  • Hi

    try to check via PowerShell.

    $Web = get-SPWeb http://<pwa instance having the issue> $Web.AllProperties | Format-Table

    If the output of this command will show a value for PWAURL, change it to NULL running the following commands. I ‘m suspecting that PWAURL will display the URL corresponding to the wrong PWA instance.

    $Web.AllProperties[“PWAURL”]=””
    $Web.Update()

    Regards

    Christoph


    Christoph Muelder | Senior Consultant, MCSE, MCT | SOLVIN information management GmbH, Germany

    Thursday, August 22, 2013 5:20 AM
  • For 2007 that powershell command won't work.. You will need to use code: http://blogs.msdn.com/b/brismith/archive/2010/05/18/project-server-2010-my-pwa-site-thinks-it-is-a-workspace-site-revisited.aspx. Paul

    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Thursday, August 22, 2013 6:15 AM
    Moderator