Unable to update the Deep Security Manager DB Schema when Microsoft SQL Server was not installed on C:\ drive

- Updated:
- 25 Aug 2017
- Product/Version:
- Deep Security 10.0
- Deep Security 10.1
- Deep Security 9.0
- Deep Security 9.5
- Deep Security 9.6
- Platform:
- Windows 2003 Enterprise
- Windows 2003 Enterprise 64-bit
- Windows 2003 Server R2
- Windows 2003 Standard
- Windows 2003 Standard 64-bit
- Windows 2008 Datacenter 64-bit
- Windows 2008 Enterprise
- Windows 2008 Enterprise 64-bit
- Windows 2008 Server R2
- Windows 2008 Server R2 Datacenter
- Windows 2008 Server R2 Enterprise
- Windows 2008 Standard
- Windows 2008 Standard 64-bit
- Windows 2012 Datacenter R2
- Windows 2012 Enterprise
- Windows 2012 Enterprise R2
- Windows 2012 Server Essential R2
- Windows 2012 Standard R2

Summary

The following DB Migration Tool logs may appear when updating the Deep Security Manager (DSM) Database (DB) Schema:

2016-Oct-24:09:27:34 [+01]	INFORMATION	Assembly Version [1.0.0.0], File Version [1.0.0.4], Compile Time [2016-Aug-24-14:28:16]  2016-Oct-24:10:17:50 [+01]	INFORMATION	SQLCMD search directory [C:\Program Files\Microsoft SQL Server\]  2016-Oct-24:10:17:50 [+01]	INFORMATION	getSQLCmdPath -> No files at [C:\Program Files\Microsoft SQL Server\]  2016-Oct-24:10:18:03 [+01]	INFORMATION	installDependencies -> SQLCMD search directory [C:\Program Files\Microsoft SQL Server\]  2016-Oct-24:10:18:03 [+01]	INFORMATION	installDependencies -> No files at [C:\Program Files\Microsoft SQL Server\]

Details

The issue happens because the SQLCMD.exe is installed in a path other than C:\Program Files\Microsoft SQL Server\.

To successfully use the DB Migration Tool, recreate the same installation path under C:\ drive:

Duplicate the folder containing the SQLCMD.exe file to the folder where migration tool is searching (C:\ drive).
For example, if the SQLCMD.exe file is under D:\Program Files\Microsoft SQL Server\100\Tools\Binn, create C:\Program Files\Microsoft SQL Server\100\Tools\Binn\SQLCMD.exe.
Copy everything under D:\Program Files\Microsoft SQL Server\100\Tools\Binn\ to C:\Program Files\Microsoft SQL Server\100\Tools\Binn.
Relaunch the DB Migration Tool and then update the Deep Security Manager DB Schema.

Rating:

Category:

Troubleshoot; Update

Solution Id:

1115670

Feedback

Did this article help you?

Thank you for your feedback!

What was the problem with this article?

The image(s) in the article did not display properly.

The article did not provide detailed procedure.

The article is hard to understand and follow.

The video did not play properly.

The article did not resolve my issue.

Others. Please specify.

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:

We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

Thanks for voting.

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:

We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.