Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

When I try to open my report in reporting services I get an error:
a.. An error has occurred during report processing. (rsProcessingAborted)
Get Online Help
a.. Cannot create a connection to data source 'Flyers'.
(rsErrorOpeningConnection) Get Online Help
a.. Cannot open database requested in login 'CRMElements_RealEstate'.
Login fails. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
----
My report is set to use NT Authentication and Works OK in VS.Net report
designer.
Reporting services is installed on a web server separate from SQL Server.
The SQL Server house both the reporting services databases and the database
I am trying to report against. Both server or Windows 2003. The SQL server
is also my AD controller.
I can get the report to work if I change the report to use SQL Server login
/ password, but then I have to supply it each time.
If I go into the report properties, data sources and try to change the way
the report authenticates I get an error:
Object reference not set to an instance of an object.
when I click apply.
The only way I can change the settings is to change them in report designer
and re-upload my report file. I am uploading the file through report
manager. I do not have any data sources configures on the report server. I
am embedding this information in the report (I think that is how it works).
IIS Security is set as Integrated Windows Authentication.
Any help as to where to look or how to troubleshoot is appreciated.I think it doesn't work because you need to activate delegation, which i am
not knowledgeable about.
As far as i know, windows credential are never retransmitted from one server
to another. Here is a little attempt at explaining what i mean
client(ie) -> reporting services(iis) -> SQL DB (sql server)
suppose these 3 elements are on distinct servers. ie will transmit your
windows authentication to IIS, but IIS will not push it to the sql server.
For this to work, i've read you need to activate delegation in active
directory, but i am not knowledgeable enough to help you on this topic. So
right now, we're just specifying sql server accounts in our report data
sources.
You can use shared data sources to make life easier.
Hope this helps
"Joe" wrote:
> When I try to open my report in reporting services I get an error:
> a.. An error has occurred during report processing. (rsProcessingAborted)
> Get Online Help
> a.. Cannot create a connection to data source 'Flyers'.
> (rsErrorOpeningConnection) Get Online Help
> a.. Cannot open database requested in login 'CRMElements_RealEstate'.
> Login fails. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> ----
> My report is set to use NT Authentication and Works OK in VS.Net report
> designer.
> Reporting services is installed on a web server separate from SQL Server.
> The SQL Server house both the reporting services databases and the database
> I am trying to report against. Both server or Windows 2003. The SQL server
> is also my AD controller.
> I can get the report to work if I change the report to use SQL Server login
> / password, but then I have to supply it each time.
> If I go into the report properties, data sources and try to change the way
> the report authenticates I get an error:
> Object reference not set to an instance of an object.
> when I click apply.
> The only way I can change the settings is to change them in report designer
> and re-upload my report file. I am uploading the file through report
> manager. I do not have any data sources configures on the report server. I
> am embedding this information in the report (I think that is how it works).
> IIS Security is set as Integrated Windows Authentication.
> Any help as to where to look or how to troubleshoot is appreciated.
>
>
>|||Do a google search for the "double hop problem."
You need to enable Server Principal Names (SPNs) which can be a daunting
task to setup properly.
-Joel
"Joe" <noemail@.noemail.com> wrote in message
news:OpPELIUaFHA.2664@.TK2MSFTNGP15.phx.gbl...
> When I try to open my report in reporting services I get an error:
> a.. An error has occurred during report processing. (rsProcessingAborted)
> Get Online Help
> a.. Cannot create a connection to data source 'Flyers'.
> (rsErrorOpeningConnection) Get Online Help
> a.. Cannot open database requested in login 'CRMElements_RealEstate'.
> Login fails. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> ----
> My report is set to use NT Authentication and Works OK in VS.Net report
> designer.
> Reporting services is installed on a web server separate from SQL Server.
> The SQL Server house both the reporting services databases and the
> database I am trying to report against. Both server or Windows 2003. The
> SQL server is also my AD controller.
> I can get the report to work if I change the report to use SQL Server
> login / password, but then I have to supply it each time.
> If I go into the report properties, data sources and try to change the way
> the report authenticates I get an error:
> Object reference not set to an instance of an object.
> when I click apply.
> The only way I can change the settings is to change them in report
> designer and re-upload my report file. I am uploading the file through
> report manager. I do not have any data sources configures on the report
> server. I am embedding this information in the report (I think that is
> how it works).
> IIS Security is set as Integrated Windows Authentication.
> Any help as to where to look or how to troubleshoot is appreciated.
>
>
>|||Please excuse my ignorance, but could you specify exactly how you do the
"specifying sql server accounts in our report data sources"
Is it on the "Credentials stored securely in the report server" on the report?
How and where would you setup the user? In Report Server?
or in SQL server. It's been a while since I setup users on a database
in SQL 6.5 or 7.0... can you just use sa '
I've got what you described in your post of 2 connections
between 3 computers and connot get it to work.
Big Thanks for the Help!
--
Robert Hansen
"/dev/null" wrote:
> I think it doesn't work because you need to activate delegation, which i am
> not knowledgeable about.
> As far as i know, windows credential are never retransmitted from one server
> to another. Here is a little attempt at explaining what i mean
> client(ie) -> reporting services(iis) -> SQL DB (sql server)
> suppose these 3 elements are on distinct servers. ie will transmit your
> windows authentication to IIS, but IIS will not push it to the sql server.
> For this to work, i've read you need to activate delegation in active
> directory, but i am not knowledgeable enough to help you on this topic. So
> right now, we're just specifying sql server accounts in our report data
> sources.
> You can use shared data sources to make life easier.
> Hope this helps
> "Joe" wrote:
> > When I try to open my report in reporting services I get an error:
> > a.. An error has occurred during report processing. (rsProcessingAborted)
> > Get Online Help
> > a.. Cannot create a connection to data source 'Flyers'.
> > (rsErrorOpeningConnection) Get Online Help
> > a.. Cannot open database requested in login 'CRMElements_RealEstate'.
> > Login fails. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> >
> > ----
> >
> > My report is set to use NT Authentication and Works OK in VS.Net report
> > designer.
> >
> > Reporting services is installed on a web server separate from SQL Server.
> > The SQL Server house both the reporting services databases and the database
> > I am trying to report against. Both server or Windows 2003. The SQL server
> > is also my AD controller.
> >
> > I can get the report to work if I change the report to use SQL Server login
> > / password, but then I have to supply it each time.
> >
> > If I go into the report properties, data sources and try to change the way
> > the report authenticates I get an error:
> > Object reference not set to an instance of an object.
> > when I click apply.
> >
> > The only way I can change the settings is to change them in report designer
> > and re-upload my report file. I am uploading the file through report
> > manager. I do not have any data sources configures on the report server. I
> > am embedding this information in the report (I think that is how it works).
> >
> > IIS Security is set as Integrated Windows Authentication.
> >
> > Any help as to where to look or how to troubleshoot is appreciated.
> >
> >
> >
> >
> >
> >|||Well with some resource digging... I've gotten my self up
out of the ignoreance hole I was in. I figured out how to
setup a SQL User Account, under Security/Logins "New Login"
and then in Reporting Services for each report under Properties-
Data Sources I checked "Credentials stored securely in the report server"
and entered <new> UserName and Password.
and it worked.!!!!! Yeah ME!!!!
I also changed it in Report Designer on on the Data Source Credentials Tab,
Saved and redeployed, but that didn't seem to do it. Looks like it has to
be done
in Report Server.
Thanks!!! Bob
To
--
Robert Hansen
"Bob Hansen" wrote:
> Please excuse my ignorance, but could you specify exactly how you do the
> "specifying sql server accounts in our report data sources"
> Is it on the "Credentials stored securely in the report server" on the report?
> How and where would you setup the user? In Report Server?
> or in SQL server. It's been a while since I setup users on a database
> in SQL 6.5 or 7.0... can you just use sa '
> I've got what you described in your post of 2 connections
> between 3 computers and connot get it to work.
> Big Thanks for the Help!
> --
> Robert Hansen
>
> "/dev/null" wrote:
> > I think it doesn't work because you need to activate delegation, which i am
> > not knowledgeable about.
> >
> > As far as i know, windows credential are never retransmitted from one server
> > to another. Here is a little attempt at explaining what i mean
> >
> > client(ie) -> reporting services(iis) -> SQL DB (sql server)
> >
> > suppose these 3 elements are on distinct servers. ie will transmit your
> > windows authentication to IIS, but IIS will not push it to the sql server.
> > For this to work, i've read you need to activate delegation in active
> > directory, but i am not knowledgeable enough to help you on this topic. So
> > right now, we're just specifying sql server accounts in our report data
> > sources.
> >
> > You can use shared data sources to make life easier.
> >
> > Hope this helps
> >
> > "Joe" wrote:
> >
> > > When I try to open my report in reporting services I get an error:
> > > a.. An error has occurred during report processing. (rsProcessingAborted)
> > > Get Online Help
> > > a.. Cannot create a connection to data source 'Flyers'.
> > > (rsErrorOpeningConnection) Get Online Help
> > > a.. Cannot open database requested in login 'CRMElements_RealEstate'.
> > > Login fails. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> > >
> > > ----
> > >
> > > My report is set to use NT Authentication and Works OK in VS.Net report
> > > designer.
> > >
> > > Reporting services is installed on a web server separate from SQL Server.
> > > The SQL Server house both the reporting services databases and the database
> > > I am trying to report against. Both server or Windows 2003. The SQL server
> > > is also my AD controller.
> > >
> > > I can get the report to work if I change the report to use SQL Server login
> > > / password, but then I have to supply it each time.
> > >
> > > If I go into the report properties, data sources and try to change the way
> > > the report authenticates I get an error:
> > > Object reference not set to an instance of an object.
> > > when I click apply.
> > >
> > > The only way I can change the settings is to change them in report designer
> > > and re-upload my report file. I am uploading the file through report
> > > manager. I do not have any data sources configures on the report server. I
> > > am embedding this information in the report (I think that is how it works).
> > >
> > > IIS Security is set as Integrated Windows Authentication.
> > >
> > > Any help as to where to look or how to troubleshoot is appreciated.
> > >
> > >
> > >
> > >
> > >
> > >

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

I get the following error message when I select a report:

An error has occurred during report processing.

Cannot create a connection to data source 'PSS5'.

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

My Data source is set to Windows Integrated Security when I get this error message. If I change my data source to be "Credential supplied by the user running the report", the report generates fine. I am running SQL 2005 SP2. I have SQL reporting services installed on different server than my database services. Both servers are W2K3 R2 x64.

My IIS website and virtual directories are set up for Integrated Windows Authentication. My IIS application pool is set up to use an AD service account. I have followed the step/procedures outlined at: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

http://blogs.msdn.com/sql_protocols/archive/2005/10/12/479871.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx

but to no avail. I am sure that I am missing something, but I can't figure out what. I would like to use Integrated Authentication, any ideas?

You are using allow anonymous in IIS. This means that your ReportViewer control is not passing the users credentials to the report server. If you want to use "allow anonymous" you will need to pass valid credentials to the report server. This can be done in your code that calls the Report Viewer control/Report Server.|||

Hi,

see more information about passing credentials programmatically here:

http://blogs.msdn.com/bimusings/archive/2005/11/05/489423.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

I don't think that the problem is related to ReportViewer or IIS configuration (Since the credantial information is passed to the datasource and denied). When u select Windows Intedrated Security for report options, the credantials of the user that initiates the Reporting Services at every start up (by default this user is: 'NT AUTHORITY\ANONYMOUS LOGON') are sent to the datasource (And if this user is not authorized in the target database you get the following error).

You can authorize the Reporting Services user in the target database ('NT AUTHORITY\ANONYMOUS LOGON' exists within your SQL Server Machines Users.

or

You can change the Reporting Services' user to a domain user that both computers can authanticate.

Administrative Tools -> Services. (Find 'SQL Server Reporting Services (MSSQLSERVER)' change user from LOG ON tab.)

I hope this helps.

|||Thanks for the replies, but they didn't seem to help. To clear up a few questions, this report was developed in Visual Studio 2005 and it works fine in it. The report renders ok if I launch in on the server, but not anywhere else. My Reporting Services' user is an AD account that both my servers can authenicate against, and this user does have access to the DB. My Website and virtual directories have "allow anonymous access" unchecked.|||I decided to try one more thing. I went into the web.config file and changed the <identity impersonate="false"/> and that fixed it for me. Thanks for all the replies.|||

Note:

The above fix will force IIS to use the Application pool account to connect to SQL on the remote server.

This is still not the permanent solution that I am looking for, I believe my problem is a kerberos issue at this point. Any tips/hints/suggestions on troubleshooting this problem would be helpful.

sql

login failed for user '(null)'| trusted connection

I had a report that was working and then this error started coming up whenever I tried to view it in the preview window.

login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection

When I upload the report rdl to our server and use an established data source the report works fine.

I have two questions. 1) Why would this error occur and 2) how do I fix it?

My guess is that I have to restablish a conenction to a working datasource but I don't know how to do it.

Any help would be greatly appreciated.

Thanks.

Is your datasource set to use integrated security? If so then you are probably hitting the double-hop problem.

http://blogs.msdn.com/jgalla/archive/2006/03/16/553314.aspx

|||I'm looking into this now but as some reports work and I can remake this report so that it functions I think it might have to be the report itself.

This report uses a private data source and I suspect that there might be a problem with it. How can I change a private data source without editing the RDL manually?

Again thank you for the help.|||I suspect that the reports that are functioning are using different credential options. You can view how the data sources are configured in Report Manager from the "Data Sources" tab for each report.|||I've received the same error but under different circumstances :

Login failed for user ". The user is not associated with trusted SQL Server connection.

The datasource is connecting to the database using SQL Server

Authentication. First time round this report previews fine.

I then copy and paste the report to obtain an identical one (with the

name of "Copy of report1") and then try and preview this new report,

but get the above error. The original report still works

fine. In the copy, all the dataset queries work fine when run

individually, the error only comes when i try and preview the

report. Any ideas why this is happening?

Guy|||Further to the previous post...

I later closed the original report and reopened it to find the original

gave the same error as above. After much investagation it

appeared that the datasets had somehow changed there datasources.

They were all pointing at datasources with the correct names, but not

shared ones - i dont recall setting up any that were not shared,

and they certainly are not showing in the solution explorer.

On re-pointing the sets to the correct shared sources it now all works

fine and copy and pastes fine too. But why should they have

changed during a copy and paste and even during a save and

reopen? ?

login failed for user '(null)'| trusted connection

I had a report that was working and then this error started coming up whenever I tried to view it in the preview window.

login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection

When I upload the report rdl to our server and use an established data source the report works fine.
I have two questions. 1) Why would this error occur and 2) how do I fix it?

My guess is that I have to restablish a conenction to a working datasource but I don't know how to do it.

Any help would be greatly appreciated.

Thanks.

Is your datasource set to use integrated security? If so then you are probably hitting the double-hop problem.

http://blogs.msdn.com/jgalla/archive/2006/03/16/553314.aspx

|||I'm looking into this now but as some reports work and I can remake this report so that it functions I think it might have to be the report itself.

This report uses a private data source and I suspect that there might be a problem with it. How can I change a private data source without editing the RDL manually?

Again thank you for the help.
|||I suspect that the reports that are functioning are using different credential options. You can view how the data sources are configured in Report Manager from the "Data Sources" tab for each report.|||I've received the same error but under different circumstances :
Login failed for user ". The user is not associated with trusted SQL Server connection.
The datasource is connecting to the database using SQL Server Authentication. First time round this report previews fine. I then copy and paste the report to obtain an identical one (with the name of "Copy of report1") and then try and preview this new report, but get the above error. The original report still works fine. In the copy, all the dataset queries work fine when run individually, the error only comes when i try and preview the report. Any ideas why this is happening?
Guy|||Further to the previous post...
I later closed the original report and reopened it to find the original gave the same error as above. After much investagation it appeared that the datasets had somehow changed there datasources. They were all pointing at datasources with the correct names, but not shared ones - i dont recall setting up any that were not shared, and they certainly are not showing in the solution explorer.
On re-pointing the sets to the correct shared sources it now all works fine and copy and pastes fine too. But why should they have changed during a copy and paste and even during a save and reopen? ?sql

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connect

Hi friends,
When I tried to connect to a report server I am getting this error.
Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection.
The sql server database is on one machine with windows 2003 standard
edition and report server is on another machine with windows 2003
webserver edition. Any help please.
Thanks in advance,
ChrisHI there,
if you have enaled Windows Authentification on your webserver and you use
integrated secuirty, your SQL Server has to be trusted for delegation to
enable him to check the credentials the user passes though:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_2gmm.asp
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Chris" <vvkp@.yahoo.com> schrieb im Newsbeitrag
news:1116879674.390989.310070@.f14g2000cwb.googlegroups.com...
> Hi friends,
> When I tried to connect to a report server I am getting this error.
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
> The sql server database is on one machine with windows 2003 standard
> edition and report server is on another machine with windows 2003
> webserver edition. Any help please.
> Thanks in advance,
> Chris
>

Login failed for user '(null)'. Reason: Not associated with a trus

I am new to SQL Server Reporting Services 2005 and have created a new very
simple report. When I run the report directly on the report server it works
fine. If I try and run the report from my laptop I get the error
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
I have set up the data source to use a trusted connection and my id has full
rights on the the database where the data resides. The Report server is
hosted on a SQL Server 2005 database and the data in the report is on a SQL
2000 named instance.
I am probably missing something in the setup, but don't know what. Any help
from anyone would be appreciated.does your SQL Server is on another server than the RS server himself?
(have you 2 servers: 1 with RS + IIS and the second with SQL Server himself)
If yes, then you suffer a Kerberos issue.
you have to setup Kerberos to allow your IIS Server to delegate the user.
Read this article:
http://support.microsoft.com/kb/215383/en-us
"gert" <gert@.discussions.microsoft.com> wrote in message
news:E981B1AB-6D2A-4751-8C0D-140B033CA1FA@.microsoft.com...
>I am new to SQL Server Reporting Services 2005 and have created a new very
> simple report. When I run the report directly on the report server it
> works
> fine. If I try and run the report from my laptop I get the error
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> I have set up the data source to use a trusted connection and my id has
> full
> rights on the the database where the data resides. The Report server is
> hosted on a SQL Server 2005 database and the data in the report is on a
> SQL
> 2000 named instance.
> I am probably missing something in the setup, but don't know what. Any
> help
> from anyone would be appreciated.

Login failed for user '(null)' - report error

Hello all,
Hope someone can help me with this problem. I wrote a report last week,
connecting to a database we have and using the " allow saving password"
option. This week I come to reopen the report and i am getting the following
error message: " a connection connot be made to the database. Set and test
the connection string. Login failed for '(null)' Reason not associated with
a trusted sql server connection" However the connection details i am
entering are exactly the same as last week. The password is the same also.
Can anyone help here? I dont want to start writing the report again.
thanks in advance
GregI am not quite sure if this is the problem, but when i have experienced this
error it was because the credentials in the datasource was missing.
"Greg" <Greg@.discussions.microsoft.com> wrote in message
news:BC1A812B-F2B9-4BAA-B76D-254D98B81854@.microsoft.com...
> Hello all,
> Hope someone can help me with this problem. I wrote a report last week,
> connecting to a database we have and using the " allow saving password"
> option. This week I come to reopen the report and i am getting the
following
> error message: " a connection connot be made to the database. Set and
test
> the connection string. Login failed for '(null)' Reason not associated
with
> a trusted sql server connection" However the connection details i am
> entering are exactly the same as last week. The password is the same
also.
> Can anyone help here? I dont want to start writing the report again.
> thanks in advance
> Greg

Login failed for user '(null)'

I have set up a vary basic report that connects to a SQL Server database,
executes a stored procedure that takes two parameters (start date and end
date). In the report I created in VS, I create the data source in VS using a
trusted connection and test the connection and it works fine. I can preview
the report with no problems. Reporting Services is installed on one server
and the database is on another server.
Once I have deployed the report and go to run it, it prompts me for the
start date and end date and then I go to view the report and I get the
following error:
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Cannot create a connection to data source 'winoasis'.
(rsErrorOpeningConnection) Get Online Help
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
I have tracing turned on to verbose and I can see my user name in the log,
but it still shows the Login failed for user '(null)'. Reason: Not associated
with a trusted SQL Server connection error.
Does the reporting services server need to have the trusted for delegation?
Any ideas on what is causing this problem?
Thanks
MichaelSounds like a datasource connection problem. Is the Authentication mode for
your SQL server Windows Only? If so, and your datasource is passing in UID
and PWD, you will need to set it to SQL Server and Windows.
Create a shared datasource in Report Manager, select the "Credentials stored
securely in the report server" and specify the User Name and Password so RS
can connect to get the data. Assign your report(s) to use the datasource.
Adrian M.
"MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
news:F9FC955B-1EF5-4670-95A8-B5BC8993A327@.microsoft.com...
>I have set up a vary basic report that connects to a SQL Server database,
> executes a stored procedure that takes two parameters (start date and end
> date). In the report I created in VS, I create the data source in VS using
> a
> trusted connection and test the connection and it works fine. I can
> preview
> the report with no problems. Reporting Services is installed on one server
> and the database is on another server.
> Once I have deployed the report and go to run it, it prompts me for the
> start date and end date and then I go to view the report and I get the
> following error:
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Cannot create a connection to data source 'winoasis'.
> (rsErrorOpeningConnection) Get Online Help
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> I have tracing turned on to verbose and I can see my user name in the log,
> but it still shows the Login failed for user '(null)'. Reason: Not
> associated
> with a trusted SQL Server connection error.
> Does the reporting services server need to have the trusted for
> delegation?
> Any ideas on what is causing this problem?
> Thanks
> Michael|||if you really want to use integrated security in this scenario (client ->
web server (RS) -> database server) than you have to set up kerberos ticket
delegation. (the web server service account needs to be trusted for
delegation)
"MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
news:F9FC955B-1EF5-4670-95A8-B5BC8993A327@.microsoft.com...
>I have set up a vary basic report that connects to a SQL Server database,
> executes a stored procedure that takes two parameters (start date and end
> date). In the report I created in VS, I create the data source in VS using
> a
> trusted connection and test the connection and it works fine. I can
> preview
> the report with no problems. Reporting Services is installed on one server
> and the database is on another server.
> Once I have deployed the report and go to run it, it prompts me for the
> start date and end date and then I go to view the report and I get the
> following error:
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Cannot create a connection to data source 'winoasis'.
> (rsErrorOpeningConnection) Get Online Help
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> I have tracing turned on to verbose and I can see my user name in the log,
> but it still shows the Login failed for user '(null)'. Reason: Not
> associated
> with a trusted SQL Server connection error.
> Does the reporting services server need to have the trusted for
> delegation?
> Any ideas on what is causing this problem?
> Thanks
> Michael|||The server is set for SQL Server and Windows. I have a login on the SQL
Server that uses windows and I connect with no problems through Enterprise
Manager and Query Analyzer. When I look at the SQL Error logs, I can see the
same error. Any other thoughts?
Michael
"Adrian M." wrote:
> Sounds like a datasource connection problem. Is the Authentication mode for
> your SQL server Windows Only? If so, and your datasource is passing in UID
> and PWD, you will need to set it to SQL Server and Windows.
> Create a shared datasource in Report Manager, select the "Credentials stored
> securely in the report server" and specify the User Name and Password so RS
> can connect to get the data. Assign your report(s) to use the datasource.
> Adrian M.
>
> "MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
> news:F9FC955B-1EF5-4670-95A8-B5BC8993A327@.microsoft.com...
> >I have set up a vary basic report that connects to a SQL Server database,
> > executes a stored procedure that takes two parameters (start date and end
> > date). In the report I created in VS, I create the data source in VS using
> > a
> > trusted connection and test the connection and it works fine. I can
> > preview
> > the report with no problems. Reporting Services is installed on one server
> > and the database is on another server.
> >
> > Once I have deployed the report and go to run it, it prompts me for the
> > start date and end date and then I go to view the report and I get the
> > following error:
> >
> > An error has occurred during report processing. (rsProcessingAborted) Get
> > Online Help
> > Cannot create a connection to data source 'winoasis'.
> > (rsErrorOpeningConnection) Get Online Help
> > Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> > Server connection.
> >
> > I have tracing turned on to verbose and I can see my user name in the log,
> > but it still shows the Login failed for user '(null)'. Reason: Not
> > associated
> > with a trusted SQL Server connection error.
> >
> > Does the reporting services server need to have the trusted for
> > delegation?
> > Any ideas on what is causing this problem?
> >
> > Thanks
> >
> > Michael
>
>|||My only other thoughts is the Connection String in the shared data source.
What option do you have selected under Connect Using on the datasource?
"MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
news:B490773D-B0EC-4B80-A6F1-AF36F2597CF0@.microsoft.com...
> The server is set for SQL Server and Windows. I have a login on the SQL
> Server that uses windows and I connect with no problems through Enterprise
> Manager and Query Analyzer. When I look at the SQL Error logs, I can see
> the
> same error. Any other thoughts?
> Michael
>
> "Adrian M." wrote:
>> Sounds like a datasource connection problem. Is the Authentication mode
>> for
>> your SQL server Windows Only? If so, and your datasource is passing in
>> UID
>> and PWD, you will need to set it to SQL Server and Windows.
>> Create a shared datasource in Report Manager, select the "Credentials
>> stored
>> securely in the report server" and specify the User Name and Password so
>> RS
>> can connect to get the data. Assign your report(s) to use the
>> datasource.
>> Adrian M.
>>
>> "MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
>> news:F9FC955B-1EF5-4670-95A8-B5BC8993A327@.microsoft.com...
>> >I have set up a vary basic report that connects to a SQL Server
>> >database,
>> > executes a stored procedure that takes two parameters (start date and
>> > end
>> > date). In the report I created in VS, I create the data source in VS
>> > using
>> > a
>> > trusted connection and test the connection and it works fine. I can
>> > preview
>> > the report with no problems. Reporting Services is installed on one
>> > server
>> > and the database is on another server.
>> >
>> > Once I have deployed the report and go to run it, it prompts me for the
>> > start date and end date and then I go to view the report and I get the
>> > following error:
>> >
>> > An error has occurred during report processing. (rsProcessingAborted)
>> > Get
>> > Online Help
>> > Cannot create a connection to data source 'winoasis'.
>> > (rsErrorOpeningConnection) Get Online Help
>> > Login failed for user '(null)'. Reason: Not associated with a trusted
>> > SQL
>> > Server connection.
>> >
>> > I have tracing turned on to verbose and I can see my user name in the
>> > log,
>> > but it still shows the Login failed for user '(null)'. Reason: Not
>> > associated
>> > with a trusted SQL Server connection error.
>> >
>> > Does the reporting services server need to have the trusted for
>> > delegation?
>> > Any ideas on what is causing this problem?
>> >
>> > Thanks
>> >
>> > Michael
>>|||I don't have the same connection auth setup that you are using but (after a
little digging) maybe this will help:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_datasources_v1_87e9.asp
Adrian M.
"MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
news:B490773D-B0EC-4B80-A6F1-AF36F2597CF0@.microsoft.com...
> The server is set for SQL Server and Windows. I have a login on the SQL
> Server that uses windows and I connect with no problems through Enterprise
> Manager and Query Analyzer. When I look at the SQL Error logs, I can see
> the
> same error. Any other thoughts?
> Michael
>
> "Adrian M." wrote:
>> Sounds like a datasource connection problem. Is the Authentication mode
>> for
>> your SQL server Windows Only? If so, and your datasource is passing in
>> UID
>> and PWD, you will need to set it to SQL Server and Windows.
>> Create a shared datasource in Report Manager, select the "Credentials
>> stored
>> securely in the report server" and specify the User Name and Password so
>> RS
>> can connect to get the data. Assign your report(s) to use the
>> datasource.
>> Adrian M.
>>
>> "MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
>> news:F9FC955B-1EF5-4670-95A8-B5BC8993A327@.microsoft.com...
>> >I have set up a vary basic report that connects to a SQL Server
>> >database,
>> > executes a stored procedure that takes two parameters (start date and
>> > end
>> > date). In the report I created in VS, I create the data source in VS
>> > using
>> > a
>> > trusted connection and test the connection and it works fine. I can
>> > preview
>> > the report with no problems. Reporting Services is installed on one
>> > server
>> > and the database is on another server.
>> >
>> > Once I have deployed the report and go to run it, it prompts me for the
>> > start date and end date and then I go to view the report and I get the
>> > following error:
>> >
>> > An error has occurred during report processing. (rsProcessingAborted)
>> > Get
>> > Online Help
>> > Cannot create a connection to data source 'winoasis'.
>> > (rsErrorOpeningConnection) Get Online Help
>> > Login failed for user '(null)'. Reason: Not associated with a trusted
>> > SQL
>> > Server connection.
>> >
>> > I have tracing turned on to verbose and I can see my user name in the
>> > log,
>> > but it still shows the Login failed for user '(null)'. Reason: Not
>> > associated
>> > with a trusted SQL Server connection error.
>> >
>> > Does the reporting services server need to have the trusted for
>> > delegation?
>> > Any ideas on what is causing this problem?
>> >
>> > Thanks
>> >
>> > Michael
>>|||Hi, I'm using Reporting Services and Everest by Outlooksoft and in the last
days sometimes I'm getting the same error message...don't know why because I
haven't modified anything in the reports I've been succesfully using in the
last months...
The only way I found to fix the problem is to restart the server...
Let me know if u find a valid solution!
thanks!
"Thomas Kern" wrote:
> if you really want to use integrated security in this scenario (client ->
> web server (RS) -> database server) than you have to set up kerberos ticket
> delegation. (the web server service account needs to be trusted for
> delegation)
>
> "MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
> news:F9FC955B-1EF5-4670-95A8-B5BC8993A327@.microsoft.com...
> >I have set up a vary basic report that connects to a SQL Server database,
> > executes a stored procedure that takes two parameters (start date and end
> > date). In the report I created in VS, I create the data source in VS using
> > a
> > trusted connection and test the connection and it works fine. I can
> > preview
> > the report with no problems. Reporting Services is installed on one server
> > and the database is on another server.
> >
> > Once I have deployed the report and go to run it, it prompts me for the
> > start date and end date and then I go to view the report and I get the
> > following error:
> >
> > An error has occurred during report processing. (rsProcessingAborted) Get
> > Online Help
> > Cannot create a connection to data source 'winoasis'.
> > (rsErrorOpeningConnection) Get Online Help
> > Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> > Server connection.
> >
> > I have tracing turned on to verbose and I can see my user name in the log,
> > but it still shows the Login failed for user '(null)'. Reason: Not
> > associated
> > with a trusted SQL Server connection error.
> >
> > Does the reporting services server need to have the trusted for
> > delegation?
> > Any ideas on what is causing this problem?
> >
> > Thanks
> >
> > Michael
>
>|||I ran into this problem yesterday and eventually solved it with the help of
the responses to your thread.
In my scenario, I was working with a Mixed security model SQL Server. I had
created a SQL Login for use with the report, and embedding the credentials
in the report. This failed with the same error you're recieving.
I finally realized that NT security was taking precedence, and changed the
login credentials to be a domain login (domain\loginname format) and the
report began to render properly.
In brief:
If working with a mixed security model, provide the Domain login info
instead of a valid SQL login.
"MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
news:B490773D-B0EC-4B80-A6F1-AF36F2597CF0@.microsoft.com...
> The server is set for SQL Server and Windows. I have a login on the SQL
> Server that uses windows and I connect with no problems through Enterprise
> Manager and Query Analyzer. When I look at the SQL Error logs, I can see
the
> same error. Any other thoughts?
> Michael
>
> "Adrian M." wrote:
> > Sounds like a datasource connection problem. Is the Authentication mode
for
> > your SQL server Windows Only? If so, and your datasource is passing in
UID
> > and PWD, you will need to set it to SQL Server and Windows.
> >
> > Create a shared datasource in Report Manager, select the "Credentials
stored
> > securely in the report server" and specify the User Name and Password so
RS
> > can connect to get the data. Assign your report(s) to use the
datasource.
> >
> > Adrian M.
> >
> >
> > "MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
> > news:F9FC955B-1EF5-4670-95A8-B5BC8993A327@.microsoft.com...
> > >I have set up a vary basic report that connects to a SQL Server
database,
> > > executes a stored procedure that takes two parameters (start date and
end
> > > date). In the report I created in VS, I create the data source in VS
using
> > > a
> > > trusted connection and test the connection and it works fine. I can
> > > preview
> > > the report with no problems. Reporting Services is installed on one
server
> > > and the database is on another server.
> > >
> > > Once I have deployed the report and go to run it, it prompts me for
the
> > > start date and end date and then I go to view the report and I get the
> > > following error:
> > >
> > > An error has occurred during report processing. (rsProcessingAborted)
Get
> > > Online Help
> > > Cannot create a connection to data source 'winoasis'.
> > > (rsErrorOpeningConnection) Get Online Help
> > > Login failed for user '(null)'. Reason: Not associated with a trusted
SQL
> > > Server connection.
> > >
> > > I have tracing turned on to verbose and I can see my user name in the
log,
> > > but it still shows the Login failed for user '(null)'. Reason: Not
> > > associated
> > > with a trusted SQL Server connection error.
> > >
> > > Does the reporting services server need to have the trusted for
> > > delegation?
> > > Any ideas on what is causing this problem?
> > >
> > > Thanks
> > >
> > > Michael
> >
> >
> >

Login failed for user '(null)'

Using RS2005 and SS2005. I am able to connect through a browser to
server/reports and run a report. However, another person is not able to run
the report. She gets the error: Cannot create a connection to data source
'dataSource1'. Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.
She is an administrator both of the network and of the database where the
data is. I also made her a sysadmin of the database where reporting services
is located but that didn't make any difference.
I originally was getting the same error until I made the server a trusted
computer for delegation. That solved the problem for me but not for her.
Any ideas? Thanks,
--
Dan D.I figured it out. I was taking off the 'anonymous access' from the reports
and reportserver web sites but I needed to remove it from the 'default web
site'. Doing that made everything work.
--
Dan D.
"Dan D." wrote:
> Using RS2005 and SS2005. I am able to connect through a browser to
> server/reports and run a report. However, another person is not able to run
> the report. She gets the error: Cannot create a connection to data source
> 'dataSource1'. Login failed for user '(null)'. Reason: Not associated with a
> trusted SQL Server connection.
> She is an administrator both of the network and of the database where the
> data is. I also made her a sysadmin of the database where reporting services
> is located but that didn't make any difference.
> I originally was getting the same error until I made the server a trusted
> computer for delegation. That solved the problem for me but not for her.
> Any ideas? Thanks,
>
> --
> Dan D.sql

Login failed for user '(null)'

I'm getting the following error:
An error has occurred during report processing.
Cannot create a connection to data source 'MyReports-ReportServer-PHX'.
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
This is only for data sources that use integrated authenticaiton. This is
on a fresh install of SQL Server 2005 and Reporting Services 2005 using
Visual Studio 2005. Per several articles/disuccsions, I've configured IIS
directory secruity to NOT allow anonymous access and to allow the Integrated
Windows Authentication exactly as I have on my other database server. This
is Windows Server 2003 IIS 6.0 and my other server is Windows 2000, IIS 5.0.
Any help would be GREATLY appreciated. Does this have something to do with
the IIS_WPG group not having correct permissions? The users do have the
correct permissions in my environment.Here's the stack trace as well from the reporting services error log...lots
of errors about the connection pool?
-- End of inner exception stack trace --
w3wp!webserver!1!01/24/2006-15:04:38:: e ERROR: Reporting Services error
Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has
occurred during report processing. -->
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An
error has occurred during report processing. -->
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'MyReports-ReportServer-PHX'. -->
System.Data.SqlClient.SqlException: Login failed for user '(null)'. Reason:
Not associated with a trusted SQL Server connection.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
enlistOK)
at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.ReportingServices.DataExtensions.SqlConnectionWrapper.Open()
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource
dataSourceObj, ReportProcessingContext pc)
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object threadSet)
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessingContext.AbortHelper.ThrowAbortException(Int32 reportUniqueName)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessingContext.CheckAndThrowIfAborted()
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.Merge.Process(ParameterInfoCollection parameters, Boolean mergeTran)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessReport(Report report, ProcessingContext pc, ProcessingContext context)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessReport(Report
report, ProcessingContext pc, Boolean snapshotProcessing, Boolean
processWithCachedData, GetReportChunk getChunkCallback, ErrorContext
errorContext, DateTime executionTime, CreateReportChunk cacheDataCallback,
ProcessingContext& context)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension
renderer, DateTime executionTimeStamp, GetReportChunk
getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc,
CreateReportChunk cacheDataCallback, Boolean& dataCached)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(DateTime
executionTimeStamp, GetReportChunk getCompiledDefinitionCallback,
ProcessingContext pc, RenderingContext rc)
at
Microsoft.ReportingServices.Library.RSService.RenderAsLive(CatalogItemContext
reportContext, ItemProperties properties, ParameterInfoCollection
effectiveParameters, Guid reportId, ClientRequest session, String
description, ReportSnapshot intermediateSnapshot, DataSourceInfoCollection
thisReportDataSources, Boolean cachingRequested, Warning[]& warnings,
ReportSnapshot& resultSnapshotData, DateTime& executionDateTime,
RuntimeDataSourceInfoCollection& alldataSources, UserProfileState&
usedUserProfile)
at
Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext
reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effectiveParameters)
at
Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext
reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames)
at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute()
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
at
Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService
rs, CatalogItemContext reportContext, ClientRequest session, JobType type,
Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]&
secondaryStreamNames)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderReport(HttpResponseStreamFactory streamFactory)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.DoStreamedOperation(StreamedOperation operation)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderItem(ItemType itemType)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageContent()
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()

Login failed for user '<<domain>>\<<server>>$'.

I am working on asp application which basically is an interface to the report server. I am currently unable to determine the source of the problem so it may have nothing to do with reporting services.

Currently the back in off this application consists of a reports and web server on a machine named tango and a SQL database server on a machine named tango.

The SQL logs show a failed login for user organization\polo$ (organization is a made up domain as i don’t what to give away where I work). There is no logon in SQL for the user polo$ and as far as I can see there is no user polo$ in the domain.

Has anyone seen this before? Can anyone account for the user polo$?

Could this be caused by reporting services trying to login to the two databases (ReportServer, ReportServerTempDB) that reporting services needs. These to databases are not on the report server. They are on tango.

Thanks in advanced

Is there a computer in the domain with the name "polo"? Network resources are accessed using the ASP.NET machine account on Windows Server 2003(BUILTIN\Network Service). The machine account name is DOMAIN\ComputerName$. The $ at the end hides it in normal views.

|||polo is the web/report server for the application.|||DOMAIN\polo$ is the name of the machine account for the web/report server. You need to grant access to ReportServer and ReportServerTempDB to DOMAIN\polo$.|||

Where can I get more information on this asp.net machine account? I don’t understand why it would be trying to access the database.

Secondly when I give it access to the database other user accounts stop working. It is like the asp.net machine account took precedence over the permissions I had set for a normal user.

|||This article (http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=2&rl=1) explains the accounts that various Reporting Services components run under on Windows 2000 Server, Windows XP, and Windows Server 2003. I suspect that you selected service account for accessing the SQL Server hosting the Reporting Services databases. You can change that option to a domain account using the rsconfig utility from the command line.|||

I was after information on SQL and ASP.NET machine account.

Because as I give the ASP.NET machine account access to the databases other user accounts stop working. It is like the ASP.NET machine account took precedence over the permissions I had set for other users.

Is this behavior normal for the ASP.NET Machine account.

|||I've honestly never seen other logins stop working when you enable the machine account. SQL Server just sees the incoming access token (DOMAIN\pogo$, DOMAIN\MyName, or whatever) and grants the appropriate permissions. Adding a user shouldn't affect the permissions for other users. Can you query using Query Analyzer and/or Enterprise Manager? Both those tools would be running under your current account. What exactly do you mean when you say the other user accounts stop working? What is the exact error message that you receive both before and after adding the DOMAIN\pogo$ account?|||After giving the machine account access to all stored procedures and databases...
Our application threw a stored procedure can not be executed user has insuffiecent privleages or something like that. When looking at the stored procedure the user did have premission to execute the stored procedure in question.

What im intersted in finding out though is why when i create a connection in my asp.net code do i get 2 logins occur One of the asp.net machine account and one of the user i am impersonating. In the sql error logs i get a login failure for the asp.net machine account. I want to know why the asp.net machine account is tyring to log on to sql in the first place when the asp.net application is impersonating a diffrent user.

I see you have read my other post at http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=66810. Which pretty much explain what i have just said. Please write all posts concerning this problem into the above mentioned thread. Thanks for you help so far.

I dont belive this to be a reporting services error anymore.

Regards

Dean Dalby

Login Failed for <domain name>\<Machine Name>

For some reason , the report server is trying to login as <domainname>\<machine name> - its supposed to be <domain>\<user name> or ASPNET or Network Service Authority - I have no clue why it is pickin gup machine name. Any ideas and how to fix?Use a Service account for your report server web identity and app pool in form <domain> \username make sure this user is an admin on DB and on the web server and is also a Member of the IIS_WPG group in the web server

gatharia

Login failed

I get this message using windows authentification. Any Ideas?
Reporting Services Error
----
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Cannot create a connection to data source 'NKRIM105_DB'.
(rsErrorOpeningConnection) Get Online Help
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
----
--
If you wait for an opportunity the opportunity will pass u by!Hi,
1) Please give your user approperiate access to database by add user to
database you are attempting to connect.
2) Your user must have appropriate access to reports deployed at report
server. Goto Report manager and add above user
Regards,
Ayaz Ahmad|||Hi,
1) Please give your user approperiate access to database by add user to
database you are attempting to connect.
2) Your user must have appropriate access to reports deployed at report
server. Goto Report manager and add above user
Regards,
Ayaz Ahmad

Login failed

I'm having trouble getting my report to run on the reporting services
server. I can run it fine from my machine, but when I deploy it, I get a
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
I've set the datasource to use a shared datasource, with a specific username
and password(which is the username and password for the reporting services
server, going after an external sql server with permissions to the reporting
services user.
Any ideas?
Thanx,
MikeAs long as I know, if you have your reporting services into one server
and your database into another, you CANNOT use trusted connection, you
must use a SQL Server login.
I'm telling this because I have the same problem and I didnt find
anything to solve so far.|||Go to report manager and the properties for your shared datasource. You
might have to set the credentials.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mike Voissem" <voissemm@.stjosephs-marhshfield.org> wrote in message
news:u8cQEhqyFHA.2312@.TK2MSFTNGP14.phx.gbl...
> I'm having trouble getting my report to run on the reporting services
> server. I can run it fine from my machine, but when I deploy it, I get a
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> I've set the datasource to use a shared datasource, with a specific
> username
> and password(which is the username and password for the reporting services
> server, going after an external sql server with permissions to the
> reporting
> services user.
> Any ideas?
> Thanx,
> Mike
>|||Thanx Bruce,
That did the trick.
Mike
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:#gJkBBryFHA.2960@.tk2msftngp13.phx.gbl...
> Go to report manager and the properties for your shared datasource. You
> might have to set the credentials.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Mike Voissem" <voissemm@.stjosephs-marhshfield.org> wrote in message
> news:u8cQEhqyFHA.2312@.TK2MSFTNGP14.phx.gbl...
> > I'm having trouble getting my report to run on the reporting services
> > server. I can run it fine from my machine, but when I deploy it, I get
a
> > Login failed for user '(null)'. Reason: Not associated with a trusted
SQL
> > Server connection.
> > I've set the datasource to use a shared datasource, with a specific
> > username
> > and password(which is the username and password for the reporting
services
> > server, going after an external sql server with permissions to the
> > reporting
> > services user.
> > Any ideas?
> > Thanx,
> > Mike
> >
> >
>

Login box when starting Report Builder

I'm new in SSRS so hopefully this will be an easy question.

I want to create a report model based on a cube. I have created a data source for the cube. Now when I click on Report Builder I get a login box titled "Microsoft Report Server Login".

When I enter the local admin account and password I get:

No report server was found at http://crossdatabase/ReportServer

When I enter that URL in IE I get:

crossdatabase/ReportServer - /

---

zondag 16 september 2007 23:24 <ds> Crossdatabase

Microsoft SQL Server Reporting Services Version 9.00.1399.00 What am I doing wrong? I already found some explanation about adding the Report Builder role so in home I now have:

EditBUILTIN\AdministratorsContent Manager, Report Builder

Anyone got any ideas?
Thanks,Stijn Verrept.

Please review the link below and let us know if this fixes your issue.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1697246&SiteID=1

|||I won't have access to the machine till later on, but this post is about users not seeing the Report Builder button. I'm admin, I see the button but when I click it I get the login box.|||

I tried but still get the same login box after clicking on the Report Builder button.

This is the login box that I get:

http://www.caresolutions.be/login.jpg

|||

According to your log above, you are running SQL Server 2005 RTM (Version 9.00.1399.00 ). You need to apply Service Pack 2 which should get you to Version 9.00.3042.00 and may fix your problem.

|||

This indeed fixed my problem, I now have another one however, but I'll post this in a new thread. Thanks.

login and pass in a web.config

Hi!!

is there any way to get the login and password on my program′s web.config?

Full explain:

I have a sub report that is missing credentials.

In my tests, the sub report worked when I fill the login and password with a login and pass (mine, for example). But, this is not a good idea because the login and password would be changed when it′s system go to a production server. So I would need to deploy again with the new login and password.

Best regards!!

Pedro

try following:

<add key="RSServerUrl" value=http://urservername/reportserver/reportfolder />

-kushpaw

|||

But this is to put on my web.config,

I need put in my report′s datasource the login and password that is in my web.config.

Pedro

Logging stored procedure use with MSDE (2000)

I have a app connected to MSDE that creates a report. The DB has over 300
stored procedures, with various args. I'm 9.9% sure the report must call a
SP. Can I somehow start a trace or log and have MSDE capture everything?
I'm hoping this way, I can discover the SP being run, along with the args.
I need to be able to run the report from the command line to get the output
into VBScript. (I know how to run a SP from VBScript, and massaging the
output shouldn't be a problem.)
Marco
You should be able to capture this using a server-side trace. Read about Profiler in Books Online,
and also read about, for instance sp_trace_create (etc).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Marco Shaw" <marco@.Znbnet.nb.ca> wrote in message news:u14RnmN4GHA.2420@.TK2MSFTNGP02.phx.gbl...
>I have a app connected to MSDE that creates a report. The DB has over 300
> stored procedures, with various args. I'm 9.9% sure the report must call a
> SP. Can I somehow start a trace or log and have MSDE capture everything?
> I'm hoping this way, I can discover the SP being run, along with the args.
> I need to be able to run the report from the command line to get the output
> into VBScript. (I know how to run a SP from VBScript, and massaging the
> output shouldn't be a problem.)
> Marco
>
|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uGNTi%23U4GHA.2596@.TK2MSFTNGP06.phx.gbl...
> You should be able to capture this using a server-side trace. Read about
Profiler in Books Online,
> and also read about, for instance sp_trace_create (etc).
Am just using MSDE which doesn't seem to have Profiler. Looking in to
sp_trace_create.
Thanks.
|||I just replied to your other post. Try to get hold of a "full" SQL Server, if only for a minute, and
script a trace from there. Here's an example, btw:
/************************************************** **/
/* Created by: SQL Server Profiler 2005 */
/* Date: 2006/09/26 16:21:52 */
/************************************************** **/
-- Create a Queue
declare @.rc int
declare @.TraceID int
declare @.maxfilesize bigint
set @.maxfilesize = 5
-- Please replace the text InsertFileNameHere, with an appropriate
-- filename prefixed by a path, e.g., c:\MyFolder\MyTrace. The .trc extension
-- will be appended to the filename automatically. If you are writing from
-- remote server to local drive, please use UNC path and make sure server has
-- write access to your network share
exec @.rc = sp_trace_create @.TraceID output, 0, N'InsertFileNameHere', @.maxfilesize, NULL
if (@.rc != 0) goto error
-- Client side File and Table cannot be scripted
-- Set the events
declare @.on bit
set @.on = 1
exec sp_trace_setevent @.TraceID, 14, 1, @.on
exec sp_trace_setevent @.TraceID, 14, 9, @.on
exec sp_trace_setevent @.TraceID, 14, 6, @.on
exec sp_trace_setevent @.TraceID, 14, 10, @.on
exec sp_trace_setevent @.TraceID, 14, 14, @.on
exec sp_trace_setevent @.TraceID, 14, 11, @.on
exec sp_trace_setevent @.TraceID, 14, 12, @.on
exec sp_trace_setevent @.TraceID, 15, 15, @.on
exec sp_trace_setevent @.TraceID, 15, 16, @.on
exec sp_trace_setevent @.TraceID, 15, 9, @.on
exec sp_trace_setevent @.TraceID, 15, 13, @.on
exec sp_trace_setevent @.TraceID, 15, 17, @.on
exec sp_trace_setevent @.TraceID, 15, 6, @.on
exec sp_trace_setevent @.TraceID, 15, 10, @.on
exec sp_trace_setevent @.TraceID, 15, 14, @.on
exec sp_trace_setevent @.TraceID, 15, 18, @.on
exec sp_trace_setevent @.TraceID, 15, 11, @.on
exec sp_trace_setevent @.TraceID, 15, 12, @.on
exec sp_trace_setevent @.TraceID, 17, 12, @.on
exec sp_trace_setevent @.TraceID, 17, 1, @.on
exec sp_trace_setevent @.TraceID, 17, 9, @.on
exec sp_trace_setevent @.TraceID, 17, 6, @.on
exec sp_trace_setevent @.TraceID, 17, 10, @.on
exec sp_trace_setevent @.TraceID, 17, 14, @.on
exec sp_trace_setevent @.TraceID, 17, 11, @.on
exec sp_trace_setevent @.TraceID, 10, 15, @.on
exec sp_trace_setevent @.TraceID, 10, 16, @.on
exec sp_trace_setevent @.TraceID, 10, 9, @.on
exec sp_trace_setevent @.TraceID, 10, 17, @.on
exec sp_trace_setevent @.TraceID, 10, 2, @.on
exec sp_trace_setevent @.TraceID, 10, 10, @.on
exec sp_trace_setevent @.TraceID, 10, 18, @.on
exec sp_trace_setevent @.TraceID, 10, 11, @.on
exec sp_trace_setevent @.TraceID, 10, 12, @.on
exec sp_trace_setevent @.TraceID, 10, 13, @.on
exec sp_trace_setevent @.TraceID, 10, 6, @.on
exec sp_trace_setevent @.TraceID, 10, 14, @.on
exec sp_trace_setevent @.TraceID, 12, 15, @.on
exec sp_trace_setevent @.TraceID, 12, 16, @.on
exec sp_trace_setevent @.TraceID, 12, 1, @.on
exec sp_trace_setevent @.TraceID, 12, 9, @.on
exec sp_trace_setevent @.TraceID, 12, 17, @.on
exec sp_trace_setevent @.TraceID, 12, 6, @.on
exec sp_trace_setevent @.TraceID, 12, 10, @.on
exec sp_trace_setevent @.TraceID, 12, 14, @.on
exec sp_trace_setevent @.TraceID, 12, 18, @.on
exec sp_trace_setevent @.TraceID, 12, 11, @.on
exec sp_trace_setevent @.TraceID, 12, 12, @.on
exec sp_trace_setevent @.TraceID, 12, 13, @.on
exec sp_trace_setevent @.TraceID, 13, 12, @.on
exec sp_trace_setevent @.TraceID, 13, 1, @.on
exec sp_trace_setevent @.TraceID, 13, 9, @.on
exec sp_trace_setevent @.TraceID, 13, 6, @.on
exec sp_trace_setevent @.TraceID, 13, 10, @.on
exec sp_trace_setevent @.TraceID, 13, 14, @.on
exec sp_trace_setevent @.TraceID, 13, 11, @.on
-- Set the Filters
declare @.intfilter int
declare @.bigintfilter bigint
exec sp_trace_setfilter @.TraceID, 10, 0, 7, N'SQL Server Profiler -
74e4bb26-8675-4e74-90d0-5793d57489d1'
-- Set the trace status to start
exec sp_trace_setstatus @.TraceID, 1
-- display trace id for future references
select TraceID=@.TraceID
goto finish
error:
select ErrorCode=@.rc
finish:
go
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Marco Shaw" <marco@.Znbnet.nb.ca> wrote in message news:e2RVkeX4GHA.4352@.TK2MSFTNGP03.phx.gbl...
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:uGNTi%23U4GHA.2596@.TK2MSFTNGP06.phx.gbl...
> Profiler in Books Online,
> Am just using MSDE which doesn't seem to have Profiler. Looking in to
> sp_trace_create.
> Thanks.
>

Logging stored procedure use with MSDE (2000)

I have a app connected to MSDE that creates a report. The DB has over 300
stored procedures, with various args. I'm 9.9% sure the report must call a
SP. Can I somehow start a trace or log and have MSDE capture everything?
I'm hoping this way, I can discover the SP being run, along with the args.
I need to be able to run the report from the command line to get the output
into VBScript. (I know how to run a SP from VBScript, and massaging the
output shouldn't be a problem.)
MarcoYou should be able to capture this using a server-side trace. Read about Pro
filer in Books Online,
and also read about, for instance sp_trace_create (etc).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Marco Shaw" <marco@.Znbnet.nb.ca> wrote in message news:u14RnmN4GHA.2420@.TK2MSFTNGP02.phx.gb
l...
>I have a app connected to MSDE that creates a report. The DB has over 300
> stored procedures, with various args. I'm 9.9% sure the report must call
a
> SP. Can I somehow start a trace or log and have MSDE capture everything?
> I'm hoping this way, I can discover the SP being run, along with the args.
> I need to be able to run the report from the command line to get the outpu
t
> into VBScript. (I know how to run a SP from VBScript, and massaging the
> output shouldn't be a problem.)
> Marco
>|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uGNTi%23U4GHA.2596@.TK2MSFTNGP06.phx.gbl...
> You should be able to capture this using a server-side trace. Read about
Profiler in Books Online,
> and also read about, for instance sp_trace_create (etc).
Am just using MSDE which doesn't seem to have Profiler. Looking in to
sp_trace_create.
Thanks.|||I just replied to your other post. Try to get hold of a "full" SQL Server, i
f only for a minute, and
script a trace from there. Here's an example, btw:
/ ****************************************
************/
/* Created by: SQL Server Profiler 2005 */
/* Date: 2006/09/26 16:21:52 */
/ ****************************************
************/
-- Create a Queue
declare @.rc int
declare @.TraceID int
declare @.maxfilesize bigint
set @.maxfilesize = 5
-- Please replace the text InsertFileNameHere, with an appropriate
-- filename prefixed by a path, e.g., c:\MyFolder\MyTrace. The .trc extensio
n
-- will be appended to the filename automatically. If you are writing from
-- remote server to local drive, please use UNC path and make sure server ha
s
-- write access to your network share
exec @.rc = sp_trace_create @.TraceID output, 0, N'InsertFileNameHere', @.maxfi
lesize, NULL
if (@.rc != 0) goto error
-- Client side File and Table cannot be scripted
-- Set the events
declare @.on bit
set @.on = 1
exec sp_trace_setevent @.TraceID, 14, 1, @.on
exec sp_trace_setevent @.TraceID, 14, 9, @.on
exec sp_trace_setevent @.TraceID, 14, 6, @.on
exec sp_trace_setevent @.TraceID, 14, 10, @.on
exec sp_trace_setevent @.TraceID, 14, 14, @.on
exec sp_trace_setevent @.TraceID, 14, 11, @.on
exec sp_trace_setevent @.TraceID, 14, 12, @.on
exec sp_trace_setevent @.TraceID, 15, 15, @.on
exec sp_trace_setevent @.TraceID, 15, 16, @.on
exec sp_trace_setevent @.TraceID, 15, 9, @.on
exec sp_trace_setevent @.TraceID, 15, 13, @.on
exec sp_trace_setevent @.TraceID, 15, 17, @.on
exec sp_trace_setevent @.TraceID, 15, 6, @.on
exec sp_trace_setevent @.TraceID, 15, 10, @.on
exec sp_trace_setevent @.TraceID, 15, 14, @.on
exec sp_trace_setevent @.TraceID, 15, 18, @.on
exec sp_trace_setevent @.TraceID, 15, 11, @.on
exec sp_trace_setevent @.TraceID, 15, 12, @.on
exec sp_trace_setevent @.TraceID, 17, 12, @.on
exec sp_trace_setevent @.TraceID, 17, 1, @.on
exec sp_trace_setevent @.TraceID, 17, 9, @.on
exec sp_trace_setevent @.TraceID, 17, 6, @.on
exec sp_trace_setevent @.TraceID, 17, 10, @.on
exec sp_trace_setevent @.TraceID, 17, 14, @.on
exec sp_trace_setevent @.TraceID, 17, 11, @.on
exec sp_trace_setevent @.TraceID, 10, 15, @.on
exec sp_trace_setevent @.TraceID, 10, 16, @.on
exec sp_trace_setevent @.TraceID, 10, 9, @.on
exec sp_trace_setevent @.TraceID, 10, 17, @.on
exec sp_trace_setevent @.TraceID, 10, 2, @.on
exec sp_trace_setevent @.TraceID, 10, 10, @.on
exec sp_trace_setevent @.TraceID, 10, 18, @.on
exec sp_trace_setevent @.TraceID, 10, 11, @.on
exec sp_trace_setevent @.TraceID, 10, 12, @.on
exec sp_trace_setevent @.TraceID, 10, 13, @.on
exec sp_trace_setevent @.TraceID, 10, 6, @.on
exec sp_trace_setevent @.TraceID, 10, 14, @.on
exec sp_trace_setevent @.TraceID, 12, 15, @.on
exec sp_trace_setevent @.TraceID, 12, 16, @.on
exec sp_trace_setevent @.TraceID, 12, 1, @.on
exec sp_trace_setevent @.TraceID, 12, 9, @.on
exec sp_trace_setevent @.TraceID, 12, 17, @.on
exec sp_trace_setevent @.TraceID, 12, 6, @.on
exec sp_trace_setevent @.TraceID, 12, 10, @.on
exec sp_trace_setevent @.TraceID, 12, 14, @.on
exec sp_trace_setevent @.TraceID, 12, 18, @.on
exec sp_trace_setevent @.TraceID, 12, 11, @.on
exec sp_trace_setevent @.TraceID, 12, 12, @.on
exec sp_trace_setevent @.TraceID, 12, 13, @.on
exec sp_trace_setevent @.TraceID, 13, 12, @.on
exec sp_trace_setevent @.TraceID, 13, 1, @.on
exec sp_trace_setevent @.TraceID, 13, 9, @.on
exec sp_trace_setevent @.TraceID, 13, 6, @.on
exec sp_trace_setevent @.TraceID, 13, 10, @.on
exec sp_trace_setevent @.TraceID, 13, 14, @.on
exec sp_trace_setevent @.TraceID, 13, 11, @.on
-- Set the Filters
declare @.intfilter int
declare @.bigintfilter bigint
exec sp_trace_setfilter @.TraceID, 10, 0, 7, N'SQL Server Profiler -
74e4bb26-8675-4e74-90d0-5793d57489d1'
-- Set the trace status to start
exec sp_trace_setstatus @.TraceID, 1
-- display trace id for future references
select TraceID=@.TraceID
goto finish
error:
select ErrorCode=@.rc
finish:
go
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Marco Shaw" <marco@.Znbnet.nb.ca> wrote in message news:e2RVkeX4GHA.4352@.TK2MSFTNGP03.phx.gb
l...
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:uGNTi%23U4GHA.2596@.TK2MSFTNGP06.phx.gbl...
> Profiler in Books Online,
> Am just using MSDE which doesn't seem to have Profiler. Looking in to
> sp_trace_create.
> Thanks.
>

Logging stored procedure use with MSDE (2000)

I have a app connected to MSDE that creates a report. The DB has over 300
stored procedures, with various args. I'm 9.9% sure the report must call a
SP. Can I somehow start a trace or log and have MSDE capture everything?
I'm hoping this way, I can discover the SP being run, along with the args.
I need to be able to run the report from the command line to get the output
into VBScript. (I know how to run a SP from VBScript, and massaging the
output shouldn't be a problem.)
MarcoYou should be able to capture this using a server-side trace. Read about Profiler in Books Online,
and also read about, for instance sp_trace_create (etc).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Marco Shaw" <marco@.Znbnet.nb.ca> wrote in message news:u14RnmN4GHA.2420@.TK2MSFTNGP02.phx.gbl...
>I have a app connected to MSDE that creates a report. The DB has over 300
> stored procedures, with various args. I'm 9.9% sure the report must call a
> SP. Can I somehow start a trace or log and have MSDE capture everything?
> I'm hoping this way, I can discover the SP being run, along with the args.
> I need to be able to run the report from the command line to get the output
> into VBScript. (I know how to run a SP from VBScript, and massaging the
> output shouldn't be a problem.)
> Marco
>|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uGNTi%23U4GHA.2596@.TK2MSFTNGP06.phx.gbl...
> You should be able to capture this using a server-side trace. Read about
Profiler in Books Online,
> and also read about, for instance sp_trace_create (etc).
Am just using MSDE which doesn't seem to have Profiler. Looking in to
sp_trace_create.
Thanks.|||I just replied to your other post. Try to get hold of a "full" SQL Server, if only for a minute, and
script a trace from there. Here's an example, btw:
/****************************************************/
/* Created by: SQL Server Profiler 2005 */
/* Date: 2006/09/26 16:21:52 */
/****************************************************/
-- Create a Queue
declare @.rc int
declare @.TraceID int
declare @.maxfilesize bigint
set @.maxfilesize = 5
-- Please replace the text InsertFileNameHere, with an appropriate
-- filename prefixed by a path, e.g., c:\MyFolder\MyTrace. The .trc extension
-- will be appended to the filename automatically. If you are writing from
-- remote server to local drive, please use UNC path and make sure server has
-- write access to your network share
exec @.rc = sp_trace_create @.TraceID output, 0, N'InsertFileNameHere', @.maxfilesize, NULL
if (@.rc != 0) goto error
-- Client side File and Table cannot be scripted
-- Set the events
declare @.on bit
set @.on = 1
exec sp_trace_setevent @.TraceID, 14, 1, @.on
exec sp_trace_setevent @.TraceID, 14, 9, @.on
exec sp_trace_setevent @.TraceID, 14, 6, @.on
exec sp_trace_setevent @.TraceID, 14, 10, @.on
exec sp_trace_setevent @.TraceID, 14, 14, @.on
exec sp_trace_setevent @.TraceID, 14, 11, @.on
exec sp_trace_setevent @.TraceID, 14, 12, @.on
exec sp_trace_setevent @.TraceID, 15, 15, @.on
exec sp_trace_setevent @.TraceID, 15, 16, @.on
exec sp_trace_setevent @.TraceID, 15, 9, @.on
exec sp_trace_setevent @.TraceID, 15, 13, @.on
exec sp_trace_setevent @.TraceID, 15, 17, @.on
exec sp_trace_setevent @.TraceID, 15, 6, @.on
exec sp_trace_setevent @.TraceID, 15, 10, @.on
exec sp_trace_setevent @.TraceID, 15, 14, @.on
exec sp_trace_setevent @.TraceID, 15, 18, @.on
exec sp_trace_setevent @.TraceID, 15, 11, @.on
exec sp_trace_setevent @.TraceID, 15, 12, @.on
exec sp_trace_setevent @.TraceID, 17, 12, @.on
exec sp_trace_setevent @.TraceID, 17, 1, @.on
exec sp_trace_setevent @.TraceID, 17, 9, @.on
exec sp_trace_setevent @.TraceID, 17, 6, @.on
exec sp_trace_setevent @.TraceID, 17, 10, @.on
exec sp_trace_setevent @.TraceID, 17, 14, @.on
exec sp_trace_setevent @.TraceID, 17, 11, @.on
exec sp_trace_setevent @.TraceID, 10, 15, @.on
exec sp_trace_setevent @.TraceID, 10, 16, @.on
exec sp_trace_setevent @.TraceID, 10, 9, @.on
exec sp_trace_setevent @.TraceID, 10, 17, @.on
exec sp_trace_setevent @.TraceID, 10, 2, @.on
exec sp_trace_setevent @.TraceID, 10, 10, @.on
exec sp_trace_setevent @.TraceID, 10, 18, @.on
exec sp_trace_setevent @.TraceID, 10, 11, @.on
exec sp_trace_setevent @.TraceID, 10, 12, @.on
exec sp_trace_setevent @.TraceID, 10, 13, @.on
exec sp_trace_setevent @.TraceID, 10, 6, @.on
exec sp_trace_setevent @.TraceID, 10, 14, @.on
exec sp_trace_setevent @.TraceID, 12, 15, @.on
exec sp_trace_setevent @.TraceID, 12, 16, @.on
exec sp_trace_setevent @.TraceID, 12, 1, @.on
exec sp_trace_setevent @.TraceID, 12, 9, @.on
exec sp_trace_setevent @.TraceID, 12, 17, @.on
exec sp_trace_setevent @.TraceID, 12, 6, @.on
exec sp_trace_setevent @.TraceID, 12, 10, @.on
exec sp_trace_setevent @.TraceID, 12, 14, @.on
exec sp_trace_setevent @.TraceID, 12, 18, @.on
exec sp_trace_setevent @.TraceID, 12, 11, @.on
exec sp_trace_setevent @.TraceID, 12, 12, @.on
exec sp_trace_setevent @.TraceID, 12, 13, @.on
exec sp_trace_setevent @.TraceID, 13, 12, @.on
exec sp_trace_setevent @.TraceID, 13, 1, @.on
exec sp_trace_setevent @.TraceID, 13, 9, @.on
exec sp_trace_setevent @.TraceID, 13, 6, @.on
exec sp_trace_setevent @.TraceID, 13, 10, @.on
exec sp_trace_setevent @.TraceID, 13, 14, @.on
exec sp_trace_setevent @.TraceID, 13, 11, @.on
-- Set the Filters
declare @.intfilter int
declare @.bigintfilter bigint
exec sp_trace_setfilter @.TraceID, 10, 0, 7, N'SQL Server Profiler -
74e4bb26-8675-4e74-90d0-5793d57489d1'
-- Set the trace status to start
exec sp_trace_setstatus @.TraceID, 1
-- display trace id for future references
select TraceID=@.TraceID
goto finish
error:
select ErrorCode=@.rc
finish:
go
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Marco Shaw" <marco@.Znbnet.nb.ca> wrote in message news:e2RVkeX4GHA.4352@.TK2MSFTNGP03.phx.gbl...
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:uGNTi%23U4GHA.2596@.TK2MSFTNGP06.phx.gbl...
>> You should be able to capture this using a server-side trace. Read about
> Profiler in Books Online,
>> and also read about, for instance sp_trace_create (etc).
> Am just using MSDE which doesn't seem to have Profiler. Looking in to
> sp_trace_create.
> Thanks.
>