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 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 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 using IP to Clustered Named Instance

I am having trouble connecting when using the IP address to a named
instanced using dynamic port assignments and hosted on a 2K3 cluster (even
when at the console on the node hosting the SQL instance). I receive "SQL
Server does not exist or access denied". There are no entries created in
the event log. I am able to connect with no problems using the instance
name. I'm attempting to connect usingQuery Analyzer. Any ideas?
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
Hi Michael,
In order to connect to a Named Instance you need to either:
a. Supply the Servername\InstanceName
b. Supply the Servername, port
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||It seems that you have trouble connecting through TCP/IP. Verify in event log that SQL is listening on TCPIP and not only on Shared Memory / Named Pipes.
To verify that this is a problem from QueryAnalyzer try to connect with tcp:ServerName\InstanceName. If it isn't work then server is not listening on TCP at all...
post back after this and we will see what then...
Rgds
Sinisa Perovic
|||Thanks for the help.
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:51hmVwbIEHA.3636@.cpmsftngxa06.phx.gbl...
> Hi Michael,
> In order to connect to a Named Instance you need to either:
> a. Supply the Servername\InstanceName
> b. Supply the Servername, port
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

Cannot connect to second cluster node w/instance name

I have an active/active SQL2005 cluster. Node1 has a default instance of
SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
without problem. When I attempt to connect to node2 remotely I get an error
basically stating "An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused
by the fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)".
When I connect I am using node2\sqlb as the connection name--this should
give me access to the named instance. I can however access node2\sqlb from
node2 directly (locally on the server). Yes, I have made sure named pipes
and tcp/ip are enabled. Made sure no firewalls, etc. The weird thing is
that I was able to make a remote connection for a short time (like two
hours) and then I couldn't anymore.
I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
console installed locally. Any information would be greatly appreciated.
Is the SQL Server Browser Service running to provide the tcp port number for
the named instance?
If not, what port is the named instance listening on? Can you connect to
node2,<port number> ?
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"JPerkins" <joshp@.CUIAB.LOCAL> wrote in message
news:DBDEDBC3-AEF7-48E0-91D7-25977A8AEBB9@.microsoft.com...
>I have an active/active SQL2005 cluster. Node1 has a default instance of
>SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
>SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
>without problem. When I attempt to connect to node2 remotely I get an
>error basically stating "An error has occurred while establishing a
>connection to the server. When connecting to SQL Server 2005, this failure
>may be caused by the fact that under the default settings SQL Server does
>not allow remote connections. (provider: SQL Network Interfaces, error:
>26 - Error Locating Server/Instance Specified)".
> When I connect I am using node2\sqlb as the connection name--this should
> give me access to the named instance. I can however access node2\sqlb
> from node2 directly (locally on the server). Yes, I have made sure named
> pipes and tcp/ip are enabled. Made sure no firewalls, etc. The weird
> thing is that I was able to make a remote connection for a short time
> (like two hours) and then I couldn't anymore.
> I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
> console installed locally. Any information would be greatly appreciated.

Cannot connect to second cluster node w/instance name

I have an active/active SQL2005 cluster. Node1 has a default instance of
SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
without problem. When I attempt to connect to node2 remotely I get an error
basically stating "An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused
by the fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)".
When I connect I am using node2\sqlb as the connection name--this should
give me access to the named instance. I can however access node2\sqlb from
node2 directly (locally on the server). Yes, I have made sure named pipes
and tcp/ip are enabled. Made sure no firewalls, etc. The weird thing is
that I was able to make a remote connection for a short time (like two
hours) and then I couldn't anymore.
I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
console installed locally. Any information would be greatly appreciated.Is the SQL Server Browser Service running to provide the tcp port number for
the named instance?
If not, what port is the named instance listening on? Can you connect to
node2,<port number> ?
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"JPerkins" <joshp@.CUIAB.LOCAL> wrote in message
news:DBDEDBC3-AEF7-48E0-91D7-25977A8AEBB9@.microsoft.com...
>I have an active/active SQL2005 cluster. Node1 has a default instance of
>SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
>SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
>without problem. When I attempt to connect to node2 remotely I get an
>error basically stating "An error has occurred while establishing a
>connection to the server. When connecting to SQL Server 2005, this failure
>may be caused by the fact that under the default settings SQL Server does
>not allow remote connections. (provider: SQL Network Interfaces, error:
>26 - Error Locating Server/Instance Specified)".
> When I connect I am using node2\sqlb as the connection name--this should
> give me access to the named instance. I can however access node2\sqlb
> from node2 directly (locally on the server). Yes, I have made sure named
> pipes and tcp/ip are enabled. Made sure no firewalls, etc. The weird
> thing is that I was able to make a remote connection for a short time
> (like two hours) and then I couldn't anymore.
> I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
> console installed locally. Any information would be greatly appreciated.

Cannot connect to Named Instance

I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
(Windows 2003). I have no problems connecting to the first virtual server by
name or IP address, but I can only connect to the named instance by using
the IP address and specifying a port (192.168.0.1, 1434).
I can connect to the named instance by IP or name from both cluster nodes,
the problem only arises with remote clients. The client machine I am testing
from is running Windows XP SP2, MDAC 2.8
Thanks in advance,
Curtis
Curtis O. Bouknight wrote:
> I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
> (Windows 2003). I have no problems connecting to the first virtual server by
> name or IP address, but I can only connect to the named instance by using
> the IP address and specifying a port (192.168.0.1, 1434).

> I can connect to the named instance by IP or name from both cluster nodes,

> the problem only arises with remote clients. The client machine I am testing
> from is running Windows XP SP2, MDAC 2.8
>
1433 is the default sql port. The problem could be with the udp listener
which tells the client where the instance is running.
when you installed the named instance you created an alias on both nodes.
Did you remove these, and if so does the sql agent connect with lpc or is it
still using named pipes? If so clean the registry
HKLM\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSo cketNetLib\LastConnect
and restart sql agent and see it fail?
Are both sqlservices running as local admin?
Hans
|||Welcome to my world.
This issue has been ongoing for me with Microsoft for almost a year now.
They have bounced around from it being a SQL Problem, to a network problem,
back to a SQL Problem, now they are looking at an OS problem. If you call
support, be ready to take system dumps, netstats, captures, etc...
One thing you can do to "verify" that you have the problem is to take a
tasklist and a netstat -aon on each node, then match the PID's up. One will
not have a listener on UDP 1434, and the other will. We had the same
scenario for quite some time, then suddenly the other node started exhibiting
the same behavior. We now tell customers to just go directly to the TCP/IP
port for both nodes to solve any confusion down the way.
js
"Curtis O. Bouknight" wrote:

> I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
> (Windows 2003). I have no problems connecting to the first virtual server by
> name or IP address, but I can only connect to the named instance by using
> the IP address and specifying a port (192.168.0.1, 1434).
> I can connect to the named instance by IP or name from both cluster nodes,
> the problem only arises with remote clients. The client machine I am testing
> from is running Windows XP SP2, MDAC 2.8
> Thanks in advance,
> Curtis
>
>
>