Kbase P137478: Webclient sporadically failing to launch when communicating to WebServers that require authenticatio
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/23/2008 |
|
Status: Unverified
SYMPTOM(s):
Webclient sporadically failing to launch when communicating to WebServers that require authentication.
prowcini.exe listed in the Windows Task Manager but no corresponding WebClient application is visible.
prowc.exe listed in the Windows Task Manager but no corresponding WebClient application is visible.
FACT(s) (Environment):
OpenEdge 10.1B
OpenEdge 10.1C
Windows Server 2003
Windows Vista
CAUSE:
When the WebClent application prowcapp file (or cab files) are on a server that requires authentication (such as web server), the initializer is supposed to prompt for user/password. Occasionally the initializer may hang before it gets a chance to prompt for the authentication information and prowcini.exe or prowc.exe will show in the Task Manager.
This has been seen on on 64-bit Windows platforms (both 2003 and Vista) and on Vista 32-bit too.
CAUSE:
Bug# OE00176570
FIX:
A workaround has been identified as a short term fix.
Change the configuration file to always prompt for the user/password (unless cached).
1) Open the project in the WebClient Application Assembler
2) On the main window, click on the Locator button next to the Configuration File URL field and then select 'Prompt for ID/Password (Unless Cached)'
3) Regenerate the version (or generate a new one) and then deploy.
This will cause the application to always try to get the user/password first. Then if the option is toggled cache the info, the WebClient application will use the cached authentication, the authentication dialog will no longer continue prompting for authentication.