install SQL on WinXP: sp3

Showing posts with label sp3. Show all posts

Thursday, March 29, 2012

Can not install Reporting Services, Help!

Hi,
I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm trying
to install the MS SQL Server Reporting Services that is in the MSDN of April
2004. I also have Visual studio.net installed.
So when I run the CD all goes well until you specify the database for the
reporting server and then I get the following error:
"This edition of the Report Server Database is not supported on the edition
of SQL Server 2000 you have chosen. Please choose on that matches the
requirements."
MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
Developer edition.
What does this mean, any comments or feedback will be greately appreciated.
- SergioI would verify that you are running the developer addition. You can do that
by running this SELECT statement on your XP machine:
SELECT SERVERPROPERTY ('edition')
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"SD" <npspam@.nowhere.net> wrote in message
news:f000323c8d8a00f8f3a9e2a81b3d483d@.ne
ws.teranews.com...
> Hi,
> I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
trying
> to install the MS SQL Server Reporting Services that is in the MSDN of
April
> 2004. I also have Visual studio.net installed.
> So when I run the CD all goes well until you specify the database for the
> reporting server and then I get the following error:
> "This edition of the Report Server Database is not supported on the
edition
> of SQL Server 2000 you have chosen. Please choose on that matches the
> requirements."
> MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> Developer edition.
> What does this mean, any comments or feedback will be greately
appreciated.
> - Sergio
>|||Ha!
I wasn't for some stupid reason I was running the personal edition. Thanks
for your help, I would still be wasting time if I hadn't followed your
suggestion.
Thank you a heap.
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> I would verify that you are running the developer addition. You can do
that
> by running this SELECT statement on your XP machine:
> SELECT SERVERPROPERTY ('edition')
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "SD" <npspam@.nowhere.net> wrote in message
> news:f000323c8d8a00f8f3a9e2a81b3d483d@.ne
ws.teranews.com...
> trying
> April
the[vbcol=seagreen]
> edition
> appreciated.
>|||I am running SQL Server developer and got the same message. However, I
continued with the installation and it works fine. That is, it works
in VS.NET 2003. I can create new "business intelligence" projects.
"SD" <npspam@.nowhere.net> wrote in message news:<ab8fe521601065edf8fa050f7602dbb6@.news.teran
ews.com>...[vbcol=seagreen]
> Ha!
> I wasn't for some stupid reason I was running the personal edition. Thanks
> for your help, I would still be wasting time if I hadn't followed your
> suggestion.
> Thank you a heap.
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> that
> --
> --
> trying
> April
> the
> edition
> appreciated.

Can not install Reporting Services, Help!

Hi,
I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm trying
to install the MS SQL Server Reporting Services that is in the MSDN of April
2004. I also have Visual studio.net installed.
So when I run the CD all goes well until you specify the database for the
reporting server and then I get the following error:
"This edition of the Report Server Database is not supported on the edition
of SQL Server 2000 you have chosen. Please choose on that matches the
requirements."
MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
Developer edition.
What does this mean, any comments or feedback will be greately appreciated.
- Sergio
I would verify that you are running the developer addition. You can do that
by running this SELECT statement on your XP machine:
SELECT SERVERPROPERTY ('edition')
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"SD" <npspam@.nowhere.net> wrote in message
news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> Hi,
> I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
trying
> to install the MS SQL Server Reporting Services that is in the MSDN of
April
> 2004. I also have Visual studio.net installed.
> So when I run the CD all goes well until you specify the database for the
> reporting server and then I get the following error:
> "This edition of the Report Server Database is not supported on the
edition
> of SQL Server 2000 you have chosen. Please choose on that matches the
> requirements."
> MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> Developer edition.
> What does this mean, any comments or feedback will be greately
appreciated.
> - Sergio
>
|||Ha!
I wasn't for some stupid reason I was running the personal edition. Thanks
for your help, I would still be wasting time if I hadn't followed your
suggestion.
Thank you a heap.
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> I would verify that you are running the developer addition. You can do
that
> by running this SELECT statement on your XP machine:
> SELECT SERVERPROPERTY ('edition')
> --
> ----
--
> ----
--[vbcol=seagreen]
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "SD" <npspam@.nowhere.net> wrote in message
> news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> trying
> April
the
> edition
> appreciated.
>
|||I am running SQL Server developer and got the same message. However, I
continued with the installation and it works fine. That is, it works
in VS.NET 2003. I can create new "business intelligence" projects.
"SD" <npspam@.nowhere.net> wrote in message news:<ab8fe521601065edf8fa050f7602dbb6@.news.terane ws.com>...[vbcol=seagreen]
> Ha!
> I wasn't for some stupid reason I was running the personal edition. Thanks
> for your help, I would still be wasting time if I hadn't followed your
> suggestion.
> Thank you a heap.
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> that
> --
> --
> trying
> April
> the
> edition
> appreciated.
sql

Can not install Reporting Services, Help!

Hi,

I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm trying
to install the MS SQL Server Reporting Services that is in the MSDN of April
2004. I also have Visual studio.net installed.

So when I run the CD all goes well until you specify the database for the
reporting server and then I get the following error:

"This edition of the Report Server Database is not supported on the edition
of SQL Server 2000 you have chosen. Please choose on that matches the
requirements."

MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
Developer edition.

What does this mean, any comments or feedback will be greately appreciated.

- SergioI would verify that you are running the developer addition. You can do that
by running this SELECT statement on your XP machine:

SELECT SERVERPROPERTY ('edition')

-----------------------
-----------------------
--

Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"SD" <npspam@.nowhere.net> wrote in message
news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> Hi,
> I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
trying
> to install the MS SQL Server Reporting Services that is in the MSDN of
April
> 2004. I also have Visual studio.net installed.
> So when I run the CD all goes well until you specify the database for the
> reporting server and then I get the following error:
> "This edition of the Report Server Database is not supported on the
edition
> of SQL Server 2000 you have chosen. Please choose on that matches the
> requirements."
> MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> Developer edition.
> What does this mean, any comments or feedback will be greately
appreciated.
> - Sergio|||Ha!

I wasn't for some stupid reason I was running the personal edition. Thanks
for your help, I would still be wasting time if I hadn't followed your
suggestion.

Thank you a heap.

"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> I would verify that you are running the developer addition. You can do
that
> by running this SELECT statement on your XP machine:
> SELECT SERVERPROPERTY ('edition')
> --
> -----------------------
--
> -----------------------
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "SD" <npspam@.nowhere.net> wrote in message
> news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> > Hi,
> > I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
> trying
> > to install the MS SQL Server Reporting Services that is in the MSDN of
> April
> > 2004. I also have Visual studio.net installed.
> > So when I run the CD all goes well until you specify the database for
the
> > reporting server and then I get the following error:
> > "This edition of the Report Server Database is not supported on the
> edition
> > of SQL Server 2000 you have chosen. Please choose on that matches the
> > requirements."
> > MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> > Developer edition.
> > What does this mean, any comments or feedback will be greately
> appreciated.
> > - Sergio|||I am running SQL Server developer and got the same message. However, I
continued with the installation and it works fine. That is, it works
in VS.NET 2003. I can create new "business intelligence" projects.

"SD" <npspam@.nowhere.net> wrote in message news:<ab8fe521601065edf8fa050f7602dbb6@.news.teranews.com >...
> Ha!
> I wasn't for some stupid reason I was running the personal edition. Thanks
> for your help, I would still be wasting time if I hadn't followed your
> suggestion.
> Thank you a heap.
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> > I would verify that you are running the developer addition. You can do
> that
> > by running this SELECT statement on your XP machine:
> > SELECT SERVERPROPERTY ('edition')
> > --
> > -----------------------
> --
> > -----------------------
> --
> > --
> > Need SQL Server Examples check out my website at
> > http://www.geocities.com/sqlserverexamples
> > "SD" <npspam@.nowhere.net> wrote in message
> > news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> > > Hi,
> > > > I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
> trying
> > > to install the MS SQL Server Reporting Services that is in the MSDN of
> April
> > > 2004. I also have Visual studio.net installed.
> > > > So when I run the CD all goes well until you specify the database for
> the
> > > reporting server and then I get the following error:
> > > > "This edition of the Report Server Database is not supported on the
> edition
> > > of SQL Server 2000 you have chosen. Please choose on that matches the
> > > requirements."
> > > > MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> > > Developer edition.
> > > > What does this mean, any comments or feedback will be greately
> appreciated.
> > > > - Sergio
> >|||How did you continue with the install. I have the same error, the
Developer Edition and when I get the error and click OK, it just returns
me to the same install step. Click Next again and I get the error message
again and so on...

Can not install Reporting Services, Help!

Hi,

So when I run the CD all goes well until you specify the database for the
reporting server and then I get the following error:

"This edition of the Report Server Database is not supported on the edition
of SQL Server 2000 you have chosen. Please choose on that matches the
requirements."

MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
Developer edition.

What does this mean, any comments or feedback will be greately appreciated.

- SergioI would verify that you are running the developer addition. You can do that
by running this SELECT statement on your XP machine:

SELECT SERVERPROPERTY ('edition')

-----------------------
-----------------------
--

I wasn't for some stupid reason I was running the personal edition. Thanks
for your help, I would still be wasting time if I hadn't followed your
suggestion.

Thank you a heap.

Tuesday, March 27, 2012

Can not drop merge replication.

Hi, i have a publisher running sql server 2000 sp3. I have
configured a merge replication with two push
subscriptions. I need to delete the subscriptions and the
publication but when i try to do it, i get this error:
Error 207: invalid column name 'enabled_for_syncmgr'
I'll really appreciate your help because i need to remove
replication from this database.
Regards,
Maria,
try running sp_helpsubscription @.publication = 'publication' , @.article =
'article'.
For each one found, run sp_dropmergesubscription, then drop the publication.
If it errors, please state at which point, and any relevant data from
sp_helpsubscription.
Regards,
Paul Ibison
|||Thanks a lot for your help. Yesterday i tryed to disable
this database for merge publications and it displays the
same error.
After that I execute the procedure you recommend me. Today
I found that the database is not configured for
replication but i still see the publication and
subscriptions in the replication monitor. The snapshot and
the subscriptions are failed displaying:
"The 'databasename' database is not published for merge
replication. "
And the subscribers displays:
"Publication 'publicationname' does not exists. The step
fails."
If i try to delete the publication diplays this error:
"Error: 21776. [SQL-DMO]The name 'publicationname' was not
found in the mergepublications collation..."
What should I do to delete the publication and subscribers
from the replication monitor?
Thanks a lot for your help.

>--Original Message--
>Maria,
>try running sp_helpsubscription @.publication
= 'publication' , @.article =
>'article'.
>For each one found, run sp_dropmergesubscription, then
drop the publication.
>If it errors, please state at which point, and any
relevant data from
>sp_helpsubscription.
>Regards,
>Paul Ibison
>
>.
>
|||Maria,
if you're lucky, this database is not needed to be used for replication as a publisher or subscriber. In this case you can run
sp_removedbreplication 'dbname'.
If not, then I'd script out what you need, remove what you can using hte replication interface in EM, then run the script above because there are some corrupted system table records which are better removed. Subsequently you can readd your scripts. Depend
ing on your replication you may be able to resume replication without reinitializing the data. Anyway, hopefully this is academic and you can simply run the command above on its own.
HTH,
Paul Ibison

Sunday, March 25, 2012

Can not delete database. Gives Error 21776. Suggestions please?

Hi,
I just installed MS SQL 2000 SE then SP3 on Windows 2000 Server. I
then backed-up a database from another MS SQL 2000 server and restored
it. After the restore, I noticed not all my tables were there, so I
decided to just do an import instead of restore. So I'm now trying to
delete the restored table, but I get the following error:
Microsoft SQL-DMO:
Error 21776:[SQL-DMO]The Name 'Accounting Database' was not found in
the Database collection. If the name is a qualified name, use [] to
seperate various parts of the name, and try again.
This is causing all sorts of problems now. Is there a script or
something I can run that will remove this database 100%? I want to
start clean, but use this same DB name. If I have to do this
manually, what tables in what database do I need to modify? And why
does Microsoft make this so difficult?
Thanks,
Alex.Hi Alex,
From Query Analyzer , Login as SA and execute the below command ,
sp_helpdb
From the result set , cut and past the Accounting database name along with
the below command,
drop database <paste the dbname>
Thanks
Hari
MCDBA
"Alex" <alex@.totallynerd.com> wrote in message
news:2ba4b4eb.0310270740.3be18d34@.posting.google.com...
> Hi,
> I just installed MS SQL 2000 SE then SP3 on Windows 2000 Server. I
> then backed-up a database from another MS SQL 2000 server and restored
> it. After the restore, I noticed not all my tables were there, so I
> decided to just do an import instead of restore. So I'm now trying to
> delete the restored table, but I get the following error:
> Microsoft SQL-DMO:
> Error 21776:[SQL-DMO]The Name 'Accounting Database' was not found in
> the Database collection. If the name is a qualified name, use [] to
> seperate various parts of the name, and try again.
> This is causing all sorts of problems now. Is there a script or
> something I can run that will remove this database 100%? I want to
> start clean, but use this same DB name. If I have to do this
> manually, what tables in what database do I need to modify? And why
> does Microsoft make this so difficult?
> Thanks,
> Alex.|||drop database [Accounting Database]
You need to wrap the database name in brackets since it has a space in the
name. Or you can right click on the database in QA and drop it, provided
that there are no connections.
-Morgan
"Alex" <alex@.totallynerd.com> wrote in message
news:2ba4b4eb.0310270740.3be18d34@.posting.google.com...
> Hi,
> I just installed MS SQL 2000 SE then SP3 on Windows 2000 Server. I
> then backed-up a database from another MS SQL 2000 server and restored
> it. After the restore, I noticed not all my tables were there, so I
> decided to just do an import instead of restore. So I'm now trying to
> delete the restored table, but I get the following error:
> Microsoft SQL-DMO:
> Error 21776:[SQL-DMO]The Name 'Accounting Database' was not found in
> the Database collection. If the name is a qualified name, use [] to
> seperate various parts of the name, and try again.
> This is causing all sorts of problems now. Is there a script or
> something I can run that will remove this database 100%? I want to
> start clean, but use this same DB name. If I have to do this
> manually, what tables in what database do I need to modify? And why
> does Microsoft make this so difficult?
> Thanks,
> Alex.|||Hi ,
Just issue this command ,
drop database [Accounting Database]
Thanks
Hari
MCDBA
"Morgan" <mfears@.spamcop.net> wrote in message
news:#5IV1sLnDHA.1764@.tk2msftngp13.phx.gbl...
> drop database [Accounting Database]
> You need to wrap the database name in brackets since it has a space in the
> name. Or you can right click on the database in QA and drop it, provided
> that there are no connections.
> -Morgan
> "Alex" <alex@.totallynerd.com> wrote in message
> news:2ba4b4eb.0310270740.3be18d34@.posting.google.com...
> > Hi,
> >
> > I just installed MS SQL 2000 SE then SP3 on Windows 2000 Server. I
> > then backed-up a database from another MS SQL 2000 server and restored
> > it. After the restore, I noticed not all my tables were there, so I
> > decided to just do an import instead of restore. So I'm now trying to
> > delete the restored table, but I get the following error:
> >
> > Microsoft SQL-DMO:
> > Error 21776:[SQL-DMO]The Name 'Accounting Database' was not found in
> > the Database collection. If the name is a qualified name, use [] to
> > seperate various parts of the name, and try again.
> >
> > This is causing all sorts of problems now. Is there a script or
> > something I can run that will remove this database 100%? I want to
> > start clean, but use this same DB name. If I have to do this
> > manually, what tables in what database do I need to modify? And why
> > does Microsoft make this so difficult?
> >
> > Thanks,
> >
> > Alex.
>

Tuesday, March 20, 2012

Can not access SQL Server

Hi,
In this case, the environment is:
Machine A: SQL Server 2000 SP3 on Windows 2003 SP1. (IP Address: 10.35.3.43)
Machine B: IIS Server on Windows XP SP2, an ASP.Net application, a WinForms
application. (In the same subnet)
In the WinForms application, I can connect to the SQL server sucessfully,
but in the ASP.Net application, I can not, the error message say that "SQL
Server does not exist, or access deny".
The code is the same in ASP.Net application and WinForms application:
==>>
string cnstring = "user id=sa;data source='10.35.3.43';persist security
info=True;initial catalog=MyDB;password='MyPassword'";
string cmdstring = "SELECT Count(*) FROM FunctionCode";
System.Data.SqlClient.SqlConnection cn = new
System.Data.SqlClient.SqlConnection(cnstring);
System.Data.SqlClient.SqlCommand cmd = new
System.Data.SqlClient.SqlCommand(cmdstring, cn);
cn.Open(); //Suceeds in WinForm, but fails in ASP.Net
int count = (int)cmd.ExecuteScalar();
cn.Close();
Response.Write(count.ToString());
<<==
How to fix this problem?
Thanks in advance
KevinRun a profiler trace on the SQL server to see if the login attempt is making
it the the SQL server. This will give you insight in to where to look next
for the problem, network or program.
--
Nik Marshall-Blank MCSD/MCDBA
"Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
news:%23g6oPUDtFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> In this case, the environment is:
> Machine A: SQL Server 2000 SP3 on Windows 2003 SP1. (IP Address:
> 10.35.3.43)
> Machine B: IIS Server on Windows XP SP2, an ASP.Net application, a
> WinForms application. (In the same subnet)
> In the WinForms application, I can connect to the SQL server sucessfully,
> but in the ASP.Net application, I can not, the error message say that "SQL
> Server does not exist, or access deny".
> The code is the same in ASP.Net application and WinForms application:
> ==>>
> string cnstring = "user id=sa;data source='10.35.3.43';persist security
> info=True;initial catalog=MyDB;password='MyPassword'";
> string cmdstring = "SELECT Count(*) FROM FunctionCode";
> System.Data.SqlClient.SqlConnection cn = new
> System.Data.SqlClient.SqlConnection(cnstring);
> System.Data.SqlClient.SqlCommand cmd = new
> System.Data.SqlClient.SqlCommand(cmdstring, cn);
> cn.Open(); //Suceeds in WinForm, but fails in ASP.Net
> int count = (int)cmd.ExecuteScalar();
> cn.Close();
> Response.Write(count.ToString());
> <<==> How to fix this problem?
> Thanks in advance
> Kevin
>|||It's not network problem, I can connect through a WinForm application. I
found something in the following article, I try but still doesn't work.
http://support.microsoft.com/default.aspx?scid=kb;en-us;888228
By the way, the two machines are in different domain.
Regars
Kevin
"Nik Marshall-Blank" <Nik@.Operatelecom.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:4iSTe.305886$WN5.7191@.fe02.news.easynews.com...
> Run a profiler trace on the SQL server to see if the login attempt is
> making it the the SQL server. This will give you insight in to where to
> look next for the problem, network or program.
> --
> Nik Marshall-Blank MCSD/MCDBA
> "Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
> news:%23g6oPUDtFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> In this case, the environment is:
>> Machine A: SQL Server 2000 SP3 on Windows 2003 SP1. (IP Address:
>> 10.35.3.43)
>> Machine B: IIS Server on Windows XP SP2, an ASP.Net application, a
>> WinForms application. (In the same subnet)
>> In the WinForms application, I can connect to the SQL server sucessfully,
>> but in the ASP.Net application, I can not, the error message say that
>> "SQL Server does not exist, or access deny".
>> The code is the same in ASP.Net application and WinForms application:
>> ==>>
>> string cnstring = "user id=sa;data source='10.35.3.43';persist security
>> info=True;initial catalog=MyDB;password='MyPassword'";
>> string cmdstring = "SELECT Count(*) FROM FunctionCode";
>> System.Data.SqlClient.SqlConnection cn = new
>> System.Data.SqlClient.SqlConnection(cnstring);
>> System.Data.SqlClient.SqlCommand cmd = new
>> System.Data.SqlClient.SqlCommand(cmdstring, cn);
>> cn.Open(); //Suceeds in WinForm, but fails in ASP.Net
>> int count = (int)cmd.ExecuteScalar();
>> cn.Close();
>> Response.Write(count.ToString());
>> <<==>> How to fix this problem?
>> Thanks in advance
>> Kevin
>>
>|||I would expect that to apply to both connections from Winform and ASP.NET.
Can you perform a profile trace on to see what credentials are being used
for the failing connection.
--
Nik Marshall-Blank MCSD/MCDBA
"Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
news:%237j8zSFtFHA.2792@.tk2msftngp13.phx.gbl...
> It's not network problem, I can connect through a WinForm application. I
> found something in the following article, I try but still doesn't work.
> http://support.microsoft.com/default.aspx?scid=kb;en-us;888228
> By the way, the two machines are in different domain.
> Regars
> Kevin
>
>
> "Nik Marshall-Blank" <Nik@.Operatelecom.com>
> Ð´ÈëÏûÏ¢ÐÂÎÅ:4iSTe.305886$WN5.7191@.fe02.news.easynews.com...
>> Run a profiler trace on the SQL server to see if the login attempt is
>> making it the the SQL server. This will give you insight in to where to
>> look next for the problem, network or program.
>> --
>> Nik Marshall-Blank MCSD/MCDBA
>> "Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
>> news:%23g6oPUDtFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> In this case, the environment is:
>> Machine A: SQL Server 2000 SP3 on Windows 2003 SP1. (IP Address:
>> 10.35.3.43)
>> Machine B: IIS Server on Windows XP SP2, an ASP.Net application, a
>> WinForms application. (In the same subnet)
>> In the WinForms application, I can connect to the SQL server
>> sucessfully, but in the ASP.Net application, I can not, the error
>> message say that "SQL Server does not exist, or access deny".
>> The code is the same in ASP.Net application and WinForms application:
>> ==>>
>> string cnstring = "user id=sa;data source='10.35.3.43';persist
>> security info=True;initial catalog=MyDB;password='MyPassword'";
>> string cmdstring = "SELECT Count(*) FROM FunctionCode";
>> System.Data.SqlClient.SqlConnection cn = new
>> System.Data.SqlClient.SqlConnection(cnstring);
>> System.Data.SqlClient.SqlCommand cmd = new
>> System.Data.SqlClient.SqlCommand(cmdstring, cn);
>> cn.Open(); //Suceeds in WinForm, but fails in ASP.Net
>> int count = (int)cmd.ExecuteScalar();
>> cn.Close();
>> Response.Write(count.ToString());
>> <<==>> How to fix this problem?
>> Thanks in advance
>> Kevin
>>
>>
>|||Hi, Nik,
I use profile trace, but there is no login or login fail events when using
ASP.Net. There is login even when using WinForm.
The source code and connection string are the same in WinForm and ASP.Net.
"Nik Marshall-Blank" <Nik@.Operatelecom.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:XrTTe.308487$kM5.134787@.fe01.news.easynews.com...
>I would expect that to apply to both connections from Winform and ASP.NET.
>Can you perform a profile trace on to see what credentials are being used
>for the failing connection.
> --
> Nik Marshall-Blank MCSD/MCDBA
> "Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
> news:%237j8zSFtFHA.2792@.tk2msftngp13.phx.gbl...
>> It's not network problem, I can connect through a WinForm application. I
>> found something in the following article, I try but still doesn't work.
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;888228
>> By the way, the two machines are in different domain.
>> Regars
>> Kevin
>>
>>
>> "Nik Marshall-Blank" <Nik@.Operatelecom.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:4iSTe.305886$WN5.7191@.fe02.news.easynews.com...
>> Run a profiler trace on the SQL server to see if the login attempt is
>> making it the the SQL server. This will give you insight in to where to
>> look next for the problem, network or program.
>> --
>> Nik Marshall-Blank MCSD/MCDBA
>> "Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
>> news:%23g6oPUDtFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> In this case, the environment is:
>> Machine A: SQL Server 2000 SP3 on Windows 2003 SP1. (IP Address:
>> 10.35.3.43)
>> Machine B: IIS Server on Windows XP SP2, an ASP.Net application, a
>> WinForms application. (In the same subnet)
>> In the WinForms application, I can connect to the SQL server
>> sucessfully, but in the ASP.Net application, I can not, the error
>> message say that "SQL Server does not exist, or access deny".
>> The code is the same in ASP.Net application and WinForms application:
>> ==>>
>> string cnstring = "user id=sa;data source='10.35.3.43';persist
>> security info=True;initial catalog=MyDB;password='MyPassword'";
>> string cmdstring = "SELECT Count(*) FROM FunctionCode";
>> System.Data.SqlClient.SqlConnection cn = new
>> System.Data.SqlClient.SqlConnection(cnstring);
>> System.Data.SqlClient.SqlCommand cmd = new
>> System.Data.SqlClient.SqlCommand(cmdstring, cn);
>> cn.Open(); //Suceeds in WinForm, but fails in ASP.Net
>> int count = (int)cmd.ExecuteScalar();
>> cn.Close();
>> Response.Write(count.ToString());
>> <<==>> How to fix this problem?
>> Thanks in advance
>> Kevin
>>
>>
>>
>|||Ok now we're getting somewhere, not sure where yet but we now going to look
at the ASP.Net server more closely.
But first just try adding the account under which ASP.Net runs as a login on
the SQL Server and see if it connects.
--
Nik Marshall-Blank MCSD/MCDBA
"Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
news:eYSsLGGtFHA.3908@.tk2msftngp13.phx.gbl...
> Hi, Nik,
> I use profile trace, but there is no login or login fail events when using
> ASP.Net. There is login even when using WinForm.
> The source code and connection string are the same in WinForm and ASP.Net.
>
>
> "Nik Marshall-Blank" <Nik@.Operatelecom.com>
> Ð´ÈëÏûÏ¢ÐÂÎÅ:XrTTe.308487$kM5.134787@.fe01.news.easynews.com...
>>I would expect that to apply to both connections from Winform and ASP.NET.
>>Can you perform a profile trace on to see what credentials are being used
>>for the failing connection.
>> --
>> Nik Marshall-Blank MCSD/MCDBA
>> "Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
>> news:%237j8zSFtFHA.2792@.tk2msftngp13.phx.gbl...
>> It's not network problem, I can connect through a WinForm application. I
>> found something in the following article, I try but still doesn't work.
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;888228
>> By the way, the two machines are in different domain.
>> Regars
>> Kevin
>>
>>
>> "Nik Marshall-Blank" <Nik@.Operatelecom.com>
>> Ð´ÈëÏûÏ¢ÐÂÎÅ:4iSTe.305886$WN5.7191@.fe02.news.easynews.com...
>> Run a profiler trace on the SQL server to see if the login attempt is
>> making it the the SQL server. This will give you insight in to where to
>> look next for the problem, network or program.
>> --
>> Nik Marshall-Blank MCSD/MCDBA
>> "Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
>> news:%23g6oPUDtFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> In this case, the environment is:
>> Machine A: SQL Server 2000 SP3 on Windows 2003 SP1. (IP Address:
>> 10.35.3.43)
>> Machine B: IIS Server on Windows XP SP2, an ASP.Net application, a
>> WinForms application. (In the same subnet)
>> In the WinForms application, I can connect to the SQL server
>> sucessfully, but in the ASP.Net application, I can not, the error
>> message say that "SQL Server does not exist, or access deny".
>> The code is the same in ASP.Net application and WinForms application:
>> ==>>
>> string cnstring = "user id=sa;data source='10.35.3.43';persist
>> security info=True;initial catalog=MyDB;password='MyPassword'";
>> string cmdstring = "SELECT Count(*) FROM FunctionCode";
>> System.Data.SqlClient.SqlConnection cn = new
>> System.Data.SqlClient.SqlConnection(cnstring);
>> System.Data.SqlClient.SqlCommand cmd = new
>> System.Data.SqlClient.SqlCommand(cmdstring, cn);
>> cn.Open(); //Suceeds in WinForm, but fails in ASP.Net
>> int count = (int)cmd.ExecuteScalar();
>> cn.Close();
>> Response.Write(count.ToString());
>> <<==>> How to fix this problem?
>> Thanks in advance
>> Kevin
>>
>>
>>
>>
>|||I now found the root cause. It's because the Machine A and Machine B are in
different domain, two domains are not trusted. If both machines in the same
domain, it works.
The reason why WinForm app succeeds is because Machine B have stored a use
account and password on Domain A, I could see the NT user name from sql
profiler, it's Domain A's user account.
"Nik Marshall-Blank" <Nik@.Operatelecom.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:DEUTe.127980$Lg2.47868@.fe12.news.easynews.com...
> Ok now we're getting somewhere, not sure where yet but we now going to
> look at the ASP.Net server more closely.
> But first just try adding the account under which ASP.Net runs as a login
> on the SQL Server and see if it connects.
> --
> Nik Marshall-Blank MCSD/MCDBA
> "Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
> news:eYSsLGGtFHA.3908@.tk2msftngp13.phx.gbl...
>> Hi, Nik,
>> I use profile trace, but there is no login or login fail events when
>> using ASP.Net. There is login even when using WinForm.
>> The source code and connection string are the same in WinForm and
>> ASP.Net.
>>
>>
>> "Nik Marshall-Blank" <Nik@.Operatelecom.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:XrTTe.308487$kM5.134787@.fe01.news.easynews.com...
>>I would expect that to apply to both connections from Winform and
>>ASP.NET. Can you perform a profile trace on to see what credentials are
>>being used for the failing connection.
>> --
>> Nik Marshall-Blank MCSD/MCDBA
>> "Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
>> news:%237j8zSFtFHA.2792@.tk2msftngp13.phx.gbl...
>> It's not network problem, I can connect through a WinForm application.
>> I found something in the following article, I try but still doesn't
>> work.
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;888228
>> By the way, the two machines are in different domain.
>> Regars
>> Kevin
>>
>>
>> "Nik Marshall-Blank" <Nik@.Operatelecom.com> Ð´ÈëÏûÏ¢ÐÂÎÅ:4iSTe.305886$WN5.7191@.fe02.news.easynews.com...
>> Run a profiler trace on the SQL server to see if the login attempt is
>> making it the the SQL server. This will give you insight in to where
>> to look next for the problem, network or program.
>> --
>> Nik Marshall-Blank MCSD/MCDBA
>> "Kevin Dai" <Kevin_Dzy@.Hotmail.com> wrote in message
>> news:%23g6oPUDtFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> In this case, the environment is:
>> Machine A: SQL Server 2000 SP3 on Windows 2003 SP1. (IP Address:
>> 10.35.3.43)
>> Machine B: IIS Server on Windows XP SP2, an ASP.Net application, a
>> WinForms application. (In the same subnet)
>> In the WinForms application, I can connect to the SQL server
>> sucessfully, but in the ASP.Net application, I can not, the error
>> message say that "SQL Server does not exist, or access deny".
>> The code is the same in ASP.Net application and WinForms application:
>> ==>>
>> string cnstring = "user id=sa;data source='10.35.3.43';persist
>> security info=True;initial catalog=MyDB;password='MyPassword'";
>> string cmdstring = "SELECT Count(*) FROM FunctionCode";
>> System.Data.SqlClient.SqlConnection cn = new
>> System.Data.SqlClient.SqlConnection(cnstring);
>> System.Data.SqlClient.SqlCommand cmd = new
>> System.Data.SqlClient.SqlCommand(cmdstring, cn);
>> cn.Open(); //Suceeds in WinForm, but fails in ASP.Net
>> int count = (int)cmd.ExecuteScalar();
>> cn.Close();
>> Response.Write(count.ToString());
>> <<==>> How to fix this problem?
>> Thanks in advance
>> Kevin
>>
>>
>>
>>
>>
>

Can not access SQL Server

Wednesday, March 7, 2012

Can I use SQL Server security with reporting services?

I'm using SQL Server 2000 SP3 Reporting Services SP2
Currently my reports are configured to use a shared data source reference.
The credentials for the data source are configured to use the same specified
user name and password, which is a login I created for the purpose of
generating the reports.
Is there a way to pass a SQL Server account user name and password to the
data source instead of using a shared account?
I've tried creating a Data Source Credentials object, but it didn't work:
dim dsc as new DataSourceCredentials
dsc.DataSourceName = "dsn"
dsc.UserName = "unm"
dsc.Password = "pwd"
...
result = rs.Render (...,dsc,...)
...
Unfortunately, I am prevented from using integrated security.
The report renders fine using the data source reference pre-configured with
the shared username and password.
Thanks!
BillHere is what I do and I think is the best thing to do. Create a readonly SQL
Server user account. Use that for your shared datasource. Limit your access
to reports using the built in security model (based on roles). If a user has
rights to run the report they they see the data. They don't need to use
their SQL Server login to do so. This will prevent you from having to manage
SQL Server accounts as much. And, it is better for performance.
By using a single, read only account it means that all database access is
happening through that account which allows connection pooling to do its
magic. Connection pooling only works if the connection string is identical.
Establishing connections is expensive. If you go the route you are
suggesting (which is not possible out of the box, you would have to write
your own forms based authentication and integrate it) then every time a new
user requests a report there will be a new connection being established to
the server.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"BillE" <belgie@.datamti.com> wrote in message
news:ercHCCmCHHA.3924@.TK2MSFTNGP02.phx.gbl...
> I'm using SQL Server 2000 SP3 Reporting Services SP2
> Currently my reports are configured to use a shared data source reference.
> The credentials for the data source are configured to use the same
> specified user name and password, which is a login I created for the
> purpose of generating the reports.
> Is there a way to pass a SQL Server account user name and password to the
> data source instead of using a shared account?
> I've tried creating a Data Source Credentials object, but it didn't work:
> dim dsc as new DataSourceCredentials
> dsc.DataSourceName = "dsn"
> dsc.UserName = "unm"
> dsc.Password = "pwd"
> ...
> result = rs.Render (...,dsc,...)
> ...
> Unfortunately, I am prevented from using integrated security.
> The report renders fine using the data source reference pre-configured
> with the shared username and password.
> Thanks!
> Bill
>
>|||Thanks for your response. This is a grey area for me, and I'm having some
trouble with it.
In the model I'm using, the user selects parameters in a web forms
interface, which builds a URL and submits it to the report server. The
report is rendered in the browser.
If the user bookmarks the report, it can be retrieved at any time from the
report server by opening the bookmark. No login is necessary, since the
report uses the shared login.
I don't see a security context to prevent a user without the appropriate
role membership from accessing a report. Perhaps my entire model is flawed.
Thanks
Bill
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:OhCo0bmCHHA.4892@.TK2MSFTNGP04.phx.gbl...
> Here is what I do and I think is the best thing to do. Create a readonly
> SQL Server user account. Use that for your shared datasource. Limit your
> access to reports using the built in security model (based on roles). If a
> user has rights to run the report they they see the data. They don't need
> to use their SQL Server login to do so. This will prevent you from having
> to manage SQL Server accounts as much. And, it is better for performance.
> By using a single, read only account it means that all database access is
> happening through that account which allows connection pooling to do its
> magic. Connection pooling only works if the connection string is
> identical. Establishing connections is expensive. If you go the route you
> are suggesting (which is not possible out of the box, you would have to
> write your own forms based authentication and integrate it) then every
> time a new user requests a report there will be a new connection being
> established to the server.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "BillE" <belgie@.datamti.com> wrote in message
> news:ercHCCmCHHA.3924@.TK2MSFTNGP02.phx.gbl...
>> I'm using SQL Server 2000 SP3 Reporting Services SP2
>> Currently my reports are configured to use a shared data source
>> reference.
>> The credentials for the data source are configured to use the same
>> specified user name and password, which is a login I created for the
>> purpose of generating the reports.
>> Is there a way to pass a SQL Server account user name and password to the
>> data source instead of using a shared account?
>> I've tried creating a Data Source Credentials object, but it didn't work:
>> dim dsc as new DataSourceCredentials
>> dsc.DataSourceName = "dsn"
>> dsc.UserName = "unm"
>> dsc.Password = "pwd"
>> ...
>> result = rs.Render (...,dsc,...)
>> ...
>> Unfortunately, I am prevented from using integrated security.
>> The report renders fine using the data source reference pre-configured
>> with the shared username and password.
>> Thanks!
>> Bill
>>
>|||RS always has a security context. Being able to have a report rendered is
different from the security used to actually get the data. For the report to
be rendered RS has to know who the user is. It then uses its role based
security to decide whether to provide the service. Then it renders the
report using the security specified for getting the data. Two levels of
security. Rights to run/render the report, rights to get the data. You have
been thinking on the latter when really the issue is more the former.
You have three choices.
1. Create your own authentication. This allows you to have the user log to
your app using the SQL Server login and have that be the login to your app.
You have to integrate this into Reporting Services.
2. Use integrated security where the windows credentials are used to
authenticate into RS. Then integrated security is use for the data source of
the reports as well.
3. Use integrated security where the windows credentials are used to
authenticate into RS. Then, use a fixed SQL Server account (one or more) in
the credentials tab of shared data source.
I do and recommend #3. #1 is non-trivial. #2 is lower performing and in your
case you say you can't use.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"BillE" <belgie@.datamti.com> wrote in message
news:uEuGchnCHHA.3228@.TK2MSFTNGP03.phx.gbl...
> Thanks for your response. This is a grey area for me, and I'm having some
> trouble with it.
> In the model I'm using, the user selects parameters in a web forms
> interface, which builds a URL and submits it to the report server. The
> report is rendered in the browser.
> If the user bookmarks the report, it can be retrieved at any time from the
> report server by opening the bookmark. No login is necessary, since the
> report uses the shared login.
> I don't see a security context to prevent a user without the appropriate
> role membership from accessing a report. Perhaps my entire model is
> flawed.
> Thanks
> Bill
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:OhCo0bmCHHA.4892@.TK2MSFTNGP04.phx.gbl...
>> Here is what I do and I think is the best thing to do. Create a readonly
>> SQL Server user account. Use that for your shared datasource. Limit your
>> access to reports using the built in security model (based on roles). If
>> a user has rights to run the report they they see the data. They don't
>> need to use their SQL Server login to do so. This will prevent you from
>> having to manage SQL Server accounts as much. And, it is better for
>> performance.
>> By using a single, read only account it means that all database access is
>> happening through that account which allows connection pooling to do its
>> magic. Connection pooling only works if the connection string is
>> identical. Establishing connections is expensive. If you go the route you
>> are suggesting (which is not possible out of the box, you would have to
>> write your own forms based authentication and integrate it) then every
>> time a new user requests a report there will be a new connection being
>> established to the server.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "BillE" <belgie@.datamti.com> wrote in message
>> news:ercHCCmCHHA.3924@.TK2MSFTNGP02.phx.gbl...
>> I'm using SQL Server 2000 SP3 Reporting Services SP2
>> Currently my reports are configured to use a shared data source
>> reference.
>> The credentials for the data source are configured to use the same
>> specified user name and password, which is a login I created for the
>> purpose of generating the reports.
>> Is there a way to pass a SQL Server account user name and password to
>> the data source instead of using a shared account?
>> I've tried creating a Data Source Credentials object, but it didn't
>> work:
>> dim dsc as new DataSourceCredentials
>> dsc.DataSourceName = "dsn"
>> dsc.UserName = "unm"
>> dsc.Password = "pwd"
>> ...
>> result = rs.Render (...,dsc,...)
>> ...
>> Unfortunately, I am prevented from using integrated security.
>> The report renders fine using the data source reference pre-configured
>> with the shared username and password.
>> Thanks!
>> Bill
>>
>>
>|||This client has users sharing computers, and they don't want to log off and
log on each time they switch users. However, one user may have access to
some reports which another user doesn't.
I'll have to pursue option #1, or (preferably) convince the client to come
to his senses.
Thanks for your help, I have a clearer understanding of the situation now.
Bill
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%232RmlDoCHHA.4256@.TK2MSFTNGP04.phx.gbl...
> RS always has a security context. Being able to have a report rendered is
> different from the security used to actually get the data. For the report
> to be rendered RS has to know who the user is. It then uses its role based
> security to decide whether to provide the service. Then it renders the
> report using the security specified for getting the data. Two levels of
> security. Rights to run/render the report, rights to get the data. You
> have been thinking on the latter when really the issue is more the former.
> You have three choices.
> 1. Create your own authentication. This allows you to have the user log to
> your app using the SQL Server login and have that be the login to your
> app. You have to integrate this into Reporting Services.
> 2. Use integrated security where the windows credentials are used to
> authenticate into RS. Then integrated security is use for the data source
> of the reports as well.
> 3. Use integrated security where the windows credentials are used to
> authenticate into RS. Then, use a fixed SQL Server account (one or more)
> in the credentials tab of shared data source.
> I do and recommend #3. #1 is non-trivial. #2 is lower performing and in
> your case you say you can't use.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "BillE" <belgie@.datamti.com> wrote in message
> news:uEuGchnCHHA.3228@.TK2MSFTNGP03.phx.gbl...
>> Thanks for your response. This is a grey area for me, and I'm having
>> some trouble with it.
>> In the model I'm using, the user selects parameters in a web forms
>> interface, which builds a URL and submits it to the report server. The
>> report is rendered in the browser.
>> If the user bookmarks the report, it can be retrieved at any time from
>> the report server by opening the bookmark. No login is necessary, since
>> the report uses the shared login.
>> I don't see a security context to prevent a user without the appropriate
>> role membership from accessing a report. Perhaps my entire model is
>> flawed.
>> Thanks
>> Bill
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:OhCo0bmCHHA.4892@.TK2MSFTNGP04.phx.gbl...
>> Here is what I do and I think is the best thing to do. Create a readonly
>> SQL Server user account. Use that for your shared datasource. Limit your
>> access to reports using the built in security model (based on roles). If
>> a user has rights to run the report they they see the data. They don't
>> need to use their SQL Server login to do so. This will prevent you from
>> having to manage SQL Server accounts as much. And, it is better for
>> performance.
>> By using a single, read only account it means that all database access
>> is happening through that account which allows connection pooling to do
>> its magic. Connection pooling only works if the connection string is
>> identical. Establishing connections is expensive. If you go the route
>> you are suggesting (which is not possible out of the box, you would have
>> to write your own forms based authentication and integrate it) then
>> every time a new user requests a report there will be a new connection
>> being established to the server.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "BillE" <belgie@.datamti.com> wrote in message
>> news:ercHCCmCHHA.3924@.TK2MSFTNGP02.phx.gbl...
>> I'm using SQL Server 2000 SP3 Reporting Services SP2
>> Currently my reports are configured to use a shared data source
>> reference.
>> The credentials for the data source are configured to use the same
>> specified user name and password, which is a login I created for the
>> purpose of generating the reports.
>> Is there a way to pass a SQL Server account user name and password to
>> the data source instead of using a shared account?
>> I've tried creating a Data Source Credentials object, but it didn't
>> work:
>> dim dsc as new DataSourceCredentials
>> dsc.DataSourceName = "dsn"
>> dsc.UserName = "unm"
>> dsc.Password = "pwd"
>> ...
>> result = rs.Render (...,dsc,...)
>> ...
>> Unfortunately, I am prevented from using integrated security.
>> The report renders fine using the data source reference pre-configured
>> with the shared username and password.
>> Thanks!
>> Bill
>>
>>
>>
>

Friday, February 10, 2012

Can I just make the necessary registry changes to turn on error reporting in SQL2000 SP3

http://support.microsoft.com/default...b;en-us;328446
The part that describes how to turn off Error Reporting for a default =
instance is unclear in this article. It looks to be missing stuff. So =
maybe all I have to do to enable Error Reporting, is to manually make =
the change in the registry. That way if I want to turn it off I just =
change 1 to 0 as is in the article. Is that OK will that be sufficient? =
Thanks.
--=20
George Hester
__________________________________
You are correct that the artilce is missing something. The proper method to
enable this is as follows:
To turn on error reporting by using SQL Server Enterprise
Manager or Analysis Manager, follow these steps:
1. Click to select the name of the server.
2. Right-click the server name, and then click Properties.
3. Click to select the Enable Error Reporting Feature check box.
It is always best to use the interface than to manually edit the registry.
Thanks for the catch. I am getting the article updated.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Oh cool yeah I'd rather do it that way. Thanks.
--=20
George Hester
__________________________________
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message =
news:#PLYRQnPEHA.1516@.cpmsftngxa10.phx.gbl...
> You are correct that the artilce is missing something. The proper =
method to=20
> enable this is as follows:
>=20
> To turn on error reporting by using SQL Server Enterprise
> Manager or Analysis Manager, follow these steps:
>=20
> 1. Click to select the name of the server.
> 2. Right-click the server name, and then click Properties.
> 3. Click to select the Enable Error Reporting Feature check box.
>=20
> It is always best to use the interface than to manually edit the =
registry.
>=20
> Thanks for the catch. I am getting the article updated.
>=20
> Rand
> This posting is provided "as is" with no warranties and confers no =
rights.
>

Can I just make the necessary registry changes to turn on error reporting in SQL2000 SP3

http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;328446
The part that describes how to turn off Error Reporting for a default = instance is unclear in this article. It looks to be missing stuff. So = maybe all I have to do to enable Error Reporting, is to manually make = the change in the registry. That way if I want to turn it off I just = change 1 to 0 as is in the article. Is that OK will that be sufficient? = Thanks.
-- George Hester
__________________________________You are correct that the artilce is missing something. The proper method to
enable this is as follows:
To turn on error reporting by using SQL Server Enterprise
Manager or Analysis Manager, follow these steps:
1. Click to select the name of the server.
2. Right-click the server name, and then click Properties.
3. Click to select the Enable Error Reporting Feature check box.
It is always best to use the interface than to manually edit the registry.
Thanks for the catch. I am getting the article updated.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Oh cool yeah I'd rather do it that way. Thanks.
-- George Hester
__________________________________
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message =news:#PLYRQnPEHA.1516@.cpmsftngxa10.phx.gbl...
> You are correct that the artilce is missing something. The proper =method to > enable this is as follows:
> > To turn on error reporting by using SQL Server Enterprise
> Manager or Analysis Manager, follow these steps:
> > 1. Click to select the name of the server.
> 2. Right-click the server name, and then click Properties.
> 3. Click to select the Enable Error Reporting Feature check box.
> > It is always best to use the interface than to manually edit the =registry.
> > Thanks for the catch. I am getting the article updated.
> > Rand
> This posting is provided "as is" with no warranties and confers no =rights.
>

Thursday, March 29, 2012

Can not install Reporting Services, Help!

Can not install Reporting Services, Help!

Can not install Reporting Services, Help!

Can not install Reporting Services, Help!

Tuesday, March 27, 2012

Can not drop merge replication.

Sunday, March 25, 2012

Can not delete database. Gives Error 21776. Suggestions please?

Tuesday, March 20, 2012

Can not access SQL Server

Can not access SQL Server

Can not access SQL Server

Wednesday, March 7, 2012

Can I use SQL Server security with reporting services?

Friday, February 10, 2012

Can I just make the necessary registry changes to turn on error reporting in SQL2000 SP3

Can I just make the necessary registry changes to turn on error reporting in SQL2000 SP3

install SQL on WinXP

Blog Archive

About Me