Technical FAQs

Ask a Question

PME 7.2/8.0: Unable to save Tables - "There has been an error while trying to save the Table"

While attempting to save Tables within PME 7.2.x / 8.x the following error occurs:

"There has been an error while trying to save the Table: ". Please check all fields and try again.

In this case, the user has verified that a valid name has been assigned to the table, parameters are selected and sources/device are selected correctly.

Product Line
StruxureWare Power Monitoring Expert 7.2.x, 8.x
Internet Explorer 11

Power Monitoring Expert Web Applications


Handling an exception. Exception details: System.InvalidOperationException: User is not authenticated. Real Time Tables Service require a valid user.
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at SyncInvokeSavePersistenceItem(Object , Object[] , Object[] )
   at UI.ApplicationFramework.Web.Services.RealTimeTablesService.SavePersistenceItem(PersistenceItem item)
   at UI.ApplicationFramework.Web.Services.RealTimeTablesService.VerifyAuthenticatedUser(

are found in the AppModsServiceTrace.svclog trace log file.


1. Enable the Anonymous Authentication and Forms Authentication for the Web and SystemDataService virtual roots in IIS by referring to the steps below:

- Launch the Control Panel, go to 'Administrative Tools' and run "Internet Information Services (IIS) Manager". 
- Expand the Servername, Sites, Default Web Site and Select "Web". Within the 'IIS' section in the window double-click on 'Forms Authentication' and ensure that the A
nonymous Authentication and Forms Authentication are enabled.
- Expand the Servername, Sites, Default Web Site and Select "SystemDataService". Within the 'IIS' section in the window double-click on 'Forms Authentication' and ensure that the Anonymous Authentication and Forms Authentication are enabled.

2. Restart the applicable server and application services:
  • Run the iisreset command from a command prompt windows.
  • Restart the ApplicationModules CoreServicesHost, DataServiceHost and ProviderEngineHost services.
3. Re-attempt to save tables within PME.

If the problem still persists perform the following steps:
NOTE:  Ensure that a copy of the 'Web.config' file is backed up to a secure location on the server prior to proceeding with the file modifications.

1. Enable Web Tracing the Web RealtimeService by referring to the following KB: FA276441
2. Enable the IncludeExceptionDetailInFaults by referring to the steps below where minor modification will be performed to the 'Web.config' file for the Tables web service:
  • Stop the ApplicationModules CoreServicesHost, DataServiceHost and ProviderEngineHost services.
  • Make a backup copy of the Web.config file for the Tables web service, which you can find at the following location:  <PME installation folder>\Applications\ApplicationFramework
    • E.g.  C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\Applications\ApplicationFramework\Web.config
  • Add the following section to the Web.config file:
    • <system.diagnostics>
                  <source name="System.ServiceModel" 
                          switchValue="Information, ActivityTracing"
                     <add name="traceListener" 
                         initializeData= "C:\Log\TablesServiceTrace.svclog" />

    • Notes:
      • The directory where the trace file is saved to on the hard drive may be modified by changing the value for initializeData.
      • It is recommended to place this new XML section below the <system.serviceModel>.
  • Perform another modification to the Web.config file in order to include detailed exception information:
    • Find the <behaviors> section underneath <system.serviceModel>
    • Change the includeExceptionDetailInFaults value to "true" as in the following (changes are underined):
      • <behaviors>
                <behavior name="">
                    <serviceMetadata httpGetEnabled="true" />
                    <serviceDebug includeExceptionDetailInFaults="true" />
                <behavior name="metadata">
                    <serviceMetadata httpsGetEnabled="true" httpGetEnabled="true" />
3. Ensure that the specific section below matches the one located within "Web.config" file found at the following location:  <PME installation folder>\Applications\ApplicationFramework
  • ​E.g. C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\Applications\ApplicationFramework\Web.config
<!-- Lines below required for authentication coordination between ApplicationFramework.Web and SystemDataService. -->
    <authentication mode="Forms">
      <forms name=".APPLICATIONFRAMEWORK" loginUrl="/SystemDataService/Auth" defaultUrl="~/" timeout="2880" protection="All" enableCrossAppRedirects="true" />
    <machineKey decryption="AES" decryptionKey="AutoGenerate" validation="HMACSHA256" validationKey="AutoGenerate" />
    <sessionState mode="StateServer" stateConnectionString="tcpip=" stateNetworkTimeout="10" cookieless="false" timeout="20" />
    <httpRuntime targetFramework="4.5" />
    <compilation batch="true" targetFramework="4.5" />
4. Examine the generated trace files for specific errors and submit those to Technical Support. 
5. To stop the tracing, restore the backup copy of Web.config
Was this helpful?
What can we do to improve the information ?