cancel
Showing results for 
Search instead for 
Did you mean: 

Service Level Accounts - SQL 2005 SSAS - Error connecting to OLAP

Former Member
0 Kudos

Hi,

Can anyone please explain what to do with the service level accounts... i am facing this problem but i cant fix it.

1. For BPC 3 accounts are created in Windows... but the BPC installation sets "System admin id" as Administrator by default during the install... therefore just 2 accounts (admin id and user id) are supposed to be created.

2. Can you please explain for Analysis Services which "log on as user" is the installation guide referring to? - After installing SQL Server 2005, pag 26.

3. On BPC, while im sending data in excel, an error shows:

==================================================

Book Name:Reporte Inicial de Prueba.xls

Application : PLANNING

Status : Success

Submitted Count : 1

Accepted Count : 1

Rejected Count : 0

- Error Message -

ExecuteBaseLogic::Error connecting to OLAP: Cannot connect to the server 'servername'. The server is either not started or too busy.

-


4. The log for OLAP shows:

Message: The flight recorder was started. (Source:
?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Log\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210005)

Message: Service started. (Source:
?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Log\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210000)

Message: Service stopped. (Source:
?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Log\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210001)

5.After some research, it found this "The only thing that allowed Analysis Services to start was to use a local user account instead of my network logon"

6. Apparently BPC "works" since i am able to send, retrieve, create dimensions and applications, but the error shows different.

Also, i am unable to modify applications. The "cubes" for applications are available in Analysis services, but im still looking how to access to the cube to see whats inside.

7. i restarted sendgovernor already and all SQL services.

Thanx in advance.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi everyone,

I managed to solve this issue, for the error displayed in excel " ExecuteBaseLogic::Error connecting to OLAP: Cannot connect to the server 'servername'. The server is either not started or too busy. ", Microsoft offers the solution in the page "Resolving common connectivity issues in SQL Server 2005 Analysis Services Connectivity Scenario".

Follow the instructions for installing 9.0 OLE DB provider and that should work.

Regards

Former Member
0 Kudos

Hi

Are you running Multi Server or Single Server configuration ?

SSAS uses windows authentication, if you are running in a multi server configuration and running OLAP under a local user, you will not be able to authenticate incoming requests.

Can you connect to the OLAP server using SQL Server Management Studio using the user account running BPC.

Kind Regards

Daniel

Former Member
0 Kudos

Hi Daniel,

Thanx, im running a single server. Actually, the Analysis services service always appears as running in the Windows services console, i am capable of connect to it using the administrator's account which is the one that i am using in BPC.

When i create an application on BPC, the "database-cube" is also created in Analysis S. but somehow the SSAS log shows "service started , service stopped"...

Regards

CV

Former Member
0 Kudos

Hi Cvelazquez

Thats strange, if you are able to connect and to create a cube from the BPC administration console, then I think your problem is not authentication nor BPC related , but SSAS and possibly SQL.

This might be a long shot, but is AUTO_CLOSE enabled on the application set database?

[SSAS keeps going down|http://forum.lessthandot.com/viewtopic.php?f=17&t=5194]

Are there any SQL dump files, or are there any issues with SQL Server which could cause SSAS to restart?

You might want to involve Microsoft, they have PS DIAG tools which could get more information and possibly give you the root cause analysis on why SSAS keeps restarting.

Kind Regards

Daniel