We have recently migrated to SharePoint 2013, but we are running in "2010 mode". We just noticed that we can't seem to edit a page once an Excel Services Web Part has been saved to the page. When a user clicks on the Edit Page button the loading notice in the upper right of the page appears and it just sits there spinning. I have tested this on any page that has the Excel Services Web part and it happens there too. I have gone back to our QA environment and I can reproduce the problem. Any ideas? 

• Moved by Hemendra AgrawalMVP Monday, September 09, 2013 3:06 PM

Hi Larry,

Can you explain, what you WebPart seems to be ?

Juste load a Excel file ? Some external connections ? etc...

Thanks

Nothing fancy. I created one test with a basic new workbook. No data connections, no million rows of data, etc. The basic fails as well as the more complex. The web parts are working, to be clear. I just can't edit the page again once I have saved the web part.

Had you deploy :

The session state service ?

The state service ?

Thanks

• Edited by Julien Stroheker Tuesday, August 06, 2013 4:04 AM

Hi Julen,

Thank you for your response. I work with Larry. 

Yes, both Sate Service and Session State are enabled and running in the farm. While the issue is happening, I'm getting the following two 'Unexpected' errors in ULS.

CannotMakeBrowserCacheSafeLayoutsUrl: 14/1033/images/agavedefaulticon96x96.png

CannotMakeBrowserCacheSafeLayoutsUrl: 14/1033/images/moe_default_icon.png

Any ideas?

Thanks.

Hi Saji,

Do you use a US version of SharePoint ? or a specific language pack ?

Have you tried to reach the both png file on the sharepoint hive 14 ?

Thanks

Thank you for the response. Yes, it's US version and there is no language pack installed (both in old 2010 and new 2013 environment).

Here is the troubleshooting I've done so far,

1. Made sure that State Service and Session State is provisioned and running. Also made sure that 'sessionStateEnabled' is set to 'true' in web application's web.config file. 
2. Checked if the two png files were present in "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\1033\IMAGES" and found that they were NOT present. But it was also found that they were NOT present in the old 2010 farm too (where the page is working fine for editing). So the ULS error is happening only in new 2013 farm (site collections in 2010 mode).
3. Created two dummy png files with names mentioned in the error message and placed them in the IMAGES folder.
4. Restarted IIS on all servers.

The ULS errors went away but the page editing issue is still there.

I thoroughly checked the ULS entries and was able to find only one entry (given below) which I assume related to this.

[08/06/2013 22:54:29.05 w3wp.exe (0x02CC) 0x0A28 SharePoint Foundation Web Parts aaruz Medium Unable to locate the WebPartAdderId for the ScriptEditorWebPart. 4198369c-3b1c-20ff-b641-2c97e8eeb369]

I made the logging level for Web Parts verbose but nothing helpful could be found.

Thanks.

Hi Saji,

Seems to be very weird.

Have you tried to test in a other browser like Chrome ?

Had you some JavaScript errors on the page ?

You said this happen only on edit mode, but when you close the editing mode that's work right ?

Thanks

Hi Saji,

Some news ?

Thanks

Hi Julien,

Sorry for the delay. The behavior is the same across browsers (IE, Chrome and Firefox). The page works fine even while the Loading... message is spinning. I can even refresh the data connection in Excel web part while it's spinning. So the only problem is that the page won't switch to Edit mode but shows the "Loading..." message for ever. Refreshing the page takes it to normal mode and everything works fine.

Following Javascript errors are shown when clicking the Edit Page link though.

1. Uncaught TypeError: Cannot call method '$N' of null EwaMoss.tp.js?rev=P%2BrNbQT85UgwZKyuecR%2Fsw%3D%3D:2
   1. _Ewa.$7H.remove_$1CiEwaMoss.tp.js?rev=P%2BrNbQT85UgwZKyuecR%2Fsw%3D%3D:2
   2. _Ewa.$40.disposeEwaMoss.tp.js?rev=P%2BrNbQT85UgwZKyuecR%2Fsw%3D%3D:2
   3. _Ewa.$3q.disposeEwaMoss.tp.js?rev=P%2BrNbQT85UgwZKyuecR%2Fsw%3D%3D:2
   4. Sys._Application.disposeElementScriptResource.axd?d=M4UgM1SCgW74lh1PN12uYFmL5LB8v27GtTakan00OvunYhyLHfFPoLAULNWwbhHu6M-7Z2t-IZMvP3mP-AmR6DGy7Wvfr8oApVRm1zIGEl_q4UM7Sf0&t=6119e399:5
   5. Sys.WebForms.PageRequestManager._updatePanelScriptResource.axd?d=03d019JaFd01uJS8rpx12FqztRqguDFJ7T_MUPbOQeco-aIA5c-BPjZ0YkLYCWBLjtIlKag3aXZCe25LPfmbqgRsImMNh39VI2kRkDWuGdw6UaEYgL0&t=6119e399:5
   6. Sys.WebForms.PageRequestManager._scriptIncludesLoadCompleteScriptResource.axd?d=03d019JaFd01uJS8rpx12FqztRqguDFJ7T_MUPbOQeco-aIA5c-BPjZ0YkLYCWBLjtIlKag3aXZCe25LPfmbqgRsImMNh39VI2kRkDWuGdw6UaEYgL0&t=6119e399:5
   7. (anonymous function)ScriptResource.axd?d=M4UgM1SCgW74lh1PN12uYFmL5LB8v27GtTakan00OvunYhyLHfFPoLAULNWwbhHu6M-7Z2t-IZMvP3mP-AmR6DGy7Wvfr8oApVRm1zIGEl_q4UM7Sf0&t=6119e399:5
   8. (anonymous function)ScriptResource.axd?d=M4UgM1SCgW74lh1PN12uYFmL5LB8v27GtTakan00OvunYhyLHfFPoLAULNWwbhHu6M-7Z2t-IZMvP3mP-AmR6DGy7Wvfr8oApVRm1zIGEl_q4UM7Sf0&t=6119e399:5
   9. Sys._ScriptLoader._loadScriptsInternalScriptResource.axd?d=03d019JaFd01uJS8rpx12FqztRqguDFJ7T_MUPbOQeco-aIA5c-BPjZ0YkLYCWBLjtIlKag3aXZCe25LPfmbqgRsImMNh39VI2kRkDWuGdw6UaEYgL0&t=6119e399:5
   10. Sys._ScriptLoader._scriptLoadedHandlerScriptResource.axd?d=03d019JaFd01uJS8rpx12FqztRqguDFJ7T_MUPbOQeco-aIA5c-BPjZ0YkLYCWBLjtIlKag3aXZCe25LPfmbqgRsImMNh39VI2kRkDWuGdw6UaEYgL0&t=6119e399:5
   11. (anonymous function)ScriptResource.axd?d=M4UgM1SCgW74lh1PN12uYFmL5LB8v27GtTakan00OvunYhyLHfFPoLAULNWwbhHu6M-7Z2t-IZMvP3mP-AmR6DGy7Wvfr8oApVRm1zIGEl_q4UM7Sf0&t=6119e399:5
   12. Sys._ScriptLoaderTask._scriptLoadHandlerScriptResource.axd?d=M4UgM1SCgW74lh1PN12uYFmL5LB8v27GtTakan00OvunYhyLHfFPoLAULNWwbhHu6M-7Z2t-IZMvP3mP-AmR6DGy7Wvfr8oApVRm1zIGEl_q4UM7Sf0&t=6119e399:5
   13. (anonymous function)ScriptResource.axd?d=M4UgM1SCgW74lh1PN12uYFmL5LB8v27GtTakan00OvunYhyLHfFPoLAULNWwbhHu6M-7Z2t-IZMvP3mP-AmR6DGy7Wvfr8oApVRm1zIGEl_q4UM7Sf0&t=6119e399:5
   14. bScriptResource.axd?d=M4UgM1SCgW74lh1PN12uYFmL5LB8v27GtTakan00OvunYhyLHfFPoLAULNWwbhHu6M-7Z2t-IZMvP3mP-AmR6DGy7Wvfr8oApVRm1zIGEl_q4UM7Sf0&t=6119e399:5

1. Uncaught TypeError: Cannot call method 'parentElement' of null sp.ui.rte.js?rev=gtvnBQlpiH6heu6RHMsIsA%3D%3D:2
   1. RTE.Canvas.checkCurrentFocussp.ui.rte.js?rev=gtvnBQlpiH6heu6RHMsIsA%3D%3D:2
   2. (anonymous function)EwaMoss.js?rev=cKzdWClE%2F7e20d0xH1lj3g%3D%3D:2

• Edited by Saji Viswambharan Monday, August 12, 2013 5:41 PM

Can you give me your Build Version of SharePoint please.

I will try to reproduce on my labs.

Thanks

Farm build is 15.0.4505.1005. The site collections are migrated from SP 2010 (14.0.6114.5000) via database attach and are in 2010 mode.

Hi Julien,

I was wondering if you were able to reproduce the issue in your environment?

Thanks,

Saji

I had the same issue, here is how i resolved it:

1. Edit Webpart

2. Removed URL from Workbook Display > Workbook: (essentially unhooking the Excel file)

3. Apply > OK.

4. Made page Edits required.

5. Relink Web part and excel file.

Good Luck

Adam

 

What page edits did you do? I have this same problem and all I have is the Excel Web Access part on the page. Please advise.

Side note: this only happens when on a Site Page, there doesn't appear to be an issue when using a Web Part Page. However, for my needs I would like to use a Site Page.

• Edited by cha d 14 hours 57 minutes ago