[RESOLVED] SQLDOM fails to install

[RESOLVED] SQLDOM fails to install by Arvind Shyamsundar

Closed

as Not Reproducible Help for as Not Reproducible

Type:	Bug
ID:	767144
Opened:	10/11/2012 11:50:03 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

I am trying to install the 32-bit SQLDOM.MSI from http://www.microsoft.com/en-us/download/details.aspx?id=29065. The installation fails with the error:

"Error writing to file: Microsoft.SqlServer.TransactSql.ScriptDom.dll. Verify that you have access to that directory."

I have verified that the MSI is intact by installing it on other machines.

Details (expand)

English

SQL Server 2012 - Enterprise Edition

Tools (SSMS, Agent, Profiler, Migration, etc.)

Other

US English

Install SQLDOM.MSI on Windows 2003.

MSI fails to install with the error "Error writing to file: Microsoft.SqlServer.TransactSql.ScriptDom.dll. Verify that you have access to that directory."

The full MSI log is here:

Error 1304. Error writing to file: Microsoft.SqlServer.TransactSql.ScriptDom.dll. Verify that you have access to that directory.
Error 2350. The installer has encountered an unexpected error. The error code is 2350. FDI server error
Error 1334. The file 'ENG_Microsoft_SqlServer_TransactSql_ScriptDom_dll_32' cannot be installed because the file cannot be found in cabinet file 'Redist.cab'. This could indicate a network error, an error reading from installation media, or a problem with this package.
=== Logging stopped: 10/12/2012 12:08:39 ===

The DOM should install on Windows 2003. I realize that the core server is not allowed to install on 2003, but then shared redistributable components like SMO still work on Windows 2003.

Hyper-V (On-Premise)

0 attachments

Posted by ajhuddymsdn on 2/6/2013 at 3:05 PM

No, it shouldn't be closed. The MSI should give a warning that .NET 4.0 is not installed.

Posted by Microsoft on 10/23/2012 at 11:44 AM

Thank you for confirming, the issue will be closed. Alex Grach [MSFT]

Posted by Arvind Shyamsundar on 10/12/2012 at 12:07 AM

My apologies, please close this as a false alarm. The issue occurred due to non-installation of the .NET 4.0 framework.

It would have been nice to have a pre-requisite check, though :-)