Archive for the ‘OfficeWebApps’ Category

Excel Web Services Unable to process request

Thursday, November 20th, 2014

Excel Web Services error in SharePoint

Unable to process the request. Wait a few minutes and try performing this operation again – Event Viewer Error 5231, 5239, 5240

Version: 1.5, Created: 11/20/2014, Last Updated: 12/15/2014

Error:

When you click on an excel file to open it in Excel web services, you get this error:
Unable to process the request. Wait a few minutes and try performing this operation again.

SharePoint Excel Services - Unable to Process Request Error
SharePoint Excel Services – Unable to Process Request Error

Few Suggestions from other sources:
1. Stopped and started Excel Calculation services from SharePoint Central Admin > Servers in Farm page > ServerName > Services

2. Make sure Excel Service app is associated with the SharePoint web app

3. Under CA > SA > Excel Services > Global Settings > Load Balancing Scheme > change the settings from ‘Workbook URL’ to ‘Local’. but same issue

4. App Pool Recycle
http://blogs.technet.com/b/excel_services__powerpivot_for_sharepoint_support_blog/archive/2013/01/24/excel-services-2010-quot-unable-to-process-the-request-quot-maximum-private-bytes-size-exceeded-unable-to-complete-the-operation.aspx

5. Excel Service Account for CDB permisions
http://support.microsoft.com/kb/981293

6. Edit host entry and loopback FQDN
7. IISReset
8. Reboot
9. Re-run psconfigui

10 no route site collection had been create when testing the service. https://<your application name>/_layouts/EwaStringsHandler.ashx/

11. Disable ASP.Net Impersonation in IIS http://blog.armgasys.com/?p=133

ULS Log Errors:

System.TypeInitializationException: The type initializer for ‘Microsoft.Office.Excel.Server.CalculationServer.ExcelServerApp’ threw an exception. —> System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)     at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException,

TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)     at Microsoft.Office.Server.Diagnostics.ULS.SendWatsonOnExceptionTag(UInt32 tagID, ULSCatBase categoryID, String output, Boolean

fRethrowException, TryBlock tryBlock, CatchBlock catchBlock, FinallyBlock finallyBlock)     at Microsoft.Office.Excel.Server.CalculationServer.ExcelServerApp..ctor()     at Mic…

There was an error in communicating with Excel Calculation Services

http://SPAppServer013:32843/0753ec6cff654ce09f369241f98d06a7/ExcelService*.asmx exception: An error has occurred. [Session:  User: domainSPFarmAdmSvcAct].

ServerSession.ProcessServerSessionException: An exception thrown during ExecuteWebMethod failed to convert to ECSException for server:

http://SPAppServer013:32843/0753ec6cff654ce09f369241f98d06a7/ExcelService*.asmx, method: GetHealthScore, ex:

Microsoft.Office.Excel.Server.CalculationServer.Proxy.ServerSessionException: An error has occurred. —>

System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the se…..

Event Viewer Logs

Error 1:
I saw this error logged every 5 mins in on a WFE server.

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Server
Date:          12/15/2014 1:04:20 PM
Event ID:      2159
Task Category: Unified Logging Service
Level:         Error
Keywords:      
User:          companySPFarmSvcAct
Computer:      SPWFEServer01.company.com
Description:
Event 5240 (Excel Services Application) of severity ‘Error’ occurred 10 more time(s) and was suppressed in the event log
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-SharePoint Server” Guid=”{C33B4F2A-64E9-4B39-BD72-F0C2F27A619A}” />
    <EventID>2159</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>31</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-12-15T19:04:20.673990100Z” />
    <EventRecordID>510279</EventRecordID>
    <Correlation />
    <Execution ProcessID=”7012″ ThreadID=”6000″ />
    <Channel>Application</Channel>
    <Computer>SPWFEServer01.company.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”int0″>5240</Data>
    <Data Name=”string1″>Excel Services Application</Data>
    <Data Name=”int2″>10</Data>
  </EventData>
</Event>

Error 2:
On WFe 3 server:

Log Name:      Application
Source:        Microsoft-SharePoint Products-Excel Services Application
Date:          12/15/2014 1:13:41 PM
Event ID:      5240
Task Category: Web Front End
Level:         Error
Keywords:      
User:          companySPFarmSvcAct
Computer:      SPWFEServer03.company.com
Description:
There was an error in communicating with Excel Calculation Services 

http://SPAppServer03:32843/0753ec6cff654ce09f369241f98d06a7/ExcelService*.asmx exception: An error has occurred.
[Session: 
User: companySPFarmSvcAct].
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-Excel Services Application” Guid=”{278E40D0-FDAA-4EB4-AB6B-9E0AD6BDBE79}” />
    <EventID>5240</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>8</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-12-15T19:13:41.610718500Z” />
    <EventRecordID>529546</EventRecordID>
    <Correlation />
    <Execution ProcessID=”5588″ ThreadID=”7280″ />
    <Channel>Application</Channel>
    <Computer>SPWFEServer03.company.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>http://SPAppServer03:32843/0753ec6cff654ce09f369241f98d06a7/ExcelService*.asmx</Data>
    <Data Name=”string1″>An error has occurred.</Data>
    <Data Name=”string2″>
    </Data>
    <Data Name=”string3″>companySPFarmSvcAct</Data>
  </EventData>
</Event>

Error 3:
Log Name:      Application
Source:        Microsoft-SharePoint Products-Excel Services Application
Date:          12/15/2014 11:28:31 AM
Event ID:      5239
Task Category: Web Front End
Level:         Error
Keywords:      
User:          companySPFarmSvcAct
Computer:      SPWFEServer02.company.com
Description:
There was an error in communicating with Excel Calculation Services 

http://SPAppServer03:32843/0753ec6cff654ce09f369241f98d06a7/ExcelService*.asmx exception: The remote server returned an error: (503) Server 

Unavailable.
[Session: 
User: companySPFarmSvcAct].
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-Excel Services Application” Guid=”{278E40D0-FDAA-4EB4-AB6B-9E0AD6BDBE79}” />
    <EventID>5239</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>8</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-12-15T17:28:31.611714800Z” />
    <EventRecordID>502287</EventRecordID>
    <Correlation />
    <Execution ProcessID=”2068″ ThreadID=”8976″ />
    <Channel>Application</Channel>
    <Computer>SPWFEServer02.company.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>http://SPAppServer03:32843/0753ec6cff654ce09f369241f98d06a7/ExcelService*.asmx</Data>
    <Data Name=”string1″>The remote server returned an error: (503) Server Unavailable.</Data>
    <Data Name=”string2″>
    </Data>
    <Data Name=”string3″>companySPFarmSvcAct</Data>
  </EventData>
</Event>

Error 4:
Log Name:      Application
Source:        Microsoft-SharePoint Products-Excel Services Application
Date:          12/15/2014 11:28:31 AM
Event ID:      5231
Task Category: Web Front End
Level:         Error
Keywords:      
User:          companySPFarmSvcAct
Computer:      SPWFEServer02.company.com
Description:
Unable to reach Excel Calculation Services http://SPAppServer03:32843/0753ec6cff654ce09f369241f98d06a7/ExcelService*.asmx.
[Session: 
User: companySPFarmSvcAct]
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-Excel Services Application” Guid=”{278E40D0-FDAA-4EB4-AB6B-9E0AD6BDBE79}” />
    <EventID>5231</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>8</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-12-15T17:28:31.611714800Z” />
    <EventRecordID>502286</EventRecordID>
    <Correlation />
    <Execution ProcessID=”2068″ ThreadID=”8976″ />
    <Channel>Application</Channel>
    <Computer>SPWFEServer02.company.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>http://SPAppServer03:32843/0753ec6cff654ce09f369241f98d06a7/ExcelService*.asmx</Data>
    <Data Name=”string1″>
    </Data>
    <Data Name=”string2″>companySPFarmSvcAct</Data>
  </EventData>
</Event>

Resolution:

There are few different resolutions you can try. In my case mostly restarting the Excel Calculation Services resolved the issue.

1. Restart excel calculations services
2. Recycle app pool
3. Make sure the account running excel calculation service is not locked
4. Reboot the server

1. Restart excel calculations services

I stopped and started the Excel Calculation services from within SharePoint Central Administration on following servers in this order:

SPAppServer01 – App
SPAppServer02 – App
SPAppServer03 – App

To stop and then start the Excel Calculation Services follow steps:
1. Go to SharePoint Central Admin site

2. Click System Settings > Manage Servers in This Farm

3. Find the servers in the farm that are running ‘Excel Calculation Services’

4. Click on one server name from that list that is running the service. Start with Web Server (if one is running the service),

5. On next page titled ‘Services on Server: servername ‘ locate the ‘Excel Calculation Services’ and click stop under action column

SharePoint Excel Services Restart Excel Calculation Services in Central Admin
SharePoint Excel Services Restart Excel Calculation Services in Central Admin

6. Refresh the page after few seconds and make sure the service is in stopped status

7. Once the Service show stopped status, click on Start under action column to start the service

8. Refresh the page for few seconds to make sure the Excel Calculation Service shows Started under status column

9. Go back to the page under step 2 above and follow steps for next server

10. Test one Excel file on the Sharepoint site by opening it in browser

Instead of restarting the servers or performing doing IISReset, stopping and starting the Excel service helped resolve the issue. Due to farm serving other critical apps out of SharePoint, server reboot and IISReset were not an option.

References:

  1. Error communicating with Excel Services Application – Events 5231 5239 5240
  2. Stefan Johansson – http://www.stefanjohansson.org/2013/03/excel-services-unable-to-process-the-request-wait-a-few-minutes-and-try-performing-this-operation-again/
  3. Armgasys – http://blog.armgasys.com/?p=133

Keywords:
  • SharePoint Unable to process the request
  • Excel Unable to process the request
  • error in communicating with Excel Calculation Services
  • Excel Services Unable to process the request
  • SharePoint farm Unable to process the request
  • SharePoint Excel Services Gotchas
  • SharePoint Excel Services issues
  • SharePoint Excel Services remedies
  • SharePoint Excel Services fixes
  • Event Viewer Error 5231
  • Event Viewer Error 5239
  • Event Viewer Error 5240
  • Event Viewer Error 2159
  • Event ID 5231
  • Event ID 5239
  • Event ID 5240
  • Event ID 2159
  • Fix for Event Viewer Error 5231
  • Fix for Event Viewer Error 5239
  • Fix for Event Viewer Error 5240
  • Fix for Event Viewer Error 2159

SharePoint Excel Services Unable to Save Workbook

Friday, November 14th, 2014

SharePoint Excel Services Unable to Save Workbook

Version: 1.0

Scenario:

A user opens an Excel file for editing using ‘Edit in Browser’ option.

SharePoint Excel Web Services - Edit In Browser an Excel File
SharePoint Excel Web Services – Edit In Browser an Excel File

Error:

After sometime in the edit mode, the user gets the message

Unable to Save Workbook

We will try again automatically, but you should try to save your workbook to another location or click Open in Excel.

There will be an error dialog box that says:
Your changes could not be saved. It is recommended that you select Open in Excel or try to save your changes to a different location immediately. If your changes can still not be saved after a few more minutes, your session will be ended to prevent any more loss of data.

SharePoint Excel Web Services - Unable to Save Workbook Error
SharePoint Excel Web Services – Unable to Save Workbook Error

Event Viewer Errors on SharePoint Application Servers running Excel Services:

1. Error on App Server 1 Event ID 7935

Log Name:      Application
Source:        Microsoft-SharePoint Products-Excel Services Application
Date:          11/6/2014 1:53:25 PM
Event ID:      7935
Task Category: Excel Calculation Services
Level:         Information
Keywords:    
User:          domainSPFarmAct
Computer:      SPAppServer1.domain.com
Description:
Unable to save the following workbook: http://sharepoint.domain.com/sites/BizSegment/Dept1/Financial

Documents/MonthlyKPIReport2015.xlsx.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-Excel Services Application” Guid=”{278E40D0-FDAA-4EB4-AB6B-9E0AD6BDBE79}” />
    <EventID>7935</EventID>
    <Version>14</Version>
    <Level>4</Level>
    <Task>2</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-11-06T19:53:25.232766900Z” />
    <EventRecordID>720780</EventRecordID>
    <Correlation ActivityID=”{00020DF6-D14B-13A9-0000-000050F7B00B}” />
    <Execution ProcessID=”5088″ ThreadID=”7456″ />
    <Channel>Application</Channel>
    <Computer>SPAppServer1.domain.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>http://sharepoint.domain.com/sites/BizSegment/Dept1/DocumentLib/MonthlyKPIReport2015.xlsx</Data>
  </EventData>
</Event>

2. Error on App Server 1 with Event ID 0 – Symantec Protection for SharePoint Servers

Log Name:      Application
Source:        Symantec Protection for SharePoint Servers Service
Date:          11/6/2014 1:57:35 PM
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SPAppServer1.domain.com
Description:
Module=ScanObject.Scan | Exception message=Failed to connect to an IPC Port: The system cannot find the file specified.
  | Stack=
Server stack trace:
   at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel,

Int32 timeout)
   at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel

level, Int32 timeout)
   at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream

requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Symantec.Sharepoint.Shared.InterfaceLibrary.ILoadBalancingService.GetAvailableScanEngine(ScanEngine& oScanEngine)
   at Symantec.Sharepoint.RTCommandClient.RTCommand.GetAvailableScanEngine(ScanEngine& oScanEngine)
   at Symantec.Sharepoint.ScanLibrary.ScanObject. (IntPtr inILockBytes, Int32& pdwStatus, String& wzVirusInfo)
Event Xml:
<Event xmlns=’http://schemas.microsoft.com/win/2004/08/events/event’><System><Provider Name=’Symantec Protection for SharePoint Servers

Service’/><EventID Qualifiers=’0′>0</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated

SystemTime=’2014-11-

06T19:57:35.000000000Z’/><EventRecordID>720783</EventRecordID><Channel>Application</Channel><Computer>SPAppServer1.domain.com</Computer

><Security/></System><EventData><Data>Module=ScanObject.Scan | Exception message=Failed to connect to an IPC Port: The system cannot

find the file specified.
  | Stack=
Server stack trace:
   at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel,

Int32 timeout)
   at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel

level, Int32 timeout)
   at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream

requestStream, ITransportHeaders&amp; responseHeaders, Stream&amp; responseStream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&amp; msgData, Int32 type)
   at Symantec.Sharepoint.Shared.InterfaceLibrary.ILoadBalancingService.GetAvailableScanEngine(ScanEngine&amp; oScanEngine)
   at Symantec.Sharepoint.RTCommandClient.RTCommand.GetAvailableScanEngine(ScanEngine&amp; oScanEngine)
   at Symantec.Sharepoint.ScanLibrary.ScanObject. (IntPtr inILockBytes, Int32&amp; pdwStatus, String&amp; wzVirusInfo)

</Data></EventData></Event>

3. Error on App Server 2 – Event ID 8031

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          11/6/2014 2:15:01 PM
Event ID:      8031
Task Category: Topology
Level:         Error
Keywords:    
User:          domainSPFarmAct
Computer:      SPAppServer2.domain.com
Description:
An exception occurred while updating addresses for connected app {6457c0c9-76ff-4fb6-a94e-4ca7928efa06_65529aa3-7640-40b8-b262-

e557c37f87e9}. The uri endpoint information may be stale. System.InvalidOperationException: The requested application could not be found.
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ProcessCommonExceptions(Uri endpointAddress, String operationName,

Exception ex, SPServiceLoadBalancerContext context)
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ExecuteOnChannel(String operationName, CodeBlock codeBlock)
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.GetEndPoints(Guid serviceId)
   at Microsoft.SharePoint.SPConnectedServiceApplicationAddressesRefreshJob.Execute(Guid targetInstanceId)
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-SharePoint Foundation” Guid=”{6FB7E0CD-52E7-47DD-997A-241563931FC2}” />
    <EventID>8031</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>13</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-11-06T20:15:01.064016600Z” />
    <EventRecordID>864875</EventRecordID>
    <Correlation ActivityID=”{7C78DFF9-926C-43B6-AEEF-60EDDB502CA2}” />
    <Execution ProcessID=”13816″ ThreadID=”18532″ />
    <Channel>Application</Channel>
    <Computer>SPAppServer2.domain.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>6457c0c9-76ff-4fb6-a94e-4ca7928efa06_65529aa3-7640-40b8-b262-e557c37f87e9</Data>
    <Data Name=”string1″>System.InvalidOperationException: The requested application could not be found.
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ProcessCommonExceptions(Uri endpointAddress, String operationName,

Exception ex, SPServiceLoadBalancerContext context)
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ExecuteOnChannel(String operationName, CodeBlock codeBlock)
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.GetEndPoints(Guid serviceId)
   at Microsoft.SharePoint.SPConnectedServiceApplicationAddressesRefreshJob.Execute(Guid targetInstanceId)</Data>
  </EventData>
</Event>

Remedy:

During the issue the users impacted can use the Save As option in Excel Web Viewer to save the file locally if they want to edit the file and upload it later after issue is fixed.
Excel Web Services - Save As option
Excel Web Services – Save As option
The user will loose the changes they will do during this issue if they will not save a copy and then edit the saved copy.
If you continue making changes in Excel file within Excel Web Viewer, you will get a prompt with following message. At this point you have lost the changes you would have made during this session.
Either due to communication issues or a server problem, you need to be rejoined to your editing session. You may have lost changes that you made recently.
Excel Web Viewer - Session Lost and Lost recent changes Message
Excel Web Viewer – Session Lost and Lost recent changes Message
At this point go to your document library location where your Excel file is located and review the Modified date. You will notice that the modified date will not reflect that it was modified. Same will be true for version number if versioning was enabled for that library.
Excel Web Services issue - File changes not Saved
Excel Web Services issue – File changes not Saved
At this point the user will feel angry, frustrated or a lost soul based no their work. Don’t loose hope. There is some green light. Its coming in next section.

Resolution:

The above issue with Excel Web View not able to save could happen due to number of reasons. In this case when I started reviewing the SharePoint Farm for the application servers running Excel Services, I found that whenever there was error in Excel web viewer for this issue, around the same time there was an error log for Symantec Protection for SharePoint Servers. Now you know why I listed the Symantec error in the Errors section. 
I went to SharePoint Central Admin website and looked at the Symantec settings. I noticed the service was showing as stopped on one application server.
SharePoint Central Admin - Symantec Protection Service Stopped on one App Server
SharePoint Central Admin – Symantec Protection Service Stopped on one App Server
Next I looked into the Windows Services console and found the service ‘Symantec Protection 6.0 for SharePoint Servers’ in STOPPING status. In that state you can not start, stop or restart that service.
Windows Services Console - Symantec Protection Service in STOPPING State
Windows Services Console – Symantec Protection Service in STOPPING State
I terminated the Symantec Protection SPSS process using Windows Task Manager on the server. Then I started that service successfully. Later I went to SharePoint Central Admin website > Symantec Protection section and looked at that server and it was showing as Started.
SharePoint Central Admin - Symantec Protection Service in Started state on an App Server
SharePoint Central Admin – Symantec Protection Service in Started state on an App Server
Next I opened the Excel file from SharePoint location in Excel Web services in edit mode. I was able to edit the file and Excel Web Services saved the changes back to the file. I then reviewed the Modified date and it was showing the file was modified at recent time with my name under Modified Bu field. 
Excel Web Services - File changes Saved
Excel Web Services – File changes Saved
Finally the Excel Services came back on track.
Keywords:
  • Excel can not save changes
  • Excel services can not save changes
  • Excel web services can not save changes
  • Excel services lost changes
  • SharePoint Excel services lost changes
  • SharePoint Excel services not saving changes
  • SharePoint Excel services not able to edit files
  • SharePoint Excel services not able to update file
  • SharePoint Excel services oddies
  • SharePoint Excel services issues
  • Can not modify Excel in SharePoint
  • Can not modify Excel in Excel Web Services

Linked Excel Files and SharePoint

Wednesday, September 17th, 2014

Linked Excel Files and SharePoint

V: 1.0

I’ve been working lately with Microsoft Excel data report files that were linked and were uploaded to SharePoint. There are few scenarios where the linked files can cause issues if not used properly. I’m describing few scenarios below:

Scenario 1: User created MS Excel files on the desktop, linked those files (desktop or shared drive). then uploaded both files to SharePoint

Scenario 2: User created MS Excel files on the desktop, linked those files (desktop or shared drive). then uploaded only container file to SharePoint

Scenario 3: User created MS Excel files on the desktop, linked those files (desktop or shared drive). then uploaded both files to SharePoint and updated the linked files using their SharePoint links

Scenario 2 is common among Excel users. Users create linked excel files and upload only the main file aka the container file. In most cases the linked file was on the desktop of the user. Now when another user tries to open the Excel container file from SharePoint or from their desktop by copying it, they get errors / warning messages. That is due to container file not able to reach to author’s desktop file from SharePoint.

I copied the container excel file on my desktop and went through it.

MS Excel Container File that has linked files
MS Excel Container File that has linked files

Click on the File menu > Info. Under security warning section you will see the warning details.

MS Excel Container File that has linked files - File Info Security Warning section
MS Excel Container File that has linked files – File Info Security Warning section

Now you click on Enable Content from either the top middle  of file or within File > Info section in an attempt to get the complete data and you are presented with a warning as shown in following image.

Error:
We can’t update some of the links in your workbook right now.
You can continue without updating their values, or edit links you think are wrong.

MS Excel Container File Warning - Linked file not Reachable
MS Excel Container File Warning – Linked file not Reachable

You may get following warning message.

Error:
This workbook contains links to one or more external sources that could be unsafe.
If you trust the links, update them to get the latest data. Otherwise, you can keep working with the data you have.

MS Excel Container File Warning - Linked file could be unsafe warning
MS Excel Container File Warning – Linked file could be unsafe warning

How to view the Linked Files in Container Excel File:
To view the linked files from container Excel file, go to Data ribbon tab and under Connections group click Edit Links.

MS Excel Container File - Edit Links to Linked File
MS Excel Container File – Edit Links to Linked File

In Edit Links window, if you select a source, you will see its location. In situations, you will find it pointing to the local desktop profile of users. Nice work with the data report, but not nicely executed.

MS Excel Container File - Edit Links window
MS Excel Container File – Edit Links window

MS Excel Container File on SharePoint and Linked file not reachable:

Now if you try to open the file directly from SharePoint, you will get warning messages. See the URL address has been appended with the linked file address!

Error:
We can’t connect to http://sharepoint.domain.com/users/WindowsProfile/desktop/excelfile.xls

Open MS Excel File from SharePoint - Linked file missing - See URL
Open MS Excel File from SharePoint – Linked file missing – See URL

Click Ok and you will be greeted with another warning. See the image below.

Error:
Microsoft Excel cannot access the file http://sharepoint.domain.com/users/WindowsProfile/desktop/excelfile.xls. There are several possible reasons.

  • The file name or path does not exist
  • The file name is being used by another program
  • The workbook you are trying to save has the same name as a currently open workbook.
Open MS Excel File from SharePoint - Linked file missing - Possible Reasons listed
Open MS Excel File from SharePoint – Linked file missing – Possible Reasons listed

My Treat for Linked Excel Files and SharePoint:

I’ll cover the other details in of different testing scenarios may be little later as time permits. I created a container and linked files with some test data. Feel free to download and play around with it on your SharePoint test farm.

Download the Test Excel Container File and Linked File

Note it down that office Web apps doesn’t support linked files. You will get prompts when viewing the Excel container file using Office Web Apps in SharePoint.

MS Excel Container File Opened in Office Web Apps in SharePoint - Linked file not supported
MS Excel Container File Opened in Office Web Apps in SharePoint – Linked file not supported

Few Resources on the Excel Linked files:

Primer on Sharepoint Excel DataRefresh Settings

Sunday, June 1st, 2014

Primer on SharePoint Excel Data Refresh Settings

V 1.2

There are different places where you can configure the Excel data refresh settings for external data when using it with SharePoint.

a. Microsoft Excel file Data Connection Properties
b. Excel Web Viewer refresh option – viewing files in Excel Web Access
c. In Central Admin > Excel Services > Trusted File Locations
d. SharePoint Excel Web Part Properties

I created this Excel Data Refresh Options Chart that I’ve used on different projects. It shows external data refresh option in standalone MS Excel file, Excel file in a SharePoint library, in Excel Web Access and in Excel Web Access Web Part. It also shows different roles around Excel in an organization. Excel Workbook Author in some organization could be different than the SharePoint Site Admin that sets the web parts.

Softvative – MS Excel External Data Refresh Options Chart

a. MS Excel Data Connection Properties

1. Open your MS Excel file that has the data. Click on Data Ribbon tab and then click Connections.

MS Excel Data Connections Menu

2. Select one of the existing connections in your workbook and then click on Properties button.

MS Excel Data Connections Dialog Box

3. Under the Usage tab, under Refresh Control section there are refresh data settings:

  • Enable background refresh
  • Refresh every n minutes
  • Refresh data when opening the file
  • Remove data from the external data range before saving the workbook
MS Excel Data Connection – Refresh Control Settings

b. Excel Web Viewer refresh option – viewing files in Excel Web Access

You need to have SharePoint Enterprise edition for Excel Services. Hover mouse over an Excel file in a library, click on drop down arrow on right side to bring the menu and choose ‘View in Browser‘.

SharePoint Excel File in a Document Library – View in Browser

 When MS Excel file opens up in Excel Web Access, click on Data menu. SharePoint users will see these two options:

  • Refresh Selected Connection
  • Refresh All Connections
SharePoint – Excel Web Access – Data Refresh Options

c. In Central Admin > Excel Services > Trusted File Locations

Follow these steps to review / configure the Excel Services Refresh Settings. 

1. Go to SharePoint Central Admin Website 
2. Click on ‘Application Management‘ on left navigation
3. Click on ‘Manage Service Applications‘ link and then click on your Excel Service Application name
4. Click Trusted File Location

SharePoint – Excel Services Application

5. Hover mouse over one of your trusted file location and from drop down menu choose Edit.

SharePoint – Excel Web Services – Trusted File Locations

6. Scroll down and review / update values as appropriate under External Data section > External Data Cache Lifetime section for automatic and manual refresh. Default setting for both is 300 seconds (5 minutes)

  • Automatic refresh (periodic / on-open)
  • Manual Refresh

SharePoint – Excel Services – External Data Cache Lifetime

d. SharePoint Excel Web Part Properties

1. Create a new page or using existing page. Edit the page by clicking on Page ribbon tab > Edit Page. (or Site Settings > Edit Page)

SharePoint – Edit Page

2. Click on ‘Add a Web Part‘ link
3. Click on ‘Business Data‘ under Categories and then click on ‘Excel Web Access‘ under Web Parts section. Click Add button on the right side of the screen.

SharePoint – Add Web Part – Categories > Excel Web Access

4. Excel Web Access – Select a Workbook web part will come up on your page. Click on link that says ‘Click here to open the tool pane

SharePoint – Excel Web Access – Select a Workbook

5. Excel Web Access Web Part Properties section comes up on the right side of the page. Select an Excel file under Workbook field.

SharePoint – Excel Web Access Web Part Properties – top

SharePoint – Excel Web Access Web Part Properties – bottom

The default refresh connection settings on that web part are:

Section Option Default
Toolbar Menu Command Refresh Selected Connection, Refresh All Connections Checked
Interactivity Periodically Refresh if Enabled in Workbook Unchecked

You can leave the default setting for “Refresh Selected Connection, Refresh All Connections” to have that refresh option for your end users. Alternatively you can uncheck that option to remove refresh connection option for your users.

6. Optionally expand the Advanced property section of the web part and uncheck following options:
Allow Close
Allow Hide
Allow Editing in Personal View

SharePoint – Web Part Advanced Properties

7. Click Apply at the bottom right of the web part properties.
8. Review the Excel Web Access file and go to Data menu and see Refresh options.
9. Edit the web part properties again and uncheck the option “Refresh Selected Connection, Refresh All Connections“. Click Apply to save changes. Now review the Data menu and you will notice the refresh options are now removed.

SharePoint – Excel Web Access – Data menu

10. Excel Web Part property ‘Type of Toolbar‘ is by default set to full. That displays toolbar options based on settings. You can set that option to Summary, Navigation or none. These settings also hide or show refresh options in the Excel Web Access tool bar.

References:

External Data Cache Lifetime reference:
http://technet.microsoft.com/en-us/library/ff191194(v=office.14).aspx

Excel 2007 with Excel Services Reference
http://office.microsoft.com/en-us/sharepoint-server-help/refresh-external-data-in-excel-services-HA010105474.aspx

Excel Web Access Web Part custom properties (Sharepoint 2010)
http://office.microsoft.com/en-us/sharepoint-server-help/excel-web-access-web-part-custom-properties-HA010377893.aspx

Getting Started with Excel Services and Excel Web Access
http://office.microsoft.com/en-us/sharepoint-server-help/getting-started-with-excel-services-and-excel-web-access-HA010377881.aspx

Excel Services 2010 Data Refresh Flowchart: What is going on behind the scenes
http://blogs.technet.com/b/tothesharepoint/archive/2011/07/29/troubleshooting-excel-services-data-refresh.aspx

Excel Services data refresh flowchart
http://technet.microsoft.com/en-us/library/hh369968.aspx

Overview of connecting to (importing) data
http://office.microsoft.com/en-us/excel-help/overview-of-connecting-to-importing-data-HP010342748.aspx

Excel 2010 – Connection Properties
http://office.microsoft.com/client/helppreview14.aspx?AssetId=HA010342299&lcid=1033&NS=EXCEL&Version=14&tl=2&queryid=&respos=1&HelpID=22115

Excel 2010 – Refresh connected (imported) data
http://office.microsoft.com/client/helppreview14.aspx?AssetId=HP010342826&lcid=1033&NS=EXCEL&Version=14&tl=2&queryid=&respos=1&HelpID=199707

Configure Excel Services data refresh by using the unattended service account (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/hh525344(v=office.14).aspx

Configure Excel Services data refresh by using external data connections (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/hh525341(v=office.14).aspx

Keyword:

  • SharePoint  BI
  • Excel Web Access BI
  • Excel Web Services BI
  • SharePoint Business Intelligence
  • Softvative SharePoint BI Data Refresh Chart
  • Data Refresh Chart
  • Excel Data Refresh Options
  • Excel Data Refresh Settings
  • Excel Automatic Data Refresh Options
  • Excel Manual Data Refresh Options

Add new Server in Farm with SharePoint, MSPS, OWS and LPs

Tuesday, May 13th, 2014
How to add a new server to the SharePoint Farm when the farm is running:
a. SharePoint 2010
b. MS Project Server 2010
c. Office Web App Server 2010
d. Language Packs

I ran through these steps.

1. Attach Setup files to new server [CD, Virtual Cd image, or setup files]
2. Start SharePoint setup and begin the SharePoint Pre-Req install
3. It failed listing update KB976462 as causing install error
4. Re-Ran the pre-req and it worked
5. Run the SharePoint 2010 setup
6. Change drive letter for Setup Data folder to D: drive. Leave the folder location with D drive as same. Also leave the SharePoint installation directory to C: drive default location
7. At the end of setup uncheck the option to Run Configuration Wizard and click close button.
8. Install Project Server 2010 setup (follow steps 6 & 7 during its setup and don’t run config wizard)
9. Install Office Web App 2010 setup (follow steps 6 & 7 during its setup and don’t run config wizard)
10. Install Language Packs for English, Chinese, Arabic or others. Install language packs for SharePoint 2010 Server version. (follow steps 6 & 7 during each setup and don’t run config wizard)
11. Install Service Pack 2 for SharePoint 2010 Server, Project Server 2010, Office Web Apps 2010, Language Packs SP 2 for each language listed in step 10 above. (follow steps 6 & 7 during its setup and don’t run config wizard)
12. Current Farm patch version was 14.0.7105.5000
13. Download Aug 2013 CU update that matches the version number for this patch.
14. Run SharePoint Config Wizard to join the server to the farm
15. Configure and verify the new server.

Adding new SharePoint ProjectServer to Farm Issue

Friday, April 11th, 2014
Scenario:

SharePoint 2010 farm with multiple servers in web and App layer. You want to add a new Web server for Microsoft SharePoint / Microsoft Project Server, and SharePoint Configuration fails on the new server. The farm has been running Sharepoint 2010, MS Project Server 2010, Office Web Apps and Language Packs. 
Error Message:
SharePoint Products Configuration Wizard brings the following message after you select the SQL Database server and then the SharePoint Farm Configuration DB.
Server Farm Products and Patch Status
The following SharePoint Technologies based products and patches were detected on your server farm.

Error:
Some farm products and patches were not detected on this or other servers. If products or patches are missing locally, you must quit this program and install the required products and patches on this server before restarting the wizard. If products or patches are missing on other servers, you must install the required products and patches on the specific servers, and you may then click the Refresh button to perform the status check again.

Scroll down the list and you will see other updates as missing as well. In my case it listed the following updates as missing on three existing servers and the new server.
Server Farm Products Status
——————————————————–
1. Microsoft Word Server
———————
HotFix for Sharepoint Server 2010 x64    Missing on SPServer01, 02 and 03
KB2825949
Security Update for Sharepoint 2010        Missing Locally [SPServer07new]
KB2837577
2. Excel Services Components
————————–
Hotfix for Sharepoint 2010 x64              Missing on SPServer01, 02 and 03
KB2825949
Security Update for Ms Sharepoint X64 Missing Locally [SPServer07new]
KB2826029
3. Access Services
——————–
Hotfix for Sharepoint 2010 x64 Missing on SPServer01, 02 and 03
KB2825949
Security Update for 2010 MS Business Missing Locally [SPServer07new]
Productivity Servers
KB2553298
The error listed basically the MS KB 2825949 patch as missing on all existing servers. That error was misleading. That patch was existed on existing servers.
I then looked for the three patches on local server – i.e the new server. The local server was missing these updates:
The new server is missing three MS KB updates.
a. KB2826029 – Excel Services Update
b. KB2553298 – Access Services / MS Business Productivity Update
c. KB2837577 – Word Automation Service Update
I went to Microsoft Knowledge base (KB) article page for KB 2826029 – Excel Services Patch to begin with. http://support.microsoft.com/kb/2826029
There wasn’t a patch download link on that KB article. I went to the IT Professional page link on that KB article and that took me to http://technet.microsoft.com/security/bulletin/MS13-084. Under ‘Affected and Non-Affected Software’ section, click the link for the SharePoint 2010 server SP2 related links. There are links for WSS, Excel Services, Word Automation. In our case the missing update KB number matches the Excel update 2826029. I downloaded and installed the Excel update. The same way I found the other two patches.
KB2826029 – Excel Services Patch – Download Link
KB2553298 – Access / Business Productivity – Download Link
KB2837577 – Word Automation Service – Download Link
I re-ran the Sharepoint Configuration wizard and it completed successfully. New Server was now part of the farm. 
Final Conclusion:
In my case, it was key to pay attention to ‘Missing Locally’ patches in the error screen. I confirmed the missing patches on new server by using Control Panel > Uninstall a Program > View Installed Updates section.
Some blogs suggest running following command to fix the issue. In my case, those smaller patches were indeed missing.
Get-SPProduct –local
psconfig -cmd installcheck -noinstallcheck
psconfig -cmd upgrade -inplace b2b -force -cmd -installcheck -noinstallcheck