none
OLE DB error: OLE DB or ODBC error: Login failed for user 'MyServer\Administrator'.; 28000.

    Question

  • Hi,

    Whilst building a component within a cube on a new server I receive the following error; -

    "OLE DB error: OLE DB or ODBC error: Login failed for user 'MyServer\Administrator'.; 28000."

    I have set the Impersonation Information to Inherit.

    On several other servers the process cube works fine.

    I can manually sucessfully build the cube on the new server by setting  Impersonation Information to a specific Windows User Name and Password.

    However setting "Impersonation Information to a specific Windows User Name and Password" breaks the SSIS packages which dynamically nightly refreshes the data within the cube.

    SSIS Package error; -

    "Message
    Executed as user: MyServer\Administrator. Microsoft (R) SQL Server Execute Package Utility  Version 10.50.2500.0 for 64-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.   
    Started:  05:17:38  Error: 2012-06-14 05:17:47.51     Code: 0x00000000     Source: My SSIS update SSAS Dimension Component Execute DDL Task   
    Description: A connection cannot be made. Ensure that the server is running.  End Error  DTExec: The package execution returned DTSER_FAILURE (1). 
    Started:  05:17:38  Finished: 05:17:47  Elapsed:  9.626 seconds.  The package execution failed.  The step failed."

    So my question is what change do I need to make to the new server so I can build the cube successfully when setting the Impersonation Information to Inherit?

    Thanks in advance,

    Kieran.


    If you have found any of my posts helpful then please vote them as helpful. Kieran Patrick Wood MCTS BI,MCC, PGD SoftDev (Open), MBCS http://www.innovativebusinessintelligence.com/ http://uk.linkedin.com/in/kieranpatrickwood

    Thursday, June 14, 2012 10:16 AM

Answers

  • I've fixed it, phew!

    Instructions as follows for anyone else who may get this issue; -

    1) Launch "SQL Server Configuration Manager"

    2) Right click on SSAS service

    3) Select log on as Network Service

    4) Restart SSAS service.

    I hope this helps someone!


    If you have found any of my posts helpful then please vote them as helpful. Kieran Patrick Wood MCTS BI,MCC, PGD SoftDev (Open), MBCS http://www.innovativebusinessintelligence.com/ http://uk.linkedin.com/in/kieranpatrickwood

    Thursday, June 14, 2012 10:42 AM

All replies

  • I've fixed it, phew!

    Instructions as follows for anyone else who may get this issue; -

    1) Launch "SQL Server Configuration Manager"

    2) Right click on SSAS service

    3) Select log on as Network Service

    4) Restart SSAS service.

    I hope this helps someone!


    If you have found any of my posts helpful then please vote them as helpful. Kieran Patrick Wood MCTS BI,MCC, PGD SoftDev (Open), MBCS http://www.innovativebusinessintelligence.com/ http://uk.linkedin.com/in/kieranpatrickwood

    Thursday, June 14, 2012 10:42 AM
  • Nope, have something similar, but your option does not work for me. Now I receive the cannot-login-error for the networdk service.

    Looking further...


    Greetz, FreeHansje

    Monday, September 24, 2012 12:39 PM
  • Hi FreeHansje,

    I am experiencing a similar issue and Kieran's solution did not resolve it for me. Did you come across another appraoch that worked for you?

    Thank you

    Seamus

    Monday, October 08, 2012 5:41 AM
  • Hi,

    Can you provide any more information surrounding your error please?

    It's very difficult for me to replicate your error. However if you are able to supply further information I will make best endevours to help you find a solution.

    Kind Regards,

    Kieran.


    If you have found any of my posts helpful then please vote them as helpful. Kieran Patrick Wood MCTS BI,MCC, PGD SoftDev (Open), MBCS http://www.innovativebusinessintelligence.com/ http://uk.linkedin.com/in/kieranpatrickwood

    • Proposed as answer by Yuri.Baijnath Friday, June 21, 2013 9:09 AM
    • Unproposed as answer by Yuri.Baijnath Friday, June 21, 2013 9:09 AM
    Friday, October 19, 2012 4:03 PM
  • Hi guys.

    i was experiencing the same problem.

    Solution is quite simple, came across it here: http://shahfaisalmuhammed.blogspot.com/2012/09/login-failed-for-mssqlserverolapservice.html

    Basically, SQL Server Analysis Services will use the service account(by default) to pull data from the data source (the database server that hosts the data). If your Analysis Services instance is running under the account 'NT Service\MSSQLServerOLAPService', then this account will be used(by default) to read data from the databases and if the account doesn't have read access, you will get the above error. To resolve this, just grant the account read access to the relational database(s) you are trying to pull data from.

    • Proposed as answer by Yuri.Baijnath Friday, June 21, 2013 9:11 AM
    Friday, June 21, 2013 9:11 AM
  • Hey,

    i just tried what Yuri described...i was mis understanding the error message..

    the thing is, the project is trying to access the data source using whatever is set in the impersonation..

    most tutorials i saw used the service account, which is supposed to be configured correctly to have read access to the database where SQL SERVER database engine is installed...which wasnt the case here..

    once i used a specific Windows account user and password, it worked..

    thanks for your post Yuri

    Thursday, July 18, 2013 7:02 AM
  • Glad to help Mazazino.
    Thursday, July 18, 2013 7:11 AM
  • Go Solution Explorer --> Data Sources --> Change the impersonation information

    |__>use current user credentials

    Tuesday, February 25, 2014 6:59 AM