Tech Articles


How to deal with the error 'No Network Connection' on logon to PowerBuilder


ISSUE: Receive error “No Network Connection” on logon to PowerBuilder

 

SYMPTOM: Error “No Network Connection” was received on every attempt to open PowerBuilder and occurs immediately on version installation. Experienced on install of  V19 - but may be experienced in other versions.  When initiating PowerBuilder process hangs for a long time and then returns a message “No Network Connection”. You exit and the application closes.

 

TEMPORARY WORKAROUND:  You can get into PowerBuilder bypassing this error by first logging into the portal of Appeon using your provided logon ID and password , then clicking on a PBW file type in your source repository. Do not go into directly into PowerBuilder first.

 

CAUSE: The issue is caused during the license verification process. The PowerBuilder application goes out to 1 of 2 URL’s (api.appeon.com and api2.appeon.com) to verify your license is up to date. Normally, these URL's would be allowed by proxy policy, if the request was made to the proxy from the software component – however our site does not use/allow “transparent proxies” – browsers and software components must be configured to make requests to the proxy explicitly. Since PowerBuilder is trying to access these api servers directly and not via our proxy the service is stopped and you receive the error “No Network Connection”.

The PowerBuilder software is not capable in V19, and other versions, to configure explicit proxy settings for the application.

 

RESOLUTON:  Create 2 Firewall rules for each PowerBuilder development PC allowing PC and its IP address direct communication (allows by pass of proxy policy) to the following Appeon license servers:

 api.appeon.com  -  192.237.225.82

api2.appeon.com -  18.218.182.153

After the rules are created logon direct to PowerBuilder occurs quickly and successfully.  

 

CONTENGENCY: Appeon servers noted above must remain static or this process will not be effective. Otherwise new Firewall rules will be required and you will need to obtain from Appeon the server names (if changed) and IP.   

 

WRITTEN BY: Robert D. Eckstine, Jr.

 

Comments (0)
There are no comments posted here yet

Find Articles by Tag

.NET Assembly Syntax ActiveX Resize Database Painter RibbonBar JSONParser .NET Std Framework Variable DevOps TFS Sort DataWindow JSON API Encoding Platform RESTClient 32-bit Export JSON 64-bit WebBrowser Debug Event Debugging Data Service Event Handler CrypterObject NativePDF Script UI Themes Icon TreeView Validation Database Profile Automated Testing SqlExecutor CI/CD Android DataWindow C# Azure PowerBuilder Compiler Excel .NET DataStore Web API PowerScript (PS) Deployment OrcaScript DLL Repository Database Table PBDOM Expression Transaction SnapDevelop REST Import JSON PowerServer Web Migration Error Export Oracle DataType Authentication Menu UI Modernization PostgreSQL Database Table Schema Event Handling IDE JSONGenerator OAuth Trial SVN Source Code TortoiseGit Windows OS SQL Server File JSON Text CoderObject Filter Elevate Conference Import SOAP Open Source PostgreSQL ODBC driver External Functions Stored Procedure PDFlib BLOB Design WinAPI PowerServer Mobile iOS Model RichTextEdit Control PDF PFC Jenkins Bug SnapObjects Performance COM Interface PowerBuilder Testing Debugger Branch & Merge Installation Git Mobile Database Object Windows 10 Icons SDK Source Control Class Graph Application OLE Encryption Window XML OAuth 2.0 DragDrop Database GhostScript Outlook License Array Authorization UI HTTPClient InfoMaker ODBC Configuration SQL RibbonBar Builder Web Service Proxy TLS/SSL MessageBox Charts Messagging PowerBuilder (Appeon) Database Connection Linux OS SqlModelMapper Database Table Data