Error Converting Date

Good Morning Forum

First time poster here, but I have gleaned much needed support using the forum in the past, so
many thanks to all.

Well, on to business.

I have a strange problem with a T-SQL stored procedure my company uses for reporting.

Around the Christmas holiday period, it just stopped working.

I managed to track the error down to the code below:

(Just the code to recreate the error.)

declare

@g datetime,

@g2 datetime

select @g2=getdate()

select @g=convert(datetime,convert(varchar(10),@g2,101))

select @g,@g2 , SERVERPROPERTY('PRODUCTVERSION'), SERVERPROPERTY ('PRODUCTLEVEL'), SERVERPROPERTY ('EDITION')

When this is run, I get this error message:

Msg 242, Level 16, State 3, Line 6

The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.

Here is the About information from .
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.13
Microsoft .NET Framework 2.0.50727.1433
Operating System 5.1.2600


I know this is not the best way to use datetime or conversions, but I did not write it, I am just supporting it.

The strange thing is, the above code has worked every week since January 2006?

The even stranger thing is, it runs on perfectly well on Server 2000 and on the version below that has not had
any recent service packs installed.

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.3790.1830
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790


Is this a bug, or have I lost the plot?

Thanks in advance for any feedback.

P.S: The style code 101, if changed to 103 allows the code to work. But, when apllied to the pre-RTM server, is
returns the same error message.