Cannot edit packages

I have sql server 2k5 sp2 cluster, IS is installed on both nodes. There are a few maintainence plans that work well until today, when I try to edit it, I got the following error message:

TITLE: Microsoft SQL Server Management Studio

Cannot show the editor for this task.

ADDITIONAL INFORMATION:

Value of '6/22/2007 12:00:00 AM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.

Parameter name: Value (System.Windows.Forms)

BUTTONS:

OK

I have to drop the task and readd it.

what's wrong with this, is this something to do with failover cluster?

thanks

Hello,

I'm going to move this question over to the SQL Server Tools forum where I think folks will have an answer.

Thanks, -Matt

|||

I'm having the same problem with a package created with the maintenance wizard on SQL 2005. Did you ever get any answers to this problem?

Looking at the dbo.sys_jobsview I can't see anything out of line (of course the date in question shouldn't be out of bounds for the datepicker control on the form anyway).

The message that I get is:

TITLE: Microsoft SQL Server Management Studio

Cannot show the editor for this task.

ADDITIONAL INFORMATION:

Value of '7/12/2007 12:00:00 AM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.
Parameter name: Value (System.Windows.Forms)

BUTTONS:

OK

Which indicates a .Net System.Windows.Forms error. We are running MSSQL2005 SP2.

|||

The full stack dump is:

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

Cannot show the editor for this task. (Microsoft SQL Server Management Studio)

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

Value of '7/12/2007 12:00:00 AM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.
Parameter name: Value (System.Windows.Forms)

Program Location:

at System.Windows.Forms.DateTimePicker.set_Value(DateTime value)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintTaskBackupControl.set_ExpireDate(DateTime value)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DBMaintTaskBackupForm.SetTask(DbMaintenanceBackupTask task)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DBMaintTaskBackupForm..ctor(TaskHost taskHost, IServiceProvider provider)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintTaskBackupUI.GetView()
at Microsoft.DataTransformationServices.Design.DtrTaskDesigner.GetTaskEditor()

|||

I just started to see same error when I tried to open one part of the maintenance job in SQL 2005.

Anyone?

|||

I'm getting the same error on one of my maintenance tasks too. Just on one task on one server, the other similar tasks seems to be fine.

Scott<-

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

for an excellent writeup on this issue.

jkh

Cannot edit packages

I have sql server 2k5 sp2 cluster, IS is installed on both nodes. There are a few maintainence plans that work well until today, when I try to edit it, I got the following error message:

TITLE: Microsoft SQL Server Management Studio

Cannot show the editor for this task.

ADDITIONAL INFORMATION:

Value of '6/22/2007 12:00:00 AM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.

Parameter name: Value (System.Windows.Forms)

BUTTONS:

OK

I have to drop the task and readd it.

what's wrong with this, is this something to do with failover cluster?

thanks

Hello,

I'm going to move this question over to the SQL Server Tools forum where I think folks will have an answer.

Thanks, -Matt

|||

I'm having the same problem with a package created with the maintenance wizard on SQL 2005. Did you ever get any answers to this problem?

Looking at the dbo.sys_jobsview I can't see anything out of line (of course the date in question shouldn't be out of bounds for the datepicker control on the form anyway).

The message that I get is:

TITLE: Microsoft SQL Server Management Studio

Cannot show the editor for this task.

ADDITIONAL INFORMATION:

Value of '7/12/2007 12:00:00 AM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.
Parameter name: Value (System.Windows.Forms)

BUTTONS:

OK

Which indicates a .Net System.Windows.Forms error. We are running MSSQL2005 SP2.

|||

The full stack dump is:

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

Cannot show the editor for this task. (Microsoft SQL Server Management Studio)

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

Value of '7/12/2007 12:00:00 AM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.
Parameter name: Value (System.Windows.Forms)

Program Location:

at System.Windows.Forms.DateTimePicker.set_Value(DateTime value)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintTaskBackupControl.set_ExpireDate(DateTime value)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DBMaintTaskBackupForm.SetTask(DbMaintenanceBackupTask task)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DBMaintTaskBackupForm..ctor(TaskHost taskHost, IServiceProvider provider)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintTaskBackupUI.GetView()
at Microsoft.DataTransformationServices.Design.DtrTaskDesigner.GetTaskEditor()

|||

I just started to see same error when I tried to open one part of the maintenance job in SQL 2005.

Anyone?

|||

I'm getting the same error on one of my maintenance tasks too. Just on one task on one server, the other similar tasks seems to be fine.

Scott<-

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

for an excellent writeup on this issue.

jkh

sql

Cannot edit packages

I have sql server 2k5 sp2 cluster, IS is installed on both nodes. There are a few maintainence plans that work well until today, when I try to edit it, I got the following error message:

TITLE: Microsoft SQL Server Management Studio

Cannot show the editor for this task.

ADDITIONAL INFORMATION:

Value of '6/22/2007 12:00:00 AM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.

Parameter name: Value (System.Windows.Forms)

BUTTONS:

OK

I have to drop the task and readd it.

what's wrong with this, is this something to do with failover cluster?

thanks

Hello,

I'm going to move this question over to the SQL Server Tools forum where I think folks will have an answer.

Thanks, -Matt

|||

I'm having the same problem with a package created with the maintenance wizard on SQL 2005. Did you ever get any answers to this problem?

Looking at the dbo.sys_jobsview I can't see anything out of line (of course the date in question shouldn't be out of bounds for the datepicker control on the form anyway).

The message that I get is:

TITLE: Microsoft SQL Server Management Studio

Cannot show the editor for this task.

ADDITIONAL INFORMATION:

Value of '7/12/2007 12:00:00 AM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.
Parameter name: Value (System.Windows.Forms)

BUTTONS:

OK

Which indicates a .Net System.Windows.Forms error. We are running MSSQL2005 SP2.

|||

The full stack dump is:

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

Cannot show the editor for this task. (Microsoft SQL Server Management Studio)

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

Value of '7/12/2007 12:00:00 AM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.
Parameter name: Value (System.Windows.Forms)

Program Location:

at System.Windows.Forms.DateTimePicker.set_Value(DateTime value)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintTaskBackupControl.set_ExpireDate(DateTime value)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DBMaintTaskBackupForm.SetTask(DbMaintenanceBackupTask task)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DBMaintTaskBackupForm..ctor(TaskHost taskHost, IServiceProvider provider)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintTaskBackupUI.GetView()
at Microsoft.DataTransformationServices.Design.DtrTaskDesigner.GetTaskEditor()

|||

I just started to see same error when I tried to open one part of the maintenance job in SQL 2005.

Anyone?

|||

I'm getting the same error on one of my maintenance tasks too. Just on one task on one server, the other similar tasks seems to be fine.

Scott<-

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

for an excellent writeup on this issue.

jkh

Cannot edit maintenance plans post SP2

I have some maintenance plans written for SQL Server 2005 SP1. After we
upgraded to SP2 I can no longer edit them. If I select the Maintneance Plans
node in Object Explorer and double click on any plan I get "Microsoft SQL
Server Management Studio is unable to load this document: One or more error
occured."
The popup message box says "Value cannot be null. Parameter name: component
(System.Design)"
Details are:"
Program Location:
at
System.ComponentModel.Design.DesignerHost.System.C omponentModel.Design.IDesignerHost.GetDesigner(ICo mponent component)
at
Microsoft.DataTransformationServices.VsIntegration .DtsDesignerService.OpenDesigner(String connectionString, Object connection, String objectUrn)
at
Microsoft.SqlServer.Management.DatabaseMaintenance .MaintDesignerMenuHandler.Invoke()"
I saw one post that sugget there is a fix that ought to be in cumulative
update package 4, but I can't see any items in that which match this problem.
The maintenance plans appear to run when called by the SQl Agent Jobs they
were initially set up with. However, I am calling one of them from another
Job and this has started throwing this error since SP2:
"Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Description: The
Execute method on the task returned error code 0x80131904 (Conversion failed
when converting from a character string to uniqueidentifier.). The Execute
method must succeed<c/> and indicate the result using an "out" parameter.
End Error"
but when I went to look at the plan, I couldn't edit it!
Any advice on how to edit the maintenance plans or fix the second error
would be great.
Thanks,
Charles
Yes. From Help -> about:
"Microsoft SQL Server Management Studio9.00.3042.00
Microsoft Analysis Services Client Tools2005.090.3042.00
Microsoft Data Access Components (MDAC)2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer6.0.2900.2180
Microsoft .NET Framework2.0.50727.832
Operating System5.1.2600"
"Tibor Karaszi" wrote:

> Did you install sp2 for the clients components (SSMS) on the machine where you try to edit the plan?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "CharlesB1" <CharlesB1@.discussions.microsoft.com> wrote in message
> news:CC70B322-EBCB-4D2E-B1DA-98AAEDDBF86A@.microsoft.com...
>
>
sql

Cannot edit maintenance plans post SP2

I have some maintenance plans written for SQL Server 2005 SP1. After we
upgraded to SP2 I can no longer edit them. If I select the Maintneance Plans
node in Object Explorer and double click on any plan I get "Microsoft SQL
Server Management Studio is unable to load this document: One or more error
occured."
The popup message box says "Value cannot be null. Parameter name: component
(System.Design)"
Details are:"
Program Location:
at
System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesi
gnerHost.GetDesigner(IComponent component)
at
Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDe
signer(String connectionString, Object connection, String objectUrn)
at
Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.
Invoke()"
I saw one post that sugget there is a fix that ought to be in cumulative
update package 4, but I can't see any items in that which match this problem
.
The maintenance plans appear to run when called by the SQl Agent Jobs they
were initially set up with. However, I am calling one of them from another
Job and this has started throwing this error since SP2:
"Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Descriptio
n: The
Execute method on the task returned error code 0x80131904 (Conversion failed
when converting from a character string to uniqueidentifier.). The Execute
method must succeed<c/> and indicate the result using an "out" parameter.
End Error"
but when I went to look at the plan, I couldn't edit it!
Any advice on how to edit the maintenance plans or fix the second error
would be great.
Thanks,
CharlesDid you install sp2 for the clients components (SSMS) on the machine where y
ou try to edit the plan?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"CharlesB1" <CharlesB1@.discussions.microsoft.com> wrote in message
news:CC70B322-EBCB-4D2E-B1DA-98AAEDDBF86A@.microsoft.com...
>I have some maintenance plans written for SQL Server 2005 SP1. After we
> upgraded to SP2 I can no longer edit them. If I select the Maintneance Pla
ns
> node in Object Explorer and double click on any plan I get "Microsoft SQL
> Server Management Studio is unable to load this document: One or more erro
r
> occured."
> The popup message box says "Value cannot be null. Parameter name: componen
t
> (System.Design)"
> Details are:"
> Program Location:
> at
> System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDe
signerHost.GetDesigner(IComponent
> component)
> at
> Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.Open
Designer(String
> connectionString, Object connection, String objectUrn)
> at
> Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandle
r.Invoke()"
> I saw one post that sugget there is a fix that ought to be in cumulative
> update package 4, but I can't see any items in that which match this probl
em.
> The maintenance plans appear to run when called by the SQl Agent Jobs they
> were initially set up with. However, I am calling one of them from another
> Job and this has started throwing this error since SP2:
> "Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
> Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Descript
ion: The
> Execute method on the task returned error code 0x80131904 (Conversion fail
ed
> when converting from a character string to uniqueidentifier.). The Execute
> method must succeed<c/> and indicate the result using an "out" parameter.
> End Error"
> but when I went to look at the plan, I couldn't edit it!
> Any advice on how to edit the maintenance plans or fix the second error
> would be great.
> Thanks,
> Charles
>|||Yes. From Help -> about :
"Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600"
"Tibor Karaszi" wrote:

> Did you install sp2 for the clients components (SSMS) on the machine where
you try to edit the plan?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "CharlesB1" <CharlesB1@.discussions.microsoft.com> wrote in message
> news:CC70B322-EBCB-4D2E-B1DA-98AAEDDBF86A@.microsoft.com...
>
>

Cannot edit maintenance plans post SP2

I have some maintenance plans written for SQL Server 2005 SP1. After we
upgraded to SP2 I can no longer edit them. If I select the Maintneance Plans
node in Object Explorer and double click on any plan I get "Microsoft SQL
Server Management Studio is unable to load this document: One or more error
occured."
The popup message box says "Value cannot be null. Parameter name: component
(System.Design)"
Details are:"
Program Location:
at
System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetDesigner(IComponent component)
at
Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDesigner(String connectionString, Object connection, String objectUrn)
at
Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()"
I saw one post that sugget there is a fix that ought to be in cumulative
update package 4, but I can't see any items in that which match this problem.
The maintenance plans appear to run when called by the SQl Agent Jobs they
were initially set up with. However, I am calling one of them from another
Job and this has started throwing this error since SP2:
"Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Description: The
Execute method on the task returned error code 0x80131904 (Conversion failed
when converting from a character string to uniqueidentifier.). The Execute
method must succeed<c/> and indicate the result using an "out" parameter.
End Error"
but when I went to look at the plan, I couldn't edit it!
Any advice on how to edit the maintenance plans or fix the second error
would be great.
Thanks,
CharlesDid you install sp2 for the clients components (SSMS) on the machine where you try to edit the plan?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"CharlesB1" <CharlesB1@.discussions.microsoft.com> wrote in message
news:CC70B322-EBCB-4D2E-B1DA-98AAEDDBF86A@.microsoft.com...
>I have some maintenance plans written for SQL Server 2005 SP1. After we
> upgraded to SP2 I can no longer edit them. If I select the Maintneance Plans
> node in Object Explorer and double click on any plan I get "Microsoft SQL
> Server Management Studio is unable to load this document: One or more error
> occured."
> The popup message box says "Value cannot be null. Parameter name: component
> (System.Design)"
> Details are:"
> Program Location:
> at
> System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetDesigner(IComponent
> component)
> at
> Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDesigner(String
> connectionString, Object connection, String objectUrn)
> at
> Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()"
> I saw one post that sugget there is a fix that ought to be in cumulative
> update package 4, but I can't see any items in that which match this problem.
> The maintenance plans appear to run when called by the SQl Agent Jobs they
> were initially set up with. However, I am calling one of them from another
> Job and this has started throwing this error since SP2:
> "Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
> Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Description: The
> Execute method on the task returned error code 0x80131904 (Conversion failed
> when converting from a character string to uniqueidentifier.). The Execute
> method must succeed<c/> and indicate the result using an "out" parameter.
> End Error"
> but when I went to look at the plan, I couldn't edit it!
> Any advice on how to edit the maintenance plans or fix the second error
> would be great.
> Thanks,
> Charles
>|||Yes. From Help -> About:
"Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600"
"Tibor Karaszi" wrote:
> Did you install sp2 for the clients components (SSMS) on the machine where you try to edit the plan?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "CharlesB1" <CharlesB1@.discussions.microsoft.com> wrote in message
> news:CC70B322-EBCB-4D2E-B1DA-98AAEDDBF86A@.microsoft.com...
> >I have some maintenance plans written for SQL Server 2005 SP1. After we
> > upgraded to SP2 I can no longer edit them. If I select the Maintneance Plans
> > node in Object Explorer and double click on any plan I get "Microsoft SQL
> > Server Management Studio is unable to load this document: One or more error
> > occured."
> >
> > The popup message box says "Value cannot be null. Parameter name: component
> > (System.Design)"
> > Details are:"
> > Program Location:
> >
> > at
> > System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetDesigner(IComponent
> > component)
> > at
> > Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDesigner(String
> > connectionString, Object connection, String objectUrn)
> > at
> > Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()"
> >
> > I saw one post that sugget there is a fix that ought to be in cumulative
> > update package 4, but I can't see any items in that which match this problem.
> >
> > The maintenance plans appear to run when called by the SQl Agent Jobs they
> > were initially set up with. However, I am calling one of them from another
> > Job and this has started throwing this error since SP2:
> > "Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
> > Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Description: The
> > Execute method on the task returned error code 0x80131904 (Conversion failed
> > when converting from a character string to uniqueidentifier.). The Execute
> > method must succeed<c/> and indicate the result using an "out" parameter.
> > End Error"
> >
> > but when I went to look at the plan, I couldn't edit it!
> >
> > Any advice on how to edit the maintenance plans or fix the second error
> > would be great.
> >
> > Thanks,
> >
> > Charles
> >
>
>

Cannot Edit Jobs

Two days back we have installed SP2 on SQLServer2005 Active/Active Cluster which result in failure.

Only Database Services and Analysis Services where not updated and rest of the services got updated.

After a restart , the behaviour of SQLServer is helarious.

We got into lot of problem so we opened support from Microsoft.

One of the problem i forgot to mentioed to Microsoft was on editing the Job i cannot see anything inside,all the entries where empty closing the job window and opening it again i got all my entries back but on editing i got the below mentioned Error.

Error:

Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error:c001f011(Microsoft.SqlServer.ManagedDTS)

If anyone faced the same problem and got any resolution please let me know.

Anyhelp will be appriciated.

Solved the Error.

In one of the artical i read tht after installation of SP2 few of the DLL left unregistered.

Registered the DTS.DLL and it work like charm.

"C:\Program Files\Microsoft SQL Server\90\DTS\Binn>regsvr32 dts.dll"

Hope this help to others.

sql

Cannot Deploy Reports to Report Server

I am in desperate need of help.
We have just set up SQL Server (2005, SP2) with RS on a Windows 2003 server.
None of us have ever deployed RS before. To make matters worse, all of our
network operations have been outsourced, so we do not have control of the
machine and the people who do don't know what they're doing either.
I can browse to <servername>\reports and to
<servername>\reportexecution2005.asmx. However when I try to browse to
<servername>\reportserver or try to deploy reports from VS2003, I get the
following error: The permissions granted to user 'ADSDOMAIN\ERichardson' are
insufficient for performing this operation. (rsAccessDenied) .
a)How should the permissions be set up so that I can deploy and manage the
reports?
b)How should the permissions be set up so that certain users can access the
Report Manager?
c)How should the permission be set up so that the majority of users can
access reports through links in the VS.Net application?
I know this is a lot of material to cover at once. We've got the blind
leading the blind here. Maybe we could start with how to grant me access to
deploy and manage the reports and then take it from there.
I would appreciate any help I can get. These outsourced people aren't going
to make the effort to figure this out. We're going to have to spoonfeed
them:-)
LizOn Sep 10, 12:40 pm, Liz <L...@.discussions.microsoft.com> wrote:
> I am in desperate need of help.
> We have just set up SQL Server (2005, SP2) with RS on a Windows 2003 server.
> None of us have ever deployed RS before. To make matters worse, all of our
> network operations have been outsourced, so we do not have control of the
> machine and the people who do don't know what they're doing either.
> I can browse to <servername>\reports and to
> <servername>\reportexecution2005.asmx. However when I try to browse to
> <servername>\reportserver or try to deploy reports from VS2003, I get the
> following error: The permissions granted to user 'ADSDOMAIN\ERichardson' are
> insufficient for performing this operation. (rsAccessDenied) .
> a)How should the permissions be set up so that I can deploy and manage the
> reports?
> b)How should the permissions be set up so that certain users can access the
> Report Manager?
> c)How should the permission be set up so that the majority of users can
> access reports through links in the VS.Net application?
> I know this is a lot of material to cover at once. We've got the blind
> leading the blind here. Maybe we could start with how to grant me access to
> deploy and manage the reports and then take it from there.
> I would appreciate any help I can get. These outsourced people aren't going
> to make the effort to figure this out. We're going to have to spoonfeed
> them:-)
> Liz
For Item (a), you may want to check the security on the Reports and
ReportServer Virtual Directories. You may want to change the Directory
Security (via right-clicking the virtual directories in IIS ->
Properties -> Directory Security tab -> Edit... button -> select
'Anonymous access' and 'Integrated Windows Authentication').
For Item (b), you set the user permissions in the Report Manager in
the second tab on the main page (I don't remember the name of it). You
can allow Browse, Publish, etc for various users that you add (note
that the standard windows format is: DOMAIN\User).
For Item (c), Browse permissions should be sufficient for most users
(refer to Item (b) response).
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Cannot Create Subscription

Using RS Standard, SP2, I am prevented from creating a subscription on
reports that I am able to schedule for snapshots. The error message says
"Subscriptions cannot be created because the credentials used to run the
report are not stored, the report is using user-defined parameter values, or
if a linked report, the report is no longer valid." There are no linked
reports involved, and there are both report parameters and query parameters,
but all have supplied values or defaults. (Since a snapshot works fine, it
would seem that criteria for a subscription would be satisfied). This is a
major problem for my users who believe subscription delivery is an essential
feature. Please help!
--
Bob RogersThen the only part of the error message your response didn't cover is the
credentials... They must be stored securely in the database... Go to the
datasource, and you may set the connection stuff to be stored in the
database... Then subscriptions can be made.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Bob Rogers" <BobRogers@.discussions.microsoft.com> wrote in message
news:1D97E909-7A7A-4617-ABF0-0610CF43B863@.microsoft.com...
> Using RS Standard, SP2, I am prevented from creating a subscription on
> reports that I am able to schedule for snapshots. The error message says
> "Subscriptions cannot be created because the credentials used to run the
> report are not stored, the report is using user-defined parameter values,
> or
> if a linked report, the report is no longer valid." There are no linked
> reports involved, and there are both report parameters and query
> parameters,
> but all have supplied values or defaults. (Since a snapshot works fine,
> it
> would seem that criteria for a subscription would be satisfied). This is
> a
> major problem for my users who believe subscription delivery is an
> essential
> feature. Please help!
> --
> Bob Rogers|||Thanks for your reply. The database credentials were good; the problem
turned out to be user id being included in the template for report footer --
user id is apparently considered a parameter.
--
Bob Rogers
"Wayne Snyder" wrote:
> Then the only part of the error message your response didn't cover is the
> credentials... They must be stored securely in the database... Go to the
> datasource, and you may set the connection stuff to be stored in the
> database... Then subscriptions can be made.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Bob Rogers" <BobRogers@.discussions.microsoft.com> wrote in message
> news:1D97E909-7A7A-4617-ABF0-0610CF43B863@.microsoft.com...
> > Using RS Standard, SP2, I am prevented from creating a subscription on
> > reports that I am able to schedule for snapshots. The error message says
> > "Subscriptions cannot be created because the credentials used to run the
> > report are not stored, the report is using user-defined parameter values,
> > or
> > if a linked report, the report is no longer valid." There are no linked
> > reports involved, and there are both report parameters and query
> > parameters,
> > but all have supplied values or defaults. (Since a snapshot works fine,
> > it
> > would seem that criteria for a subscription would be satisfied). This is
> > a
> > major problem for my users who believe subscription delivery is an
> > essential
> > feature. Please help!
> > --
> > Bob Rogers
>
>

Cannot create a connection to data source

I am running SQL Server 2005, SP2 on a Windows Server 2003, SP1.
When I open a report in the Report Server I get the following error:
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'ASCCSP'. (rsErrorOpeningConnection)
The ConnectionString property has not been initialized.
I am connecting to an Oracle database (using the Oracle client).
I have run into the problem before and have always been able to fix it by
giving the Web Service Identity, ASP.NET Service Account read/execute
permissions on the Oracle driver folder. This is not fixing the issue in
this case. The ASP.NET Service Account that I see in the Reporting Services
Configuration Manager is "NT Authority\Network Service". When I am adding
permissions to the security of the Oracle driver folder, I don't find an
exact match for this user (NT Authority\Network Service), I only find NETWORK
SERVICE. I gave NETWORK SERVICE read/execute rights to the Oracle client
folder. But no luck.
Any suggestions?
Thank you.
--
LaurieTCan you create a read-only user on the Oracle side and then enter those
credentials in the report connection?
"LaurieT" wrote:
> I am running SQL Server 2005, SP2 on a Windows Server 2003, SP1.
> When I open a report in the Report Server I get the following error:
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot create a connection to data source 'ASCCSP'. (rsErrorOpeningConnection)
> The ConnectionString property has not been initialized.
> I am connecting to an Oracle database (using the Oracle client).
> I have run into the problem before and have always been able to fix it by
> giving the Web Service Identity, ASP.NET Service Account read/execute
> permissions on the Oracle driver folder. This is not fixing the issue in
> this case. The ASP.NET Service Account that I see in the Reporting Services
> Configuration Manager is "NT Authority\Network Service". When I am adding
> permissions to the security of the Oracle driver folder, I don't find an
> exact match for this user (NT Authority\Network Service), I only find NETWORK
> SERVICE. I gave NETWORK SERVICE read/execute rights to the Oracle client
> folder. But no luck.
> Any suggestions?
> Thank you.
> --
> LaurieT|||The issue is not with accessing the report data in Oracle (this works fine in
the business intelligence development studio, I can preview the reports here
with no issue) ... it is just with getting the Oracle client to run. When I
try to run reports through the Report Manager, I believe that Reporting
Services uses the Web Service Identity account to access and run the Oracle
client and in my case, it does not have the correct permissions to access and
run the client ... but I can't figure out how to change it.
--
LaurieT
"lonnye" wrote:
> Can you create a read-only user on the Oracle side and then enter those
> credentials in the report connection?
> "LaurieT" wrote:
> > I am running SQL Server 2005, SP2 on a Windows Server 2003, SP1.
> >
> > When I open a report in the Report Server I get the following error:
> > An error has occurred during report processing. (rsProcessingAborted)
> > Cannot create a connection to data source 'ASCCSP'. (rsErrorOpeningConnection)
> > The ConnectionString property has not been initialized.
> >
> > I am connecting to an Oracle database (using the Oracle client).
> >
> > I have run into the problem before and have always been able to fix it by
> > giving the Web Service Identity, ASP.NET Service Account read/execute
> > permissions on the Oracle driver folder. This is not fixing the issue in
> > this case. The ASP.NET Service Account that I see in the Reporting Services
> > Configuration Manager is "NT Authority\Network Service". When I am adding
> > permissions to the security of the Oracle driver folder, I don't find an
> > exact match for this user (NT Authority\Network Service), I only find NETWORK
> > SERVICE. I gave NETWORK SERVICE read/execute rights to the Oracle client
> > folder. But no luck.
> >
> > Any suggestions?
> >
> > Thank you.
> > --
> > LaurieT|||You can change the service accounts by using the Reporting Services
Configuration Tool... Here is a link to more info on how to do this:
http://technet.microsoft.com/en-us/library/bb326419.aspx
--
~lb
"LaurieT" wrote:
> The issue is not with accessing the report data in Oracle (this works fine in
> the business intelligence development studio, I can preview the reports here
> with no issue) ... it is just with getting the Oracle client to run. When I
> try to run reports through the Report Manager, I believe that Reporting
> Services uses the Web Service Identity account to access and run the Oracle
> client and in my case, it does not have the correct permissions to access and
> run the client ... but I can't figure out how to change it.
> --
> LaurieT
>
> "lonnye" wrote:
> > Can you create a read-only user on the Oracle side and then enter those
> > credentials in the report connection?
> >
> > "LaurieT" wrote:
> >
> > > I am running SQL Server 2005, SP2 on a Windows Server 2003, SP1.
> > >
> > > When I open a report in the Report Server I get the following error:
> > > An error has occurred during report processing. (rsProcessingAborted)
> > > Cannot create a connection to data source 'ASCCSP'. (rsErrorOpeningConnection)
> > > The ConnectionString property has not been initialized.
> > >
> > > I am connecting to an Oracle database (using the Oracle client).
> > >
> > > I have run into the problem before and have always been able to fix it by
> > > giving the Web Service Identity, ASP.NET Service Account read/execute
> > > permissions on the Oracle driver folder. This is not fixing the issue in
> > > this case. The ASP.NET Service Account that I see in the Reporting Services
> > > Configuration Manager is "NT Authority\Network Service". When I am adding
> > > permissions to the security of the Oracle driver folder, I don't find an
> > > exact match for this user (NT Authority\Network Service), I only find NETWORK
> > > SERVICE. I gave NETWORK SERVICE read/execute rights to the Oracle client
> > > folder. But no luck.
> > >
> > > Any suggestions?
> > >
> > > Thank you.
> > > --
> > > LaurieT

Cannot connect with SQL Server Management Studio to SQL2K5

Hi
we are using SQL 2005 SP2 cluster with 3 instances. We are trying to connect
with SQL Server Management Studio thrue a Firewall that have only port
1433/TCP open. This has worked with SQL Auth and SQL 2000 perfectly. I also
tried to add 1433/UDP, 1434/TCP and 1434/UDP, but haven't had any success.
On the machines themself the connection is working well... i'm connecting to
the instances with server name "CLU1INS1\Instance1", "CLU1INS2\Instance2"
and "CLU1INS3\Instance3" and SQL Auth, but from remote it is not working.
What could be wrong here and how are we able to solve this problem?
Regards
MarcMarc
Do you get an error? If so , what?
"Marc Bauer" <marc.bau@.gmx.net> wrote in message
news:u06scMCXIHA.4440@.TK2MSFTNGP06.phx.gbl...
> Hi
> we are using SQL 2005 SP2 cluster with 3 instances. We are trying to
> connect with SQL Server Management Studio thrue a Firewall that have only
> port 1433/TCP open. This has worked with SQL Auth and SQL 2000 perfectly.
> I also tried to add 1433/UDP, 1434/TCP and 1434/UDP, but haven't had any
> success.
> On the machines themself the connection is working well... i'm connecting
> to the instances with server name "CLU1INS1\Instance1",
> "CLU1INS2\Instance2" and "CLU1INS3\Instance3" and SQL Auth, but from
> remote it is not working.
> What could be wrong here and how are we able to solve this problem?
>
> Regards
> Marc
>
>|||Only default instance of SQL Server (referring to it by computer's name)
uses port 1433, named instance (computerName\instanceName) uses other
port/dynamic port. You must determine which port the named SQL Server
instance uses and allow the port on the firewall.
"Marc Bauer" <marc.bau@.gmx.net> wrote in message
news:u06scMCXIHA.4440@.TK2MSFTNGP06.phx.gbl...
> Hi
> we are using SQL 2005 SP2 cluster with 3 instances. We are trying to
> connect with SQL Server Management Studio thrue a Firewall that have only
> port 1433/TCP open. This has worked with SQL Auth and SQL 2000 perfectly.
> I also tried to add 1433/UDP, 1434/TCP and 1434/UDP, but haven't had any
> success.
> On the machines themself the connection is working well... i'm connecting
> to the instances with server name "CLU1INS1\Instance1",
> "CLU1INS2\Instance2" and "CLU1INS3\Instance3" and SQL Auth, but from
> remote it is not working.
> What could be wrong here and how are we able to solve this problem?
>
> Regards
> Marc
>
>|||hi
> Only default instance of SQL Server (referring to it by computer's name)
> uses port 1433, named instance (computerName\instanceName) uses other
> port/dynamic port. You must determine which port the named SQL Server
> instance uses and allow the port on the firewall.
Ups... never heard about this... where can i change this setting? Every
instance has it's own IP... so i don't know why this should be dynamic...
Marc|||It is port, not IP Address. At the same IP address, different applications
use different ports. SQL Server's default instance uses port 1433 by
default, named instance uses different port. but you could configure it to
use whatever port you see fits. Use SQL Server's server configuration tool
to examine/set TCP/IP port used by an SQL Server instance.
"Marc Bauer" <marc.bau@.gmx.net> wrote in message
news:%23DQg3yDXIHA.4684@.TK2MSFTNGP06.phx.gbl...
> hi
>> Only default instance of SQL Server (referring to it by computer's name)
>> uses port 1433, named instance (computerName\instanceName) uses other
>> port/dynamic port. You must determine which port the named SQL Server
>> instance uses and allow the port on the firewall.
> Ups... never heard about this... where can i change this setting? Every
> instance has it's own IP... so i don't know why this should be dynamic...
>
> Marc
>|||Hi
> It is port, not IP Address. At the same IP address, different applications
Yep, i know, but i tried to understand why instances have dynamic ports...
normaly every instance need it's own IP adrress. If this is the case i can
bind 1433 to every instance without any collisions, isn't it?
> use different ports. SQL Server's default instance uses port 1433 by
> default, named instance uses different port. but you could configure it to
> use whatever port you see fits. Use SQL Server's server configuration tool
> to examine/set TCP/IP port used by an SQL Server instance.
This settings tool is somewhat strange... "0" enables dynamic ports and
"blank" disabled this... however there is a "AllIP" setting that have a
dynamic port value of 1512 (what ever this means). I switched this to blank
value and set the Port to 1433. Should this work as expected? I've only done
this on a testing system... not sure if i must configure every instance for
it's own or if there is a global setting.
Gruss
Alex

Cannot connect to SQL server over network after SP2

Hello,
I'll try my luck in this group before I re-install the whole thing.
I'm running MS SQL Server 2005 developer edition on the Windows Server
2003 Small Business Edition.
Few days ago I have updated to the SP2 via windows update.
Since then I cannot connect to the SQL server remotely (using
Management Studio).
- If I log remotely to the server box I can connect locally and all
looks fine.
However, from the network it does not work.
- The SQL Server browser is running..
- TCP & Named Pipes are enabled.
- No errors in the Event Viewer
- "Allow remote connections to this server" property is enabled
- Both firewalls (server & client) are off.
- Both authentication types (SQL auth / Windows auth) are not working
Has anyone had similar problem? Any ideas?
Thank you,
Damir Sudarevic
What is the error message you are getting? We just finished installing SP2
on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
log event at all? Or when trying to access the server from remote location
the computer refuses to see the SQL server?
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:

> Hello,
> I'll try my luck in this group before I re-install the whole thing.
> I'm running MS SQL Server 2005 developer edition on the Windows Server
> 2003 Small Business Edition.
> Few days ago I have updated to the SP2 via windows update.
> Since then I cannot connect to the SQL server remotely (using
> Management Studio).
> - If I log remotely to the server box I can connect locally and all
> looks fine.
> However, from the network it does not work.
> - The SQL Server browser is running..
> - TCP & Named Pipes are enabled.
> - No errors in the Event Viewer
> - "Allow remote connections to this server" property is enabled
> - Both firewalls (server & client) are off.
> - Both authentication types (SQL auth / Windows auth) are not working
>
> Has anyone had similar problem? Any ideas?
> Thank you,
> Damir Sudarevic
>
|||On Jun 27, 8:12 pm, Mohit K. Gupta
<MohitKGu...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> What is the error message you are getting? We just finished installingSP2
> on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> log event at all? Or when trying to access the server from remote location
> the computer refuses to see the SQL server?
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
>
>
>
>
Hi,
No error messages. The Management Studio (from remote clients - more
than one) simply hangs up.
The studio actually sees the server (in browse servers), but
connection can not be established.
If I log in remotely to the server box and start MS over there it
works fine.
Thanks.
|||Hangs up? SO you have to kill the SSMS and then you can use the computer,
only thing I had that is when our network guys mucked up the firewall
settings. Check for port 1433 connection.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:

> On Jun 27, 8:12 pm, Mohit K. Gupta
> <MohitKGu...@.discussions.microsoft.com> wrote:
> Hi,
> No error messages. The Management Studio (from remote clients - more
> than one) simply hangs up.
> The studio actually sees the server (in browse servers), but
> connection can not be established.
> If I log in remotely to the server box and start MS over there it
> works fine.
> Thanks.
>
|||On Jun 29, 1:28 pm, Mohit K. Gupta <mohitkgu...@.msn.com> wrote:[vbcol=seagreen]
> Hangs up? SO you have to kill the SSMS and then you can use the computer,
> only thing I had that is when our network guys mucked up the firewall
> settings. Check for port 1433 connection.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
>
>
>
>
>
>
>
Works!
Thank you Mohit, it was (something) about the ports. Changed TCP ports
to Dynamic and everything started working. Not quite sure what is
dynamic vs 1433; but as long as it works...
Thanks again,
Damir

Cannot connect to SQL server over network after SP2

Hello,
I'll try my luck in this group before I re-install the whole thing.
I'm running MS SQL Server 2005 developer edition on the Windows Server
2003 Small Business Edition.
Few days ago I have updated to the SP2 via windows update.
Since then I cannot connect to the SQL server remotely (using
Management Studio).
- If I log remotely to the server box I can connect locally and all
looks fine.
However, from the network it does not work.
- The SQL Server browser is running..
- TCP & Named Pipes are enabled.
- No errors in the Event Viewer
- "Allow remote connections to this server" property is enabled
- Both firewalls (server & client) are off.
- Both authentication types (SQL auth / Windows auth) are not working
Has anyone had similar problem? Any ideas?
Thank you,
Damir SudarevicWhat is the error message you are getting? We just finished installing SP2
on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
log event at all? Or when trying to access the server from remote location
the computer refuses to see the SQL server?
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:

> Hello,
> I'll try my luck in this group before I re-install the whole thing.
> I'm running MS SQL Server 2005 developer edition on the Windows Server
> 2003 Small Business Edition.
> Few days ago I have updated to the SP2 via windows update.
> Since then I cannot connect to the SQL server remotely (using
> Management Studio).
> - If I log remotely to the server box I can connect locally and all
> looks fine.
> However, from the network it does not work.
> - The SQL Server browser is running..
> - TCP & Named Pipes are enabled.
> - No errors in the Event Viewer
> - "Allow remote connections to this server" property is enabled
> - Both firewalls (server & client) are off.
> - Both authentication types (SQL auth / Windows auth) are not working
>
> Has anyone had similar problem? Any ideas?
> Thank you,
> Damir Sudarevic
>|||On Jun 27, 8:12 pm, Mohit K. Gupta
<MohitKGu...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> What is the error message you are getting? We just finished installingSP2
> on SQL 2005 EE, and no problems at all. Does it contain Login Failed erro
r
> log event at all? Or when trying to access the server from remote locatio
n
> the computer refuses to see the SQL server?
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
>
>
>
>
>
>
>
>
>
Hi,
No error messages. The Management Studio (from remote clients - more
than one) simply hangs up.
The studio actually sees the server (in browse servers), but
connection can not be established.
If I log in remotely to the server box and start MS over there it
works fine.
Thanks.|||Hangs up? SO you have to kill the SSMS and then you can use the computer,
only thing I had that is when our network guys mucked up the firewall
settings. Check for port 1433 connection.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:

> On Jun 27, 8:12 pm, Mohit K. Gupta
> <MohitKGu...@.discussions.microsoft.com> wrote:
> Hi,
> No error messages. The Management Studio (from remote clients - more
> than one) simply hangs up.
> The studio actually sees the server (in browse servers), but
> connection can not be established.
> If I log in remotely to the server box and start MS over there it
> works fine.
> Thanks.
>|||On Jun 29, 1:28 pm, Mohit K. Gupta <mohitkgu...@.msn.com> wrote:[vbcol=seagreen]
> Hangs up? SO you have to kill the SSMS and then you can use the computer,
> only thing I had that is when our network guys mucked up the firewall
> settings. Check for port 1433 connection.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Works!
Thank you Mohit, it was (something) about the ports. Changed TCP ports
to Dynamic and everything started working. Not quite sure what is
dynamic vs 1433; but as long as it works...
Thanks again,
Damir

Cannot connect to SQL server over network after SP2

Hello,
I'll try my luck in this group before I re-install the whole thing.
I'm running MS SQL Server 2005 developer edition on the Windows Server
2003 Small Business Edition.
Few days ago I have updated to the SP2 via windows update.
Since then I cannot connect to the SQL server remotely (using
Management Studio).
- If I log remotely to the server box I can connect locally and all
looks fine.
However, from the network it does not work.
- The SQL Server browser is running..
- TCP & Named Pipes are enabled.
- No errors in the Event Viewer
- "Allow remote connections to this server" property is enabled
- Both firewalls (server & client) are off.
- Both authentication types (SQL auth / Windows auth) are not working
Has anyone had similar problem? Any ideas?
Thank you,
Damir SudarevicWhat is the error message you are getting? We just finished installing SP2
on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
log event at all? Or when trying to access the server from remote location
the computer refuses to see the SQL server?
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:
> Hello,
> I'll try my luck in this group before I re-install the whole thing.
> I'm running MS SQL Server 2005 developer edition on the Windows Server
> 2003 Small Business Edition.
> Few days ago I have updated to the SP2 via windows update.
> Since then I cannot connect to the SQL server remotely (using
> Management Studio).
> - If I log remotely to the server box I can connect locally and all
> looks fine.
> However, from the network it does not work.
> - The SQL Server browser is running..
> - TCP & Named Pipes are enabled.
> - No errors in the Event Viewer
> - "Allow remote connections to this server" property is enabled
> - Both firewalls (server & client) are off.
> - Both authentication types (SQL auth / Windows auth) are not working
>
> Has anyone had similar problem? Any ideas?
> Thank you,
> Damir Sudarevic
>|||On Jun 27, 8:12 pm, Mohit K. Gupta
<MohitKGu...@.discussions.microsoft.com> wrote:
> What is the error message you are getting? We just finished installingSP2
> on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> log event at all? Or when trying to access the server from remote location
> the computer refuses to see the SQL server?
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
> > Hello,
> > I'll try my luck in this group before I re-install the whole thing.
> > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > 2003 Small Business Edition.
> > Few days ago I have updated to theSP2via windows update.
> > Since then Icannotconnectto the SQL server remotely (using
> > Management Studio).
> > - If I log remotely to the server box I canconnectlocally and all
> > looks fine.
> > However, from the network it does not work.
> > - The SQL Server browser is running..
> > - TCP & Named Pipes are enabled.
> > - No errors in the Event Viewer
> > - "Allow remote connections to this server" property is enabled
> > - Both firewalls (server & client) are off.
> > - Both authentication types (SQL auth / Windows auth) are not working
> > Has anyone had similar problem? Any ideas?
> > Thank you,
> > Damir Sudarevic
Hi,
No error messages. The Management Studio (from remote clients - more
than one) simply hangs up.
The studio actually sees the server (in browse servers), but
connection can not be established.
If I log in remotely to the server box and start MS over there it
works fine.
Thanks.|||Hangs up? SO you have to kill the SSMS and then you can use the computer,
only thing I had that is when our network guys mucked up the firewall
settings. Check for port 1433 connection.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:
> On Jun 27, 8:12 pm, Mohit K. Gupta
> <MohitKGu...@.discussions.microsoft.com> wrote:
> > What is the error message you are getting? We just finished installingSP2
> > on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> > log event at all? Or when trying to access the server from remote location
> > the computer refuses to see the SQL server?
> >
> > --
> > Mohit K. Gupta
> > B.Sc. CS, Minor Japanese
> > MCTS: SQL Server 2005
> >
> > "Damir" wrote:
> > > Hello,
> >
> > > I'll try my luck in this group before I re-install the whole thing.
> >
> > > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > > 2003 Small Business Edition.
> >
> > > Few days ago I have updated to theSP2via windows update.
> > > Since then Icannotconnectto the SQL server remotely (using
> > > Management Studio).
> >
> > > - If I log remotely to the server box I canconnectlocally and all
> > > looks fine.
> >
> > > However, from the network it does not work.
> >
> > > - The SQL Server browser is running..
> > > - TCP & Named Pipes are enabled.
> > > - No errors in the Event Viewer
> > > - "Allow remote connections to this server" property is enabled
> > > - Both firewalls (server & client) are off.
> > > - Both authentication types (SQL auth / Windows auth) are not working
> >
> > > Has anyone had similar problem? Any ideas?
> >
> > > Thank you,
> >
> > > Damir Sudarevic
> Hi,
> No error messages. The Management Studio (from remote clients - more
> than one) simply hangs up.
> The studio actually sees the server (in browse servers), but
> connection can not be established.
> If I log in remotely to the server box and start MS over there it
> works fine.
> Thanks.
>|||On Jun 29, 1:28 pm, Mohit K. Gupta <mohitkgu...@.msn.com> wrote:
> Hangs up? SO you have to kill the SSMS and then you can use the computer,
> only thing I had that is when our network guys mucked up the firewall
> settings. Check for port 1433 connection.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
> > On Jun 27, 8:12 pm, Mohit K. Gupta
> > <MohitKGu...@.discussions.microsoft.com> wrote:
> > > What is the error message you are getting? We just finished installingSP2
> > > on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> > > log event at all? Or when trying to access the server from remote location
> > > the computer refuses to see the SQL server?
> > > --
> > > Mohit K. Gupta
> > > B.Sc. CS, Minor Japanese
> > > MCTS: SQL Server 2005
> > > "Damir" wrote:
> > > > Hello,
> > > > I'll try my luck in this group before I re-install the whole thing.
> > > > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > > > 2003 Small Business Edition.
> > > > Few days ago I have updated to theSP2via windows update.
> > > > Since then Icannotconnectto the SQL server remotely (using
> > > > Management Studio).
> > > > - If I log remotely to the server box I canconnectlocally and all
> > > > looks fine.
> > > > However, from the network it does not work.
> > > > - The SQL Server browser is running..
> > > > - TCP & Named Pipes are enabled.
> > > > - No errors in the Event Viewer
> > > > - "Allow remote connections to this server" property is enabled
> > > > - Both firewalls (server & client) are off.
> > > > - Both authentication types (SQL auth / Windows auth) are not working
> > > > Has anyone had similar problem? Any ideas?
> > > > Thank you,
> > > > Damir Sudarevic
> > Hi,
> > No error messages. The Management Studio (from remote clients - more
> > than one) simply hangs up.
> > The studio actually sees the server (in browse servers), but
> > connection can not be established.
> > If I log in remotely to the server box and start MS over there it
> > works fine.
> > Thanks.
Works!
Thank you Mohit, it was (something) about the ports. Changed TCP ports
to Dynamic and everything started working. Not quite sure what is
dynamic vs 1433; but as long as it works...
Thanks again,
Damir

Cannot connect to SQL Server 2000.

I have installed Windows XP SP2 RC2 on a machine with SQL Server 2000. I ca
nnot connect to that machine's port 1433. I have disabled the Windows Firew
all. I have run netstat -a to check what ports are listening but I don't se
e port 1433 and port 1434.
I have not tried telnet to that port yet.Is this a default instance or a named instance.
A named instance need not listen on the 1433 port.
You can use the server network utility to find out what port sql is
listening on.
Then you can try telneting to that port.
hth
Vikram
"peter" <peter@.discussions.microsoft.com> wrote in message
news:1D686B59-EDFD-493D-A34C-72F68BE9D8CB@.microsoft.com...
> I have installed Windows XP SP2 RC2 on a machine with SQL Server 2000. I
cannot connect to that machine's port 1433. I have disabled the Windows
Firewall. I have run netstat -a to check what ports are listening but I
don't see port 1433 and port 1434.
> I have not tried telnet to that port yet.|||Hi Vikram,
This is a default instance and Server Network Utility is showing 1433.
I have tried telnet ip address 1433 on that Windows XP SP2 RC2 and cannot be
connected.
I have checked SQL Server Logs and noticed that SQL Server is only listening
on Shared Memory and Named Pipes. I have checked the log before XP SP2 RC2
is applied, the SQL Server was listening on TCP, Shared Memory and Named Pi
pes. How can I make SQL Se
rver listening on TCP? My understanding is that it should be based on what h
as been setup in the Server Network Utility. I have tried to disable and th
en enable TCP/IP but SQL Server is still only listening to Shared Memory and
Named Pipes.
"Vikram Vamshi" wrote:

> Is this a default instance or a named instance.
> A named instance need not listen on the 1433 port.
> You can use the server network utility to find out what port sql is
> listening on.
> Then you can try telneting to that port.
> hth
> Vikram
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:1D686B59-EDFD-493D-A34C-72F68BE9D8CB@.microsoft.com...
> cannot connect to that machine's port 1433. I have disabled the Windows
> Firewall. I have run netstat -a to check what ports are listening but I
> don't see port 1433 and port 1434.
>
>|||Hi Vikram,
I forget to mention in my last post that the SQL Server 2000 has only been a
pplied with SP2 not SP3a.
"peter" wrote:

> Hi Vikram,
> This is a default instance and Server Network Utility is showing 1433.
> I have tried telnet ip address 1433 on that Windows XP SP2 RC2 and cannot
be connected.
> I have checked SQL Server Logs and noticed that SQL Server is only listening on Sh
ared Memory and Named Pipes. I have checked the log before XP SP2 RC2 is applied, t
he SQL Server was listening on TCP, Shared Memory and Named Pipes. How can I make S
QL
Server listening on TCP? My understanding is that it should be based on what has been setup
in the Server Network Utility. I have tried to disable and then enable TCP/IP but SQL Serve
r is still only listening to Shared Memory and Named Pipes.[vbcol=seagreen]
> "Vikram Vamshi" wrote:
>|||Did you look at your sql server log?
If it is listening on tcp/ip it should have something like:
2004-06-18 20:01:46.93 server Using 'SSNETLIB.DLL' version '8.0.818'.
2004-06-18 20:01:46.95 server SQL server listening on 192.168.0.101:
1433.
2004-06-18 20:01:46.95 server SQL server listening on 127.0.0.1: 1433.
2004-06-18 20:01:46.96 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-06-18 20:01:46.96 server SQL Server is ready for client connections
hth
Vikram
Vikram Vamshi
Eclipsys Corporation
"peter" <peter@.discussions.microsoft.com> wrote in message
news:28229D3F-05BB-4354-A333-870335CDD1E4@.microsoft.com...
> Hi Vikram,
> I forget to mention in my last post that the SQL Server 2000 has only been
applied with SP2 not SP3a.[vbcol=seagreen]
> "peter" wrote:
>
cannot be connected.[vbcol=seagreen]
listening on Shared Memory and Named Pipes. I have checked the log before
XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory
and Named Pipes. How can I make SQL Server listening on TCP? My
understanding is that it should be based on what has been setup in the
Server Network Utility. I have tried to disable and then enable TCP/IP but
SQL Server is still only listening to Shared Memory and Named Pipes.[vbcol=seagreen]
2000. I[vbcol=seagreen]
Windows[vbcol=seagreen]
I[vbcol=seagreen]|||Sorry,
I did not read your post completely.
You may want to check the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketNet
Lib\Tcp
tcpport should be 1433
Vikram
--
Vikram Vamshi
Eclipsys Corporation
"Vikram Vamshi" <vikram.vamshi@.nospam.com> wrote in message
news:eQMqdyyVEHA.384@.TK2MSFTNGP10.phx.gbl...
> Did you look at your sql server log?
> If it is listening on tcp/ip it should have something like:
> 2004-06-18 20:01:46.93 server Using 'SSNETLIB.DLL' version '8.0.818'.
> 2004-06-18 20:01:46.95 server SQL server listening on 192.168.0.101:
> 1433.
> 2004-06-18 20:01:46.95 server SQL server listening on 127.0.0.1: 1433.
> 2004-06-18 20:01:46.96 server SQL server listening on TCP, Shared
Memory,
> Named Pipes.
> 2004-06-18 20:01:46.96 server SQL Server is ready for client
connections
> hth
> Vikram
> --
> Vikram Vamshi
> Eclipsys Corporation
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:28229D3F-05BB-4354-A333-870335CDD1E4@.microsoft.com...
been[vbcol=seagreen]
> applied with SP2 not SP3a.
> cannot be connected.
> listening on Shared Memory and Named Pipes. I have checked the log before
> XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory
> and Named Pipes. How can I make SQL Server listening on TCP? My
> understanding is that it should be based on what has been setup in the
> Server Network Utility. I have tried to disable and then enable TCP/IP
but
> SQL Server is still only listening to Shared Memory and Named Pipes.
> 2000. I
> Windows
but[vbcol=seagreen]
> I
>|||And you missed my 3rd post
Did you check the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketNet
Lib\Tcp
tcpport should be 1433
vikram
Vikram Vamshi
Eclipsys Corporation
"peter" <peter@.discussions.microsoft.com> wrote in message
news:F3928A71-8F08-4C0A-AD09-D2CB6297BEC6@.microsoft.com...
> Hi Vikram,
> I guess you missed my 2nd post. I repost part of 2nd post here:
> I have checked SQL Server Logs and noticed that SQL Server is only
> listening on Shared Memory and Named Pipes. I have checked the log before
> XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory
> and Named Pipes. How can I make SQL Server listening on TCP? My
> understanding is that it should be based on what has been setup in the
> Server Network Utility. I have tried to disable and then enable TCP/IP
but
> SQL Server is still only listening to Shared Memory and Named Pipes.
> It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433).
But I think it cannot be true for MS to make such mistake.[vbcol=seagreen]
> "Vikram Vamshi" wrote:
>
1433.[vbcol=seagreen]
Memory,[vbcol=seagreen]
connections[vbcol=seagreen]
been[vbcol=seagreen]
1433.[vbcol=seagreen]
before[vbcol=seagreen]
Memory[vbcol=seagreen]
but[vbcol=seagreen]
is[vbcol=seagreen]
but[vbcol=seagreen]|||Hi Vikram,
I checked that registry and it has 1433.
It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433). But
I think it cannot be true for MS to make such mistake.
"Vikram Vamshi" wrote:

> Sorry,
> I did not read your post completely.
> You may want to check the following registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketN
et
> Lib\Tcp
> tcpport should be 1433
> Vikram
> --
> Vikram Vamshi
> Eclipsys Corporation
> "Vikram Vamshi" <vikram.vamshi@.nospam.com> wrote in message
> news:eQMqdyyVEHA.384@.TK2MSFTNGP10.phx.gbl...
> Memory,
> connections
> been
> but
> but
>
>|||I very much doubt that (of course you can never be sure with M$ )
I heard that sp2 was a major security overhaul, but that should not change
the applications (like sql server).
Can you post your sql server errorlog?
also make sure that tcp is listed in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketNet
Lib
Vikram
Vikram Vamshi
Eclipsys Corporation
"peter" <peter@.discussions.microsoft.com> wrote in message
news:C40DF985-F005-4766-AE43-D06AFF9F6499@.microsoft.com...
> Hi Vikram,
> I checked that registry and it has 1433.
> It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433).
But I think it cannot be true for MS to make such mistake.[vbcol=seagreen]
> "Vikram Vamshi" wrote:
>
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketNet[vbc
ol=seagreen]
'8.0.818'.[vbcol=seagreen]
192.168.0.101:[vbcol=seagreen]
1433.[vbcol=seagreen]
only[vbcol=seagreen]
1433.[vbcol=seagreen]
before[vbcol=seagreen]
Memory[vbcol=seagreen]
TCP/IP[vbcol=seagreen]
is[vbcol=seagreen]
Server[vbcol=seagreen]
listening[vbcol=seagreen]|||Hi Vikram,
I did not miss your 3rd post, but I guess I'm posting my reply when you post
this one. Anyway, here is the reply:
Hi Vikram,
I checked that registry and it has 1433.
It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433). But
I think it cannot be true for MS to make such mistake.
"Vikram Vamshi" wrote:

> And you missed my 3rd post
> Did you check the registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketN
et
> Lib\Tcp
> tcpport should be 1433
> vikram
> --
> Vikram Vamshi
> Eclipsys Corporation
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:F3928A71-8F08-4C0A-AD09-D2CB6297BEC6@.microsoft.com...
> but
> But I think it cannot be true for MS to make such mistake.
> 1433.
> Memory,
> connections
> been
> 1433.
> before
> Memory
> but
> is
> but
>
>

Cannot connect to SQL Server 2000.

I have installed Windows XP SP2 RC2 on a machine with SQL Server 2000. I cannot connect to that machine's port 1433. I have disabled the Windows Firewall. I have run netstat -a to check what ports are listening but I don't see port 1433 and port 1434.
I have not tried telnet to that port yet.
Is this a default instance or a named instance.
A named instance need not listen on the 1433 port.
You can use the server network utility to find out what port sql is
listening on.
Then you can try telneting to that port.
hth
Vikram
"peter" <peter@.discussions.microsoft.com> wrote in message
news:1D686B59-EDFD-493D-A34C-72F68BE9D8CB@.microsoft.com...
> I have installed Windows XP SP2 RC2 on a machine with SQL Server 2000. I
cannot connect to that machine's port 1433. I have disabled the Windows
Firewall. I have run netstat -a to check what ports are listening but I
don't see port 1433 and port 1434.
> I have not tried telnet to that port yet.
|||Hi Vikram,
This is a default instance and Server Network Utility is showing 1433.
I have tried telnet ip address 1433 on that Windows XP SP2 RC2 and cannot be connected.
I have checked SQL Server Logs and noticed that SQL Server is only listening on Shared Memory and Named Pipes. I have checked the log before XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory and Named Pipes. How can I make SQL Se
rver listening on TCP? My understanding is that it should be based on what has been setup in the Server Network Utility. I have tried to disable and then enable TCP/IP but SQL Server is still only listening to Shared Memory and Named Pipes.
"Vikram Vamshi" wrote:

> Is this a default instance or a named instance.
> A named instance need not listen on the 1433 port.
> You can use the server network utility to find out what port sql is
> listening on.
> Then you can try telneting to that port.
> hth
> Vikram
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:1D686B59-EDFD-493D-A34C-72F68BE9D8CB@.microsoft.com...
> cannot connect to that machine's port 1433. I have disabled the Windows
> Firewall. I have run netstat -a to check what ports are listening but I
> don't see port 1433 and port 1434.
>
>
|||Hi Vikram,
I forget to mention in my last post that the SQL Server 2000 has only been applied with SP2 not SP3a.
"peter" wrote:

> Hi Vikram,
> This is a default instance and Server Network Utility is showing 1433.
> I have tried telnet ip address 1433 on that Windows XP SP2 RC2 and cannot be connected.
> I have checked SQL Server Logs and noticed that SQL Server is only listening on Shared Memory and Named Pipes. I have checked the log before XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory and Named Pipes. How can I make SQL
Server listening on TCP? My understanding is that it should be based on what has been setup in the Server Network Utility. I have tried to disable and then enable TCP/IP but SQL Server is still only listening to Shared Memory and Named Pipes.[vbcol=seagreen]
> "Vikram Vamshi" wrote:
|||Did you look at your sql server log?
If it is listening on tcp/ip it should have something like:
2004-06-18 20:01:46.93 server Using 'SSNETLIB.DLL' version '8.0.818'.
2004-06-18 20:01:46.95 server SQL server listening on 192.168.0.101:
1433.
2004-06-18 20:01:46.95 server SQL server listening on 127.0.0.1: 1433.
2004-06-18 20:01:46.96 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-06-18 20:01:46.96 server SQL Server is ready for client connections
hth
Vikram
Vikram Vamshi
Eclipsys Corporation
"peter" <peter@.discussions.microsoft.com> wrote in message
news:28229D3F-05BB-4354-A333-870335CDD1E4@.microsoft.com...
> Hi Vikram,
> I forget to mention in my last post that the SQL Server 2000 has only been
applied with SP2 not SP3a.[vbcol=seagreen]
> "peter" wrote:
cannot be connected.[vbcol=seagreen]
listening on Shared Memory and Named Pipes. I have checked the log before
XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory
and Named Pipes. How can I make SQL Server listening on TCP? My
understanding is that it should be based on what has been setup in the
Server Network Utility. I have tried to disable and then enable TCP/IP but
SQL Server is still only listening to Shared Memory and Named Pipes.[vbcol=seagreen]
2000. I[vbcol=seagreen]
Windows[vbcol=seagreen]
I[vbcol=seagreen]
|||Sorry,
I did not read your post completely.
You may want to check the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\SuperSocketNet
Lib\Tcp
tcpport should be 1433
Vikram
Vikram Vamshi
Eclipsys Corporation
"Vikram Vamshi" <vikram.vamshi@.nospam.com> wrote in message
news:eQMqdyyVEHA.384@.TK2MSFTNGP10.phx.gbl...
> Did you look at your sql server log?
> If it is listening on tcp/ip it should have something like:
> 2004-06-18 20:01:46.93 server Using 'SSNETLIB.DLL' version '8.0.818'.
> 2004-06-18 20:01:46.95 server SQL server listening on 192.168.0.101:
> 1433.
> 2004-06-18 20:01:46.95 server SQL server listening on 127.0.0.1: 1433.
> 2004-06-18 20:01:46.96 server SQL server listening on TCP, Shared
Memory,
> Named Pipes.
> 2004-06-18 20:01:46.96 server SQL Server is ready for client
connections[vbcol=seagreen]
> hth
> Vikram
> --
> Vikram Vamshi
> Eclipsys Corporation
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:28229D3F-05BB-4354-A333-870335CDD1E4@.microsoft.com...
been
> applied with SP2 not SP3a.
> cannot be connected.
> listening on Shared Memory and Named Pipes. I have checked the log before
> XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory
> and Named Pipes. How can I make SQL Server listening on TCP? My
> understanding is that it should be based on what has been setup in the
> Server Network Utility. I have tried to disable and then enable TCP/IP
but[vbcol=seagreen]
> SQL Server is still only listening to Shared Memory and Named Pipes.
> 2000. I
> Windows
but
> I
>
|||Hi Vikram,
I guess you missed my 2nd post. I repost part of 2nd post here:
I have checked SQL Server Logs and noticed that SQL Server is only
listening on Shared Memory and Named Pipes. I have checked the log before
XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory
and Named Pipes. How can I make SQL Server listening on TCP? My
understanding is that it should be based on what has been setup in the
Server Network Utility. I have tried to disable and then enable TCP/IP but
SQL Server is still only listening to Shared Memory and Named Pipes.
It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433). But I think it cannot be true for MS to make such mistake.
"Vikram Vamshi" wrote:

> Did you look at your sql server log?
> If it is listening on tcp/ip it should have something like:
> 2004-06-18 20:01:46.93 server Using 'SSNETLIB.DLL' version '8.0.818'.
> 2004-06-18 20:01:46.95 server SQL server listening on 192.168.0.101:
> 1433.
> 2004-06-18 20:01:46.95 server SQL server listening on 127.0.0.1: 1433.
> 2004-06-18 20:01:46.96 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2004-06-18 20:01:46.96 server SQL Server is ready for client connections
> hth
> Vikram
> --
> Vikram Vamshi
> Eclipsys Corporation
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:28229D3F-05BB-4354-A333-870335CDD1E4@.microsoft.com...
> applied with SP2 not SP3a.
> cannot be connected.
> listening on Shared Memory and Named Pipes. I have checked the log before
> XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory
> and Named Pipes. How can I make SQL Server listening on TCP? My
> understanding is that it should be based on what has been setup in the
> Server Network Utility. I have tried to disable and then enable TCP/IP but
> SQL Server is still only listening to Shared Memory and Named Pipes.
> 2000. I
> Windows
> I
>
>
|||And you missed my 3rd post
Did you check the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\SuperSocketNet
Lib\Tcp
tcpport should be 1433
vikram
Vikram Vamshi
Eclipsys Corporation
"peter" <peter@.discussions.microsoft.com> wrote in message
news:F3928A71-8F08-4C0A-AD09-D2CB6297BEC6@.microsoft.com...
> Hi Vikram,
> I guess you missed my 2nd post. I repost part of 2nd post here:
> I have checked SQL Server Logs and noticed that SQL Server is only
> listening on Shared Memory and Named Pipes. I have checked the log before
> XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory
> and Named Pipes. How can I make SQL Server listening on TCP? My
> understanding is that it should be based on what has been setup in the
> Server Network Utility. I have tried to disable and then enable TCP/IP
but
> SQL Server is still only listening to Shared Memory and Named Pipes.
> It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433).
But I think it cannot be true for MS to make such mistake.[vbcol=seagreen]
> "Vikram Vamshi" wrote:
1433.[vbcol=seagreen]
Memory,[vbcol=seagreen]
connections[vbcol=seagreen]
been[vbcol=seagreen]
1433.[vbcol=seagreen]
before[vbcol=seagreen]
Memory[vbcol=seagreen]
but[vbcol=seagreen]
is[vbcol=seagreen]
but[vbcol=seagreen]
|||Hi Vikram,
I did not miss your 3rd post, but I guess I'm posting my reply when you post this one. Anyway, here is the reply:
Hi Vikram,
I checked that registry and it has 1433.
It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433). But I think it cannot be true for MS to make such mistake.
"Vikram Vamshi" wrote:

> And you missed my 3rd post
> Did you check the registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\SuperSocketNet
> Lib\Tcp
> tcpport should be 1433
> vikram
> --
> Vikram Vamshi
> Eclipsys Corporation
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:F3928A71-8F08-4C0A-AD09-D2CB6297BEC6@.microsoft.com...
> but
> But I think it cannot be true for MS to make such mistake.
> 1433.
> Memory,
> connections
> been
> 1433.
> before
> Memory
> but
> is
> but
>
>
|||Hi Vikram,
I will listen to the XP SP2 and SQL Server webcast to see whether there is anything about this.
"peter" wrote:
[vbcol=seagreen]
> Hi Vikram,
> I did not miss your 3rd post, but I guess I'm posting my reply when you post this one. Anyway, here is the reply:
> Hi Vikram,
> I checked that registry and it has 1433.
> It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433). But I think it cannot be true for MS to make such mistake.
>
> "Vikram Vamshi" wrote:

Cannot connect to SQL Server

I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
The two servers are indentical, but if the two clients can connect S1, they
cant' connect to S2 ""Access denied or SQL Server does not exist" (but S2
can connect S1).
- I have checked the Server Network Utility and ClientNetwork Utility : all
is correct
- I have tried with the firewall unactivated : no change...
- The version of SQL 2000 on the two servers are the same.
- The network is a wire LAN.
Can anyone tell me where else to look or what else to try?
Many thanks in advance
Henri (Paris)
So you can connect:
C1 -> S1
C2 -> S1
S2 -> S1
but cannot connect:
C1 -> S2
C2 -> S2
Some things to check:
Can you connect from S2 to S2? If this fails, I suspect the SQL Server is
not started, or you have the name wrong because it's a named instance such
as S2\MSDN, or it is not accepting any connections on the protocol you are
using.
If you can connect from S2 to S2, then I would double-check the firewall. I
see that you said you tried turning off the firewall, but the Windows
firewall that is turned on in SP2 causes most of these problems.
What protocol are you using? If TCP/IP, try connecting using the TCP address
and port number, such as 120.24.118.17,1433. It's possible you have a
problem resolving the computer name. That would cause this error.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Henri" <foucauld@.wanadoo.fr> wrote in message
news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
>S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
> The two servers are indentical, but if the two clients can connect S1,
> they cant' connect to S2 ""Access denied or SQL Server does not exist"
> (but S2 can connect S1).
> - I have checked the Server Network Utility and ClientNetwork Utility :
> all is correct
> - I have tried with the firewall unactivated : no change...
> - The version of SQL 2000 on the two servers are the same.
> - The network is a wire LAN.
> Can anyone tell me where else to look or what else to try?
> Many thanks in advance
> Henri (Paris)
>
|||Is the Browser service running on S2?
Did you see the whitepaper on my blog?
http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Henri" <foucauld@.wanadoo.fr> wrote in message
news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
>S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
> The two servers are indentical, but if the two clients can connect S1,
> they cant' connect to S2 ""Access denied or SQL Server does not exist"
> (but S2 can connect S1).
> - I have checked the Server Network Utility and ClientNetwork Utility :
> all is correct
> - I have tried with the firewall unactivated : no change...
> - The version of SQL 2000 on the two servers are the same.
> - The network is a wire LAN.
> Can anyone tell me where else to look or what else to try?
> Many thanks in advance
> Henri (Paris)
>
|||Is the SQL Browser service running on S2?
Did you read
http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html ?
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:7F6297AB-2D3D-41FF-932D-A0971C0188F4@.microsoft.com...
> So you can connect:
> C1 -> S1
> C2 -> S1
> S2 -> S1
> but cannot connect:
> C1 -> S2
> C2 -> S2
> Some things to check:
> Can you connect from S2 to S2? If this fails, I suspect the SQL Server is
> not started, or you have the name wrong because it's a named instance such
> as S2\MSDN, or it is not accepting any connections on the protocol you are
> using.
> If you can connect from S2 to S2, then I would double-check the firewall.
> I see that you said you tried turning off the firewall, but the Windows
> firewall that is turned on in SP2 causes most of these problems.
> What protocol are you using? If TCP/IP, try connecting using the TCP
> address and port number, such as 120.24.118.17,1433. It's possible you
> have a problem resolving the computer name. That would cause this error.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Henri" <foucauld@.wanadoo.fr> wrote in message
> news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>

Cannot connect to SQL Server

I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
The two servers are indentical, but if the two clients can connect S1, they
cant' connect to S2 ""Access denied or SQL Server does not exist" (but S2
can connect S1).
- I have checked the Server Network Utility and ClientNetwork Utility : all
is correct
- I have tried with the firewall unactivated : no change...
- The version of SQL 2000 on the two servers are the same.
- The network is a wire LAN.
Can anyone tell me where else to look or what else to try?
Many thanks in advance
Henri (Paris)So you can connect:
C1 -> S1
C2 -> S1
S2 -> S1
but cannot connect:
C1 -> S2
C2 -> S2
Some things to check:
Can you connect from S2 to S2? If this fails, I suspect the SQL Server is
not started, or you have the name wrong because it's a named instance such
as S2\MSDN, or it is not accepting any connections on the protocol you are
using.
If you can connect from S2 to S2, then I would double-check the firewall. I
see that you said you tried turning off the firewall, but the Windows
firewall that is turned on in SP2 causes most of these problems.
What protocol are you using? If TCP/IP, try connecting using the TCP address
and port number, such as 120.24.118.17,1433. It's possible you have a
problem resolving the computer name. That would cause this error.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Henri" <foucauld@.wanadoo.fr> wrote in message
news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
>S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
> The two servers are indentical, but if the two clients can connect S1,
> they cant' connect to S2 ""Access denied or SQL Server does not exist"
> (but S2 can connect S1).
> - I have checked the Server Network Utility and ClientNetwork Utility :
> all is correct
> - I have tried with the firewall unactivated : no change...
> - The version of SQL 2000 on the two servers are the same.
> - The network is a wire LAN.
> Can anyone tell me where else to look or what else to try?
> Many thanks in advance
> Henri (Paris)
>|||Is the Browser service running on S2?
Did you see the whitepaper on my blog?
http://betav.com/blog/billva/2006/0..._connected.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Henri" <foucauld@.wanadoo.fr> wrote in message
news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
>S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
> The two servers are indentical, but if the two clients can connect S1,
> they cant' connect to S2 ""Access denied or SQL Server does not exist"
> (but S2 can connect S1).
> - I have checked the Server Network Utility and ClientNetwork Utility :
> all is correct
> - I have tried with the firewall unactivated : no change...
> - The version of SQL 2000 on the two servers are the same.
> - The network is a wire LAN.
> Can anyone tell me where else to look or what else to try?
> Many thanks in advance
> Henri (Paris)
>|||Is the SQL Browser service running on S2?
Did you read
http://betav.com/blog/billva/2006/0..._connected.html ?
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:7F6297AB-2D3D-41FF-932D-A0971C0188F4@.microsoft.com...
> So you can connect:
> C1 -> S1
> C2 -> S1
> S2 -> S1
> but cannot connect:
> C1 -> S2
> C2 -> S2
> Some things to check:
> Can you connect from S2 to S2? If this fails, I suspect the SQL Server is
> not started, or you have the name wrong because it's a named instance such
> as S2\MSDN, or it is not accepting any connections on the protocol you are
> using.
> If you can connect from S2 to S2, then I would double-check the firewall.
> I see that you said you tried turning off the firewall, but the Windows
> firewall that is turned on in SP2 causes most of these problems.
> What protocol are you using? If TCP/IP, try connecting using the TCP
> address and port number, such as 120.24.118.17,1433. It's possible you
> have a problem resolving the computer name. That would cause this error.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Henri" <foucauld@.wanadoo.fr> wrote in message
> news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>