I've created an HTTP inbound port. I'm able to access the services using Visual Studio. However, when I try to add the service to the wcfTestClient, I get the following error:
Failed to add a service. Service metadata may not be accessible. Make sure your service is running and exposing metadata.
c:\Users\firstname.lastname\AppData\Local\Temp\Test Client
Projects\10.0\45eaacda-a1b6-4b95-be46-7634658b8393\Client.cs(508,73) :
error CS0234: The type or namespace name 'Application' does not exist
in the namespace 'Microsoft.Dynamics.Ax' (are you missing an assembly
reference?)
Any ideas on what might be causing the issue or where I can look to find out more information.
Thank you.
Related
We installed fuse-online 7.4 on openshift 3.11. We created an integration containing an OpenApiProvider connection and an SQL connection.
When we publish the integration, the build fails with the following error:
"repo1.maven.org: Name or service not known: Unknown host repo1.maven.org: Name or service not known"
Openshift is installed behing an enterprise http proxy
The image registry.access.redhat.com/fuse7/fuse-ignite-s2i is pulled correctly since docker is configured with proxy.
syndesis-server DeploymentConfig has been set with proxies environment variables
I suppose that, since the buildconfig for the integration is created dynamically, is not possible to inject HTTP_PROXY,HTTPS_PROXY,NO_PROXY env variables to the build pod.
We read https://docs.openshift.com/container-platform/3.11/install_config/http_proxies.html#s2i-builds but since we don't have any rights to modify s2i image we cannot proceed.
Is there any way to provide proxy information during during fuse-online integration build?
Finally we succeeded to inject http proxy environment variables in dynamic created build pods.
We modified syndesis-server-config config map reporting proxy variables on mavenOptions key like this:
mavenOptions: "-XX:+UseG1GC -XX:+UseStringDeduplication -Xmx310m -Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttps.proxyHost= -Dhttps.proxyPort= -Dhttp.nonProxyHosts="
Thanks for the support
Let me know if you have any other idea of resolving the issue
Can you check the DNS of your network connection? Not sure why but sometimes I have to use one of the "reliable" DNS on my machine (like the 8.8.8.8 from Google) to make sure repo1.maven.org is reachable.
You can check if this is the problem trying a simple
$ ping repo1.maven.org
If that doesn't work, you have to check your DNS.
I have recently built a proxy service in WSo2 ESB that was not fully implemented. When I saved it generated a fault service message and a link was provided to a faulty service group at the top of the ESB console. Since then, I have corrected the service and it has been transferring files as I have intended. However the service does not show in the initial list of services and I have to click on the link 7 deployed service group(s) to now view it in the proxy list.
Here is what the link looks like:
6 active services. 7 deployed service group(s). 1 faulty service(s).
When I click on the 1 faulty service(s) I see the following but cannot delete it in an attempt to clear it.
*Faulty Service Actions
RenZipExtractProxy proxy
Unable to configure the service RenZipExtractProxy for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport.*
How do I clear this faulty service issue? My updated service works fine but I continue to get the faulty service situation as stated above.
You can manually delete deployment artifacts in the directory <ESB>/repository/deployment/server/synapse-configs/default/proxy-services
I have noticed that when we configure WSO2 esb with VFS protocol and do not provide any parameter then it is going under Faulty service. I resolved this problem after mentioning VFS related parameters.
Please refer https://docs.wso2.com/display/ESB481/VFS+Transport
Note: If we try to delete faulty proxy service from console then also it will not deleted. Please try to delete it from file system.
<ESB_HOME>/repository/deployment/server/synapse-configs/default/proxy-services
I installed a new instance of hybris server in a VM and made it available on a public internet page. I am trying to call the Product resource REST server or even a simple list of countries REST service.
http://xxx.xxx.com/ws410/rest/countries
However, I am getting an error with the status "HTTP/1.1 404 Not Found". Please can you help me?
Am I missing something? Should I Configure ws410 path somewhere?
Did you added platformwebservices extension into your localextensions.xml file ? Please ensure that you have below line in your localextensions.xml file
<extension name="platformwebservices" />
For more details check this.
ws410 is a default webroot path which is defined in platformwebservices/extensioninfo.xml file.
<webmodule jspcompile="false" webroot="/ws410"/>
Do you add the port 9001 par default on your URL. Try this http://xxx.xxx.com:9001/ws410/rest/countries
I am getting an error " There is no service with namespace = ' http://schemas.microsoft.com/dynamics/2008/01/services' and external name = 'ItemService' while running the batch using file system adapter. I went to different forums and as per the suggestions I made sure that the name of the namespace is correct in the services node in the AOT. I am not being able to understand why the system is not able to find the service with the given namespace. Any suggestions?
One cause of this problem can be an extra slash at the end of your namespace on the service node.
Remove it and it should work, as I describe here: AIF: There is no service with namespace = ‘http://yournamespace’ and external name = ‘aService’.
You might also want to do a refresh in the services form and a redeploy of your services after that.
I am using AppFabric 1.1 in IIS 7.5 on windows 7 machine to host my Workflows as service. Though I am able to see System endpoints and Application Default endpoints in AppFabric dashboard in IIS, I am not able to see my endpoints that I defined in Web.config file of the application.Also when I add Service Reference in my client projects, I can only see default endpoint configuration values provided by AppFabric. It appears that AppFabric is ignoring <'Service'> tag values in application's web.config file.What could be the reason? Is there something I might have missed ? Any suggestions are greately appreciated.
Thanks
I found the answer. When I changed the service name (in service tag element) exactly as it is in appfabric dashboard for the service, the application endpoints are showing up.