I had originally posted on the sybase forum, about an issue
where we seemed to have powerbuilder applications that would hang, when splwow was running on a windows 7 - 64 bit
original post
We have a Main jump off point to our other applications.
We use a Run Command to call these.
One of the people here, seems to think that it's hanging
on the splwow64.exe even though there is no printing
involved.
It seems like it's waiting on something to free up, before
proceeding. The application is running in the task manager,
it's just waiting.
This is happening on a window 7 64-bit.
response
Have you tried using /pbdebug when you open the other applications? This
will give you an indicator of what line in the PB app it's hung on, and
if the debug output never shows up, you'll know it's the OS having
problems actually loading the app itself.
Does it happen for ALL of the "other" apps? Or only some of them? If
only some, any commonality between them? (order of startup, specific
data it's pulling, common objects being used)
More Detail
we ran one of our modules under debug
and, it seems to be handing when we do an openchannel
Executing instruction at line 6
Executing instruction at line 7
Executing class function F_PASS_SECURITY for class F_PASS_SECURITY, lib entry F_PASS_SECURITY
Executing instruction at line 5
Executing instruction at line 7
Executing class function OPENCHANNEL for class SYSTEMFUNCTIONS, lib entry _TYPEDEF
Executing system dll function
If we kill the splwow process... the module continues to run as normal
Any thoughts on this?