While we don't run Cygwin on our BladeLogic appservers, I do run Cygwin on my PC where I use nsh. I get the problem described in the OP every time I update Cygwin and get a newer version of cygwin1.dll than the one stored with BladeLogic.
To fix it, I just copy the more recent version of cygwin1.dll on top of the the older, BladeLogic one.
This is explained in more detail below (which I found some where on the Web):
The error is received because there is more than one version of the
Cygwin DLL found on the machine. Unfortunately, due to the way Cygwin works,
only one version of the cygwin1.dll may exist at a time on the system.
Cygwin strives to maintain backwards compatibility and their recommended
solution to this is that you should always use the latest version of Cygwin
on a system.
To resolve this issue, you should determine which version of cygwin1.dll
is newer (the one that BSA installs or the one that is part of your other
Cygwin installation) and sync both of them up to whichever is newer
(ie. either copy the one from BSA to your Cygwin directory or vice versa).
There are other utilities that use cygwin – iirc nomachine, some ssh servers, etc
Hi Brian, I have copied latest version of cygwin1.dll to C:\Program Files\BMC Software\BladeLogic\NSH\bin\ in our app servers (windows 2008 R2 servers) didn't resolve the issue.
This is like pain now.. We are using fully automated deployments using NSH from jenkins. now all our auto deployments are failing continuously with above errors..
Please let me know perm. solution to this.
The only other thought I have is to make sure that all the copies of cygwin1.dll are the same up-to-date version. Try using "find" to identify all the cygwin1.dll files you have. As pointed out by Bill, other apps use Cygwin too.
Does Atrium Orchestrator use cygwin1.dll anywhere? We had this issue recently occur and it corresponded almost exactly with resetting the AO CDP to try to resolve an unrelated issue.
If it’s calling nsh it would.