SQL Server Q&A

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘microsoft web site’

The Setup.exe program is unable to remove security code groups that were created during the installation of SQL Server 2008

Symptoms
Consider the following scenario. You run the Setup.exe program to install Microsoft SQL Server 2008. The Setup.exe program is stopped suddenly before it is completed, either intentionally or because of a power failure. In this scenario, the Setup.exe program is unable to remove security code groups that were created during the installation. Therefore, the computer may be left vulnerable to attack.
Note Code groups are created to allow for users to run the Setup.exe program from a network share.
Resolution
To work around this problem, use the Code Access Security Policy tool to manually remove the security code groups. To do this, follow these steps.
Notes You must have machine-level security policy to use the Code Access Security Policy tool.For more information, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/cb6t8dtz(VS.80).aspx(http://msdn.microsoft.com/en-us/library/cb6t8dtz(VS.80).aspx)If the Code Access Security Policy tool is not located on the computer, reinstallthe Microsoft .NET Framework 3.5. To download the .NET Framework 3.5, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=333325fd-ae52-4e35-b531-508d977d32a6&displaylang=en(http://www.microsoft.com/downloads/details.aspx?familyid=333325fd-ae52-4e35-b531-508d977d32a6&displaylang=en)Click Start, click Run, type cmd, and then click OK.Locate one orboth of the following folders, depending on your operating system:
32-bit editions of Windows
%systemdrive%\Microsoft.NET\Framework\v2.0.50727
64-bit editions of Windows
Note In 64-bit editions of Windows, you must run the CasPol.exe –q –rg code group command in the following folders: %systemdrive%\Microsoft.NET\Framework\v2.0.50727%systemdrive%\Microsoft.NET\Framework64\v2.0.50727For each security code group that is listed in this step, type the following command, and then press ENTER.
Note You do not have to restart the computer after you run the command for each security code group.
Command
CasPol.exe -q -rg code_group_nameNote In this command, the placeholder code_group_name represents the name of the security code group.
Security code groupsMSVCM80MICROSOFT.SQLSERVER.CHAINER.SETUPMICROSOFT.SQL.CHAINER.PACKAGEMICROSOFT.SQLSERVER.CHAINER.INFRASTRUCTUREMICROSOFT.SQLSERVER.CONFIGURATION.BOOTSTRAPEXTENSIONMICROSOFT.SQLSERVER.SETUP.CHAINER.WORKFLOWMICROSOFT.SQLSERVER.CONFIGURATION.SQLCONFIGBASEMICROSOFT.SQLSERVER.CONFIGURATION.SFCMICROSOFT.SQLSERVER.CONFIGURATION.SETUPEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.MSIEXTENSIONMICROSOFT.SQLSERVER.CHAINER.EXTENSIONCOMMONMICROSOFT.SQLSERVER.CONFIGURATION.SCOMICROSOFT.SQLSERVER.CONFIGURATION.CONFIGEXTENSIONMICROSOFT.SQLSERVER.DISCOVERYMICROSOFT.SQLSERVER.CONFIGURATION.UIEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.SSTRINGMICROSOFT.SQLSERVER.CONFIGURATION.WIZARDFRAMEWORKMICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARDFRAMEWORKMICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARDMICROSOFT.SQLSERVER.MANAGEMENT.CONTROLSMICROSOFT.SQLSERVER.CONFIGURATIONMICROSOFT.SQLSERVER.CONFIGURATION.CONNECTIONINFOMICROSOFT.SQLSERVER.CONFIGURATION.RULESENGINEEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.CLUSTERMSCLUSTERLIBMICROSOFT.SQL.CHAINER.PACKAGEDATAMICROSOFT.SQL.CHAINER.PRODUCTMICROSOFT.NETENTERPRISESERVERS.EXCEPTIONMESSAGEBOXLANDINGPAGEMICROSOFT.SQLSERVER.CONFIGURATION.SLPEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.AGENTEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.POWERSHELLEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.SSISEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.ASEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.REPL_CONFIGEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.MANAGEMENTTOOLSEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.SQLSERVER_CONFIGEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.SNISERVERCONFIGEXTMICROSOFT.SQLSERVER.CONFIGURATION.SQLBROWSEREXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.RSEXTENSIONMICROSOFT.SQLSERVER.CONFIGURATION.DMFMICROSOFT.SQLSERVER.CONFIGURATION.SMOMICROSOFT.SQLSERVER.CONFIGURATION.SQLENUMMICROSOFT.SQLSERVER.CONFIGURATION.FULLTEXT_CONFIGEXTENSIONFIXSQLREGISTRYKEYMICROSOFT.SQLSERVER.CHAINER.SETUP.RESOURCESMICROSOFT.SQLSERVER.CHAINER.INFRASTRUCTURE.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.BOOTSTRAPEXTENSION.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.SQLCONFIGBASE.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.SFC.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.SETUPEXTENSION.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.MSIEXTENSION.RESOURCESMICROSOFT.SQLSERVER.CHAINER.EXTENSIONCOMMON.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.SCO.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.CONFIGEXTENSION.RESOURCESMICROSOFT.SQLSERVER.DISCOVERY.RESOURCESMICROSOFT.SQLSERVER.CONNECTIONINFO.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.UIEXTENSION.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.WIZARDFRAMEWORK.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARDFRAMEWORK.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARD.RESOURCESMICROSOFT.SQLSERVER.MANAGEMENT.CONTROLS.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.CONNECTIONINFO.RESOURCESMICROSOFT.SQLSERVER.CONFIGURATION.RULESENGINEEXTENSION.RESOURCESLANDINGPAGE.RESOURCESIf the security code group is not located on the computer, the following error message is returned:

1. c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>caspol -remgroup blah
2. Microsoft (R) .NET Framework CasPol 2.0.50727.1433
3. Copyright (c) Microsoft Corporation.All rights reserved.
4.
5. ERROR: Invalid label or name
6.
7. Usage: caspol <option> <args> …
8.
9. caspol -rg
10. caspol -remgroup <label|name>
11. Remove code group at <label|name>
12.
13.
14. where “<mship>” can be:
15. -allcodeAll code
16. -appdirApplication directory
17. -custom <xml_file>Custom membership condition
18. -hash <hashAlg> {-hex <hashValue>|-file <assembly_name>}
19. Assembly hash
20. -pub {-cert <cert_file_name> | -file <signed_file_name> | -hex <hex_string>}
21. Software publisher
22. -gacInstalled in the Global Assembly Cache
23. -site <website>Site
24. -strong {-file <assemblyfile_name> | -hex <public_key>}
25. {<name> | -noname} {<version> | -noversion}
26. Strong name
27. -url <url>URL
28. -zone <zone_name>Zone, where zone can be:
29. MyComputer
30. Intranet
31. Trusted
32. Internet
33. Untrusted
34.
35. where “<flag>” can be any combination of:
36. -exclusive {on|off}
37. Set the policy statement Exclusive flag
38. -levelfinal {on|off}
39. Set the policy statement LevelFinal flag
40. -n[ame] <name>
41. Code group name
42. -d[escription] <desc>
43. Code group description
44.
45. c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>If the security code group is deleted when you run the caspol.exe –q –rg code group command, the following message is returned:
1. c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>caspol -remgroup blah
2. Microsoft (R) .NET Framework CasPol 2.0.50727.1433
3. Copyright (c) Microsoft Corporation.All rights reserved.
4.
5. The operation you are performing will alter security policy.
6. Are you sure you want to perform this operation? (yes/no)
7. y
8. Removed code group from the Machine level.
9. Success

The Microsoft SQL Server support policy for Microsoft Clustering

Symptoms
This article describes the Microsoft support policy for SQL Server failover clustering. Microsoft Customer Support Services (CSS) supports SQL Server failover clustering that is based on the failover clustering features of the Microsoft Cluster Service in the following products: Windows 2000 Advanced ServerWindows 2000 Datacenter EditionWindows Server 2003 Enterprise EditionWindows Server 2003 Datacenter EditionWindows Server 2008 Enterprise EditionNote Windows Server 2008 failover clusters only support SQL Server 2005 Service Pack 2 or later versions.
Important Upgrading SQL Server 2000 Enterprise Edition to SQL Server 2005 Standard Edition is not a supported upgrade path. For more information, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms143393.aspx(http://msdn2.microsoft.com/en-us/library/ms143393.aspx) If you want a fallback solution when you upgrade the SQL Server 2000 failover cluster instance,we recommend that you perform a new installation of the SQL Server 2005 failover cluster instance because ofextreme recovery measures. Then, migrate the data to the new installation. The current installation will remain intact if unforeseen circumstances prevent the SQL Server 2005 installation from completing in a timely manner.
Microsoft server clusters are only supported on cluster solutions that are listed in the Windows Server Catalog under Cluster Solutions. To view the Windows Server Catalog, visit the following Microsoft Web site:
http://www.windowsservercatalog.com/(http://www.windowsservercatalog.com/)The term “server clusters” means computers that run the Microsoft Cluster Service. The Windows Server 2003 family provides the following types of clustering services: Server Cluster (Failover Cluster) Network Load BalancingCompute Cluster ServerOnly the Server Cluster solutions can be used together with SQL Server for high availability if a node is lost or if a problem exists with an instance of SQL Server. Network Load Balancing may be used in some cases together with stand-alone read-only SQL Server installations. SQL Server Failover Clustered Instances each require a unique group. This requirement is true on cluster disk resources that use drive letters that are unique to the cluster and to each SQL Server Failover Clustered Instance. Each Failover Clustered Instance of SQL Servermust also have at least one unique IP address. Depending on the version that is installed, multiple unique IP addresses may be possible. Additionally, each Failover Clustered Instance must have both virtual server and instance names that are unique to the domain to which the cluster belongs.
Supported SQL Server failover clustering installations must also follow the Microsoft support policy for server clusters, and the Windows Server Catalog/Hardware Compatibility List.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
309395?(http://support.microsoft.com/kb/309395/) The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server CatalogStarting with Windows Server 2003, Microsoft SQL Server 6.5 and Microsoft SQL Server 7.0 clustering will no longer be supported, as noted in the following Microsoft Knowledge Base article:
810391?(http://support.microsoft.com/kb/810391/) SQL Server 6.5, SQL Server 7.0, and MSDE 1.0 support on Windows Server 2003If you cluster SQL Server with any clustering product other than Microsoft Server Clustering, your primary support contact is the third-party cluster solution provider for any support issues that are related to SQL Server. SQL Server was developed and tested by using Microsoft Server Clustering. Third-party clustering solutions that support SQL Server installations should be your primary contact for any installation issues, performance issues, or cluster behavior issues. CSS provides commercially reasonable support for third-party cluster installations in same manner that we do for a stand-alone version of SQL Server.Number of supported nodesThe following is a list of the number of nodes that are supported by each version of Microsoft SQL Server: Microsoft SQL Server 7.0
Microsoft SQL Server 7.0 supports up to two nodes in a failover cluster.Microsoft SQL Server 2000 Enterprise Edition (32-bit)
Microsoft SQL Server 2000 Enterprise Edition (32-bit) supports up to four nodes in a failover cluster.Microsoft SQL Server Enterprise Edition (64-bit)
Microsoft SQL Server Enterprise Edition (64-bit) supports up to eight nodes in a failover cluster.Microsoft SQL Server 2005 Standard Edition (32-bit or 64-bit)
Microsoft SQL Server 2005 Standard Edition supports up to two nodes in a failover cluster.Microsoft SQL Server 2005 Enterprise Edition (32-bit or 64-bit)
Microsoft SQL Server 2005 Enterprise Edition supports up to eight nodes in a failover cluster.Note If you upgrade Microsoft SQL Server 2000 (32-bit) to Microsoft SQL Server Enterprise Edition (64-bit), SQL Server will still only support four nodes.Mounted drivesThe use of mounted drives is not supported on a cluster that includes a Microsoft SQL Server installation. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
819546?(http://support.microsoft.com/kb/819546/) SQL Server 2000 and SQL Server 2005 support for mounted volumes
Note SQL Server 2005 failover cluster instances are not supported on failover cluster instance nodes that are used as domain controllers.
Resolution
SQL Server failover clustering for clusters that are not listed on the HCL in the cluster categoryIf your SQL Server failover cluster solution is not listed in the Windows Server Catalog/Hardware Compatibility List. as a supported “Cluster Solution”, it is considered unsupported and may yield unexpected behavior. However, CSS will offer troubleshooting tips and provide reasonable support if requested. However, CSS does not guarantee that a resolution will be found for non-Windows Server Catalog/HCL cluster solutions.
For support, follow these steps: Before any troubleshooting begins, you must contact the Original Equipment Manufacturer (OEM) to discuss whether your particular cluster implementation is supportable. The OEM can best answer configuration and supportability questions for the cluster hardware.Upon agreement that no solution is guaranteed, and that no incident refund will be provided, CSS can troubleshoot the issue. Microsoft does not guarantee a solution with non-HCL clusters. If no resolution is found, the incident will not be refunded.
If it is not agreed that a solution is not guaranteed, CSS will not troubleshoot the issue and will refund the incident.CSS will use standard troubleshooting processes to isolate the server cluster issue. Some typical troubleshooting methods that are used by CSS include: Use of the Microsoft Knowledge Base. The Microsoft Knowledge Base is available to customers through Microsoft TechNet, or you can visit the following Microsoft Web site:
http://support.microsoft.com(http://support.microsoft.com/)Determine whether the problem can be replicated on supported clusters (where possible).Note If the cluster is not certified, there is no hotfix support available. CSS cannot determine whether the problem is caused by hardware incompatibility or by unwanted software behavior.If there is no solution to the problem, CSS may recommend some constructive alternatives, which include: Having you reproduce the problem on a cluster that is on the Cluster HCL.Asking you to use a cluster solution that is on the Cluster HCL.Having you work with the OEM to get the cluster on the Cluster HCL.Asking you to work with the OEM for a solution. The hardware specifications for server clusters are extremely stringent. The Cluster HCL contains a list of known acceptable cluster configurations that have been tested. You can waste a lot of time by trying to troubleshoot perceived server cluster issues that are being caused by the cluster hardware that you are using.
Some examples of hardware incompatibilities that can cause cluster problems include: SQL Server Failover Clustering installation failures.The cluster solution does not correctly isolate the shared disk and host bus adapters (HBAs) from other devices on the shared bus.The SCSI controller does not support operating in a multiple-initiator environment.The HBA does not correctly handle reservations or release or renew a device on the shared bus.The caching mechanism on the controller is incompatible with the cluster configuration.The network adapters for intra-cluster communication have too high a latency.The RAID controller does not correctly replicate configuration information between controllers.The PCI bus is incorrectly configured and has incorrect adapters in the wrong bus (primary, secondary, tertiary).The controllers are incompatible with the “Physical Disk Resource” type.The SCSI controller does not deploy proper termination. This list does not include all the issues that can cause problems with a server cluster. None of these issues can be detected by CSS. All these issues would typically be discovered if the complete cluster solution were tested for Cluster HCL compatibility.
If a complete cluster configuration is listed for an earlier operating system but is not listed for the newer operating system that you are using, support as documented in this section will be followed.
SQL Server 2005 support for mixed 32-bit and 64-bit SQL Server failover cluster instancesYou must be running Windows Server 2003 Service Pack 1 or a later version. For more information, see the following Microsoft Knowledge Base articles. For IA-64 installations, see the following article in the Microsoft Knowledge Base:
312090?(http://support.microsoft.com/kb/312090/) Cannot use 32-bit resources on a 64-bit server clusterFor X64 installations, see the following article in the Microsoft Knowledge Base:
875423?(http://support.microsoft.com/kb/875423/) Support for 32-bit programs on 64-bit server clusters is included in Windows Server 2003 Service Pack 1 and in x64-based versions of Windows Server 2003Warning Resource DLLs for 32-bit programs cannot run on a 64-bit computer that is running a 32-bit version of Windows Server 2003 without any service packs installed. Therefore, you cannot run 32-bit programs on a 64-bit server cluster. In this scenario, you must use a 64-bit version of the resource DLL.
Limitations of using mixed SQL Server 2000 and SQL Server 2005 failover cluster instancesWhen you use SQL Server 2000 installations and SQL Server 2005 installations on the same cluster, the SQL Server 2000 installations must be installed before you install SQL Server 2005 instances locally or as failover cluster instances. All failover cluster instances will use the SQL Server 2005 Server Cluster resource. This includes the instances of SQL Server 2000.
Additionally, after SQL Server 2005 is installed, SQL Server Native Client is the primary protocol that is used. The changes to the Server Cluster resource DLL and the primary protocol that is used will prevent installation of SQL Server 2000 or re-addition of nodes to SQL Server 2000 failover cluster instances. This occurs because neither the resource DLL nor the primary protocol existed at the time SQL Server 2000 was released and will not be recognized as a valid Server Cluster resource DLL or as a primary protocol for SQL Server failover cluster instances.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
905618?(http://support.microsoft.com/kb/905618/) You may receive a connection error message when you try to connect to an instance of SQL Server 2000 or of SQL Server 7.0 that was installed after you installed SQL Server 2005Stand-alone installations are not affected during initial installation like virtual failover cluster instances. In virtual failover cluster instances, this will prevent the initial installation from completing.
Note After you install SQL Server 2005, SQL Server Service Manager displays the node name instead of the virtual SQL Server 2005 server name. It does this because SQL Server Service Manager was not coded to handle SQL Server 2005, and SQL Server 2005 does not include SQL Server Service Manager.
Windows Server 2008 Failover ClustersOnly SQL Server 2005 Service Pack 2 (SP2) or later versions of SQL Server 2005 are supported with Windows Server 2008 Failover Clusters.
Migrating SQL Server Failover Cluster Instances to New Domain SQL Server 2000, 2005, and 2008 can be migrated to a new domain while clusterd is using domain users for service accounts on Windows 2000 and Windows 2003 Server Failover Clusters. SQL Server installations on Windows 2008 Failover Cluster will require uninstalling SQL Server Database Engine and Analysis Services if installed since Cluster will need to be uninstalled per
269196?(http://support.microsoft.com/kb/269196/) How to move a Windows Server cluster from one domain to anotherPrior to uninstalling SQL Server must be set to use mixed mode security or new domain accounts added to the SQL Server logins and the DATA folder containing system databases must be renamed prior to uninstalling so this folder may be swapped back in once reinstalled to reduce down time. No removal of SQL Server support files, SQL Server Native Client, Integration Services or Workstation Components should be done.

FIX: Restoring a SQL Server 7.0 database backup in SQL Server 2000 Service Pack 2 (SP2) may cause an assertion error in the Xdes.cpp file

Symptoms
When you try to restore a database backup, the restoration may fail, and a retail assertion with error 3624 may occur. You may see the following error message in the SQL Server error log files as a result of the assertion error:

SQL Server Assertion: File: <xdes.cpp>, line=9860
Failed Assertion = ‘IS_OFF_SAFE (XDES_OUTCOME_ONLY, m_status)’
This problem occurs when all the following conditions are true: You take the database backup from a Microsoft SQL Server 7.0 database.Whileyou take the database backup, transactions that involve multiple databases are logged in the transaction logs.You restore the database backup in SQL Server 2000 Service Pack 2 (SP2).
Resolution
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or tocreate a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

DateTimeVersionSizeFile namePlatform————————————————————————-09-Dec-200221:392000.80.714.07,471,185Sqlservr.exeX86 Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
Important This hotfix build is designed for a server that is running Microsoft SQL Server 2000 Service Pack 2:

Error message when you try to install SQL Server 2005: “Could not find a package to install on the installation media”

Symptoms
When you try to install a version of MicrosoftSQL Server 2005 that has been downloaded from the Microsoft Web site, you receive the following error message:

Could not find a package to install on the installation media.Additionally, error messages that resemble the following may be logged in the SQLSetupNumber_ServerName_Core(local).log file:

2005/9/30 10:5:19Error: Action “DeterminePackageTransformsAction” threw an exception during execution.
Failed to open package to determine installing product code : 110NotesThe SQLSetupNumber_ServerName _Core(local).log file is located in the C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files folder.Number is a placeholder for a number that increases for every installation of SQL Server 2005. The log file that has the largest value for Number in the file name is the log file for the most recent installation of SQL Server 2005.
Resolution
This problem occurs because a Sqlrun_*.msi file in the Setup folder on the SQL Server 2005 Setup media is corrupted. For example, the Sqlrun_NS.msi file is corrupted. Therefore, the Setup program cannot open the corrupted package during the installation and returns error code 110.

BUG: You receive an error message that contains a decimal representation of the SQL Server version number

Symptoms
When you restore a system database from a backup device file in Microsoft SQL Server, you may receive an error message that is similar to the following:

The backup of the system database on device Full Path of the Backup Device File cannot be restored because it was created by a different version of the server (134218407) than this server (134218488).
RESTORE DATABASE is terminating abnormally.
The error message contains version numbers in parentheses that are not valid (7.00.623 for SQL Server 7.0 or 8.00.760 for SQL Server 2000 Service Pack 3 [SP3], for example).
Resolution
To determine the correct version of a database backup device file in SQL Server, run the RESTORE HEADERONLY Transact-SQL statement using the backup device file name.TheRESTORE HEADERONLY Transact-SQL statement returns the following columns to help you determine the version of the database backup file:SoftwareVersionMajorSoftwareVersionMinorSoftwareVersionBuildFor more information about the RESTORE HEADERONLY Transact-SQL statement, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/aa238455(SQL.80).aspx(http://msdn2.microsoft.com/en-us/library/aa238455(SQL.80).aspx)The decimal numberthat indicates the version of SQL Server in the error message is obtained by converting part of the SQL Server version number to a hexadecimal representation.You can also manually determine the actual version number of SQL Server from the decimal number that is mentioned in the error message.To do so, follow these steps: Convert the decimal number that is mentioned in the error message to a hexadecimal representation. Convert only the last four digits of the hexadecimal representation to a decimal representation.Replace the last three digits of the hexadecimal representation with the decimal number from step 2.To determine the actual version number of SQL Server, format the result by using the information in the “Standard format of SQL Server version numbers” section of this article.Note You can use the Calculator program in Microsoft Windows in Scientific view to convert the number from a decimal representation to a hexadecimal representation.
For example, to determine the actual SQL Server version number for the decimal number that is mentioned in the error message (134218407), follow these steps: Convert the decimal number 134218407 to a hexadecimal representation. The hexadecimal representation of 134218407 is 80002A7.Convert the last four digits of the hexadecimal representation to a decimal representation. The decimal representation of 02A7 is 679.Replace the last four digits of the hexadecimal representation with the decimal numbers that you obtained in step 2. The number is 800679.Format the number in step 3 by using the information in the “Standard format of SQL Server version numbers” section of this article. The version of SQL Server is 8.00.679.
Standard format of SQL Server version numbersThe version numbers of SQL Server use the following standard format:
Major version number.Minor version number.Build number
For example, the version number of an instance of SQL Server 2000 SP3 is 8.00.760, where the first number (8) indicates the major version number, the next two numbers (00) indicate the minor version number, and the last three numbers (760) indicate the build number.

FIX: Exception Error Closing an Application Containing a CoolBar Control

Symptoms
A Visual Basic application that has a CoolBar control crashes while exiting the application. This occurs when there is an End statement in the unload event of the form that hosts a CoolBar control. This behavior occurs only when running the executable and does not happen in the Visual Basic integrated development environment (IDE). The error message is similar to the following:
In the Windows 9x platform:

This program has performed an illegal operation and will be shutdown.Clicking on the Details button may reveal text similar to the following:

PROJECT1 caused an exception 10H in module MSVBVM60.DLL at 015f:66024d53.In Windows NT or Windows 2000 platform, the following error message appears:

Form1:Project1.exe – Application Error
The exception Floating-point inexact result.
(0xc000008f) occurred in the application at location 0×77f1d493.
Resolution
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected inService Pack 4 for Visual Studio 6.0.
For additional information about Visual Studio service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base:
194022?(http://support.microsoft.com/kb/194022/EN-US/) INFO: Visual Studio 6.0 Service Packs, What, Where, Why
194295?(http://support.microsoft.com/kb/194295/EN-US/) HOWTO: Tell That a Visual Studio Service Pack Is InstalledTo download the latest Visual Studio service pack, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/vstudio/Aa718353.aspx(http://msdn2.microsoft.com/en-us/vstudio/Aa718353.aspx)