Profound Logic Forums

The most obvious cause of a problem like this would be if the initial program is ending without displaying a rich display file.

Another idea is to try running your program in debug mode, as described here:
http://www.profoundlogic.com/docs/displ ... ith+STRDBG

Maybe you can see if it's opening/displaying a file properly?

Thank you Scott for replying to my query. however, even if I try to launch programs from the puisample library, which was working before the upgrade, the same message is being displayed, so I know something is not right. please find attached the screen-shot I get when I try to use the web-debugging as suggested.

Hi Chris,

Thank you for the reply! And, I agree with you, something is not right. The hard part, however, is to understand what is not right, so we can correct it.

When I launch programs in PUISAMPLES from my machine, they launch without error. So we need to figure out what's different about your setup/machine vs. mine. Once I'm able to reproduce the problem on my own machine, I think I'll be able to help you fix the problem pretty easily. So the hard part is figuring out what might be different.

The job log you posted shows that ProfoundUI is calling a routine named PUIRUNERRO (Which may be an abbreviation for another routine name). however, I've looked for this routine in the source code of Profound UI, and it does not appear that we call a routine with this name -- so that's very strange. Possibly, you are running an older version of Profound UI? Or, maybe you have some left over objects from an old version? These would be good things to look for.

Hi Scott, is it possible for me to uninstall the profoundui and do a clean reinstallation? Atrium runs fine on the development partition, but it's the designer that's installed on the development partition that's giving the problem. I have already tried simply re-installing the profoundui on this partition, to no avail.
so any suggestions on uninstalling it?

Thanks in advance.

Hi Chris,

I don't think that the designer causes your problems. I run on my demo machine 4.2.2 without having problems, except changes in the application environment are done. Remember, have you changed any adjustment, library, authority, user-profiles or something like that before?
This can affect the initial program (e.g. default library list) and the launch of any program will fail.

no change at all. I asked my developers to exit the designer, then I installed the upgrade, then told them to continue. that's when the problem started. I really need some help here.

Hi Chris:

I am in version 4.2.2 and I found the procedure PUIRUNERROR inside the service program PUIRUNERR.

Attached find the screen shots of what I found.

Hiya Chris,

If you really need help and are up-to-date on your support contract, don't forget that you can contact support@profoundlogic.com to create a support ticket and get higher priority placed on your problem.

If you'd like to keep working in forums, I can keep trying to help you, too.

As far as removing ProfoundUI, there are really only a few components.

• Before doing anything, please back everything up. There's an excellent chance that you have made modifications to your environment that will be lost by delete/reinstall if you don't create good backups.
• During installation, there's a library created named PROFOUNDUI by default -- however, you can change that name during install. So if you can rememeber what you called it (or left the default of PROFOUNDUI) then deleting this library will go a long way to removng PROFOUNDUI.
• During installation, ProfoundUI will create an HTTP server instance. By default, that's located in /www/profoundui of the IFS. However, like the library name, you are able to modify the name during install -- so if you changed it, make sure you use the changed name. Deleting this will remove all of the code that gets loaded and run in a web browser when using PUI. Be careful with this part, as it's very frequent for customers to make modifications, here -- so make sure your backups are good.
• ProfoundUI also creates a member in the QUSRSYS/QATMHINSTC file provided by the IBM i operating system. This file is the master list of all HTTP servers running on your partition. Most likely, it's not needed to remove this -- but, if you do, it's a matter of finding the member named PROFOUNDUI (though, again, an alternate name can be given during installation)
• Finally, ProfoundUI creates a data area named QGPL/PUIKEY where it stores your license information. I strongly recommend leaving this object intact. Deleting it will not help you.

So, it's mainly just the two locations, the PROFOUNDUI library and the /www/profoundui IFS path, by default. Wiping those out and reinstalling may help. But, again, please be careful of any customizations you might've made. Most customizations will be in /www/profoundui/htdocs/userdata, but they are sometimes found in other areas within /www/profoundui.

Hope that helps!

Thanks Jac53 and Scott. I'll try removing the components, maybe that particular service program on my system is corrupted.
We do have custom widgets, no custom library names tho. only the port number is customised.

Update to my predicament!
I deleted the profoundui library, deleted the www/profoundui ifs folder and installed the latest profoundui version (4.2.3). After giving back authority to the objects in the profoundui folder to to my developers, everything seems to be working once again. Thanks again guys.