429 The custom error module does not recognize this error - acumatica

Every once in a while, while I'm using Contract-Based Acumatica Web Services API, I receive an error message like so:
HTTP 429
Server: Microsoft-IIS/8.5
X-Powered-By: ASP.NET
Date: Thu, 08 Aug 2019 20:38:29 GMT
Content-Type: text/html
Content-Length: 54
The custom error module does not recognize this error.

This happens when you go over your Maximum Number of Concurrent Web Services API Requests or Maximum Number of Web Services API Requests per Minute limit.
In the License Monitoring Console (SM604000) it should show up as a Declined Number of Web Services Requests
More information about License Monitoring Console (SM604000):
https://help.acumatica.com/Help?ScreenId=ShowWiki&pageid=06869c57-819d-4626-a5a8-72507e6a79d8

Related

POST to BotFramework using Node

I have a BotFramework v4 deployed in Azure using the virtual agent template and have been trying to POST to the endpoint to have a message sent to users in Teams but the response received is a 400 Bad Request. We can perform a POST using Postman with the same information and it will post without issue. The Bot is deployed using C# while the software we are using requires node to perform the fetch/https request.
Local testing of the code is below with some information redacted. Tried using HTTPS request as well and got the same results of 400 Bad Request
Update
We got an HTTPS request working in local testing but once published to Azure and sending the POST to the Azure url, we get a 200 response but the POST is not going to the MS Teams conversation as expected. Application insights shows no errors.
Update 2
Using live metrics found that when sending the POST to the bot this is the error received:
System.ArgumentNullException: Value cannot be null. (Parameter 'clientSecret')
at Microsoft.IdentityModel.Clients.ActiveDirectory.ClientCredential..ctor(String clientId, String clientSecret)
at Microsoft.Bot.Connector.Authentication.MicrosoftAppCredentials.b__14_0()

I am trying to implement paytm subscription

I am putting the values of mandatory parameter in step-2. but it gives error that Something went wrong. The transaction request sent by you is incorrect. Kindly email your MID - XXxVMh74422683748269, Order ID - TEST_1593759129069 and order time - Jul 3, 2020 12:22
Here is the link for subscription-payments in paytm
https://developer.paytm.com/docs/v1/subscription-payments/
Paytm Subscription is enterprise solution and it require to be enable on the paytm backend system on the merchant ID (MID).
Looks like the subscription is not configured for your merchant id( mid) at Paytm side. Please raise the request to developer support. Kindly check after subscription gets configured on your mid in staging environment.

Azure CSP Subscription Usage information

Does anyone know if it is possible to retrieve current usage information for a CSP subscription. I have looked at the Partner API but this only gives usage information at a aggregate level. I would like to have information per service running in Azure.
The official microsoft docs provide to use the rest api or C# code for retrieving montly usage based information.
To call this api will give you a monthly usage. https://learn.microsoft.com/en-us/partner-center/develop/get-a-subscriptions-resource-usage-information
GET https://api.partnercenter.microsoft.com/v1/customers/{customer-tenant-id}/subscriptions/{id-for-subscription}/usagerecords/resources HTTP/1.1
Authorization: Bearer <token>
Accept: application/json
MS-RequestId: 65b26053-37d0-4303-9fd1-46ad8012bcb6
MS-CorrelationId: 47c36033-af5d-4457-80a4-512c1626fac4

Java based configuration for Fax Inbound/Outbound for Interfax API using Spring Integration, HTTP outbound gateway with basic authorization

We are trying to implement the Fax Inbound/Outbound messaging using the Spring Integration gateways using the Java based configuration with Interfax API.
The rest services are :
outbound : https://rest.interfax.net/outbound/faxes
Inbound: https://rest.interfax.net/inbound/faxes
Can you please help, how the payloads will be for this API, which will contain fax_number, file, content_type, etc.,
How the gateways can be created for both the Inbound & Outbound faxes. Please suggest the approaches.
We now offer an easy-to-use library for Java to allow customers to easily integrate the InterFAX API into their own system.
For the outbound API, to send a fax, all you will need is the file you wish to send, the fax number of the destination and the credentials for InterFAX.
The request to the API to send a fax should look something similar to the following (assuming you are sending a PDF file):
POST /outbound/faxes?faxNumber=0018885551234&reference=this is my fax HTTP/1.1
Host: rest.interfax.net
Authorization: Basic ZXlhbG5ldm86WkFRIXphcTFuaHk2
Content-Type: application/pdf
Cache-Control: no-cache
[file binary content goes here]
For the inbound API, you can search for faxes to retrieve their metadata and then you download the fax image of a specific fax.
The request to the API to search for faxes would look something like this:
GET /inbound/faxes?limit=10 HTTP/1.1
Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=
Host: rest.interfax.net.
InterFAX also offers a callback system (for both inbound and outbound faxes) -- you can read this article comparing the differences between polling and callback -- which will push notifications and status updates to customer's web service - for outbound faxes, once the fax has been completed processing and for inbound faxes, once a new fax has been received.
We would recommend to build a gateway that based on a callback input from InterFAX for inbound faxes, the gateway will store all fax metadata in the callback and then proceed to download the fax image - storing all information in a location accessible by the end user.
For outbound faxes, you will need to create a form submission of some kind for the end customers to submit their fax information. Once submitted, the fax will be submitted to InterFAX via the API and the resulting fax transaction ID (which is returned to you as the response for submitting the fax), will be stored in a local database.
Once the fax has been completed, the callback will trigger an update to your system to update the fax records in your database.

Sending Email on behalf of a different username other than authenticating username

I have a docusign developer account in demo.docusign.net. I am integrating my application with docusign through SOAP API. I want to send signature email notification through a different username other than authenticating user. I guess my requirement is close to SOBO(Send On Behalf Of) feature in docusign. But when I am building the SOAP Header like below it is throwing an error
Error : "This User lacks sufficient permissions. Fail to resolve SendOnBehalfOf user"
Soap Header:
r.Headers.Add("X-DocuSign-Authentication", String.Format("<DocuSignCredentials><Username>{0}</Username><Password>{1}</Password><IntegratorKey>{2}</IntegratorKey></DocuSignCredentials>", "[memukesh#yahoo.com; Mka Agr]" & UserName, Password, IntegratorKey))
Raw XML:
POST https://demo.docusign.net/api/3.0/dsapi.asmx HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.5420)
X-DocuSign-Authentication: <DocuSignCredentials><Username>[memukesh#yahoo.com; Mka Agr]163ef546-49fd-487c-90a5-cbd0c40d174f</Username><Password>XXXXX</Password><IntegratorKey>TEST-54822f15-d597-40bf-a835-c5fd9241f97f</IntegratorKey></DocuSignCredentials>
VsDebuggerCausalityData: uIDPo59vkwnnhgJAhoiRA3V9nFwAAAAASqymGNrUZk6ydtO1QDqOu14YrRe53eBIkSLy+CUq/l4ACQAA
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://www.docusign.net/API/3.0/RequestStatus"
Host: demo.docusign.net
Content-Length: 378
Expect: 100-continue
Connection: Keep-Alive
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><RequestStatus xmlns="http://www.docusign.net/API/3.0"><EnvelopeID>ba96b207-057f-4dbe-9696-b8ea28a2da7d</EnvelopeID></RequestStatus></soap:Body></soap:Envelope>
Can you please tell me whats wrong here?
With DocuSign you never need an account to sign documents and signing is always free, however, you do need a DocuSign account to Create and/or Send signature requests. With that said, using SOBO is indeed one way of showing a different user name as the sender, but you can only use SOBO for authenticated users in the same account.
Therefore, if you want to show two different senders the best way is to create users for every unique sender you have. Based on the account plan that you purchase you're allowed a given amount of users on that account plan. You can create/add users manually through the Web Console or programmatically through the REST or SOAP APIs.
See here for creating new users through the REST API.
See here for creating new users through the SOAP API.
Note that you can also create new accounts through the APIs as well though to do so you need to contact your account manager for a distributor code and password.
Looks like you have the format within right:
<Username>[mysoboemail#email.com]myconnectingemail#email.com</Username> (or use userid instead of email).
I think you just need to change [memukesh#yahoo.com; Mka Agr] to only be [memukesh#yahoo.com]. Remember that email has to be associated with a DocuSign account as well

Resources