Testing the Cadacus WCF Service:
To test whether the Cadacus WCF Service is properly connected, functioning, and not restricted by a firewall port block or a device configuration, open a browser on the server where the service is installed and running; then enter the following URL (note for the testing in this section, the URL is NOT case sensitive):
OR, rather than "localhost", enter the IP of the machine where the service is running. For Handheld WMS configuration setup, using the IP address (rather than "localhost") is recommended, so using this example would be a good test for that purpose:
In any case, the following XML response should be returned:
To test the validity of the SYSPRO username and password, enter the following URL:
The returned results should be as follows:
If the above response is not returned, check the registry settings as follows:
1. Go to Windows Services and stop the CadacusWCFService; if there is more than one Cadacus WCF Service running, "end task" in Task Manager for both.
2. Modify the login by going into REGEDIT and find one of the keys below depending on if the server is 64 or 32 bit:
-- For 64 bit servers the key "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cadacus\WCFService"
-- For 32 bit servers the key "HKEY_LOCAL_MACHINE\SOFTWARE\Cadacus\WCFService"
3. Edit the entries for "Company", "CompanyPassword", "User" and "UserPassword" entries as necessary. The use of a SYSPRO username NOT used by anyone else is recommended. This user must be enabled to access the SYSPRO query business object.
4. Go to Windows Services and restart the CadacusWCFService.
- To check the version of the WCF service installed, enter the following URL, which should return version information, as in this example:
More troubleshooting if the WCF Service stops
If the Cadacus WCF Service continues running after attempting handheld transactions, the issue is likely to be related to other network communications.
However, if the service check is not working and the WCF Service is stopped after any communications, it might be due to having more than one version of SYSPRO on the server which tends to cause an e.Net registration issue and may be addressed as follows:
-- Find the icon for the command prompt. Right click and choose "Run as administrator". It is not good enough to be logged in as administrator. The word "Administrator" should be in the title of the window when it is running.
-- While in the "Administrator" command prompt, changed directory (CD) to the SYSPRO base folder and run the following register command:
The command line should return a message that the dll was successfully registered.
-- Now, go to Start-->Run RegEdit
Go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SYSPRO\e.net solutions
In that registry setting, look at the BaseDir value and make sure it points to the proper SYSPRO base folder (example shown below)
-- Restart the WCF Service