Visual C++ files in vendor MSI


I have just packaged Cisco Jabber 11 for deployment. The package consists of the Vendor MSI and a custom MST with only very few changes generated by Installshield.

Once the package is installed the software works fine. The problem arises when you launch our mail client Lotus Notes 8.5.3...

All of a sudden Lotus notes is complaining about missing two files




Which are components of Visual Studio c++. Now the Jabber installation does in fact install these files into it's install directory but I can NOT find these files anywhere else on the system so I am at a loss as to why simply installing this software has suddenly impacted Lotus Notes. The files are not set to self register either so again that seems strange.

Two fixes I have are a) move the files to the System32 directory so Lotus Notes can reference them also or b) install MS VisualC++ 2013 redistributable as a dependency to fix this issue with the other application...seems a roundabout fix.

Thoughts? Recommendations?



0 Comments   [ + ] Show comments

Answers (4)

Answer Summary:
Thanks Dunnpy, looks like this is a known issue with the version we are installing...I have sent the bug report to our cisco support team to get them to review and download the latest version.
Posted by: cj goggin 5 years ago
White Belt

Alter your lotus notes installer so that it also drops copies of those dlls in the same path as that of its main executable.   Alternatively, your own b) option but as a separate package so that it can be linked to other installer packages and installed before them as needed.

Posted by: apptopack 7 years ago
Red Belt
Why not use merge module to overcome this issue.
Posted by: dunnpy 7 years ago
Red Belt

Top Answer

This would appear to be a recent, known bug with Jabber 11 (16/12/2015)

You need a login with a Cisco.com account to access the information about the resolution etc.


Posted by: Pressanykey 7 years ago
Red Belt
I would suggest that you create a deployment package for the version of the c/c++ runtime (12?) as these applications will not be the only ones that *may* need them. If this solves your direct problem I cannot say, but it is one less potential cause. As it seems that Jabber is installing them "privately" no other applications will "see" them, hence if other applications depend on these dll's (as they are not COM they do not require registration) cannot find them, and this may cause the errors you are experiencing.

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ