CRM Plugin Registration Tool Error - An unsecured or incorrectly secured fault - plugins

I'm trying to run the CRM Plugin Registration Tool for the first time and I'm getting the following error: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.
I'm using the following for the Discovery URL as it's web based CRM: https://dev.crm.dynamics.com.
User name and label are correct.
Thanks in advance.

I had same issue in registering new assembly.
My problem solved in this way:
1- Close current connection in Plugin Registration Tool.
2- Create new connection to server (login again). If you couldn't login, you should reset IIS or Recycle Application Pool or (at least) Restart Server.
Best Regards.

Related

Drools controller URL responding with error code 405

We are exploring Drools BPM for one of our new project. I am basically from .Net background and doesn't have much knowledge with java techs.
Our expectation is that we should able to create rules and workflows using Drools so that it can be exposed as REST API's and then the rules should be executed from .net/angular client applications using this REST.
I have configured the KIE server using WildFly10 server. It seems that all my configurations are working fine but when i try to connect to controller ("http://localhost:8080/kie-wb/rest/controller") it gives the below error message.
Error Message :
2018-01-22 12:30:09,263 INFO [org.kie.server.controller.websocket.client.WebSocketKieServerControllerImpl] (KieServer-ControllerConnect) Kie Server points to non Web Socket controller 'http://localhost:8080/kie-wb/rest/controller', using default REST mechanism
2018-01-22 12:30:09,263 WARN [org.kie.server.common.KeyStoreHelperUtil] (KieServer-ControllerConnect) Unable to load key store. Using password from configuration
2018-01-22 12:30:09,274 WARN [org.kie.server.services.impl.controller.DefaultRestControllerImpl] (KieServer-ControllerConnect) Exception encountered while syncing with controller at http://localhost:8080/kie-wb/rest/controller/server/wildfly-kieserver error Error while sending PUT request to http://localhost:8080/kie-wb/rest/controller/server/wildfly-kieserver response code 405
The below URL's are working fine
http://localhost:8080/kie-wb
http://localhost:8080/kie-server/services/rest/server/
http://localhost:8080/kie-wb/rest/controller/management/servers
I was able to get both workbench and kie server to work on the same web and/or app server following various examples that are proliferated on the internet. However, I encountered this particular error when setting up for a more realistic production ready environment using separate app servers on the same host running on different ports. The issue is, the REST version of the url is only supported when both workbench and kie server are running on the same app or web server. When on separate app or web servers, it must use web sockets (see docs for property org.kie.workbench.controller):
http://docs.jboss.org/drools/release/7.8.0.Final/drools-docs/html_single/#_wb.systemproperties
Only Web Socket protocol is supported for connecting with a remote Kie Server Controller. When specifying this proporty, the Workbench will automatically disable all the features related to running the embbeded controller.
After reading this, the 405 makes sense (method not allowed). I changed the URL from
http://ACTUAL_HOST_NAME:8080/kie-drools-wb/rest/controller
to
ws://ACTUAL_HOST_NAME:8080/kie-drools-wb/websocket/controller
and that resolved the 405.
Also, I was originally using 'localhost' for the actual host name, but it still would not connect, so I changed it to the actual host name. Finally, I was still seeing a connection problem and then found out that both servers need
-Dorg.kie.workbench.controller.user=kieserver
-Dorg.kie.workbench.controller.pwd=kieserver1!
-Dorg.kie.server.user=kieserver
-Dorg.kie.server.pwd=kieserver1!
to be set on both servers (See https://groups.google.com/d/msg/drools-setup/Bpt-r_bIa2U/g0H1J77sBgAJ and https://groups.google.com/d/msg/drools-setup/Aru_F98nL9g/Z6vUCm6hBQAJ).
Edit:
After fiddling with it some more and read the documentation a little bit more, the referenced documentation was referring to workbench connecting to an external controller, instead of configuring the controller within workbench.
After much torment, my problem was solved by adding role "kieserver=kie-server,rest-all" and user "kieserver" to Business Central Workbench.
Without this data, I consistently received 405.

Web Deploy not working. Timeout on client. Schannel 1203 on server

I'm trying to deploy an application via web deploy to a windows 2012 r2 server.
First tried installing iis, web deploy using the msi. After getting an unreachable error I saw somewhere that I needed wmsvc to be installed and installed it via powershell command Install-WindowsFeature Web-Mgmt-Service.
I stopped getting the unreachable error and started getting this error ->
Error: Could not complete the request to remote agent URL 'http://xx.x.xx.xx:8172/MSDEPLOYAGENTSERVICE'.
Error: The operation has timed out
On the server's event viewer under system I get the following error ->
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1203.
Any idea of what could be going on? Did I miss something on the installation?
After this I also tried installing everything but without iis and I get the same error.
So, this is really not a PoSH issue.
Maybe you should consider movin gthis question to another forum.
Anyway, you have either real server config issues (this can sometimes mean wipe and rebuild - very ugly option - but if it's a virtual machine and you have a snapshot, just roll back), or an app causing this.
Typically for Schannel type of error, it has to do with application or service in machine not able to complete any SSL connection sort of connection.
The error state parameter of 1203 means client error connecting to server, ie invalid ClientHello from the client
See if you can collect more data by...
https://support.microsoft.com/en-us/help/260729/how-to-enable-schannel-event-logging-in-iis
I realized this is an old question, but in case somebody ran into the same issue, here are my solution.
I had to follow this guidelines : https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-web-deploy-handler
Copy the resulting publishsetting file. In the Publish/Profile page import it.
In the Publish/Connection page, change the server to the server address with the 8172 port. Add the password. Change the Destination URL to the site to go to after the publish is completed.
Then after Validate connection was completed, go ahead and publish it!

Gateway Timeout when accessing Bluemix WEB IDE/Node.js logs

I am using Web IDE and want to see the log by clicking on the arrow.I can only see an empty "Untitled" page. The Node.js app is running normally. Live edit is switch off.
After some minutes:
Gateway Timeout
The proxy server did not receive a timely response from the upstream server.
Reference #1.45bf1402.1511018717.3dddb8b
I'm not for sure what Web IDE you are referring to. The only one I'm aware of is the DevOps (which works for me below):
It seems to me like this error that you posted would indicate a temporary outage. Is it still an issue?
In any case, I would advise opening a support ticket if you encounter this issue again (more details about your account would help). I think the Bluemix proxy will time out requests if they take too long.

error opening dashDB

After I have added a service dashDB to my Bluemix application and I click on it, I got in IE11 this message:
The website declined to show this webpage
HTTP 403
When I did the same in the Google crome I got a square head which looked sad.
Does anyone know what to do?
Thank you!
There is not much information to go but I would suggest the following to narrow down the cause of the problem or resolve the issue:
- verify that service has been provisioned successfully (unless it's an existing instance that is known to work in the past)
- clear browser cache/restart to eliminate any transient issues
- BlueMix status page (https://developer.ibm.com/bluemix/support/#status) is currently reporting some authentication issues which potentially could cause problem, it should be check if the 403 error is still reported after the problem is resolved.
It might be worth to create the service with the "leave unbound" option and try to click on it. After you could bind it to your app.
You can verify if the dashDB instance is up or not by accessing the https_url from the VCAP variable associated with the dashDB instance (for e.g.: https://bluemix05.bluforcloud.com:8443) and provide your username and password (also from the VCAP variable) for that instance and see if you can log in.

How do I get more details on my request error on IIS7

I have deployed a REST service on an external server (IIS7). When I start the service from VS on the Dev server it works fine. But on the server i get:
Request Error, The server encountered an error processing the request. Please see the service help page for constructing valid requests to the service.
How do I get more details on this error? I have looked in the log files directory that is configured under Logging feature for this web site in IIS Manager, but there are no files at all for this site it seems.
You should look in the Windows Event Log using the Event Viewer application (eventvwr.exe). Output to the IIS log files may be buffered so their contents may be updated after a restart, or when IIS is set to do it. Restarting IIS is a surefire way to force this.
Here is a blog post on how to do this.
I'm aware of 3 ways to get nicer errors:
Set UseVerboseErrors in InitializeService method. However, this won't give you anything if your error occurs before InitializeService is called (which happens).
Set IncludeExceptionDetailInFaults to true using an attribute before your service class.
Set IncludeExceptionDetailInFaults to true using web.config.