[03] FlowSsh Technical Support

These discussion groups are closed due to spam that could not be controlled within abilities of this support system.

For any technical or licensing inquiries about FlowSsh, please open a new support case.

Any information you find herein is outdated, and not applicable to our latest software versions.

Visual Studio 2005 C++ runtime

Hi all,  We have begun to distribute our flowSSH based application.  We have noticed that on most of the server installations, after installing the c++ redistributable, a reboot is required.  Although the redist package does not notify the user as such. The reboot requirement is killing us becasue we install the client on production database servers that have high availability requirements. (Target OS is windows server 2008 r2)

I have been told that if we use a merge module approach to installing the c++ runtime we would not have this problem.  Can you provide any guidance on what we need to package in the merge module for FlowSSH to work?  Or if a merge module would alleviate the reboot requirement?
Wednesday, January 25, 2012

I am surprised that a reboot is required after installing the run-time. I have not witnessed the need for a reboot so far; in my experience, after running the needed version of vcredist, the application that requires the runtime begins to work.

Are you finding that this is not the case after you run vcredist on the target platform?

I found the following information about installing the VS runtime using merge modules:


Please note that this assumes that your existing installation is done using MSI. Merge modules cannot be installed on their own, but are intended to be integrated into another MSI-based installation:


The .msm file version you will need depends on whether you're using the FlowSshNet DLL we provide, or a version that you compiled on your own.

If you're using our version of the FlowSshNet DLL, please let me know, and I will look into obtaining the right .msm file that you can use.

If you're using a FlowSshNet DLL that you compiled yourself, then look into the following directory on your development machine:

C:\Program Files\Common Files\Merge Modules

Alternately, if your development machine is 64-bit:

C:\Program Files (x86)\Common Files\Merge Modules

You will find here a bunch of MSM files for the various versions of the Visual Studio runtimes.

I suspect that one or both of the following are what you need:

denis bider
Wednesday, January 25, 2012

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
Powered by FogBugz