Recent content by Dan4gl

Thank you .. that gives us some place to look in our code.

i do think that the disk usage is related to one of the following : lbi... rcda.. , DBI, or SRT files ,but since the file is marked for deletion and is in this odd state, we cannot tell what file type is consuming the disk space. Look at the screen shots attached and you will see why we cannot...

I have attached a screen shot of what we see when using Wiztree , so not an issue of unhiding files. We know that the files are hidden by default, but this seems to be some OS (windows) item. This is very similar to the original post. Using Process Explorer we can trace the files to an Agent...

Thank you as this is very helpful.. problem is we cant enable logging on a large user system due to performance issue but would have to do so in our QA environment. Sorry for posting on an old post, but the extend/deleted folder was similar to what we were seeing. We are also seeing the disk...

We are using PASOE 12.2.16 and found that the mproapsv.exe was holding over 6.5 GB in one of the files in that folder H:\$Extend\$Deleted on our "Temp" folder drive. Using Process Explorer from Sysinternals we could connect the file unique identifier to the file in WizTree looking at the file...

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