We are getting the following error on executing dlls that we recompile and deploy.
Nome da aplicação com falha: MTrans.EXE, versão: 0.0.0.0, carimbo de data/hora: 0x51475a10
Nome do módulo com falha: MFC80.DLL, versão: 8.0.50727.6195, carimbo de data/hora: 0x4dcdeca2
Código de excepção: 0xc0000005
Desvio de falha: 0x00022df8
ID do processo com falha: 0x1120
Data/hora de início da aplicação com falha: 0x01cf7e6938d114e9
Caminho da aplicação com falha: F:\Transporter\LocalFilesDEV\MTrans.EXE
Caminho do módulo com falha: C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
ID do Relatório: 8cc52d1a-ea5c-11e3-b7da-9c8e9959cdaf
The error is in Portuguese, but the recognizable part is where it mentions the MFC80.DLL, the version and so on, believe you will recognize it (Lucio posted a similar error in another thread and is in English https://communities.ca.com/web/ca-plex-ca-2e-global-user-community/message-board/-/message_boards/message/118725937?p_p_auth=cMS8qv7B&#p_19).
We know that this type of error may be caused by missing VC++ 2005 redistributables, but when that is the case, the error in event viewer mentions “SideBySide”, which is not happening at the moment and we know for a fact that they are installed, the application was and is running fine, except for what we recompile, which produces the error above.
We are generating cpp and the error appear to be in WinC functions, compiling with VS 2005 8.0.50727.867. The functions that we are replacing were previous compiled around 3 or 4 months ago and those run without any error. On other clients, this is not happening when we deploy the new files.
We see that the manifest files on the obj folder appear to be the same as before and the MFC80.dll dependency is from the same version.
When we check the old dll and pnl on Dependecy Walker and compare with the recompiled ones, it shows the same files dependencies and versions.
Anyone had any similar problem or have any idea what the problem may be?
The problem is now solved with a recompile of a specific function.
I am still without a reason for what happened, but the problem was not what we recompiled, was not recompiling one function called by the one we were recompiling.
There was no error with wrong parameter format, the previous and current version of the dll show the same dependencies on the Dependency Walker, so we see no difference.
If we get some explanation will post here.