SQL Server BCP and Phantom CRLFs

Microsoft SQL Server comes with bcp.exe, a command-line tool that uses the Bulk Copy Program API. It allows to export data from tables and queries, import data from files into tables and it generates format files. Bcp comes with a lot of command line parameters. Find them all here. The tool is very convenient if you want a […]

Read More SQL Server BCP and Phantom CRLFs

SQL Server 2008 R2 – The performance counter registry hive is corrupted.

Sequel number four (yes, 4!) of the SQL Server 2008 R2 installation woes saga. Previous posts include: Version string portion was too short or too long Error code: 1605 Version’s parameters must be greater than or equal to zero This post discusses the following error which appears in Summary_%computername%_%date%_%time%.txt, located in C:\Program Files\Microsoft SQL Server\100\Setup […]

Read More SQL Server 2008 R2 – The performance counter registry hive is corrupted.

SQL Server 2008 R2 – Version’s parameters must be greater than or equal to zero

A third (!) and hopefully final blog post on SQL Server 2008 R2 deployment woes. Previous posts include SQL Server 2008 R2 – Version string portion was too short or too long and SQL Server 2008 R2 – Error code: 1605. This time the installation problem comes with the following beauty: Exception type: System.ArgumentOutOfRangeException Message: Version’s parameters must be greater […]

Read More SQL Server 2008 R2 – Version’s parameters must be greater than or equal to zero

SQL Server 2008 R2 – Error code: 1605

Yet another post on SQL Server 2008 R2 deployment woes. An unattended installation of SQL Server 2008 R2 – developer/management tools on Windows XP SP3 clients in this particular case – might fail with the following error: MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = ‘{0A869A65-8C94-4F7C-A5C7-972D3C8CED9E}’. Error code: 1605. The error appears in […]

Read More SQL Server 2008 R2 – Error code: 1605

SQL Server 2008 R2 – Version string portion was too short or too long

An enterprise-wide rollout of Microsoft SQL Server 2008 R2 Developer Edition can result in serious headaches. On Windows XP SP3 clients, the installer may abort with a System.ArgumentException error: Version string portion was too short or too long. The logfiles residing in %ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\Log reveal that the error occurs during the RunDiscoveryAction phase: Running Action: […]

Read More SQL Server 2008 R2 – Version string portion was too short or too long