Solved

Error deploying tabular endpoint - "A device attached to the system is not functioning"

  • 17 January 2024
  • 7 replies
  • 132 views

During deployment of a tabular endpoint in 20.10.44.64 the error listed below occurs. The same error appears for multiple people in my organization, also in TimeXtender 6346.1

The error only occurs when deploying, not when executing. In SQL Server Management Studio (Analysis Server), the executed tables do occur, but remain empty. 

Naturally, connecting to the endpoint in Power BI is not possible.

 

Error:

Failed to save modifications to the server. Error returned: 'The following system error occurred:  A device attached to the system is not functioning. 
The following system error occurred:  A device attached to the system is not functioning. 
The following system error occurred:  A device attached to the system is not functioning. 
The following system error occurred:  A device attached to the system is not functioning. 
The following system error occurred:  A device attached to the system is not functioning. 
The following system error occurred:  A device attached to the system is not functioning. 
An error occurred while creating persistence directories for the Schema 'BusinessCase' in parallel.
'.

Details:

Failed to save modifications to the server. Error returned: 'The following system error occurred:  A device attached to the system is not functioning.  ...
Module: Microsoft.AnalysisServices.Tabular
Microsoft.AnalysisServices.OperationException
   at Microsoft.AnalysisServices.Tabular.Model.SaveChangesImpl(SaveOptions options)
   at TimeXtender.Tabular.Engine.TabularEngine.CreateDatabase(Model model, String databaseName, Server server, Boolean isForOfflineProcessing)
   at TimeXtender.Tabular.Engine.TabularEngine.CreateModel(Model model)
   at TimeXtender.DataManager.TabularEndpointDeployExecute.Deploy(TabularEndpoint endpoint, VariableResolveObject variableResolveObject, Boolean scriptDatabase)
   at TimeXtender.DataManager.StepEndpointDeploy.DoAbstractStep(StepSetup stepSetup)
 

 

Hope anyone can help! Thanks in advance

icon

Best answer by rory.smith 18 January 2024, 08:32

View original

7 replies

Userlevel 6
Badge +5

Hi @mvansprundel 

Is your DW Instances or DWH on a local server that is connecting to the Azure Analysis Services?

If so it may be the Gateway that has issues.

If the DW Instances or DWH on an Azure server what rights does the setup of the Tabular endpoint have on the Azure SQL.

Userlevel 4
Badge +5

Dear @mvansprundel ,

Does your account or the service account that TX runs on has the rights to makes changes in the Analysis Services or AAS?

@Thomas Lind it is on a local server
@daniel it has the correct security credentials (db_datareader). Or do you mean something else?

Userlevel 6
Badge +5

Hi @mvansprundel 

As Daniel alludes to it can be about the user running the tabular call not having enough rights on the specific DW Instance database.

For local SQL to local Analysis Services it is the service user for the Analysis Services that needs to have rights, but for Azure it is different.

Explained here

  1. In the Processing Authentication list, select how the Tabular service will connect to the data warehouse.
    • Click Service account to use the SQL Server Analysis Services service account.
    • Click Windows user to use another user and then enter the user name for the user in the Username box and the corresponding password in the Password box.

How is the setup for yours?

Userlevel 5
Badge +7

Hi,

 

do you have (or had) Power BI installed on the same VM you are deploying from? If so it can be the following:

 

If you are ever confronted with errors from Analysis Services: " The following system error occurred: A device attached to the system is not functioning" when deploying/executing PowerBI endpoints on a machine which has PowerBI installed on it:

  • Open intl.cpl (regional settings)
  • Change all settings in here to be US english (all tabs, all links & all buttons)
  • un-Install Power BI x64 (yes, really)
  • Reboot
  • Change the pulldown at the top of the locale settings back to what it was
  • Reboot
  • Download the regional version of PowerBI that matches those settings
  • Happily choose English while installing PowerBI

 

For some mysterious reason a PowerBI install on a non-US English locale can break Analysis Services

 

See: https://community.powerbi.com/t5/Issues/PBI-X64-error-July-2...

Userlevel 4
Badge +5

Thanks @rory.smith 
Super weird issue. Really good to know

Thank you @rory.smith. This indeed helped to solve the issue!

Reply