When I try to connect to sql server instance I received this error:
TITLE: Microsoft SQL Server Management Studio
--
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
ADDITIONAL INFORMATION:
Error executing extended stored procedure: Invalid Parameter
Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
Server, Error: 22001)
when i click refresh button i am able to see my schema, but i can't see the
properties of my base and any table properties. I receive error:
TITLE: Microsoft SQL Server Management Studio
--
Cannot show requested dialog.
--
ADDITIONAL INFORMATION:
Cannot show requested dialog. (SqlMgmt)
--
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
Error executing extended stored procedure: Invalid Parameter
Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
Server, Error: 22001)
--
BUTTONS:
OK
--
also the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names is
locked and can not be opened.
After a reboot the key is now readable and the 2005 instance can be
connected to without these messages.
But after a while it does it again.
does anyone have any idea what is going wrong?Hi
My guess is that you have some group policy or Anti-virus/ISD system that is
locking down this registry key.
John
"nikolakg" wrote:
> When I try to connect to sql server instance I received this error:
> TITLE: Microsoft SQL Server Management Studio
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> ADDITIONAL INFORMATION:
> Error executing extended stored procedure: Invalid Parameter
> Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
> Server, Error: 22001)
>
> when i click refresh button i am able to see my schema, but i can't see the
> properties of my base and any table properties. I receive error:
> TITLE: Microsoft SQL Server Management Studio
> --
> Cannot show requested dialog.
> --
> ADDITIONAL INFORMATION:
> Cannot show requested dialog. (SqlMgmt)
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> Error executing extended stored procedure: Invalid Parameter
> Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
> Server, Error: 22001)
>
> --
> BUTTONS:
> OK
> --
>
> also the registry key
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names is
> locked and can not be opened.
> After a reboot the key is now readable and the 2005 instance can be
> connected to without these messages.
> But after a while it does it again.
> does anyone have any idea what is going wrong?
Showing posts with label invalid. Show all posts
Showing posts with label invalid. Show all posts
Tuesday, March 27, 2012
Friday, March 9, 2012
Error converting a text field to a datetime datatype, who can figure this anyone??
Hello,
I'm trying to convert data on a text field to datetime datatype. This data
has invalid dates such as 10/30, 2/31235, 32/1/2004, 345/2345 etc.
I have been trying to convert whatever I can but I keep getting errors when
I perform a
SELECT CONVERT(datetime, text_field) FROM Old_data
Obviously my select statemt is abruptly terminated when I hit one of these
records with a invalid date.
I tried looping throught the records using a curson and try to capture and
check for errors:
SET @.user_1_date = convert(datetime, @.USER_1)
IF @.@.ERROR <> 0
BEGIN
PRINT 'ERROR FOUND'
END
ELSE
BEGIN
print 'NO ERROR FOUND'
END
I'm using PRINT for simplicity but the conversion error can not be
controlled through this method. SQL halts when it tries to convert the date.
I would love to be able to trap the error and skip the record and move on to
the new one. The bulk of the data is good, but there are over 175,000
records and I can not do this manually.
Any thoughts or suggestions?
ThanksAsked and answered by lw in the .programming group. Please don't
multi-post.
"Sd" <nowhere@.sadfs.com> wrote in message
news:3ac3890e730ead0e80076b10ff132aaa@.ne
ws.teranews.com...
> Hello,
> I'm trying to convert data on a text field to datetime datatype. This data
> has invalid dates such as 10/30, 2/31235, 32/1/2004, 345/2345 etc.
> I have been trying to convert whatever I can but I keep getting errors
when
> I perform a
> SELECT CONVERT(datetime, text_field) FROM Old_data
> Obviously my select statemt is abruptly terminated when I hit one of these
> records with a invalid date.
> I tried looping throught the records using a curson and try to capture and
> check for errors:
> SET @.user_1_date = convert(datetime, @.USER_1)
> IF @.@.ERROR <> 0
> BEGIN
> PRINT 'ERROR FOUND'
> END
> ELSE
> BEGIN
> print 'NO ERROR FOUND'
> END
> I'm using PRINT for simplicity but the conversion error can not be
> controlled through this method. SQL halts when it tries to convert the
date.
> I would love to be able to trap the error and skip the record and move on
to
> the new one. The bulk of the data is good, but there are over 175,000
> records and I can not do this manually.
> Any thoughts or suggestions?
> Thanks
>
>|||Sd (nowhere@.sadfs.com) writes:
> I have been trying to convert whatever I can but I keep getting errors
> when I perform a
> SELECT CONVERT(datetime, text_field) FROM Old_data
> Obviously my select statemt is abruptly terminated when I hit one of these
> records with a invalid date.
> I tried looping throught the records using a curson and try to capture and
> check for errors:
But since SQL Server thinks conversion error is reason enough for aborting
the batch, that does not fly.
But this should do:
SELECT CASE WHEN is_date(text_field) = 1
THEN convert(datetime, text_field)
END
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
I'm trying to convert data on a text field to datetime datatype. This data
has invalid dates such as 10/30, 2/31235, 32/1/2004, 345/2345 etc.
I have been trying to convert whatever I can but I keep getting errors when
I perform a
SELECT CONVERT(datetime, text_field) FROM Old_data
Obviously my select statemt is abruptly terminated when I hit one of these
records with a invalid date.
I tried looping throught the records using a curson and try to capture and
check for errors:
SET @.user_1_date = convert(datetime, @.USER_1)
IF @.@.ERROR <> 0
BEGIN
PRINT 'ERROR FOUND'
END
ELSE
BEGIN
print 'NO ERROR FOUND'
END
I'm using PRINT for simplicity but the conversion error can not be
controlled through this method. SQL halts when it tries to convert the date.
I would love to be able to trap the error and skip the record and move on to
the new one. The bulk of the data is good, but there are over 175,000
records and I can not do this manually.
Any thoughts or suggestions?
ThanksAsked and answered by lw in the .programming group. Please don't
multi-post.
"Sd" <nowhere@.sadfs.com> wrote in message
news:3ac3890e730ead0e80076b10ff132aaa@.ne
ws.teranews.com...
> Hello,
> I'm trying to convert data on a text field to datetime datatype. This data
> has invalid dates such as 10/30, 2/31235, 32/1/2004, 345/2345 etc.
> I have been trying to convert whatever I can but I keep getting errors
when
> I perform a
> SELECT CONVERT(datetime, text_field) FROM Old_data
> Obviously my select statemt is abruptly terminated when I hit one of these
> records with a invalid date.
> I tried looping throught the records using a curson and try to capture and
> check for errors:
> SET @.user_1_date = convert(datetime, @.USER_1)
> IF @.@.ERROR <> 0
> BEGIN
> PRINT 'ERROR FOUND'
> END
> ELSE
> BEGIN
> print 'NO ERROR FOUND'
> END
> I'm using PRINT for simplicity but the conversion error can not be
> controlled through this method. SQL halts when it tries to convert the
date.
> I would love to be able to trap the error and skip the record and move on
to
> the new one. The bulk of the data is good, but there are over 175,000
> records and I can not do this manually.
> Any thoughts or suggestions?
> Thanks
>
>|||Sd (nowhere@.sadfs.com) writes:
> I have been trying to convert whatever I can but I keep getting errors
> when I perform a
> SELECT CONVERT(datetime, text_field) FROM Old_data
> Obviously my select statemt is abruptly terminated when I hit one of these
> records with a invalid date.
> I tried looping throught the records using a curson and try to capture and
> check for errors:
But since SQL Server thinks conversion error is reason enough for aborting
the batch, that does not fly.
But this should do:
SELECT CASE WHEN is_date(text_field) = 1
THEN convert(datetime, text_field)
END
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
Error converting a text field to a datetime datatype, who can figure this anyone??
Hello,
I'm trying to convert data on a text field to datetime datatype. This data
has invalid dates such as 10/30, 2/31235, 32/1/2004, 345/2345 etc.
I have been trying to convert whatever I can but I keep getting errors when
I perform a
SELECT CONVERT(datetime, text_field) FROM Old_data
Obviously my select statemt is abruptly terminated when I hit one of these
records with a invalid date.
I tried looping throught the records using a curson and try to capture and
check for errors:
SET @.user_1_date = convert(datetime, @.USER_1)
IF @.@.ERROR <> 0
BEGIN
PRINT 'ERROR FOUND'
END
ELSE
BEGIN
print 'NO ERROR FOUND'
END
I'm using PRINT for simplicity but the conversion error can not be
controlled through this method. SQL halts when it tries to convert the date.
I would love to be able to trap the error and skip the record and move on to
the new one. The bulk of the data is good, but there are over 175,000
records and I can not do this manually.
Any thoughts or suggestions?
ThanksAsked and answered by lw in the .programming group. Please don't
multi-post.
"Sd" <nowhere@.sadfs.com> wrote in message
news:3ac3890e730ead0e80076b10ff132aaa@.news.teranews.com...
> Hello,
> I'm trying to convert data on a text field to datetime datatype. This data
> has invalid dates such as 10/30, 2/31235, 32/1/2004, 345/2345 etc.
> I have been trying to convert whatever I can but I keep getting errors
when
> I perform a
> SELECT CONVERT(datetime, text_field) FROM Old_data
> Obviously my select statemt is abruptly terminated when I hit one of these
> records with a invalid date.
> I tried looping throught the records using a curson and try to capture and
> check for errors:
> SET @.user_1_date = convert(datetime, @.USER_1)
> IF @.@.ERROR <> 0
> BEGIN
> PRINT 'ERROR FOUND'
> END
> ELSE
> BEGIN
> print 'NO ERROR FOUND'
> END
> I'm using PRINT for simplicity but the conversion error can not be
> controlled through this method. SQL halts when it tries to convert the
date.
> I would love to be able to trap the error and skip the record and move on
to
> the new one. The bulk of the data is good, but there are over 175,000
> records and I can not do this manually.
> Any thoughts or suggestions?
> Thanks
>
>|||Sd (nowhere@.sadfs.com) writes:
> I have been trying to convert whatever I can but I keep getting errors
> when I perform a
> SELECT CONVERT(datetime, text_field) FROM Old_data
> Obviously my select statemt is abruptly terminated when I hit one of these
> records with a invalid date.
> I tried looping throught the records using a curson and try to capture and
> check for errors:
But since SQL Server thinks conversion error is reason enough for aborting
the batch, that does not fly.
But this should do:
SELECT CASE WHEN is_date(text_field) = 1
THEN convert(datetime, text_field)
END
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
I'm trying to convert data on a text field to datetime datatype. This data
has invalid dates such as 10/30, 2/31235, 32/1/2004, 345/2345 etc.
I have been trying to convert whatever I can but I keep getting errors when
I perform a
SELECT CONVERT(datetime, text_field) FROM Old_data
Obviously my select statemt is abruptly terminated when I hit one of these
records with a invalid date.
I tried looping throught the records using a curson and try to capture and
check for errors:
SET @.user_1_date = convert(datetime, @.USER_1)
IF @.@.ERROR <> 0
BEGIN
PRINT 'ERROR FOUND'
END
ELSE
BEGIN
print 'NO ERROR FOUND'
END
I'm using PRINT for simplicity but the conversion error can not be
controlled through this method. SQL halts when it tries to convert the date.
I would love to be able to trap the error and skip the record and move on to
the new one. The bulk of the data is good, but there are over 175,000
records and I can not do this manually.
Any thoughts or suggestions?
ThanksAsked and answered by lw in the .programming group. Please don't
multi-post.
"Sd" <nowhere@.sadfs.com> wrote in message
news:3ac3890e730ead0e80076b10ff132aaa@.news.teranews.com...
> Hello,
> I'm trying to convert data on a text field to datetime datatype. This data
> has invalid dates such as 10/30, 2/31235, 32/1/2004, 345/2345 etc.
> I have been trying to convert whatever I can but I keep getting errors
when
> I perform a
> SELECT CONVERT(datetime, text_field) FROM Old_data
> Obviously my select statemt is abruptly terminated when I hit one of these
> records with a invalid date.
> I tried looping throught the records using a curson and try to capture and
> check for errors:
> SET @.user_1_date = convert(datetime, @.USER_1)
> IF @.@.ERROR <> 0
> BEGIN
> PRINT 'ERROR FOUND'
> END
> ELSE
> BEGIN
> print 'NO ERROR FOUND'
> END
> I'm using PRINT for simplicity but the conversion error can not be
> controlled through this method. SQL halts when it tries to convert the
date.
> I would love to be able to trap the error and skip the record and move on
to
> the new one. The bulk of the data is good, but there are over 175,000
> records and I can not do this manually.
> Any thoughts or suggestions?
> Thanks
>
>|||Sd (nowhere@.sadfs.com) writes:
> I have been trying to convert whatever I can but I keep getting errors
> when I perform a
> SELECT CONVERT(datetime, text_field) FROM Old_data
> Obviously my select statemt is abruptly terminated when I hit one of these
> records with a invalid date.
> I tried looping throught the records using a curson and try to capture and
> check for errors:
But since SQL Server thinks conversion error is reason enough for aborting
the batch, that does not fly.
But this should do:
SELECT CASE WHEN is_date(text_field) = 1
THEN convert(datetime, text_field)
END
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Wednesday, February 15, 2012
Error Accessing SSRS Web Applications - Service Unavailable/Invalid Version
We have an instance of SQL Server 2005 on a server that also has a SQL
Server 2000 instance. Neither was installed with Reporting Services. We went
back and installed Reporting Services on the 2005 instance only. Went
through the config tool with no problems and the virtual directories look
fine in IIS.
When we try to hit the Reports web page using IE, we get "Service
Unavailable." The service shows as "Started."
Event viewer shows two errors, which occur every 12 hours. The first says
"The report server database is an invalid version" (Event ID 117) and the
second says "Report Server Windows Service (MSSQLSERVER) cannot connect to
the report server dartabase" (Event ID 107).
The server has 2.0 of the framework intalled and the SSRS web applications
are pointing to ASP 2.0.
I googled around on these messages and the only resolutions I found
suggested that the Reporting Services config tool had not been run. It had
been run, and to play it safe I ran it again. But no luck.
Any suggestions? The server is running Windows Server 2003 SP1 and SQL
Server is version 9.0.3054.
Thanks in advance for any help.On Dec 6, 11:20 am, "CapCity" <sgomori at yahoo dot com> wrote:
> We have an instance of SQLServer2005 on aserverthat also has a SQLServer2000 instance. Neither was installed with Reporting Services. We went
> back and installed Reporting Services on the 2005 instance only. Went
> through the config tool with no problems and the virtual directories look
> fine in IIS.
> When we try to hit the Reports web page using IE, we get "Service
> Unavailable." Theserviceshows as "Started."
> Event viewer shows two errors, which occur every 12 hours. The first says
> "Thereportserverdatabase is an invalid version" (Event ID 117) and the
> second says "ReportServerWindowsService(MSSQLSERVER) cannot connect to
> thereportserverdartabase" (Event ID 107).
> Theserverhas 2.0 of the framework intalled and the SSRS web applications
> are pointing to ASP 2.0.
> I googled around on these messages and the only resolutions I found
> suggested that the Reporting Services config tool hadnotbeen run. It had
> been run, and to play it safe I ran it again. But no luck.
> Any suggestions? TheserverisrunningWindowsServer2003 SP1 and SQLServeris version 9.0.3054.
> Thanks in advance for any help.
The *WINDOWS* Service may not be running.
Start >> Administrative Tools >> Services >> SQL Server Reporting
Services (MSSQLSERVER)
Make sure that is started and working properly.|||"BM" <moore.brent@.gmail.com> wrote in message
news:c25281d0-9f47-41ff-844f-e6317ec42e09@.w40g2000hsb.googlegroups.com...
> On Dec 6, 11:20 am, "CapCity" <sgomori at yahoo dot com> wrote:
>> We have an instance of SQLServer2005 on aserverthat also has a
>> SQLServer2000 instance. Neither was installed with Reporting Services. We
>> went
>> back and installed Reporting Services on the 2005 instance only. Went
>> through the config tool with no problems and the virtual directories look
>> fine in IIS.
>> When we try to hit the Reports web page using IE, we get "Service
>> Unavailable." Theserviceshows as "Started."
>> Event viewer shows two errors, which occur every 12 hours. The first says
>> "Thereportserverdatabase is an invalid version" (Event ID 117) and the
>> second says "ReportServerWindowsService(MSSQLSERVER) cannot connect to
>> thereportserverdartabase" (Event ID 107).
>> Theserverhas 2.0 of the framework intalled and the SSRS web applications
>> are pointing to ASP 2.0.
>> I googled around on these messages and the only resolutions I found
>> suggested that the Reporting Services config tool hadnotbeen run. It had
>> been run, and to play it safe I ran it again. But no luck.
>> Any suggestions? TheserverisrunningWindowsServer2003 SP1 and SQLServeris
>> version 9.0.3054.
>> Thanks in advance for any help.
> The *WINDOWS* Service may not be running.
> Start >> Administrative Tools >> Services >> SQL Server Reporting
> Services (MSSQLSERVER)
> Make sure that is started and working properly.
The service is running. I even stopped it and restarted it, but still get
the same error.
Server 2000 instance. Neither was installed with Reporting Services. We went
back and installed Reporting Services on the 2005 instance only. Went
through the config tool with no problems and the virtual directories look
fine in IIS.
When we try to hit the Reports web page using IE, we get "Service
Unavailable." The service shows as "Started."
Event viewer shows two errors, which occur every 12 hours. The first says
"The report server database is an invalid version" (Event ID 117) and the
second says "Report Server Windows Service (MSSQLSERVER) cannot connect to
the report server dartabase" (Event ID 107).
The server has 2.0 of the framework intalled and the SSRS web applications
are pointing to ASP 2.0.
I googled around on these messages and the only resolutions I found
suggested that the Reporting Services config tool had not been run. It had
been run, and to play it safe I ran it again. But no luck.
Any suggestions? The server is running Windows Server 2003 SP1 and SQL
Server is version 9.0.3054.
Thanks in advance for any help.On Dec 6, 11:20 am, "CapCity" <sgomori at yahoo dot com> wrote:
> We have an instance of SQLServer2005 on aserverthat also has a SQLServer2000 instance. Neither was installed with Reporting Services. We went
> back and installed Reporting Services on the 2005 instance only. Went
> through the config tool with no problems and the virtual directories look
> fine in IIS.
> When we try to hit the Reports web page using IE, we get "Service
> Unavailable." Theserviceshows as "Started."
> Event viewer shows two errors, which occur every 12 hours. The first says
> "Thereportserverdatabase is an invalid version" (Event ID 117) and the
> second says "ReportServerWindowsService(MSSQLSERVER) cannot connect to
> thereportserverdartabase" (Event ID 107).
> Theserverhas 2.0 of the framework intalled and the SSRS web applications
> are pointing to ASP 2.0.
> I googled around on these messages and the only resolutions I found
> suggested that the Reporting Services config tool hadnotbeen run. It had
> been run, and to play it safe I ran it again. But no luck.
> Any suggestions? TheserverisrunningWindowsServer2003 SP1 and SQLServeris version 9.0.3054.
> Thanks in advance for any help.
The *WINDOWS* Service may not be running.
Start >> Administrative Tools >> Services >> SQL Server Reporting
Services (MSSQLSERVER)
Make sure that is started and working properly.|||"BM" <moore.brent@.gmail.com> wrote in message
news:c25281d0-9f47-41ff-844f-e6317ec42e09@.w40g2000hsb.googlegroups.com...
> On Dec 6, 11:20 am, "CapCity" <sgomori at yahoo dot com> wrote:
>> We have an instance of SQLServer2005 on aserverthat also has a
>> SQLServer2000 instance. Neither was installed with Reporting Services. We
>> went
>> back and installed Reporting Services on the 2005 instance only. Went
>> through the config tool with no problems and the virtual directories look
>> fine in IIS.
>> When we try to hit the Reports web page using IE, we get "Service
>> Unavailable." Theserviceshows as "Started."
>> Event viewer shows two errors, which occur every 12 hours. The first says
>> "Thereportserverdatabase is an invalid version" (Event ID 117) and the
>> second says "ReportServerWindowsService(MSSQLSERVER) cannot connect to
>> thereportserverdartabase" (Event ID 107).
>> Theserverhas 2.0 of the framework intalled and the SSRS web applications
>> are pointing to ASP 2.0.
>> I googled around on these messages and the only resolutions I found
>> suggested that the Reporting Services config tool hadnotbeen run. It had
>> been run, and to play it safe I ran it again. But no luck.
>> Any suggestions? TheserverisrunningWindowsServer2003 SP1 and SQLServeris
>> version 9.0.3054.
>> Thanks in advance for any help.
> The *WINDOWS* Service may not be running.
> Start >> Administrative Tools >> Services >> SQL Server Reporting
> Services (MSSQLSERVER)
> Make sure that is started and working properly.
The service is running. I even stopped it and restarted it, but still get
the same error.
Subscribe to:
Posts (Atom)