Exception occurs while processing SSAS cube [duplicate] - ssas

This question already has answers here:
SQL Server 2012: Login failed for user 'NT Service\MSSQLServerOLAPService'.; 28000
(8 answers)
Closed 7 years ago.
while creating cube it show deployment as success but while processing cube below exception occurs.
OLE DB error: OLE DB or ODBC error: Login failed for user 'NT Service\MSSQLServerOLAPService'.; 28000.

Your SSAS service account doesn't have permissions to access warehouse DB. You can either explicitly set data source credentials in cube's data source or grant database permissions to NT Service\MSSQLServerOLAPService in MSSQL.

Related

How to resolve an intermittent issue in linked server?

Getting the below intermittent error, when inserting the records in Oracle DB using a stored procedure in SQL via linked server.
The OLE DB provider "OraOLEDB.Oracle" for linked server "linkedServer" supplied inconsistent metadata. An extra column was supplied during execution that was not found at compile time.
When I re-run the stored procedure with same arguments again and its successful.

What can be the Cause of this Error "Communication link failure "?

Respected Experts,
I have just joined a new company.
We have created a replicated database to store the replicated data from MS power Bi. We made a stored procedure to select data from cloud database and insert that in our server. When we are executing our stored procedure to get last 12 months data we are getting this error:
Executed as user: abcserver\useradmin. Stored Procedure failed with error:TCP Provider: An existing connection was forcibly closed by the remote host. [SQLSTATE 42000] (Error 50000) OLE DB provider "SQLNCLI11" for linked server "BI-Server" returned message "Communication link failure". [SQLSTATE 01000](Error 7412). The step failed.
The main points of consideration are:
Last week It was working perfectly for 12 months data. Just stopped 3 days before.
Currently it is successfully working for 3 months data. But we are unable to get more then that.
There is not any dramatic change in the database records(means row count)
Can you please guide me what can be the cause for this error. Please help.
I have tried increasing the packet size and connection timeout but does not work.
Thanks

Got errors when trying to deploy cube

I tried to deploy my cubes but got these error on visual studio 2012. Please help me as i am new and i dont understand what to do. Errors are listed below.
Internal error: The operation terminated unsuccessfully.
OLE DB error: OLE DB or ODBC error: Cannot open database "datawarehouse" requested by the login. The login failed.; 42000.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Datawarehouse', Name of 'Datawarehouse'.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed.
Errors in the OLAP storage engine: An error occurred while the 'Cust Id' attribute of the 'Customer' dimension from the 'dwCube' database was being processed.
Server: The current operation was cancelled because another operation in the transaction failed.
OLE DB error: OLE DB or ODBC error: Cannot open database "datawarehouse" requested by the login. The login failed.; 42000.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Datawarehouse', Name of 'Datawarehouse'.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Route', Name of 'Route' was being processed.
Errors in the OLAP storage engine: An error occurred while the 'Route Id' attribute of the 'Route' dimension from the 'dwCube' database was being processed.
Please check if the connection for cube is available or not
Connect to your cube by SSMS
And find the cube datasource by expand CubeDataBase Folder->DataSouce Folder->DataSouce.
3.Double click the DataSouce and Open the Connectin String property window.
4.Type the valid cube server name, username and password.
5.Make sure succeed to test the connection.
6.Then try to process your cube manually.
MDXHelper : IDE to Write, Analyze, Tuning, Debug MDX efficiently

Using linked server returns error - "Cannot obtain the schema rowset for OLE DB provider"

I tried to move data aka ETL from one sql server to another as mentioned in a previous question - Copy data from one column into another column. Now, I get an error when I try to execute a query.
Query -
INSERT INTO [Target_server].[Target_DB1].[dbo].[Target_Table1](Target_Column1)
SELECT Source_Column222
FROM [Source_server].[Source_DB1].[dbo].[Source_Table1]
WHERE Source_Column1 = 'ID7162'
Error -
OLE DB provider "SQLNCLI" for linked server "MYLINKEDSERVER" returned message "Unspecified error".
OLE DB provider "SQLNCLI" for linked server "MYLINKEDSERVER" returned message "The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator.".
Msg 7311, Level 16, State 2, Line 1
Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI" for linked server "MYLINKEDSERVER". The provider supports the interface, but returns a failure code when it is used.
If your wrote that simple select is not working, the issue is in security configuration of the linked server and permissions which your user receive there.
Among this, when you execution your query, you don't need to specify the server name and DB name for both parts - source and target. You simply need to execute the query on target server and target database. In this case your query instead of
INSERT INTO [Target_server].[Target_DB1].[dbo].[Target_Table1](Target_Column1)
SELECT Source_Column222
FROM [Source_server].[Source_DB1].[dbo].[Source_Table1]
WHERE Source_Column1 = 'ID7162'
will looks like the following:
INSERT INTO [dbo].[Target_Table1](Target_Column1)
SELECT Source_Column222
FROM [Source_server].[Source_DB1].[dbo].[Source_Table1]
WHERE Source_Column1 = 'ID7162'
and you need your connection to be opened on server [Target_server] and database [Target_DB1]. Also the linked server security properties need to be checked on [Target_server] against the [Source_server].
If you are using loop back linked server (linked server refering to the same database in the same server) then refer the below mentioned link:
Transaction with loopback linked server - locking issues
If that is not the case, this is the solution provided by Microsoft.

SQL Server 2008 R2 Performance Studio - Data Collection works but View Report throws 'Failed to connect...' 18456 error

I set up SQL Server 2008 R2 Performance Studio data collection from this tutorial. Data collection appears to be working great but, when I right-click on Data Collection --> Reports --> Management Data Warehouse and then select any of the reports to load, I get the following error:
'Failed to connect to server sql1.myserver.com. --< Login failed. The login is from an untrusted domain and cannot be used with Windows Authentication.'
This is strange because I set up a new SQL login for MDW to use, and I am logged in to SQL Management Studio with a SQL login as well. A look at the SQL logs gives me this:
Date 9/14/2011 11:12:13 PM
Log Data Collection (Query Statistics)
Log ID 179
Source Query Statistics
Collection Set Name Query Statistics
Collection Item Name
Status Error
Runtime Execution Mode Upload
Start Time 9/14/2011 11:12:13 PM
Last Iteration Time
Finish Time 9/14/2011 11:12:13 PM
Duration (ms) 0
Operator NT AUTHORITY\SYSTEM
Package Execution ID
Event
Data Code
Message
Failed to connecto to the management data warehouse server Inner Error ------------------>
Row#: 0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "IP-0AAAEEDF" Procedure: "" Line#: 1 Error Number: 18456 Error State: 1 Error Severity: 14 Error Message: "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'." Help File: "(null)", Help context: 0 GUID: {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}.
OLE DB Error Record dump end.
If anyone can provide any help at all, it would help me out immeasurably!
Best regards,
Sebastian
There may be some datacollection configuration issue. In my case it is working fine. From error message it is obvious there is some authentication issue "sql1.myserver.com. --< Login failed". So Try to configure data collection with different credentials.