This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM. Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 5 years and 8 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
I was able to isolate the problem to the Uri object. In our hosts, it decodes the Uri but in the PowerShell.exe it doesn't. So, I dug into PowerShell.exe's config and found this:
This setting tells the Uri object to not escape those characters when creating a Uri object. We will need to update our config files to make this our default as well.
Thank you once again, for providing a test OData service. You can disable it now.
We will update on configure files in the next service release, but if you do not wish to wait, you can add the Url nodes to the ScriptDriver*.exe config files in the following folder:
This topic is 5 years and 8 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.