Problem with Analysis Server

I just installed 2005 and have an Enterprise Editition instance on my local machine. My SSAS service appears to be working properly in Services. However, whenever I try to deploy a cube (simple one from tutorial) or try to connect from Management Console, I get rejected. The error message is:

No connection could be made because the target machine actively refused it (System).

I've tried about everything I can think of and can't get past this. Any guidance would be greatly appreciated.

Rod, can you enable shared memory and try again? This should solve the problem.

Thanks,
Sam Lester (MSFT)

|||How do you "enable" shared memory?sql

Problem with Analysis Server

I just installed 2005 and have an Enterprise Editition instance on my local machine. My SSAS service appears to be working properly in Services. However, whenever I try to deploy a cube (simple one from tutorial) or try to connect from Management Console, I get rejected. The error message is:

No connection could be made because the target machine actively refused it (System).

I've tried about everything I can think of and can't get past this. Any guidance would be greatly appreciated.

Rod, can you enable shared memory and try again? This should solve the problem.

Thanks,
Sam Lester (MSFT)

|||How do you "enable" shared memory?

Problem with Analysis Server

I just installed 2005 and have an Enterprise Editition instance on my local machine. My SSAS service appears to be working properly in Services. However, whenever I try to deploy a cube (simple one from tutorial) or try to connect from Management Console, I get rejected. The error message is:

No connection could be made because the target machine actively refused it (System).

I've tried about everything I can think of and can't get past this. Any guidance would be greatly appreciated.

Rod, can you enable shared memory and try again? This should solve the problem.

Thanks,
Sam Lester (MSFT)

|||How do you "enable" shared memory?

Problem when rebuild system databases for a clustered instance of

Has anyone rebuilt system databases for a SQL2005 clustered instance?
I have followed the code from "To rebuild system databases for a clustered."
section at http://msdn2.microsoft.com/en-us/library/ms144259.aspx, and keep
getting message saying to add more parameters. I added the parameter
whenever it required, "Group", then "addnode", even INSTALLSQLDATADIR = "S:\"
which data should go.
The summary.txt says "Setup succeeded with the installation". But in the
files\setup_*_core.log for both node2, I have this error:
Error: Action "LaunchLocalBootstrapAction" threw an exception during
execution. Error information reported during run:
"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe"
finished and returned: 0
Aborting queue processing as nested installer has completed
Message pump returning: 0
I want to know whether anyone has similar problem or succeed when rebuild
system DBs for a cluster.
What are all the parameters needed for rebuilding sys databases on a
cluster? Is there anything should be aware of?
Hi Julia
Did you manage to resolve this problem? I am experiencing exactly the
same thing .
Cheers
Jesse
*** Sent via Developersdex http://www.codecomments.com ***
|||No. I have contacted Microsoft but no answer. I would recommend you report
this problem as well to them and get them to look into it.
"Jesse Easton" wrote:

>
> Hi Julia
> Did you manage to resolve this problem? I am experiencing exactly the
> same thing .
> Cheers
> Jesse
> *** Sent via Developersdex http://www.codecomments.com ***
>

Problem when connecting to a named sql 2000 instance

Hi,
I have a problem when connecting to a named sql 2000 instance . The instance
is running in a 2 node cluster configuration. The second instance on the
other node works fine.
When I try to connect with a client on another pc, the connection only works
when I set the correct (static) port number.
But if I leave it to dynamically determine ports it is not able to connect.
There is no firewall between the client pc and the database server
and udp port 1434 is listening.
Stranger is that this problem also occurs on the server itself. When i
connect to the servernode where the instance of sql is running,
i have to set an alias with the portnumber to be able to connect to the
instance. Without this the connection fails.
Anybody any idea(s)?
Regards,
CihatUnfortunately no response. Here my response so that others with same problem
maybe solve it more quickly. When this happens and all checks appear okey,
you have to failover the group and reboot the server where this problem
occur. After the reboot it worked fine for me. Still dont know the cause, bu
t
it works now.
"Cihat" wrote:

> Hi,
> I have a problem when connecting to a named sql 2000 instance . The instan
ce
> is running in a 2 node cluster configuration. The second instance on the
> other node works fine.
> When I try to connect with a client on another pc, the connection only wor
ks
> when I set the correct (static) port number.
> But if I leave it to dynamically determine ports it is not able to connect
.
> There is no firewall between the client pc and the database server
> and udp port 1434 is listening.
> Stranger is that this problem also occurs on the server itself. When i
> connect to the servernode where the instance of sql is running,
> i have to set an alias with the portnumber to be able to connect to the
> instance. Without this the connection fails.
> Anybody any idea(s)?
> Regards,
> Cihat
>

Problem when connect to SQL Server 2005 (SQL Native Client + Named instance)

Hi,
I have an application which previous connect to SQL Server 2000.
Now, I installed SQL Server 2005, and try to conncet to it.
The previous connection string is:
sString.Format("DSN=%s;uid=%s;pwd=%s", sDb, sUser, sPassword);
In order to support SQL Native Client driver in SQL Server 2005, I
changed the connection string to:
sString.Format("Provider=SQLNCLI;
DataTypeCompatibility=80;DSN=%s;uid=%s;pwd=%s", sDb, sUser,
sPassword);
I have a default instance and a named instance in my database. So i
created two DSN:
(1) Use SQL Native Client as the driver and connect to the default
instance.
The application could work well under this configuration.
(2) Use SQL Native Client as the driver and connect to the named
instance.
The application could not work successfully under this
configuration.
It could not connect to the database.
I have started the SQL Server Browser service.
Why I could not connect to the database when i use SQL Native Client +
Named instance
Who can help me?
Thanks in advance.
Did you enable the Allow Remote Connections option? Have you run the
Surface Area Configurator and the SQL Server Configuration Manager?
Andrew J. Kelly SQL MVP
<yangrudy@.126.com> wrote in message
news:1140155887.725187.43270@.g44g2000cwa.googlegro ups.com...
> Hi,
> I have an application which previous connect to SQL Server 2000.
> Now, I installed SQL Server 2005, and try to conncet to it.
> The previous connection string is:
> sString.Format("DSN=%s;uid=%s;pwd=%s", sDb, sUser, sPassword);
> In order to support SQL Native Client driver in SQL Server 2005, I
> changed the connection string to:
> sString.Format("Provider=SQLNCLI;
> DataTypeCompatibility=80;DSN=%s;uid=%s;pwd=%s", sDb, sUser,
> sPassword);
> I have a default instance and a named instance in my database. So i
> created two DSN:
> (1) Use SQL Native Client as the driver and connect to the default
> instance.
> The application could work well under this configuration.
> (2) Use SQL Native Client as the driver and connect to the named
> instance.
> The application could not work successfully under this
> configuration.
> It could not connect to the database.
> I have started the SQL Server Browser service.
> Why I could not connect to the database when i use SQL Native Client +
> Named instance
> Who can help me?
> Thanks in advance.
>

Problem when connect to SQL Server 2005 (SQL Native Client + Named instance)

Hi,
I have an application which previous connect to SQL Server 2000.
Now, I installed SQL Server 2005, and try to conncet to it.
The previous connection string is:
sString.Format("DSN=%s;uid=%s;pwd=%s", sDb, sUser, sPassword);
In order to support SQL Native Client driver in SQL Server 2005, I
changed the connection string to:
sString.Format("Provider=SQLNCLI;
DataTypeCompatibility=80;DSN=%s;uid=%s;p
wd=%s", sDb, sUser,
sPassword);
I have a default instance and a named instance in my database. So i
created two DSN:
(1) Use SQL Native Client as the driver and connect to the default
instance.
The application could work well under this configuration.
(2) Use SQL Native Client as the driver and connect to the named
instance.
The application could not work successfully under this
configuration.
It could not connect to the database.
I have started the SQL Server Browser service.
Why I could not connect to the database when i use SQL Native Client +
Named instance
Who can help me?
Thanks in advance.Did you enable the Allow Remote Connections option? Have you run the
Surface Area Configurator and the SQL Server Configuration Manager?
Andrew J. Kelly SQL MVP
<yangrudy@.126.com> wrote in message
news:1140155887.725187.43270@.g44g2000cwa.googlegroups.com...
> Hi,
> I have an application which previous connect to SQL Server 2000.
> Now, I installed SQL Server 2005, and try to conncet to it.
> The previous connection string is:
> sString.Format("DSN=%s;uid=%s;pwd=%s", sDb, sUser, sPassword);
> In order to support SQL Native Client driver in SQL Server 2005, I
> changed the connection string to:
> sString.Format("Provider=SQLNCLI;
> DataTypeCompatibility=80;DSN=%s;uid=%s;p
wd=%s", sDb, sUser,
> sPassword);
> I have a default instance and a named instance in my database. So i
> created two DSN:
> (1) Use SQL Native Client as the driver and connect to the default
> instance.
> The application could work well under this configuration.
> (2) Use SQL Native Client as the driver and connect to the named
> instance.
> The application could not work successfully under this
> configuration.
> It could not connect to the database.
> I have started the SQL Server Browser service.
> Why I could not connect to the database when i use SQL Native Client +
> Named instance
> Who can help me?
> Thanks in advance.
>

problem using OSQL -E

Hi..
I try to connect sql server. I have installed a sql server
1. SELFPACEDSQL
2. an instance with name MyNamedInstance
I am trying to follow the sertification book page number: 95 Chapter 3.
figur 3,11
I got this message when I try to execute following commands:
C:\Documents and Settings\Administrator>OSQL -E
1> SELECT @.@.SELFPACEDSQL
2> SELECT @.@.VERSION
3> GO
Msg 137, Level 15, State 2, Server SELFPACEDSQL, Line 2
Must declare the variable '@.@.SELFPACEDSQL'.
1>
And when I write this I got this:
C:\Documents and Settings\Administrator>OSQL -L
Servers:
(local)
SELFPACEDSQL\MYNAMEDINSTANCE
C:\Documents and Settings\Administrator>
Do I do something wrong.
My computer name is: SelfPacedSQL.SelfPacedCPU
Domain: SelfPacedCPU
Try with that:
OSQL -E -SSELFPACEDSQL\MYNAMEDINSTANCE
May the forces be with you.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"dreamlearn_ms" <dreamlearn@.yahoo.no> schrieb im Newsbeitrag
news:%23j3SDZiZFHA.3320@.TK2MSFTNGP12.phx.gbl...
> Hi..
> I try to connect sql server. I have installed a sql server
> 1. SELFPACEDSQL
> 2. an instance with name MyNamedInstance
> I am trying to follow the sertification book page number: 95 Chapter 3.
> figur 3,11
> I got this message when I try to execute following commands:
>
> C:\Documents and Settings\Administrator>OSQL -E
> 1> SELECT @.@.SELFPACEDSQL
> 2> SELECT @.@.VERSION
> 3> GO
> Msg 137, Level 15, State 2, Server SELFPACEDSQL, Line 2
> Must declare the variable '@.@.SELFPACEDSQL'.
> 1>
> And when I write this I got this:
> C:\Documents and Settings\Administrator>OSQL -L
> Servers:
> (local)
> SELFPACEDSQL\MYNAMEDINSTANCE
> C:\Documents and Settings\Administrator>
> Do I do something wrong.
> My computer name is: SelfPacedSQL.SelfPacedCPU
> Domain: SelfPacedCPU
>

problem using OSQL -E

Hi..
I try to connect sql server. I have installed a sql server
1. SELFPACEDSQL
2. an instance with name MyNamedInstance
I am trying to follow the sertification book page number: 95 Chapter 3.
figur 3,11
I got this message when I try to execute following commands:
C:\Documents and Settings\Administrator>OSQL -E
1> SELECT @.@.SELFPACEDSQL
2> SELECT @.@.VERSION
3> GO
Msg 137, Level 15, State 2, Server SELFPACEDSQL, Line 2
Must declare the variable '@.@.SELFPACEDSQL'.
1>
And when I write this I got this:
C:\Documents and Settings\Administrator>OSQL -L
Servers:
(local)
SELFPACEDSQL\MYNAMEDINSTANCE
C:\Documents and Settings\Administrator>
Do I do something wrong.
My computer name is: SelfPacedSQL.SelfPacedCPU
Domain: SelfPacedCPUTry with that:
OSQL -E -SSELFPACEDSQL\MYNAMEDINSTANCE
May the forces be with you.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"dreamlearn_ms" <dreamlearn@.yahoo.no> schrieb im Newsbeitrag
news:%23j3SDZiZFHA.3320@.TK2MSFTNGP12.phx.gbl...
> Hi..
> I try to connect sql server. I have installed a sql server
> 1. SELFPACEDSQL
> 2. an instance with name MyNamedInstance
> I am trying to follow the sertification book page number: 95 Chapter 3.
> figur 3,11
> I got this message when I try to execute following commands:
>
> C:\Documents and Settings\Administrator>OSQL -E
> 1> SELECT @.@.SELFPACEDSQL
> 2> SELECT @.@.VERSION
> 3> GO
> Msg 137, Level 15, State 2, Server SELFPACEDSQL, Line 2
> Must declare the variable '@.@.SELFPACEDSQL'.
> 1>
> And when I write this I got this:
> C:\Documents and Settings\Administrator>OSQL -L
> Servers:
> (local)
> SELFPACEDSQL\MYNAMEDINSTANCE
> C:\Documents and Settings\Administrator>
> Do I do something wrong.
> My computer name is: SelfPacedSQL.SelfPacedCPU
> Domain: SelfPacedCPU
>

Problem using Client Tools to Remotely Connect to a SQL Server Instance on Anoth

Someone please help me before I loose all of my hair :mad: !!!

I have two machines, a Windows Server 2003 machine running an SQL Server Standard Edition database instance and client tools (Enterprize Manager etc.), and a workstation PC running Windows XP SP2 which has just the SQL Server client tools (not an actual DB instance).

I'm trying to use the Enterprize Manager client tool on my WinXP machine to remotely connect to the server instance on the server PC (via 'New SQL Server Registration' option). Everytime I do this I get the following error message:

Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server Connection.

Now I've tried using different usernames and passwords. I have login details for my SQL Server set to use Windows Login rather then SQL Server login, so I tried remotely connecting with the username and password for the server PC, tried 'sa' with server password, even tried setting up a new user on the server and logging in from the client with that, no luck. I've opened up correct ports 1433 on both PCs, even disabled the windows firewalls algother. Both server and client have SP3a installed, WinServer2003 has SP1 and XP SP2.

So I'm at a loss to how to remotely connect to my SQL Server. FYI I know the server itself is working fine because I can connect to it using Enterprize Manager/Query Analyser on the local machine. Any ideas? Many thanks for your help!If the client and the server are on the same domain, or if the client account belongs to the tree where domain belongs to, then you can use Windows authentication. But if you already tried this, can you do a TELNET from the client with 1433 successfully?|||I've not setup a Domain Controller. Anyway I've solved it, I had SQL Server running in Windows Authentification Mode, so I switched to mixed mode and all is well now :)