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 while taking script

Hi all,
I have some stored procedures in my database.
When I take script of a stored procedure using Enterprise manager from a
client system, the alignment of IF, ELSE, END,etc... are changed. They are
not in a format that I typed in query analyzer.
When I take the same script from another client system they are in proper
alignment.
Please guide me to avoid this.
Should I change any of the settings?
Thanks,
SouraHi
You may want to check what service pack has been applied to the client i.e.
check the file version of (say) one of the exes ? Try scripting from the
Object Browser in Query Analyser.
John
"SouRa" wrote:
> Hi all,
> I have some stored procedures in my database.
> When I take script of a stored procedure using Enterprise manager from a
> client system, the alignment of IF, ELSE, END,etc... are changed. They are
> not in a format that I typed in query analyzer.
> When I take the same script from another client system they are in proper
> alignment.
> Please guide me to avoid this.
> Should I change any of the settings?
> Thanks,
> Soura

Problem while taking script

Hi all,
I have some stored procedures in my database.
When I take script of a stored procedure using Enterprise manager from a
client system, the alignment of IF, ELSE, END,etc... are changed. They are
not in a format that I typed in query analyzer.
When I take the same script from another client system they are in proper
alignment.
Please guide me to avoid this.
Should I change any of the settings?
Thanks,
SouraHi
You may want to check what service pack has been applied to the client i.e.
check the file version of (say) one of the exes ? Try scripting from the
Object Browser in Query Analyser.
John
"SouRa" wrote:

> Hi all,
> I have some stored procedures in my database.
> When I take script of a stored procedure using Enterprise manager from a
> client system, the alignment of IF, ELSE, END,etc... are changed. They ar
e
> not in a format that I typed in query analyzer.
> When I take the same script from another client system they are in proper
> alignment.
> Please guide me to avoid this.
> Should I change any of the settings?
> Thanks,
> Soura

Problem Viewing Databases in Enterprise Manager

I am using SQL Server 7.0 desktop version. I have a remote server registered in SQL Enterprise Manager. I can see the server itself and the main folders under it such as Databases, Management, Data Transformation Services, Security, and Support Services. However, when I click on the plus sign next to databases or try to view the databases it comes up "(No Items)". I am set up as a owner of one of the databases on this machine and I think I have access to all databases in this machine. Is there anything I can do to solve this problem?
I am not having this problem with any other registered SQL servers.I made sure the Show system databases and system object box was checked. It is checked. I still can not see anything.
-- anonymous@.discussions.microsoft.com wrote: --
Not sure if this will solve your problem, but give it a
try:
Right click on server name, select Edit sql server
registration properties and check "Show system databases
and system objects" box.
This should atleast show you master and other system
databases, if nothing else is wrong.
>--Original Message--
>>I am using SQL Server 7.0 desktop version. I have a
remote server registered in SQL Enterprise Manager. I can
see the server itself and the main folders under it such
as Databases, Management, Data Transformation Services,
Security, and Support Services. However, when I click on
the plus sign next to databases or try to view the
databases it comes up "(No Items)". I am set up as a
owner of one of the databases on this machine and I think
I have access to all databases in this machine. Is there
anything I can do to solve this problem?
>>I am not having this problem with any other registered
SQL servers.
>.
>

Problem using bcp with SQL MSDE

I successfully tested a bcp command similar to that below on a Small Business Manager database using SQL Enterprise Edition:
bcp "SELECT EMPLOYID FROM TWO..UPR00100" queryout testfile.txt -U login -P -C
I then tried using the same basic command for another Small Business Manager installation using SQL Desktop Edition. But I get the following:
SQLState = 08001, NativeError = 17
Error = [Microsoft][ODBC SQL Server Driver][DBNETLIB] SQL Server does not
exist or access denied.
The only other difference I'm aware of aside from the SQL edition is that an
'sa' password exists for the second environment. But I put the password in
the bcp command.
Does anyone have an idea why the bcp command works in the one
environment but not the other?
Thanks,
Tom
hi Tom,
"Tom Glasser" <Tom Glasser@.discussions.microsoft.com> ha scritto nel
messaggio news:3076FF6F-2708-4908-9149-6B0E148E6087@.microsoft.com...
> I successfully tested a bcp command similar to that below on a Small
Business Manager database using SQL Enterprise Edition:
> bcp "SELECT EMPLOYID FROM TWO..UPR00100" queryout testfile.txt -U
login -P -C
> I then tried using the same basic command for another Small Business
Manager installation using SQL Desktop Edition. But I get the following:
> SQLState = 08001, NativeError = 17
> Error = [Microsoft][ODBC SQL Server Driver][DBNETLIB] SQL Server does not
> exist or access denied.
> The only other difference I'm aware of aside from the SQL edition is that
an
> 'sa' password exists for the second environment. But I put the password
in
> the bcp command.
> Does anyone have an idea why the bcp command works in the one
> environment but not the other?
>
please have a look at
http://support.microsoft.com/default...B;EN-US;328306
it's possible that your 2nd environment does not accept SQL Server
authenticated connection... if this is the case, please have a look at
http://support.microsoft.com/default...b;en-us;285097 for further
info on how to hack the Windows Registry in order to allow SQL Server
quthenticated connections..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Problem using bcp with SQL MSDE

I successfully tested a bcp command similar to that below on a Small Business Manager database using SQL Enterprise Edition:
bcp "SELECT EMPLOYID FROM TWO..UPR00100" queryout testfile.txt -U login -P -C
I then tried using the same basic command for another Small Business Manager installation using SQL Desktop Edition. But I get the following:
SQLState = 08001, NativeError = 17
Error = [Microsoft][ODBC SQL Server Driver][DBNETLIB] SQL Server does not
exist or access denied.
The only other difference I'm aware of aside from the SQL edition is that an
'sa' password exists for the second environment. But I put the password in
the bcp command.
Does anyone have an idea why the bcp command works in the one
environment but not the other?
Thanks,
Tom
hi Tom,
"Tom Glasser" <Tom Glasser@.discussions.microsoft.com> ha scritto nel
messaggio news:3076FF6F-2708-4908-9149-6B0E148E6087@.microsoft.com...
> I successfully tested a bcp command similar to that below on a Small
Business Manager database using SQL Enterprise Edition:
> bcp "SELECT EMPLOYID FROM TWO..UPR00100" queryout testfile.txt -U
login -P -C
> I then tried using the same basic command for another Small Business
Manager installation using SQL Desktop Edition. But I get the following:
> SQLState = 08001, NativeError = 17
> Error = [Microsoft][ODBC SQL Server Driver][DBNETLIB] SQL Server does not
> exist or access denied.
> The only other difference I'm aware of aside from the SQL edition is that
an
> 'sa' password exists for the second environment. But I put the password
in
> the bcp command.
> Does anyone have an idea why the bcp command works in the one
> environment but not the other?
>
please have a look at
http://support.microsoft.com/default...B;EN-US;328306
it's possible that your 2nd environment does not accept SQL Server
authenticated connection... if this is the case, please have a look at
http://support.microsoft.com/default...b;en-us;285097 for further
info on how to hack the Windows Registry in order to allow SQL Server
quthenticated connections..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Problem upgrading from Standard to Enterprise

I'm hoping someone can explain why the following is happening and how
I can resolve the issue. My company uses SQL Standard for it's prod
server. We decided to setup another server to utilize log shipping.
The server that was installed with Enterprise from scratch worked
perfect. The server that we upgraded from standard appears to work
fine as a server and I can now see the server as a destination server
for log shipping. (hence it does recognize it as Enterprise edition)
The problem is that the upgraded server does not contain any of the
log shipping tables or stored procedures required for log shipping.
Why is this? What is my solution to resolve this? The database is
our production server and is very large so I don't even want to think
about scratching the drive, reinstalling sql, and restoring the
database. Any clues?
Thanks,
willDid you run the log shipping wizard against it? The tables are not there by
default.
Andrew J. Kelly SQL MVP
"Will Wirtz" <WillCWirtz@.Yahoo.com> wrote in message
news:223f5e88.0407202028.448f131e@.posting.google.com...
> I'm hoping someone can explain why the following is happening and how
> I can resolve the issue. My company uses SQL Standard for it's prod
> server. We decided to setup another server to utilize log shipping.
> The server that was installed with Enterprise from scratch worked
> perfect. The server that we upgraded from standard appears to work
> fine as a server and I can now see the server as a destination server
> for log shipping. (hence it does recognize it as Enterprise edition)
> The problem is that the upgraded server does not contain any of the
> log shipping tables or stored procedures required for log shipping.
> Why is this? What is my solution to resolve this? The database is
> our production server and is very large so I don't even want to think
> about scratching the drive, reinstalling sql, and restoring the
> database. Any clues?
> Thanks,
> will

Problem upgrading from Standard to Enterprise

I'm hoping someone can explain why the following is happening and how
I can resolve the issue. My company uses SQL Standard for it's prod
server. We decided to setup another server to utilize log shipping.
The server that was installed with Enterprise from scratch worked
perfect. The server that we upgraded from standard appears to work
fine as a server and I can now see the server as a destination server
for log shipping. (hence it does recognize it as Enterprise edition)
The problem is that the upgraded server does not contain any of the
log shipping tables or stored procedures required for log shipping.
Why is this? What is my solution to resolve this? The database is
our production server and is very large so I don't even want to think
about scratching the drive, reinstalling sql, and restoring the
database. Any clues?
Thanks,
will
Did you run the log shipping wizard against it? The tables are not there by
default.
Andrew J. Kelly SQL MVP
"Will Wirtz" <WillCWirtz@.Yahoo.com> wrote in message
news:223f5e88.0407202028.448f131e@.posting.google.c om...
> I'm hoping someone can explain why the following is happening and how
> I can resolve the issue. My company uses SQL Standard for it's prod
> server. We decided to setup another server to utilize log shipping.
> The server that was installed with Enterprise from scratch worked
> perfect. The server that we upgraded from standard appears to work
> fine as a server and I can now see the server as a destination server
> for log shipping. (hence it does recognize it as Enterprise edition)
> The problem is that the upgraded server does not contain any of the
> log shipping tables or stored procedures required for log shipping.
> Why is this? What is my solution to resolve this? The database is
> our production server and is very large so I don't even want to think
> about scratching the drive, reinstalling sql, and restoring the
> database. Any clues?
> Thanks,
> will

Problem upgrading from Standard to Enterprise

I'm hoping someone can explain why the following is happening and how
I can resolve the issue. My company uses SQL Standard for it's prod
server. We decided to setup another server to utilize log shipping.
The server that was installed with Enterprise from scratch worked
perfect. The server that we upgraded from standard appears to work
fine as a server and I can now see the server as a destination server
for log shipping. (hence it does recognize it as Enterprise edition)
The problem is that the upgraded server does not contain any of the
log shipping tables or stored procedures required for log shipping.
Why is this? What is my solution to resolve this? The database is
our production server and is very large so I don't even want to think
about scratching the drive, reinstalling sql, and restoring the
database. Any clues?
Thanks,
willDid you run the log shipping wizard against it? The tables are not there by
default.
--
Andrew J. Kelly SQL MVP
"Will Wirtz" <WillCWirtz@.Yahoo.com> wrote in message
news:223f5e88.0407202028.448f131e@.posting.google.com...
> I'm hoping someone can explain why the following is happening and how
> I can resolve the issue. My company uses SQL Standard for it's prod
> server. We decided to setup another server to utilize log shipping.
> The server that was installed with Enterprise from scratch worked
> perfect. The server that we upgraded from standard appears to work
> fine as a server and I can now see the server as a destination server
> for log shipping. (hence it does recognize it as Enterprise edition)
> The problem is that the upgraded server does not contain any of the
> log shipping tables or stored procedures required for log shipping.
> Why is this? What is my solution to resolve this? The database is
> our production server and is very large so I don't even want to think
> about scratching the drive, reinstalling sql, and restoring the
> database. Any clues?
> Thanks,
> will