Cannot create an instance of OLE DB provider "IBMDADB2" for linked server

System:Win 2003, SQL Server 2005, Using an AD win account that is not a member of the Admin group on the server.

Error message from Management Studio query window:

Msg 7302, Level 16, State 1, Line 1

Cannot create an instance of OLE DB provider "IBMDADB2" for linked server "Sname".

Event messages associated with this error:

App Event ID: 19036

The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact product support for the OLEDB provider.

Sys Event ID: 10016

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2206CDB0-19C1-11D1-89E0-00C04FD7A829}

to the user domain\user SID (S-1-5-21-126051702-1034962659-2130403006-7826). This security permission can be modified using the Component Services administrative tool.

I’m getting this error message when trying to run an openquery statement through a linked server to DB2. (SELECT * FROM OPENQUERY(Sname, 'SELECT * FROM tablename’))

The linked server has a remote login and password that it uses to connect to DB2.

I found this from another post on how to fix this error:

Expand Component Services - Computers - My Computer - DCOM Config Select MSDAINITIALIZE Right Click properties then security

Under Security - Launch Permission: enable Local Launch and Local Activation for your SQL Service account

Under Security - Access permissions: Allow System: Local Access and Remote Access.

After completing these steps I still get the error message but the events are no longer generated.I’ve also tried different variations of these steps.The only way I can get this to work is to either make the AD user a member of the Admin group on the server or by putting in a user account that has admin rights to the server in the MSDAINITIALIZE properties – Identity Tab – Run this App as this User.

Can someone please tell me the steps that I’m missing?

Additional info:

If I set the providers allowinprocess to 1 with this,

EXEC master.dbo.sp_MSset_oledb_prop N'IBMDADB2', N'AllowInProcess', 1

It responds with this error:

OLE DB provider "IBMDADB2" for linked server "LName" returned message " SQL10007N Message "0" could not be retrieved. Reason code: "2".

".

Msg 7303, Level 16, State 1, Line 1

Cannot initialize the data source object of OLE DB provider "IBMDADB2" for linked server "LName".

Cannot create a connection to data source !!!!!!!

I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg

Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

An error has occurred during report processing.

Cannot create a connection to data source 'datasourcename'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

no it usues whatever account iis is running under.

IUSR_something I think.

if you want use integrated auth you need to use impersonation.

|||ok....then how do incorporate personalization in Reporting Services! I don't see anything on that...I think you're referring to .NET, I'm talking about Reporting Services 2005|||I posted this in the wrong forum by accident..I'll move it to Reporting Services..sorry

Cannot create a connection to data source !!!! SSRS 2005

I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg

Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

An error has occurred during report processing.

Cannot create a connection to data source 'datasourcename'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Are the client, RS, and SQL server all on different machines? If so, then you are probably hitting the double-hop problem. This is a limitation of integrated security in environments which don't support kerberos.

Tudor talks about it a bit in this blog entry:

http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

You might want to check that out and see if the problem described there is what you are experiencing.

|||

No, I have gotten this to work fine for my test server which is the server running both RS and SQL Server 2005. RS and SQL Server 2005 are on the same box. The server I'm trying to connect to now is a different server's DB which is where the datasource is pointing to. So there is no double-hop issue here at least!

So in other words if I change the datasets to use the datasources that piont to ServerA below, my report runs for me ok. If I change the datasets in my report to talk to ServerB, I get the error immediately. The datasets are running stored procs and referencing the data sources for the DB connection in the dataset properties. I am using 3 datasets in my report and around 4 datasources are in my project that are uploaded automatically when I deploy my report to the report serve (TestServerA)

TestServerA - Has RS and SQL Server 2005. When using Datasources that point to this server's stored procs, it works for me at least the other users still have issues though where it's prompting them for a windows username and password

ServerB - a production server running SQL Server 2000 (doesn't have Reporting Services on it, we're just runnign stored procs against it for the datasets) in which the dataset (on TestServerA) is trying to run a stored proc off of ServerB. It stil uses ServerA for Reporting services part...whcih is where I'm getting the error from my own client when trying to run the report from the client in Report Manager

|||Ok, now I tried logging on directly to my TestServerA and ran the report from IE on that server (report Manager) and it works fine. Ok, so how am I getting a double hop issue if I have everything installed on the same server? I don't think hopping is the issue here still!|||scratch my last response...it was working only because my datasets were pointing to the datasources that were pointing to my TestServerA. Once I changed it back to the point where I got the error (for this post) whcih was to chagne teh datasets to point to the datasources that point to ServerB, I still get the error, even when running the report from TestServerA's Report Manager....|||

Here's a diagram to show you what's going on. Keep in mind, if the datasets aren't using datasources that point to ServerB and are using datasources that point to TestServerA, all works fine...it's just when my report is using datasources trying to talk to ServerB.

http://www.webfound.net/diagram.jpg

|||

Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

Thanks,

Tudor

|||

In your second setup (ServerB) you are describing what I would expect to be the symptoms of the double hop problem. You have 3 machines, A->B->C. A is the client machine, B is the machine with reporting services, and C is the machine that has the data you are reporting against. You are trying to pass credentials from machine A all the way to machine C. Unless you have set up your environment to allow kerberos delegation (see the links that I pasted above), then this will fail. If you don't want to (or cannot) enable delegation, then a workaround for you is to store credentials for accessing the datasources in the catalog.

In your 1st scenario (TestServerA), I am not certain why they are getting prompted for credentials. I suspect it is because your test users don't have access to your machine, are they able to connect when providing their credentials?

|||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

,I have missed the same problem once ,the problem is that ur datasource was set ot windows Authentification,(if u pay more attention to ur report'Connection string,u could find the bugs),but ur database has no right for this kind of user,

u could follow this steps to add a user or a group which the user belong to :

1.login in database

2.extend the security node

3.extend the logins node

3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

And there is a skill,if ur user is a member of administrator,and u assign permissions to the other user,by default,this kind of user only is a menber of user,dont have the role of administrator,so if u use the windows Authentification to build connection string for ur report,the user who just have a role of user don't have logins to database,u need to follow the steps above to add the user or the group to Database'logins.

|||Samuel, they definitely already have logins to the database, right down to the permissions of the stored procs being called by the datasets so this is covered! They have read rights as well as datawriter (which isn't really needed). This is why I posted, I have done almost everything.|||

I believe you are running into a couple of problems which are not necessarily related.

When you are prompted for credentials in IE with the standard credentials dialog, it is because IIS did not accept the user's token when IE presented it in response to a 401. This usually means that the user is not a valid user on the target machine. Check your IIS logs for 401s.

The datasource problems are because the user we are trying to access the database with is not allowed access. This can be for any number of reasons, the double-hop issue being a pretty common one when people are trying to pass through Windows credentials.

|||I have a similar problem to FlavorFlave. Our setup:

Machine A : client
Machine B: SSRS 2005
Machine C: SSAS 2000

Running reports from Machine B works, running from from A does not - getting the exact error he specified. Logged on to machine A with a limited user account, onto B/C with full admin rights.

Enabling delegation is not going to be possible on our network. John, i see you say a workaround is to "store credentials for accessing the datasources in the catalog". Not sure what you meant by this.. or where to do this?|||never mind.. ive figured it out :)

stored the credentials securely within the datasource on the report server itself. works now... though its slower to initialise than when the security is integrated.
|||talwar, can you explain the steps you took in detail so hopefully I can do the same...thanks

Cannot create a connection to data source !!!! SSRS 2005

I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg

Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

An error has occurred during report processing.

Cannot create a connection to data source 'datasourcename'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Are the client, RS, and SQL server all on different machines? If so, then you are probably hitting the double-hop problem. This is a limitation of integrated security in environments which don't support kerberos.

Tudor talks about it a bit in this blog entry:

http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

You might want to check that out and see if the problem described there is what you are experiencing.

|||

No, I have gotten this to work fine for my test server which is the server running both RS and SQL Server 2005. RS and SQL Server 2005 are on the same box. The server I'm trying to connect to now is a different server's DB which is where the datasource is pointing to. So there is no double-hop issue here at least!

So in other words if I change the datasets to use the datasources that piont to ServerA below, my report runs for me ok. If I change the datasets in my report to talk to ServerB, I get the error immediately. The datasets are running stored procs and referencing the data sources for the DB connection in the dataset properties. I am using 3 datasets in my report and around 4 datasources are in my project that are uploaded automatically when I deploy my report to the report serve (TestServerA)

TestServerA - Has RS and SQL Server 2005. When using Datasources that point to this server's stored procs, it works for me at least the other users still have issues though where it's prompting them for a windows username and password

ServerB - a production server running SQL Server 2000 (doesn't have Reporting Services on it, we're just runnign stored procs against it for the datasets) in which the dataset (on TestServerA) is trying to run a stored proc off of ServerB. It stil uses ServerA for Reporting services part...whcih is where I'm getting the error from my own client when trying to run the report from the client in Report Manager

|||Ok, now I tried logging on directly to my TestServerA and ran the report from IE on that server (report Manager) and it works fine. Ok, so how am I getting a double hop issue if I have everything installed on the same server? I don't think hopping is the issue here still!|||scratch my last response...it was working only because my datasets were pointing to the datasources that were pointing to my TestServerA. Once I changed it back to the point where I got the error (for this post) whcih was to chagne teh datasets to point to the datasources that point to ServerB, I still get the error, even when running the report from TestServerA's Report Manager....|||

Here's a diagram to show you what's going on. Keep in mind, if the datasets aren't using datasources that point to ServerB and are using datasources that point to TestServerA, all works fine...it's just when my report is using datasources trying to talk to ServerB.

http://www.webfound.net/diagram.jpg

|||

Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

Thanks,

Tudor

|||

In your second setup (ServerB) you are describing what I would expect to be the symptoms of the double hop problem. You have 3 machines, A->B->C. A is the client machine, B is the machine with reporting services, and C is the machine that has the data you are reporting against. You are trying to pass credentials from machine A all the way to machine C. Unless you have set up your environment to allow kerberos delegation (see the links that I pasted above), then this will fail. If you don't want to (or cannot) enable delegation, then a workaround for you is to store credentials for accessing the datasources in the catalog.

In your 1st scenario (TestServerA), I am not certain why they are getting prompted for credentials. I suspect it is because your test users don't have access to your machine, are they able to connect when providing their credentials?

|||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

,I have missed the same problem once ,the problem is that ur datasource was set ot windows Authentification,(if u pay more attention to ur report'Connection string,u could find the bugs),but ur database has no right for this kind of user,

u could follow this steps to add a user or a group which the user belong to :

1.login in database

2.extend the security node

3.extend the logins node

3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

And there is a skill,if ur user is a member of administrator,and u assign permissions to the other user,by default,this kind of user only is a menber of user,dont have the role of administrator,so if u use the windows Authentification to build connection string for ur report,the user who just have a role of user don't have logins to database,u need to follow the steps above to add the user or the group to Database'logins.

|||Samuel, they definitely already have logins to the database, right down to the permissions of the stored procs being called by the datasets so this is covered! They have read rights as well as datawriter (which isn't really needed). This is why I posted, I have done almost everything.|||

I believe you are running into a couple of problems which are not necessarily related.

When you are prompted for credentials in IE with the standard credentials dialog, it is because IIS did not accept the user's token when IE presented it in response to a 401. This usually means that the user is not a valid user on the target machine. Check your IIS logs for 401s.

The datasource problems are because the user we are trying to access the database with is not allowed access. This can be for any number of reasons, the double-hop issue being a pretty common one when people are trying to pass through Windows credentials.

|||I have a similar problem to FlavorFlave. Our setup:

Machine A : client
Machine B: SSRS 2005
Machine C: SSAS 2000

Running reports from Machine B works, running from from A does not - getting the exact error he specified. Logged on to machine A with a limited user account, onto B/C with full admin rights.

Enabling delegation is not going to be possible on our network. John, i see you say a workaround is to "store credentials for accessing the datasources in the catalog". Not sure what you meant by this.. or where to do this?|||never mind.. ive figured it out :)

stored the credentials securely within the datasource on the report server itself. works now... though its slower to initialise than when the security is integrated.
|||talwar, can you explain the steps you took in detail so hopefully I can do the same...thanks

Cannot create a connection to data source !!!! SSRS 2005

I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg

Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

An error has occurred during report processing.

Cannot create a connection to data source 'datasourcename'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Are the client, RS, and SQL server all on different machines? If so, then you are probably hitting the double-hop problem. This is a limitation of integrated security in environments which don't support kerberos.

Tudor talks about it a bit in this blog entry:

http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

You might want to check that out and see if the problem described there is what you are experiencing.

|||

No, I have gotten this to work fine for my test server which is the server running both RS and SQL Server 2005. RS and SQL Server 2005 are on the same box. The server I'm trying to connect to now is a different server's DB which is where the datasource is pointing to. So there is no double-hop issue here at least!

So in other words if I change the datasets to use the datasources that piont to ServerA below, my report runs for me ok. If I change the datasets in my report to talk to ServerB, I get the error immediately. The datasets are running stored procs and referencing the data sources for the DB connection in the dataset properties. I am using 3 datasets in my report and around 4 datasources are in my project that are uploaded automatically when I deploy my report to the report serve (TestServerA)

TestServerA - Has RS and SQL Server 2005. When using Datasources that point to this server's stored procs, it works for me at least the other users still have issues though where it's prompting them for a windows username and password

ServerB - a production server running SQL Server 2000 (doesn't have Reporting Services on it, we're just runnign stored procs against it for the datasets) in which the dataset (on TestServerA) is trying to run a stored proc off of ServerB. It stil uses ServerA for Reporting services part...whcih is where I'm getting the error from my own client when trying to run the report from the client in Report Manager

|||Ok, now I tried logging on directly to my TestServerA and ran the report from IE on that server (report Manager) and it works fine. Ok, so how am I getting a double hop issue if I have everything installed on the same server? I don't think hopping is the issue here still!|||scratch my last response...it was working only because my datasets were pointing to the datasources that were pointing to my TestServerA. Once I changed it back to the point where I got the error (for this post) whcih was to chagne teh datasets to point to the datasources that point to ServerB, I still get the error, even when running the report from TestServerA's Report Manager....|||

Here's a diagram to show you what's going on. Keep in mind, if the datasets aren't using datasources that point to ServerB and are using datasources that point to TestServerA, all works fine...it's just when my report is using datasources trying to talk to ServerB.

http://www.webfound.net/diagram.jpg

|||

Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

Thanks,

Tudor

|||

In your second setup (ServerB) you are describing what I would expect to be the symptoms of the double hop problem. You have 3 machines, A->B->C. A is the client machine, B is the machine with reporting services, and C is the machine that has the data you are reporting against. You are trying to pass credentials from machine A all the way to machine C. Unless you have set up your environment to allow kerberos delegation (see the links that I pasted above), then this will fail. If you don't want to (or cannot) enable delegation, then a workaround for you is to store credentials for accessing the datasources in the catalog.

In your 1st scenario (TestServerA), I am not certain why they are getting prompted for credentials. I suspect it is because your test users don't have access to your machine, are they able to connect when providing their credentials?

|||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

,I have missed the same problem once ,the problem is that ur datasource was set ot windows Authentification,(if u pay more attention to ur report'Connection string,u could find the bugs),but ur database has no right for this kind of user,

u could follow this steps to add a user or a group which the user belong to :

1.login in database

2.extend the security node

3.extend the logins node

3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

And there is a skill,if ur user is a member of administrator,and u assign permissions to the other user,by default,this kind of user only is a menber of user,dont have the role of administrator,so if u use the windows Authentification to build connection string for ur report,the user who just have a role of user don't have logins to database,u need to follow the steps above to add the user or the group to Database'logins.

|||Samuel, they definitely already have logins to the database, right down to the permissions of the stored procs being called by the datasets so this is covered! They have read rights as well as datawriter (which isn't really needed). This is why I posted, I have done almost everything.|||

I believe you are running into a couple of problems which are not necessarily related.

When you are prompted for credentials in IE with the standard credentials dialog, it is because IIS did not accept the user's token when IE presented it in response to a 401. This usually means that the user is not a valid user on the target machine. Check your IIS logs for 401s.

The datasource problems are because the user we are trying to access the database with is not allowed access. This can be for any number of reasons, the double-hop issue being a pretty common one when people are trying to pass through Windows credentials.

|||

I have a similar problem to FlavorFlave. Our setup:

Machine A : client
Machine B: SSRS 2005
Machine C: SSAS 2000

Running

reports from Machine B works, running from from A does not - getting the

exact error he specified. Logged on to machine A with a limited user

account, onto B/C with full admin rights.

Enabling delegation is

not going to be possible on our network. John, i see you say a

workaround is to "store credentials for accessing the datasources in

the catalog". Not sure what you meant by this.. or where to do this?|||never mind.. ive figured it out :)

stored the credentials securely within the datasource on the report server itself. works now... though its slower to initialise than when the security is integrated.|||talwar, can you explain the steps you took in detail so hopefully I can do the same...thanks

Cannot create a connection to data source !!!! SSRS 2005

I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg

Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

An error has occurred during report processing.

Cannot create a connection to data source 'datasourcename'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Are the client, RS, and SQL server all on different machines? If so, then you are probably hitting the double-hop problem. This is a limitation of integrated security in environments which don't support kerberos.

Tudor talks about it a bit in this blog entry:

http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

You might want to check that out and see if the problem described there is what you are experiencing.

|||

No, I have gotten this to work fine for my test server which is the server running both RS and SQL Server 2005. RS and SQL Server 2005 are on the same box. The server I'm trying to connect to now is a different server's DB which is where the datasource is pointing to. So there is no double-hop issue here at least!

So in other words if I change the datasets to use the datasources that piont to ServerA below, my report runs for me ok. If I change the datasets in my report to talk to ServerB, I get the error immediately. The datasets are running stored procs and referencing the data sources for the DB connection in the dataset properties. I am using 3 datasets in my report and around 4 datasources are in my project that are uploaded automatically when I deploy my report to the report serve (TestServerA)

TestServerA - Has RS and SQL Server 2005. When using Datasources that point to this server's stored procs, it works for me at least the other users still have issues though where it's prompting them for a windows username and password

ServerB - a production server running SQL Server 2000 (doesn't have Reporting Services on it, we're just runnign stored procs against it for the datasets) in which the dataset (on TestServerA) is trying to run a stored proc off of ServerB. It stil uses ServerA for Reporting services part...whcih is where I'm getting the error from my own client when trying to run the report from the client in Report Manager

|||Ok, now I tried logging on directly to my TestServerA and ran the report from IE on that server (report Manager) and it works fine. Ok, so how am I getting a double hop issue if I have everything installed on the same server? I don't think hopping is the issue here still!|||scratch my last response...it was working only because my datasets were pointing to the datasources that were pointing to my TestServerA. Once I changed it back to the point where I got the error (for this post) whcih was to chagne teh datasets to point to the datasources that point to ServerB, I still get the error, even when running the report from TestServerA's Report Manager....|||

Here's a diagram to show you what's going on. Keep in mind, if the datasets aren't using datasources that point to ServerB and are using datasources that point to TestServerA, all works fine...it's just when my report is using datasources trying to talk to ServerB.

http://www.webfound.net/diagram.jpg

|||

Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

Thanks,

Tudor

|||

In your second setup (ServerB) you are describing what I would expect to be the symptoms of the double hop problem. You have 3 machines, A->B->C. A is the client machine, B is the machine with reporting services, and C is the machine that has the data you are reporting against. You are trying to pass credentials from machine A all the way to machine C. Unless you have set up your environment to allow kerberos delegation (see the links that I pasted above), then this will fail. If you don't want to (or cannot) enable delegation, then a workaround for you is to store credentials for accessing the datasources in the catalog.

In your 1st scenario (TestServerA), I am not certain why they are getting prompted for credentials. I suspect it is because your test users don't have access to your machine, are they able to connect when providing their credentials?

|||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

,I have missed the same problem once ,the problem is that ur datasource was set ot windows Authentification,(if u pay more attention to ur report'Connection string,u could find the bugs),but ur database has no right for this kind of user,

u could follow this steps to add a user or a group which the user belong to :

1.login in database

2.extend the security node

3.extend the logins node

3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

And there is a skill,if ur user is a member of administrator,and u assign permissions to the other user,by default,this kind of user only is a menber of user,dont have the role of administrator,so if u use the windows Authentification to build connection string for ur report,the user who just have a role of user don't have logins to database,u need to follow the steps above to add the user or the group to Database'logins.

|||Samuel, they definitely already have logins to the database, right down to the permissions of the stored procs being called by the datasets so this is covered! They have read rights as well as datawriter (which isn't really needed). This is why I posted, I have done almost everything.|||

I believe you are running into a couple of problems which are not necessarily related.

When you are prompted for credentials in IE with the standard credentials dialog, it is because IIS did not accept the user's token when IE presented it in response to a 401. This usually means that the user is not a valid user on the target machine. Check your IIS logs for 401s.

The datasource problems are because the user we are trying to access the database with is not allowed access. This can be for any number of reasons, the double-hop issue being a pretty common one when people are trying to pass through Windows credentials.

|||I have a similar problem to FlavorFlave. Our setup:

Machine A : client
Machine B: SSRS 2005
Machine C: SSAS 2000

Running reports from Machine B works, running from from A does not - getting the exact error he specified. Logged on to machine A with a limited user account, onto B/C with full admin rights.

Enabling delegation is not going to be possible on our network. John, i see you say a workaround is to "store credentials for accessing the datasources in the catalog". Not sure what you meant by this.. or where to do this?|||never mind.. ive figured it out :)

stored the credentials securely within the datasource on the report server itself. works now... though its slower to initialise than when the security is integrated.
|||talwar, can you explain the steps you took in detail so hopefully I can do the same...thanks

Cannot create a connection to data source - SSRS 2005

I cannot get this error resolve either for myself or any users, and I'm
actually part of the Admin group! Furthermore, a user with whom I'm
tring allow to view this report keeps getting prompted for their
windows username and password. I thought that since this datasource
was set to Windows Authentification that it would just pass it through?
I'm pulling my hair out at this point:
Screen Shots:
http://www.webfound.net/datasource_connection.jpg
http://www.webfound.net/datasource_connection2.jpg
http://www.webfound.net/datasource_connection3.jpg
Also As far as I know, I've given proper permissions to the right
logins and right users on my SQL Databases and related stored procs
that the datasets (not datasource) run
An error has occurred during report processing.
Cannot create a connection to data source 'datasourcename'.
For more information about this error navigate to the report server on
the local server machine, or enable remote errorsWith windows authentication issue, there is a parameter in Internet
Explorer which can cause this. Goto Tools|Internet options|Security
then I think the problem is likely to be the Intranet Zone, but
depending on your setup it could be one of the others too. Anyway,
select the Intranet Zone then custom, scroll to the bottom and you
should see User Authentication, you've probably got it set to Prompt on
this particular PC. This seems to be the default on Windows 2000
machines.
You may also find Active Directory policies can override this setting,
when they reboot.
On the data source issue:
A bit of a long shot this, but try removing the hyphens '-' from the
datasource names. It's never a good idea to put these sorts of
characters in SQL related stuff (this is the voice of experience!).
Also, can you run it from BIDS? If you can, then it would suggest the
server you are deploying to cannot see the server containing the actual
datasource.
Also, it may be worth checking the datasource "file" on the report
server. Remember, when you deploy a report it won't overwrite a
datasource if it already exists, and if it's been changed on the server
in any way the report will use that instead. Having said that, viewing
your screenshots it doesn't look like this is the case.
My hunch is your report server can't gain access to the server with the
data. Maybe describing the server setup a bit more may shed some more
light on the issue.
Hope some of this helps.
Cheers
Chris
dba123 wrote:
> I cannot get this error resolve either for myself or any users, and
> I'm actually part of the Admin group! Furthermore, a user with whom
> I'm tring allow to view this report keeps getting prompted for their
> windows username and password. I thought that since this datasource
> was set to Windows Authentification that it would just pass it
> through?
> I'm pulling my hair out at this point:
> Screen Shots:
> http://www.webfound.net/datasource_connection.jpg
> http://www.webfound.net/datasource_connection2.jpg
> http://www.webfound.net/datasource_connection3.jpg
>
> Also As far as I know, I've given proper permissions to the right
> logins and right users on my SQL Databases and related stored procs
> that the datasets (not datasource) run
> An error has occurred during report processing.
> Cannot create a connection to data source 'datasourcename'.
> For more information about this error navigate to the report server on
> the local server machine, or enable remote errors

Cannot connect to AdventureWorks db

All,

I am running SQL05 Dev with AdventureWorks on my desktop with local admin rights. I also have it configured to connect locally since it's a DEV version of SQL.

When I use either of the connection strings below I get the error message at the end of this post.

Thanks,

>Scott

Here are the strings:

Data source=(local); initial catalog=AdventureWorks or Data source=(SQLDEV05); initial catalog=AdventureWorks

Here is the error message:

TITLE: Microsoft Report Designer

A connection cannot be made to the database.
Set and test the connection string.

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

Although it should work if you are connecting locally, you may want to try enabling TCP/IP and Named Pipes connections (which are off by default) just to see if that solves the problem. You can do this through SQL Server Surface Area Configuration tool. Let us know if that works, if not, it may be a different issue.

|||

Hi:

According to the connection string you posted, please try the following changes and see if any of them works for you:

Origional: "Data source=(local); initial catalog=AdventureWorks"

Modified: "Data source=(local); initial catalog=AdventureWorks; Integrated Security=true"

or

Origional: "Data source=(SQLDEV05); initial catalog=AdventureWorks;"

Modified: "Data source=SQLDEV05; initial catalog=AdventureWorks; Integrated Security=true"

For more information about connection string, please use the following link for references.

http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring.aspx

Hope this helps. :-)

Thanks.

Cannot Connect to Analysis Server-not a member of OLAP Admin

I have set up the the Analysis Service to log on as DOMAIN\administrator.
I have added DOMAIN\administrator as a member of OLAP Adminitration
I initially logged in as DOMAIN\administrator.
Upon trying to connect in Analysis Server, I get the error messge Cannot
connect to SERVER registry or you are not a member of the OLAP
AdministratorGroup
What gives? How do I resolve this?
Are you running the latest service pack for Analysis Services?
Kevin E.
"Diane" <Diane@.discussions.microsoft.com> wrote in message
news:B2888652-78F9-4F32-88B2-F21C03A48A65@.microsoft.com...
>I have set up the the Analysis Service to log on as DOMAIN\administrator.
> I have added DOMAIN\administrator as a member of OLAP Adminitration
> I initially logged in as DOMAIN\administrator.
> Upon trying to connect in Analysis Server, I get the error messge Cannot
> connect to SERVER registry or you are not a member of the OLAP
> AdministratorGroup
> What gives? How do I resolve this?
|||Yes, I am.
"Diane" wrote:

> I have set up the the Analysis Service to log on as DOMAIN\administrator.
> I have added DOMAIN\administrator as a member of OLAP Adminitration
> I initially logged in as DOMAIN\administrator.
> Upon trying to connect in Analysis Server, I get the error messge Cannot
> connect to SERVER registry or you are not a member of the OLAP
> AdministratorGroup
> What gives? How do I resolve this?
|||We had the same problem on some of our installations. Seems like after we
rebooted and then tried to connect it worked fine. Might of had something to
do with MSSQLServerOLAPService not being started until after reboot. Just a
thought.
Kevin
"Diane" <Diane@.discussions.microsoft.com> wrote in message
news:904C6394-D5AE-4BC4-8A45-39B58AA742BD@.microsoft.com...[vbcol=seagreen]
> Yes, I am.
> "Diane" wrote:

Cannot connect to 2000 analysis services from SSMS for 2005

I am not able to connect to SQL Server 2000 analysis services from the SSMS for SQL Server 2005.

I have both domain admin and sql server 2000 admin permissions for the sql server 2000 box in question.

The error message I get is as follows:

A connection cannot be made. Ensure the server is running.

Microsoft.AnalysisServices.AdomdClient

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

This is a Standard Edition install of both SQL Server 2005 and of SQL Server 2000 on separate servers.

I can connect to database engine just fine.

Any ideas about what permissions I need that I've screwed up on setting?

Thanks

S Wells

I do not believe you can connect to AS 2000 from Management Studio 2005. I think you still need the Analysis Services 2000 Manager.

Hope I'm wrong or this is fixed in SP1.

|||

I hope you are wrong too because what I need to do is to migrate the SQL server 2000 Analysis services to 2005 while leaving the 2000 intact for current production.

Thanks,

S Wells

|||

Well, what I settled for doing was to migrate the analysis services from the SQL Server 2000 instance to a SQL Server 2005 instance. It did not come over in working order (there were some issues with dimension names being changed) and now the cubes cannot be processed. Since I cannot connect to the old SQL Server 2000 analysis services using analysis manager for SQL Server 2000 on the server where SQL Server 2000 is installed (something is hosed up) and since I cannot install SQL Server 2000 Analysis services manager on my development machine while SQL Server 2005 Analysis Services is installed (via BIDS and SSMS) I can't examine the old Analysis services set up to see exactly what is going on.

So, I'm back to my original issue. Does anyone know what could cause me to get a message telling me that Analysis Services Manager on the SQL Server 2000 server cannot access the registry or that I'm not part of the OLAP administrators group?

I am in the OLAD administrators group, I am a domain admin, and I am admin on the SQL Server 2000 server itself. SQL server 2000 is at Service Pack 4. The machine it is on is running Windows Server 2003 Standard Edition at Service Pack 1.

|||

Hi Swells and others,

Did you ever resolve this issue? I am also trying to connect to Analysis Services 2000 via Business Scorecard Manager 2005 and also SQL Server Management Studio. I cannot connect via either though.

I am not getting an error message from BSM. I am simply getting a blank "Database Name" list after entering the "Server Name" with creating a new datasource.

The message I am getting from MSSMS is telling me that "the server actively refused the connection".

I can connect to my SQL2K database via the "Database Engine" connection in SQL2K5, but cannot connect via an ODBC data source in BSM.

SQL2K SP4 and AS SP4 arei nstalled on an XP machine with ADOMD.Net, MSXML4 and SQLXML 3.0.

My domain account is a member of domain admins and also a member of administrators and OLAP admins on the XP machine.

SQL 2K5 is installed on a Win2K3 virtual server with BSM Server.

Both machines are members of our domain.

Please help me resolve this problem :)

Jeremy

|||

hello,

connecting to AS2000 is not supported in SSMS.

hope this clarifies.

|||

Hi all,

Then how we will migrate AS2000 database to AS2005?

Regards,

Vinod

|||

Hi Swell,

I am also facing the same issue.. Kindly help me to sort out this issue.

Send me mail to chris_asir@.hotmail.com

regards,

Anand

|||

Gentlemen,

For step-by-step example, wherein MSSQL2k a sample database is migrated to MSSQL2k5, see my article at:

http://www.databasejournal.com/features/mssql/article.php/3564291

In this article, I address different migration scenarios with regard to MSSQL server versions (side-by-side, “straight upgrade,” and migration of existing Analysis Services 2000 databases from within the SQL Server 2005 Analysis Services platform), mentioning the fact that this provides a host of flexible opportunities for staging partial and full cutovers, simultaneous operations of different versions within other strategies, and so forth.

The approach I take in the article is, of course, a simple one, of many possible approaches. However, this will probably be useful to you in that this procedure leaves the original Analysis Services 2000 databases intact as Analysis Services 2000 databases, working with automatically created copies of the original databases in reconstructing them on the desired instance of Analysis Services 2005.

Good Luck!

Bill

William E. Pearson III
CPA, CMA, CIA, MCSE, MCDBA
Island Technologies Inc.
931 Monroe Drive
Suite 102-321
Atlanta, GA 30308

404.872.5972 Office

wep3@.islandtechnologies.com

wep3@.ssas-architect.com
www.ssas-architect.com
-- -- --

Publisher Sites:

http://www.databasejournal.com/article.php/1459531

http://www.sql-server-performance.com/bill_pearson.asp

http://www.informit.com/authors/bio.asp?a=862acd62-4662-49ae-879d-541c8b4d656f

http://www.2000trainers.com/section.aspx?sectionID=17

Cannot connect to 2000 analysis services from SSMS for 2005

I am not able to connect to SQL Server 2000 analysis services from the SSMS for SQL Server 2005.

I have both domain admin and sql server 2000 admin permissions for the sql server 2000 box in question.

The error message I get is as follows:

A connection cannot be made. Ensure the server is running.

Microsoft.AnalysisServices.AdomdClient

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

This is a Standard Edition install of both SQL Server 2005 and of SQL Server 2000 on separate servers.

I can connect to database engine just fine.

Any ideas about what permissions I need that I've screwed up on setting?

Thanks

S Wells

I do not believe you can connect to AS 2000 from Management Studio 2005. I think you still need the Analysis Services 2000 Manager.

Hope I'm wrong or this is fixed in SP1.

|||

I hope you are wrong too because what I need to do is to migrate the SQL server 2000 Analysis services to 2005 while leaving the 2000 intact for current production.

Thanks,

S Wells

|||

Well, what I settled for doing was to migrate the analysis services from the SQL Server 2000 instance to a SQL Server 2005 instance. It did not come over in working order (there were some issues with dimension names being changed) and now the cubes cannot be processed. Since I cannot connect to the old SQL Server 2000 analysis services using analysis manager for SQL Server 2000 on the server where SQL Server 2000 is installed (something is hosed up) and since I cannot install SQL Server 2000 Analysis services manager on my development machine while SQL Server 2005 Analysis Services is installed (via BIDS and SSMS) I can't examine the old Analysis services set up to see exactly what is going on.

So, I'm back to my original issue. Does anyone know what could cause me to get a message telling me that Analysis Services Manager on the SQL Server 2000 server cannot access the registry or that I'm not part of the OLAP administrators group?

I am in the OLAD administrators group, I am a domain admin, and I am admin on the SQL Server 2000 server itself. SQL server 2000 is at Service Pack 4. The machine it is on is running Windows Server 2003 Standard Edition at Service Pack 1.

|||

Hi Swells and others,

Did you ever resolve this issue? I am also trying to connect to Analysis Services 2000 via Business Scorecard Manager 2005 and also SQL Server Management Studio. I cannot connect via either though.

I am not getting an error message from BSM. I am simply getting a blank "Database Name" list after entering the "Server Name" with creating a new datasource.

The message I am getting from MSSMS is telling me that "the server actively refused the connection".

I can connect to my SQL2K database via the "Database Engine" connection in SQL2K5, but cannot connect via an ODBC data source in BSM.

SQL2K SP4 and AS SP4 arei nstalled on an XP machine with ADOMD.Net, MSXML4 and SQLXML 3.0.

My domain account is a member of domain admins and also a member of administrators and OLAP admins on the XP machine.

SQL 2K5 is installed on a Win2K3 virtual server with BSM Server.

Both machines are members of our domain.

Please help me resolve this problem :)

Jeremy

|||

hello,

connecting to AS2000 is not supported in SSMS.

hope this clarifies.

|||

Hi all,

Then how we will migrate AS2000 database to AS2005?

Regards,

Vinod

|||

Hi Swell,

I am also facing the same issue.. Kindly help me to sort out this issue.

Send me mail to chris_asir@.hotmail.com

regards,

Anand

|||

Gentlemen,

For step-by-step example, wherein MSSQL2k a sample database is migrated to MSSQL2k5, see my article at:

http://www.databasejournal.com/features/mssql/article.php/3564291

In this article, I address different migration scenarios with regard to MSSQL server versions (side-by-side, “straight upgrade,” and migration of existing Analysis Services 2000 databases from within the SQL Server 2005 Analysis Services platform), mentioning the fact that this provides a host of flexible opportunities for staging partial and full cutovers, simultaneous operations of different versions within other strategies, and so forth.

The approach I take in the article is, of course, a simple one, of many possible approaches. However, this will probably be useful to you in that this procedure leaves the original Analysis Services 2000 databases intact as Analysis Services 2000 databases, working with automatically created copies of the original databases in reconstructing them on the desired instance of Analysis Services 2005.

Good Luck!

Bill

William E. Pearson III
CPA, CMA, CIA, MCSE, MCDBA
Island Technologies Inc.
931 Monroe Drive
Suite 102-321
Atlanta, GA 30308

404.872.5972 Office

wep3@.islandtechnologies.com

wep3@.ssas-architect.com
www.ssas-architect.com
-- -- --

Publisher Sites:

http://www.databasejournal.com/article.php/1459531

http://www.sql-server-performance.com/bill_pearson.asp

http://www.informit.com/authors/bio.asp?a=862acd62-4662-49ae-879d-541c8b4d656f

http://www.2000trainers.com/section.aspx?sectionID=17

Cannot connect to 2000 analysis services from SSMS for 2005

I am not able to connect to SQL Server 2000 analysis services from the SSMS for SQL Server 2005.

I have both domain admin and sql server 2000 admin permissions for the sql server 2000 box in question.

The error message I get is as follows:

A connection cannot be made. Ensure the server is running.

Microsoft.AnalysisServices.AdomdClient

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

This is a Standard Edition install of both SQL Server 2005 and of SQL Server 2000 on separate servers.

I can connect to database engine just fine.

Any ideas about what permissions I need that I've screwed up on setting?

Thanks

S Wells

I do not believe you can connect to AS 2000 from Management Studio 2005. I think you still need the Analysis Services 2000 Manager.

Hope I'm wrong or this is fixed in SP1.

|||

I hope you are wrong too because what I need to do is to migrate the SQL server 2000 Analysis services to 2005 while leaving the 2000 intact for current production.

Thanks,

S Wells

|||

Well, what I settled for doing was to migrate the analysis services from the SQL Server 2000 instance to a SQL Server 2005 instance. It did not come over in working order (there were some issues with dimension names being changed) and now the cubes cannot be processed. Since I cannot connect to the old SQL Server 2000 analysis services using analysis manager for SQL Server 2000 on the server where SQL Server 2000 is installed (something is hosed up) and since I cannot install SQL Server 2000 Analysis services manager on my development machine while SQL Server 2005 Analysis Services is installed (via BIDS and SSMS) I can't examine the old Analysis services set up to see exactly what is going on.

So, I'm back to my original issue. Does anyone know what could cause me to get a message telling me that Analysis Services Manager on the SQL Server 2000 server cannot access the registry or that I'm not part of the OLAP administrators group?

I am in the OLAD administrators group, I am a domain admin, and I am admin on the SQL Server 2000 server itself. SQL server 2000 is at Service Pack 4. The machine it is on is running Windows Server 2003 Standard Edition at Service Pack 1.

|||

Hi Swells and others,

Did you ever resolve this issue? I am also trying to connect to Analysis Services 2000 via Business Scorecard Manager 2005 and also SQL Server Management Studio. I cannot connect via either though.

I am not getting an error message from BSM. I am simply getting a blank "Database Name" list after entering the "Server Name" with creating a new datasource.

The message I am getting from MSSMS is telling me that "the server actively refused the connection".

I can connect to my SQL2K database via the "Database Engine" connection in SQL2K5, but cannot connect via an ODBC data source in BSM.

SQL2K SP4 and AS SP4 arei nstalled on an XP machine with ADOMD.Net, MSXML4 and SQLXML 3.0.

My domain account is a member of domain admins and also a member of administrators and OLAP admins on the XP machine.

SQL 2K5 is installed on a Win2K3 virtual server with BSM Server.

Both machines are members of our domain.

Please help me resolve this problem :)

Jeremy

|||

hello,

connecting to AS2000 is not supported in SSMS.

hope this clarifies.

|||

Hi all,

Then how we will migrate AS2000 database to AS2005?

Regards,

Vinod

|||

Hi Swell,

I am also facing the same issue.. Kindly help me to sort out this issue.

Send me mail to chris_asir@.hotmail.com

regards,

Anand

|||

Gentlemen,

For step-by-step example, wherein MSSQL2k a sample database is migrated to MSSQL2k5, see my article at:

http://www.databasejournal.com/features/mssql/article.php/3564291

In this article, I address different migration scenarios with regard to MSSQL server versions (side-by-side, “straight upgrade,” and migration of existing Analysis Services 2000 databases from within the SQL Server 2005 Analysis Services platform), mentioning the fact that this provides a host of flexible opportunities for staging partial and full cutovers, simultaneous operations of different versions within other strategies, and so forth.

The approach I take in the article is, of course, a simple one, of many possible approaches. However, this will probably be useful to you in that this procedure leaves the original Analysis Services 2000 databases intact as Analysis Services 2000 databases, working with automatically created copies of the original databases in reconstructing them on the desired instance of Analysis Services 2005.

Good Luck!

Bill

William E. Pearson III
CPA, CMA, CIA, MCSE, MCDBA
Island Technologies Inc.
931 Monroe Drive
Suite 102-321
Atlanta, GA 30308

404.872.5972 Office

wep3@.islandtechnologies.com

wep3@.ssas-architect.com
www.ssas-architect.com
-- -- --

Publisher Sites:

http://www.databasejournal.com/article.php/1459531

http://www.sql-server-performance.com/bill_pearson.asp

http://www.informit.com/authors/bio.asp?a=862acd62-4662-49ae-879d-541c8b4d656f

http://www.2000trainers.com/section.aspx?sectionID=17

Cannot connect to 2000 analysis services from SSMS for 2005

I am not able to connect to SQL Server 2000 analysis services from the SSMS for SQL Server 2005.

I have both domain admin and sql server 2000 admin permissions for the sql server 2000 box in question.

The error message I get is as follows:

A connection cannot be made. Ensure the server is running.

Microsoft.AnalysisServices.AdomdClient

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

This is a Standard Edition install of both SQL Server 2005 and of SQL Server 2000 on separate servers.

I can connect to database engine just fine.

Any ideas about what permissions I need that I've screwed up on setting?

Thanks

S Wells

I do not believe you can connect to AS 2000 from Management Studio 2005. I think you still need the Analysis Services 2000 Manager.

Hope I'm wrong or this is fixed in SP1.

|||

I hope you are wrong too because what I need to do is to migrate the SQL server 2000 Analysis services to 2005 while leaving the 2000 intact for current production.

Thanks,

S Wells

|||

Well, what I settled for doing was to migrate the analysis services from the SQL Server 2000 instance to a SQL Server 2005 instance. It did not come over in working order (there were some issues with dimension names being changed) and now the cubes cannot be processed. Since I cannot connect to the old SQL Server 2000 analysis services using analysis manager for SQL Server 2000 on the server where SQL Server 2000 is installed (something is hosed up) and since I cannot install SQL Server 2000 Analysis services manager on my development machine while SQL Server 2005 Analysis Services is installed (via BIDS and SSMS) I can't examine the old Analysis services set up to see exactly what is going on.

So, I'm back to my original issue. Does anyone know what could cause me to get a message telling me that Analysis Services Manager on the SQL Server 2000 server cannot access the registry or that I'm not part of the OLAP administrators group?

I am in the OLAD administrators group, I am a domain admin, and I am admin on the SQL Server 2000 server itself. SQL server 2000 is at Service Pack 4. The machine it is on is running Windows Server 2003 Standard Edition at Service Pack 1.

|||

Hi Swells and others,

Did you ever resolve this issue? I am also trying to connect to Analysis Services 2000 via Business Scorecard Manager 2005 and also SQL Server Management Studio. I cannot connect via either though.

I am not getting an error message from BSM. I am simply getting a blank "Database Name" list after entering the "Server Name" with creating a new datasource.

The message I am getting from MSSMS is telling me that "the server actively refused the connection".

I can connect to my SQL2K database via the "Database Engine" connection in SQL2K5, but cannot connect via an ODBC data source in BSM.

SQL2K SP4 and AS SP4 arei nstalled on an XP machine with ADOMD.Net, MSXML4 and SQLXML 3.0.

My domain account is a member of domain admins and also a member of administrators and OLAP admins on the XP machine.

SQL 2K5 is installed on a Win2K3 virtual server with BSM Server.

Both machines are members of our domain.

Please help me resolve this problem :)

Jeremy

|||

hello,

connecting to AS2000 is not supported in SSMS.

hope this clarifies.

|||

Hi all,

Then how we will migrate AS2000 database to AS2005?

Regards,

Vinod

|||

Hi Swell,

I am also facing the same issue.. Kindly help me to sort out this issue.

Send me mail to chris_asir@.hotmail.com

regards,

Anand

|||

Gentlemen,

For step-by-step example, wherein MSSQL2k a sample database is migrated to MSSQL2k5, see my article at:

http://www.databasejournal.com/features/mssql/article.php/3564291

In this article, I address different migration scenarios with regard to MSSQL server versions (side-by-side, “straight upgrade,” and migration of existing Analysis Services 2000 databases from within the SQL Server 2005 Analysis Services platform), mentioning the fact that this provides a host of flexible opportunities for staging partial and full cutovers, simultaneous operations of different versions within other strategies, and so forth.

The approach I take in the article is, of course, a simple one, of many possible approaches. However, this will probably be useful to you in that this procedure leaves the original Analysis Services 2000 databases intact as Analysis Services 2000 databases, working with automatically created copies of the original databases in reconstructing them on the desired instance of Analysis Services 2005.

Good Luck!

Bill

William E. Pearson III
CPA, CMA, CIA, MCSE, MCDBA
Island Technologies Inc.
931 Monroe Drive
Suite 102-321
Atlanta, GA 30308

404.872.5972 Office

wep3@.islandtechnologies.com

wep3@.ssas-architect.com
www.ssas-architect.com
-- -- --

Publisher Sites:

http://www.databasejournal.com/article.php/1459531

http://www.sql-server-performance.com/bill_pearson.asp

http://www.informit.com/authors/bio.asp?a=862acd62-4662-49ae-879d-541c8b4d656f

http://www.2000trainers.com/section.aspx?sectionID=17