Can ProjectWiseWSGConnector connect to a local server, and if how ? What should I put into the Bentley ProjectWise Connection Parameters ? It seems like the URL i use in ProjectWise doesn't function in FME.
Solved
Connect via ProjectWiseWSGConnector to local server - Need help connecting to local projectwise server
+6- Contributor
Best answer by david_r
In theory it should be able to connect to any server, as long as there is a network connection. So first step is to verify any firewalls.
Also, you cannot use URLs starting with "pw:\\\\", the FME web connection URL should look something like this: https://hostname.domain.com/ws/
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
- Best Answer
In theory it should be able to connect to any server, as long as there is a network connection. So first step is to verify any firewalls.
Also, you cannot use URLs starting with "pw:\\\\", the FME web connection URL should look something like this: https://hostname.domain.com/ws/
+6- Contributor
In theory it should be able to connect to any server, as long as there is a network connection. So first step is to verify any firewalls.
Also, you cannot use URLs starting with "pw:\\\\", the FME web connection URL should look something like this: https://hostname.domain.com/ws/
Hey David,
thank you for the quick response.
Just to be sure, so if my url would be:
pw:\\\\test-example.bentley.com:example-pw-01\\Documents\\
instead it should be :
https://test-example.bentley.com.example-pw-01/Documents
And if that returns :
Retrieval Error: Unable to make the request to web service. Ensure your machine has internet connectivity
It's probably a firewall.
Hey David,
thank you for the quick response.
Just to be sure, so if my url would be:
pw:\\\\test-example.bentley.com:example-pw-01\\Documents\\
instead it should be :
https://test-example.bentley.com.example-pw-01/Documents
And if that returns :
Retrieval Error: Unable to make the request to web service. Ensure your machine has internet connectivity
It's probably a firewall.
Try https://test-example.bentley.com/ws
Notice the "/ws" endpoint, as you need to point to the ProjectWise web service gateway (WSG), not to any of the contents.
+6- Contributor
Hey David,
thank you for the quick response.
Just to be sure, so if my url would be:
pw:\\\\test-example.bentley.com:example-pw-01\\Documents\\
instead it should be :
https://test-example.bentley.com.example-pw-01/Documents
And if that returns :
Retrieval Error: Unable to make the request to web service. Ensure your machine has internet connectivity
It's probably a firewall.
Thanks again, it still fails to connect, so I'll look into firewalls now.
Hey David,
thank you for the quick response.
Just to be sure, so if my url would be:
pw:\\\\test-example.bentley.com:example-pw-01\\Documents\\
instead it should be :
https://test-example.bentley.com.example-pw-01/Documents
And if that returns :
Retrieval Error: Unable to make the request to web service. Ensure your machine has internet connectivity
It's probably a firewall.
The URL should also work in a browser, which is fairly helpful for testing the connection.
+6- Contributor
Hey David,
thank you for the quick response.
Just to be sure, so if my url would be:
pw:\\\\test-example.bentley.com:example-pw-01\\Documents\\
instead it should be :
https://test-example.bentley.com.example-pw-01/Documents
And if that returns :
Retrieval Error: Unable to make the request to web service. Ensure your machine has internet connectivity
It's probably a firewall.
Great thanks!
Too long to response -- ERR_CONNECTION_TIMED_OUT
So it looks like firewall.
+6- Contributor
Hello David,
A new problem has arrived.
I can log on via my browser, but not via the ProjectWiseWSGConnector.
Would it be a problem if my version is
And the ProjectWise Web API version selectable in the webconnection in FME is 2.4?
Thanks in advance
best regards
Jonathan
+6- Contributor
Update:
I forgot this, the problem appears when I try to acces a repository.
Hello David,
A new problem has arrived.
I can log on via my browser, but not via the ProjectWiseWSGConnector.
Would it be a problem if my version is
And the ProjectWise Web API version selectable in the webconnection in FME is 2.4?
Thanks in advance
best regards
Jonathan
I think you should be OK for the API version.
The error message you see comes directly from the ProjectWise WSG, so basically double check the username and password. Also check that the user has sufficient rights to any repository that you're trying to access.
+6- Contributor
I think you should be OK for the API version.
The error message you see comes directly from the ProjectWise WSG, so basically double check the username and password. Also check that the user has sufficient rights to any repository that you're trying to access.
The error persists when trying to connect through FME.
Are there any dependencies or anything I'm missing?
I think you should be OK for the API version.
The error message you see comes directly from the ProjectWise WSG, so basically double check the username and password. Also check that the user has sufficient rights to any repository that you're trying to access.
In my experience, there should be no dependencies. It could perhaps be worth it to intercept the API calls using something like Telerik Fiddler and see what happens. But based on the error message it's fairly certain that the WSG isn't accepting the username/password combination, which shouldn't have anything to do with the API version, as it's using http basic authentication in all cases.