Check buildpro/tmp directory for webapimanager.log and xdev_err.txt to detemine problem.

Check Windows Registry (run regedit.exe) and make sure ConfigPath points to the correct path to the location of webapimanager.ini.

HKEY_LOCAL_MACHINE/SOFTWARE/TODAY Systems, Inc./BuildProfessional Web-API/ConfigPath

The ConfigPath determines the location of webapimanager.ini which in turn provides the configurations for the Web-API Manager.

If ConfigPath is set correctly, will always place log messages in webapimanager.log.
 

Test the connection with by running a status request from webapiclient.exe:

webapiclient.exe -s > status.xml

Open the status.xml in Internet Explorer or other editor to view the details. In the default setup there should be an "xdev" service.

Note. To check a server different from localhost, edit "host" in webapiclient.ini.
 

If your PC does not have IIS installed, you will need to change the file xdevProfile_user.xml. Change the XMLServer reference to c:\buildpro\web\bpxml (or the equivalent of your install directory).

Background: Certain xml resource files are required by the Developer. These are installed in c:\buildpro\web\bpxml. On Windows, the installation will create a virtual directory called bpxml via IIS to this path. On Linux systems, the virtual path must be created manually.

In a team environment, you will only need one bpxml resource on your LAN. Point all Developer profiles to this common bpxml resource. Example:

<XMLServer>http://teamserver/bpxml</XMLServer>

While too slow for daily work, you could also point to the TODAY Systems public bpxml resource:

<XMLServer>http://www.todaysystems.com/bpxml</XMLServer>