MSSQLServerOLAPSevice

all of a sudden my MSSQLServerOLAPSevice are stopped, rest all services are
working excelp OLAP services, i even restarted the server. In service manager
it shows 'Starting' on status bar. when i try to connect server through MSA
it gives me error 'cannot open connection to Analysis server the server is
either not started or is too busy', Can anyone help me, it's very urgent
This sounds like it could be related to KB 883656. I have seen this at a client site, where AS would restart itself every 20-30 seconds, and you will see the state cycle in Service Manager.
There is a hotfix for this bug, and it is also included in the new SP4. In order to recover from the corrupted state to allow you to apply the service pack, you'll need to do the following:
1) Using the SQL Server Service Manager, select the MSSQLServerOLAPService in the second (Services) drop-down list. Uncheck the “Auto-start service when OS starts” box.
2) Close the Service Manger. Reboot the server to get the restart process to stop looping.
3) Rename the data folder where Analysis Services stores its databases. By default, this is c:\Program Files\Microsoft Analysis Services\Data but it may be different on your system, particularly if there are alternate drives. The folder in question will have subfolders along this structure:
… Data
MyASDatabase
MyCube1
MyCube2
MyCube3
and these lowest level folders will have the many data and aggregate files for each cube inside them.
4) Create a new folder in the same directory called Data
5) Restart Analysis Services through the SQL Server Service Manager by selecting the MSSQLServerOLAPService in the second (Services) drop-down list and clicking the Start icon. Also, check the “Auto-start service when OS starts” box. Close the Service Manager.
This should get your instance back to normal, the cubes will rebuild from the stored metadata next time that you use them. You will need to reprocess.
"Pravin" <Pravin@.discussions.microsoft.com> wrote in message news:64D82324-1604-4627-8A9E-67186A547AA2@.microsoft.com...
> all of a sudden my MSSQLServerOLAPSevice are stopped, rest all services are
> working excelp OLAP services, i even restarted the server. In service manager
> it shows 'Starting' on status bar. when i try to connect server through MSA
> it gives me error 'cannot open connection to Analysis server the server is
> either not started or is too busy', Can anyone help me, it's very urgent

MSSQLServerOLAPSevice

all of a sudden my MSSQLServerOLAPSevice are stopped, rest all services are
working excelp OLAP services, i even restarted the server. In service manage
r
it shows 'Starting' on status bar. when i try to connect server through MSA
it gives me error 'cannot open connection to Analysis server the server is
either not started or is too busy', Can anyone help me, it's very urgentThis sounds like it could be related to KB 883656. I have seen this at a cl
ient site, where AS would restart itself every 20-30 seconds, and you will s
ee the state cycle in Service Manager.
There is a hotfix for this bug, and it is also included in the new SP4. In
order to recover from the corrupted state to allow you to apply the service
pack, you'll need to do the following:
1) Using the SQL Server Service Manager, select the MSSQLServerOLAPSer
vice in the second (Services) drop-down list. Uncheck the “Auto-start ser
vice when OS starts” box.
2) Close the Service Manger. Reboot the server to get the restart pro
cess to stop looping.
3) Rename the data folder where Analysis Services stores its databases
. By default, this is c:\Program Files\Microsoft Analysis Services\Data but
it may be different on your system, particularly if there are alternate dri
ves. The folder in question will have subfolders along this structure:
… Data
MyASDatabase
MyCube1
MyCube2
MyCube3
and these lowest level folders will have the many data and aggregate files f
or each cube inside them.
4) Create a new folder in the same directory called Data
5) Restart Analysis Services through the SQL Server Service Manager by
selecting the MSSQLServerOLAPService in the second (Services) drop-down lis
t and clicking the Start icon. Also, check the “Auto-start service when O
S starts” box. Close the Service Manager.
This should get your instance back to normal, the cubes will rebuild from th
e stored metadata next time that you use them. You will need to reprocess.
"Pravin" <Pravin@.discussions.microsoft.com> wrote in message news:64D82324-1604-4627-8A9E-67
186A547AA2@.microsoft.com...
> all of a sudden my MSSQLServerOLAPSevice are stopped, rest all services ar
e
> working excelp OLAP services, i even restarted the server. In service mana
ger
> it shows 'Starting' on status bar. when i try to connect server through M
SA
> it gives me error 'cannot open connection to Analysis server the server is
> either not started or is too busy', Can anyone help me, it's very urgent

MSSQLSERVER eventId 17055

Hello ...

I have 3 servers running MSSQLSERVER.
Last night I found out that the MSSQLSERVER service restarted itself ( on all MSSQLSERVER servers ).

This is what the logs said :

eventId = 17055
8-1-03 , 2:45:12 AM
17310 :
SqlDumpExceptionHandler: Process 796 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

eventId = 17055
8-1-03 , 2:45:24 AM
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.

eventId = 17052
8-1-03 , 2:45:30 AM
The MSSQLSERVER service terminated unexpectedly.

All the servers had the same logs ( expect of the time and differect process ).

Does anybody have a clue what it could be ?RE:

I have 3 servers running MSSQLSERVER. Last night I found out that the MSSQLSERVER service restarted itself ( on all MSSQLSERVER servers ). All the servers had the same logs ( expect of the time and differect process ).

Q1 Does anybody have a clue what it could be ?

A1 No.

However, from the co-incidence described, a wild guess would be that some SQL in a reused code snippet or a common user stored procedure is causing the issue to manifest itself. {For example: such issues have been observed to exist in certain circumstances when SELECT statements apply the DISTINCT logical operator, and SELECT statements have been known to cause such AVs when:
1 A CHECK constraint exists on one of the columns in a queried table object, and
2 The column with the Check constraint is a specified part of the SELECT statement, and
3 The SELECT statement utilizes several LIKE predicates (in the WHERE clause of the SELECT statement).}

One possible strategy to consider would be to attempt to identify the offending SQL, and reproduce the error. Once certain of the SQL the issue occurs with, one would then re-write the sql statement(s) and / or proc such that the error does not occur.

Another would be to open a case with MS, and let PSS think about it (if it is indeed confirmed to be a bug, you may ask and have the support call fee refunded).

MSSQLServer dependent service startup

Hello,
I have some services that are dependent on MSSQLServer serivce but when the
computer is restarted, my services don't start and I get an error message
"Cannot open database requrent in login 'database name'. Login fails'.
It seems like to me that these services come up before SQL Server even
though I have the dependencies set right.
Any help is appreciated.
Thanks
Shipra,
From the error it looks like the sql server is up when your application
is trying to connect. Since it will not give login failure. if the SQL Server
is not up it will give a error "could not connect or something". Is your
application by default using any id to connect to the database. It seems that
the ID doesn't have access to the default database.
Neeraj
"Shipra Gupta" wrote:

> Hello,
> I have some services that are dependent on MSSQLServer serivce but when the
> computer is restarted, my services don't start and I get an error message
> "Cannot open database requrent in login 'database name'. Login fails'.
> It seems like to me that these services come up before SQL Server even
> though I have the dependencies set right.
> Any help is appreciated.
> Thanks
>
|||Yes, that's true. But the login ID being used has all the required
permissions, I think it is a timing issue because later when I start the
services, they all start without a problem.
Thanks
"Neeraj" wrote:
[vbcol=seagreen]
> Shipra,
> From the error it looks like the sql server is up when your application
> is trying to connect. Since it will not give login failure. if the SQL Server
> is not up it will give a error "could not connect or something". Is your
> application by default using any id to connect to the database. It seems that
> the ID doesn't have access to the default database.
> Neeraj
> "Shipra Gupta" wrote:
|||Its possible that database SQL Server is up but default database is going
through the recovery. Adding a bit of delay might help. In Sybase we can
chage the order in which the databases get recovered, i don't know if we can
do the same in sql server or not. If yes then you can set it such that the
database gets recovered before any other database.
Neeraj
"Shipra Gupta" wrote:
[vbcol=seagreen]
> Yes, that's true. But the login ID being used has all the required
> permissions, I think it is a timing issue because later when I start the
> services, they all start without a problem.
> Thanks
> "Neeraj" wrote:

MSSQLServer dependent service startup

Hello,
I have some services that are dependent on MSSQLServer serivce but when the
computer is restarted, my services don't start and I get an error message
"Cannot open database requrent in login 'database name'. Login fails'.
It seems like to me that these services come up before SQL Server even
though I have the dependencies set right.
Any help is appreciated.
ThanksShipra,
From the error it looks like the sql server is up when your application
is trying to connect. Since it will not give login failure. if the SQL Serve
r
is not up it will give a error "could not connect or something". Is your
application by default using any id to connect to the database. It seems tha
t
the ID doesn't have access to the default database.
Neeraj
"Shipra Gupta" wrote:

> Hello,
> I have some services that are dependent on MSSQLServer serivce but when th
e
> computer is restarted, my services don't start and I get an error message
> "Cannot open database requrent in login 'database name'. Login fails'.
> It seems like to me that these services come up before SQL Server even
> though I have the dependencies set right.
> Any help is appreciated.
> Thanks
>|||Yes, that's true. But the login ID being used has all the required
permissions, I think it is a timing issue because later when I start the
services, they all start without a problem.
Thanks
"Neeraj" wrote:
[vbcol=seagreen]
> Shipra,
> From the error it looks like the sql server is up when your applicati
on
> is trying to connect. Since it will not give login failure. if the SQL Ser
ver
> is not up it will give a error "could not connect or something". Is your
> application by default using any id to connect to the database. It seems t
hat
> the ID doesn't have access to the default database.
> Neeraj
> "Shipra Gupta" wrote:
>|||Its possible that database SQL Server is up but default database is going
through the recovery. Adding a bit of delay might help. In Sybase we can
chage the order in which the databases get recovered, i don't know if we can
do the same in sql server or not. If yes then you can set it such that the
database gets recovered before any other database.
Neeraj
"Shipra Gupta" wrote:
[vbcol=seagreen]
> Yes, that's true. But the login ID being used has all the required
> permissions, I think it is a timing issue because later when I start the
> services, they all start without a problem.
> Thanks
> "Neeraj" wrote:
>