I'm configuring the adapter for AX, all the steps in the configuration have been performed.
In the inbound ports I found this one: http://servername/MicrosoftDynamicsAxAif60/ScribeAxWebService/xppservice.svc but I get this error:
Connection Error: The HTTP request is unauthorized with client
authentication scheme 'Anonymous'. The authentication header
received from the server was 'Negotiate,NTLM'.
If I go in AX and change the security mode to "None" for using anonymous authentication then I get
The client and service bindings may be mismatched.
The remote server returned an error: (415)
Cannot process the message because the content type
'application/soap+xml; charset=utf-8' was not the
expected type 'text/xml; charset=utf-8'..
Where can I find the right one?
Your question is for propriety software, so this isn't exactly the right forum for it, but I've used some older versions of Scribe (4+ yrs ago).
I'd guess the domain user account running the Scribe service is not added as an AX user. Where are you getting "unauthorized"?
You already have indicated that web.config is changed, but there is a good example on MSDN, see the section XML Snippet from Web.Config. There are TWO changes to be made. The wsHttpBinding section, and then to each service that it's binding = "wsHttpBinding" is correct.
Finally, I also add a log file to AIF during the testing phase.
Related
I have just exposed my database on openshift and it gives me an 'https://....' url
Does anybody know how to connect using DBeaver by using this url that openshift gave to me.
The error that dbeaver says to me is the following
Malformed database URL, failed to parse the main URL sections.
Short answer: You can't with aRoute
Route can only expose http/https traffic
If you want to expose tcp traffic (like for a database), do not create aRouteand change yourServicetype to "NodePort"`
Check my previous answer for this kind of problem (exposing MQ in this case): How to connect to IBM MQ deployed to OpenShift?
OpenShift doc on NodePorts: https://docs.openshift.com/container-platform/4.7/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.html
There's another way to do this.
If your Route is set to "passthrough" it will just look at the SNI headers to determine where to route the traffic but won't unwrap it (and expect http inside) which will let it pass other traffic through to a pod.
I use this mechanism to run a ZNC bouncer (irc traffic) behind SNI.
The downside is you need to provide your own TLS cert inside the pod instead of leveraging the general one available to *.apps.(cluster).com
As for the specific error, "Malformed database URL", I've not used this software but from a quick websearch it looks like you want to rewrite the https://(appname).(clustername).com into a jdbc:.../hostname... string, and then enable TLS in settings.
I found this page that talks about setting it up, so it might be helpful if you've not around found it -- https://github.com/dbeaver/dbeaver/issues/9573
I'm running SSRS 2016 on a local machine for development purposes. I've been running into this error quite frequently and spontaneously, as in I will run a report, then 3 minutes later try running the same report with the same parameters and all of a sudden my config is broken without changes. I start mucking around with the configs and eventually, seemingly spontaneously, again it will start working again. Then the cycle continues where it works for 1 hour - a few months before just breaking again.
Here is the screenshot from my Web Service URL:
The actual error message from the log is:
ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: AuthzInitializeContextFromSid: Win32 error: 1355, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
When I google that error message I get a bunch of forum posts about sending emails and email configuration but I'm not trying to send emails nor do I have any email stuff configured.
Here is the configuration I'm using under Reporting Services Configuration Manager:
Service Account:
User Another Account (My Domain Account) I've also tried every combination of built-in account which also seem to work when the server doesn't throw this error..
Web Service URL:
IP Address: All Assigned
TCP Port: 80
HTTPS Cert: N/A
HHTPS Port: {blank}
Database:
My Local SQL Server instance and Report DBs using Windows Account login
Email Settings (all default settings):
Sender Address: {blank}
Current SMTP Delivery Method: Use SMTP Server (drop down is read only cannot be changed)
SMTP Server: {blank}
Authentication: No Authentication
Execution Account:
Specify an existing Account: unchecked
Subscription Settings:
Specify a file share account: unchecked
I've also restored and changed encryption keys numerous times and deleted all Encrypted Content under the Encryption Keys Pane. I always use the same snk file for the key and same password so I know it's correct.
If there's any additional information I can provide to help, please let me know. I know this is a bit of a longshot but it's really annoying and impedes my productivity developing SSRS reports.
Thanks in advance.
Well, after more googling, half way down the first page of results I finally came across this article:
https://support.microsoft.com/en-ca/help/3171505/fix-the-service-is-not-available-error-when-you-use-ssrs-2016-portal-a
I downloaded the suggested Cumulative Update 2 for SQL Server 2016 and low and behold, my local setup is working again. Could this be just a coincidence? Absolutely. I will report back if it dies again with the same error but I'm hopeful for the time being.
I am using the fabric8 library to create replication controllers on the kubernetes cluster. When I create areplication controller with the name rc-UUID.toString();
It errors aout with the following message
ReplicationController is forbidden. What does this indicate?
I don't think that the problem is the name.
Names like: rc-fa75ddfd-bea7-45b5-8d2f-ed806652b461 are valid.
Usually the message forbidden appears in one of the following cases:
i) http status code 401
ii) https status code 404
Error (i) appears when you are connecting to a remote Kubernetes Environment and can be solved by login in. Try kubectl login or oc login.
Error (ii) appears when the client is instantiated from within Kubernetes and the service account hasn't been properly configured.
Either way, I'd strongly encourage you to upgrade to a more recent version of the cabernets client, which has more meaningful error messages.
If none of my suggestion solves your issue, please attach the full output.
Cheers
I have configured SCIM inbound provisioning in pingfederate 7.2.0 using Active Directory as an user store. But when I hit the URL exposed by ping to search for an user I get the following error on the browser-
{ "totalResults":0,"itemsPerPage":0,"startIndex":0,
"errors":[{"description":"User and/or certificate not found","code":"401"}]
}
In the logs it says
11:34:29,251 DEBUG [Authenticator] AuthnInfo: ID='null' cert:false
basic:false from CERT:'null' BASIC:'null' 11:34:29,251 ERROR [UsersIdResource]
Unable to find a connection associated with the username/password and/or
certificate passed in with the request.
11:34:29,252 DEBUG [TrackingIdSupport] [cross-reference-message]
entityid:null subject:ranajoy
Can someone please help me with this?
I was having this exact same issue. I set up my Provisioning connection correctly, and it worked in other environments, and everything looked good. But then I got this error. If I changed the Basic Auth to a bad password, the error message at least changed to "Bad Password for <user>".
I took another look at my connection and realized I never actually activated the connection:
How do I configure SSRS/Windows Server 2003, so that I can setup email delivery via a remote SMTP server that requires username and password.
I can configure SSRS with an SMTP address and other parameters, but nowhere is it possible to configure it with smtp username and password.
I have hunted around, but can only find vague reference to setting up some sort of relay, to cover up the bizarre lack of smtp functionality that SSRS has out of the box.
Any ideas?
Here are the steps to set this up using only Microsoft SSRS/Windows Server 2003 components.
1) Install SMTP server in Add/Remove programs / App Server / IIS
In IIS Manager:
2) add the domain (as a remote type) you will be sending as such as yourwebsite.com
3) Under Default SMTP Virtual Server properties / delivery tab / advaced button, add your remote smtp server in the smart host field.
4) Under Default SMTP Virtual Server properties / delivery tab / Outbound security button, choose Basic Authentication, user name = SMTP user name, password = SMTP password
In the rsreportserver.config file (sql drive:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer):
5) Populate <SMTPServer>x.x.x.x</SMTPServer> with the IP of the machine where you just setup the SMTP server.
6) Populate <From>you#yourwebserver.com</From>
7) Change this one to false <SendEmailToUserAlias>False</SendEmailToUserAlias>
8) Lastly, make sure you setup the domain as a permitted host such as this:
<PermittedHosts> <HostName>yourwebsite.com</HostName></PermittedHosts>
As far as why SMTP basic authenication isn't supported directly in SSRS seems to be by design. The best explaination I could find was here on this MSDN forum:
As one poster here mentions, there is a Microsoft Connect ticket open for people who are requesting this functionality.
For sure you have already solved this issue, but let me put here an additional information so others that have this same problem, like me, can solve it by following this how to that Tom Willwerth post.
To solve this issue of SMTP relay just follow the steps above, but be sure to do an additional step, that can be called:
4-a) On Access tab, choose Relay and select "All except the below" on Select which computer may relay through this virtual server:
This will allow all connections to send through this smtp, but be aware that the smtp server will relay anyone who connects to it. If you want to restrict this relay, than you choose "Only the list below" and add the machine you want to relay on.
For more detailed information on this, you can see the source where i found this information on:
http://businessintelligencechronicles.blogspot.com/2010/08/configure-reporting-services-to-use.html
And another thing, the step 8) isn't necessary .
Hope it can be helpful to others and thank you for the information, it helps and now i think one can solve this issue just by following this steps on this link.
Regards
Ps: sorry for the mistakes
This might help you a little: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\rsreportserver.config contains all of the configurations settings in the . I don't see exactly what you want so you'll probably have to perform some relay tricks.