A connection cannot be made to Analysis Services 2005

Please help!

I have been trying to deploy an Analysis Services 2005 cube to a server from a local PC. I have had no luck. This was working yesterday and I cannot work out what might be different. This is the error message I am getting:

The project could not be deployed to the 'qccatsvr1' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.

By the way this works on another PC that is set up the same way...the only thing I can see different is the Novell user account I used to log in to the PC.

This is what I have tried so far:

Checked that the Analysis Services service is running on the server - it is. Check the target server - this is ok. Re-install Analysis Services 2005 - no problems occurred during this Tried all different changes to the security log on in the Analysis Services service - nothing worked. Tried to open the AS solution file from the actual server and deploy - no luck.

So you can see that I am now getting quite frustrated. I know (hope) it is something simple that I have missed.

Does anyone have any ideas/solutions for me.

Thanks in advance!!!

Steve

SSAS uses windows authentication exclusively. It will not authenticate using a Novell account, but there should be a setting in your Novell client which controls how the user is logged on to the local machine. It is the local windows account that needs to have administrator priviledges in SSAS in order to be able to deploy a new database.

Were you using the same user account when you logged on to the server and tried to deploy the solution? If you use the same account that was used to install SSAS you should not have any issues.

If you want to deploy a solution from a remote machine on a Novell network you will need to setup a local account on the remote workstation which is set to log on to the local machine when the Novell user logs in and then you will need to set up an identical local account (with an identical password) on the server machine and assign the account on the server to the server administration role in SSAS.

|||

I have setup exactly the same account on the server as the windows username used to logon to the remote PC. The account also has exactyl the same password and has been given full access to SSAS. However this does not work either.

The things that has got me confused is that this user was able to deploy a few days before I posted this thread with no problems...that was without a username and password set up on the server with access to SSAS.

Do you have any aother ideas?

|||

I thought you mentioned in your original post that you were now using a different user account. Which is what made me think that it must be something to do with the Novell account/local account connection.

You could have a look at the following link, it contains information on troubleshooting SSAS connection issues: http://www.sqljunkies.com/WebLog/edwardm/archive/2006/05/26/21447.aspx

|||

Darren,

Thank-you for your advice. I got onto that document and tried a couple of things. The one that helped the most was the SQL Server Profiler. This showed me what was happening with particular accounts and I was able to change the account permission accordingly.

Everything is now ok.

Thanks again for your help with this one...

A connection cannot be made to Analysis Services 2005

Please help!

I have been trying to deploy an Analysis Services 2005 cube to a server from a local PC. I have had no luck. This was working yesterday and I cannot work out what might be different. This is the error message I am getting:

The project could not be deployed to the 'qccatsvr1' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.

By the way this works on another PC that is set up the same way...the only thing I can see different is the Novell user account I used to log in to the PC.

This is what I have tried so far:

Checked that the Analysis Services service is running on the server - it is.

Check the target server - this is ok.

Re-install Analysis Services 2005 - no problems occurred during this

Tried all different changes to the security log on in the Analysis Services service - nothing worked.

Tried to open the AS solution file from the actual server and deploy - no luck.

So you can see that I am now getting quite frustrated. I know (hope) it is something simple that I have missed.

Does anyone have any ideas/solutions for me.

Thanks in advance!!!

Steve

SSAS uses windows authentication exclusively. It will not authenticate using a Novell account, but there should be a setting in your Novell client which controls how the user is logged on to the local machine. It is the local windows account that needs to have administrator priviledges in SSAS in order to be able to deploy a new database.

Were you using the same user account when you logged on to the server and tried to deploy the solution? If you use the same account that was used to install SSAS you should not have any issues.

If you want to deploy a solution from a remote machine on a Novell network you will need to setup a local account on the remote workstation which is set to log on to the local machine when the Novell user logs in and then you will need to set up an identical local account (with an identical password) on the server machine and assign the account on the server to the server administration role in SSAS.

|||

I have setup exactly the same account on the server as the windows username used to logon to the remote PC. The account also has exactyl the same password and has been given full access to SSAS. However this does not work either.

The things that has got me confused is that this user was able to deploy a few days before I posted this thread with no problems...that was without a username and password set up on the server with access to SSAS.

Do you have any aother ideas?

|||

I thought you mentioned in your original post that you were now using a different user account. Which is what made me think that it must be something to do with the Novell account/local account connection.

You could have a look at the following link, it contains information on troubleshooting SSAS connection issues: http://www.sqljunkies.com/WebLog/edwardm/archive/2006/05/26/21447.aspx

|||

Darren,

Thank-you for your advice. I got onto that document and tried a couple of things. The one that helped the most was the SQL Server Profiler. This showed me what was happening with particular accounts and I was able to change the account permission accordingly.

Everything is now ok.

Thanks again for your help with this one...

8GB RAM in SQL Server

Hi,
I'm just designing a server... What can I do with 8GB RAM in the Box?
Analysis Services is limited to 8GB. The Enterprise Edition of SQL Server
can use max.8GB RAM. Windows 2003 Enterprise Edition can use 8GB, too.
So I can use 3GB for Analysis Services and the remaining 5GB are used for
SQL Server and the OS? Is this right?
Thanks
ThomasActually, there is no direct answer for this. It depends
on how much memory the analysis server requires for cubes
and memory required for SQL Server.
It also depends on any other applications running on the
same box.
In General, You have to allocate for OS,SQLServer,analysis
Server and then for other applications.
Please read this to get some idea on how SQL Server memory
works. http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/adminsql/ad_config_9zfy.asp
Also , read "memory architecture" from BOL.
To allocate memory for Analysis Server, stop and start the
analysis services and open the task manager and look for
memory used by the processess "msmdsrv.exe"
and "msmdvldm.exe". The sum of these memory is minimum
required for analysis services to start.
SQLVarad (MCDBA-1999,MCSE-1999)
>--Original Message--
>Hi,
>I'm just designing a server... What can I do with 8GB RAM
in the Box?
>Analysis Services is limited to 8GB. The Enterprise
Edition of SQL Server
>can use max.8GB RAM. Windows 2003 Enterprise Edition can
use 8GB, too.
>So I can use 3GB for Analysis Services and the remaining
5GB are used for
>SQL Server and the OS? Is this right?
>
>Thanks
>
>Thomas
>
>.
>|||Hi,
thanks, that pointed me in the right direction...
Thomas
"SQLVarad" <SQLVarad@.hotmail.com> schrieb im Newsbeitrag
news:010c01c3a3d4$6cc8f790$a601280a@.phx.gbl...
> Actually, there is no direct answer for this. It depends
> on how much memory the analysis server requires for cubes
> and memory required for SQL Server.
> It also depends on any other applications running on the
> same box.
> In General, You have to allocate for OS,SQLServer,analysis
> Server and then for other applications.
> Please read this to get some idea on how SQL Server memory
> works. http://msdn.microsoft.com/library/default.asp?
> url=/library/en-us/adminsql/ad_config_9zfy.asp
> Also , read "memory architecture" from BOL.
> To allocate memory for Analysis Server, stop and start the
> analysis services and open the task manager and look for
> memory used by the processess "msmdsrv.exe"
> and "msmdvldm.exe". The sum of these memory is minimum
> required for analysis services to start.
> SQLVarad (MCDBA-1999,MCSE-1999)
>
> >--Original Message--
> >Hi,
> >
> >I'm just designing a server... What can I do with 8GB RAM
> in the Box?
> >Analysis Services is limited to 8GB. The Enterprise
> Edition of SQL Server
> >can use max.8GB RAM. Windows 2003 Enterprise Edition can
> use 8GB, too.
> >So I can use 3GB for Analysis Services and the remaining
> 5GB are used for
> >SQL Server and the OS? Is this right?
> >
> >
> >Thanks
> >
> >
> >Thomas
> >
> >
> >.
> >

4 Gb RAM in SQL 2000 Standard

I want to run both analysis services and standard relational Db services on
one server with 4 Gb of RAM. I have read that if you want to use more than 2
Gb RAM you should choose the Enterprise version of SQL 2000. I want to know
if that 2 Gb limit is for both analysis and relational combined or whether
the limit is 2 Gb per service.
Can anyone tell me with absolute certainty?Hi
2Gb is per instance of SQL Server. If you have 4Gb, at most you can use is
3GB (with the /3gb switch in boot.ini)
So in effect, AS and SQL Engine can use 3Gb between them, but one can not
use more than 2Gb.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"cathedr@.wa.state.gov" <cathedrwastategov@.discussions.microsoft.com> wrote
in message news:2F2C975C-3322-41BF-8EB3-C5552A47DB39@.microsoft.com...
> I want to run both analysis services and standard relational Db services
on
> one server with 4 Gb of RAM. I have read that if you want to use more
than 2
> Gb RAM you should choose the Enterprise version of SQL 2000. I want to
know
> if that 2 Gb limit is for both analysis and relational combined or whether
> the limit is 2 Gb per service.
> Can anyone tell me with absolute certainty?|||With Standard Edition all you can ever use is 2GB per instance, even with
the /3GB. If it were EE then that would be true. But if you only have 4GB
you never want both instances of SQL Server to use all 2GB each. Then you
leave nothing for the OS or any other apps that yo may run and you will
certainly get page swapping at the OS level. SQL Server will dynamically
allocate memory to minimize this but if you fully utilize all the physical
memory for SQL Server you will get swapping at hte OS level.
--
Andrew J. Kelly SQL MVP
"cathedr@.wa.state.gov" <cathedrwastategov@.discussions.microsoft.com> wrote
in message news:2F2C975C-3322-41BF-8EB3-C5552A47DB39@.microsoft.com...
>I want to run both analysis services and standard relational Db services on
> one server with 4 Gb of RAM. I have read that if you want to use more
> than 2
> Gb RAM you should choose the Enterprise version of SQL 2000. I want to
> know
> if that 2 Gb limit is for both analysis and relational combined or whether
> the limit is 2 Gb per service.
> Can anyone tell me with absolute certainty?

4 Gb RAM in SQL 2000 Standard

I want to run both analysis services and standard relational Db services on
one server with 4 Gb of RAM. I have read that if you want to use more than 2
Gb RAM you should choose the Enterprise version of SQL 2000. I want to know
if that 2 Gb limit is for both analysis and relational combined or whether
the limit is 2 Gb per service.
Can anyone tell me with absolute certainty?
Hi
2Gb is per instance of SQL Server. If you have 4Gb, at most you can use is
3GB (with the /3gb switch in boot.ini)
So in effect, AS and SQL Engine can use 3Gb between them, but one can not
use more than 2Gb.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"cathedr@.wa.state.gov" <cathedrwastategov@.discussions.microsoft.com> wrote
in message news:2F2C975C-3322-41BF-8EB3-C5552A47DB39@.microsoft.com...
> I want to run both analysis services and standard relational Db services
on
> one server with 4 Gb of RAM. I have read that if you want to use more
than 2
> Gb RAM you should choose the Enterprise version of SQL 2000. I want to
know
> if that 2 Gb limit is for both analysis and relational combined or whether
> the limit is 2 Gb per service.
> Can anyone tell me with absolute certainty?
|||With Standard Edition all you can ever use is 2GB per instance, even with
the /3GB. If it were EE then that would be true. But if you only have 4GB
you never want both instances of SQL Server to use all 2GB each. Then you
leave nothing for the OS or any other apps that yo may run and you will
certainly get page swapping at the OS level. SQL Server will dynamically
allocate memory to minimize this but if you fully utilize all the physical
memory for SQL Server you will get swapping at hte OS level.
Andrew J. Kelly SQL MVP
"cathedr@.wa.state.gov" <cathedrwastategov@.discussions.microsoft.com> wrote
in message news:2F2C975C-3322-41BF-8EB3-C5552A47DB39@.microsoft.com...
>I want to run both analysis services and standard relational Db services on
> one server with 4 Gb of RAM. I have read that if you want to use more
> than 2
> Gb RAM you should choose the Enterprise version of SQL 2000. I want to
> know
> if that 2 Gb limit is for both analysis and relational combined or whether
> the limit is 2 Gb per service.
> Can anyone tell me with absolute certainty?

4 Gb RAM in SQL 2000 Standard

I want to run both analysis services and standard relational Db services on
one server with 4 Gb of RAM. I have read that if you want to use more than
2
Gb RAM you should choose the Enterprise version of SQL 2000. I want to know
if that 2 Gb limit is for both analysis and relational combined or whether
the limit is 2 Gb per service.
Can anyone tell me with absolute certainty?Hi
2Gb is per instance of SQL Server. If you have 4Gb, at most you can use is
3GB (with the /3gb switch in boot.ini)
So in effect, AS and SQL Engine can use 3Gb between them, but one can not
use more than 2Gb.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"cathedr@.wa.state.gov" <cathedrwastategov@.discussions.microsoft.com> wrote
in message news:2F2C975C-3322-41BF-8EB3-C5552A47DB39@.microsoft.com...
> I want to run both analysis services and standard relational Db services
on
> one server with 4 Gb of RAM. I have read that if you want to use more
than 2
> Gb RAM you should choose the Enterprise version of SQL 2000. I want to
know
> if that 2 Gb limit is for both analysis and relational combined or whether
> the limit is 2 Gb per service.
> Can anyone tell me with absolute certainty?|||With Standard Edition all you can ever use is 2GB per instance, even with
the /3GB. If it were EE then that would be true. But if you only have 4GB
you never want both instances of SQL Server to use all 2GB each. Then you
leave nothing for the OS or any other apps that yo may run and you will
certainly get page swapping at the OS level. SQL Server will dynamically
allocate memory to minimize this but if you fully utilize all the physical
memory for SQL Server you will get swapping at hte OS level.
Andrew J. Kelly SQL MVP
"cathedr@.wa.state.gov" <cathedrwastategov@.discussions.microsoft.com> wrote
in message news:2F2C975C-3322-41BF-8EB3-C5552A47DB39@.microsoft.com...
>I want to run both analysis services and standard relational Db services on
> one server with 4 Gb of RAM. I have read that if you want to use more
> than 2
> Gb RAM you should choose the Enterprise version of SQL 2000. I want to
> know
> if that 2 Gb limit is for both analysis and relational combined or whether
> the limit is 2 Gb per service.
> Can anyone tell me with absolute certainty?

3455: Analysis of database is 100% complete

We're running SQL std. ed., v. 8.00.2039, SP4 using 'no-sync' replication (8
sites). In the Application log of the Event Viewer I get the following
message in groups of 3 every 15 minutes, "3455: Analysis of database
XXPROLAW' (7) is 100% complete (approximately 0 seconds)." I can't identify
what is triggering this analysis and it may be interferring with other
scheduled jobs causing them to fail. Couldn't find anything on Google or MS
N
K-base.
--
Steven PattonTry removing Auto Close from the database.
Found on another newsgroup and it works (but I don't know why).

3455: Analysis of database is 100% complete

We're running SQL std. ed., v. 8.00.2039, SP4 using 'no-sync' replication (8
sites). In the Application log of the Event Viewer I get the following
message in groups of 3 every 15 minutes, "3455: Analysis of database
XXPROLAW' (7) is 100% complete (approximately 0 seconds)." I can't identify
what is triggering this analysis and it may be interferring with other
scheduled jobs causing them to fail. Couldn't find anything on Google or MSN
K-base.
--
Steven PattonTry removing Auto Close from the database.
Found on another newsgroup and it works (but I don't know why).