Analisys Services OLAP Error

running sql server 2000 w/ analisys serv sp4 on w2k3 sp1. Yes, also we are running sql 2000 sp4.

I keep getting an event id 6034.

The mssqlserverolapservice service terminated unexpectedly. It has done this 134 times.

Now, i went ahead and installed the suggested rollup hotfix already, which is a post AS SP4 rollup hotfix that fixes this.

It didn't.

What next?

Mike,

This is just one of the possible options:

I have seen this happening with corrupted database. To fix this, you have to find corrupted database and remove it from data folder. I was doing this:

1. Stop Analysis Services service.

2. Go to analysis services data folder and copy folder for one database to another outside folder. Also copy related file from root data folder (I think something like DBName.odb, forgot extension)?

3. Try to start analysis services, if same problem, choose another database and do step 2.

If you'll find corrupted databases, copy all other ones back. Restore corrupted database from backup.

Vidas Matelis

sql

An existing connection was forcibly closed by the remote host

It is very appreciated if someone can help me on this problem:

I have 2 machines, connected with workgroup (not domain machine), 1 is win2003 sp1, 1 is xp.

How can I connect SSAS from XP machine with windows authentication?

Looks the Native client fix the windows authentication with local user name.

When I connect from XP, my application with following codes:

string connstr = "Provider=MSOLAP.3;Data Source=amsserver;Password=accenture;User ID=administrator;Initial Catalog=MIP2ASProject";

AdomdConnection objConnection = new AdomdConnection();

// Assign the connection string and try to

//open a connection.

objConnection.ConnectionString = connstr;

objConnection.Open();

It give me this error:

An existing connection was forcibly closed by the remote host

First of all, you dont need the User ID and Password in the connection string if you are connecting using TCP/IP (you would use them only when connecting with HTTP using Basic auth).

Second, in order to use "Provider=MSOLAP.3" you will need to install "Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider" provider from http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

Yes, I have installed oledb AS9 provider.

If you think SSAS only support windows authentication which must use inside the domain, I really couldn't understand why oledbconnection works fine with same connection string?

I am not sure about whether impersonation belong to windows authentication, but, my testing prove that oledb can connect in this way, adomd can't.

BTW, thankful if anyone can let me know how to enable SSAS's anonymous connection?

Jerry

|||

it is an antivirus problem

uninstall antivirus and try again

what antivirus do you have?

|||

What version of ADOM.NET are you using?

Try downloading and installing "Microsoft ADOMD.NET " from http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

An error occurred during decryption

I have a 2 node cluster that I recently installed. During the installation,
node 2 was active. After the installation of SQL 2005 and the SP1, I added
some linked servers that use SQL authentication. When I fail over to node 1,
I get the following error:
An error occurred during decryption.
On all of my linked servers. If I fail back, everything works great. I have
these same linked servers on several other non-clustered machines and they
work fine. Is this possible a service master key issue?Could be. Can you post the error from the errorlog, including a few lines
before and after it, for context? You can remove sensitive information like
IP addresses or account names - I just need to see the error number, state,
and message.
Thanks
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dave B" <DaveB@.discussions.microsoft.com> wrote in message
news:535415A4-4727-4652-82DC-401A3FD74D00@.microsoft.com...
>I have a 2 node cluster that I recently installed. During the installation,
> node 2 was active. After the installation of SQL 2005 and the SP1, I added
> some linked servers that use SQL authentication. When I fail over to node
> 1,
> I get the following error:
> An error occurred during decryption.
> On all of my linked servers. If I fail back, everything works great. I
> have
> these same linked servers on several other non-clustered machines and they
> work fine. Is this possible a service master key issue?
>|||this is a few lines of the log file.
10/20/2006 01:17:05,spid9s,Unknown,Starting up database 'tempdb'.
10/20/2006 01:17:05,spid9s,Unknown,Clearing tempdb database.
10/20/2006 01:17:05,spid9s,Unknown,Starting up database 'model'.
10/20/2006 01:17:05,spid5s,Unknown,The NETBIOS name of the local node that
is running the server is 'SRVLWDSQL1'. This is an informational message only
.
No user action is required.
10/20/2006 01:17:05,spid5s,Unknown,Server name is 'SQLSERVER'. This is an
informational message only. No user action is required.
10/20/2006 01:17:05,spid5s,Unknown,An error occurred during decryption.
10/20/2006 01:17:05,spid5s,Unknown,Error: 15466<c/> Severity: 16<c/> State:
1.
10/20/2006 01:17:05,spid5s,Unknown,Starting up database 'mssqlsystemresource
'.
10/20/2006 01:17:05,spid5s,Unknown,SQL Trace ID 1 was started by login "sa".
"Laurentiu Cristofor [MSFT]" wrote:

> Could be. Can you post the error from the errorlog, including a few lines
> before and after it, for context? You can remove sensitive information lik
e
> IP addresses or account names - I just need to see the error number, state
,
> and message.
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Dave B" <DaveB@.discussions.microsoft.com> wrote in message
> news:535415A4-4727-4652-82DC-401A3FD74D00@.microsoft.com...
>
>|||I read your blog on the Service Master Key (SMK). One other question I have
is what is encrypted by the SMK? If I regenerate the key and/or force the
regeneration of the key, what data am I at risk of losing? I would assume SQ
L
login passwords and other database master keys. Anything else? I am just
wondering what I may need to recreate if I need to regenerate the key.
"Laurentiu Cristofor [MSFT]" wrote:

> Could be. Can you post the error from the errorlog, including a few lines
> before and after it, for context? You can remove sensitive information lik
e
> IP addresses or account names - I just need to see the error number, state
,
> and message.
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Dave B" <DaveB@.discussions.microsoft.com> wrote in message
> news:535415A4-4727-4652-82DC-401A3FD74D00@.microsoft.com...
>
>|||It does look like an error with the service master key decryption. Have you
copied your master database from another instance or performed any changes
to your installation before starting to see this?
I wrote a post on this exact topic on my blog. See
http://blogs.msdn.com/lcris/archive...10/572678.aspx.
Also, I am not clear of what you mean by linked servers and how do they
relate to your clustered installation and encryption. Can you elaborate on
your setup?
Thanks
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dave B" <DaveB@.discussions.microsoft.com> wrote in message
news:123435F7-6631-4C05-B5CD-CA50884DCB64@.microsoft.com...[vbcol=seagreen]
>I read your blog on the Service Master Key (SMK). One other question I have
> is what is encrypted by the SMK? If I regenerate the key and/or force the
> regeneration of the key, what data am I at risk of losing? I would assume
> SQL
> login passwords and other database master keys. Anything else? I am just
> wondering what I may need to recreate if I need to regenerate the key.
> "Laurentiu Cristofor [MSFT]" wrote:
>|||The issue that I am seeing on my cluster is any linked servers using sql
authentication created on NodeA fail when I move over to NodeB. They work
fine when I fail back to NodeA. The error I get is:
An error occurred during decryption
That is really the only link between the cluster and linked server. This
error occured both during an upgrade of the server and a new server
installation. Before I regenerate the key, I just want to know how
destructive the regenerate could be. Anything that I may need to recreate, I
want to have scripted before my maintenance window starts.
"Laurentiu Cristofor [MSFT]" wrote:

> It does look like an error with the service master key decryption. Have yo
u
> copied your master database from another instance or performed any changes
> to your installation before starting to see this?
> I wrote a post on this exact topic on my blog. See
> http://blogs.msdn.com/lcris/archive...10/572678.aspx.
> Also, I am not clear of what you mean by linked servers and how do they
> relate to your clustered installation and encryption. Can you elaborate on
> your setup?
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Dave B" <DaveB@.discussions.microsoft.com> wrote in message
> news:123435F7-6631-4C05-B5CD-CA50884DCB64@.microsoft.com...
>
>|||Are your nodes running under the same service account? They should be, but
I'd like to double check.
To confirm that the error happens with the service master key (SMK), run
ALTER SERVICE MASTER KEY REGENERATE. This is safe - it will fail if it
detects any problem, so you can use it as a quick SMK integrity check.
The service master key encrypts credentials (CREATE CREDENTIAL), linked
server login passwords, and database master keys (DbMK). You can loose the
first two if you FORCE regenerate the SMK, but you should still be able to
recover your DbMKs using their password encryption. This was explained in
the post I referred you to.
However, if things work on NodeA but not on NodeB, the problem is not with
the SMK. It looks like something is wrong with your cluster configuration
and the key cannot be recovered after failover. If what I told you so far
doesn't help, I suggest that you open a feedback report at
http://connect.microsoft.com/site/s...aspx?SiteID=68 and provide us
with more details about your configuration. Also request that the report be
assigned to me.
Thanks
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dave B" <DaveB@.discussions.microsoft.com> wrote in message
news:CE0975B0-FD47-4193-B485-7EED618C20E7@.microsoft.com...[vbcol=seagreen]
> The issue that I am seeing on my cluster is any linked servers using sql
> authentication created on NodeA fail when I move over to NodeB. They work
> fine when I fail back to NodeA. The error I get is:
> An error occurred during decryption
> That is really the only link between the cluster and linked server. This
> error occured both during an upgrade of the server and a new server
> installation. Before I regenerate the key, I just want to know how
> destructive the regenerate could be. Anything that I may need to recreate,
> I
> want to have scripted before my maintenance window starts.
>
> "Laurentiu Cristofor [MSFT]" wrote:
>|||The ALTER SERVICE MASTER KEY REGENERATE command worked. No errors, no
warnings no issues with linked servers. However, I started experiencing othe
r
issues after the failover. After a few hours of looking, it appeared the
second node did not receive the SP1 update. I know this is a different topic
so I will start a new discussion if I can’t find any resolution.
Thanks for you help.
"Laurentiu Cristofor [MSFT]" wrote:

> Are your nodes running under the same service account? They should be, but
> I'd like to double check.
> To confirm that the error happens with the service master key (SMK), run
> ALTER SERVICE MASTER KEY REGENERATE. This is safe - it will fail if it
> detects any problem, so you can use it as a quick SMK integrity check.
> The service master key encrypts credentials (CREATE CREDENTIAL), linked
> server login passwords, and database master keys (DbMK). You can loose the
> first two if you FORCE regenerate the SMK, but you should still be able to
> recover your DbMKs using their password encryption. This was explained in
> the post I referred you to.
> However, if things work on NodeA but not on NodeB, the problem is not with
> the SMK. It looks like something is wrong with your cluster configuration
> and the key cannot be recovered after failover. If what I told you so far
> doesn't help, I suggest that you open a feedback report at
> http://connect.microsoft.com/site/s...aspx?SiteID=68 and provide us
> with more details about your configuration. Also request that the report b
e
> assigned to me.
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Dave B" <DaveB@.discussions.microsoft.com> wrote in message
> news:CE0975B0-FD47-4193-B485-7EED618C20E7@.microsoft.com...
>
>