Datasource = SQL 2000 sp2 (Cross-Database-Ownership Chaining?)

We have a report in RS 2005, data source uses Windows Integrated Security,
Initial Catalog is the database where the stored procedure is. The stored
procedure selects data from a different database on the server. This server
is running SQL Server 200 sp2 (so pre-Cross-Database-Ownership Chaining
option). The users can execute the stored procedure fine so it does not seem
to be a permissions issue to the data. The Report runs fine FROM the Report
Server. But, if I try to run the report from a different machine, I get:
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DataSourceNameIsHere'.
(rsErrorOpeningConnection)
For more information about this error navigate to the report server on the
local server machine, or enable remote errors
The report also runs fine if we don't use Windows Integrated Security. The
report runs fine if the datasource (both databases) are on SQL2000 sp3. Is
there anything that we can do to get this working on SQL2000 sp2? I'm not
sure that all systems on this server are supported on sp3 (3a or 4). It hosts
several databases from purchased products.I found this in the Reporting Services Log:
ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'DataSourceNameIsHere'., ;
Info:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'DataSourceNameIsHere'. -->
System.Data.SqlClient.SqlException: Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
Michelle
"Michelle" wrote:
> We have a report in RS 2005, data source uses Windows Integrated Security,
> Initial Catalog is the database where the stored procedure is. The stored
> procedure selects data from a different database on the server. This server
> is running SQL Server 200 sp2 (so pre-Cross-Database-Ownership Chaining
> option). The users can execute the stored procedure fine so it does not seem
> to be a permissions issue to the data. The Report runs fine FROM the Report
> Server. But, if I try to run the report from a different machine, I get:
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot create a connection to data source 'DataSourceNameIsHere'.
> (rsErrorOpeningConnection)
> For more information about this error navigate to the report server on the
> local server machine, or enable remote errors
> The report also runs fine if we don't use Windows Integrated Security. The
> report runs fine if the datasource (both databases) are on SQL2000 sp3. Is
> there anything that we can do to get this working on SQL2000 sp2? I'm not
> sure that all systems on this server are supported on sp3 (3a or 4). It hosts
> several databases from purchased products.sql

Datasource = SQL 2000 sp2 (Cross-Database-Ownership Chaining?)

We have a report in RS 2005, data source uses Windows Integrated

Security, Initial Catalog is the database where the stored procedure

is. The stored procedure selects data from a different database on the

server. This server is running SQL Server 200 sp2 (so

pre-Cross-Database-Ownership Chaining option). The users can execute

the stored procedure fine so it does not seem to be a permissions issue

to the data. The Report runs fine FROM the Report Server. But, if I try

to run the report from a different machine, I get:

An error has occurred during report processing. (rsProcessingAborted)

Cannot create a connection to data source 'DataSourceNameIsHere'. (rsErrorOpeningConnection)

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

The report also runs fine if we don't use Windows Integrated Security.

The report runs fine if the datasource (both databases) are on SQL2000

sp3. Is there anything that we can do to get this working on SQL2000

sp2? I'm not sure that all systems on this server are supported on sp3

(3a or 4). It hosts several databases from purchased products.I found this in the Reporting Services Log:

ERROR: Throwing

Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:

Cannot create a connection to data source 'DataSourceNameIsHere'., ;

Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'DataSourceNameIsHere'. > System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Michelle

Datasource = SQL 2000 sp2 (Cross-Database-Ownership Chaining?)

We have a report in RS 2005, data source uses Windows Integrated

Security, Initial Catalog is the database where the stored procedure

is. The stored procedure selects data from a different database on the

server. This server is running SQL Server 200 sp2 (so

pre-Cross-Database-Ownership Chaining option). The users can execute

the stored procedure fine so it does not seem to be a permissions issue

to the data. The Report runs fine FROM the Report Server. But, if I try

to run the report from a different machine, I get:

An error has occurred during report processing. (rsProcessingAborted)

Cannot create a connection to data source 'DataSourceNameIsHere'. (rsErrorOpeningConnection)

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

The report also runs fine if we don't use Windows Integrated Security.

The report runs fine if the datasource (both databases) are on SQL2000

sp3. Is there anything that we can do to get this working on SQL2000

sp2? I'm not sure that all systems on this server are supported on sp3

(3a or 4). It hosts several databases from purchased products.I found this in the Reporting Services Log:

ERROR: Throwing

Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:

Cannot create a connection to data source 'DataSourceNameIsHere'., ;

Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'DataSourceNameIsHere'. > System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Michelle

Databases with simple recovery is NOT excluded when backing up logs

SQL 2005 SP2:
I have several Sharepoint databases, all in full recovery mode except the
large search database which I want to run in simple mode because of the
large amount of transactions and because data recovery is not needed.
The back up log task in SQL Server Managment Studio is said to automatically
exclude databases in simple recovery mode, but it doesen't - anyone having a
workaround?
Other users reported that this problem was introduced in SP2, see
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1336939&SiteID=17
Here's how I reproduce the error:
When I edit a maintenance plan which backs up transaction logs, I can select
"Database(s)":
At the top of the window it says after the yellow exclamation mark:
"Databases with simple recovery will be excluded". Here I select "All user
databases". (I want to use "All user databases" so that any Sharepoint
databases created in the future are automatically included in this task.)
Back at the "Back up Database Task", when using the button "View T-SQL" i
see that the database in simple mode is not included - as expected.
But when the task is run, it fails. That is, it does what it is expected
to - it backs up all logs except from the database in simple mode, but it
returns an error; where I expected it to run with out error.
When looking in the job log in MSSQL\LOG, it shows that the reason of the
error is that it tried to backup the log from the database in simple
recovery mode - which the GUI said was excluded from the task.
"Failed:(0) Database 'SharedServices1_Search_DB' will not be backed up
because it does not have its recovery model set to Full or BulkLogged."
Regards,
Peter
www.skov.comHi Peter, I have confirmed that this issue happens and have filed a Connect
item. Please vote and add any other pertinent information.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=320914
"Peter" <pafpaf@.hotmail.com> wrote in message
news:urIlQygTIHA.536@.TK2MSFTNGP06.phx.gbl...
> SQL 2005 SP2:
> I have several Sharepoint databases, all in full recovery mode except the
> large search database which I want to run in simple mode because of the
> large amount of transactions and because data recovery is not needed.
> The back up log task in SQL Server Managment Studio is said to
> automatically exclude databases in simple recovery mode, but it doesen't -
> anyone having a workaround?
> Other users reported that this problem was introduced in SP2, see
> http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1336939&SiteID=17
> Here's how I reproduce the error:
> When I edit a maintenance plan which backs up transaction logs, I can
> select "Database(s)":
> At the top of the window it says after the yellow exclamation mark:
> "Databases with simple recovery will be excluded". Here I select "All user
> databases". (I want to use "All user databases" so that any Sharepoint
> databases created in the future are automatically included in this task.)
> Back at the "Back up Database Task", when using the button "View T-SQL" i
> see that the database in simple mode is not included - as expected.
> But when the task is run, it fails. That is, it does what it is expected
> to - it backs up all logs except from the database in simple mode, but it
> returns an error; where I expected it to run with out error.
> When looking in the job log in MSSQL\LOG, it shows that the reason of the
> error is that it tried to backup the log from the database in simple
> recovery mode - which the GUI said was excluded from the task.
> "Failed:(0) Database 'SharedServices1_Search_DB' will not be backed up
> because it does not have its recovery model set to Full or BulkLogged."
> Regards,
> Peter
> www.skov.com
>
>
>|||I also posted a related item:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=320918|||Good idea, I was actually thinking exactly the same today when I had the
problem. :-)
Peter
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23CaJ7%23hTIHA.4880@.TK2MSFTNGP03.phx.gbl...
>I also posted a related item:
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=320918
>
...it would be beneficial to be able to examine the T-SQL and possibly amend
or comment out the line(s) that are causing problems

Databases can only be backed up locally?

Dear all,
I have two windows 2003 servers, one is running arcserve 11.1 with sp2,
the
other is running MSSQL 2000 with SP4 with SAP application.
I have already installed the client agnet and sql agnet 11.1 sp2 to the
SQL
server.
However whenever I backup the SQL database arcserve will give me the
Error 1
326 saying that the username/password is incorrect.
I can browse thru the tree in arcserve manager and I can backup other
file o
n the sql server with no problem.
Then I tried to install the arcserve manager to the sql server and
tried to
backup the sql database with exactly the same username and password, it
work
s!
I confirm that there is no blocking for any network traffic between two
serv
er.
Would anyone help me on this to allow backup thru network from the sql
serve
r to the backup server?
Thanks a lot!
--
kevinling1
---
Posted via http://www.webservertalk.com
---
View this thread: http://www.webservertalk.com/message1564670.htmlkevinling1 wrote:
> Dear all,
> Would anyone help me on this to allow backup thru network from the sql
> serve
> r to the backup server?
> Thanks a lot!
>
I can't help you with the Arcserve problem, but I'd like to suggest
STRONGLY that you not perform your database backups using an agent like
this. Do your database backups using the native SQL BACKUP command,
backing up your data to a file on disk. Use Arcserve to backup that
disk file. These agent-based database backups tend to be not the most
reliable things.

Databases can only be backed up locally?

Dear all,
I have two windows 2003 servers, one is running arcserve 11.1 with sp2, the
other is running MSSQL 2000 with SP4 with SAP application.
I have already installed the client agnet and sql agnet 11.1 sp2 to the SQL
server.
However whenever I backup the SQL database arcserve will give me the Error 1
326 saying that the username/password is incorrect.
I can browse thru the tree in arcserve manager and I can backup other file o
n the sql server with no problem.
Then I tried to install the arcserve manager to the sql server and tried to
backup the sql database with exactly the same username and password, it work
s!
I confirm that there is no blocking for any network traffic between two serv
er.
Would anyone help me on this to allow backup thru network from the sql serve
r to the backup server?
Thanks a lot!kevinling1 wrote:
> Dear all,
> Would anyone help me on this to allow backup thru network from the sql
> serve
> r to the backup server?
> Thanks a lot!
>
I can't help you with the Arcserve problem, but I'd like to suggest
STRONGLY that you not perform your database backups using an agent like
this. Do your database backups using the native SQL BACKUP command,
backing up your data to a file on disk. Use Arcserve to backup that
disk file. These agent-based database backups tend to be not the most
reliable things.|||kevinling1 wrote:
> Dear all,
> Would anyone help me on this to allow backup thru network from the sql
> serve
> r to the backup server?
> Thanks a lot!
>
I can't help you with the Arcserve problem, but I'd like to suggest
STRONGLY that you not perform your database backups using an agent like
this. Do your database backups using the native SQL BACKUP command,
backing up your data to a file on disk. Use Arcserve to backup that
disk file. These agent-based database backups tend to be not the most
reliable things.

Database Transfermation from SQL 2000 to SQL 2005

Hello
We have two SQL server installation. SQL server 2000 with sp4 and SQL server
2005 sp2. We want tp transfer 2 data bases from SQL 2000 to SQL 2005. how can
we update or transfer Databse from one old version to new version?
best regards,
Thor
Thor
I'd go with BACKUP/RESTORE , however you are able to detach/attach those
databases as well. See the explanation in the BOL
"Thor" <Thor@.discussions.microsoft.com> wrote in message
news:DEE2E28A-2EA8-4532-A2B2-E8F31CB85B3B@.microsoft.com...
> Hello
> We have two SQL server installation. SQL server 2000 with sp4 and SQL
> server
> 2005 sp2. We want tp transfer 2 data bases from SQL 2000 to SQL 2005. how
> can
> we update or transfer Databse from one old version to new version?
> best regards,
> Thor

Database Transfermation from SQL 2000 to SQL 2005

Hello
We have two SQL server installation. SQL server 2000 with sp4 and SQL server
2005 sp2. We want tp transfer 2 data bases from SQL 2000 to SQL 2005. how can
we update or transfer Databse from one old version to new version?
best regards,
ThorThor
I'd go with BACKUP/RESTORE , however you are able to detach/attach those
databases as well. See the explanation in the BOL
"Thor" <Thor@.discussions.microsoft.com> wrote in message
news:DEE2E28A-2EA8-4532-A2B2-E8F31CB85B3B@.microsoft.com...
> Hello
> We have two SQL server installation. SQL server 2000 with sp4 and SQL
> server
> 2005 sp2. We want tp transfer 2 data bases from SQL 2000 to SQL 2005. how
> can
> we update or transfer Databse from one old version to new version?
> best regards,
> Thor|||"Thor" <Thor@.discussions.microsoft.com> wrote in message
news:DEE2E28A-2EA8-4532-A2B2-E8F31CB85B3B@.microsoft.com...
> Hello
> We have two SQL server installation. SQL server 2000 with sp4 and SQL
> server
> 2005 sp2. We want tp transfer 2 data bases from SQL 2000 to SQL 2005. how
> can
> we update or transfer Databse from one old version to new version?
> best regards,
> Thor
Hi Thor
If you are wanting to upgrade check out other posts regarding this such as
http://tinyurl.com/4uzmyl, running the upgrade advisor will show up most of
the potential problems, rebuilding indexes, stats and usage will reduce the
risk of poorly performing queries. If you do have performance issues check
the query plan.
John