Another example of MS making it hard to quickly check what version of a software you are running.

Use the SQL script below to find your SMS sites service pack version level for SMS 2.0 or SMS 2003 sites.

SQL Query:

Select
SiteCode,
SiteServer,
SiteName,

'Version' = Case
When Version between '2.00.1239.0000' And '2.00.1239.0999'
Then 'SMS Version 2.0 RTM'
When Version between '2.00.1380.1000' And '2.00.1380.1999'
Then 'SMS Version 2.0 Service Pack 1'
When Version between '2.00.1493.2000' And '2.00.1493.2999'
Then 'SMS Version 2.0 Service Pack 2'
When Version between '2.00.1493.3000' And '2.00.1493.3999'
Then 'SMS Version 2.0 Service Pack 3'
When Version between '2.00.1493.4000' And '2.00.1493.4999'
Then 'SMS Version 2.0 Service Pack 4'
When Version between '2.00.1493.5000' And '2.00.1493.5999'
Then 'SMS Version 2.0 Service Pack 5'
When Version = '2.50.2726.0018'
Then 'SMS 2003 RTM'
When Version = '2.50.3174.1018'
Then 'SMS 2003 SP 1'
When Version = '2.50.4160.2000'
Then 'SMS 2003 SP 2'
Else 'Unable To Determine Service Pack!'
End

From Sites

After a power outage this morning we had some issues with our local primary SMS site server. Who knows if the issues were directly related to the power outage or if they would have occurred at the next reboot, but the server would not boot - it would stall at the Windows 2003 splash screen. I got it to boot by running a repair of the OS from the CD. Everything looked to be online at that point but I got the below error when testing the SMS Admin Console mmc:

MMC cannot open the file [drive]:\SMS\bin\i386\sms.msc
This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient rights to the file.

Since I had run a repair of the OS, my worst case was this somehow messed up my SMS install which would not have been pleasant. But I was able to open the admin console on other PCs so I did some research and found that the error is profile related. I read that is usually caused when you have a terminal session open with the SMS Admin console open and the session is killed.

The resolution is to rename the "sms" file in C:\Documents and Settings\[username]\Application Data\Microsoft\MMC\SMS to something else and then start up the SMS Admin console again for it to be recreated.

This fixed it for me and worth noting because the error message does not even hint at the actual problem.