locked
Internet Explorer and PWA v2010 crashes when Modifying a Second Record for an Enteprise Field with a Pick List RRS feed

  • Question

  • We are operating Project Server v2010 with SP2.

    We have discovered that if we edit a schedule in PWA and then change an enterprise field that has a pick list, then you will get a fatal Internet Explorer error the next time you try to edit a an enterprise field with a pick list. 

    The error reads:

    "Internet Explorer has stopped working

    A problem caused the program to stop working correctly.  Please close the program.

    Close the Program"

    The file remains checked-out and an administrator must to a force check-in.

    The problem so far seems to be limited to one of our Project Servers and we have not been able to replicate the problem in two of our other Servers.

     

    Friday, August 22, 2014 2:42 PM

Answers

  • Problem solved!

    Our IT people tell us that they added the affected site to the Local Intranet Zone via IE Security settings.

    Friday, November 21, 2014 1:51 PM

All replies

  • Have you tried to see if this behavior occurs when running IE in compatibility mode? 

    And have you tried using Chrome?

    Also, does the pick list contain any special characters? 

    Cheers!


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Sunday, August 24, 2014 4:15 AM
  • Hi Michael -

    It crashes in Chrome, as well. 

    Yes, the field is using special characters --- It uses "(", ")", and "/".  However, we are using exactly the same field and lookup table on our test Server as we are using our our production Server.  The test Server works, but the Production Server does not.

    With regards to compatibility mode, we are running the production Server and test Server on the same instance of IE, so I am not sure what difference that would make.

    Chris

    Monday, August 25, 2014 11:16 AM
  • Hi

    Try installing the August 2014 IE patch on that machine and check the behavior.

    http://support.microsoft.com//kb/2976627

    Monday, August 25, 2014 8:22 PM
  • Hi Krishnp -

    First off, things like patches to IE are controlled by another contractor ---- my company does not manage the network.  We have logged the problem as a trouble ticket, but any decision to install a patch would have to be approved by that company, and the US Government, which owns the network (not an easy task).

    Second, I am using exactly the same IE instance to review what is on the test Server and the production server.  I don't see how applying a patch will fix the problem.

    Chris

    Wednesday, August 27, 2014 10:44 AM
  • Edit the enterprise custom table that drop down is using.  Remove special characters from list.  I have seen issues when # or & are used.

    cheers


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Friday, August 29, 2014 11:31 AM
  • Michael - the custom table is not using # or &.  Furthermore, we are not able to replicate the problem using the exact same lookup table in our test environment. 
    Friday, August 29, 2014 1:05 PM
  • Michael - I just found out that the difference between our "production" server and test-string servers is that the test-string servers are quick & dirty partioned servers where all of the databases are in the same spot.  In the production server, the web server and the database server are two different servers. 

    This is leading us to believe that there is some communication issue between the database server and the web server.

    We are not sure how to solve that problem.

    To repeat, we are unable the replicate the problem on our test servers, but it only occurs on our production server, even when we use identical lookup tables and enterprise fields.

    Chris

    Wednesday, September 10, 2014 4:18 PM
  • Personally, I don't think that would cause this problem.

    Have you tried using IE compatibility mode?

    Have you tried making site a trusted site in IE?

    Have you tried, editing the lookup table and basically clearing the field and re-entering the exact text.  My thinking, is that you have an embedded hidden character.

    Also, you can always open a troubleshooting ticket with Microsoft if you have support.


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Thursday, September 11, 2014 4:27 AM
  • Hi Michael,

    We are operating this Project Server on a nework that is being managed by another contractor.  The options to use Compatibility Mode or make the PWA a trusted site are grayed-out for me. 

    With regards to editing the lookup table, we have a number of fields that use lookup tables.  Regardless of which field we choose we get the same behavior; the moment you select a second pick list IE crashes that tab with the PWA.  That is another thing that I noticed today.  It crashes just the tab, not the entire instance of IE.  There are a lot of lookup tables --- 49 at my count; I am not eager to go rebuilding lookup tables in an operational environment when the behavior seems to be independent of the field chosen.

    The protocol here is that we have filed a ticket with the group that manages the network.  If Microsoft is called in to help, it will be after the administrators for this network have exhausted their options.

    Regards,

    Chris

    Thursday, September 11, 2014 1:48 PM
  • Hi Michael -

    Our other administrator was able to verify that there was no change in behavior when running in compatibility mode.

    I decided to sort our lookup table list from most recent modified to oldest modified.  I was surprised to find 9 lookup tables in our production server with "&" somewhere in the table.  After a gruelling search, I replaced all of the "&"'s with "and".  At the end of the exercise, we are still getting the same behavior.

    As a note, 2 of the 9 lookup tables are identical on our test Server, and the test Server is fine.

    Still flumoxed,

    Chris

    Thursday, September 11, 2014 5:05 PM
  • Go to SharePoint Central and

    click on Upgrade and Migration

    Click on Check Production and Patch installation statues -- any errors

    Click Riview Database status  -- any errors

    Click Check upgrade status - any errors

    Run the ULSViewer and capture the errors in log for the correlation ID when it crashes. Dump here.


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Wednesday, September 17, 2014 4:04 AM
  • Hi Mike - I am afraid that I can't share the logs.  They come from a sealed network.

    Chris

    Thursday, September 18, 2014 5:17 PM
  • Problem solved!

    Our IT people tell us that they added the affected site to the Local Intranet Zone via IE Security settings.

    Friday, November 21, 2014 1:51 PM