|
Home > Archive > MS SQL Server > December 2006 > Incorrect LicenseType & NumLicenses returned by SERVERPROPERTY fnc
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Incorrect LicenseType & NumLicenses returned by SERVERPROPERTY fnc
|
|
| DBADave 2006-12-07, 12:12 am |
| I am attempting to poll my inventory of multiple SQL 2000 Servers to
detemrine their license model and # of licenses. Each of these SQL 2000
Servers are running either SQL 2k SP3a or SQL 2k SP4 and they are all either
running the Standard or Enterprise edition of SQL. On a handful of servers
however, if I run a SELECT
SERVERPROPERTY('Lice
nseType'),SERVERPROP
ERTY('NumLicenses') I get 'DISABLED'
and NULL values returned. If I look in Control Panel, I do see that these
servers are running PER_SEAT.
Any idea why the incorrect values are reported across multiple servers (that
are running the standard or enterprise edtion with an SP level above SP2)?
As a work-around, are there registry values that can be extracted to
retrieve this info instead?
Thanks!
| |
| DBADave 2006-12-13, 7:12 pm |
| I haven't received a response on this issue. Have I left everyone speechless?
"DBADave" wrote:
> I am attempting to poll my inventory of multiple SQL 2000 Servers to
> detemrine their license model and # of licenses. Each of these SQL 2000
> Servers are running either SQL 2k SP3a or SQL 2k SP4 and they are all either
> running the Standard or Enterprise edition of SQL. On a handful of servers
> however, if I run a SELECT
> SERVERPROPERTY('Lice
nseType'),SERVERPROP
ERTY('NumLicenses') I get 'DISABLED'
> and NULL values returned. If I look in Control Panel, I do see that these
> servers are running PER_SEAT.
>
> Any idea why the incorrect values are reported across multiple servers (that
> are running the standard or enterprise edtion with an SP level above SP2)?
>
> As a work-around, are there registry values that can be extracted to
> retrieve this info instead?
>
> Thanks!
| |
| Aaron Bertrand [SQL Server MVP] 2006-12-13, 7:12 pm |
| My guess is that these "servers" where you get DISABLED are not running
server operating systems (XP, 2000 Pro), or are running Developer edition,
or are using an unlicensed edition (e.g. from MSDN), or someone tried to
muck with the licensing mode in the registry or elsewhere (changing license
modes after SQL Server 2000 installed is not supported).
There is an obscure chance these servers are running a very ancient build of
SQL Server 2000, and in addition are coincidentally in the same scenario as
described in this fix (which was included in Service Pack 2):
http://support.microsoft.com/kb/291332
If that it the case, then obviously, you should update those servers to SP4.
But my money is on at least one item from the first list.
A
"DBADave" <DBADave@discussions.microsoft.com> wrote in message
news:FFF86264-3510-4D7D-BBD8- 672C9F2D799B@microso
ft.com...[color=darkred]
>I haven't received a response on this issue. Have I left everyone
>speechless?
>
>
> "DBADave" wrote:
>
|
|
|
|
|