hdeshmukh
10-08-2003, 04:41 PM
Hi there,
I seem to have this intermittent problem in my current Visual Build Pro setup. Randomly during the compile of a large dsw file, Visual Build Pro gets a DDE Error Memory Access Violation from C++ which results in a message box that waits for user to input ok or cancel. The problem is:
(a) there is nothing wrong with the code being compiled. It has not changed and compiled in VC++ Successfully and also compiled successfully in VisualBuild as well.
(b) if I re-run the step, it is just as likely to complete as it is to fail with the same error.
(c) the error step of sending an email does not get triggered until the user clicks on the message box, which is a real pain, cause you can never know when the build has actually failed, in which case it just sits there and the build has to be constantly monitored to make it complete successfully.
Now with VisualBuild Pro 4.5, I found that running PCAnywhere on the build machine at the same time as a build would increase the chances of the error occurring. But on this new build machine, with version 5.0, PCAnywhere is not installed (Only VNC is), although it seems that the error started occurring more once Symantec Norton Antivirus was installed. So I disabled Norton Antivirus, but I am still getting this same error.
Has anyone run into the problem? And has anyone got any tips for me to avoid this situation.
Thanks in advance for any assistance/advice
UPDATE: How fortunate!!! The error just reoccurred! I can now attach the bmp of the error message:
Hamad Deshmukh
Software Developer
Creo Inc.
email: Hamad.Deshmukh@Creo.com
I seem to have this intermittent problem in my current Visual Build Pro setup. Randomly during the compile of a large dsw file, Visual Build Pro gets a DDE Error Memory Access Violation from C++ which results in a message box that waits for user to input ok or cancel. The problem is:
(a) there is nothing wrong with the code being compiled. It has not changed and compiled in VC++ Successfully and also compiled successfully in VisualBuild as well.
(b) if I re-run the step, it is just as likely to complete as it is to fail with the same error.
(c) the error step of sending an email does not get triggered until the user clicks on the message box, which is a real pain, cause you can never know when the build has actually failed, in which case it just sits there and the build has to be constantly monitored to make it complete successfully.
Now with VisualBuild Pro 4.5, I found that running PCAnywhere on the build machine at the same time as a build would increase the chances of the error occurring. But on this new build machine, with version 5.0, PCAnywhere is not installed (Only VNC is), although it seems that the error started occurring more once Symantec Norton Antivirus was installed. So I disabled Norton Antivirus, but I am still getting this same error.
Has anyone run into the problem? And has anyone got any tips for me to avoid this situation.
Thanks in advance for any assistance/advice
UPDATE: How fortunate!!! The error just reoccurred! I can now attach the bmp of the error message:
Hamad Deshmukh
Software Developer
Creo Inc.
email: Hamad.Deshmukh@Creo.com