Non SMTP email

Hi,
On my network exchange servers don't use smtp.
Is it possible to configure RS to email using other methods link MAPI,
... ?The delivery extension that shipped with RS only works with SMTP. You would
need to write you own delivery extension to do this.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
<kamara1@.yahoo.com> wrote in message
news:1105611912.754219.160300@.f14g2000cwb.googlegroups.com...
> Hi,
> On my network exchange servers don't use smtp.
> Is it possible to configure RS to email using other methods link MAPI,
> ... ?
>

Non Admin user error on Reporting Services

I am very new to reporting services. I have completed the SQL Tutorials that come with however I am stuck on something.

My network here consists of a 2003 AD Controlled Domain, various servers yadda yadda. I obviously am a Domain admin as well as a Normal Administrator. I have deployed my report and when I, or any other member on the domain who is in the same groups as me tries to access the report it works perfectly however, when a normal Domain User tries to access the report from http://servername/reports they get the following message :-

An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DashboardSQL-2K5'. (rsErrorOpeningConnection)
For more information about this error navigate to the report server on the local server machine, or enable remote errors

What on earth does this mean. Once I have deployed the report I am going into Reporting Services manager and reapplying the security permissions for the Data Source but it appears to make no difference.

Anybody able to shed some light on this?

Regards

It sounds like you have configured the data source 'DashboardSQL-2K5' to use Windows credentials. In this case RS will use the credentials of the user who is running the report to connect to the data source. Do your non-admin users have permission to login to your SQL Server?

-Albert

Non- Admin connection

I am testing an Access Database on network workstations with linked tables
to SQL Server. I set up a DSN and have no problem logged in as myself with
Admin rights to the server. But when I login as a user with no admin rights
I am denied access with this message:
Connection failed:
SQL Server State '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'dayoubunc1\Sales'.
The network server is Windows 2003 Server, the workstation is Windows 2000
Pro and the SQL Server is a runtime version which came with a Veratis backup
system.
The purpose of moving the tables to SQL Server is security. A user can
steal an Access backend, so I don't want the user to have admin rights to
use the DB. What can I do.
Thanks and God Bless,
Mark A. Sam
Are you sure that it is related to admin rights? Maybe you just need to add a user named "Sales" to
the SQL Server permissions?
"Mark A. Sam" <msam@.Plan-It-Earth.Net> wrote in message
news:u2oqViHmFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I am testing an Access Database on network workstations with linked tables
> to SQL Server. I set up a DSN and have no problem logged in as myself with
> Admin rights to the server. But when I login as a user with no admin rights
> I am denied access with this message:
> Connection failed:
> SQL Server State '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'dayoubunc1\Sales'.
>
> The network server is Windows 2003 Server, the workstation is Windows 2000
> Pro and the SQL Server is a runtime version which came with a Veratis backup
> system.
> The purpose of moving the tables to SQL Server is security. A user can
> steal an Access backend, so I don't want the user to have admin rights to
> use the DB. What can I do.
> Thanks and God Bless,
> Mark A. Sam
>
|||Hello Scot,
I don't know how I would do that. I opened Enterprise manager and tried to
add a new user but the Network users weren't available. I am very
inexperienced with SQL Server, but I think I recall from another client db
that the users network users were listed. And thinking about they, they had
many users who only had to log in and the DB worked, even through terminal
service sessions. It seems as though I only set up the DSNs on those
workstations.
God Bless,
Mark
|||I tried adding full Control to the user for the SQL Server Folder as well as
the database folder, but it didn't get me any further. Authenticated Users
also have access to the SQL Folder.
Could it me that it is a Run Time Version (that is what I was told) of SQL
Server? Does the client need to purchase the full version?

Non- Admin connection

I am testing an Access Database on network workstations with linked tables
to SQL Server. I set up a DSN and have no problem logged in as myself with
Admin rights to the server. But when I login as a user with no admin rights
I am denied access with this message:
Connection failed:
SQL Server State '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'dayoubunc1\Sales'.
The network server is Windows 2003 Server, the workstation is Windows 2000
Pro and the SQL Server is a runtime version which came with a Veratis backup
system.
The purpose of moving the tables to SQL Server is security. A user can
steal an Access backend, so I don't want the user to have admin rights to
use the DB. What can I do.
Thanks and God Bless,
Mark A. SamAre you sure that it is related to admin rights? Maybe you just need to add
a user named "Sales" to
the SQL Server permissions?
"Mark A. Sam" <msam@.Plan-It-Earth.Net> wrote in message
news:u2oqViHmFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I am testing an Access Database on network workstations with linked tables
> to SQL Server. I set up a DSN and have no problem logged in as myself with
> Admin rights to the server. But when I login as a user with no admin righ
ts
> I am denied access with this message:
> Connection failed:
> SQL Server State '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> 'dayoubunc1\Sales'.
>
> The network server is Windows 2003 Server, the workstation is Windows 2000
> Pro and the SQL Server is a runtime version which came with a Veratis back
up
> system.
> The purpose of moving the tables to SQL Server is security. A user can
> steal an Access backend, so I don't want the user to have admin rights to
> use the DB. What can I do.
> Thanks and God Bless,
> Mark A. Sam
>|||Hello Scot,
I don't know how I would do that. I opened Enterprise manager and tried to
add a new user but the Network users weren't available. I am very
inexperienced with SQL Server, but I think I recall from another client db
that the users network users were listed. And thinking about they, they had
many users who only had to log in and the DB worked, even through terminal
service sessions. It seems as though I only set up the DSNs on those
workstations.
God Bless,
Mark|||I tried adding full Control to the user for the SQL Server Folder as well as
the database folder, but it didn't get me any further. Authenticated Users
also have access to the SQL Folder.
Could it me that it is a Run Time Version (that is what I was told) of SQL
Server? Does the client need to purchase the full version?

Node Cluster - Fails on Network Resources

I am running a 2-node cluster for SQL Server. After powering down both
servers (passive then active), one of the nodes did not successfully join the
cluster. This node shows exclamation marks on the Network Interfaces in
Cluster Administrator. These nics are functioning correctly outside of the
cluster. The cluster log on the failed node indicates that these network
interfaces are functioning each time it tries to join the cluster. The
active node's cluster log indicates that these resources are not functioning
and removes the other node from being active.
If anyone has any ideas on how to solve this problem, your input would be
greatly appreciated.
Thanks,
Debbie
Is the NIC you have exclamation mark on Public or Private network?
Ayad
"Debbie" <Debbie@.discussions.microsoft.com> wrote in message
news:1CC9F5E6-46E3-482A-913C-B8C57692BDB2@.microsoft.com...
> I am running a 2-node cluster for SQL Server. After powering down both
> servers (passive then active), one of the nodes did not successfully join
the
> cluster. This node shows exclamation marks on the Network Interfaces in
> Cluster Administrator. These nics are functioning correctly outside of
the
> cluster. The cluster log on the failed node indicates that these network
> interfaces are functioning each time it tries to join the cluster. The
> active node's cluster log indicates that these resources are not
functioning
> and removes the other node from being active.
> If anyone has any ideas on how to solve this problem, your input would be
> greatly appreciated.
> Thanks,
> Debbie
>
|||There are three NICs, the heartbeat (crossover), private (for backups) and
our intranet. All three have the exclamation mark.
"Ayad" wrote:

> Is the NIC you have exclamation mark on Public or Private network?
> Ayad
> "Debbie" <Debbie@.discussions.microsoft.com> wrote in message
> news:1CC9F5E6-46E3-482A-913C-B8C57692BDB2@.microsoft.com...
> the
> the
> functioning
>
>
|||Check your IP settings and make sure you are using the correct subnet mask
address and network segment for each port and match each port with the other
node's port.
Was it working before or this is a new install?
Ayad
"Debbie" <Debbie@.discussions.microsoft.com> wrote in message
news:89B546EC-247D-464E-A149-6952D4AC5EC7@.microsoft.com...[vbcol=seagreen]
> There are three NICs, the heartbeat (crossover), private (for backups) and
> our intranet. All three have the exclamation mark.
> "Ayad" wrote:
join[vbcol=seagreen]
in[vbcol=seagreen]
of[vbcol=seagreen]
network[vbcol=seagreen]
The[vbcol=seagreen]
be[vbcol=seagreen]
|||Ayad,
This is not a new install. It was working before. We had to power down all
of the servers for a generator hook-up to be installed. When bringing the
cluster back up, this server failed and has failed ever since with these NIC
resource errors.
The subnets look good on the NICs.
Thanks,
Debbie
"Ayad" wrote:

> Check your IP settings and make sure you are using the correct subnet mask
> address and network segment for each port and match each port with the other
> node's port.
> Was it working before or this is a new install?
> Ayad
> "Debbie" <Debbie@.discussions.microsoft.com> wrote in message
> news:89B546EC-247D-464E-A149-6952D4AC5EC7@.microsoft.com...
> join
> in
> of
> network
> The
> be
>
>
|||Debbie,
Try Shutdown that node (server hard reboot) and power it ON again and see if
it clears your NIC issue.
Ayad
"Debbie" <Debbie@.discussions.microsoft.com> wrote in message
news:9AA7AFAC-5A77-4A71-B901-9CB4E99462ED@.microsoft.com...
> Ayad,
> This is not a new install. It was working before. We had to power down
all
> of the servers for a generator hook-up to be installed. When bringing the
> cluster back up, this server failed and has failed ever since with these
NIC[vbcol=seagreen]
> resource errors.
> The subnets look good on the NICs.
> Thanks,
> Debbie
> "Ayad" wrote:
mask[vbcol=seagreen]
other[vbcol=seagreen]
and[vbcol=seagreen]
both[vbcol=seagreen]
successfully[vbcol=seagreen]
Interfaces[vbcol=seagreen]
outside[vbcol=seagreen]
would[vbcol=seagreen]
|||Ayad,
The hard reboot did not clear up the problem. I am thinking of removing
this node from the cluster and then readding it to the cluster to see if that
clears up the problem.
Thanks,
Debbie
"Ayad" wrote:

> Debbie,
> Try Shutdown that node (server hard reboot) and power it ON again and see if
> it clears your NIC issue.
> Ayad
> "Debbie" <Debbie@.discussions.microsoft.com> wrote in message
> news:9AA7AFAC-5A77-4A71-B901-9CB4E99462ED@.microsoft.com...
> all
> NIC
> mask
> other
> and
> both
> successfully
> Interfaces
> outside
> would
>
>

no such interface supported virus

I'm running an access 2000 front end with a slq server 2000 back end on a lo
cal network. All of the sudden one workstation couldn't connect to the serv
er. So after trying several things I think I've came to the correct conclus
ion. I believe that the ma
chine was infected by a virus that was missed by two different scanners. I
think its a hijack virus that takes control of sql when its trying to connec
t to the server using the server name. Its very odd and isn't detected by s
canners. A temp. fix is to
just use the ip of the server to connect and then it works. Also if I try a
nd ping the server by name it doesn't get a return however if I use the elon
gated full name of the server with domain its fine. Any ideas suggestions c
lues?Is the server running a Personal Firewall?
Are you connecting via TCP or Named Pipes?
What are you using for Name Resolution of the server?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.