This content has been marked as final. Show 3 replies
You possibly have your proxy settings to be set correctly on your training lab computers. If the browser encounters a problem and needs to close, proxy settings need to be altered. Move the message that says there is a problem and make a note of the server address (IP/URL) which is launching the Siebel application. Now you need to include the Siebel server as a proxy exception (IE Options, Connections, LAN settings, Advanced (proxy server settings), Do not use proxy server for addresses beginning with <noted address>).
Let me know if this helps.
Did you manage to fix this? One of my clients is facing exactly this problem. Could you please share if you managed a fix?
See Oracle support details & inpromation:
We are getting an "AppErrCommunication" error when accessing "About View", "Save Query As", "Record Count", and just about every other Siebel menu item dropdown throughout the application.
However, MVG applets, pick applets, etc. are fine.
This is happening with both thick and thin clients.
After comparing that specific desktop with another users and looking for differences between those machines, when it dawned on that screen resolution was set fairly high.
After lowering the setting, it worked fine.