Search results

We have a very large legacy application with 32 bit OCX controls and DLLs that will take a very large effort to replace and test. OOM = Out of memory exception messages from Windows. PASOE reference will solve only half the problem. We have tried to use... I believe it was called the...

We are slated to move to PASOE 12.2.12 in the near future but until then we are on this stable version. We are not able to upgrade to .17 as we would need to do that on over 2500 servers for many different customers. We deploy this as an external application to our customers. We see it in...

We are running 11.7.5.009 and we dont have the luxury of enabling client logging on our users systems as that would slow things down and we dont know what sessions are leaking the memory. Its not a workflow that we are able to reproduce.

We are having issues with memory leaks and having a really hard time finding them. It could be there is just more data needed for the application. We are trying to use a stop gap measure in the meantime to add LargeAddressAware to the prowin32.exe and _proapsrv.exe . We were wondering if...

I have found that this has to do with the way the database is setup and not so much with the connection string. Try removing the -Mm parameter from the database startup or select the SQL only option in the Progress Explorer tool.

Researched Prospy So far it appears that you must do a "complete" Install of Provision and not the Typical Installation. There must be some dependencies that are missing when doing a "Typical" Install. :eek:

I have tried to use Pro*Spy plus in 9.1D05 and it appears not to work at all. There are several error messages that come up but there is no action on the part of the tool. Has anyone out there had any luck with the new "enhanced" Pro Spy Plus.... :( Thanks