Can't Find SQL Native Client in ODBC Connection Manager

I am running Windows XP Pro SP2. I have installed the SQL Native Client for
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this
procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?MDAC issues, related DLL conflicts. The ODBC Data Source
Administrator piece can get hosed out with DLL conflicts on
an MDAC installation. You'd probably want to start checking
the MDAC installation using component checker. You can
download it from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 13 Feb 2007 10:31:01 -0800, Jim Strickland <Jim
Strickland@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I am running Windows XP Pro SP2. I have installed the SQL Native Client for
>XP. However, when I try to add a new data source through ODBC Connection
>Manager, SQL Native Client is not listed as an option. I have followed this
>procedure on three other systems with no problems. What would be causing th
e
>SQL Native Client to not show up in the list of available ODBC data sources?[/vbcol
]

Can't Find SQL Native Client in ODBC Connection Manager

I am running Windows XP Pro SP2. I have installed the SQL Native Client for
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this
procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?
MDAC issues, related DLL conflicts. The ODBC Data Source
Administrator piece can get hosed out with DLL conflicts on
an MDAC installation. You'd probably want to start checking
the MDAC installation using component checker. You can
download it from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 13 Feb 2007 10:31:01 -0800, Jim Strickland <Jim
Strickland@.discussions.microsoft.com> wrote:

>I am running Windows XP Pro SP2. I have installed the SQL Native Client for
>XP. However, when I try to add a new data source through ODBC Connection
>Manager, SQL Native Client is not listed as an option. I have followed this
>procedure on three other systems with no problems. What would be causing the
>SQL Native Client to not show up in the list of available ODBC data sources?

Can't find AdventureWorks in order to connect

I am working with SQL Server 2005 Express installed on my workstation under
XP SP2.
I am trying to work through the online tutorial. I am on
http://msdn2.microsoft.com/en-us/library/ms170681.aspx
I downloaded the AdventureWorksDB.msi and installed it. The files
AdventureWorks_Data and AdventureWorks_Log are in my C:\Program
File\Microsoft SQL Server\MSSQL.1\MSSQL\Data directory.
I am now trying to register the AdventureWorks server. Everything looks as
described in the tutorial until I get to the Connection Properties in Step 5.
There are no options for me to select. There are no databases other than
the initial system databases (no User Databases) when I try to browse.
Did I do something wrong? How do I locate the database so I can register it?Ensure you attached the AdventureWorks database to your SQL Server instance
which you choose in the New Server Registration window as the Server Name
editbox (e.g. EKREM-PC\test2)
If the AdventureWorks database is attached to your SQL Server instance and
if you type this SQL Server instance' s name in the Server Name editbox in
the New Server Registration, then you should be seeing the AdventureWorks
database in the combobox in Connection Properties tab in the New Server
Registration window.
--
Ekrem Ã?nsoy
"epignosis" <epignosis@.discussions.microsoft.com> wrote in message
news:C6DBA92F-A5A1-4333-993C-46E08CE8FCF8@.microsoft.com...
>I am working with SQL Server 2005 Express installed on my workstation under
> XP SP2.
> I am trying to work through the online tutorial. I am on
> http://msdn2.microsoft.com/en-us/library/ms170681.aspx
> I downloaded the AdventureWorksDB.msi and installed it. The files
> AdventureWorks_Data and AdventureWorks_Log are in my C:\Program
> File\Microsoft SQL Server\MSSQL.1\MSSQL\Data directory.
> I am now trying to register the AdventureWorks server. Everything looks
> as
> described in the tutorial until I get to the Connection Properties in Step
> 5.
> There are no options for me to select. There are no databases other than
> the initial system databases (no User Databases) when I try to browse.
> Did I do something wrong? How do I locate the database so I can register
> it?
>
>|||"Installing" from the MSI just extracts the database files. You then need
to run CREATE DATABASE ... FOR ATTACH. See Books Online for exact syntax.
"epignosis" <epignosis@.discussions.microsoft.com> wrote in message
news:C6DBA92F-A5A1-4333-993C-46E08CE8FCF8@.microsoft.com...
>I am working with SQL Server 2005 Express installed on my workstation under
> XP SP2.
> I am trying to work through the online tutorial. I am on
> http://msdn2.microsoft.com/en-us/library/ms170681.aspx
> I downloaded the AdventureWorksDB.msi and installed it. The files
> AdventureWorks_Data and AdventureWorks_Log are in my C:\Program
> File\Microsoft SQL Server\MSSQL.1\MSSQL\Data directory.
> I am now trying to register the AdventureWorks server. Everything looks
> as
> described in the tutorial until I get to the Connection Properties in Step
> 5.
> There are no options for me to select. There are no databases other than
> the initial system databases (no User Databases) when I try to browse.
> Did I do something wrong? How do I locate the database so I can register
> it?
>
>

Can't find AdventureWorks in order to connect

I am working with SQL Server 2005 Express installed on my workstation under
XP SP2.
I am trying to work through the online tutorial. I am on
http://msdn2.microsoft.com/en-us/library/ms170681.aspx
I downloaded the AdventureWorksDB.msi and installed it. The files
AdventureWorks_Data and AdventureWorks_Log are in my C:\Program
File\Microsoft SQL Server\MSSQL.1\MSSQL\Data directory.
I am now trying to register the AdventureWorks server. Everything looks as
described in the tutorial until I get to the Connection Properties in Step 5.
There are no options for me to select. There are no databases other than
the initial system databases (no User Databases) when I try to browse.
Did I do something wrong? How do I locate the database so I can register it?
Ensure you attached the AdventureWorks database to your SQL Server instance
which you choose in the New Server Registration window as the Server Name
editbox (e.g. EKREM-PC\test2)
If the AdventureWorks database is attached to your SQL Server instance and
if you type this SQL Server instance' s name in the Server Name editbox in
the New Server Registration, then you should be seeing the AdventureWorks
database in the combobox in Connection Properties tab in the New Server
Registration window.
Ekrem ?nsoy
"epignosis" <epignosis@.discussions.microsoft.com> wrote in message
news:C6DBA92F-A5A1-4333-993C-46E08CE8FCF8@.microsoft.com...
>I am working with SQL Server 2005 Express installed on my workstation under
> XP SP2.
> I am trying to work through the online tutorial. I am on
> http://msdn2.microsoft.com/en-us/library/ms170681.aspx
> I downloaded the AdventureWorksDB.msi and installed it. The files
> AdventureWorks_Data and AdventureWorks_Log are in my C:\Program
> File\Microsoft SQL Server\MSSQL.1\MSSQL\Data directory.
> I am now trying to register the AdventureWorks server. Everything looks
> as
> described in the tutorial until I get to the Connection Properties in Step
> 5.
> There are no options for me to select. There are no databases other than
> the initial system databases (no User Databases) when I try to browse.
> Did I do something wrong? How do I locate the database so I can register
> it?
>
>
|||"Installing" from the MSI just extracts the database files. You then need
to run CREATE DATABASE ... FOR ATTACH. See Books Online for exact syntax.
"epignosis" <epignosis@.discussions.microsoft.com> wrote in message
news:C6DBA92F-A5A1-4333-993C-46E08CE8FCF8@.microsoft.com...
>I am working with SQL Server 2005 Express installed on my workstation under
> XP SP2.
> I am trying to work through the online tutorial. I am on
> http://msdn2.microsoft.com/en-us/library/ms170681.aspx
> I downloaded the AdventureWorksDB.msi and installed it. The files
> AdventureWorks_Data and AdventureWorks_Log are in my C:\Program
> File\Microsoft SQL Server\MSSQL.1\MSSQL\Data directory.
> I am now trying to register the AdventureWorks server. Everything looks
> as
> described in the tutorial until I get to the Connection Properties in Step
> 5.
> There are no options for me to select. There are no databases other than
> the initial system databases (no User Databases) when I try to browse.
> Did I do something wrong? How do I locate the database so I can register
> it?
>
>
sql

Can't find AdventureWorks in order to connect

I am working with SQL Server 2005 Express installed on my workstation under
XP SP2.
I am trying to work through the online tutorial. I am on
http://msdn2.microsoft.com/en-us/library/ms170681.aspx
I downloaded the AdventureWorksDB.msi and installed it. The files
AdventureWorks_Data and AdventureWorks_Log are in my C:\Program
File\Microsoft SQL Server\MSSQL.1\MSSQL\Data directory.
I am now trying to register the AdventureWorks server. Everything looks as
described in the tutorial until I get to the Connection Properties in Step 5
.
There are no options for me to select. There are no databases other than
the initial system databases (no User Databases) when I try to browse.
Did I do something wrong? How do I locate the database so I can register it
?Ensure you attached the AdventureWorks database to your SQL Server instance
which you choose in the New Server Registration window as the Server Name
editbox (e.g. EKREM-PC\test2)
If the AdventureWorks database is attached to your SQL Server instance and
if you type this SQL Server instance' s name in the Server Name editbox in
the New Server Registration, then you should be seeing the AdventureWorks
database in the combobox in Connection Properties tab in the New Server
Registration window.
Ekrem ?nsoy
"epignosis" <epignosis@.discussions.microsoft.com> wrote in message
news:C6DBA92F-A5A1-4333-993C-46E08CE8FCF8@.microsoft.com...
>I am working with SQL Server 2005 Express installed on my workstation under
> XP SP2.
> I am trying to work through the online tutorial. I am on
> http://msdn2.microsoft.com/en-us/library/ms170681.aspx
> I downloaded the AdventureWorksDB.msi and installed it. The files
> AdventureWorks_Data and AdventureWorks_Log are in my C:\Program
> File\Microsoft SQL Server\MSSQL.1\MSSQL\Data directory.
> I am now trying to register the AdventureWorks server. Everything looks
> as
> described in the tutorial until I get to the Connection Properties in Step
> 5.
> There are no options for me to select. There are no databases other than
> the initial system databases (no User Databases) when I try to browse.
> Did I do something wrong? How do I locate the database so I can register
> it?
>
>|||"Installing" from the MSI just extracts the database files. You then need
to run CREATE DATABASE ... FOR ATTACH. See Books Online for exact syntax.
"epignosis" <epignosis@.discussions.microsoft.com> wrote in message
news:C6DBA92F-A5A1-4333-993C-46E08CE8FCF8@.microsoft.com...
>I am working with SQL Server 2005 Express installed on my workstation under
> XP SP2.
> I am trying to work through the online tutorial. I am on
> http://msdn2.microsoft.com/en-us/library/ms170681.aspx
> I downloaded the AdventureWorksDB.msi and installed it. The files
> AdventureWorks_Data and AdventureWorks_Log are in my C:\Program
> File\Microsoft SQL Server\MSSQL.1\MSSQL\Data directory.
> I am now trying to register the AdventureWorks server. Everything looks
> as
> described in the tutorial until I get to the Connection Properties in Step
> 5.
> There are no options for me to select. There are no databases other than
> the initial system databases (no User Databases) when I try to browse.
> Did I do something wrong? How do I locate the database so I can register
> it?
>
>

Can't Execute Package from BIDS Solution Explorer Post SP2 Install

Yesterday, SQL Server 2005 SP2 was installed on our DEV Server (Windows 2003 SP1 x86) and now I cannot right-click a package in the Solutions Explorer window in BIDS and Execute Package. When I do, I get the following error

===================================

Object reference not set to an instance of an object. (Microsoft Visual Studio)

Program Location:

at Microsoft.DataTransformationServices.Project.DtsPackagesFolderProjectFeature.ExecuteTaskOrPackage(ProjectItem prjItem, String taskPath)

I know I could do this yesterday morning pre SP2. I've attempted this with a couple of different packages and solutions, so it is probably not a corrupt package (unless now they are all corrupt). I can execute in debug mode if I open the package first and then hit Start Debugging. However this is not always an optimal solution because I sometimes have many connected packages and sometimes what gets executed is not what is expected.

Your thoughts would be appreciated.

I'm having the identical problem. If I create a new package, it will work for a short period of time. I didn't measure the time precisely, but it is within 15 minutes and an hour or so. I appreciate your run-in-debug solution, but it is still not a clean fix.sql

Can't display the report page from the Internet

Hi,

I am using SQL 2000 SP4 and Report Server SP2 on W2k3 SP1 Server.

I am having trouble displaying the report pages if I am connected from the Internet.

I have no problem if I am connected in the office (Intranet).

The frame that is not show is underneath the New Subscription bar in my report page. I can see everything above (header pages etc) and Home page etc.

I think for some reasons the request frame URL page is still https://myserver/Repor... instead https://myserver.mycompany.com/Report...

Thank's for any help

gogu

PS: Also I am able to deploy only from the Intranet with Target Server URL https://myserver/ReportServer
If I setup VS.NET deploy Target Server URL https://myserver.mycompany.com/ReportServer it comes up with "A connection could not be made ..."
If I open the Browser from the Intranet I can see the reports pages even if with https://myserver.mycompany.com/Reports...
but it ask me for Username / Password.
How can I tell VS.NET when deploy to use username/password?

I think I figure out this (PostID=499647);

I modified RSWebApplication.config see PostID=499647 above and reinstall SSL certificate with <FQDN>

What stupid think is that only the body of report page follows the key <ReportServerUrl> other frame pages are relative to browser URL?

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||

Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can't delete a maintenance plan in SQL 2005

hi everyone,
Thank you for your help in advance. I just set up a MS SQL 2005 standard
server with SP2 for one of my finance software. The OS is Windows 2003 with
SP2.
The database itself is checked with "2000 sql compatible". I also have TCP,
and Named Pipes enable. The server is in the AD domain. I use both Windows
and SQL authentication with my sa account.
I just created a maintenance plan in the Studio console so that the backup
and reindex can run on the server db. However, the job failed last nite. I
decide delete the plan and set up another one. I connected to the server by
using the Studio console on itself and tried to remove the plan, but it
failed. I clicked on the error (a link displayed in the Studio) said the
following:
#############
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
An error has occurred while establishing a connection to the server. When
connecting to the SQL server 2005, this failure may be caused by the fact
that under the default settings SQL server does not allow remote connections.
(provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
Server)(Microsoft SQL server, Error:53)
##############
I have made sure the remote connection (right click on the server object in
the Studio thing) is enabled. As mentioend, I also made sure the named pipes
is enabled (\\.\pipe\sql\query).
May you provide idea so that I can remove the plan successfully?
Thank you!
BobsonWere you able to fix your problem? I have the same issue but didn't found
anything helpful yet.
Thanks
Denis Desjardins
"Bobson" wrote:
> hi everyone,
> Thank you for your help in advance. I just set up a MS SQL 2005 standard
> server with SP2 for one of my finance software. The OS is Windows 2003 with
> SP2.
> The database itself is checked with "2000 sql compatible". I also have TCP,
> and Named Pipes enable. The server is in the AD domain. I use both Windows
> and SQL authentication with my sa account.
> I just created a maintenance plan in the Studio console so that the backup
> and reindex can run on the server db. However, the job failed last nite. I
> decide delete the plan and set up another one. I connected to the server by
> using the Studio console on itself and tried to remove the plan, but it
> failed. I clicked on the error (a link displayed in the Studio) said the
> following:
> #############
> Exception has been thrown by the target of an invocation. (mscorlib)
> Additional information:
> An error has occurred while establishing a connection to the server. When
> connecting to the SQL server 2005, this failure may be caused by the fact
> that under the default settings SQL server does not allow remote connections.
> (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> Server)(Microsoft SQL server, Error:53)
> ##############
> I have made sure the remote connection (right click on the server object in
> the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> is enabled (\\.\pipe\sql\query).
> May you provide idea so that I can remove the plan successfully?
> Thank you!
> Bobson|||Dennis,
Great someone read my post :) Before telling my point of view... I would
like to ask if you do the following :
1.) Put the sql in the domain
2.) rename the server couple times as the task already created
3.) use different admin account to log on and config both sql and OS (I am
still thinking permission related)
I have no one to respond to me as I could not find any solution on the Net
(the closest one is to run some scripts and clean up registry). The problem
still remains. But I did a test by setting up a clean new server with the
SQL. And I cannot duplicate the problem! In the test I do not do anythings I
mentioned above...
I was about to submit an issue to MS... but the SQL admin finally said we
could ignore the issue...so I just seize my action.
May I get your person email so we can talk more about it? Mine is
ultrabobson@.hotmail.com
Thank you, and stay in touch.
Bobson
"Denis Desjardins" wrote:
> Were you able to fix your problem? I have the same issue but didn't found
> anything helpful yet.
> Thanks
> Denis Desjardins
> "Bobson" wrote:
> > hi everyone,
> >
> > Thank you for your help in advance. I just set up a MS SQL 2005 standard
> > server with SP2 for one of my finance software. The OS is Windows 2003 with
> > SP2.
> >
> > The database itself is checked with "2000 sql compatible". I also have TCP,
> > and Named Pipes enable. The server is in the AD domain. I use both Windows
> > and SQL authentication with my sa account.
> >
> > I just created a maintenance plan in the Studio console so that the backup
> > and reindex can run on the server db. However, the job failed last nite. I
> > decide delete the plan and set up another one. I connected to the server by
> > using the Studio console on itself and tried to remove the plan, but it
> > failed. I clicked on the error (a link displayed in the Studio) said the
> > following:
> >
> > #############
> > Exception has been thrown by the target of an invocation. (mscorlib)
> >
> > Additional information:
> > An error has occurred while establishing a connection to the server. When
> > connecting to the SQL server 2005, this failure may be caused by the fact
> > that under the default settings SQL server does not allow remote connections.
> > (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> > Server)(Microsoft SQL server, Error:53)
> > ##############
> >
> > I have made sure the remote connection (right click on the server object in
> > the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> > is enabled (\\.\pipe\sql\query).
> >
> > May you provide idea so that I can remove the plan successfully?
> >
> > Thank you!
> >
> > Bobson|||Bobson,
I send you an email on your hotmail address but didn't have any answer yet.
Here's what i mention in my email:
Yes I actually renamed the server, or more precisely the virtual server name
since Iâ'm running on a cluster, after the maintenance plan was created. I
know thatâ's related, but I just want to be able to delete those problematic
plans and recreated them afterward. Any idea?
"Bobson" wrote:
> Dennis,
> Great someone read my post :) Before telling my point of view... I would
> like to ask if you do the following :
> 1.) Put the sql in the domain
> 2.) rename the server couple times as the task already created
> 3.) use different admin account to log on and config both sql and OS (I am
> still thinking permission related)
> I have no one to respond to me as I could not find any solution on the Net
> (the closest one is to run some scripts and clean up registry). The problem
> still remains. But I did a test by setting up a clean new server with the
> SQL. And I cannot duplicate the problem! In the test I do not do anythings I
> mentioned above...
> I was about to submit an issue to MS... but the SQL admin finally said we
> could ignore the issue...so I just seize my action.
> May I get your person email so we can talk more about it? Mine is
> ultrabobson@.hotmail.com
> Thank you, and stay in touch.
> Bobson
>
> "Denis Desjardins" wrote:
> > Were you able to fix your problem? I have the same issue but didn't found
> > anything helpful yet.
> >
> > Thanks
> >
> > Denis Desjardins
> >
> > "Bobson" wrote:
> >
> > > hi everyone,
> > >
> > > Thank you for your help in advance. I just set up a MS SQL 2005 standard
> > > server with SP2 for one of my finance software. The OS is Windows 2003 with
> > > SP2.
> > >
> > > The database itself is checked with "2000 sql compatible". I also have TCP,
> > > and Named Pipes enable. The server is in the AD domain. I use both Windows
> > > and SQL authentication with my sa account.
> > >
> > > I just created a maintenance plan in the Studio console so that the backup
> > > and reindex can run on the server db. However, the job failed last nite. I
> > > decide delete the plan and set up another one. I connected to the server by
> > > using the Studio console on itself and tried to remove the plan, but it
> > > failed. I clicked on the error (a link displayed in the Studio) said the
> > > following:
> > >
> > > #############
> > > Exception has been thrown by the target of an invocation. (mscorlib)
> > >
> > > Additional information:
> > > An error has occurred while establishing a connection to the server. When
> > > connecting to the SQL server 2005, this failure may be caused by the fact
> > > that under the default settings SQL server does not allow remote connections.
> > > (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> > > Server)(Microsoft SQL server, Error:53)
> > > ##############
> > >
> > > I have made sure the remote connection (right click on the server object in
> > > the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> > > is enabled (\\.\pipe\sql\query).
> > >
> > > May you provide idea so that I can remove the plan successfully?
> > >
> > > Thank you!
> > >
> > > Bobson|||Hi Dennis,
I am sorry if I might overlook it... Please try again with my
ultrabobson@.yahoo.com (or hotmail.com)
So you have very similar issue as what we did. We did not have any
reolsutions yet...even though we renamed the server back to the original
name. But it still could not resovle the issue. What we ran around was to
crate another plan.
I have couple of Technet tickets and I might try to submit the issue to
them. I may not do this tsoon, but I will keep you posted once I do that.
Stay in touch.
Bobson
"Denis Desjardins" wrote:
> Bobson,
> I send you an email on your hotmail address but didn't have any answer yet.
> Here's what i mention in my email:
> Yes I actually renamed the server, or more precisely the virtual server name
> since Iâ'm running on a cluster, after the maintenance plan was created. I
> know thatâ's related, but I just want to be able to delete those problematic
> plans and recreated them afterward. Any idea?
>
> "Bobson" wrote:
> > Dennis,
> >
> > Great someone read my post :) Before telling my point of view... I would
> > like to ask if you do the following :
> >
> > 1.) Put the sql in the domain
> > 2.) rename the server couple times as the task already created
> > 3.) use different admin account to log on and config both sql and OS (I am
> > still thinking permission related)
> >
> > I have no one to respond to me as I could not find any solution on the Net
> > (the closest one is to run some scripts and clean up registry). The problem
> > still remains. But I did a test by setting up a clean new server with the
> > SQL. And I cannot duplicate the problem! In the test I do not do anythings I
> > mentioned above...
> >
> > I was about to submit an issue to MS... but the SQL admin finally said we
> > could ignore the issue...so I just seize my action.
> >
> > May I get your person email so we can talk more about it? Mine is
> > ultrabobson@.hotmail.com
> >
> > Thank you, and stay in touch.
> >
> > Bobson
> >
> >
> >
> > "Denis Desjardins" wrote:
> >
> > > Were you able to fix your problem? I have the same issue but didn't found
> > > anything helpful yet.
> > >
> > > Thanks
> > >
> > > Denis Desjardins
> > >
> > > "Bobson" wrote:
> > >
> > > > hi everyone,
> > > >
> > > > Thank you for your help in advance. I just set up a MS SQL 2005 standard
> > > > server with SP2 for one of my finance software. The OS is Windows 2003 with
> > > > SP2.
> > > >
> > > > The database itself is checked with "2000 sql compatible". I also have TCP,
> > > > and Named Pipes enable. The server is in the AD domain. I use both Windows
> > > > and SQL authentication with my sa account.
> > > >
> > > > I just created a maintenance plan in the Studio console so that the backup
> > > > and reindex can run on the server db. However, the job failed last nite. I
> > > > decide delete the plan and set up another one. I connected to the server by
> > > > using the Studio console on itself and tried to remove the plan, but it
> > > > failed. I clicked on the error (a link displayed in the Studio) said the
> > > > following:
> > > >
> > > > #############
> > > > Exception has been thrown by the target of an invocation. (mscorlib)
> > > >
> > > > Additional information:
> > > > An error has occurred while establishing a connection to the server. When
> > > > connecting to the SQL server 2005, this failure may be caused by the fact
> > > > that under the default settings SQL server does not allow remote connections.
> > > > (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> > > > Server)(Microsoft SQL server, Error:53)
> > > > ##############
> > > >
> > > > I have made sure the remote connection (right click on the server object in
> > > > the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> > > > is enabled (\\.\pipe\sql\query).
> > > >
> > > > May you provide idea so that I can remove the plan successfully?
> > > >
> > > > Thank you!
> > > >
> > > > Bobson

Can't delete a maintenance plan in SQL 2005

hi everyone,
Thank you for your help in advance. I just set up a MS SQL 2005 standard
server with SP2 for one of my finance software. The OS is Windows 2003 with
SP2.
The database itself is checked with "2000 sql compatible". I also have TCP,
and Named Pipes enable. The server is in the AD domain. I use both Windows
and SQL authentication with my sa account.
I just created a maintenance plan in the Studio console so that the backup
and reindex can run on the server db. However, the job failed last nite. I
decide delete the plan and set up another one. I connected to the server by
using the Studio console on itself and tried to remove the plan, but it
failed. I clicked on the error (a link displayed in the Studio) said the
following:
#############
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
An error has occurred while establishing a connection to the server. When
connecting to the SQL server 2005, this failure may be caused by the fact
that under the default settings SQL server does not allow remote connections.
(provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
Server)(Microsoft SQL server, Error:53)
##############
I have made sure the remote connection (right click on the server object in
the Studio thing) is enabled. As mentioend, I also made sure the named pipes
is enabled (\\.\pipe\sql\query).
May you provide idea so that I can remove the plan successfully?
Thank you!
Bobson
Were you able to fix your problem? I have the same issue but didn't found
anything helpful yet.
Thanks
Denis Desjardins
"Bobson" wrote:

> hi everyone,
> Thank you for your help in advance. I just set up a MS SQL 2005 standard
> server with SP2 for one of my finance software. The OS is Windows 2003 with
> SP2.
> The database itself is checked with "2000 sql compatible". I also have TCP,
> and Named Pipes enable. The server is in the AD domain. I use both Windows
> and SQL authentication with my sa account.
> I just created a maintenance plan in the Studio console so that the backup
> and reindex can run on the server db. However, the job failed last nite. I
> decide delete the plan and set up another one. I connected to the server by
> using the Studio console on itself and tried to remove the plan, but it
> failed. I clicked on the error (a link displayed in the Studio) said the
> following:
> #############
> Exception has been thrown by the target of an invocation. (mscorlib)
> Additional information:
> An error has occurred while establishing a connection to the server. When
> connecting to the SQL server 2005, this failure may be caused by the fact
> that under the default settings SQL server does not allow remote connections.
> (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> Server)(Microsoft SQL server, Error:53)
> ##############
> I have made sure the remote connection (right click on the server object in
> the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> is enabled (\\.\pipe\sql\query).
> May you provide idea so that I can remove the plan successfully?
> Thank you!
> Bobson
|||Dennis,
Great someone read my post Before telling my point of view... I would
like to ask if you do the following :
1.) Put the sql in the domain
2.) rename the server couple times as the task already created
3.) use different admin account to log on and config both sql and OS (I am
still thinking permission related)
I have no one to respond to me as I could not find any solution on the Net
(the closest one is to run some scripts and clean up registry). The problem
still remains. But I did a test by setting up a clean new server with the
SQL. And I cannot duplicate the problem! In the test I do not do anythings I
mentioned above...
I was about to submit an issue to MS... but the SQL admin finally said we
could ignore the issue...so I just seize my action.
May I get your person email so we can talk more about it? Mine is
ultrabobson@.hotmail.com
Thank you, and stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Were you able to fix your problem? I have the same issue but didn't found
> anything helpful yet.
> Thanks
> Denis Desjardins
> "Bobson" wrote:
|||Bobson,
I send you an email on your hotmail address but didn't have any answer yet.
Here's what i mention in my email:
Yes I actually renamed the server, or more precisely the virtual server name
since I’m running on a cluster, after the maintenance plan was created. I
know that’s related, but I just want to be able to delete those problematic
plans and recreated them afterward. Any idea?
"Bobson" wrote:
[vbcol=seagreen]
> Dennis,
> Great someone read my post Before telling my point of view... I would
> like to ask if you do the following :
> 1.) Put the sql in the domain
> 2.) rename the server couple times as the task already created
> 3.) use different admin account to log on and config both sql and OS (I am
> still thinking permission related)
> I have no one to respond to me as I could not find any solution on the Net
> (the closest one is to run some scripts and clean up registry). The problem
> still remains. But I did a test by setting up a clean new server with the
> SQL. And I cannot duplicate the problem! In the test I do not do anythings I
> mentioned above...
> I was about to submit an issue to MS... but the SQL admin finally said we
> could ignore the issue...so I just seize my action.
> May I get your person email so we can talk more about it? Mine is
> ultrabobson@.hotmail.com
> Thank you, and stay in touch.
> Bobson
>
> "Denis Desjardins" wrote:
|||Hi Dennis,
I am sorry if I might overlook it... Please try again with my
ultrabobson@.yahoo.com (or hotmail.com)
So you have very similar issue as what we did. We did not have any
reolsutions yet...even though we renamed the server back to the original
name. But it still could not resovle the issue. What we ran around was to
crate another plan.
I have couple of Technet tickets and I might try to submit the issue to
them. I may not do this tsoon, but I will keep you posted once I do that.
Stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Bobson,
> I send you an email on your hotmail address but didn't have any answer yet.
> Here's what i mention in my email:
> Yes I actually renamed the server, or more precisely the virtual server name
> since I’m running on a cluster, after the maintenance plan was created. I
> know that’s related, but I just want to be able to delete those problematic
> plans and recreated them afterward. Any idea?
>
> "Bobson" wrote:

Can't delete a maintenance plan in SQL 2005

hi everyone,
Thank you for your help in advance. I just set up a MS SQL 2005 standard
server with SP2 for one of my finance software. The OS is Windows 2003 with
SP2.
The database itself is checked with "2000 sql compatible". I also have TCP,
and Named Pipes enable. The server is in the AD domain. I use both Windows
and SQL authentication with my sa account.
I just created a maintenance plan in the Studio console so that the backup
and reindex can run on the server db. However, the job failed last nite. I
decide delete the plan and set up another one. I connected to the server by
using the Studio console on itself and tried to remove the plan, but it
failed. I clicked on the error (a link displayed in the Studio) said the
following:
#############
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
An error has occurred while establishing a connection to the server. When
connecting to the SQL server 2005, this failure may be caused by the fact
that under the default settings SQL server does not allow remote connections
.
(provide: Named Pipes Provide, error: 40 - Could not open a connection to SQ
L
Server)(Microsoft SQL server, Error:53)
##############
I have made sure the remote connection (right click on the server object in
the Studio thing) is enabled. As mentioend, I also made sure the named pipes
is enabled (\\.\pipe\sql\query).
May you provide idea so that I can remove the plan successfully?
Thank you!
BobsonWere you able to fix your problem? I have the same issue but didn't found
anything helpful yet.
Thanks
Denis Desjardins
"Bobson" wrote:

> hi everyone,
> Thank you for your help in advance. I just set up a MS SQL 2005 standard
> server with SP2 for one of my finance software. The OS is Windows 2003 wit
h
> SP2.
> The database itself is checked with "2000 sql compatible". I also have TCP
,
> and Named Pipes enable. The server is in the AD domain. I use both Windows
> and SQL authentication with my sa account.
> I just created a maintenance plan in the Studio console so that the backup
> and reindex can run on the server db. However, the job failed last nite. I
> decide delete the plan and set up another one. I connected to the server b
y
> using the Studio console on itself and tried to remove the plan, but it
> failed. I clicked on the error (a link displayed in the Studio) said the
> following:
> #############
> Exception has been thrown by the target of an invocation. (mscorlib)
> Additional information:
> An error has occurred while establishing a connection to the server. When
> connecting to the SQL server 2005, this failure may be caused by the fact
> that under the default settings SQL server does not allow remote connectio
ns.
> (provide: Named Pipes Provide, error: 40 - Could not open a connection to
SQL
> Server)(Microsoft SQL server, Error:53)
> ##############
> I have made sure the remote connection (right click on the server object i
n
> the Studio thing) is enabled. As mentioend, I also made sure the named pip
es
> is enabled (\\.\pipe\sql\query).
> May you provide idea so that I can remove the plan successfully?
> Thank you!
> Bobson|||Dennis,
Great someone read my post Before telling my point of view... I would
like to ask if you do the following :
1.) Put the sql in the domain
2.) rename the server couple times as the task already created
3.) use different admin account to log on and config both sql and OS (I am
still thinking permission related)
I have no one to respond to me as I could not find any solution on the Net
(the closest one is to run some scripts and clean up registry). The problem
still remains. But I did a test by setting up a clean new server with the
SQL. And I cannot duplicate the problem! In the test I do not do anythings I
mentioned above...
I was about to submit an issue to MS... but the SQL admin finally said we
could ignore the issue...so I just seize my action.
May I get your person email so we can talk more about it? Mine is
ultrabobson@.hotmail.com
Thank you, and stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Were you able to fix your problem? I have the same issue but didn't found
> anything helpful yet.
> Thanks
> Denis Desjardins
> "Bobson" wrote:
>|||Bobson,
I send you an email on your hotmail address but didn't have any answer yet.
Here's what i mention in my email:
Yes I actually renamed the server, or more precisely the virtual server name
since I’m running on a cluster, after the maintenance plan was created. I
know that’s related, but I just want to be able to delete those problemati
c
plans and recreated them afterward. Any idea?
"Bobson" wrote:
[vbcol=seagreen]
> Dennis,
> Great someone read my post Before telling my point of view... I would
> like to ask if you do the following :
> 1.) Put the sql in the domain
> 2.) rename the server couple times as the task already created
> 3.) use different admin account to log on and config both sql and OS (I am
> still thinking permission related)
> I have no one to respond to me as I could not find any solution on the Net
> (the closest one is to run some scripts and clean up registry). The proble
m
> still remains. But I did a test by setting up a clean new server with the
> SQL. And I cannot duplicate the problem! In the test I do not do anythings
I
> mentioned above...
> I was about to submit an issue to MS... but the SQL admin finally said we
> could ignore the issue...so I just seize my action.
> May I get your person email so we can talk more about it? Mine is
> ultrabobson@.hotmail.com
> Thank you, and stay in touch.
> Bobson
>
> "Denis Desjardins" wrote:
>|||Hi Dennis,
I am sorry if I might overlook it... Please try again with my
ultrabobson@.yahoo.com (or hotmail.com)
So you have very similar issue as what we did. We did not have any
reolsutions yet...even though we renamed the server back to the original
name. But it still could not resovle the issue. What we ran around was to
crate another plan.
I have couple of technet tickets and I might try to submit the issue to
them. I may not do this tsoon, but I will keep you posted once I do that.
Stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Bobson,
> I send you an email on your hotmail address but didn't have any answer yet
.
> Here's what i mention in my email:
> Yes I actually renamed the server, or more precisely the virtual server na
me
> since I’m running on a cluster, after the maintenance plan was created.
I
> know that’s related, but I just want to be able to delete those problema
tic
> plans and recreated them afterward. Any idea?
>
> "Bobson" wrote:
>

Can't debug proc after Sp2 on WinXP

Hi,
After installation of SP2 on my WinXP Prof I can't run debug in SQL Query
Analyzer.
Unable to connect to debugger on "SERVER" (Error = 0x800706ba). Ensure that
client-side components, such as SQLDBREG.EXE, are installed and registered on
"MYXP". Debugging disabled for connection nn.
Server is Win 2003 and SQL 2000 with Sp3
Before Sp2 everything was OK.
Thanks for the help.
ML
Make sure you have followed all the steps in the help topic
in books online: Troubleshooting the Transact-SQL Debugger
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Wed, 27 Oct 2004 05:13:03 -0700, MarekL
<MarekL@.discussions.microsoft.com> wrote:

>Hi,
>After installation of SP2 on my WinXP Prof I can't run debug in SQL Query
>Analyzer.
>Unable to connect to debugger on "SERVER" (Error = 0x800706ba). Ensure that
>client-side components, such as SQLDBREG.EXE, are installed and registered on
>"MYXP". Debugging disabled for connection nn.
>Server is Win 2003 and SQL 2000 with Sp3
>Before Sp2 everything was OK.
>Thanks for the help.
>ML

Cant create index on view

Hi,

SQL Server 2005 (SP2) Developer edition on XP Pro

Can anyone help with setting up an indexed view? Part of the select statement calls a couple of very simple functions which are deterministic. The functions which are shown below do not perform any aggregation.

This is the error message.

Msg 8668, Level 16, State 0, Line 2
Cannot create the clustered index 'IX3_SA' on view 'XPS.dbo.SA_INDEXED' because the select list of the view contains an expression on result of aggregate function or grouping column. Consider removing expression on result of aggregate function or grouping column from select list.

Function definitions:

create FUNCTION [dbo].[MonthName](@.MonthNo TINYINT)
RETURNS CHAR(3)
with schemabinding
AS
BEGIN
DECLARE @.MonthName CHAR(3)
IF @.MonthNo BETWEEN 1 AND 12 SET @.MonthName = SUBSTRING('JanFebMarAprMayJunJulAugSepOctNovDec',((@.MonthNo*3) -2),3)
RETURN ISNULL(@.MonthName,'')
END

create FUNCTION [dbo].[FinancialYear](
@.Year INT,
@.MonthNo TINYINT,
@.YearEndMonthNo TINYINT)
RETURNS INT
with schemabinding
AS
BEGIN
DECLARE @.FinancialYear INT
IF @.MonthNo <= @.YearEndMonthNo
SET @.FinancialYear = @.Year
ELSE
SET @.FinancialYear = @.Year + 1
RETURN @.FinancialYear
END

The first part of the select statement is as follows:

(SELECT
count_big(*) as CB,

dbo.FinancialYear(YR.Number,MTH.Number,YEAR_END_MONTH) AS REPORT_FINANCIAL_YEAR,
dbo.MonthName(MTH.Number) + ' ' + CAST(YR.Number AS CHAR(4)) AS REPORT_MONTH,
dbo.MonthName(YEAR_END_MONTH) + ' ' + CAST(dbo.FinancialYear(YR.Number,MTH.Number,YEAR_END_MONTH) AS CHAR(4)) AS REPORT_FINANCIAL_YEAR_END,

I can create the index on this view if I comment out the calls to the functions so I know that is where the problem is. I can't however see why this is erroring as both only return a single value without any agregation.

Anyone got any ideas on this?

Thanks in advance

David.

Well that met with a deafening silence.

The answer was to move these function calls out of the indexed view definition into a standard view that sits above it.

cant connect xp pro sp2 to database on ntserver 4

We have a program using sqlserver7, bde 5.01, msde, which works fine on the
98se machines we have connecting to ntserver4, however we got a new xp pro
machine with sp2, I have mapped the exe to the network and it goes to a login
screen, where it then fails to connect to the database with a generic cannot
connect to database error. I have turned the firewall in xp off to see if
that helps, I have also included the exe and the instance of sql server on
the list of exceptions
in the firewall
any ideas what I'm missing?
managed to fix the problem ourselves, looked in the registry settings for
borland, turns out the config file was looking at the server but the dll was
looking locally, so we repointed the dll to the server borland folder and hey
presto program connects and works fine
another side point, I was able to export the borland registry key from a
98se machine into the xp pro machine to enable quick setup of borland on xp
"seatzie" wrote:

> We have a program using sqlserver7, bde 5.01, msde, which works fine on the
> 98se machines we have connecting to ntserver4, however we got a new xp pro
> machine with sp2, I have mapped the exe to the network and it goes to a login
> screen, where it then fails to connect to the database with a generic cannot
> connect to database error. I have turned the firewall in xp off to see if
> that helps, I have also included the exe and the instance of sql server on
> the list of exceptions
> in the firewall
> any ideas what I'm missing?

cant connect xp pro sp2 to database on ntserver 4

We have a program using sqlserver7, bde 5.01, msde, which works fine on the
98se machines we have connecting to ntserver4, however we got a new xp pro
machine with sp2, I have mapped the exe to the network and it goes to a logi
n
screen, where it then fails to connect to the database with a generic cannot
connect to database error. I have turned the firewall in xp off to see if
that helps, I have also included the exe and the instance of sql server on
the list of exceptions
in the firewall
any ideas what I'm missing?managed to fix the problem ourselves, looked in the registry settings for
borland, turns out the config file was looking at the server but the dll was
looking locally, so we repointed the dll to the server borland folder and he
y
presto program connects and works fine
another side point, I was able to export the borland registry key from a
98se machine into the xp pro machine to enable quick setup of borland on xp
"seatzie" wrote:

> We have a program using sqlserver7, bde 5.01, msde, which works fine on th
e
> 98se machines we have connecting to ntserver4, however we got a new xp pro
> machine with sp2, I have mapped the exe to the network and it goes to a lo
gin
> screen, where it then fails to connect to the database with a generic cann
ot
> connect to database error. I have turned the firewall in xp off to see if
> that helps, I have also included the exe and the instance of sql server on
> the list of exceptions
> in the firewall
> any ideas what I'm missing?

Can't connect to SQL server in Windows XP SP2

Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
set to windows or sql authentication. I believe I opened them with the
correct TCP/UDP combination. I also told windows firewall about
sqlserver.exe, however I suspect that is more for outbound connections.
I understand the security reasons why the normal error message has to be
vague about sql server does not exist or access denied. Is it possible to
configure SQL server into a diagnostic mode where it will tell the client
that the sql server does exist but it was just that access was denied? This
would help me narrow down the problem.
If not, how can I tell if it is networking/firewall type problem or an SQL
server security problem?
Chris Pankhurst
Sometimes you can tell from the full text of the error
messages. You could turn on failed login auditing to see if
the login is hitting the server and failing. You can also
monitor for login failures in Profiler. You won't get a lot
of information on the login failure but enough to see if the
client is hitting the server.
-Sue
On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:

>Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
>set to windows or sql authentication. I believe I opened them with the
>correct TCP/UDP combination. I also told windows firewall about
>sqlserver.exe, however I suspect that is more for outbound connections.
>I understand the security reasons why the normal error message has to be
>vague about sql server does not exist or access denied. Is it possible to
>configure SQL server into a diagnostic mode where it will tell the client
>that the sql server does exist but it was just that access was denied? This
>would help me narrow down the problem.
>If not, how can I tell if it is networking/firewall type problem or an SQL
>server security problem?
>Chris Pankhurst
>
|||Thanks, I'm not sure how to turn on login auditing, but using profiler is a
good idea. I wonder why I didn't think of it.
Chris Pankhurst
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.4ax.com... [vbcol=seagreen]
> Sometimes you can tell from the full text of the error
> messages. You could turn on failed login auditing to see if
> the login is hitting the server and failing. You can also
> monitor for login failures in Profiler. You won't get a lot
> of information on the login failure but enough to see if the
> client is hitting the server.
> -Sue
> On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
> <christopher_pankhurst@.hotmail.com> wrote:
is[vbcol=seagreen]
This[vbcol=seagreen]
SQL
>
|||For login audits, in Enterprise Manager, right click on the
server and select properties. Go to the Security tab and you
can set the audit level for logins (success, failure or
all). You need to restart the service for the settings to
take effect.
-Sue
On Mon, 26 Sep 2005 08:32:32 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:

>Thanks, I'm not sure how to turn on login auditing, but using profiler is a
>good idea. I wonder why I didn't think of it.
>Chris Pankhurst
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.4ax.com.. .
>is
>This
>SQL
>

Can't connect to SQL server in Windows XP SP2

Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
set to windows or sql authentication. I believe I opened them with the
correct TCP/UDP combination. I also told windows firewall about
sqlserver.exe, however I suspect that is more for outbound connections.
I understand the security reasons why the normal error message has to be
vague about sql server does not exist or access denied. Is it possible to
configure SQL server into a diagnostic mode where it will tell the client
that the sql server does exist but it was just that access was denied? This
would help me narrow down the problem.
If not, how can I tell if it is networking/firewall type problem or an SQL
server security problem?
Chris PankhurstSometimes you can tell from the full text of the error
messages. You could turn on failed login auditing to see if
the login is hitting the server and failing. You can also
monitor for login failures in Profiler. You won't get a lot
of information on the login failure but enough to see if the
client is hitting the server.
-Sue
On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:

>Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
>set to windows or sql authentication. I believe I opened them with the
>correct TCP/UDP combination. I also told windows firewall about
>sqlserver.exe, however I suspect that is more for outbound connections.
>I understand the security reasons why the normal error message has to be
>vague about sql server does not exist or access denied. Is it possible to
>configure SQL server into a diagnostic mode where it will tell the client
>that the sql server does exist but it was just that access was denied? This
>would help me narrow down the problem.
>If not, how can I tell if it is networking/firewall type problem or an SQL
>server security problem?
>Chris Pankhurst
>|||Thanks, I'm not sure how to turn on login auditing, but using profiler is a
good idea. I wonder why I didn't think of it.
Chris Pankhurst
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.
4ax.com...
> Sometimes you can tell from the full text of the error
> messages. You could turn on failed login auditing to see if
> the login is hitting the server and failing. You can also
> monitor for login failures in Profiler. You won't get a lot
> of information on the login failure but enough to see if the
> client is hitting the server.
> -Sue
> On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
> <christopher_pankhurst@.hotmail.com> wrote:
>
is[vbcol=seagreen]
This[vbcol=seagreen]
SQL[vbcol=seagreen]
>|||For login audits, in Enterprise Manager, right click on the
server and select properties. Go to the Security tab and you
can set the audit level for logins (success, failure or
all). You need to restart the service for the settings to
take effect.
-Sue
On Mon, 26 Sep 2005 08:32:32 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:

>Thanks, I'm not sure how to turn on login auditing, but using profiler is a
>good idea. I wonder why I didn't think of it.
>Chris Pankhurst
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.
4ax.com...
>is
>This
>SQL
>