Connection Issues To Report Services

Hello all,

I just installed the SQL 2k5 standard suite of services on a w2k3 enterprise edition server. All went well except for the connection to the reporting server. I get the error below.

"No connection could be made because the target machine actively refused it"

I can't seem to find any information on this error and have no clue where to even start. I've done 10+ installations of this software on various machines and have not encountered this error on any of them.

I have uninstalled, then reinstalled the reporting services and still no solution. All connection attempts are being made on the actual server, not from a desktop. sp1 for sql 2k5 is also installed, if that helps.

Windows Firewall is off.

What web searches I've done have turned up nothing useful. I'm pretty good at figuring this stuff out but this error provides very little of any use.

Anyone out there have any ideas?

Thanks in advance,

Greg

Have you seen this page: http://www.sqljunkies.com/WebLog/edwardm/ ?|||

First, thanks for the link. I'll make note of the ports used by SSAS and some of the other information in there.

I did figure this out, though. Not a very scientific approach so I'll have to run into this problem again to verify but, at a minimum, backing up the encryption key from within Reporting Services Configuration seemed to do the trick. I had a few other things out of whack, too.

At one point, the Backup option was disabled, but disabling "Web Server and HTTP Access" via SQL Server Surface Area Configuration -> Surface Area Configuration for Feature -> Reporting Services enabled the Backup button (kind of a round-about way of making that happen).

After backing up the encryption key, I enabled that option and could connect after that. Problem Solved!

This was further complicated by the fact that the reporting services install didn't conform to some "default" system configuration and performed only a "files-only" install. I really didn't pay that much attention during the install and the difference never really registered in my mind. So, I had to manually configure the reporting server (web directories, db connections, dbs and all).

So, chalk this up to experience and I'll know the next time I run into this.

Other things I addressed, but I'm not sure were relevant were:

the state of the IIS Admin and WWW publishing services (these were stopped and in manual mode during the install - I would think the install would start these if needed)

The execution permissions and application protection modes of the reporting server virtual directories (these were different on the problem installation than a "default" installation - an install on another machine that did work fine)

I don't think I needed to do the reporting services re-install.

When creating the databases manually, I ended up having to do that with scripts. For some reason, the database creation was timing out. The creation of the two databases was ok, but the reporting server temp db did not have any objects in it (no tables, views, etc).

There are a myriad of other things, but I'm almost certain these weren't relevant. All-in-all, a hassle.

Greg

|||Greg: Thanks for your post. I have a problem getting SSRS to work on one of my servers, too. I posted on Sunday:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1215786&SiteID=1
but no one answered. In my case, the local SSRS does not even appear in the list of servers to initialize, within the RS Config Manager. When I installed SSRS, I got the message "Reporting Services was installed, but not configured". This was on a reinstall of SQL05 needed to place the files on a drive other than C:

I will see if backing up the key fixes my problem, next time I'm at that site.|||I'm back at the server with the problem. When I run RS Config Mgr, the button to back up the encryption key is disabled. The only enabled buttons on that page are the 'Restore' button, and the 'Delete' (delete encrypted content) button.

I tried disabling HTTP and Web Access using the Surface Area tool, but the 'Backup' button is still disabled.

Any ideas on how to diagnose and fix this?|||

Hmm. That's what I did. One other thing you might try is deleting the encrypted content. At some point in my troubleshooting process, I pressed that button. I would assume that if encrypted content did exist, and you didn't have the proper encryption key to restore from, the encrypted content would be un-accessible (that's rather obvious). I was comfortable deleting encrypted content because the installation was new and there was nothing to lose.

After doing that, you could then go throught the HTTP and Web Access routine again.

|||No luck for me. Could not get the 'Backup' button enabled on the Encryption Key page. I found in the event log I'm getting EventID 7000 from the RS Service saying "...cannot connect to the report server database". I tried scripting out the DB creation and running that separately. The script ran without errors, but I still get the connection failure event.

I tried running "rsconfig.exe -t -c -d SSRS -a windows -s mssqlserver", where SSRS is my RS db name and mssqlserver is the SQL Server instance name (the default instance), and it came back with "The command completed successfully"

Now since running rsconfig, in the GUI version, RS Configuration Mgr, I'm getting error popups saying it can't connect to SQL Server at all. The popups say it was trying to connect using named pipes. I went to the Surface Area tool and enabled named pipes on remote connections, but RS Config Mgr still can't connect.

It seems like my installation is hosed. I thought Crystal Enterprise was hard to use, but this SSRS is worse! I'm open to suggestions. Does anyone know a reliable way to configure the db connection for Reporting Services?|||I uninstalled and reinstalled the Reporting Services components. This at least allowed RS Config Mgr to connect to SQL Server. However, when I attempt to create a new database for RS, each step succeeds except the last one. For the "Setting Connection Info for the Reporting Server" task, there

was a yellow '!', with the explanation, "Although saving the database

connection succeeded, the report server cannot access internal

information about this deployment to determine if the current

configuration is valid for this edition. ..." The RS Service is still logging errors in the event log saying it cannot connect. I give up.

connection issue with enterprise manager but works with management studio

Hi,

I have an interesting scenario.

I have a SQL Server 2000 Standard Edition instance running on Computer A. I'm trying to access it through computers B and C.

Computer B has Sql Server 2005 Express Edition installed and I was able to use its Management Studio and
connect to instance on Computer A.

Computer C has SQL Server 2000 Standard Edition installed. When I try to connect to the instance on Computer A,
I get connection failed message.

I checked some settings. Both TCP/IP and Named pipes are enabled on the instance in A. The TCP/IP port is set to 1433 for
both client and server.

Please give me some ideas as to how I can solve this problem.

-Thanks

What is the error message that is displayed?|||I am assuming all three are on the same network then it is a simple right click at the top of Management Studio and register the 2000 then it becomes local to you. I have registered 68 7/2000 in one box so it works . Hope this helps.|||

The error said something like

Invalid Connection.ConnetionOpen(Invalid Instance)

|||

I figured it out.

Both A and C had Sql Server 2000 instances. When you try to connect to one Sql Server 2000 instance from another, Enterprise Manager automatically sets "Dynamically determine port" option and hence the connection fails. What you can do is use the Client Network Utility in C and create a new TCP/IP alias and uncheck the "dynamically determine port" option and manually set it to 1433. Then u can use Enterprise Manager in C and select the new alias that you created and finish registering the 2000 instance from A.

Thanks for your replies.

|||

shiversticks:

I figured it out.

Both A and C had Sql Server 2000 instances. When you try to connect to one Sql Server 2000 instance from another, Enterprise Manager automatically sets "Dynamically determine port" option and hence the connection fails. What you can do is use the Client Network Utility in C and create a new TCP/IP alias and uncheck the "dynamically determine port" option and manually set it to 1433. Then u can use Enterprise Manager in C and select the new alias that you created and finish registering the 2000 instance from A.

Thanks for your replies.

(on the same network then it is a simple right click at the top of Management Studio and register the 2000 then it becomes local to you. I have registered 68 7/2000 in one box so it works )

For the reference of future readers of this thread you just right click and register the other SQL Server as I originally posted and leave your port setings alone in eigth years I have not had reason to touch port settings it is not needed. Port settings could lead to SQL injection attacks.

Connection handshake failed.

Hi.

I created two instances of SQL Server Dev Edition on the same machine.

The two instances acted as the sender / receiver.

However, when the message is transmitted from "Sender" to "Receiver", the following errors are
displayed in "SQL Profiler".

「Connection handshake failed. There is no compatible authentication protocol. State 21.」

How should be dealt with with this?
My best regards.

piknik

Seems like there is a problem with how you've setup your endpoints. Could you paste the script which you used for creating the endpoints? If you don't have that, could you paste the results from this query run on both instances?

select * from sys.service_broker_endpoints

|||

One machine is configured to use CERTIFICATE authentication, the other is configured to use WINDOWS. (or one is configured to use WINDOWS KERBEROS and the other WINDOWS NTLM).

Configure the endpoints to have at least one compatible authentication protocol and it will work.

HTH,
~ Remus

|||

Thank you for the reply.

I used following Script.

[Sender]

USE master
GO

-- Create master key in the master database
CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'password62374'

-- Create the certificate for transport security
CREATE CERTIFICATE TransportCert1
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\TransportCert1.cer'
WITH PRIVATE KEY (
FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\TransportCert1.pvk',
DECRYPTION BY PASSWORD = 'password62374'
)
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Create a user in the master db to be associated with
-- the public key from the remote certificate (TestCert2.cer)
CREATE LOGIN remcert WITH PASSWORD = 'password62374'
CREATE USER remcert FOR LOGIN remcert

-- remcert has to have connect priviliges
GRANT CONNECT TO remcert

-- Install the public key from the remote cert in master
CREATE CERTIFICATE TransportCert2
AUTHORIZATION remcert
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\TransportCert2.cer'
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Switch to the user database
USE SuperMarketServer
GO

-- Create a master key
CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'password62374'

-- Create a certificate for dialog security
CREATE CERTIFICATE DialogCert1
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\DialogCert1.cer'
WITH PRIVATE KEY (
FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\DialogCert1.pvk',
DECRYPTION BY PASSWORD = 'password62374'
)
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Create user that holds the remote public key for the dialog security certificate
CREATE USER remcert FOR LOGIN remcert

CREATE CERTIFICATE DialogCert2
AUTHORIZATION remcert
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\DialogCert2.cer'
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Create a remote service binding associating the remcert user
-- with the remote service
CREATE REMOTE SERVICE BINDING [SellItemBinding]
TO SERVICE 'SellItemService'
WITH USER = remcert,
ANONYMOUS = Off

-- The user has to have SEND permissions
GRANT SEND ON SERVICE::[SoldItemService] TO remcert
go

-- Enable communication between instances by creating an endpoint
CREATE ENDPOINT ServerEndpoint
STATE = STARTED
AS TCP
(
LISTENER_PORT = 5024
)
FOR SERVICE_BROKER (AUTHENTICATION = CERTIFICATE TransportCert1)

-- Finally grant connect permission to user used to secure the dialog
USE master
GO

GRANT CONNECT ON ENDPOINT::ServerEndpoint TO remcert
GO

SELECT * FROM sys.endpoints
--

It is set to "CERTIFICATE authentication" as which Sender and Reciver are the
same.

The sample of Script is put.
http://enterpriselibrary.jp/SampleDemo.zip

My Best Regards.

piknik.

connection failed from client application

Hi ,
the client application used is ms access via odbc to sql server 2000 std
edition sp3a
sometimes the user just get the following error :
1 - Connection failed , SQL state : S1000 , SQL Server Error : 0 Cannot
generate SSPI context
2 - Connection failed , SQL state : HY000 , SQL Server Error : 0 Cannot
generate SSPI context
does anyone knows wat's the cause and how to resolve
if need to reinstall the odbc , how can i do that ?
tks & rdgsHi
You may want to check out
http://support.microsoft.com/kb/811889/
http://support.microsoft.com/default.aspx?scid=kb;en-us;267588
http://support.microsoft.com/default.aspx?scid=kb;en-us;814401
John
"maxzsim" wrote:
> Hi ,
> the client application used is ms access via odbc to sql server 2000 std
> edition sp3a
> sometimes the user just get the following error :
> 1 - Connection failed , SQL state : S1000 , SQL Server Error : 0 Cannot
> generate SSPI context
> 2 - Connection failed , SQL state : HY000 , SQL Server Error : 0 Cannot
> generate SSPI context
> does anyone knows wat's the cause and how to resolve
> if need to reinstall the odbc , how can i do that ?
> tks & rdgs
>

Connection Error when trying to run MDX-queries

To learn MDX (on SQL Server 2005 dev edition) I decided to put up some sample cubes and run MDX-queries from SQL Server Management Studio. When processing the cube in BI Studio I get the following error:

"The datasource , 'Adventure Works DW', contains an ImpersonationMode that that is not supported for processing operations."

Fair enough, then I change the impersonationmode in the datasource to service account. It all processes/deploys well and I can browse the cube in BI Studio. Off to Management studio to run some mdx-queries. Here however I get the error:

"Error (Data mining): Either the user, ######, does not have permission to access the referenced mining model, Analysis Services Tutorial, or the object does not exist."

That is of course due to me using the current user credentials for the query. So I try to change the current connection in management studio but the helpbutton informs me that as of now only windowsauthentication can be used for analysis services. So the only connectionway I can use from here is the only one not supported when processing?! This must mean I've done some childishly simple newbiemistake and I would be very grateful if you pointed it out so I could get started with the MDX.

Perhaps I should add that the user ##### is administrator for the entire server. The server administrator role should take precedence over database roles, right (not that it helped when I added one of those and included me)? The user is also a member of the SQLServer2005OLAPUser group. I also have full access to the underlying relational database. So I can delete or create elements or entire databases at will but not ask simple questions to them...

The other option - that the cube doesn't exist seems dispelled by being able to browse it and the dimensions etc. showing up in object explorers and in the left pane of the MDX Query interface.

Which leaves me at some permission problem again - some help would REALLY be appreciated.

|||Please provide more information as something strange is going on here - given what you have provided, you should not be having a permission error - but, the error message does not make sense as the Analysis Services Tutorial has no data mining component.|||

I don't have the queries I tested with anymore since I got it to work but the bottomline was that I didn't have any "ON ROW|COLUMNS" etc. part of the selection clause which obviously sent the engine looking for something that didn't exist. I.e. just had queries with variations on the form:

SELECT dim

FROM cube

Looked at what the browser sent with the profiler and changed to:

SELECT dim ON 0

FROM cube

and everything has been working well since then. Perhaps a bit strange errormessage but otherwise my mistake. Sorry for taking up your time with this one

|||

I am new to Analysis services. I migared on of the Sql 2000 cube to sql 2005 .I am getting the same message , when i use Pivot table to dipaly data from sql 2005 Cube.With sql 2000, it works great.Here is the eror message.

Error (Data mining): Either the user, Domain/User doen not have permission to access the referenced mining model, SalesHistoryData , or the object does not exist. Error (Data mining): Either the user, DOMAIN\USER , does not have permission to access the referenced mining model, SalesHistoryData , or the object does not exist.

When i ran Profiler , it is trying to run the following sql statement.

SELECT * FROM "SalesHistoryData "

I have granted all high level rights.Still not working.

Expecting fix from someone.

|||

hi, i recv the same while trying to query the cube from SSMS...

Error (Data mining): Either the user, domain\account, does not have permission to access the referenced mining model, MaxMinSalesDM, or the object does not exist.

no error building or deploying the cube..

can see the cube in the database folder as well

please help...

|||

sorry, my mistake...

it should be select from [Cube Name], not select * from [Cube Name]

|||

My issue solved.I just had to change the Data Source Provider to msolap.2 to msolap.3 in the Pivot table properties.

You may also have to try with just msolap(No vesion) in case the above change doesn't fix it.

Connection Error when trying to run MDX-queries

To learn MDX (on SQL Server 2005 dev edition) I decided to put up some sample cubes and run MDX-queries from SQL Server Management Studio. When processing the cube in BI Studio I get the following error:

"The datasource , 'Adventure Works DW', contains an ImpersonationMode that that is not supported for processing operations."

Fair enough, then I change the impersonationmode in the datasource to service account. It all processes/deploys well and I can browse the cube in BI Studio. Off to Management studio to run some mdx-queries. Here however I get the error:

"Error (Data mining): Either the user, ######, does not have permission to access the referenced mining model, Analysis Services Tutorial, or the object does not exist."

That is of course due to me using the current user credentials for the query. So I try to change the current connection in management studio but the helpbutton informs me that as of now only windowsauthentication can be used for analysis services. So the only connectionway I can use from here is the only one not supported when processing?! This must mean I've done some childishly simple newbiemistake and I would be very grateful if you pointed it out so I could get started with the MDX.

Perhaps I should add that the user ##### is administrator for the entire server. The server administrator role should take precedence over database roles, right (not that it helped when I added one of those and included me)? The user is also a member of the SQLServer2005OLAPUser group. I also have full access to the underlying relational database. So I can delete or create elements or entire databases at will but not ask simple questions to them...

The other option - that the cube doesn't exist seems dispelled by being able to browse it and the dimensions etc. showing up in object explorers and in the left pane of the MDX Query interface.

Which leaves me at some permission problem again - some help would REALLY be appreciated.

|||Please provide more information as something strange is going on here - given what you have provided, you should not be having a permission error - but, the error message does not make sense as the Analysis Services Tutorial has no data mining component.|||

I don't have the queries I tested with anymore since I got it to work but the bottomline was that I didn't have any "ON ROW|COLUMNS" etc. part of the selection clause which obviously sent the engine looking for something that didn't exist. I.e. just had queries with variations on the form:

SELECT dim

FROM cube

Looked at what the browser sent with the profiler and changed to:

SELECT dim ON 0

FROM cube

and everything has been working well since then. Perhaps a bit strange errormessage but otherwise my mistake. Sorry for taking up your time with this one

|||

I am new to Analysis services. I migared on of the Sql 2000 cube to sql 2005 .I am getting the same message , when i use Pivot table to dipaly data from sql 2005 Cube.With sql 2000, it works great.Here is the eror message.

Error (Data mining): Either the user, Domain/User doen not have permission to access the referenced mining model, SalesHistoryData , or the object does not exist. Error (Data mining): Either the user, DOMAIN\USER , does not have permission to access the referenced mining model, SalesHistoryData , or the object does not exist.

When i ran Profiler , it is trying to run the following sql statement.

SELECT * FROM "SalesHistoryData "

I have granted all high level rights.Still not working.

Expecting fix from someone.

|||

hi, i recv the same while trying to query the cube from SSMS...

Error (Data mining): Either the user, domain\account, does not have permission to access the referenced mining model, MaxMinSalesDM, or the object does not exist.

no error building or deploying the cube..

can see the cube in the database folder as well

please help...

|||

sorry, my mistake...

it should be select from [Cube Name], not select * from [Cube Name]

|||

My issue solved.I just had to change the Data Source Provider to msolap.2 to msolap.3 in the Pivot table properties.

You may also have to try with just msolap(No vesion) in case the above change doesn't fix it.

Connection Error when trying to run MDX-queries

To learn MDX (on SQL Server 2005 dev edition) I decided to put up some sample cubes and run MDX-queries from SQL Server Management Studio. When processing the cube in BI Studio I get the following error:

"The datasource , 'Adventure Works DW', contains an ImpersonationMode that that is not supported for processing operations."

Fair enough, then I change the impersonationmode in the datasource to service account. It all processes/deploys well and I can browse the cube in BI Studio. Off to Management studio to run some mdx-queries. Here however I get the error:

"Error (Data mining): Either the user, ######, does not have permission to access the referenced mining model, Analysis Services Tutorial, or the object does not exist."

That is of course due to me using the current user credentials for the query. So I try to change the current connection in management studio but the helpbutton informs me that as of now only windowsauthentication can be used for analysis services. So the only connectionway I can use from here is the only one not supported when processing?! This must mean I've done some childishly simple newbiemistake and I would be very grateful if you pointed it out so I could get started with the MDX.

Perhaps I should add that the user ##### is administrator for the entire server. The server administrator role should take precedence over database roles, right (not that it helped when I added one of those and included me)? The user is also a member of the SQLServer2005OLAPUser group. I also have full access to the underlying relational database. So I can delete or create elements or entire databases at will but not ask simple questions to them...

The other option - that the cube doesn't exist seems dispelled by being able to browse it and the dimensions etc. showing up in object explorers and in the left pane of the MDX Query interface.

Which leaves me at some permission problem again - some help would REALLY be appreciated.

|||Please provide more information as something strange is going on here - given what you have provided, you should not be having a permission error - but, the error message does not make sense as the Analysis Services Tutorial has no data mining component.|||

I don't have the queries I tested with anymore since I got it to work but the bottomline was that I didn't have any "ON ROW|COLUMNS" etc. part of the selection clause which obviously sent the engine looking for something that didn't exist. I.e. just had queries with variations on the form:

SELECT dim

FROM cube

Looked at what the browser sent with the profiler and changed to:

SELECT dim ON 0

FROM cube

and everything has been working well since then. Perhaps a bit strange errormessage but otherwise my mistake. Sorry for taking up your time with this one

|||

I am new to Analysis services. I migared on of the Sql 2000 cube to sql 2005 .I am getting the same message , when i use Pivot table to dipaly data from sql 2005 Cube.With sql 2000, it works great.Here is the eror message.

Error (Data mining): Either the user, Domain/User doen not have permission to access the referenced mining model, SalesHistoryData , or the object does not exist. Error (Data mining): Either the user, DOMAIN\USER , does not have permission to access the referenced mining model, SalesHistoryData , or the object does not exist.

When i ran Profiler , it is trying to run the following sql statement.

SELECT * FROM "SalesHistoryData "

I have granted all high level rights.Still not working.

Expecting fix from someone.

|||

hi, i recv the same while trying to query the cube from SSMS...

Error (Data mining): Either the user, domain\account, does not have permission to access the referenced mining model, MaxMinSalesDM, or the object does not exist.

no error building or deploying the cube..

can see the cube in the database folder as well

please help...

|||

sorry, my mistake...

it should be select from [Cube Name], not select * from [Cube Name]

|||

My issue solved.I just had to change the Data Source Provider to msolap.2 to msolap.3 in the Pivot table properties.

You may also have to try with just msolap(No vesion) in case the above change doesn't fix it.

Connection Error when trying to run MDX-queries

To learn MDX (on SQL Server 2005 dev edition) I decided to put up some sample cubes and run MDX-queries from SQL Server Management Studio. When processing the cube in BI Studio I get the following error:

"The datasource , 'Adventure Works DW', contains an ImpersonationMode that that is not supported for processing operations."

Fair enough, then I change the impersonationmode in the datasource to service account. It all processes/deploys well and I can browse the cube in BI Studio. Off to Management studio to run some mdx-queries. Here however I get the error:

"Error (Data mining): Either the user, ######, does not have permission to access the referenced mining model, Analysis Services Tutorial, or the object does not exist."

That is of course due to me using the current user credentials for the query. So I try to change the current connection in management studio but the helpbutton informs me that as of now only windowsauthentication can be used for analysis services. So the only connectionway I can use from here is the only one not supported when processing?! This must mean I've done some childishly simple newbiemistake and I would be very grateful if you pointed it out so I could get started with the MDX.

Perhaps I should add that the user ##### is administrator for the entire server. The server administrator role should take precedence over database roles, right (not that it helped when I added one of those and included me)? The user is also a member of the SQLServer2005OLAPUser group. I also have full access to the underlying relational database. So I can delete or create elements or entire databases at will but not ask simple questions to them...

The other option - that the cube doesn't exist seems dispelled by being able to browse it and the dimensions etc. showing up in object explorers and in the left pane of the MDX Query interface.

Which leaves me at some permission problem again - some help would REALLY be appreciated.

|||Please provide more information as something strange is going on here - given what you have provided, you should not be having a permission error - but, the error message does not make sense as the Analysis Services Tutorial has no data mining component.|||

I don't have the queries I tested with anymore since I got it to work but the bottomline was that I didn't have any "ON ROW|COLUMNS" etc. part of the selection clause which obviously sent the engine looking for something that didn't exist. I.e. just had queries with variations on the form:

SELECT dim

FROM cube

Looked at what the browser sent with the profiler and changed to:

SELECT dim ON 0

FROM cube

and everything has been working well since then. Perhaps a bit strange errormessage but otherwise my mistake. Sorry for taking up your time with this one

|||

I am new to Analysis services. I migared on of the Sql 2000 cube to sql 2005 .I am getting the same message , when i use Pivot table to dipaly data from sql 2005 Cube.With sql 2000, it works great.Here is the eror message.

Error (Data mining): Either the user, Domain/User doen not have permission to access the referenced mining model, SalesHistoryData , or the object does not exist. Error (Data mining): Either the user, DOMAIN\USER , does not have permission to access the referenced mining model, SalesHistoryData , or the object does not exist.

When i ran Profiler , it is trying to run the following sql statement.

SELECT * FROM "SalesHistoryData "

I have granted all high level rights.Still not working.

Expecting fix from someone.

|||

hi, i recv the same while trying to query the cube from SSMS...

Error (Data mining): Either the user, domain\account, does not have permission to access the referenced mining model, MaxMinSalesDM, or the object does not exist.

no error building or deploying the cube..

can see the cube in the database folder as well

please help...

|||

sorry, my mistake...

it should be select from [Cube Name], not select * from [Cube Name]

|||

My issue solved.I just had to change the Data Source Provider to msolap.2 to msolap.3 in the Pivot table properties.

You may also have to try with just msolap(No vesion) in case the above change doesn't fix it.

Connection error in sql server compact edition 2005

HI friends,

i m working on device application ..i m using sql server ce 2005 with c#.net ... but when i m trying to connect to database it shows me error that

"the database path not found ... please check the path [,,,filename,,,]"

my code is as below

private string ConnStr = "Data Source =\\My Documents\\Employee.sdf;";

private void cmdCheckConnecton_Click(object sender, EventArgs e)
{
try
{
cn = new System.Data.SqlServerCe.SqlCeConnection(ConnStr);
cn.Open();
MessageBox.Show(cn.State.ToString());
}
catch (SqlCeException ex)
{
MessageBox.Show(ex.Message.ToString());
}
}

i have my database in My Documents and the path is right still it shows the error

pls help if any one have a solution regarding this problem

thanxx

Zalak Shah

This is just a guess, but looking at my connection strings they have quotes around the Data Source, so maybe try adding those in.

private string ConnStr = "Data Source =\"\\My Documents\\Employee.sdf\";";

|||hi

i have done it but still it doesn't work

one more thing i want to tell u .. if i create the database on the same location even it is there it will create once again and no files will be create at that location that 's just a file in a memory .... and after that that memory file will accessed by that code and working perfectly as i needed

can u tell me one thing that location is in mobile device (Emulator) 's location or my hard drive's location

Connection error in sql server compact edition 2005

HI friends,

i m working on device application ..i m using sql server ce 2005 with c#.net ... but when i m trying to connect to database it shows me error that

"the database path not found ... please check the path [,,,filename,,,]"

my code is as below

private string ConnStr = "Data Source =\\My Documents\\Employee.sdf;";

private void cmdCheckConnecton_Click(object sender, EventArgs e)
{
try
{
cn = new System.Data.SqlServerCe.SqlCeConnection(ConnStr);
cn.Open();
MessageBox.Show(cn.State.ToString());
}
catch (SqlCeException ex)
{
MessageBox.Show(ex.Message.ToString());
}
}

i have my database in My Documents and the path is right still it shows the error

pls help if any one have a solution regarding this problem

thanxx

Zalak Shah

This is just a guess, but looking at my connection strings they have quotes around the Data Source, so maybe try adding those in.

private string ConnStr = "Data Source =\"\\My Documents\\Employee.sdf\";";

|||hi

i have done it but still it doesn't work

one more thing i want to tell u .. if i create the database on the same location even it is there it will create once again and no files will be create at that location that 's just a file in a memory .... and after that that memory file will accessed by that code and working perfectly as i needed

can u tell me one thing that location is in mobile device (Emulator) 's location or my hard drive's location

Connection between SQL Server 2000 SP3a and ODBC Driver

Database: SQL Server 2000 Developer Edition SP3a
Frontend: MS Access 2000 and Access 2003
A Custm-built Medical Records Database
I am having a problem connecting to my SQL server with certain ODBC drivers
(sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
particular ones which retrieve from lots of columns. On these forms there is
a long delay, and a little of the data is retrieved, but the rest of fields
arent. And there are no error messages.
I am trying to connect to a MS-SQL Server 2000 SP3a database through Access
2003 (frontend of database) on our only XP machine. All my NT machines
connect
easily, with no problems. A handful of Windows 2000 machines give me
problems with the newer ODBC drivers, but if i would replace the
SQLSRV32.DLL with a copy from the NT machines it would work ok.
I thought upgrading the Service Pack from SP2 to SP3a would help but that
didnt work. I cant figure out what the problem is, but it sounds (to me)
similar to what is described in (FIX 814410 -
http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this be
it? but the SP upgrade didnt fix/help...
Please advise how I can fix it, or where i can look to figure out what the
problem is.
Thank you.
Hi
SQL Profiler will indicate what queries are running slow. Try running it
from Query Analyser and check out their query plan. You may also want to
look at the statistics and how often they are updated. You may also want to
check the
Also you may want to check the version of MDAC you are running on each
machine using the MDAC component checker
http://msdn.microsoft.com/data/mdac/default.aspx
John
"desimaj" <desimaj@.discussions.microsoft.com> wrote in message
news:92716878-DB7C-4479-A96C-892F313C6F6B@.microsoft.com...
> Database: SQL Server 2000 Developer Edition SP3a
> Frontend: MS Access 2000 and Access 2003
> A Custm-built Medical Records Database
> I am having a problem connecting to my SQL server with certain ODBC
> drivers
> (sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
> particular ones which retrieve from lots of columns. On these forms there
> is
> a long delay, and a little of the data is retrieved, but the rest of
> fields
> arent. And there are no error messages.
> I am trying to connect to a MS-SQL Server 2000 SP3a database through
> Access
> 2003 (frontend of database) on our only XP machine. All my NT machines
> connect
> easily, with no problems. A handful of Windows 2000 machines give me
> problems with the newer ODBC drivers, but if i would replace the
> SQLSRV32.DLL with a copy from the NT machines it would work ok.
> I thought upgrading the Service Pack from SP2 to SP3a would help but that
> didnt work. I cant figure out what the problem is, but it sounds (to me)
> similar to what is described in (FIX 814410 -
> http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this
> be
> it? but the SP upgrade didnt fix/help...
> Please advise how I can fix it, or where i can look to figure out what the
> problem is.
> Thank you.
>

Connection between SQL Server 2000 SP3a and ODBC Driver

Database: SQL Server 2000 Developer Edition SP3a
Frontend: MS Access 2000 and Access 2003
A Custm-built Medical Records Database
I am having a problem connecting to my SQL server with certain ODBC drivers
(sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
particular ones which retrieve from lots of columns. On these forms there is
a long delay, and a little of the data is retrieved, but the rest of fields
arent. And there are no error messages.
I am trying to connect to a MS-SQL Server 2000 SP3a database through Access
2003 (frontend of database) on our only XP machine. All my NT machines
connect
easily, with no problems. A handful of Windows 2000 machines give me
problems with the newer ODBC drivers, but if i would replace the
SQLSRV32.DLL with a copy from the NT machines it would work ok.
I thought upgrading the Service Pack from SP2 to SP3a would help but that
didnt work. I cant figure out what the problem is, but it sounds (to me)
similar to what is described in (FIX 814410 -
http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this be
it? but the SP upgrade didnt fix/help...
Please advise how I can fix it, or where i can look to figure out what the
problem is.
Thank you.Hi
SQL Profiler will indicate what queries are running slow. Try running it
from Query Analyser and check out their query plan. You may also want to
look at the statistics and how often they are updated. You may also want to
check the
Also you may want to check the version of MDAC you are running on each
machine using the MDAC component checker
http://msdn.microsoft.com/data/mdac/default.aspx
John
"desimaj" <desimaj@.discussions.microsoft.com> wrote in message
news:92716878-DB7C-4479-A96C-892F313C6F6B@.microsoft.com...
> Database: SQL Server 2000 Developer Edition SP3a
> Frontend: MS Access 2000 and Access 2003
> A Custm-built Medical Records Database
> I am having a problem connecting to my SQL server with certain ODBC
> drivers
> (sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
> particular ones which retrieve from lots of columns. On these forms there
> is
> a long delay, and a little of the data is retrieved, but the rest of
> fields
> arent. And there are no error messages.
> I am trying to connect to a MS-SQL Server 2000 SP3a database through
> Access
> 2003 (frontend of database) on our only XP machine. All my NT machines
> connect
> easily, with no problems. A handful of Windows 2000 machines give me
> problems with the newer ODBC drivers, but if i would replace the
> SQLSRV32.DLL with a copy from the NT machines it would work ok.
> I thought upgrading the Service Pack from SP2 to SP3a would help but that
> didnt work. I cant figure out what the problem is, but it sounds (to me)
> similar to what is described in (FIX 814410 -
> http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this
> be
> it? but the SP upgrade didnt fix/help...
> Please advise how I can fix it, or where i can look to figure out what the
> problem is.
> Thank you.
>

Connection between Principal and Mirror servers

Hi guys, right now I am facing this scenario several times and I wonder why it can be happen. Both SQL servers are in Enterprise SP1 edition. The mirroring setup can be work fine to me. Once my principal get attacking by DDOS, then mirroring session change the status to 'DISCONNECTED'. However, after DDOS attack solved and line connection gets back on the principal server, the mirroring session still remain to the status ('DISCONNECTED'). If I restart the SQL services on principal server or mirror server, then only the mirroring session change to 'SYNCHRONIZING' status. Does anyone faced this happen before? I need some assistance on it and hope able to get any explanation or solution from you guys. Thanx and have a nice day.

Best Regards,

Hans

Are the SQL server services set to BOOT or enabled to restart on the failure.

Also chekc the SQL server error log in this case.

Connection

Hi,

I installed SQLSERVER EXPRESS Edition.When i try to connect to sqlserver express,In the server name what we have to specify.

I know that we have to specify Systemname\SqlServer instance name.

I find sqlserver instance name

in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SSMSEE

My system name is Kal.

Now my server name:kal\SSMSEE

and i followed windows authentication.

Username:kal\Administrator.

And click on connect.

Iam getting this error.Couldnot connect to SqlServer.Server does not allow Remote connections.

How to resolve this error.

Thanks in advance

Hi,

have a look at my site under the section Screencasts on the top navbar. YOu will find the Screencast for Enabling remote connections here which will guide you through the process of enabling your SQL Server (Express) for remote connectivity.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

connection

Hi
I get this error from sql server 2005 developer edition on windows. I ca't
seem to get any connection to work sqlnative client og file connection. I
have installed all features from the sql developer dvd.
* The connection "SourceConnectionOLEDB" is not found. This error is thrown
by Connections collection when the specific connection element is not found.
({58517491-4481-44D8-BD05-DAA10CBF420E})
/rkri
Have you enabled TCP/IP on your SQL Server developer edition installation? I
think it is disabled by default. Check the Configuration Manager.
Ben Nevarez, M.Sc.
MCDBA, OCP
"Ren K" <rkri000@.foa.dk> wrote in message
news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
> Hi
> I get this error from sql server 2005 developer edition on windows. I
> ca't
> seem to get any connection to work sqlnative client og file connection. I
> have installed all features from the sql developer dvd.
> * The connection "SourceConnectionOLEDB" is not found. This error is
> thrown
> by Connections collection when the specific connection element is not
> found.
> ({58517491-4481-44D8-BD05-DAA10CBF420E})
> /rkri
>
>
|||I have a installed the sql server 2005 on a named instance called sql2005
and this is running side-by-side with sqlexpress and msde ( 2000). my tcp/tp
is enabled i checked this under protocols for sql2005, I have enabled named
pipes and shared memory ( this was enabled by default ). I don't understand
I never had any problems whatsoever with sql server 2000 and are already
looking forward to the first service pack.
Thanks for the reply
/rkri
"Ben Nevarez" <bnevarez@.sjm.com> skrev i en meddelelse
news:uJhHClQ$FHA.4028@.tk2msftngp13.phx.gbl...
> Have you enabled TCP/IP on your SQL Server developer edition installation?
> I think it is disabled by default. Check the Configuration Manager.
> Ben Nevarez, M.Sc.
> MCDBA, OCP
>
> "Ren K" <rkri000@.foa.dk> wrote in message
> news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
>

connection

Hi
I get this error from sql server 2005 developer edition on windows. I ca't
seem to get any connection to work sqlnative client og file connection. I
have installed all features from the sql developer dvd.
* The connection "SourceConnectionOLEDB" is not found. This error is thrown
by Connections collection when the specific connection element is not found.
({58517491-4481-44D8-BD05-DAA10CBF420E})
/rkriHave you enabled TCP/IP on your SQL Server developer edition installation? I
think it is disabled by default. Check the Configuration Manager.
Ben Nevarez, M.Sc.
MCDBA, OCP
"Ren K" <rkri000@.foa.dk> wrote in message
news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
> Hi
> I get this error from sql server 2005 developer edition on windows. I
> ca't
> seem to get any connection to work sqlnative client og file connection. I
> have installed all features from the sql developer dvd.
> * The connection "SourceConnectionOLEDB" is not found. This error is
> thrown
> by Connections collection when the specific connection element is not
> found.
> ({58517491-4481-44D8-BD05-DAA10CBF420E})
> /rkri
>
>|||I have a installed the sql server 2005 on a named instance called sql2005
and this is running side-by-side with sqlexpress and msde ( 2000). my tcp/tp
is enabled i checked this under protocols for sql2005, I have enabled named
pipes and shared memory ( this was enabled by default ). I don't understand
I never had any problems whatsoever with sql server 2000 and are already
looking forward to the first service pack.
Thanks for the reply
/rkri
"Ben Nevarez" <bnevarez@.sjm.com> skrev i en meddelelse
news:uJhHClQ$FHA.4028@.tk2msftngp13.phx.gbl...
> Have you enabled TCP/IP on your SQL Server developer edition installation?
> I think it is disabled by default. Check the Configuration Manager.
> Ben Nevarez, M.Sc.
> MCDBA, OCP
>
> "Ren K" <rkri000@.foa.dk> wrote in message
> news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
>

connection

Hi
I get this error from sql server 2005 developer edition on windows. I ca't
seem to get any connection to work sqlnative client og file connection. I
have installed all features from the sql developer dvd.
* The connection "SourceConnectionOLEDB" is not found. This error is thrown
by Connections collection when the specific connection element is not found.
({58517491-4481-44D8-BD05-DAA10CBF420E})
/rkriHave you enabled TCP/IP on your SQL Server developer edition installation? I
think it is disabled by default. Check the Configuration Manager.
Ben Nevarez, M.Sc.
MCDBA, OCP
"René K" <rkri000@.foa.dk> wrote in message
news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
> Hi
> I get this error from sql server 2005 developer edition on windows. I
> ca't
> seem to get any connection to work sqlnative client og file connection. I
> have installed all features from the sql developer dvd.
> * The connection "SourceConnectionOLEDB" is not found. This error is
> thrown
> by Connections collection when the specific connection element is not
> found.
> ({58517491-4481-44D8-BD05-DAA10CBF420E})
> /rkri
>
>|||I have a installed the sql server 2005 on a named instance called sql2005
and this is running side-by-side with sqlexpress and msde ( 2000). my tcp/tp
is enabled i checked this under protocols for sql2005, I have enabled named
pipes and shared memory ( this was enabled by default ). I don't understand
I never had any problems whatsoever with sql server 2000 and are already
looking forward to the first service pack.
Thanks for the reply
/rkri
"Ben Nevarez" <bnevarez@.sjm.com> skrev i en meddelelse
news:uJhHClQ$FHA.4028@.tk2msftngp13.phx.gbl...
> Have you enabled TCP/IP on your SQL Server developer edition installation?
> I think it is disabled by default. Check the Configuration Manager.
> Ben Nevarez, M.Sc.
> MCDBA, OCP
>
> "René K" <rkri000@.foa.dk> wrote in message
> news:ObaCPXQ$FHA.356@.TK2MSFTNGP12.phx.gbl...
>> Hi
>> I get this error from sql server 2005 developer edition on windows. I
>> ca't
>> seem to get any connection to work sqlnative client og file connection. I
>> have installed all features from the sql developer dvd.
>> * The connection "SourceConnectionOLEDB" is not found. This error is
>> thrown
>> by Connections collection when the specific connection element is not
>> found.
>> ({58517491-4481-44D8-BD05-DAA10CBF420E})
>> /rkri
>>
>

Connecting Visual Studio 2003 to SQL Server Express 2005 Edition

I was wondering if it is possible to connect the SQL Server 2005 Express Version to Visual Studio 2003.If its possible , how can it be done?Cos i seem to have an error if i do so.

You can check here for basic connectivity information:

http://msdn2.microsoft.com/en-us/library/ms345332.aspx

And make sure you check out the complete Express tutorial that Microsoft puts out for free:

http://msdn.microsoft.com/vstudio/express/sql/learning/default.aspx

Buck Woody

Connecting Visual Studio 2003 to SQL Server Express 2005 Edition

I was wondering if it is possible to connect the SQL Server 2005 Express Version to Visual Studio 2003.If its possible , how can it be done?Cos i seem to have an error if i do so.

You can check here for basic connectivity information:

http://msdn2.microsoft.com/en-us/library/ms345332.aspx

And make sure you check out the complete Express tutorial that Microsoft puts out for free:

http://msdn.microsoft.com/vstudio/express/sql/learning/default.aspx

Buck Woody

Connecting via Management Studio

hi,

I've installed Microsoft SQL Server Compact Edition 3.1 .I want to connect to via management studio , but I dont khonw how!

SDK says :

1. In SQL Server Management Studio, open Object Explorer.

2. In Object Explorer, click Connect, and then choose SQL Server Compact Edition.

but there is no "Server Compact Edition" !

please help, Thanks

In my installation, it is still called SQL Server Mobile Edition, not Compact Edition, in the Object Explorer > Connect menu.

HTH,
Jon
|||

It is working but I doubt that it is the CE 3.1 !

Thanks.

|||

Your doubt is justified

There's "Compact Edition" all over the management studio

In VS2005 prof i first installed the SP1 then: (in this order)

SSCE31VSTools-enu-exe

SQLServerCE31-EN.msi

SSCE31BOL (Books online)

SSCE31SDK-ENU.msi

After that the newest version of management studio express (SQLServer2005_SSMSEE.msi)

This is how I did connect.

(Though not everything works: see my message somewhere below!

Anne-Jan Tuinstra

|||I Download and install "SQLServer2005_SSMSEE.msi" but the server type in this version is "Database Engine" and I can't change it!(It is disabled)|||Any idea ? Please help!