User has a client in a remote office who has installed Projectwise Explorer, but when they launch it, no datasources appear in the window.
In order to connect to a datasource the Projectwise Network Control DNS and Datasource tabs need to be populated, Port 5800 needs to be open bi-directionally, and if the network is being restricted, the FQDN for the ProjectWise server you are connecting to needs to be allowed through any proxy \ firewall filters.
Go to Control Panel, then double click the ProjectWise Network icon
On the General Tab, solid check the “Prevent UDP”
On the DNS Services tab, enter in a name for the connection, under Host Name enter in the FQDN name of the server you are trying to reach, and under port put 5800, then click add
On the Datasource Listing tab, enter in a name for the connection, under Host Name enter in the FQDN name of the server you are trying to reach, and under port put 5800, then click add
Click apply and okay. Launch Projectwise Explorer to see if this process solved the problem
Note you can also get to the ProjectWise V8i Network Control by launching Projectwise explorer, then choosing Tools \ Network Configuration Settings.
If Telnet is not installed on the client machine, go to control panel, programs and features, click the link that says “ turn windows features on or off”, a new window will pop up, turn on Telnet Client. Click okay.
Telnet should be run from the command prompt on the client machine. Go to start, run, then type cmd. (you may need to run as administrator depending on how locked down the system is)
Example command line: Telnet Projectwise.Bentley.Com 5800
Where Projectwise.Bentley.Com is the information that the you enter into the ProjectWise network control for the connection to your server.
If it does not connect, then port 5800 is blocked somewhere on the network.
Or it could be that the address (in this example:Projectwise.Bentley.Com) needs to be allowed through the firewall.
Unblocking the port and or address is a Network administrators job. Allowing access to the FQDN is also a network firewall issue. It is not a client side problem unless the client has their client firewall locked down.
Running Telnet will prove to the network admin that the port and or address is blocked.
Go to Start \ Programs \ Bentley \ Projectwise \ Tools \ User Tools \ Windows Socket Analyzer
Protocol name: TCP (Click Next)
Service Name: dms (Click Next)
Port number: 5800 (Click Next)
Remote host: <FQDN of server you are trying to reach>
Click next and it should resolve the Ip address of the server you entered
Click next again and the clients name and IP address are resolved.
Click next again, and the tool sends a bit of data to the Projectwise server.
If it is successful, then at the bottom of the tool you will see a message that says " Connection to remote host established and closed successfully"
If it fails you will be presented with an error message with the possible cause of the problem.
Go to C:\Program Files (x86)\Bentley\ProjectWise\Bin and open pwc.log.xml with notepad
Choose Edit \ Replace
Under Find What type =”warn”
Under Replace With type =”all”
Click replace all
Now choose Edit \ Find
Look for the work Hook
If found change the priority value from "all" back to "fatal"
<category name="pwise.hook"> <priority value="all"/></category>
<category name="pwise.hook"> <priority value="fatal"/></category>
Save and exit the file
Go to C:\Users\<user name>\AppData\Local\Bentley\Logs and delete the pwc.log
Launch Projectwise Explorer. Then open the pwc.log file in notepad
Choose Edit \ Find, the look for the work ERROR and match case.
The most common problems are:
Reverse DNS lookup is not configured for the server you are configured to connect to, or that a server listed in the Gateway section of the dmsknrl.cfg on the server you are connecting through is not configured correctly
The Gateway section of the dmsknrl.cfg on the server you are connecting through is not configured correctly, either has an incorrect address, miss spelling, etc.. or your ipaddress has been denied access.