Was this article helpful?
Was this article helpful?
Related Articles
Memory violation (49) when connected to secured db via shared memory in 12.2 467Number of Views MS Agents stop with memory violation (49) 2.92KNumber of Views Memory violation. (49) reported with a Rest request on PASOE 402Number of Views Client crashing with Memory Violation (49) when sending print job to invalid printer or printer queue times out. 244Number of Views Promon throws Memory violation (49) and brings database down 3.5KNumber of Views
Disclaimer
The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.
Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.