Can't find Reporting Service?

I wanted to add Reports Service to my sql express. I downloaded the SQLEXPR_ADV.EXE and also Edition Toolkit SP1. But can't see the option to install Report service.

Any help please.

Juvan

Reporting Services is included with SQL Express Advanced. Launch this installer and you will see an option to install it during the "Feature Selection" dialog.

Thanks,
Sam Lester (MSFT)

Can't find Reporting Service?

I wanted to add Reports Service to my sql express. I downloaded the SQLEXPR_ADV.EXE and also Edition Toolkit SP1. But can't see the option to install Report service.

Any help please.

Juvan

Reporting Services is included with SQL Express Advanced. Launch this installer and you will see an option to install it during the "Feature Selection" dialog.

Thanks,
Sam Lester (MSFT)

Can't find Microsoft.ReportingServices.ReportRendering assembly

Hi,
I have installed Microsoft SQL Server 2000 Reporting services
Evaluation Edition. I am trying to wrtie a custom rendering service.
But to implement the
IRenderingExtension interface i need to reference
Microsoft.ReportingServices.ReportRendering assembly. I am unable to
find it any of the installed directories. Can you please tell me how
to go about this?
Any help will be appreciated.
Regards
VijaykumarHi,
I don't think such a file exists.
You have specific dlls for rendering extensiosn for example :
Microsoft.reportingservices.excelrendering,
Microsoft.reportingservices.csvrendering.
You don't have a dll for a report rendering. Reports are rendered through
rendering extensions (excel, pdf, csv, etc...
Cédric
"Vijaykumar" <vijaykumarkarekar@.hotmail.com> wrote in message
news:63da8fe5.0408152338.88b9e0b@.posting.google.com...
> Hi,
> I have installed Microsoft SQL Server 2000 Reporting services
> Evaluation Edition. I am trying to wrtie a custom rendering service.
> But to implement the
> IRenderingExtension interface i need to reference
> Microsoft.ReportingServices.ReportRendering assembly. I am unable to
> find it any of the installed directories. Can you please tell me how
> to go about this?
> Any help will be appreciated.
> Regards
> Vijaykumar|||Hi Vijaykumar:
The type IRenderingExtension exists in the
Microsoft.ReportingServices.ReportRendering *namespace*.
The assembly for the type is actually
Microsoft.ReportingServices.Processing.dll.
HTH,
--
Scott
http://www.OdeToCode.com
On 16 Aug 2004 00:38:26 -0700, vijaykumarkarekar@.hotmail.com
(Vijaykumar) wrote:
>Hi,
>I have installed Microsoft SQL Server 2000 Reporting services
>Evaluation Edition. I am trying to wrtie a custom rendering service.
>But to implement the
>IRenderingExtension interface i need to reference
>Microsoft.ReportingServices.ReportRendering assembly. I am unable to
>find it any of the installed directories. Can you please tell me how
>to go about this?
>Any help will be appreciated.
>Regards
>Vijaykumar|||You need to reference the ReportRendering namespace, which is contained in
the same assembly as the ReportProcessing namespace:
Microsoft.ReportingServices.Processing.dll
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Vijaykumar" <vijaykumarkarekar@.hotmail.com> wrote in message
news:63da8fe5.0408152338.88b9e0b@.posting.google.com...
> Hi,
> I have installed Microsoft SQL Server 2000 Reporting services
> Evaluation Edition. I am trying to wrtie a custom rendering service.
> But to implement the
> IRenderingExtension interface i need to reference
> Microsoft.ReportingServices.ReportRendering assembly. I am unable to
> find it any of the installed directories. Can you please tell me how
> to go about this?
> Any help will be appreciated.
> Regards
> Vijaykumar|||"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message news:<#uOoZ$5gEHA.1656@.TK2MSFTNGP09.phx.gbl>...
> You need to reference the ReportRendering namespace, which is contained in
> the same assembly as the ReportProcessing namespace:
> Microsoft.ReportingServices.Processing.dll
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Vijaykumar" <vijaykumarkarekar@.hotmail.com> wrote in message
> news:63da8fe5.0408152338.88b9e0b@.posting.google.com...
> > Hi,
> > I have installed Microsoft SQL Server 2000 Reporting services
> > Evaluation Edition. I am trying to wrtie a custom rendering service.
> > But to implement the
> > IRenderingExtension interface i need to reference
> > Microsoft.ReportingServices.ReportRendering assembly. I am unable to
> > find it any of the installed directories. Can you please tell me how
> > to go about this?
> >
> > Any help will be appreciated.
> >
> > Regards
> > Vijaykumar
Thnaks Robert I got it. Let me try to implement the custom rendering.

Can't export report to CSV,XMl correctly, sql 2005 reporting service

Hi all,

I am developing reports using sql2005 report service. I can export reports in excel and pdf format, but can't export to csv and xml correctly.

The exported csv and xml files only contain some thing like the textbox,..., but no report content are there.

Anybody can help? thanks in advance.

BTW, all reports are matrix, is martrix can cause some issues?

Hi,

For most items on your report, you can define how it needs to be rendered to XML. For example the xml output for an item in a matrix can be set as follow:

select the item in the matrix|||

Thanks, Greert.

Your reply is really helpful. Now I know how to export report in xml format. But, how about CSV? I still can't export report to csv.

Thanks again

|||

Hi,

The same goes for CSV. For example if you set the Output of a column to No, you will see that the column is not included in the CSV file.

Greetz,

Geert

Geert Verhoeven
Consultant @. Ausy Belgium

My Personal Blog

|||Hi Geert,

Thanks a lot.

When I set th output of a column to yes, it works. Before, the the output of column was set to Auto.

Cant download Service Pack 3

Hi,

I have been tring to download MS SQL Service Pack 3 for days now from microsoft.. but the site won't respond or the download operation will failed at the middle.. I have a fast connection so I don't think it is a connection problem ..

is there any other place I can download it from ??Howdy

Try microsoft in another country....

Cant connect to server

Hey,
I've had a server running for the last couple of months and earlier today it died, i managed to get Service Pack 2 on it, and now it will start but nothing will interface with it,
especially not coldfusion

Coldfusion says
SQLException occurred in JDBCPool while attempting to connect, please check your username, password, URL, and other connectivity info.

though when i use ODBC and i set a new DSN
if i use Windows Authentication, it goes through, and i test the source and it says succesful
though if i try and use SQL Authentication it says

Connection Failed :
SQL State : '28000'
SQL Server Error : 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for 'username'. Reason : User not associated with a trusted SQL connection

any ideas?Is your sql instance set up for windows only authentification or mixed-mode ?|||Originally posted by rnealejr
Is your sql instance set up for windows only authentification or mixed-mode ?

its ok
sorted it now, it was for SQL Authentication, not mixed or windows

i rebuilt the registry and it worked

Can't connect to named instance from clients

I created a second SQL Server 2000 instance in my computer. I started the
service using the service manager and registered it successfully to the
local Enterprise Manager.
When I try to register the instance to a remote Enterprise Manager or when I
try to create a dsn from another machine to the new instance I get a "SQL
Server is unavailable or does not exist" error.
Sergio Florez M.
Miembro activo www.AlianzaDev.net
El que persevera insiste
Medelln, Colombia
DCE 4
How are you connecting to the instance?
Servername\InstanceName?
"Sergio Florez M." wrote:

> I created a second SQL Server 2000 instance in my computer. I started the
> service using the service manager and registered it successfully to the
> local Enterprise Manager.
> When I try to register the instance to a remote Enterprise Manager or when I
> try to create a dsn from another machine to the new instance I get a "SQL
> Server is unavailable or does not exist" error.
> --
> Sergio Florez M.
> Miembro activo www.AlianzaDev.net
> El que persevera insiste
> MedellXn, Colombia
> DCE 4
>
>

Can't connect to named instance from clients

I created a second SQL Server 2000 instance in my computer. I started the
service using the service manager and registered it successfully to the
local Enterprise Manager.
When I try to register the instance to a remote Enterprise Manager or when I
try to create a dsn from another machine to the new instance I get a "SQL
Server is unavailable or does not exist" error.
Sergio Florez M.
Miembro activo www.AlianzaDev.net
El que persevera insiste
Medelln, Colombia
DCE 4How are you connecting to the instance?
Servername\InstanceName?
"Sergio Florez M." wrote:

> I created a second SQL Server 2000 instance in my computer. I started the
> service using the service manager and registered it successfully to the
> local Enterprise Manager.
> When I try to register the instance to a remote Enterprise Manager or when
I
> try to create a dsn from another machine to the new instance I get a "SQL
> Server is unavailable or does not exist" error.
> --
> Sergio Florez M.
> Miembro activo www.AlianzaDev.net
> El que persevera insiste
> Medell_n, Colombia
> DCE 4
>
>

Can't Connect to Multiple SQL Instances over the Internet with SQL Browser Service

I recently setup mutliple instances of SQL Server Express at my office. I have 1 default instance, and two named instances. I can connect to the named instance of the default port of 1433 with Microsoft SQL Management Studio Express, however the other instances on dynamic TCP ports can not be accessed by the instance name over the internet. I have to specify the dynamic TCP port in this form: xxx.uconn.edu/SQLTEST, Port number. My current thinking is that the SQL Browser service should tell Management Studio Express what dynamic port number each SQL instance is listening to. Any ideas?

hi,

CTJohn23 wrote:

I recently setup mutliple instances of SQL Server Express at my office. I have 1 default instance, and two named instances. I can connect to the named instance of the default port of 1433 with Microsoft SQL Management Studio Express,

TCP/IP 1433 is usually reserved for the default instance...

however the other instances on dynamic TCP ports can not be accessed by the instance name over the internet. I have to specify the dynamic TCP port in this form: xxx.uconn.edu/SQLTEST, Port number. My current thinking is that the SQL Browser service should tell Management Studio Express what dynamic port number each SQL instance is listening to. Any ideas?

the SQLBrowser can not "work" over the internet in that way... all enlistment for instance presence are available via an UDP broadcast call on the local area, when no firewall action is involved...

don't know if the "tool" still relies on SQLBrowseConnect ODBC function, like SQL Server 7.0 and 2000 ListAvailableServer used it, an ODBC function (SQLBrowseConnect()) provided by ODBC libraries installed by Mdac;
this is a mechanism working in broadcast calls, which result never are conclusive and consistent, becouse results are influenced of various servers's answer states, answer time, etc.

Until Mdac 2.5, SQLBrowseConnect function works based on a NetBIOS broadcast, on which SQL Servers respond (Default protocol for SQL Server 7.0), while in SQL Server 2000 the rules changed, because the default client protocol changed to TCP/IP and now a UDP broadcast is used, beside a NetBIOS broadcast, listening on port 1434:
which is using a UDP broadcast on port 1434, if instance do not listen or not respond on time they will not be part of the enumeration.

Some basic rules for 7.0 are:
- SQL Servers have to be running on Windows NT or Windows 2000 and have to listen on Named Pipes, that is why in 7.0 Windows 9x SQL Servers will never show up, because they do not listen on Named Pipes.
- The SQL Server has to be running in order to respond on the broadcast. There is a gray window of 15 minutes after shutdown, where a browse master in the domain may respond on the broadcast and answer.
- If you have routers in your network, that do not pass on NetBIOS broadcasts, this might limit your scope of the broadcast.
- Only servers within the same NT domain (or trust) will get enumerated.

In SQL Server 2000 using MDAC 2.6 this changes a little, because now the default protocol has been changed to be TCP/IP sockets and instead of a NetBIOS broadcast, they use a TCP UDP to detect the servers. The same logic still applies roughly.
- SQL Server that are running
- SQL Server that listening on TCP/IP
- Running on Windows NT or Windows 2000 or Windows 9x
- If you use routers and these are configured not to pass UDP broadcasts, only machines within the same subnet show up.

Upgrading to Service Pack 2 of SQL Server 2000 is required in order to have .ListAvailableServer method to work properly, becouse precding release of Sql-DMO Components of Sql Server 2000 present a bug in this area.

Courtesy of Mr. Gert E.R. Drapers
further Information at
http://sqldev.net/misc.htm

The Service Pack 3a introduced some new amenity in order to prevent MSDE 2000 to be hit by Internet worms like Slammer and Saphire virus and to increase security, so that Microsoft decided to default for disabling SuperSockets Network Protocols on new MSDE 2000 installation.
Instances of SQL Server 2000 SP3a or MSDE 2000 SP3a will stop listening on UDP port 1434 when they are configured to not listen on any network protocols. This will stop enlisting these servers.

Can't connect remotely when SQL services running as a domain account

I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email alerts. I
configured the sql service and sql agent service to run as a domain account.
I made that account a member of the administrators group on the SQL server,
and restarted the services. Everything looked fine. The problem is, some of
my remote applications cannot connect when it is running as a domain
account, but they are fine when it is running as a local system account. On
a remote Microsoft WSUS server, it breaks when the SQL services on the SQL
server use a domain account. Osql on the remote box generates this:
Cannot generate SSPI context
I did try to research this before posting here, but I couldn't find anything
that described this problem. Everything was referring to PCs connecting from
a different domain. That is not the case here.
Thanks,
MatthewCannot Generate SSPI context is almost always related to there not being a
Service Principal Name defined for that server, account and port in a
Kerberos environment.
Domain accounts do not create an SPN, whereas Domain Admins and Local System
do.
Test this by making (temporarily) your startup account a domain admin and
the resetting in in SQL Enterprise Manager. restart and test connectivity.
If it connects, have your domain admin (must be a domain admin) create an
SPN for the MSSQLSvc in Active Directory.
See the Books Online article "Security Account Delegation" for formot of
what the resulting SPN should look like.
Also, make sure the SQL Server is listening on TCP...make that your first
step.
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email alerts.
> I configured the sql service and sql agent service to run as a domain
> account. I made that account a member of the administrators group on the
> SQL server, and restarted the services. Everything looked fine. The
> problem is, some of my remote applications cannot connect when it is
> running as a domain account, but they are fine when it is running as a
> local system account. On a remote Microsoft WSUS server, it breaks when
> the SQL services on the SQL server use a domain account. Osql on the
> remote box generates this:
> Cannot generate SSPI context
> I did try to research this before posting here, but I couldn't find
> anything that described this problem. Everything was referring to PCs
> connecting from a different domain. That is not the case here.
> Thanks,
> Matthew
>|||I am the domain admin, so that won't be a problem. As soon as some of the
current activity dies down, I will try this. Thanks!
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Cannot Generate SSPI context is almost always related to there not being a
> Service Principal Name defined for that server, account and port in a
> Kerberos environment.
> Domain accounts do not create an SPN, whereas Domain Admins and Local
> System do.
> Test this by making (temporarily) your startup account a domain admin and
> the resetting in in SQL Enterprise Manager. restart and test
> connectivity.
> If it connects, have your domain admin (must be a domain admin) create an
> SPN for the MSSQLSvc in Active Directory.
> See the Books Online article "Security Account Delegation" for formot of
> what the resulting SPN should look like.
> Also, make sure the SQL Server is listening on TCP...make that your first
> step.
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>|||Thanks! Adding the SPN took care of it. I thought I was there, but now I'm
having problems configuring the alerts. Outlook 2003 SP2 is installed. I
logged in with he SQL service account, and setup the MAPI profile. That
worked fine. When I set up an operator logged in as the service account,
clicking Test email generates this error:
http://img167.imageshack.us/my.php?...sqlerroran3.png
If I log in as my self, it acts like it went through when I click test, but
no email is generated.
Any ideas?
Thanks again for your help.
-Matthew
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Cannot Generate SSPI context is almost always related to there not being a
> Service Principal Name defined for that server, account and port in a
> Kerberos environment.
> Domain accounts do not create an SPN, whereas Domain Admins and Local
> System do.
> Test this by making (temporarily) your startup account a domain admin and
> the resetting in in SQL Enterprise Manager. restart and test
> connectivity.
> If it connects, have your domain admin (must be a domain admin) create an
> SPN for the MSSQLSvc in Active Directory.
> See the Books Online article "Security Account Delegation" for formot of
> what the resulting SPN should look like.
> Also, make sure the SQL Server is listening on TCP...make that your first
> step.
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>|||All I can tell you is that SQL mail is profiel specific...could be a
permissions issue on the profile itself?
That's not my area :-)
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
message news:eMiLlw33GHA.5000@.TK2MSFTNGP02.phx.gbl...
> Thanks! Adding the SPN took care of it. I thought I was there, but now I'm
> having problems configuring the alerts. Outlook 2003 SP2 is installed. I
> logged in with he SQL service account, and setup the MAPI profile. That
> worked fine. When I set up an operator logged in as the service account,
> clicking Test email generates this error:
> http://img167.imageshack.us/my.php?...sqlerroran3.png
> If I log in as my self, it acts like it went through when I click test,
> but no email is generated.
> Any ideas?
> Thanks again for your help.
> -Matthew
> "Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
> news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
>|||This thing is baffling. I read a couple posts that just the 'Test' button
has issues. I scheduled some maintenance to run at 4 AM last night. It ran,
sent me the results, and the log indicated the job failed because the last
step, the email, failed.
The job failed. The Job was invoked by Schedule 4 (Schedule 1). The last
step to run was step 1 (Step 1). NOTE: Failed to notify 'SQL Alerts' via
email.
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:uFBi8n43GHA.4924@.TK2MSFTNGP05.phx.gbl...
> All I can tell you is that SQL mail is profiel specific...could be a
> permissions issue on the profile itself?
> That's not my area :-)
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:eMiLlw33GHA.5000@.TK2MSFTNGP02.phx.gbl...
>

Can't connect remotely when SQL services running as a domain account

I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email alerts. I
configured the sql service and sql agent service to run as a domain account.
I made that account a member of the administrators group on the SQL server,
and restarted the services. Everything looked fine. The problem is, some of
my remote applications cannot connect when it is running as a domain
account, but they are fine when it is running as a local system account. On
a remote Microsoft WSUS server, it breaks when the SQL services on the SQL
server use a domain account. Osql on the remote box generates this:
Cannot generate SSPI context
I did try to research this before posting here, but I couldn't find anything
that described this problem. Everything was referring to PCs connecting from
a different domain. That is not the case here.
Thanks,
Matthew
Cannot Generate SSPI context is almost always related to there not being a
Service Principal Name defined for that server, account and port in a
Kerberos environment.
Domain accounts do not create an SPN, whereas Domain Admins and Local System
do.
Test this by making (temporarily) your startup account a domain admin and
the resetting in in SQL Enterprise Manager. restart and test connectivity.
If it connects, have your domain admin (must be a domain admin) create an
SPN for the MSSQLSvc in Active Directory.
See the Books Online article "Security Account Delegation" for formot of
what the resulting SPN should look like.
Also, make sure the SQL Server is listening on TCP...make that your first
step.
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email alerts.
> I configured the sql service and sql agent service to run as a domain
> account. I made that account a member of the administrators group on the
> SQL server, and restarted the services. Everything looked fine. The
> problem is, some of my remote applications cannot connect when it is
> running as a domain account, but they are fine when it is running as a
> local system account. On a remote Microsoft WSUS server, it breaks when
> the SQL services on the SQL server use a domain account. Osql on the
> remote box generates this:
> Cannot generate SSPI context
> I did try to research this before posting here, but I couldn't find
> anything that described this problem. Everything was referring to PCs
> connecting from a different domain. That is not the case here.
> Thanks,
> Matthew
>
|||I am the domain admin, so that won't be a problem. As soon as some of the
current activity dies down, I will try this. Thanks!
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Cannot Generate SSPI context is almost always related to there not being a
> Service Principal Name defined for that server, account and port in a
> Kerberos environment.
> Domain accounts do not create an SPN, whereas Domain Admins and Local
> System do.
> Test this by making (temporarily) your startup account a domain admin and
> the resetting in in SQL Enterprise Manager. restart and test
> connectivity.
> If it connects, have your domain admin (must be a domain admin) create an
> SPN for the MSSQLSvc in Active Directory.
> See the Books Online article "Security Account Delegation" for formot of
> what the resulting SPN should look like.
> Also, make sure the SQL Server is listening on TCP...make that your first
> step.
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>
|||Thanks! Adding the SPN took care of it. I thought I was there, but now I'm
having problems configuring the alerts. Outlook 2003 SP2 is installed. I
logged in with he SQL service account, and setup the MAPI profile. That
worked fine. When I set up an operator logged in as the service account,
clicking Test email generates this error:
http://img167.imageshack.us/my.php?i...qlerroran3.png
If I log in as my self, it acts like it went through when I click test, but
no email is generated.
Any ideas?
Thanks again for your help.
-Matthew
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Cannot Generate SSPI context is almost always related to there not being a
> Service Principal Name defined for that server, account and port in a
> Kerberos environment.
> Domain accounts do not create an SPN, whereas Domain Admins and Local
> System do.
> Test this by making (temporarily) your startup account a domain admin and
> the resetting in in SQL Enterprise Manager. restart and test
> connectivity.
> If it connects, have your domain admin (must be a domain admin) create an
> SPN for the MSSQLSvc in Active Directory.
> See the Books Online article "Security Account Delegation" for formot of
> what the resulting SPN should look like.
> Also, make sure the SQL Server is listening on TCP...make that your first
> step.
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>
|||All I can tell you is that SQL mail is profiel specific...could be a
permissions issue on the profile itself?
That's not my area :-)
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
message news:eMiLlw33GHA.5000@.TK2MSFTNGP02.phx.gbl...
> Thanks! Adding the SPN took care of it. I thought I was there, but now I'm
> having problems configuring the alerts. Outlook 2003 SP2 is installed. I
> logged in with he SQL service account, and setup the MAPI profile. That
> worked fine. When I set up an operator logged in as the service account,
> clicking Test email generates this error:
> http://img167.imageshack.us/my.php?i...qlerroran3.png
> If I log in as my self, it acts like it went through when I click test,
> but no email is generated.
> Any ideas?
> Thanks again for your help.
> -Matthew
> "Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
> news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
>
|||This thing is baffling. I read a couple posts that just the 'Test' button
has issues. I scheduled some maintenance to run at 4 AM last night. It ran,
sent me the results, and the log indicated the job failed because the last
step, the email, failed.
The job failed. The Job was invoked by Schedule 4 (Schedule 1). The last
step to run was step 1 (Step 1). NOTE: Failed to notify 'SQL Alerts' via
email.
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:uFBi8n43GHA.4924@.TK2MSFTNGP05.phx.gbl...
> All I can tell you is that SQL mail is profiel specific...could be a
> permissions issue on the profile itself?
> That's not my area :-)
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:eMiLlw33GHA.5000@.TK2MSFTNGP02.phx.gbl...
>

Can't connect remotely when SQL services running as a domain account

I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email alerts. I
configured the sql service and sql agent service to run as a domain account.
I made that account a member of the administrators group on the SQL server,
and restarted the services. Everything looked fine. The problem is, some of
my remote applications cannot connect when it is running as a domain
account, but they are fine when it is running as a local system account. On
a remote Microsoft WSUS server, it breaks when the SQL services on the SQL
server use a domain account. Osql on the remote box generates this:
Cannot generate SSPI context
I did try to research this before posting here, but I couldn't find anything
that described this problem. Everything was referring to PCs connecting from
a different domain. That is not the case here.
Thanks,
MatthewCannot Generate SSPI context is almost always related to there not being a
Service Principal Name defined for that server, account and port in a
Kerberos environment.
Domain accounts do not create an SPN, whereas Domain Admins and Local System
do.
Test this by making (temporarily) your startup account a domain admin and
the resetting in in SQL Enterprise Manager. restart and test connectivity.
If it connects, have your domain admin (must be a domain admin) create an
SPN for the MSSQLSvc in Active Directory.
See the Books Online article "Security Account Delegation" for formot of
what the resulting SPN should look like.
Also, make sure the SQL Server is listening on TCP...make that your first
step.
--
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email alerts.
> I configured the sql service and sql agent service to run as a domain
> account. I made that account a member of the administrators group on the
> SQL server, and restarted the services. Everything looked fine. The
> problem is, some of my remote applications cannot connect when it is
> running as a domain account, but they are fine when it is running as a
> local system account. On a remote Microsoft WSUS server, it breaks when
> the SQL services on the SQL server use a domain account. Osql on the
> remote box generates this:
> Cannot generate SSPI context
> I did try to research this before posting here, but I couldn't find
> anything that described this problem. Everything was referring to PCs
> connecting from a different domain. That is not the case here.
> Thanks,
> Matthew
>|||I am the domain admin, so that won't be a problem. As soon as some of the
current activity dies down, I will try this. Thanks!
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Cannot Generate SSPI context is almost always related to there not being a
> Service Principal Name defined for that server, account and port in a
> Kerberos environment.
> Domain accounts do not create an SPN, whereas Domain Admins and Local
> System do.
> Test this by making (temporarily) your startup account a domain admin and
> the resetting in in SQL Enterprise Manager. restart and test
> connectivity.
> If it connects, have your domain admin (must be a domain admin) create an
> SPN for the MSSQLSvc in Active Directory.
> See the Books Online article "Security Account Delegation" for formot of
> what the resulting SPN should look like.
> Also, make sure the SQL Server is listening on TCP...make that your first
> step.
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators group
>> on the SQL server, and restarted the services. Everything looked fine.
>> The problem is, some of my remote applications cannot connect when it is
>> running as a domain account, but they are fine when it is running as a
>> local system account. On a remote Microsoft WSUS server, it breaks when
>> the SQL services on the SQL server use a domain account. Osql on the
>> remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>|||Thanks! Adding the SPN took care of it. I thought I was there, but now I'm
having problems configuring the alerts. Outlook 2003 SP2 is installed. I
logged in with he SQL service account, and setup the MAPI profile. That
worked fine. When I set up an operator logged in as the service account,
clicking Test email generates this error:
http://img167.imageshack.us/my.php?image=sqlerroran3.png
If I log in as my self, it acts like it went through when I click test, but
no email is generated.
Any ideas?
Thanks again for your help.
-Matthew
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Cannot Generate SSPI context is almost always related to there not being a
> Service Principal Name defined for that server, account and port in a
> Kerberos environment.
> Domain accounts do not create an SPN, whereas Domain Admins and Local
> System do.
> Test this by making (temporarily) your startup account a domain admin and
> the resetting in in SQL Enterprise Manager. restart and test
> connectivity.
> If it connects, have your domain admin (must be a domain admin) create an
> SPN for the MSSQLSvc in Active Directory.
> See the Books Online article "Security Account Delegation" for formot of
> what the resulting SPN should look like.
> Also, make sure the SQL Server is listening on TCP...make that your first
> step.
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators group
>> on the SQL server, and restarted the services. Everything looked fine.
>> The problem is, some of my remote applications cannot connect when it is
>> running as a domain account, but they are fine when it is running as a
>> local system account. On a remote Microsoft WSUS server, it breaks when
>> the SQL services on the SQL server use a domain account. Osql on the
>> remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>|||All I can tell you is that SQL mail is profiel specific...could be a
permissions issue on the profile itself?
That's not my area :-)
--
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
message news:eMiLlw33GHA.5000@.TK2MSFTNGP02.phx.gbl...
> Thanks! Adding the SPN took care of it. I thought I was there, but now I'm
> having problems configuring the alerts. Outlook 2003 SP2 is installed. I
> logged in with he SQL service account, and setup the MAPI profile. That
> worked fine. When I set up an operator logged in as the service account,
> clicking Test email generates this error:
> http://img167.imageshack.us/my.php?image=sqlerroran3.png
> If I log in as my self, it acts like it went through when I click test,
> but no email is generated.
> Any ideas?
> Thanks again for your help.
> -Matthew
> "Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
> news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
>> Cannot Generate SSPI context is almost always related to there not being
>> a Service Principal Name defined for that server, account and port in a
>> Kerberos environment.
>> Domain accounts do not create an SPN, whereas Domain Admins and Local
>> System do.
>> Test this by making (temporarily) your startup account a domain admin and
>> the resetting in in SQL Enterprise Manager. restart and test
>> connectivity.
>> If it connects, have your domain admin (must be a domain admin) create an
>> SPN for the MSSQLSvc in Active Directory.
>> See the Books Online article "Security Account Delegation" for formot of
>> what the resulting SPN should look like.
>> Also, make sure the SQL Server is listening on TCP...make that your first
>> step.
>> --
>> Kevin Hill
>> 3NF Consulting
>> www.3nf-inc.com/NewsGroups.htm
>>
>>
>> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
>> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators group
>> on the SQL server, and restarted the services. Everything looked fine.
>> The problem is, some of my remote applications cannot connect when it is
>> running as a domain account, but they are fine when it is running as a
>> local system account. On a remote Microsoft WSUS server, it breaks when
>> the SQL services on the SQL server use a domain account. Osql on the
>> remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>>
>|||This thing is baffling. I read a couple posts that just the 'Test' button
has issues. I scheduled some maintenance to run at 4 AM last night. It ran,
sent me the results, and the log indicated the job failed because the last
step, the email, failed.
The job failed. The Job was invoked by Schedule 4 (Schedule 1). The last
step to run was step 1 (Step 1). NOTE: Failed to notify 'SQL Alerts' via
email.
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:uFBi8n43GHA.4924@.TK2MSFTNGP05.phx.gbl...
> All I can tell you is that SQL mail is profiel specific...could be a
> permissions issue on the profile itself?
> That's not my area :-)
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:eMiLlw33GHA.5000@.TK2MSFTNGP02.phx.gbl...
>> Thanks! Adding the SPN took care of it. I thought I was there, but now
>> I'm having problems configuring the alerts. Outlook 2003 SP2 is
>> installed. I logged in with he SQL service account, and setup the MAPI
>> profile. That worked fine. When I set up an operator logged in as the
>> service account, clicking Test email generates this error:
>> http://img167.imageshack.us/my.php?image=sqlerroran3.png
>> If I log in as my self, it acts like it went through when I click test,
>> but no email is generated.
>> Any ideas?
>> Thanks again for your help.
>> -Matthew
>> "Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
>> news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
>> Cannot Generate SSPI context is almost always related to there not being
>> a Service Principal Name defined for that server, account and port in a
>> Kerberos environment.
>> Domain accounts do not create an SPN, whereas Domain Admins and Local
>> System do.
>> Test this by making (temporarily) your startup account a domain admin
>> and the resetting in in SQL Enterprise Manager. restart and test
>> connectivity.
>> If it connects, have your domain admin (must be a domain admin) create
>> an SPN for the MSSQLSvc in Active Directory.
>> See the Books Online article "Security Account Delegation" for formot of
>> what the resulting SPN should look like.
>> Also, make sure the SQL Server is listening on TCP...make that your
>> first step.
>> --
>> Kevin Hill
>> 3NF Consulting
>> www.3nf-inc.com/NewsGroups.htm
>>
>>
>> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
>> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators
>> group on the SQL server, and restarted the services. Everything looked
>> fine. The problem is, some of my remote applications cannot connect
>> when it is running as a domain account, but they are fine when it is
>> running as a local system account. On a remote Microsoft WSUS server,
>> it breaks when the SQL services on the SQL server use a domain account.
>> Osql on the remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>>
>>
>