How to Process Cubes on Different Server?

Shohei 1 Reputation point
2020-08-18T05:50:26.93+00:00

Hi guys,

I am trying to process SSAS cubes on server"B" by kicking SSIS on server"A" with the EffectiveUserName option.
The job executing user is an AD user whitch has admin authority on both server "A" and "B", and also has SSAS admin on server"B".
The user specified in EffectiveUserName is Windows local user on server"B".

By kicking the SSIS, I get below.
'We can’t sign you with this credential because your domain isn’t available. Make sure your device is connected to your organization’s network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.'

Do you have any suggestions to solve this problem?

SQL Server Analysis Services
SQL Server Analysis Services
A Microsoft online analytical data engine used in decision support and business analytics, providing the analytical data for business reports and client applications such as Power BI, Excel, Reporting Services reports, and other data visualization tools.
1,258 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lukas Yu -MSFT 5,816 Reputation points
    2020-08-19T03:22:20.293+00:00

    Hi,
    It is quite confusing since if the domain/user has permission as described , this error should not pop up.
    I suspect it has something to do with the account permission.
    Could you try to set with other account or create a new test AD account for this operation see if it works?

    1 person found this answer helpful.
  2. Darren Gosbell 2,376 Reputation points
    2020-08-20T04:12:55.277+00:00

    The job executing user is an AD user whitch has admin authority on both server "A" and "B", and also has SSAS admin on server"B".

    If this is the case why are you trying to use a different user? If the user executing the job is already an admin it should have rights to processing the cube

    The user specified in EffectiveUserName is Windows local user on server"B".

    It sounds like this is the cause of your issue. I'm guessing from the error that SSIS is trying to login and execute the process as the server B user which it can't do as it's running on Server A

    0 comments