SharePoint 2013 - getting an error while clicking on the ellipsis of a document in a Document Library

I have a standard out-of-the-box Document Library. versioning/checkin/out is enabled. There are a few extra columns added to the library. There is this a weird random behavior when clicking on the ellipsis (...) button on a document. Sometimes it will display the context menu and sometimes it will give me this error:

TypeError: Unable to get property 'FileLeafRef' of undefined or null referenceTypeError: Unable to get property 'ItemType' of undefined or null referenceTypeError: Unable to get property 'ID' of undefined or null reference

Sometimes a refresh will fix it. Sometimes it won't. It's all pretty random.

Anyone have this issue or have any ideas on how to solve it?

October 31st, 2013 6:38pm

Hi,

According to your post, my understanding is that sometimes you got an error while clicking on the ellipsis of a document in a Document library.

I tried to reproduce the issue, every documents in my environment worked well.

Did the issue occur in every library? You can recreate a library, then check whether it worked, maybe the library had been corrupted.

You can also check the event log and ULS log to see if anything unexpected occurred.

To check event log, click the Start button and type Event Viewer in the Search box.

For SharePoint 2013, by default, ULS log is at

               

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS

You can check the ULS log by the methods here:

http://blogs.msdn.com/b/opal/archive/2009/12/22/uls-viewer-for-sharepoint-2010-troubleshooting.aspx

http://msdn.microsoft.com/en-us/library/gg193966(v=office.14).aspx

Thanks & Regards,

Jason 
Free Windows Admin Tool Kit Click here and download it now
November 1st, 2013 6:53am

Did you find an answer to this?  We have the same behavior: random times, random documents, unreproducable except by accident.

nsy

November 13th, 2013 6:02pm

I'm having the same problem, would love to get this resolved. Its only with certain users, not all. Thanks
Free Windows Admin Tool Kit Click here and download it now
November 15th, 2013 3:24am

I too have had this problem with pattern as to when it occurs.  Generally a refresh of the page seems to sort it.  Is there any fix for this?
November 19th, 2013 3:20pm

We are also seeing this behavior. It affects everyone on checkout of the document.  A refresh (F5 or CTRL-F5) seems to take it away for that instance.  As soon as another document is checked out it will affect that item until refreshed.
Free Windows Admin Tool Kit Click here and download it now
February 6th, 2014 11:42pm

Hi,

This error message is pretty consistent in SharePoint 2013 Document library views with Grouping enabled. 

1. Create a view grouped by certain column.(Make sure, at least a few groups are there).

2. Expand more than 2 groups.

3. Refresh the page and click the ellipsis for individual documents.

4. If normal refresh doesn't help, try ctrl + F5 and try clicking the ellipsis.

Tried the following but no luck in resolving:

1. Disabled Minimal download Strategy feature.

2. In Fiddler, I could see a 401 while trying to hit commandui.ashx.

/_layouts/15/commandui.ashx?ver=757996781&id=Ribbon.Read&lcid=1033&qt=ribbonvisibletabdeep

Any resolution for this?

March 7th, 2014 12:34am

I'm also experiencing this at a customer.  It just happens for one user, on a document library.

When I access the library with admin account, or a user with elevated priveleges, it works fine.

The view does have grouping on.

I see there is a answer marked here, but there is no resolution?

Free Windows Admin Tool Kit Click here and download it now
April 9th, 2014 9:38am

Hi,

According to your post, my understanding is that sometimes you got an error while clicking on the ellipsis of a document in a Document library.

I tried to reproduce the issue, every documents in my environment worked well.

Did the issue occur in every library? You can recreate a library, then check whether it worked, maybe the library had been corrupted.

You can also check the event log and ULS log to see if anything unexpected occurred.

To check event log, click the Start button and type Event Viewer in the Search box.

For SharePoint 2013, by default, ULS log is at

               

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS

You can check the ULS log by the methods here:

http://blogs.msdn.com/b/opal/archive/2009/12/22/uls-viewer-for-sharepoint-2010-troubleshooting.aspx

http://msdn.microsoft.com/en-us/library/gg193966(v=office.14).aspx

Thanks & Regards,

Jason&nb
June 4th, 2014 9:30am

Did anyone try raising this issue with Microsoft? It looks like a product bug to me ! Let me know if it has been raised and if it is listed to be fixed in the future updates.
Free Windows Admin Tool Kit Click here and download it now
June 11th, 2014 11:37am

I had the same problem as described below every now and then I'm getting an error in the calloutusagecontrolscript.js script

TypeError: Unable to get property 'FileLeafRef' of undefined or null referenceTypeError: Unable to get property 'ItemType' of undefined or null referenceTypeError: Unable to get property 'ID' of undefined or null reference

The debugger is telling me that the following line is causing the problem:

f=g.getItemById(a.CurrentItem.ID)

CurrentItem isn't defined so that is causing the problem.

Also when I started to debug things  inplview.js is also reporting "Invalid character " ut it looks like that is following the earlier problem

So the problem is actually on the call out. With a bit more playing with the document library affected. I found some causes for this problem.

1. I'm using document sets

2. I'm using grouping in my view (about 30 groups appear on my page)

3. I collapsed many groups while I'm loading the page.

If I wait long enough (probably until the page is loaded) then there isn't a problem. If I load the page and click on the ... of a document as soon as it appears then I get the above error.

Most likely some of the JavaScript isn't loading properly by the time you first click on the page.

.

July 4th, 2014 12:21pm

Glad I found this thread. This problem was also reported by a couple of our users back in May 2014. But as it was intermittent so we did not do any detailed investigation. Today I tried to use Chrome Developer Tools to investigate but it was still very difficult to find out what caused the problem. (Yes, we know where the problem line is, but we don't know what caused it to become the problem line).

Some facts from us:

1. This happens in one of our DOCUMENT LIBRARIES too.
2. In Chrome, it seems to happen more consistently when the Developer Tool is being used.
3. With the Chrome Developer Tool in use, if I then open Fiddler too, then it reduces the chance of it happening significantly!
4. The document library has more than 5000 items, which may cause list view threshold issue.
5. Managed Metadata is used for Grouping.

I wish pmsrofe will unmark Jason's replay as answer, since it is definitely NOT the answer, after so many people are encountering this issue.

 



  • Edited by Conway Liu Tuesday, November 11, 2014 6:50 AM
Free Windows Admin Tool Kit Click here and download it now
August 11th, 2014 2:36am

Glad I found this thread. This problem was also reported by a couple of our users back in May 2014. But as it was intermittent so we did not do any detailed investigation. Today I tried to use Chrome Developer Tools to investigate but it was still very difficult to find out what caused the problem. (Yes, we know where the problem line is, but we don't know what caused it to become the problem line).

Some facts from us:

1. This happens in one of our DOCUMENT LIBRARIES too.
2. In Chrome, it seems to happen more consistently when the Developer Tool is being used.
3. With the Chrome Developer Tool in use, if I then open Fiddler too, then it reduces the chance of it happening significantly!
4. The document library has more than 5000 items, which may cause list view threshold issue.
5. Managed Metadata is used for Grouping.

I wish pmsrofe will unmark Jason's replay as answer, since it is definitely NOT the answer, after so many people are encountering this issue.

 



  • Edited by Conway Liu Tuesday, November 11, 2014 6:50 AM
August 11th, 2014 2:36am

Sameproblem here, SharePoint 2013 in a Document Library.

Randomly receives " typeerror unable to get property fileleafref of undefined or null referencetypeerror"

Sometimes it's enough with a refresh, sometimes is randomly "heals" itself and sometimes it persist for some days..

Help?


  • Edited by smekfis Monday, August 18, 2014 11:29 AM
Free Windows Admin Tool Kit Click here and download it now
August 18th, 2014 11:28am

Sameproblem here, SharePoint 2013 in a Document Library.

Randomly receives " typeerror unable to get property fileleafref of undefined or null referencetypeerror"

Sometimes it's enough with a refresh, sometimes is randomly "heals" itself and sometimes it persist for some days..

Help?


  • Edited by smekfis Monday, August 18, 2014 11:29 AM
August 18th, 2014 11:28am

Hi,

Has anyone been able to solve this?

We're expecting this behavior with a customer aswell.

Free Windows Admin Tool Kit Click here and download it now
November 25th, 2014 9:35am

We're getting this issue as well on a SharePoint 2013 farm with SP1+Nov14CU. We have a support ticket running for this but no solution yet. It is indeed related to grouping in views, as that seems the common denominator.
January 8th, 2015 11:48am

Any answers from Microsoft regarding this issue?
Free Windows Admin Tool Kit Click here and download it now
January 19th, 2015 12:15pm

Hi, the Microsoft Support Engineer has marked it as a possible bug and will be escalated further. We have devised a workaround that was found "most feasible for the time being" by the engineer.

WORKAROUND:

(Note that I'm showing the debug versions for ease of reading because they are not minified)

  • Edit 15\TEMPLATE\LAYOUTS\INPLVIEW.js on all servers (make a backup first though! optionally do the debug versions as well)
  • Comment out the following if-statement so that the statement inside runs unconditionally
if (typeof m$ != "undefined")

  • (Optional) Add the if statement to the MergeListData function right above the line where "m$.extend" is called
function MergeListData(existingData, dataToMerge) {
    for (var newRow in dataToMerge.Row) {
        var bFound = false;

        for (var existingRow in existingData.Row) {
            if (dataToMerge.Row[newRow].ID == existingData.Row[existingRow].ID) {
                bFound = true;
				if(typeof m$!="undefined")
					m$.extend(existingData.Row[existingRow], dataToMerge.Row[newRow]);
                continue;
            }
        }
...

I have uploaded "my" versions of the relevant files HERE. They are for build 15.0.4667.1000 (SP1 + Nov14CU) but may apply to other builds as well. Best to compare them with your own or manually apply the workaround steps yourself.

I'll update this thread if there's news from the Support Engineer.



January 22nd, 2015 8:39am

Hi, the Microsoft Support Engineer has marked it as a possible bug and will be escalated further. We have devised a workaround that was found "most feasible for the time being" by the engineer.

WORKAROUND:

(Note that I'm showing the debug versions for ease of reading because they are not minified)

  • Edit 15\TEMPLATE\LAYOUTS\INPLVIEW.js on all servers (make a backup first though! optionally do the debug versions as well)
  • Comment out the following if-statement so that the statement inside runs unconditionally
if (typeof m$ != "undefined")

  • (Optional) Add the if statement to the MergeListData function right above the line where "m$.extend" is called
function MergeListData(existingData, dataToMerge) {
    for (var newRow in dataToMerge.Row) {
        var bFound = false;

        for (var existingRow in existingData.Row) {
            if (dataToMerge.Row[newRow].ID == existingData.Row[existingRow].ID) {
                bFound = true;
				if(typeof m$!="undefined")
					m$.extend(existingData.Row[existingRow], dataToMerge.Row[newRow]);
                continue;
            }
        }
...

I have uploaded "my" versions of the relevant files HERE. They are for build 15.0.4667.1000 (SP1 + Nov14CU) but may apply to other builds as well. Best to compare them with your own or manually apply the workaround steps yourself.

I'll update this thread if there's news from the Support Engineer.



Free Windows Admin Tool Kit Click here and download it now
January 22nd, 2015 8:39am

Good man Steven, thanks for this.

January 22nd, 2015 11:00pm

Thank you for posting this. Very helpful.
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2015 6:27pm

This is great that there is a workaround.  It would be great if our Support team would be willing to implement it.  This is more than a possible bug.  It is clearly a bug.  Did they give some sort of reference ID to follow up and allow others to comment/reinforce/vote on the bug?  I don't know if Microsoft does that or not.
February 24th, 2015 7:39pm

Same issue here, the ellipsis (...) button works sometimes, not always.  Happens to all users in multiple site collections.  Happens with No grouping or customizations.    Refreshing page once or twice usually resolves the issue but it's a pain to do that all the time.

In developer mode, I see this error:

SCRIPT5007: Unable to get property 'substr' of undefined or null reference
core.js, line 1 character 201459

Free Windows Admin Tool Kit Click here and download it now
February 25th, 2015 2:30pm

The case is archived and the bug is escalated to the Development Team for review. I don't know if they'll let me know of any outcome of that. You won't find the case publicly available for voting or follow up.
February 26th, 2015 10:08am

You'll have to trace the error like we dit using the dev tools in the browser. Since I can't reproduce it's difficult to troubleshoot.
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2015 10:09am

Hi

"TypeError: Unable to get property 'FileLeafRef' of undefined or null reference"

You can find some alternatives here (none of which have I tried or am I recommending):

http://alternativeto.net/software/hotspot-shield/

I'd still suggest ensuring you are running the latest version and contacting the vendor

-------------------------------------------

"TypeError: Unable to get property 'ItemType' of undefined or null reference"

please try to test the site using IE Compatibility View, compare the result.

Also, try to reset IE , compare the result.

Here is a similar posts for your reference:

http://social.technet.microsoft.com/Forums/en-US/6efe0564-7df9-4812-b08b-a9d36e3c257b/typeerror?forum=w8itprogeneral

---------------------------------------

TypeError: Unable to get property 'ID' of undefined or null reference

http://community.microstrategy.com/t5/Web/TN204030-TypeError-Unable-to-get-property-id-of-undefined-or/ta-p/204030

February 26th, 2015 12:23pm

Any update on this? We've encountered the same issue, but editing the .js file seems to have no effect in our case.

After doing an iisreset on the WFE, the issue goes away, but it's easily reproducible: click on the ellipsis of a document (in a view with grouping), select Edit Properties, then click Cancel. Afterwards, clicking on the ellipsis will consistently produce the error for every document in that group.

Thank you for your suggestions!

Ryan

Free Windows Admin Tool Kit Click here and download it now
March 12th, 2015 6:58pm

Hi Ryan,

Are you sure you're editing the right file (debug vs 'regular', correct/all WFE's) ? Check the browser cache for the file and see if it contains 'your' modifications.

No update from Microsoft on this.

Cheers

March 13th, 2015 2:20am

Hello, Steven. Thank you for your quick response!

In this case, I'm not even making any changes--after selecting Edit Properties, I'm clicking the Cancel button without changing any properties of the file. Before doing this, I can click on the ellipsis and see the doc preview, etc. After clicking the Cancel button, clicking on the ellipsis produces the "TypeError: Unable to get property..." error message for each document in the first grouping of the doc library. Hitting refresh has no effect. Clearing the cache also has no effect. Switching to a different doc library or to a different view and back has no effect. There's only one WFE in this setup.

This seems like a pretty significant issue... I would think this would have been addresses if so many people are experiencing it. I guess it only affects a small number of users? (Though it seems to affect many people here....)

Free Windows Admin Tool Kit Click here and download it now
March 13th, 2015 2:40am

Hi Ryan,

I was referring to the JS file you need to edit in order to fix this. If you have edited the wrong file then your/my modification won't apply.

But even then I can't guarantee that "my" fix works for all cases. It just did for mine and a few others...

Cheers,

Steven

March 13th, 2015 7:31am

Ah, apologies about my misunderstanding. Yes, I edited the one INPLVIEW.js in the following location on the one WFE: Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS. I ran iisreset afterwards. It sounds like it may be worthwhile if I open up a ticket on this as well? Would you have another ticket number I could reference to help push the issue?

Thank you for your assistance!

Ryan

Free Windows Admin Tool Kit Click here and download it now
March 13th, 2015 1:45pm

Hi Ryan,

Make sure that the INPLVIEW.js is used. For example if you have debug=true in the web.config it will use the debug-version of that file. Then, rule out browser caching so that you're sure you're using the modified version of the JS file. If you've done all that then my fix doesn't apply to you it seems.

Contact me privately for the case number. I'd rather not share it with the whole world :)

Cheers

March 16th, 2015 2:31am

Hello,

is there any update for this problem?

Editing files on the live server is not really an option.

Free Windows Admin Tool Kit Click here and download it now
August 31st, 2015 2:02am

Not that I know of. We have stopped pursuing the issue since the workaround.

August 31st, 2015 2:37am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics